Related
Just got my G2x, and I'm excited to install one of the ROMs. I'm trying to install the ClockworkMod Recovery Flasher following the instructions in this tread http://forum.xda-developers.com/showthread.php?t=1056847 but "APX Device" isn't being detected. I have the LG driver installed on the computer. Can someone please help me out?
anjuice said:
Just got my G2x, and I'm excited to install one of the ROMs. I'm trying to install the ClockworkMod Recovery Flasher following the instructions in this tread http://forum.xda-developers.com/showthread.php?t=1056847 but "APX Device" isn't being detected. I have the LG driver installed on the computer. Can someone please help me out?
Click to expand...
Click to collapse
When trying to install the APX driver are you being sure to remove the phone battery, hold volume up+down together, and then plug the phone into the computer? You have to keep both volume buttons held down until the device is recognized. Then you go into device manager on your computer and right click on the APX device and update the driver software from there. Point the driver installation to the APX folder that was unzipped with the nvflash tool. The computer will find the appropriate driver and install it.
phburks said:
When trying to install the APX driver are you being sure to remove the phone battery, hold volume up+down together, and then plug the phone into the computer? You have to keep both volume buttons held down until the device is recognized. Then you go into device manager on your computer and right click on the APX device and update the driver software from there. Point the driver installation to the APX folder that was unzipped with the nvflash tool. The computer will find the appropriate driver and install it.
Click to expand...
Click to collapse
Ahhh, yeah.. Sadly the computer won't recognize it when I hold the volume up+down together and plug it into the computer. Battery is taken out before I attempt it. It's really weird . I was following the directions from the thread down to the T. Thanks a lot for the help!!
Does your computer recognize the phone when you plug it in with the power on? As in can you use usb storage or tethering? If so it should recognize it in apx.
Sent from my Nexus Prime using XDA Ultimate App
anjuice said:
Ahhh, yeah.. Sadly the computer won't recognize it when I hold the volume up+down together and plug it into the computer. Battery is taken out before I attempt it. It's really weird . I was following the directions from the thread down to the T. Thanks a lot for the help!!
Click to expand...
Click to collapse
I wonder if you try uninstalling all drivers for the phone (LG drivers and apx drivers) and install them fresh?
phburks said:
I wonder if you try uninstalling all drivers for the phone (LG drivers and apx drivers) and install them fresh?
Click to expand...
Click to collapse
It seems I haven't installed the APX driver. I do have the One-Click-G2x-recovery-flasher-06-16.rar, and inside is an APX folder with a bunch of .dll files. Are those what I'm supposed to use?
Alright it seems I was able to install the APX driver, thanks for all the help! It was odd... to put it in APX mode I left the battery in and held the power button plus the volume up and down buttons.. Weird.
anjuice said:
Alright it seems I was able to install the APX driver, thanks for all the help! It was odd... to put it in APX mode I left the battery in and held the power button plus the volume up and down buttons.. Weird.
Click to expand...
Click to collapse
Were you using a USB port on your computer or through a hub? You cannot use a hub to flash most phones. Because it worked with your battery it appears that the USB port you used is not supplying the required 5 volts, 500ma it is supposed to supply. Sounds like you were on an unpowered hub and it did not pass through power from the computer as it should.
jboxer said:
Were you using a USB port on your computer or through a hub? You cannot use a hub to flash most phones. Because it worked with your battery it appears that the USB port you used is not supplying the required 5 volts, 500ma it is supposed to supply. Sounds like you were on an unpowered hub and it did not pass through power from the computer as it should.
Click to expand...
Click to collapse
That's possible. I used the USB port that's installed in the front of my tower. Thanks for the explanation!
Virtualbox VM not recognizing phone
I'm using the VirtualBox VM method to flash clockworkmod recovery from this post: [RECOVERY] G2x ClockworkMod flash for Mac. I have completed steps 1-7 and everything seems to be in working order. However, once I pull the battery and hold down the volume up and volume down then plug in the USB. Nothing happens. The phone never turns on nor is recognized by Virtualbox VM. What am I doing wrong?
mylomine said:
I'm using the VirtualBox VM method to flash clockworkmod recovery from this post: [RECOVERY] G2x ClockworkMod flash for Mac. I have completed steps 1-7 and everything seems to be in working order. However, once I pull the battery and hold down the volume up and volume down then plug in the USB. Nothing happens. The phone never turns on nor is recognized by Virtualbox VM. What am I doing wrong?
Click to expand...
Click to collapse
The phone doesn't turn on. You will hear a beep that the phone tried to connect to the computer. Usually driver installation fails. You then go to the control panel, find the device under USB Devices and then direct Windows to manually install the driver from the APX directory. The screen on the phone doesn't show anything until AFTER a successful flash of the recovery (counter-intuitive but that is how it works). If you are using a VB VM setup, you need to make sure the USB ports are assigned to your virtual machine first.
USB Drivers are let your PC communicate with your device.
If you are executing some ADB Commands, you will need USB Drivers installed which will let the ADB server on your PC communicate with the ADB client on your device. If there are no USB Drivers installed on your PC, you will not be able to perform activities on your device via the PC.
First of All I would recommend you to install Universal ADB Driver Installer.The Universal ADB Driver installer detects your phone and installs the ADB drivers for it.This tool developed by drsmart is your solution to the “device not found” error you might get on executing ADB commands.
Universal ADB Driver Installer Download Link - http://adbdriver.com/downloads/
USB DRIVERS
1.SAMSUNG:
--- http://www.samsung.com/us/support/downloads
2.LG
---http://www.lg.com/us/support/mobile-support
3.HTC
---https://support.htc.com/en
4.SONY
---http://developer.sonymobile.com/downloads/drivers/
5.ASUS
---http://support.asus.com/download/options.aspx?SLanguage=en&type=1
6.MOTOROLA
---http://www.motorola.com/sites/motodev/us-en/motodev_lp.html
MORE DEVICES WILL BE UPDATED
Thanks for the info. I tried the univ adb driver installer but it showed I already had the right driver installed. Windows explorer can see my phone but other apps like HTC Sync or myphoneexplorer can't. This only happened after I rooted & installed a new rom. Maybe the rom is faulty...
I want Google nexus driver
any one can help me ?
mt6572 driver
Please add driver for mt6572 device
thx. very usefull!
thanks for the updated links.
Gole Maryam said:
I want Google nexus driver
any one can help me ?
Click to expand...
Click to collapse
an universal driver for all Nexus Devices (Phones and Tablets) can be found here:
http://forum.xda-developers.com/showthread.php?t=2513339
No access to USB debug
I give up and need some professional help...Ya both kinds.
Here we go, I have the Galaxy 3 d2att I747
Rooted
I was running CM 10.2 with latest nightly, I think 20131208 and decided to update to CM11 via my Cyanogenmod updater but before I did I had read somewhere I should change from CWM recovery to TWRP so I downloaded Goomanager and updated to the TWRP version for my phone then went for the KitKat update and thats when the trouble began.
I am now stuck in a boot loop even if I try to boot into TWRP all I get is the TWRP boot logo then straight into boot loop again. I am almost positive I did a factory wipe as well as cache/dalvik.
Not being able to use TWRP to get into recovery I thought I would just use Odin but I can't get any of my laptops to recognize the phones USB, I just get the windows usb driver error and have tried to install the drivers manually via device manager using my samsung 7 chronos with windows 8.1 and my acer with windows 7. I updated drivers using Samsung Kies and from the website, no luck.
I also ventured into an area that I have no expertise in but I guess thats how we learn so I downloaded the Android SDK thinking I could use it to download and install the google USB drivers that way, but I can't get out of boot loop to make sure USB debugging is checked. The only thing I can access is the stock download mode which would be great if I could use the USB connection.
What am I missing? Any suggestions?
USB Not Recognized Error
I noticed that my phone suddenly stopped being recognized on both my Windows 7 and Win8 laptops. I have been trying to fix it with the drivers but to no avail. However, I plugged my phone in with a different USB cord and voila it was recognized and working. Maybe this could possibly be a simple fix.
My computer stopped recognizing my Skyrocket
Hi Everyone,
I also am having trouble with my win 7 computer recognizing my Skyrocket suddenly. I have been using several KitKat roms and they have been working just fine, except for some reported bugs that the CM devs are working on. I even was able to connect to the computer and explore both my internal and external drives. Then suddenly that stopped and the computer gave me a need to get drivers warning. I've tried to download drivers from Samsung and the computer says they are already installed. I also tried the universal driver download and got the same message. Any help would be appreciated. Like the others on this forum, I wouldn't be able to odin if I got in trouble.
Thanks for your concideration,
drewfs7270
I switched to a different rom and now it's working again !
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Thanks.. :good: usefull
Also, any mobile manufacturer website has guides or direct downloads for drivers. Otherwise uni drivers suffice.....
Sent from my Nexus 5 using xda app-developers app
mtk preloader driver unable to install/unplugged appears
mt65xx unplugged when I try installing my device, I tried uninstalling all preloader vcom drivers in my laptop then restart and when I try to connect my device mtk mt65xx preloader just pops up in device manager then suddenly disappears and unknown device shows instead. I also tried manually update driver for unknown device then select the folder where my mtk driver is saved still unsuccessful? I've also searched and tried many other ways out there still no luck. Can anybody give me a solution? By the way i'm using windows 7 x64.
Delted
Edit: Deleted
soft brick
I face bad experienced, the tablet can not boot ( after install TWRP ) but enable to enter the fastboot mode and can be detected by the computer as android adb interface but adb can't communicated with the tablet. (list of devices atached)
I do have a backup file ( I make it before soft brick, I make backup using dd command, because I don't have cwm/twrp recovery ).... but how to flash it ? Tablet chipset is wonder media 8980 OS android 4.2.2
I can not flash it by adb/fastboot.
Maybe someone here can give me a little guide for how to....
I really appreciate for your kindness
Hey, I made an expirience, which might help other users as well.
I have a Sony device (Z1C) and use Windows 10, maybe this will help for other brands and for other Windows 10 users.
I installed drivers for my device and was able to use adb. When I put the phone into fastboot mode, it was not recognized anymore. I found out, Sony has a seperate (updated, maybe?) driver for fastboot mode. When I tried to install this, the driver was not signed and Windows refused to install it. However, you can enter the UEFI (successor of BIOS) and enable installation of unsigned drivers (at own risk). Then I was able to install the fastboot driver and controll my phone in fastboot mode as well as in adb mode.
In conclusion: You might think you installed drivers, because you did, but maybe you did not.
Even on LineageOS page, many people fail to mention that, you DON'T and SHOULDN'T install any generic or universal ADB driver if you have Samsung device. As you can just install Samsung USB Drivers officially from Samsung site. Samsung USB Drivers already contain ABD interface driver just fine so Universal ADB driver is redundant for Samsung phones.
Hi,
Have a TF101 tablet here stock rom, stock recovery...
However it seems the USB will not detect on a windows PC tried multiple cables multiple PC's tried from recovery nothing is detected in device manager at all. Tablet doesn't even detect that its connected to PC either.
Is there anyway to root this thing without USB??? I need to root it so I can install recovery and flash another rom.
Thanks,
Which Windows version are you running?
If you use Win 7 and prior you should be able to connect with the universal naked drivers manually installed from device manager
Win 8 and above need driver signing disabled or they wont install the driver and the PC wont see the TF
If you have already tried the above, you might need a new cable
http://forum.xda-developers.com/showthread.php?t=1688012
*Detection* said:
Which Windows version are you running?
If you use Win 7 and prior you should be able to connect with the universal naked drivers manually installed from device manager
Win 8 and above need driver signing disabled or they wont install the driver and the PC wont see the TF
If you have already tried the above, you might need a new cable
http://forum.xda-developers.com/showthread.php?t=1688012
Click to expand...
Click to collapse
Thanks. Well i tried windows 7 x64 and windows 8 x64, neither showed any device or unknown device in device manager... Tried multiple cables as wel, no dice...
Shouldn't MTP work regardless of drivers installed in windows 7/8 ?
Are you putting the TF into APX mode?
Connect TF to PC USB > Power Off TF > Hold Power & Volume Up until the PC recognises it (Only takes a couple seconds, nothing appears on the TF screen) then install drivers
You need APX mode for Easyflasher
For normal media transfer, it will still need to install at least some USB type driver, as do all USB devices to function, possibly not the APX drivers
Check in Developer Options > USB Debugging mode
Try it enabled and disabled with the TF plugged in
But really the MTP drivers are not what you need if you want to root. you need APX mode to work (As above)
*Detection* said:
Are you putting the TF into APX mode?
Connect TF to PC USB > Power Off TF > Hold Power & Volume Up until the PC recognises it (Only takes a couple seconds, nothing appears on the TF screen) then install drivers
You need APX mode for Easyflasher
For normal media transfer, it will still need to install at least some USB type driver, as do all USB devices to function, possibly not the APX drivers
Check in Developer Options > USB Debugging mode
Try it enabled and disabled with the TF plugged in
But really the MTP drivers are not what you need if you want to root. you need APX mode to work (As above)
Click to expand...
Click to collapse
Doesn't seem to do anything when I hold power vol+, the screen of the tablet (blank/off) and on the pc nothing is being detected.
I can get to the bootloader/recovery via holding power vol- though. Also tried USB debugging mode... nothing is detected whatsoever... ordering another cable on ebay will see if that works but I doubt it since it seems to be a common issue with this tablet (port not working with pc)
I edited my post
Nothing will appear on the TF screen in APX mode until data transfer begins
The cheap non genuine cables are renowned for data connection failing, genuine cables are recommended
I still have my original cable and it still works 100%
*Detection* said:
I edited my post
Nothing will appear on the TF screen in APX mode until data transfer begins
The cheap non genuine cables are renowned for data connection failing, genuine cables are recommended
I still have my original cable and it still works 100%
Click to expand...
Click to collapse
Using the original cable, I still can't tell if its in APX mode, installed all the drivers provided by asus, nothing is detected in windows device manager. I'm 100% its not being detected ie. no connection. I ran easyflasher anyway both sbk1 and sbk2 says it flashed recovery but it never did still the stock recovery is on the tablet.
Will try again once the new cable comes in, thanks.
Forget the ASUS drivers, use the Universal ones from the Easyflasher thread
Here's what will happen when its working as intended
When you plug the TF into the PC, no matter what mode it is in, the PC should sound the USB connect sound
When you power off the TF, then put it in APX mode, the PC will again sound the USB connect noise, then it will fail to install the correct drivers
That's when you open Device Manager, find the ! missing driver ! exclamation mark, and update drivers manually pointing it to the extracted Universal drivers
Once you have installed them, then Easyflasher should work as normal
So unless you actually have a hardware fault on the TF, or the USB ports of the PC, Id hedge my bets on the cable
Have you tried a different PC?
*Detection* said:
Forget the ASUS drivers, use the Universal ones from the Easyflasher thread
Here's what will happen when its working as intended
When you plug the TF into the PC, no matter what mode it is in, the PC should sound the USB connect sound
When you power off the TF, then put it in APX mode, the PC will again sound the USB connect noise, then it will fail to install the correct drivers
That's when you open Device Manager, find the ! missing driver ! exclamation mark, and update drivers manually pointing it to the extracted Universal drivers
Once you have installed them, then Easyflasher should work as normal
So unless you actually have a hardware fault on the TF, or the USB ports of the PC, Id hedge my bets on the cable
Have you tried a different PC?
Click to expand...
Click to collapse
Ok, well ya thats the thing no sound or detection of anything when plugging it in, or going into apx mode, rebooting etc...
I tried 2 cables and 2 different PCs. Will try a new cable but I betting that is won't work either... we'll see.
Thanks again
No need to bother with cables and drivers, just download Baidu Root: https://app.box.com/s/pyehf9fh4xem3hy50dot
EDIT: The app has built-in su access management, but I'd recommend installing SuperSU from the Play Store.
Duchman said:
No need to bother with cables and drivers, just download Baidu Root: https://app.box.com/s/pyehf9fh4xem3hy50dot
EDIT: The app has built-in su access management, but I'd recommend installing SuperSU from the Play Store.
Click to expand...
Click to collapse
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!! Worked to let me get TWRP installed and flashed a new rom with SU etc...
Thanks again!!!!!!!!!
Hi guys. I come here in search for help as I already tried possibly all the methods and unbrick solutions that I saw to fix my Oneplus One. Basically when I turn it on it gets stuck on "1+ powered by android" screen. I can't go to Recovery Mode and I can only enter the Fastboot mode if I'm not connected to PC. It doesn't get recognized when I connect it to PC unless I press the "Vol. up + Power" button combination. After this, it gets recognized on windows' device manager as "Qualcomm HS-USB QDLoader 9008" and the phone gets in a mode that doesn't show anything on the screen and apparently necessary to do what's described in this post. This was the last thing that I've tried after I tried several other solutions.
Thanks in advance to anyone who might help me. I love this phone and I hate just the thought of buying a new one.
Twody said:
Hi guys. I come here in search for help as I already tried possibly all the methods and unbrick solutions that I saw to fix my Oneplus One. Basically when I turn it on it gets stuck on "1+ powered by android" screen. I can't go to Recovery Mode and I can only enter the Fastboot mode if I'm not connected to PC. It doesn't get recognized when I connect it to PC unless I press the "Vol. up + Power" button combination. After this, it gets recognized on windows' device manager as "Qualcomm HS-USB QDLoader 9008" and the phone gets in a mode that doesn't show anything on the screen and apparently necessary to do what's described in this post. This was the last thing that I've tried after I tried several other solutions.
Thanks in advance to anyone who might help me. I love this phone and I hate just the thought of buying a new one.
Click to expand...
Click to collapse
Why not just enter into fastboot,install fastboot drivers in pc and connect device in fastboot mode to pc and flash cos13?
Mr.Ak said:
Why not just enter into fastboot,install fastboot drivers in pc and connect device in fastboot mode to pc and flash cos13?
Click to expand...
Click to collapse
I already intalled fastboot drivers and put the phone in fastboot mode. When I plug the phone to the PC it doesn't get recognized. Can you tell me how to install the fastboot drivers? Maybe I missed something.
Twody said:
I already intalled fastboot drivers and put the phone in fastboot mode. When I plug the phone to the PC it doesn't get recognized. Can you tell me how to install the fastboot drivers? Maybe I missed something.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2588979
Which windows you're using?
Mr.Ak said:
https://forum.xda-developers.com/showthread.php?t=2588979
Which windows you're using?
Click to expand...
Click to collapse
Yes, that was the one I installed. I'm using windows 10 x64.
Twody said:
Yes, that was the one I installed. I'm using windows 10 x64.
Click to expand...
Click to collapse
Try using win7.
PS: did you launched the tool with administrator privileges?
I download the latest adb and fastboot drivers from Android Studio site under command line tools.
Here is a good Article on how to configure the drivers on your machine.https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Need help. I was using Miracle Box to flash stock ROM, I don't know how but the phone (Micromax E453) is bricked now. I tried to start phone in Meta Mode (swiched off phone connected to PC by holding volume up button), it worked once, then following some tutorials I uninstalled (and checked, Delete the driver software for this device) MTK USB COM driver under port. Since then phone is not turning on and PC is not recognizing the device. Tired changing the USB cable and even tried it on another laptop, but no go. Kindly share what else I can try. PC has Windows 10 64 bit and MTK preloader vcom driver always has yellow exclamation mark (always installs with error code 10). I have disabled driver signature verificiation.
vnandwana said:
Need help. I was using Miracle Box to flash stock ROM, I don't know how but the phone (Micromax E453) is bricked now. I tried to start phone in Meta Mode (swiched off phone connected to PC by holding volume up button), it worked once, then following some tutorials I uninstalled (and checked, Delete the driver software for this device) MTK USB COM driver under port. Since then phone is not turning on and PC is not recognizing the device. Tired changing the USB cable and even tried it on another laptop, but no go. Kindly share what else I can try. PC has Windows 10 64 bit and MTK preloader vcom driver always has yellow exclamation mark (always installs with error code 10). I have disabled driver signature verificiation.
Click to expand...
Click to collapse
Did you have USB debugging enabled in the device's system settings before it got bricked? If not, you might not get it to connect via USB and be recognized.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Did you have USB debugging enabled in the device's system settings before it got bricked? If not, you might not get it to connect via USB and be recognized.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thank you for your response. Yes, USB debugging was enabled before it got bricked. I was able to successfully see my device when I ran adb -devices command. I was also able to run fastboot commands. Now its completely dead.