Related
Hello Everyone,
The AAHK guide says that Do NOT attempt to install earlier ENG HBOOTs on these models and also Do NOT attempt to downgrade a Inspire or DHD shipped with Gingerbread with a Froyo RUU.
Can anybody tell me what is a Froyou RUU and ENG HBOOTs so that I avoid doing these since my device was shipped with Gingerbread.
Guys please help me on another issue. I installed the Advanced Ace Hack Kit (AAHK) and installed the drivers. I run the file and it gives a error message that:
phone is not connected
or
driver not installed
or
USB Debugging not enabled
Please does anhyone know what seems to be the problem.
Husnain01 said:
Guys please help me on another issue. I installed the Advanced Ace Hack Kit (AAHK) and installed the drivers. I run the file and it gives a error message that:
phone is not connected
or
driver not installed
or
USB Debugging not enabled
Please does anhyone know what seems to be the problem.
Click to expand...
Click to collapse
So, have you made sure none of these three possibilities are true? If your phone is connected, make sure you enabled the USB debug. You can find it in Settings → Developer Options → Debugging. There should be a specific icon at the left part of your notification area after that.
How to fix this issue!
Husnain01 said:
Guys please help me on another issue. I installed the Advanced Ace Hack Kit (AAHK) and installed the drivers. I run the file and it gives a error message that:
phone is not connected
or
driver not installed
or
USB Debugging not enabled
Please does anhyone know what seems to be the problem.
Click to expand...
Click to collapse
I had the exact same problem, I didn't get connection to my DHD. I'm on Windows 8 btw. I resolved this issue by downloading HTC Sync from the HTC website, install it, right after install, remove the HTC Sync and the HTC Driver manager (or something like that). ONLY keep the original HTC drivers. try again, and everything worked like a charm after. (even though I was told it was never going to work with Windows 8 due to unsigned drivers. Well, I don't think so! ) Try it, good luck!
Husnain01 said:
Guys please help me on another issue. I installed the Advanced Ace Hack Kit (AAHK) and installed the drivers. I run the file and it gives a error message that:
phone is not connected
or
driver not installed
or
USB Debugging not enabled
Please does anhyone know what seems to be the problem.
Click to expand...
Click to collapse
Drivers HAVE TO BE installed with the phone unplugged. If you didn't do it like that, uninstall them from control panel and reinstall with the phone unplugged.
I recently broke my HOX+ and got a GNex for my replacement. Whenever I try to connect it, using another cable (Nexus 7) because its stock cable did not come with the phone (used) I get that pop up which says "Unable to recognize device" or sometimes an error. Though on all events, I get something called Error 43.
Anyone know how to fix this? Ive tried fixing to usb port. It is all stock. I just want to connect so I can root this thing.
Mikeonic said:
I recently broke my HOX+ and got a GNex for my replacement. Whenever I try to connect it, using another cable (Nexus 7) because its stock cable did not come with the phone (used) I get that pop up which says "Unable to recognize device" or sometimes an error. Though on all events, I get something called Error 43.
Anyone know how to fix this? Ive tried fixing to usb port. It is all stock. I just want to connect so I can root this thing.
Click to expand...
Click to collapse
Try installing samsung mtp drivers..
Sent from my Galaxy Nexus
Ive tried
mixtapes08 said:
Try installing samsung mtp drivers..
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I have tried installing drivers...still nothing..
I do assume you're using windows?
And my apologies, are you getting this error message when you try to root?
Were these the MTP drivers you installed?
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW
iLeopard said:
I do assume you're using windows?
And my apologies, are you getting this error message when you try to root?
Were these the MTP drivers you installed?
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW
Click to expand...
Click to collapse
Yes, Windows 7. Those were the ones and I want to root, but I can't even connect my phone. I'll plug in my GNex and it will charge through the computer though it will not be recognized nor connected for storage purposes.
Mikeonic said:
Yes, Windows 7. Those were the ones and I want to root, but I can't even connect my phone. I'll plug in my GNex and it will charge through the computer though it will not be recognized nor connected for storage purposes.
Click to expand...
Click to collapse
One thing you may want to try if you havent yet:
My Computer -> Right Click -> Properties -> Device Manager (On Sidebar) -> Find the GNex Drivers currently installed and remove them and reinstall (Re-plug) your phone so that the drivers can re-install.
Is this a used or new replacement?
iLeopard said:
One thing you may want to try if you havent yet:
My Computer -> Right Click -> Properties -> Device Manager (On Sidebar) -> Find the GNex Drivers currently installed and remove them and reinstall (Re-plug) your phone so that the drivers can re-install.
Is this a used or new replacement?
Click to expand...
Click to collapse
Unfortunately, the device appears as Unknown Device. It was my Uncles and it was able to work for him. So it bothers me how its not for me. At times even, when I connect the USB to the Device, it causes my Computer to Shut Down abnormally. So, either something is wrong and I need to fix it...or this phone is haunted,
Mikeonic said:
Unfortunately, the device appears as Unknown Device. It was my Uncles and it was able to work for him. So it bothers me how its not for me. At times even, when I connect the USB to the Device, it causes my Computer to Shut Down abnormally. So, either something is wrong and I need to fix it...or this phone is haunted,
Click to expand...
Click to collapse
Even after deleting it?
Did he by chance have it rooted prior to the ownership change?
Is the result replicated in other computers? If you haven't tried, do so. That way you can eliminate either your PC or the GNex as the culprit.
iLeopard said:
Even after deleting it?
Did he by chance have it rooted prior to the ownership change?
Is the result replicated in other computers? If you haven't tried, do so. That way you can eliminate either your PC or the GNex as the culprit.
Click to expand...
Click to collapse
He was stock at all times. Though when I got it, it seemed to be freshly restored...but 5 minutes into using the phone, it froze and gave a fixed screen of something being flashed...though even after I factory restored it again...It wont connect to my All in One PC, Desktop or Laptop, every other device I own connects properly .
Mikeonic said:
He was stock at all times. Though when I got it, it seemed to be freshly restored...but 5 minutes into using the phone, it froze and gave a fixed screen of something being flashed...though even after I factory restored it again...It wont connect to my All in One PC, Desktop or Laptop, every other device I own connects properly .
Click to expand...
Click to collapse
Wierd. Did you try a reset through the stock recovery or just defaults from the security menu?
Here's what I've done. I've pulled my drivers and compressed them. Update the "Unknown Device" from the Device Manager by pointing it to the extracted DLL's and see if that will work.
Drivers
iLeopard said:
Wierd. Did you try a reset through the stock recovery or just defaults from the security menu?
Here's what I've done. I've pulled my drivers and compressed them. Update the "Unknown Device" from the Device Manager by pointing it to the extracted DLL's and see if that will work.
Drivers
Click to expand...
Click to collapse
Been trying and it wont let me push those files and when I do, I get Code Error 10
Mikeonic said:
Been trying and it wont let me push those files and when I do, I get Code Error 10
Click to expand...
Click to collapse
Pushing them? Sorry for my poor explanation. Those files you downloaded are my working drivers that I managed to pull from:
C:\Windows\system32\DRIVERS\UMDF
C:\Windows\system32\DRIVERS\
C:\Windows\system32\
All you have to do is press START -> Type "Device Manager" -> Select the "Unknown Device" -> Press "Update Driver" -> "Browse my computer for driver software" -> Hit "Browse" and point to the folder were the DLL's are located in your computer (Once you have decompressed the archive of course)
iLeopard said:
Pushing them? Sorry for my poor explanation. Those files you downloaded are my working drivers that I managed to pull from:
C:\Windows\system32\DRIVERS\UMDF
C:\Windows\system32\DRIVERS\
C:\Windows\system32\
All you have to do is press START -> Type "Device Manager" -> Select the "Unknown Device" -> Press "Update Driver" -> "Browse my computer for driver software" -> Hit "Browse" and point to the folder were the DLL's are located in your computer (Once you have decompressed the archive of course)
Click to expand...
Click to collapse
It says there are no files in the folder...
UPDATE
It says it FOUND Drivers though cannot execute actions due to error 43
Mikeonic said:
UPDATE
It says it FOUND Drivers though cannot execute actions due to error 43
Click to expand...
Click to collapse
Honestly, I'm stumped. The drivers should have installed correctly regardless. This leads me to believe that its the GN acting up. Again, when you did a reset on it; Did you do it from the Security Submenu or from the Stock Recovery?
Is the device recognized under fastboot? ADB usually works fine there.
iLeopard said:
Honestly, I'm stumped. The drivers should have installed correctly regardless. This leads me to believe that its the GN acting up. Again, when you did a reset on it; Did you do it from the Security Submenu or from the Stock Recovery?
Is the device recognized under fastboot? ADB usually works fine there.
Click to expand...
Click to collapse
It was through the Settings SubMenu, I'll try a Fast boot
Mikeonic said:
It was through the Settings SubMenu, I'll try a Fast boot
Click to expand...
Click to collapse
Also try a factory reset via Stock Recovery. You should find it under the Fastboot menu
iLeopard said:
Also try a factory reset via Stock Recovery. You should find it under the Fastboot menu
Click to expand...
Click to collapse
Still nothing....this is hopeless
Mikeonic said:
Still nothing....this is hopeless
Click to expand...
Click to collapse
Wow, I'm truly amazed how nothing seemed to work. I don't think 1-Click Temp-Root Methods work on the GN, in which case you would use the terminal to Perm-Root it.
This happens on all computers?
Tried Different USB ports?
Rebooting PC?
iLeopard said:
Wow, I'm truly amazed how nothing seemed to work. I don't think 1-Click Temp-Root Methods work on the GN, in which case you would use the terminal to Perm-Root it.
This happens on all computers?
Tried Different USB ports?
Rebooting PC?
Click to expand...
Click to collapse
I will try getting a new USB, maybe a stock if I can find and see if that works. Wish I could root without a USB...Thank You for your help. I will update if anything.
i downloaded the software Ace Advance Hack Kit to root my HTC HD desire
I started rooting from the command prompt of my PC through the software
and used USB debugging option of my Android Phone.
It started rooting and in the meantime my mobile gets off and since then it is not opening and command prompt gives an error at that time "Error Device Offline"
harisazfar230 said:
i downloaded the software Ace Advance Hack Kit to root my HTC HD desire
I started rooting from the command prompt of my PC through the software
and used USB debugging option of my Android Phone.
It started rooting and in the meantime my mobile gets off and since then it is not opening and command prompt gives an error at that time "Error Device Offline"
Click to expand...
Click to collapse
Hack kit has been retired And so has been The support. Why are You using it?
Flash a Ruu And You will Get a working phone again
Since the early October update of Nougat's, my Pixel C is not being recognized, or plainly shows up as MTP device and I'm unable to transfer. When in fastboot And adb the PixC's model# Does register. Ive updated Everything incl. WugFresh, Skipsoft and sdks. Please help!
iamkardde said:
Since the early October update of Nougat's, my Pixel C is not being recognized, or plainly shows up as MTP device and I'm unable to transfer. When in fastboot And adb the PixC's model# Does register. Ive updated Everything incl. WugFresh, Skipsoft and sdks. Please help!
Click to expand...
Click to collapse
Update the drivers on your PC.
Thank you, though have done. Right after i saw reply i found DriverBooster4 and it "updated 13 drivers" but i guess not the right ones
iamkardde said:
Thank you, though have done. Right after i saw reply i found DriverBooster4 and it "updated 13 drivers" but i guess not the right ones
Click to expand...
Click to collapse
You need to do it manually. Google "how to manually update drivers windows 10". Do it via device manager with your Pixel C plugged in.
did do. And also before have tried to "point the update to" sdk and Wug's folders. Am not a total noob, but braincells do die, I cant stop it! If it matters, I did just few days ago clean-"re"install win10 64 but this problem was b4 that.. hence the clean start over. All Im ever getting is MTP USB Device, or wen tab's in fastboot, Android ADB Device. Both say "best is already installed".
also have done the "disable driver enforce", i do that routinely now til this is solved..
iamkardde said:
also have done the "disable driver enforce", i do that routinely now til this is solved..
Click to expand...
Click to collapse
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
with plugged in, debug on and mtp on, it showed as portable devices/mtp usb device. it did install successfully (again); reboot using f7 and... nothing, still the same
iamkardde said:
with plugged in, debug on and mtp on, it showed as portable devices/mtp usb device. it did install successfully (again); reboot using f7 and... nothing, still the same
Click to expand...
Click to collapse
it no longer shows as "unknown".
iamkardde said:
it no longer shows as "unknown".
Click to expand...
Click to collapse
I can b a bit dense, so in case i forget, Thank you for your help!! will probab say this again later..
Thanks to cam30era for the helping!! Problem was simply my misuse of TB. No mystery or MS/Google conspiracy. I went back to stock, re-rooted and Voila!
I'm trying to work out unlocking bootloader, but when I get to the point where device should be in fastboot mode, and on computer I write fastboot oem get_unlock_data command in cmd, it shows "waiting for any devices" and nothing happens. Tried writing fastboot devices, but it shows blank list.
USB drivers are PROBABLY installed with some bugs, I cannot install nor unistall them now idk why, during installation process it shows error "Parameter is incorrect" and then Motorola Driver Installation Utility shows up, which stays at half of the process of scanning drivers. When I choose the "clean only" option, Runtime error shows up at some point. Choosing update driver does nothing.
Any ideas what to do?
turn on your mobile and make this cmd.
adb devices
a window will open on your mobile, check the box and restart the unlocking of the mobile.
lohanbarth said:
turn on your mobile and make this cmd.
adb devices
a window will open on your mobile, check the box and restart the unlocking of the mobile.
Click to expand...
Click to collapse
Did it, checked the box. Nothing have changed, still "waiting for any device "
Sarid said:
Did it, checked the box. Nothing have changed, still "waiting for any device "
Click to expand...
Click to collapse
your debugging usb and enabled?
lohanbarth said:
your debugging usb and enabled?
Click to expand...
Click to collapse
Yes
Sarid said:
Yes
Click to expand...
Click to collapse
did you install the adb drivers?
lohanbarth said:
did you install the adb drivers?
Click to expand...
Click to collapse
Installing adb drivers helped, thank you very much