Hi there,
i want to unlock my phone and having root and update it also to the new update 4.0.2 ... but
The problem come from the start .... my phone is working fine and i can transfer data to my compute
but in the drives it say (The drivers for this device are not installed),
So my computer can't recognize it when i try to log in, when i'm in the Bootloader
and i try with most of the drives and it's not working and with the CD that is come with the phone
my computer in the windows 8
You probably need to disable driver signature here is a guide. https://www.google.co.uk/amp/www.ho...so-that-you-can-install-unsigned-drivers/amp/
Then install the driver package. :fingers-crossed:
LMcR92 said:
You probably need to disable driver signature here is a guide. https://www.google.co.uk/amp/www.ho...so-that-you-can-install-unsigned-drivers/amp/
Then install the driver package. :fingers-crossed:
Click to expand...
Click to collapse
true. i had the same problem once.
LMcR92 said:
You probably need to disable driver signature here is a guide. https://www.google.co.uk/amp/www.ho...so-that-you-can-install-unsigned-drivers/amp/
Then install the driver package. :fingers-crossed:
Click to expand...
Click to collapse
it's working know, after i disable the driver signature i try to install the CD again and it work this time.
So, thanks a lot guys for this help.
Related
i'm having trouble installing the USB driver for my s3 for tmobile. i get an error pop up on my phone saying that i need to install windows media 10 for the usb driver to work. is there any way to install the usb driver without installing windows media 10?
obla1 said:
i'm having trouble installing the USB driver for my s3 for tmobile. i get an error pop up on my phone saying that i need to install windows media 10 for the usb driver to work. is there any way to install the usb driver without installing windows media 10?
Click to expand...
Click to collapse
No thast not necessary. How are you installing the usb driver? If you look at thread below and go to step 1. There's a link in there for the usb driver. Its for Sprint and Tmo S3. Just run it and it should install automatically without needing any other software installed. I've done this with windows XP at work and my windows 7 at home.
http://forum.xda-developers.com/showthread.php?t=1726088
aznmode said:
No thast not necessary. How are you installing the usb driver? If you look at thread below and go to step 1. There's a link in there for the usb driver. Its for Sprint and Tmo S3. Just run it and it should install automatically without needing any other software installed. I've done this with windows XP at work and my windows 7 at home.
http://forum.xda-developers.com/showthread.php?t=1726088
Click to expand...
Click to collapse
ues i did install it. but then i get an error on the PC saying: "there was a problem installing this hardware.. MTP. An error occurred during installation of the device. A service installation section in this INF is invalid."
Is it really such a big deal to install it anyway and test if you can install your SGS3 drivers? You could always uninstall once you get the drivers working. Besides, it's only WMP10. Not like it's iTunes or Quicktime.
You need to have windows media player 11 or higher in order for your computer to recognize your phone. That's what worked for me.
Xanatos57 said:
Is it really such a big deal to install it anyway and test if you can install your SGS3 drivers? You could always uninstall once you get the drivers working. Besides, it's only WMP10. Not like it's iTunes or Quicktime.
Click to expand...
Click to collapse
i already installed WMP11 and i still get the same error.
scrued said:
You need to have windows media player 11 or higher in order for your computer to recognize your phone. That's what worked for me.
Click to expand...
Click to collapse
i already installed WMP11 and i still get the same error.
Have you tried installing the Snapdragon toolkit and installing the drivers through that program?
no need to open two threads,you will get help when people get around to it. this is not a tech support site,itsa development site.
Im unable to connect to usb while in recovery because I can't find the drivers. I've installed every drivers I could find and no go. I tried also switching ports and no matter what the driver isnt found and it prevents me from running scripts like the auto debloat because my device cannot be found. im running stock rooted Help!
Did you enable USB debugging?
tonymtl said:
Did you enable USB debugging?
Click to expand...
Click to collapse
Yeah
Why in recovery mode? You can run it booted to ROM.
tonymtl said:
Why in recovery mode? You can run it booted to ROM.
Click to expand...
Click to collapse
well the auto debloat i found needed to be used in cwm. While I would appreciate if you can point me to and alternate solution; I still need figure this out to avoid future mishaps.
I mean you should be booted to ROM with USB debugging on and run it, it will auto reboot to recovery.
tonymtl said:
I mean you should be booted to ROM with USB debugging on and run it, it will auto reboot to recovery.
Click to expand...
Click to collapse
ah gotcha. well I did but when i get to recovery my computer is asking for a driver that cant be found and i have no idea why. the script says that the "device is not found" and im pretty sure this is why. thanks for the help btw
Plug in your phone to PC, it will show locate drivers recommended, leave it.
In Windows go to control panel/system/device manager you'll see one with yellow "?" mark right click on it and update driver software>browse my computer for driver software >let me pick from list>pick Samsung android ADB interface. That should do it.
tonymtl said:
Plug in your phone to PC, it will show locate drivers recommended, leave it.
In Windows go to control panel/system/device manager you'll see one with yellow "?" mark right click on it and update driver software>browse my computer for driver software >let me pick from list>pick Samsung android ADB interface. That should do it.
Click to expand...
Click to collapse
you hit it on the nose. thanks man. now the next problem. all the apps were not found on the debloat script. smh. 1 down 1 to go. many thx
I believe that script was written for international gs3. You can download root browser and manually delete apps you don't like.
tonymtl said:
I believe that script was written for international gs3. You can download root browser and manually delete apps you don't like.
Click to expand...
Click to collapse
yeah i just read about it. what a bust. big help man.
Hello, I cannot get my computer to recognize my phone while in download mode, thus I cannot load a KDZ file to restore my soft bricked phone. I have the latest LG device drivers installed and have been able to transfer files before I bricked my phone (I accidentally wiped the OS in TWRP). Device manager states that there is a problem with the drivers. Is there anyway I can restore my phone? Thanks in advance
- Philip
basketballexplo said:
Hello, I cannot get my computer to recognize my phone while in download mode, thus I cannot load a KDZ file to restore my soft bricked phone. I have the latest LG device drivers installed and have been able to transfer files before I bricked my phone (I accidentally wiped the OS in TWRP). Device manager states that there is a problem with the drivers. Is there anyway I can restore my phone? Thanks in advance
- Philip
Click to expand...
Click to collapse
Reinstall the USB driver, Change USB Port
uppon2 said:
Reinstall the USB driver, Change USB Port
Click to expand...
Click to collapse
I have tried uninstalling the drivers many time and have also let Windows find the drivers itself but it says that the driver cannot be found.
basketballexplo said:
I have tried uninstalling the drivers many time and have also let Windows find the drivers itself but it says that the driver cannot be found.
Click to expand...
Click to collapse
Try a different USB cable and port. Have you got ADB installed? If so you should do a complete update of that too
uppon2 said:
Reinstall the USB driver, Change USB Port
Click to expand...
Click to collapse
uppon2 said:
Try a different USB cable and port. Have you got ADB installed? If so you should do a complete update of that too
Click to expand...
Click to collapse
Thanks for the help. but I finally got it to work by using a Windows 7 computer. I believe that there was something interfering with the drivers on my Windows 8 64 bit version.
basketballexplo said:
Thanks for the help. but I finally got it to work by using a Windows 7 computer. I believe that there was something interfering with the drivers on my Windows 8 64 bit version.
Click to expand...
Click to collapse
Glad to hear you have it working
Hi,
I try to flash my OP3.
I did first the UNLOCK, that worked with the CMD (Running Windows 10).
My device is Unlocked.
But when I wanna try fastboot flash recovery recovery.img
Or I type then it says waiting for device...
and when i typ: fastboot devices
then if gives nothing.
Yes, I did the OEM unlock in developers options en USB debugging is on.
HELP!
HELP!
Try manual boot into fastboot mode https://youtu.be/7ihDGm3EX_o and then reconnect.
peterk-1 said:
Try manual boot into fastboot mode https://youtu.be/7ihDGm3EX_o and then reconnect.
Click to expand...
Click to collapse
Yes, I did that.
But not working...
Over WiFi it's working, but not with USB.
Oke, ADB is working, but only when the device in ON.
When I does the device in Fastboot.
Than it doesn't work!
HELP!
Oke, I fix it.
Did it in an VM with Windows 7.
Bye.
YourTheBest said:
Oke, I fix it.
Did it in an VM with Windows 7.
Bye.
Click to expand...
Click to collapse
I'm also stuck with this, could briefly tell me how you set up a VM with window's 7 please? I tried with Ubuntu but no luck installing the adb and fastboot? Stuck with no recovery so please help
First Tick OEM unlock and enable usb debugging. And install latest driver
Ajshal said:
First Tick OEM unlock and enable usb debugging. And install latest driver
Click to expand...
Click to collapse
Way past that mate everything is installed, I need to get device to show in fastboot as it's currently not showing
How did you install the driver? do you have windows 8 or above?
daviss101 said:
Way past that mate everything is installed, I need to get device to show in fastboot as it's currently not showing
Click to expand...
Click to collapse
I have same pblm on my LG K10 dude
therightperson_630 said:
How did you install the driver? do you have windows 8 or above?
Click to expand...
Click to collapse
At first it it was called Marshall London bootloader interface but after clicking automatic driver update it then showed as "kedacom bootloader" it does show its in adb mode thou. Is there any Google/Samsung drivers you could link me?
Edit- windows 10
daviss101 said:
At first it it was called Marshall London bootloader interface but after clicking automatic driver update it then showed as "kedacom bootloader" it does show its in adb mode thou. Is there any Google/Samsung drivers you could link me?
Edit- windows 10
Click to expand...
Click to collapse
Ok, not sure if you know about this, but you'll have to install the drivers with signed driver enforcement turned off in windows 10:
Setting > update & security > recovery tab > Advanced start-up (restart now).
On boot up you'll use the function keys to turn off "signed driver enforcement" or something similar.
Then try and install adb/fastboot from this http://forum.xda-developers.com/showthread.php?t=2317790
It should come up with an extra security window during the installation - the driver will be properly installed and you'll be able to use fastboot on your OP3
therightperson_630 said:
Ok, not sure if you know about this, but you'll have to install the drivers with signed driver enforcement turned off in windows 10:
Setting > update & security > recovery tab > Advanced start-up (restart now).
On boot up you'll use the function keys to turn off "signed driver enforcement" or something similar.
Then try and install adb/fastboot from this http://forum.xda-developers.com/showthread.php?t=2317790
It should come up with an extra security window during the installation - the driver will be properly installed and you'll be able to use fastboot on your OP3
Click to expand...
Click to collapse
Okay thanks, I have tried that step but that's when it changed to kedacom via automatic update. I'm confused here I downloaded official oneplus drivers and installed and my phone is perfectly recognised as A300 when its file transfer but when you say install drivers which ones can I download to install manually to remove kedacom? Thanks your time to help but I'm completely stuck
daviss101 said:
Okay thanks, I have tried that step but that's when it changed to kedacom via automatic update. I'm confused here I downloaded official oneplus drivers and installed and my phone is perfectly recognised as A300 when its file transfer but when you say install drivers which ones can I download to install manually to remove kedacom? Thanks your time to help but I'm completely stuck
Click to expand...
Click to collapse
go to device manager and manually uninstall kedacom driver and install minimal adb/fastboot from the link I posted, they'll install the driver automatically
daviss101 said:
Way past that mate everything is installed, I need to get device to show in fastboot as it's currently not showing
Click to expand...
Click to collapse
Just install an FRESH Windows 7.
Install ADB Drivers
Install OP3 drivers
And than open CMD an enter the commands.
YourTheBest said:
Just install an FRESH Windows 7.
Install ADB Drivers
Install OP3 drivers
And than open CMD an enter the commands.
Click to expand...
Click to collapse
How do I get a free version of windows 7 without downloading a cracked ISO?
My ADB works fine but not getting a fastboot devices detect for TWRP fastboot.
I also see driver missing in device manager on Win11 but none of various versions of Google ADB, Xiaomi, etc drivers I have tried seem to match the hardware it thinks its detecting
It did work prior with stock recovery fastboot.
Prior there was some Win 11 driver signing issue for fastboot drivers.. But I have Shift rebooted and disabled driver signature enforcement, which was what worked last time, but its not helping with TWRP.
Anything obvious to suggest here ??
Poco F3 with TWRP cant detect fastboot.
windows 11 is still on its embryonic stage expect some bugs and compatibility issue, try reinstalling all drivers of your poco f3 but before that, you need to disable driver signature enforcement before reinstalling drivers search on google on how to disable this matter
I have done that though.. Rebooted with driver signature turned off (thats what worked last time) and added / removed phone.. rebooted phone.. Tried manually reinstalling same drivers, new drivers, searching for drivers, etc..
Can TWRP need any different driver pairing than the stock recovery drivers ??
Worked straight away when stock.
Phat Phreddy said:
I have done that though.. Rebooted with driver signature turned off (thats what worked last time) and added / removed phone.. rebooted phone.. Tried manually reinstalling same drivers, new drivers, searching for drivers, etc..
Can TWRP need any different driver pairing than the stock recovery drivers ??
Worked straight away when stock.
Click to expand...
Click to collapse
i am currently running on win 10, nebrassy and vasishath twrp build no issue about fastboot, maybe you should try to downgrade your pc
Phat Phreddy said:
I have done that though.. Rebooted with driver signature turned off (thats what worked last time) and added / removed phone.. rebooted phone.. Tried manually reinstalling same drivers, new drivers, searching for drivers, etc..
Can TWRP need any different driver pairing than the stock recovery drivers ??
Worked straight away when stock.
Click to expand...
Click to collapse
if it worked on stock have you maybe forgoten to enable usb debugging again? lol
Phat Phreddy said:
My ADB works fine but not getting a fastboot devices detect for TWRP fastboot.
I also see driver missing in device manager on Win11 but none of various versions of Google ADB, Xiaomi, etc drivers I have tried seem to match the hardware it thinks its detecting
It did work prior with stock recovery fastboot.
Prior there was some Win 11 driver signing issue for fastboot drivers.. But I have Shift rebooted and disabled driver signature enforcement, which was what worked last time, but its not helping with TWRP.
Anything obvious to suggest here ??
Poco F3 with TWRP cant detect fastboot.
Click to expand...
Click to collapse
Have you tried to install the drivers present on the miflash program with the Windows driver signature disabled? If that doesn't work either, I think the problem is your win 11. I tried win 11 last month and with those drivers and sdk platform tools the phone was well recognized in fastboot
mlcattini said:
if it worked on stock have you maybe forgoten to enable usb debugging again? lol
Click to expand...
Click to collapse
But I said its working on ADB..
RollDload said:
Have you tried to install the drivers present on the miflash program with the Windows driver signature disabled? If that doesn't work either, I think the problem is your win 11. I tried win 11 last month and with those drivers and sdk platform tools the phone was well recognized in fastboot
Click to expand...
Click to collapse
Will give this a go..
Can I 'update driver' and point it at the file folder or does this need re-installing the miflash app ?
Phat Phreddy said:
Will give this a go..
Can I 'update driver' and point it at the file folder or does this need re-installing the miflash app ?
Click to expand...
Click to collapse
you could try, however miflash doesn't need installation you just need to unzip it. you can also try to change USB port better if rear and 2.0
Strange I thought I replied in here this morning..
Anyway.. Got it going.. Disabled driver checking.. Then forced 'from disk' and manually pushed it to use the xiaomi drivers.. It wouldnt auto detect or even find the drivers when pointed at the disk, btu the prior install version worked and now both adb and fastboot working even when booted with driver checking on.
Phat Phreddy said:
Strange I thought I replied in here this morning..
Anyway.. Got it going.. Disabled driver checking.. Then forced 'from disk' and manually pushed it to use the xiaomi drivers.. It wouldnt auto detect or even find the drivers when pointed at the disk, btu the prior install version worked and now both adb and fastboot working even when booted with driver checking on.
Click to expand...
Click to collapse
then it was definitely a problem in the driver.