Dears,
Can you please anyone share the windows 7 ADB drivers?
Regards
androidgalaxyman
Get PDA net adb drivers work on all windows. Tested on win 10 developer preview alaoy.
Sent from my AO5510 using XDA Premium 4 mobile app
Thanks
Siddhesh.K15 said:
Get PDA net adb drivers work on all windows. Tested on win 10 developer preview alaoy.
Sent from my AO5510 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks
androidgalaxyman said:
Dears,
Can you please anyone share the windows 7 ADB drivers?
Regards
androidgalaxyman
Click to expand...
Click to collapse
I got mine working with this on windows 8.1. Try just in case.
http://www.koushikdutta.com/post/universal-adb-driver.
PRRash said:
I got mine working with this on windows 8.1. Try just in case.
http://www.koushikdutta.com/post/universal-adb-driver.
Click to expand...
Click to collapse
It wasn't working in Windows 7
The instructions are incomplete so there will be no rooting unless you install proper micromax drivers for adb . Looks like the instructions were emailed and posted by someone else. Disabling driver signature enforcement is also not helpful .Tried it on 4 different systems and a fresh vm with x86,x64 win7 & win8 . drivers from koushik also does not work
Drivers plz
Did anyone found the drivers for YU yureka? Plz upload if u have.. My system detects the mobile when it is switched on but when I enter bootloader the system doesn't detect it..
darshan.devadiga said:
Did anyone found the drivers for YU yureka? Plz upload if u have.. My system detects the mobile when it is switched on but when I enter bootloader the system doesn't detect it..
Click to expand...
Click to collapse
Metoo adb works fine but not fastboot:banghead:
Hey.. I finally got the fix.. Download all in one toolbox for yureka and then try in that.. Worked for me.. Hit thanks if it works
Install Universaladb driver setup
Handset still wontget recognized
Goto device manager and set custom driver for exclamation mark to "android composite interface" confirm the android debugging popup with mac , now boot to adb reboot-bootloader
Again browse the exlamation mark android to "android composite interface" and push in the fastboot command
adb reboot-bootloader
YU will now be in fastboot mode.
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf flash recovery recovery-yu.img
fastboot -i 0x1ebf reboot
boot into newly installed recovery.
adb reboot recovery
Hey
androidgalaxyman said:
Dears,
Can you please anyone share the windows 7 ADB drivers?
Regards
androidgalaxyman
Click to expand...
Click to collapse
Hey dude, i'm using windows 7 Ultimate as well and the adb/fastboot do not work for my yureka. Were you successful in finding the proper drivers?
asim.sidz said:
Hey dude, i'm using windows 7 Ultimate as well and the adb/fastboot do not work for my yureka. Were you successful in finding the proper drivers?
Click to expand...
Click to collapse
I request all the Yureka owers to raise a voice and join the campaign !
[PROJECT] Reviving Hard Bricked YU (QLoader 9008 Mode) at YUPLAYGOD.COM
Related
after i flashed the aospa 4.4 i lost custom recovery and my pc wont recognize my ohone , ive tried wugs toolkits and installed drivers but it still wont recognize the freaking phone lol
costarican said:
after i flashed the aospa 4.4 i lost custom recovery and my pc wont recognize my ohone , ive tried wugs toolkits and installed drivers but it still wont recognize the freaking phone lol
Click to expand...
Click to collapse
Do this.
download the exe file of fastboot and then goto to bootloader where it shows all thedetails of your phone and the in Pc
open cmd and type fastboot flash recovery recovery.img and enter
you should have a .img file of the recovery.
All done. :good:
my 4.4 is revognized in mtp so its not 4.4,install universal naked drivers. :good
:
Rohit02 said:
Do this.
download the exe file of fastboot and then goto to bootloader where it shows all thedetails of your phone and the in Pc
open cmd and type fastboot flash recovery recovery.img and enter
you should have a .img file of the recovery.
All done. :good:
my 4.4 is revognized in mtp so its not 4.4,install universal naked drivers. :good
:
Click to expand...
Click to collapse
can you link me up please ive been trying for days :/ or pm me please
cmd says fastboot is not recognized as an internal or external command
neither tpt or adb work , the phone only charges thorugh usb
costarican said:
can you link me up please ive been trying for days :/ or pm me please
Click to expand...
Click to collapse
I had the same problem just install the wugfresh tool from development and reinstall the drivers then make sure you have adb on in developers option and when you connect make sure you are connected ptp the picture mode one and then it will recognize it.
Sent from my Nexus 4 using xda app-developers app
dntipwn said:
I had the same problem just install the wugfresh tool from development and reinstall the drivers then make sure you have adb on in developers option and when you connect make sure you are connected ptp the picture mode one and then it will recognize it.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I've tried in different PCs and it won't even recognize picture mode
Sent from my AOSP on Mako using Tapatalk 2
dntipwn said:
I had the same problem just install the wugfresh tool from development and reinstall the drivers then make sure you have adb on in developers option and when you connect make sure you are connected ptp the picture mode one and then it will recognize it.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
All I need is to get it to recognize to fastboot to install the recovery
Sent from my AOSP on Mako using Tapatalk 2
costarican said:
All I need is to get it to recognize to fastboot to install the recovery
Sent from my AOSP on Mako using Tapatalk 2
Click to expand...
Click to collapse
Make sure usb debugging is on.
then install universal naked drivers and then see if your phone is recognized and then install the exe file of fastboot and on cmd prompt in pc follow theinstructions. Profit.
N4 16Gb : Loliop 5.02, SimpleAOSPv11, AK Kernel, CWM Philz Touch 6.46.3
I foolishly ran "Clean to install new ROM" from Philz recovery (under "Factory Reset").
I don't have a ROM on the device to flash, and can't see the device over USB or ADB.
Can anyone help recover this please? Thanks
fr0d0#2 said:
N4 16Gb : Loliop 5.02, SimpleAOSPv11, AK Kernel, CWM Philz Touch 6.46.3
I foolishly ran "Clean to install new ROM" from Philz recovery (under "Factory Reset").
I don't have a ROM on the device to flash, and can't see the device over USB or ADB.
Can anyone help recover this please? Thanks
Click to expand...
Click to collapse
First off, you're not bricked. When you boot into recovery and your device connected to your pc what do you get when you run the command adb devices from a Windows command window?
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
First off, you're not bricked. When you boot into recovery and your device connected to your pc what do you get when you run the command adb devices from a Windows command window?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks jd
I don't get anything no matter which mode I boot into
fr0d0#2 said:
Thanks jd
I don't get anything no matter which mode I boot into
Click to expand...
Click to collapse
Are you on a Windows pc? Do you have adb and fastboot setup on the pc? Had the pc recognize the device in the past?
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Are you on a Windows pc? Do you have adb and fastboot setup on the pc? Had the pc recognize the device in the past?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Windows 8 with adb installed that has previously seen the N4, yes.
I've had an HTC M8 connected recently. Just now, before wiping, I was connected via USB.
fr0d0#2 said:
Windows 8 with adb installed that has previously seen the N4, yes.
I've had an HTC M8 connected recently. Just now, before wiping, I was connected via USB.
Click to expand...
Click to collapse
Ok, so it doesn't seem like a driver or software issue. With your device booted into recovery and connected to the pc what do you see the device in device manager? It should show up as an android adb composite interface, or something like that.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Ok, so it doesn't seem like a driver or software issue. With your device booted into recovery and connected to the pc what do you see the device in device manager? It should show up as an android adb composite interface, or something like that.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I have an exclamation mark next to N4
Driver re-installed - now recognised as Android Composite ADB Device
fr0d0#2 said:
Driver re-installed - now recognised as Android Composite ADB Device
Click to expand...
Click to collapse
Good, download a rom.zip to your pc if you don't already have one. Then you're going to want to boot into recovery and push the zip to your device using adb. Once there you'll be able to flash it in philz
adb push rom.zip /sdcard/Download. I might have the / backwards. I always forget which way they go. For rom.zip use the full name of the rom. You'll want to have the rom.zip in the same folder as adb.exe and open your command window in that folder too.
Sent from my Nexus 9 using XDA Free mobile app
Thanks jd
You had the slashes the right way around - back in a bit
I'm still not getting the device listed at the command prompt, and get an error saying the same when I try the push command.
WUGs toolkit says it's there and in fastboot mode, and says it's pushed the file successfully but there's nothing there.
fr0d0#2 said:
I'm still not getting the device listed at the command prompt, and get an error saying the same when I try the push command.
WUGs toolkit says it's there and in fastboot mode, and says it's pushed the file successfully but there's nothing there.
Click to expand...
Click to collapse
I'm not that familiar with philz. Does it have an option to enable mtp when you're booted into it? If it did you can copy and paste the rom from your pc to the device. Twrp has that option under mount. I may have you boot into twrp with fastboot to use that option. How familiar are you with fastboot?
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I'm not that familiar with philz. Does it have an option to enable mtp when you're booted into it? If it did you can copy and paste the rom from your pc to the device. Twrp has that option under mount. I may have you boot into twrp with fastboot to use that option. How familiar are you with fastboot?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Not that I can find JD. There are several mount options but USB doesn't work... because it's looking for an external source I presume.
Not very familiar.
fr0d0#2 said:
Not that I can find JD. There are several mount options but USB doesn't work... because it's looking for an external source I presume.
Not very familiar.
Click to expand...
Click to collapse
Well,a good time to learn. Download the latest twrp image from here http://techerrata.com/browse/twrp2/mako. Rename it recovery for simplicity. I'm going to have you re-install fastboot from, Google 15 second adb install xda. That'll simplify the path issues using fastboot and adb, it sets an environment variable so you don't have to worry about the path to adb or fastboot.
Then open a command window in the same folder as the twrp image is in. With your device booted into the bootloader and connected to your pc run the command
fastboot boot recovery.img.
That'll boot you into the twrp recovery. Go to mount and in the lower right hand corner you should see and option to mount mtp. Then you should see your device in Windows just like you normally would. That should make it easy to copy and paste the rom.zip to your device. Once it's copied just install it using twrp. You shouldn't have to reboot or anything.
Sent from my Nexus 9 using XDA Free mobile app
Thank you so much JD
twrp installed and mtp enabled - plain sailing from there on.
I owe you a pint :good: :highfive:
fr0d0#2 said:
Thank you so much JD
twrp installed and mtp enabled - plain sailing from there on.
I owe you a pint :good: :highfive:
Click to expand...
Click to collapse
Glad you got it working
Sent from my Nexus 9 using XDA Free mobile app
For future reference a USB otg cord and pen drive would of been very easy and cheap glad you got it fixed!!
Sent from my LG-VS985 using XDA Free mobile app
hello every one plyze i need help every time i trying to root my ze500kl it said only waitting for device and do nothing
Mohamed elkholy said:
hello every one plyze i need help every time i trying to root my ze500kl it said only waitting for device and do nothing
Click to expand...
Click to collapse
It's probably a problem with drivers. It's common in Windows. Search in the forum for these keywords: ADB Windows driver problems
I resolved using a Linux distro (Debian Sid, but Ubuntu is OK and more friendly too), no problems with drivers anymore.
but when i type adb device i found my device but when
he enter to the fastboot mode it said waiting for device
do you can help me please how do you have fixed it
mohamedelkholy said:
but when i type adb device i found my device but when
he enter to the fastboot mode it said waiting for device
do you can help me please how do you have fixed it
Click to expand...
Click to collapse
Do you run the command prompt as Administrator (right clic on the Command Prompt icon > Run as Administrator)?
Do you run fastboot devices before to check if the phone is recognized by fastboot?
i have run the cmd as an admiristratore but how to reconized it
mohamedelkholy said:
i have run the cmd as an admiristratore but how to reconized it
Click to expand...
Click to collapse
with the command:
Code:
fastboot devices
if the phone is recognized, it should respond with
Code:
random123 fastboot
if nothing happens, you have to check your adb drivers (uninstall and reinstall for example).
My redmi 3s prime is not detected by command prompt, in Fastboot mode. Any solution
Ushubh Singh said:
My redmi 3s prime is not detected by command prompt, in Fastboot mode. Any solution
Click to expand...
Click to collapse
Install proper drivers and check. Always open command prompt in adb folder for successful recognition of fastboot devices.
william.johhn7! said:
Install proper drivers and check. Always open command prompt in adb folder for successful recognition of fastboot devices.
Click to expand...
Click to collapse
Ya I try all ways but still not recognized
Ushubh Singh said:
Ya I try all ways but still not recognized
Click to expand...
Click to collapse
Try Asus drivers. They're basically universal. Make sure you install adb files.
william.johhn7! said:
Try Asus drivers. They're basically universal. Make sure you install adb files.
Click to expand...
Click to collapse
Kk, can u send me Asus driver link. If possible
Ushubh Singh said:
Kk, can u send me Asus driver link. If possible
Click to expand...
Click to collapse
Sorry. I don't remember from where I downloaded it. You could give it a try by googling it.
william.johhn7! said:
Sorry. I don't remember from where I downloaded it. You could give it a try by googling it.
Click to expand...
Click to collapse
Kk thnx... Bro
Step 1:-
Open CMD and type fastboot if it says not a internal/external command then u need to flash drivers. If many texts appears like fastboot commands etc then follow next step
Step 2:-
Connect your phone in fastboot to your computer
Right click my pc go to device manager then you can see Android with (!) Mark then double click update drivers choose manually then again set to android:> Android bootloader interface and done
Hello Everyone,
I would like to install fastboot ROM on Redmi Note 7 and my PC cannot recognized it on fastboot mode. I almost tried everything like intall 5sec fastboot driver and latest fastbott drivers but it didn't work. I sincerely ask you guys how can I solve it.
Thank you so much
saonaylinn said:
Hello Everyone,
I would like to install fastboot ROM on Redmi Note 7 and my PC cannot recognized it on fastboot mode. I almost tried everything like intall 5sec fastboot driver and latest fastbott drivers but it didn't work. I sincerely ask you guys how can I solve it.
Thank you so much
Click to expand...
Click to collapse
Install Miflash +drivers.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
and/or
https://avalonsciences.com/wp-conte...Signature-Verification-on-Windows-8-or-10.pdf
I recently started having trouble sideloading updates through ADB. I was using Win 11, PowerShell and had Bitdefender installed as anti-virus. However, I had no problem on a Win 10 machines using the same programs.
To fix it on my primary Win 11 machine, I disconnected from internet after my download of the OTA, killed BitDefender, and used a Command window instead of PowerShell. That worked for me.
Granted fastboot is different than ADB, but it could be the same problem. Also make sure your Platform Tools is up to date.