Hi there I am writing this guide as I have had hit and miss with windows 10 getting out of qcom 9008 mode, some times it works sometimes it don't, when windows is in normal mode you sometimes get I/O errors trying to blank flash
check list check you phone is in qcom 9008 mode if you have a blank screen go to device manager and click ports (COM & LPT)
in there you should see the 9008 mode is connected on one of the com ports if so your good to go.
1. Open a CMD prompt with admin privileges. Type in search CMD right click and select run as administrator.
in command prompt type Bcdedit.exe -set TESTSIGNING ON and hit enter, once complete restart you computer you will now be in test mode indicated in the bottom right hand corner.
2. Grab the blank flash file for N or O from here https://mirrors.lolinet.com/firmware/moto/nash/blankflash/
some have reported that even though they were running oreo that the oreo blank flash did not work and the Nougat blank flashed worked (I also had this problem and still have).
Create two folders (I use the names blank N and blank O but you can use whatever you like) extract the files from the blankflash zips to your named folders. once extracted run the Blank-flash.bat (windows batch file)
If this works you should be back too your bootloader.
3. Grab the prep file rootjunky.com created drop box link https://www.dropbox.com/s/ca62gr9aowdndzu/FlashAll_XT1789-05.zip?dl=0
don't worry that its for the xt1789-05 it should do the same for any variant
4. Grab the firmware for your device either from https://mirrors.lolinet.com/firmware/moto/nash/official/ or https://mirrors.lolinet.com/firmware/moto/nash/official/ (2nd link is the Z2 play folder our device has not got its own folder just make sure you get the file name starting with NASH and your Variant)
5. create a folder where you desire and extract the files from the prep file and your firmware to that folder (I name them flashall N or flashall O but you can use whatever you like ) once both extracted in that folder run the preparation.bat (windows batch file) this will create a flashfile.bat (windows batch file) from the flashfile.xml document from your firmware zip you extracted in this folder.
6. click the flashfile.bat (windows batch file) sit back and relax this will take a little while hopefully It has flashed everything correctly and your phone should reboot and your phone should be back to a working state
to get back out of test mode on windows follow instruction from number 1 and change ON for OFF
Hope this worked It did for me
Thanks to all from XDA for your help and all who provided the files on the links.
I will add some pictures next time I get back to qcom 9008 which I am sure I will.
The reason driver signing verification is disabled on windows during a blankflash is so that the qualcomm drivers can be installed, the previous ones weren't signed. However, in the other xt1789-05 thread there is a link to signed drivers that are win 10 compatible, so you shouldn't need to enable test signing or disable verification at all. I haven't tested it personally, but with signed drivers it should simplify the process a little. Might be worth a look, you know the full process so you could verify it easily.
41rw4lk said:
The reason driver signing verification is disabled on windows during a blankflash is so that the qualcomm drivers can be installed, the previous ones weren't signed. However, in the other xt1789-05 thread there is a link to signed drivers that are win 10 compatible, so you shouldn't need to enable test signing or disable verification at all. I haven't tested it personally, but with signed drivers it should simplify the process a little. Might be worth a look, you know the full process so you could verify it easily.
Click to expand...
Click to collapse
Thanks for this information. I may have missed that one with the signed drivers. I'm sure I had the ones from that thread. For some reason it just would not flash on both my laptop and desktop, I've used the blank flash on both desktop without being in test mode about 4 times and then all of a sudden it would not work. I'll have a go at reinstalling the drivers before I try next time.
Related
When I tried to install it, it failed and now when I try again it says
bad image
C;\windows
system32\wdcoinstaller01005.dll is either not designed to run windows or it contains an error. Try installing the program using the original installation media or contact your system administrator or the software vendor for support
you dont install anything. you extract the android sdk into the c:\. then you copy the two files mention in the thread to c:\windows\system32. you then go to start>run>cmd(enter). type adb devices. ADB is ALL COMMAND LINE. THERE IS NO PROGRAM YOU INSTALL
what two files?
blackfire1 said:
what two files?
Click to expand...
Click to collapse
~sigh~ are you sure you read how to do this at all?
adb.exe and AdbWinApi.dll are the two files that need to go to system32
and then install the drivers from your usb_driver folder from the SDK. Use the AMD one if you're using a 64bit OS or the Intel one for 32bit OS.
Okay but I get a problem at
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows-1.5_r2\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
I get a problem at this part when I click install drivers from my pc it pops up an error
bad image
C;\windows
system32\wdcoinstaller01005.dll is either not designed to run windows or it contains an error. Try installing the program using the original installation media or contact your system administrator or the software vendor for support
It worked before but I picked the amd one before because I didnt know which one to pick now it messed up my system and I cant do it again and it didnt work.
blackfire1 said:
Okay but I get a problem at
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows-1.5_r2\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
I get a problem at this part when I click install drivers from my pc it pops up an error
bad image
C;\windows
system32\wdcoinstaller01005.dll is either not designed to run windows or it contains an error. Try installing the program using the original installation media or contact your system administrator or the software vendor for support
It worked before but I picked the amd one before because I didnt know which one to pick now it messed up my system and I cant do it again and it didnt work.
Click to expand...
Click to collapse
System Restore and try it again.
that has nothing to do with adb. that means your driver installer that is resident in windows is corrupted. unless you can system restore to a point at which it was working, the only real fix is going to be a new windows install. not entirely sure how one breaks the library for installing device drivers, but hey, thats what you've got.
Ok the problem was solved when I used my other computer.
Hello XDA Community.
I'm attempting to install the new RC of CyanogenMod-6 for the Hero CDMA. I'm currently running the stock 2.1 version of Android. I've been following the guides that were referred to in the thread (I tried posting the urls but new users can't do so to prevent spam).
I've successfully rooted my phone and now I'm trying to do a Nandroid backup. I'm running Windows 7 32-bit and have hit a road block with ADB not recognizing my device. I followed the guide put together by Nephron to install the Android SDK. I've spent several hours going through threads and doing google searches looking for the solution. I have debugging turned on and I don't mount my SD drive when I plug the USB cord in. I've used USBDeview as some have suggested to delete current HTC drivers and then reinstall - no luck.
Here is a screen shot of what happens when I plug in my Hero:
See attached - "failedinstall.jpg"
Then I'll go to device manager to manually install the driver (it never allows me to manually select upon connection for some reason):
See attached "devicemgr.png"
And then this is the message I get when I point it to the "right" folder with the drivers:
See attached - "unabletoinstall.png"
So, on the Android SDK site I noticed this message:
"The USB driver for Windows provides support for the following Android-powered devices:
T-Mobile G1* / ADP1
T-Mobile myTouch 3G* / Google Ion
Verizon Droid*
Nexus One
* Or similar hardware on other carriers
Any additional devices will require Windows drivers provided by the hardware manufacturer.
^So is all of this HTC's fault? I've downloaded a couple of different .zip folders from different threads claiming that these drivers would work. But none of them have yet to do the trick for me.
I'm new at this so I have a few other questions as well:
Most guides I've read about how to do a Nandroid backup always recommend flashing a ROM b/f doing a backup. But I want to backup my current stock rom and settings before I flash. Wouldn't I want to create a recovery image before installing any other ROMs? Perhaps I'm misunderstanding some requirements?
Referring again to the thread on the CyanogenMod RC, can someone help me understand step #3? How do I know if it is necessary to update my radio? What implications does this have? I tried looking for info about this on the wiki and I couldn't find anything comprehensive enough to answer my question.
I'd appreciate any guidance!
Before you modify anything you will want to boot into recovery, assuming you flashed one, by holding down Home and turning the phone phone back on(power button). But since you don't have adb working then you probably haven't. You can still do this using terminal on your phone.
Download terminal emulator from market and then download a revoery image (AmonRa 1.6.2 or Darch's 1.7xx) and then mount your sdcard to the computer and transfer the recovery to the root of the sdcard. Open up terminal emulator and type in
Code:
su
cd /sdcard
flash_image recovery recovery-RA-heroc-v1.6.2.img(type the exact file name of the recovery you are using)
reboot recovery
If you had factory 2.1 on your phone then you have the latest radio. The radio can be flashed just like any ROM, but make sure that the radio is not for GSM phones as this will destroy your phone.
Instructions from Android Developers and ADB, Fastboot, and Nandroid for Noob
Download the latest Android SDK.
Unzip to C:\AndroidSDK
Right-click on (My) Computer, and select Properties
Go to Advanced settings
XP: Click the Advanced tab
Vista/7: Click Advanced system settings on the left
Click the Environment Variables button
double-click on Path (under System Variables)
Add the full path to the tools/ directory:
C:\AndroidSDK\tools\
(make sure a semicolon ( separates this new path from all the others)
Latest windows sdk version appears to need: "C:\AndroidSDK\android-sdk-windows\tools", install location may change with further updates..
Run C:\AndroidSDK\SDK Setup.exe
If you get an error about not having Java SDK installed but you do, add the path to 'bin' within your Java installation location to the Path environmental variable as described above before the sdk entry you just made. (eg add "C:\Program Files\Java\jdk1.6.0_20\bin;") This is likely to only be necessary where the 64 bit Java SDK is installed (obviously) on a 64 bit machine.
If it gives you an error about http go to settings and click on "Force http//....."
Unselect all options except for the USB driver
If you can't get the setup to work, download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows.
After it installs the drivers, goto the Start menu and type cmd into the search bar (Vista or higher) or click Run then type in cmd (XP) to open the command prompt.
Type the following into the command prompt window:
adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set. If you do NOT see a serial number, then we need to reinstall the drivers.
Download USBDeview
While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the HTC/Android drivers and uninstall them all. (Windows Vista requires program to be run as an administrator, otherwise files won't uninstall.)
Once all have been uninstalled, unplug the phone from the USB cable and plug it back in.
The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
To check, go to Devices in your Start menu then click on the “Android Phone”. Click on the Hardware tab, and check the list of drivers for ADB Interface under Type.
Done! Now you can use ADB to alter your phone from your computer.
If all else fails try installing HTC Sync software-- http://member.america.htc.com/download/Driver/HTC Hero (Sprint)/HTC_Sync_2.0.40.exe and then removing the drivers for it and then trying to install the android sdk drivers
Or you can dual boot with Linux and all you will need to do is download and unzip android sdk and edit 2 files and everything will work.
WOW>>>>>no that is way to confusing. the best thing to do is install vmware workstation. Then do a virtual WINDOWS XP MODE. from there you will be able to install the drivers and such in order to get the phone to be seen.
the version of htc sync i used for all my computers including win 7 was 2.0.33
if you want it then just pm me and I will get it to you
they don't offer it for a download anymore
this version corrected all my driver issues
This is a guide from a noob who spent a few hours today on my wifes phone trying to get it into Download mode after using Master Clear.....Worked fine before Master Clear but I wanted all the root apps IE Titanium) gone which the stock ROM update did not do. Being a total noob at Android and the Captivate being my first foray I though I would try to provide noob instructions to cover most bases. Most of the instructions here are scattered and not easy to find or are incomplete and make assumptions. This is specifically for those who cannot get into recovery or download mode.
Recovery/ Download modes are SEPARATE modes for for different uses.
I used recovery mode to "root' the phone AFTER putting the "update" file into the root directory using USB mass storage mode.
I use Download mode to install ROMS such as Stock and the 2.2 update.
My biggest issue was having a device that Would not GO INTO RECOVERY/DOWNLOAD MODE using any combination of button presses which it did before I Master cleared the phone. . Very frustrating. So I decided to bite the bullet and use the SDK mode. This first part will guide one on how to use the Android SDK and Command Prompt.
The assumption is all the drivers have been loaded for the Samsung Captivate.
First you need to have JAVA installed in your PC ( I did not)
The next you need to download the SDK package readily available
http://developer.android.com/sdk/index.html
This is what I did:
1. Created a folder called SDK on my C drive root directory.
2. Copied the android-sdk_r07-windows.zip SDK file to that directory
3. Extracted the ZIP into a newly created folder in that Directory
4. Deleted the Downloaded Zip package.
5. Moved all files from the new folder created by the extraction to the root SDK directory and deleted the now empty folder they came from. (This makes the path to the tools folder simple (as you will need to type that path out exactly in command Prompt)
My Path looked like this C:\SDK\Tools . Doesn't matter how you get there but tools folder must be in the path and the path must be exact
Next I started my Captivate normally and put my Captivate in USB debugging mode. Plugged in the USB.
I then opened the ODIN file I wanted to use whether original stock ROM or the new Froyo ROM
1. Opened command prompt on PC
2. Type CD\ to start at C root directory
3. from there I typed in CD \sdk\tools\
4. The next step involves the typing the command to open the screen you want the Phone to use...Recovery or download
4. Type in adb reboot recovery for the recovery screen (This gets you into the "three button screen" with no USB attached many cannot get into.
5. OR type in adb Reboot download to get the yellow download screen...
From there ODIN should indicate a com port..You hit start and the new ROM will be installed. There should be NO hangups on the indicated steps within ODIN. it happens pretty quickly.....YOu will see a filler bar at the top of ODIN and a blue line filler across the phone as the ROM is loaded.
I used Froyo..and discovered with Froyo I did not need to use the SDK method to get into recovery mode.....Froyo fixed that.
I have two Odin files. One for Jf6 Stock and the new 2.2.
I updated the JH7 FW using mini Kies in debugging mode. That was the only way I could load that FW which did not work OTA.
Bottomline is this is not a Hardware phone replacement issue if one cannot get into download mode. It is all about the FW in the phone. IF you can use the SDK you may likely not have to use it again.
OK ALL YOU EXPERTS Please correct or certify the steps.
Just trying to hep those who cannot read a 110 page thread that goes in many different directions.
Very nice instructions...
This type of detail is refreshing to see. Nice to see that assumptions aren't made. This type of detail can eliminate a lot of questions/posts.
I would just add - make sure you grab the right SDK - 1.5 ADB will not work with 2.1.
Thank You !
Followed your instructions but..
I tried to use sdk tools to reboot into download mode this is the specific comand I use:
adb reboot download
If I type this in the phone acts like i typed
adb reboot
The fact is that I searched help in the comand line and there is no reboot download only reboot recovery or reboot bootloader.
I cant get my kyocera torque into download mode and that is the problem I have also tried to boot with keys pressed nothing works. I want to get the phone to download mode so that I can install cwm recovery through odin
Maybe there is a esier way ?
U can make or buy a download mode jig. Quick search in the Captivate forums will show ya a thread of how to make one. Plus a lot of videos r on youtube as well.
Sent from my Nexus 5 using Tapatalk
In this guide I'm going to assume you know how to get SDK working. Here's the video if you don't: http://www.youtube.com/watch?v=oaNM-lt_aHw
This is in reference to Hascode's guide http://forum.xda-developers.com/showthread.php?t=2128175]
for steps 4.5 AND BEYOND or if you just want to enter Fastboot for yourself.
1. Download this: https://dl.dropbox.com/u/54456659/KFFirstAide64.zip (64 bit) OR https://dl.dropbox.com/u/54456659/KFFirstAide32.zip (32 bit)
Latest version of Java: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
Source: prokennexusa
2. Extract it to your C Drive (or primary), keep the folder name the same KFFirst AIDE (Do not change it)
3. Make a Path to that folder, as shown in the video. Instead you will put ;C:\KFFirstAide
4. Download Hashcode's files and place them in that FirstAide Folder.
5. Before going further, uninstall any previous drivers for the Kindle in Control Panel and Device Manager.
6. Install ADB Drivers found within KFFirstAide -> KindleADB
7. Open up RunMe.bat and run option 11 to verify ADB is working.
8. Now run option 15 to boot into Fastboot, it may take a min.
9. Once in Fastboot, open Device Manager and update the driver, browse to C: -> Program Files -> Amazon -> Drivers -> WinUSB
10. Open CMD and type in cd C:\KFFirstAide
11. Now type in Hashcode's Fastboot lines and it should run (you can verify this because the files pushed will also show up on your Kindle)
NOTE: It's important that you do not have any ADB or Kindle drivers installed prior to installing the one in the FirstAide folder (Check Device Manager)
If you have questions, post a comment down below and I will try to answer them.
Fixed Links. Working Now.
I need some help! I was using KFFristaide64 with my 8.9 KFHD. I was trying to flash to the 8.1.2, option 5, and it flashed the boot, recovery and system, them hung at deleting user data for about 2 hours. When it finally rebooted the kindle screen never comes on, and windows emits the beeps it uses to notify a usb device attachment and removal back to back to back, and the kindle never shows up in windows or ADB. I have tried to get into fastboot with option 15 and 16 using a standard and factory USB cable, but no combination will bring up fast boot, just get the cycling connection/disconnect sounds from windows. Does anyone know if there is a way to recover from this? I have a full back up (all 11 partitions) that I created just before starting. My device was rooted before I began, but I have no clue where in the process it would be now. Can anyone help, or should I just start looking for a new 8.9 KFHD?
Whenever I try to run step 6 of this, the installer tells me that it's failed and that I need to install the drivers manually. Doing that doesn't change anything, I still get the Kindle in the device manager with the exclamation point telling me that drivers have not been installed. I've removed everything from device manager/control panel before I run it.
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.