Related
Hi Guys!!!
Recently I had A problem Installing Windows 32 bit Driver For Android So i searched On the web for this error & Found that there were many people with this error...
Here Is the info about that Error In My Last Post: http://forum.xda-developers.com/showthread.php?t=493604
WINDOWS XP x86 / 32-Bit Only
The error was so:
When we download the android_usb_windows.zip then extract it and then try to install it via device manager all goes right it detects the driver but at the last step where it asks for androidusb.sys file and when given the path it waits some time and says Fatal Error...
SO I tried To Go deep in the system32 folder There Go into Drivers Folder Now Here You begin some stuff:
1. Go in "C:\WINDOWS\system32\drivers" Folder there Find These files and cut them and paste in some folder where its safe:
androidusb.sys
usbccgp.sys
usbstor.sys
wdf01000.sys !!!! (Be Careful Deleting this File, I Say First try Without Deleting this file !)
2. Now Go to device manager "Right-click My Computer -> Manager -> Device Manager"
3. Click On ADB Interference Or something like that U ll Get a sub-category Right-click on it Click Uninstall -> OK
Do The Same For the Following :
USB Composite Device
USB Mass Storage Device
4. Get The Drivers From Here If U already Don't Have: http://dl.google.com/android/android-sdk-windows-1.0_r2.zip
OR
Get The Haykuro's Updated USB Drivers from here : http://sapphire-port-dream.googlecode.com/files/usb_driver_updated.zip
5. Now Try To Install The Driver Again By Going to "Right-click My Computer -> Manager -> Device Manager -> Action -> Scan for Hardware Changes" Then You will Get a pop-up saying Found New Hardware...
6. Install the drivers As Usual..... It Will install The Drivers Succesfully....
You Are Done.....
All I can say is THANK YOU.
THANK YOU THANK YOU THANK YOU.
This post deserves a sticky..
you are great
LOL
-- well after this I couldn't use FASTBOOT anymore hahahahaha
well, I worked around that, had to reinstall drivers for Haykuro's SPL too. So now both ADB and FASTBOOT work.
Thanks helped with my Win NT at work. lol
lol i have no idea if this was the cause... after this, I was no longer able to use my laptops keyboard, mice, video card drivers were corrupted along with network drivers, processor bus communications driver and a whole lot more. I had to perform a full system recovery so... yay.. lost everything, but im working on it.
---EDIT, I performed this on my fully recovered system again, and had the same results after it rebooted. I was able to conlude that it was caused by the system file with the wdf in it. Luckily, I hadn't deleted it and simply moved it into the recylcing bin and was able to recover from it. This may just be specific to my system, but I'm not sure. Just a warning to back everything up.
SolemnWishing said:
lol i have no idea if this was the cause... after this, I was no longer able to use my laptops keyboard, mice, video card drivers were corrupted along with network drivers, processor bus communications driver and a whole lot more. I had to perform a full system recovery so... yay.. lost everything, but im working on it.
---EDIT, I performed this on my fully recovered system again, and had the same results after it rebooted. I was able to conlude that it was caused by the system file with the wdf in it. Luckily, I hadn't deleted it and simply moved it into the recylcing bin and was able to recover from it. This may just be specific to my system, but I'm not sure. Just a warning to back everything up.
Click to expand...
Click to collapse
So Is that you are sayin is we do not need to remove the wdf file, did the drivers work without removing & again installing that wdf file?
or u did not put the new file again before rebooting ?
I am not really sure. It can possibly just be my computer. Once removing all the drivers you listed, the ADB then successfully worked, and continued to work as long as the computer was not rebooted. Once rebooted, I drivers for many pieces of hardware became corrupt and unreadable. By simply replacing the wdf driver and rebooting, it fixed the issue. So, I really am not sure. My computer... is strange. I believe it likely could just be my computer thats all.
next time if u get such problem just try solving without removing the wdf file & post what happens...
& plz post the consequences....thanks
The key points are:
To choose ADB interface\HTC Dream Composite ADB Interface to install
--DIYism
sangeet.003 said:
next time if u get such problem just try solving without removing the wdf file & post what happens...
& plz post the consequences....thanks
Click to expand...
Click to collapse
I will be performing another system recovery install soon, so I will post the results. My computer got screwed up again, so backing everything up now...
I still have a problem...
thanks for your tutorial.
I followed as you say, but I can't find my phone in cmd mode in my computer.
I succeed to install driver also it's shown in device manager as like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but something wrong in cmd mode as like this.
I'v tried whatever I can do..reinstall driver, adb, swipe my phone..
what shall I do now?
adb problem
Hi,
Same problem here, tried everything but CMD just is not showing any device...
I found the solution: make sure that debugging mode is checked in your G1 settings because if not ADB will not work.
pluplus said:
I found the solution: make sure that debugging mode is checked in your G1 settings because if not ADB will not work.
Click to expand...
Click to collapse
I followed this completely, I have the phone installed correctly now, not a mass storage device, device manager reads:
ADB Interface > HTC Dream Composite ADB Interface
However, I have usb debugging enabled, and still get the same *error: device not found*
Took a decent amount of time to get done right too, thanks to "trustedinstaller" being the only "user" that can delete drivers on my laptop..yay for changing ownerships! You'd think administrator would suffice, but nay.
Anywho..wtf am I missing here?
edit: win 7 x64, however the same rules for this how-to should still apply, as all the drivers and install options/processes are identical
ive found that trying to use the adb driver the driver gave me error code 10 (within the device manager)
ive got rc win7 64 bit
what i used to get rid of this problem is the program called USBdeview ( google for it)
and uninstalled everything related to htc/android
after connecting the phone the correct driver installed and i could use the adb device
I didn't want to make another topic on this, but I have a problem. Whenever I uninstall the drivers from device manager, then search for new devices, it installs the drivers automatically. I have mass storage and adb dream interface, but no devices are found when I execute the adb command. I cleaned out what I could from the system32 and /drivers folder. Any clues? Just to add, it did work about a week ago, didn't need to use it, now it doesn't work.
Edit: Oops, I forgot the check the uninstall driver box. I have the drivers, they install correctly, but I still can't use adb.
PS: vista x64, installing from the amd64 subfolder.
sangeet.003 said:
Hi Guys!!!
Recently I had A problem Installing Windows 32 bit Driver For Android So i searched On the web for this error & Found that there were many people with this error...
Here Is the info about that Error In My Last Post: http://forum.xda-developers.com/showthread.php?t=493604
The error was so:
When we download the android_usb_windows.zip then extract it and then try to install it via device manager all goes right it detects the driver but at the last step where it asks for androidusb.sys file and when given the path it waits some time and says Fatal Error...
SO I tried To Go deep in the system32 folder There Go into Drivers Folder Now Here You begin some stuff:
1. Go in "C:\WINDOWS\system32\drivers" Folder there Find These files and cut them and paste in some folder where its safe:
androidusb.sys
usbccgp.sys
usbstor.sys
wdf01000.sys
2. Now Go to device manager "Right-click My Computer -> Manager -> Device Manager"
3. Click On ADB Interference Or something like that U ll Get a sub-category Right-click on it Click Uninstall -> OK
Do The Same For the Following :
USB Composite Device
USB Mass Storage Device
4. Get The Drivers From Here If U already Don't Have: http://dl.google.com/android/android-sdk-windows-1.0_r2.zip
OR
Get The Haykuro's Updated USB Drivers from here : http://sapphire-port-dream.googlecode.com/files/usb_driver_updated.zip
5. Now Try To Install The Driver Again By Going to "Right-click My Computer -> Manager -> Device Manager -> Action -> Scan for Hardware Changes" Then You will Get a pop-up saying Found New Hardware...
6. Install the drivers As Usual..... It Will install The Drivers Succesfully....
You Are Done.....
Click to expand...
Click to collapse
nothing happeneds...
after doing that after reboot my laptop,i'm loosing harware keyboard and have some other problems too..
i just change the drivers again and reboot and all ok but there isn't any way to my laptop(toshiba xqosmio x300 with vista 32bit)read my hero in fastboot usb condition...
i tried it and in 2 pc's with xp (service pack 2) but the same again and there....
adb shell and adb devices aren't reade the phone in fastboot usb ....
in my cmd i'm taking allways the same error message when i try to load the cm-hero-recovery.img ""canot load cm-hero-recovery.img""
anybody who can help??
i have the windows usb drivers. and when i go into device manager on my 32bit vista machine, it shows "Android Phone" under portable devices. i click update drivers and select the usb drivers. problem is, it tries to install them, then i get a message saying like 'unable to install "da da what ever driver its called" then it just closes.
why wont this work help is appreciated
THANKS, i was keen to install linux
Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you.
You save my life. I've been having this problem for MONTHS!!! and no way im gonna restore my windows xp again. Thanks so much.
Hey there,
My Asus Transformer TF101 was working fine yesterday... I recently updated to ICS without any problem. I then rooted my device using viperMOD PrimeTime v4.5. Once again, everything worked without any problem.
After rooting, I ran the V6 SuperCharger script. The device rebooted and everything was fine... Then according to the instructions, I downloaded a modified version of the services.odex file and I replaced the original system file (I did kept the original file by changing the extention to .tmp). This is the last time I've seen my Transformer booting. I did this because of the reply from bsoplinger on this post:
http://forum.xda-developers.com/showthread.php?t=991276&page=906
The thing is that I forgot to change the owner:group to root:root and to chmod 644. I believe this is where I failed.
Asus Transformer TF101 B80
Rooted ICS with viperMOD PrimeTime v4.5
V6 SuperCharger Script activated (Choose Option #8)
Replaced original services.odex with a new "empty" one
Now, when booting it gets stuck on the Asus Logo with the rotating loading circles... they keep rotating forever until the battery is drained out.
This is what I tried:
Booting with Power button & Volume down then Volume down again (tried Cold boot and Wipe)
Booting with Power button & Volume down then Volume up (Recovery)
Booting with Power button & Volume up + NVFlash (won't work because it is not a B50-B60-B70)
Drained the battery to 0%
Put an official firmware update zip file on a microSD and booted with it
So.... this is pretty much it... As of now, I'm out of ressources and I don't know what else I can do... 40$ via Paypal to the first persone who gives me a working solution.
Thank you for your time!
If you have the original saved on your PC, try pushing it to your TF with ADB
So you can boot into recovery? If you can get into there I'm sure there are ways to fix your bricked device.
Which recovery are you using? If you don't have it already, I'd recommend installing CWM recovery and flashing a new kernal/rom.
There are plenty guides on how to do that, or I can try to walk you through it but if you managed to do that other stuff to your transformer I think you'd be able to follow the current online guides.
baseballfanz said:
If you have the original saved on your PC, try pushing it to your TF with ADB
Click to expand...
Click to collapse
Actually, the renamed original file is only on the internal SD card of the Transformer. I don't have a copy.
I am currently trying to ADB work... I installed the proper APX drivers but I get a message from Windows saying that the ASUS Android MTP Drivers failed to install and all I get from ADB/Fastboot is a "- waiting for device -" message...
I'm using Windows 7 Pro 64bit
Jfuginay said:
So you can boot into recovery? If you can get into there I'm sure there are ways to fix your bricked device.
Which recovery are you using? If you don't have it already, I'd recommend installing CWM recovery and flashing a new kernal/rom.
There are plenty guides on how to do that, or I can try to walk you through it but if you managed to do that other stuff to your transformer I think you'd be able to follow the current online guides.
Click to expand...
Click to collapse
Thanks for your reply. I am new to Android but as far as I know I can only get into the stock Asus recovery mode. I can't get (or don't know how to get into CWN recovery). CWM was supposed to be included in viperMOD PrimeTime v4.5 root but I am unable to boot in it.... I am trying to make ADB/Fastboot work to see if I can launch it from there but so far I can't make it communicate with my device...
When I press Power + Volume Down and then Volume Up, all I get is a green android robot with a black "!" in a red triangle...
I had the same issue for a while, on my windows 7, it seems there are multiple things that may be using the same resources you need for this process to work. Try ctr + alt + delete to view running processes, and shut down anything that may be using adb. It is crucial to shut down Asus sync, asus webstorage, etc, as they tie up your adb line when trying these methods.
I had bricked my transformer as well, and all the processes to fix it weren't working because of "waiting for device" messages.
They finally started working once I closed all other programs using adb.
Plus, with nvflash, make sure to unpack the Rom into the folder, rather than just having the rom's zip in the folder.
After fixing the "waiting for device" error, I still couldn't get mine to work because the rom wouldn't flash over as is, I had to take the "Prime" rom's tar located with in nvflash, and extract the files into the same folder.
Once I did that, I ran nvflash, and the rom transfered over fine and I was able to unbrick my device.
Yeah you are still on stock recovery.
Your best bet is to get adb working, you can then pull the file, renamed and push it back.
bArDBQ said:
Thanks for your reply. I am new to Android but as far as I know I can only get into the stock Asus recovery mode. I can't get (or don't know how to get into CWN recovery). CWM was supposed to be included in viperMOD PrimeTime v4.5 root but I am unable to boot in it.... I am trying to make ADB/Fastboot work to see if I can launch it from there but so far I can't make it communicate with my device...
When I press Power + Volume Down and then Volume Up, all I get is a green android robot with a black "!" in a red triangle...
Click to expand...
Click to collapse
Try what I mentioned about shutting down processes and hold down Volume up plus power when booting. You'll see a black screen but that's ok, you can verify that there is actually something going on because your computer should make the sound stating a new device has been connected to your pc.
From that black screen, you should be able to get nvflash to work, assuming you've shut down other programs that could be using adb, and have installed the correct driver for nvflash, and have also unpacked the prime rom into the nvflashf folder.
Jfuginay said:
I had the same issue for a while, on my windows 7, it seems there are multiple things that may be using the same resources you need for this process to work. Try ctr + alt + delete to view running processes, and shut down anything that may be using adb. It is crucial to shut down Asus sync, asus webstorage, etc, as they tie up your adb line when trying these methods.
I had bricked my transformer as well, and all the processes to fix it weren't working because of "waiting for device" messages.
They finally started working once I closed all other programs using adb.
Plus, with nvflash, make sure to unpack the Rom into the folder, rather than just having the rom's zip in the folder.
After fixing the "waiting for device" error, I still couldn't get mine to work because the rom wouldn't flash over as is, I had to take the "Prime" rom's tar located with in nvflash, and extract the files into the same folder.
Once I did that, I ran nvflash, and the rom transfered over fine and I was able to unbrick my device.
Click to expand...
Click to collapse
I will try to close all process that might use ADB but I already know that NVFlash will not help me since my device is a B80 and that NVFlash won't work with anything over B70
baseballfanz said:
Yeah you are still on stock recovery.
Your best bet is to get adb working, you can then pull the file, renamed and push it back.
Click to expand...
Click to collapse
I will make ADB working and see what I can do from that... Should not be that difficult.
I am installing Asus PC Suite since it seems to be the best way to get the missing drivers...
baseballfanz said:
Yeah you are still on stock recovery.
Your best bet is to get adb working, you can then pull the file, renamed and push it back.
Click to expand...
Click to collapse
I just can't get ADB to see my device...
I installed Asus PC Suite, it does detect the device and show it as "Nvidia USB Boot-recovery driver for Mobile device" in Window's device list when I boot using Power Button + Volume UP... When I launch adb from command prompt deamon starts but when I type "adb devices" it shows: "List of devices attached" but that's it... no devices in the list.
I deleted the "Nvidia USB Boot-recovery driver for Mobile device" and installed the default ASUSTeK Computer Inc. drivers I already had in Windows drivers list "ASUS Android ADB Device" but I get the exact same result.
I also tried to install the USB Drivers from ASUS website "ASUS_Android_USB_drivers_for_Windows.zip" but it seems like they are not made for Windows 7 64bits... The OS doesn't see them or won't install them...
AAAAAAAAAAAAHHHHHHH
When using ADB you do NOT put it into APX mode.
Try cold booting your TF, once it get to the Eee Pad screen where it's stuck.
See if ADB can recognize your device there.
baseballfanz said:
When using ADB you do NOT put it into APX mode.
Try cold booting your TF, once it get to the Eee Pad screen where it's stuck.
See if ADB can recognize your device there.
Click to expand...
Click to collapse
......... I installed Asus PC Suite, Droid Explorer... Installed/Reinstalled drivers... nothing works... I get the nVidia APX drivers to work but I just can't get the MTP Drivers to work... it is always saying that the Device can't start...
I don't know what to do.
bArDBQ said:
......... I installed Asus PC Suite, Droid Explorer... Installed/Reinstalled drivers... nothing works... I get the nVidia APX drivers to work but I just can't get the MTP Drivers to work... it is always saying that the Device can't start...
I don't know what to do.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi bArDBQ,
First of all, the driver pkg 'ASUS_Android_USB_drivers_for_Windows.zip' IS the correct pkg and contains both 32 and 64 bit drivers; the .INF (installer file will enumerate/choose the correct files)
The image you posted (Device Manager) isn't even showing ADB 'mode'; 'Android Device/Phone' should be at the top of the list, if you've already manually installed the drivers or 'Other devices|Unknown device' if you have not .
Make sure you have USB debugging enabled in Settings on the device
After enabling, when you connect to your PC you will have an ?unknown? device in Device Manager under 'Other devices' and have to install/update the drivers manually (unless the files from ASUS PC Suite are still in Windows driver store).
Right-click 'Unknown device' > Update Driver Software... > Browse my computer for driver software > Browse | Include subfolders - (choose the extracted folder 'Android' e.g., [ ASUS Android USB drivers for Windows_20110321\Android ] )
You can also update 'ASUS Android MTP Device' the same way; just choose the 'MTP' driver sub-folder instead of 'Android'
You probably could just choose the top-level folder (extracted USB Driver folder) when choosing for each driver (because we chose 'Include subfolders') but that's up to you.
HTH,
-JR-
baseballfanz said:
When using ADB you do NOT put it into APX mode.
Try cold booting your TF, once it get to the Eee Pad screen where it's stuck.
See if ADB can recognize your device there.
Click to expand...
Click to collapse
So, cold-booting did not help, when I do this, the device manager shows that the "ASUS Android MTP device" drivers failed to install. I get the Code 10 (This device cannot start)
jazzruby said:
Hi bArDBQ,
First of all, the driver pkg 'ASUS_Android_USB_drivers_for_Windows.zip' IS the correct pkg and contains both 32 and 64 bit drivers; the .INF (installer file will enumerate/choose the correct files)
The image you posted (Device Manager) isn't even showing ADB 'mode'; 'Android Device/Phone' should be at the top of the list, if you've already manually installed the drivers or 'Other devices|Unknown device' if you have not .
Make sure you have USB debugging enabled in Settings on the device
After enabling, when you connect to your PC you will have an ?unknown? device in Device Manager under 'Other devices' and have to install/update the drivers manually (unless the files from ASUS PC Suite are still in Windows driver store).
Right-click 'Unknown device' > Update Driver Software... > Browse my computer for driver software > Browse | Include subfolders - (choose the extracted folder 'Android' e.g., [ ASUS Android USB drivers for Windows_20110321\Android ] )
You can also update 'ASUS Android MTP Device' the same way; just choose the 'MTP' driver sub-folder instead of 'Android'
You probably could just choose the top-level folder (extracted USB Driver folder) when choosing for each driver (because we chose 'Include subfolders') but that's up to you.
HTH,
-JR-
Click to expand...
Click to collapse
Hello JR,
Thanks for the reply.
I manage to show the ghost devices and hidden device in the device manager. I deleted everything, and rebooted the computer. I connected the Transformer and cold-booted. Windows detected the device and I choose the MTP drivers from ASUS_Android_USB_drivers_for_Windows.zip but I got the same result. When I was booting using the Power Button + Volume Up Windows was detecting the device in ADB mode and I was able to install the proper drivers and make it work.
This said, it was impossible for me to get the Transformer in the device list in ADB. My computer simply can't connect to the tablet.
I can't make sure USB debugging is enabled in Settings on the device since the device do not boot but it was before it was bricked.
bArDBQ , did you ever get this working. it seems i'm in the same boat your in except i'm on b70
BiohazardPL said:
bArDBQ , did you ever get this working. it seems i'm in the same boat your in except i'm on b70
Click to expand...
Click to collapse
Hey,
No, I was unable to fix the problem. I returned the device to ASUS and my replacement unit is on its way. I guess I was lucky they were not able to fix it.
Since you are on a B70 you might be able to use NVFlash. You should try it if not already done.
Good Luck!
SON OF A BBBBBBbbbbb
Son of a bbbb... Son of a BBBB.... Son of a BBBB... hot damn. Ok Rooted, stock TF101. I was beta testing an app, and got the andy on his back with red triangle for my TF101 (us variant). I can see the Eee pad logo start, then nothing, only the back light stays on. Recovery leads to andy on his back. I tried Vol down + Power until reboot, then let it settle and come up with either choose to enter android or wipe data. Either one does nothing. Only the back light stays lit.
Recovery option is a no go.
Normal cold boot is a no go,
Hot boot is a no go.
PERI is a no go.
NVFlash is not tried yet.
ODIN is a no go.
12 pack of beer is a GO. Need more though I think.
Any assistance would be helpful.
UPDATE : Easyflash with the latest OFFICIAL Asus 4.0.3 update worked perfectly. NOTE : there was a simple partial file error that caused the problem.
Hello!!
First off; This is copied, from my thread, in the Galaxy Nexus forum... Sorry, if you find the words "Galaxy" or "Samsung". But, this works for pretty much every phone, (except, for the USB drivers)...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, give it a go...
I haven't found another tutorial, like this at all... So, if you find something like this it's copied from me
Now, on to the actually interesting stuff ^^
I have found a solution, to the following problem;
After installing Windows 8, you cannot install fastboot drivers, but it recognizes the ADB drivers...
Solution:
Note: If you feel more comfortable using the Windows Power Shell, you can use that as well, it is, after all, only the Windows shell
Open the dev-manager, by typing following, in a command prompt window, or the run dialog. Whichever you prefer... :
Code:
[B][COLOR="Cyan"]devmgmt.msc[/COLOR][/B]
Now, the device manager, should pop up.
Install ADB drivers, (If you do not have them present, download them here
To prevent confusion: When I say install, it can mean unpack, or install... Quick tip: An installer does nothing, apart from unpacking files, to allocated space, on your computer
Download USB drivers, from here. (Link fixed. Again (-_-") ) (Note: These are the Sammy OEM drivers.)
Should you NOT have drivers installed:
Install the USB drivers, and download ADB/fastboot drivers.
Installation of ADB/fastboot drivers:
Open the device manager, and look for "Samsung Mobile Device", or "Unidentified Device". You can make your search easier, by unplugging the phone, whilst in device manager, then plug it back in, and see what's changed...
Once you have found your phone, Perform a right-click, on the device. Select : "Update device drivers", once the dialog has popped up, choose "Browse my computer" and goto your desktop, where you have installed the files to.
Open just the "drivers" folder, nothing else...
Select OK, then wait for installation to finish.
Once that has been done, you need to reboot your device, into bootloader mode; do this by typing
Code:
path=%userprofile%\Desktop\ADB\
adb reboot-bootloader
into the command prompt (download & install this, if you want to do it the cmd-way...)
Or, turn off your phone, and reboot i it manually into bootloader-mode, by pressing
Code:
VOL UP +DWM & PWR
together, untill phone vibrates...
Once the phone is in bootloader, go back to the device manager, and look for a device named "android 1.0". Perform a right-click on this and select "Update device drivers". Again, selct "Browse my computer", but, instead of clicking on "Browse" and selecting the folder, again, select "Let me pick from a list of drivers." Once the menu has popped up, select "Samsung Android ADB interface". Click OK, and wait for the drivers to install . Then, you're done. You have then successfully installed the ADB + fastboot drivers correctly, to test this, open a cmd window, and type following:
Code:
path=%userprofile%\Desktop\ADB\
fastboot devices
If your device shows up, then you have done it!!
Now type:
Code:
fastboot reboot
adb wait-for-device
adb kill-server
Note: while the phone is booting (If you typed "adb wait-for-device") A cursor will blink, wait for that, to stop blinking, then type the next command
I hope you learned, from this tutorial!! Check out Beatsleigher & M4gkman's Universal Android Toolkit, if you have enough time
Should you have problems, in recovery, open your dev. manager, and look for following device:
Code:
Full
Select, right-click. Update driver (blah, blah, witter, droan)
Browse my computer -> Let me pick -> Samsung ADB -> Done. You have enabled the ADB drivers, on your Android Device!!!!
So, apparently, if you're using Windows 8 and/or USB 3.0 ports, Windows installs its crappy drivers, so you should check out this link, posted by the awesome @tommy_riley and try it out for yourselves! Don't forget to drop him a 'Thanks'!
http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers <- Courtesy of @tommy_riley!
Wow. Over 40.000 clicks and downloads. I'm amazed at you guys!
It doesn't cost anything or hurt to hit that 'Thanks' button... Please be sure to hit it, it helps me out and also shows me what sort of content you want to see from me.
Do you like the effort I put into this? Then consider donating, by adding towards a new PC: http://www.gofundme.com/NewPC
With a new PC, I can create more one-click solutions and stuff and things!
Updates & other info!! (Reserved)
If you have a problem, I'll do it over TeamViewer, if you wish
Ok, here is some news, for you!
Well, according to some people, who have used this tutorial, Microsoft has done something new to their device driver signing.
I did not have note of this, as I was using Ubuntu most of the time and the laptop I was using broke, several weeks ago (It's gonna take me ages to get a new one, with which I can finally finish my ROM cooking..)
And Senior Member "purpler" has posted a link, which teaches you to turn device driver signing off, in the new bootloader, which Windows 8 is using/will be using, so; let's give him loads of thanks, for this!
here is his answer:
purpler said:
confirmed that it works but i had to diable driver signing from Windows8 bootloader (Shutdown.exe /r /o)
Use and Access Windows 8 Boot Loader and Advanced Boot Options
Click to expand...
Click to collapse
Many thanks to you, purpler!
Please, if you notice anymore changes, which interferes with this method, please let me know, how to solve the problem!
Every helpfull answer, with new solutions will be posted in this thread and thanked many times!
EDIT: If you don't want to donate, but still want to thank me, then use these links, instead of the links, in the tutorial.
Mod edit: No adfly links allowed.
4lex96 said:
I've solve the problem, in stead of usb 3.0 i used a usb 2.0 and it worked! Very strange, with 3.0 i had problem with 2.0 no. I hope this funny thing can help someone.
Best regards
Click to expand...
Click to collapse
Senior member 4alex96 has experienced some problems, while using USB® 3.0 ports.
If you are also experiencing these problems, or you have found a solution to this, be sure to post in this thread or write to me via PM and I'll be sure to quote and write this, so others also get to know and are able to get the most out of there Androids!
Creating a new tool!
Hey guys, I'm going to be creating a new tool or two, which will allow you to install ADB and Fastboot directly to the system root and which will install the Google drivers to your C:\ drive.
These tools will be available for a small donation, and they will save you a lot of work, i.e. you will never have to type in "path=<Whereever the ADB files are>" but you can just debug on
If you want to have the program, hit the "Donate to Me" button on the left of this post and donate a small amount. Then in the donation, write me a message, saying what it's for and give me your XDA username and I'll PM you the download link.
(Minimum of 5€)
tommy_riley said:
For Windows 8, I was having an issue getting my phone to be recognized in bootloader mode on an ASUS laptop that only had USB 3.0 drivers, I followed the procedures at the below URL (luckily I had an INTEL chipset) and once I replaced my native Windows USB 3.0 drivers with the Intel USB 3.0 drivers, I was able to work around a lot of issues:
http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
(I cant post HTTP links yet, but you should be able to plug the above into a browser to find the instructions...)
hope this helps!
Click to expand...
Click to collapse
You get that, guys? Go check out that website, and try it out for yourselves!
Tried using this fix keep getting an error saying the driver is not signed.
-Edit
Got it working had to go into advanced boot options and turn off device signing
thisiswar951 said:
Tried using this fix keep getting an error saying the driver is not signed.
-Edit
Got it working had to go into advanced boot options and turn off device signing
Click to expand...
Click to collapse
Ok, cool. I haven't been on my laptop, for a few days, so I wouldn't know, if MS has released any updates, yet...
I was thinking: WTF is he talking about? It's worked by so many people :O...
xD
LG familyguy59
confirmed that it works but i had to diable driver signing from Windows8 bootloader (Shutdown.exe /r /o)
Use and Access Windows 8 Boot Loader and Advanced Boot Options
Hi, I'm using win8 pro 64bit rtm.
when I double click on the UsbDrv.exe from Samsumg nothing comes up.
even when I run it in compatibility mode it doesn't help...
any ideas? I have disabled signed drivers.
thanks!
hshen45 said:
Hi, I'm using win8 pro 64bit rtm.
when I double click on the UsbDrv.exe from Samsumg nothing comes up.
even when I run it in compatibility mode it doesn't help...
any ideas? I have disabled signed drivers.
thanks!
Click to expand...
Click to collapse
You'll have to wait a moment, the system has to look for all the needed files, in the exe, and then needs to try to execute. If it then doesn't work, I'll upload an updated version, but as this seems to be working pretty much fine, I'll hesitate, not that the updated verison causes problems.
Anyways, I was running Win8 64x and it worked fine, just let the computer do it's work and it will work sooner or later, if nothing happens, even after waiting for 5-10 minutes, then try running it with administrative rights (Run as administrator).. Let me know if it works!
Doesn't work for me because I cant even see my S3 in the device manager.
leeznon said:
Doesn't work for me because I cant even see my S3 in the device manager.
Click to expand...
Click to collapse
Then try a different computer Doesn't mean that your S III is kaputt, does it?
If it then doesn't work, you've probably got dirt in the socket, or something else, like that.
And if you don't have dirt in the socket, then I don't know, whats wrong, but it'll definitely go over warranty
I have find an easiest way to install adb driver on windows 8 : ( disabling driver signature )
- after BIOS on "choose Operating system" screen
-clic "change default setting"
-clic "choose other option"
-clic "troubleshoot"
-clic "advanced option"
-clic " startup setting"
-clic on "restart"
-Install the driver adb as if you were on Windows 7 :laugh:
dalien26 said:
I have find an easiest way to install adb driver on windows 8 : ( disabling driver signature )
- after BIOS on "choose Operating system" screen
-clic "change default setting"
-clic "choose other option"
-clic "troubleshoot"
-clic "advanced option"
-clic " startup setting"
-clic on "restart"
-Install the driver adb as if you were on Windows 7 :laugh:
Click to expand...
Click to collapse
That's what the link in the first post is for. And you still need to follow the steps in the tutorial, otherwise it won't work properly.
I know the tutorial looks complex, but it isn't. You just need to read properly
LG familyguy59/Beatsleigher
EDIT: It's spelled "click"
help me to connect android in win 8
Please help me i am not expert I will give my teamviewr password. i spent hole to connect my android to win 8 but not succeed. when you come to online just inform me. many thanks those were helping.
netbook said:
Please help me i am not expert I will give my teamviewr password. i spent hole to connect my android to win 8 but not succeed. when you come to online just inform me. many thanks those were helping.
Click to expand...
Click to collapse
OK, I will be back, tomorrow. I'm currently at a friend's, so I will be back tomorrow. Send me an e-mail, when you're back, and I'll help you, right away!
LG familyguy59/Beatsleigher
familyguy59 said:
Hello!!
First off; This is copied, from my thread, in the Galaxy Nexus forum... Sorry, if you find the words "Galaxy" or "Samsung". But, this works for pretty much every phone, (except, for the USB drivers)...
So, give it a go...
I haven't found another tutorial, like this at all... So, if you find something like this it's copied from me
Now, on to the actually interesting stuff ^^
I have found a solution, to the following problem;
After installing Windows 8, you cannot install fastboot drivers, but it recognizes the ADB drivers...
Solution:
Note: If you feel more comfortable using the Windows Power Shell, you can use that aswell, it is, afterall, only the Windows shell
Open the dev-manager, by typing following, in a command prompt window, or the run dialog. Whichever you prefer... :
Code:
[B][COLOR="Cyan"]devmgmt.msc[/COLOR][/B]
Now, the device manager, should pop up.
Install ADB drivers, (If you do not have them present, download them here
To prevent confusion: When I say install, it can mean unpack, or install... Quick tip: An installer does nothing, apart from unpacking files, to allocated space, on your computer
Download USB drivers, from here. (Link fixed) (Thanks so much for 5k+ downloads!!)
Should you NOT have drivers installed:
Install the USB drivers, and download ADB/fastboot drivers.
Installation of ADB/fastboot drivers:
Open the device manager, and look for "Samsung Mobile Device", or "Unidentified Device". You can make your search easier, by unplugging the phone, whilst in device manager, then plug it back in, and see what's changed...
Once you have found your phone, Perform a right-click, on the device. Select : "Update device drivers", once the dialog has popped up, choose "Browse my computer" and goto your desktop, where you have installed the files to.
Open just the "drivers" folder, nothing else...
Select OK, then wait for installation to finish.
Once that has been done, you need to reboot your device, into bootloader mode; do this by typing
Code:
path=%userprofile%\Desktop\ADB\
adb reboot-bootloader
into the command prompt (download & install this, if you want to do it the cmd-way...)
Or, turn off your phone, and reboot i it manually into bootloader-mode, by pressing
Code:
VOL UP +DWM & PWR
together, untill phone vibrates...
Once the phone is in bootloader, go back to the device manager, and look for a device named "android 1.0". Perform a right-click on this and select "Update device drivers". Again, selct "Browse my computer", but, instead of clicking on "Browse" and selecting the folder, again, select "Let me pick from a list of drivers." Once the menu has popped up, select "Samsung Android ADB interface". Click OK, and wait for the drivers to install . Then, you're done. You have then successfully installed the ADB + fastboot drivers correctly, to test this, open a cmd window, and type following:
Code:
path=%userprofile%\Desktop\ADB\
fastboot devices
If your device shows up, then you have done it!!
Now type:
Code:
fastboot reboot
adb wait-for-device
adb kill-server
Note: while the phone is booting (If you typed "adb wait-for-device") A cursor will blink, wait for that, to stop blinking, then type the next command
I hope you learned, from this tutorial!! Check my root helper out, if you have enough time
Should you have problems, in recovery, open your dev. manager, and look for following device:
Code:
Full
Select, right-click. Update driver (blah, blah, witter, droan)
Browse my computer -> Let me pick -> Samsung ADB -> Done. You have enabled the ADB drivers, on your Android Device!!!!
Thanks a ton for 6k+ views/downloads!! The thanks are also very much appreciated!!
9K+ views!!
15K+ views!!!
Click to expand...
Click to collapse
Thanks!!!!! You have no idea how you helped me! Now I don't haveto dual boot Win7 just for this purpose! Thanks a ton!!
llsiddhantll said:
Thanks!!!!! You have no idea how you helped me! Now I don't haveto dual boot Win7 just for this purpose! Thanks a ton!!
Click to expand...
Click to collapse
I'm always glad to help, dude
LG familyguy59/Beatsleigher
heads up - driver signature enforcement policy on win8 can cause some problems. i just disabled it.
shaolinx said:
heads up - driver signature enforcement policy on win8 can cause some problems. i just disabled it.
Click to expand...
Click to collapse
We're already aware of that (see post #2) but still thanks for briefing everyone again.
LG familyguy59/Beatsleigher
Cyanogenmodded very skankily via XDA app. Skanky, indeed
Hi
i try to do this from yesterday night (maybe from 3 o'clock) and nothing... I've windows 8 64bit and xperia S with ICS. With windows 7 i haven't problem but with windwos 8...
Can you help me trought teamviewer?
Thanks a lot dude!
4lex96 said:
Hi
i try to do this from yesterday night (maybe from 3 o'clock) and nothing... I've windows 8 64bit and xperia S with ICS. With windows 7 i haven't problem but with windwos 8...
Can you help me trought teamviewer?
Thanks a lot dude!
Click to expand...
Click to collapse
Well, not at the moment, but I'll get back to you, as soon as I can!
But, to save time, when I'm on your PC, could you make sure you have the executables (ADB, fastboot and the DLLs) from the first post and your OEM USB drivers? That saves a heck of a lot of time
LG familyguy59/Beatsleigher
familyguy59 said:
Well, not at the moment, but I'll get back to you, as soon as I can!
But, to save time, when I'm on your PC, could you make sure you have the executables (ADB, fastboot and the DLLs) from the first post and your OEM USB drivers? That saves a heck of a lot of time
LG familyguy59/Beatsleigher
Click to expand...
Click to collapse
I've solve the problem, in stead of usb 3.0 i used a usb 2.0 and it worked! Very strange, with 3.0 i had problem with 2.0 no. I hope this funny thing can help someone.
Best regards
Hello all,
I picked up a used TF700T in good shape. Looks like some kid only used it to play Minecraft.
It pulled an OTA update to JB4.2.1, build .10
The goal is to put CROMBi-KK on there; I've read a bunch of the threads on the topic.
So first I tried to get the unlock tool on there...
-downloaded Unlock Tool V8 to PC, hooked up tablet via USB (USB debugging enabled, trusting unknown sources): no luck, getting the "USB device not recognized" error, PC keeps alternating the USB-connect&-disconnect sounds.
-Went ahead and downloaded Unlock Tool V8 straight to tablet. Getting "App not installed" error.
-Went and got Unlock Tool V7 instead, installed successfully - but now getting "network error" repeatedly...
-Read somewhere that signing in to Asus Tracker triggered unlock success for some, so I tried that: the Tracker website won't even take my serial number...
Obviously I am stuck early on - What do I do next?
What's the magic words to use with Asus support, can they even help me?
Asus support might be extra tricky because the previous owner may have registered the serial number...
Any obvious solution I am missing (I have used the forum search, but haven't found any new leads...)?
Do I just keep trying the Unlock tool V7 until the end of days?
bas2205 said:
Obviously I am stuck early on - What do I do next?
Click to expand...
Click to collapse
Had the same problem; it's a common bug with tf700t: some serial numbers (only of tf700t) aren't registered in factory's servers.
I pulled a ticket with ASUS support (here in Germany), explaned the problem, sent them the MAC adress and S/N of my tab and got 3 days later notice, that my tab could be unlocked - and it worked, they registered tab in their korean servers.
das chaos said:
Had the same problem; it's a common bug with tf700t: some serial numbers (only of tf700t) aren't registered in factory's servers.
I pulled a ticket with ASUS support (here in Germany), explaned the problem, sent them the MAC adress and S/N of my tab and got 3 days later notice, that my tab could be unlocked - and it worked, they registered tab in their korean servers.
Click to expand...
Click to collapse
Wow! That's the easiest resolution of that common problem I've ever heard of! Hope it goes just as well for him ^^
BTW, the servers are in Taiwan at HQ I believe
berndblb said:
Wow! That's the easiest resolution of that common problem I've ever heard of! Hope it goes just as well for him ^^
BTW, the servers are in Taiwan at HQ I believe
Click to expand...
Click to collapse
I thought, it was Taiwan, but was to lazy to look it up.
I did not invent this; it has been reported repeatedly in german boards.
Thanks again for the info guys!
I did as recommended, contacted support, telling them my serial number and MAC address. Got a response within ~36h saying they forwarded my request and the other department will take care of it in 10-15 days. So I am crossing my fingers for this to take care of the unlock issue.
I have been trying all sorts of stuff for the USB issue, no success so far. The person I got it from complained about the tablet not charging. Wondering if those two issues are related, I am suspecting a bad USB/charge port. Ordered a spare from ebay and will replace when it gets here next week. At this point (and not being the original owner), I am obviously not worried about warranty issues...
@das chaos : ich weiss allerdings nicht, ob der US-Support da genauso schnell geholfen haette; Gruesse aus TX.
bas2205 said:
@das chaos : ich weiss allerdings nicht, ob der US-Support da genauso schnell geholfen haette; Gruesse aus TX.
Click to expand...
Click to collapse
You're right as I usually am.
Hier muss wohl ein Nest sein!
I did get the spare USB ribbon&port on Saturday and replaced it. Unfortunately, that changed nothing;
I have also tried downgrading to V10.6.1.14.8 and even V10.4.4.25...
Same result, whenever I plug it into a PC (have tried different ones), it just says "USB device not recognized". When I select the "Unknown Device" under Devices&Printers, I don't even get the option of installing a different driver.
I have tried this with the Asus driver installed, then I tried with the 'naked' driver.
Tablet is in MTP mode; I have tried it with "USB debugging" disabled and enabled,nothing works.
Any ideas?
Tough, since you are not the original owner... The USB cable, I mean the external charging/data cable: Do you know if it is the original one?
May it be damaged as in : broken strands or some such?
bas2205 said:
I did get the spare USB ribbon&port on Saturday and replaced it. Unfortunately, that changed nothing;
...
nothing works.
Any ideas?
Click to expand...
Click to collapse
Same result in any of the 3 modes: apx, fastboot, normal?
.... if it's not charging either, you should be soon at an end with the tablet.
@berndblb: I had to buy a new (external) USB/charging cable and wall charger. I bought the ASUS original one straight from them through Amazon.
@das chaos: not sure what you mean - can I still get to APX or fastboot even if the tablet is not recognized upon plugging in?
How would I go about doing that, install first the tool/driver and hope that it assigns drivers properly when I plug in? @sbdags recommended I take a look at this thread (http://forum.xda-developers.com/showthread.php?t=2646279)...
In device manager, it does not show up with an exclamation point, but as an "unknown device"; The catch-22 with that is that Windows claims that the proper driver is installed and doesn't let me load a different driver. The connection is also a bit unstable, disconnecting&reconnecting after a few seconds (looks like an unstable USB stack...
bas2205 said:
@berndblb: I had to buy a new (external) USB/charging cable and wall charger. I bought the ASUS original one straight from them through Amazon.
@das chaos: not sure what you mean - can I still get to APX or fastboot even if the tablet is not recognized upon plugging in?
How would I go about doing that, install first the tool/driver and hope that it assigns drivers properly when I plug in? @sbdags recommended I take a look at this thread (http://forum.xda-developers.com/showthread.php?t=2646279)...
In device manager, it does not show up with an exclamation point, but as an "unknown device"; The catch-22 with that is that Windows claims that the proper driver is installed and doesn't let me load a different driver. The connection is also a bit unstable, disconnecting&reconnecting after a few seconds (looks like an unstable USB stack...
Click to expand...
Click to collapse
If it is shown up in Windows manager, then it is recognized! Only there are not the right drivers installed. For each mode (apx, fastboot, adb) you need a separate driver installed, wich normally are packed together in naked driver pack.
Windows doesn't install drivers of ASUS by it's own. You have to engage forced driver install routine; and there is a warning not to install those drivers. Do it nevertheless otherwise you won't be able to connect to transformers.
Thanks for the link. I was already aware of how to force a driver.
I took some screenshots to clarify where I am stuck.
First I get the USB not recognized error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next, in Device Manager, an Unknown Device shows up under USB (no exclamation point).
Then when I inspect it, it says No Drivers are installed.
When I try to point it at the driver through forcing procedure, it ends with " The folder you specified does not contain a compatible software driver for your device", despite me picking the correct inf. Same result for Naked Driver 0.72, 0.73 and the package sdbags referenced...
Ok, I think it's time to determine if you have a Windows/driver issue or a cable/port issue.
Try this Linux live CD: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
It comes with fastboot/adb already installed, doesn't need any drivers - so it should connect to your tablet with no problem at all. Unless there's a hardware issue....
bas2205 said:
Thanks for the link. I was already aware of how to force a driver.
I took some screenshots to clarify where I am stuck.
First I get the USB not recognized error
Next, in Device Manager, an Unknown Device shows up under USB (no exclamation point).
Then when I inspect it, it says No Drivers are installed.
When I try to point it at the driver through forcing procedure, it ends with " The folder you specified does not contain a compatible software driver for your device", despite me picking the correct inf. Same result for Naked Driver 0.72, 0.73 and the package sdbags referenced...
Click to expand...
Click to collapse
What do you have under Portable device? Your driver should be there....
Did you only do the 'Search folder for driver' routine or did you also try the ' Let me pick from a list of device drivers' option and then point to the folder with the naked drivers?
.... on second sight:
You seem to have an x64 OS. Are you shure, you got the appropriate drivers for x64? There seem to be different ones on the internet.
http://forum.xda-developers.com/galaxy-nexus/development/adb-fb-apx-driver-universal-naked-t1379875/
Scroll through the posts to find people with x64 machines having trouble with drivers.
bas2205 said:
Next, in Device Manager, an Unknown Device shows up under USB (no exclamation point).
Click to expand...
Click to collapse
Look under Details (Hardware Ids) for the VID and PID to see if this is really your tablet. These are the ones that I know:
0b05:4c90 = TF700
0b05:4c91 = TF700 in USB Debugging mode
0b05:4c92 to 4c95: TF700 in some other modes
0b05:4daf = Fastboot mode
0955:7030 = APX mode
LetMeKnow said:
What do you have under Portable device? Your driver should be there....
Click to expand...
Click to collapse
Unfortunately, all unrelated:
berndblb said:
Ok, I think it's time to determine if you have a Windows/driver issue or a cable/port issue.
Try this Linux live CD: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
It comes with fastboot/adb already installed, doesn't need any drivers - so it should connect to your tablet with no problem at all. Unless there's a hardware issue....
Click to expand...
Click to collapse
Thanks, I will get right to that homework... I hope it's a driver issue. If it is a hardware issue, since I have already ruled out the internal USB connector and I am dealing with a new USB&chargin cable, that would leave the MoBo...
berndblb said:
Ok, I think it's time to determine if you have a Windows/driver issue or a cable/port issue.
Try this Linux live CD: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
It comes with fastboot/adb already installed, doesn't need any drivers - so it should connect to your tablet with no problem at all. Unless there's a hardware issue....
Click to expand...
Click to collapse
Just tried the Live-CD... no luck! Both "adb devices" and "fastboot devices" returned an empty list despite me following instructions from the other thread.
I guess my last option (after I unlock) would be to try and install TWRP through the app method?
I need help and I need it fast!
I had my S7 G930F rooted a while ago and all was well until I recently decided my phone could use a restart. So I did, and after that I suddenly got the "Custom binary blocked" message.
I have already tried several things, but the phone is not connecting over USB, it refuses to charge, Odin doesn't see the device, and it won't boot into recovery mode.
It does however boot into Odin download mode but Odin refuses to see the phone so I can't perform a ROM flash.
Help?
You turned off "OEM unlock" ?
Need to stay enabled if you are running custom anything
Need to find a way to get ODIN to recognise the phone so you can flash the stock firmware again iirc
Check in device manager if driver it's installed or reinstall it.
I did turn off OEM Unlock at some point, but I believe the phone restarted somewere inbetween as well when it was off and I didn't experience any problems then.
The phone is trying to connect to the computer however but I don't see how or what drivers I need to install. I already tried to reinstall the samsung usb drivers and all the other android drivers you can find online.
Windows should install the drivers itself
Try a different USB cable / Port / PC
Trust me I have tried all these options. Windows keeps trying to search for drivers but it can't find them and then it stops doing anything with it.
And I have tried every single USB port and cable I own.
ChaoticQube said:
Trust me I have tried all these options. Windows keeps trying to search for drivers but it can't find them and then it stops doing anything with it.
And I have tried every single USB port and cable I own.
Click to expand...
Click to collapse
Try installing these
http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Or extract with 7zip and manually install via device manager
*Detection* said:
Try installing these
http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Or extract with 7zip and manually install via device manager
Click to expand...
Click to collapse
Already have, those were the first I installed. Didn't work.
ChaoticQube said:
Already have, those were the first I installed. Didn't work.
Click to expand...
Click to collapse
Listing the things you have already tried would help, rather than others wasting their time linking you to things and explaining how to do things, for you to say "Already done it"
Anyway, you need to get the PC to see the phone, flash stock, job done
Good luck
*Detection* said:
Listing the things you have already tried would help, rather than others wasting their time linking you to things and explaining how to do things, for you to say "Already done it"
Anyway, you need to get the PC to see the phone, flash stock, job done
Good luck
Click to expand...
Click to collapse
I have tried to install all available USB drivers related to the G930F.
My device manager currently shows a USB-controller and SM-buscontroller as missing drivers (plus an unknown devices which is most likely the phone), after re-installing the Samsung drivers they still come up as drivers that are not there or are not installed.
ChaoticQube said:
I have tried to install all available USB drivers related to the G930F.
My device manager currently shows a USB-controller and SM-buscontroller as missing drivers (plus an unknown devices which is most likely the phone), after re-installing the Samsung drivers they still come up as drivers that are not there or are not installed.
Click to expand...
Click to collapse
Did you tried also on a different pc? Maybe you have some issue on yours. Put in download mode and try to flash it with a different computer
gsdamian said:
Did you tried also on a different pc? Maybe you have some issue on yours. Put in download mode and try to flash it with a different computer
Click to expand...
Click to collapse
I don't have access to another PC, this is the only one I got. I doubt it could be my PC since it used to work before, it's the same PC I used to root the phone.
ChaoticQube said:
I don't have access to another PC, this is the only one I got. I doubt it could be my PC since it used to work before, it's the same PC I used to root the phone.
Click to expand...
Click to collapse
Sometimes can be those kind of problems with usb motherboard or drivers conflict, before making sure phone has an issue I suggest to try what I said, maybe you find a different pc to test
gsdamian said:
Sometimes can be those kind of problems with usb motherboard or drivers conflict, before making sure phone has an issue I suggest to try what I said, maybe you find a different pc to test
Click to expand...
Click to collapse
You're obviously not reading the previous posts, I already determined that it is a driver issue. And if I don't have easy access to another PC you can't continue suggesting the idea.
Regarding USB-controller and the phone not being recognised. What I need to know is what drivers I need to install other than Samsung's.
ChaoticQube said:
I have tried to install all available USB drivers related to the G930F.
My device manager currently shows a USB-controller and SM-buscontroller as missing drivers (plus an unknown devices which is most likely the phone), after re-installing the Samsung drivers they still come up as drivers that are not there or are not installed.
Click to expand...
Click to collapse
Sounds like possibly your motherboards chipset drivers are missing, or something along those lines
Do other USB devices work OK?
Check your motherboards manufacturers site for drivers and get all those missing drivers fixed before connecting your phone
*Detection* said:
Sounds like possibly your motherboards chipset drivers are missing, or something along those lines
Do other USB devices work OK?
Check your motherboards manufacturers site for drivers and get all those missing drivers fixed before connecting your phone
Click to expand...
Click to collapse
All of my other USB devices (headphones, keyboards, adapters) work fine, no issues. I have also checked my motherboards manufacturer site but couldn't find any drivers that would relate to the issue.
Meanwhile, whenever I connect the phone, the pc tells me the device is unknown.
ChaoticQube said:
All of my other USB devices (headphones, keyboards, adapters) work fine, no issues. I have also checked my motherboards manufacturer site but couldn't find any drivers that would relate to the issue.
Meanwhile, whenever I connect the phone, the pc tells me the device is unknown.
Click to expand...
Click to collapse
Well those devices you list as not being installed are related to the chipset
Right click each one in turn, > properties > details tab > select the "Hardware ID" dropdown box
Copy the long ID at the top and google it to find out what the device is, and subsequently which driver you are missing
(BTW - If your phone is not connected, any missing device driver is not the phone)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did all you told me and found all the missing drivers but indeed, the phone is still coming up as an unknown device, not sure what driver to install to be able to detect the phone.
ChaoticQube said:
I did all you told me and found all the missing drivers but indeed, the phone is still coming up as an unknown device, not sure what driver to install to be able to detect the phone.
Click to expand...
Click to collapse
OK, try this program
https://ghostbuster.codeplex.com/
1. Disconnect the phone
2. Run GhostBuster
3. Right any entry of each section and choose "Add class"
4. Click "Remove Ghosts" at the lower right corner
(The program might restart again with Admin privileges, if so just click "Remove ghosts" again)
This will remove all disconnected device drivers from the system forcing them to reinstall when reconnected, such as your phone
Reboot the PC, then connect the phone and see if it installs properly this time
*Detection* said:
OK, try this program
https://ghostbuster.codeplex.com/
1. Disconnect the phone
2. Run GhostBuster
3. Right any entry of each section and choose "Add class"
4. Click "Remove Ghosts" at the lower right corner
(The program might restart again with Admin privileges, if so just click "Remove ghosts" again)
This will remove all disconnected device drivers from the system forcing them to reinstall when reconnected, such as your phone
Reboot the PC, then connect the phone and see if it installs properly this time
Click to expand...
Click to collapse
Tried twice, didn't work. PC keeps saying "The USB device can not be recognized"
Maybe it helps when I say that the computer only sees the phone when it's in download mode.
I really don't know how to fix this. I do know that the phone is soft-bricked since it's able to start and boot into download mode and all.