This thread is a process of how to potentially get your phone prepared for these steps:
http://forum.xda-developers.com/moto-x/general/tut-resurrecting-bricked-moto-x-corrupt-t2629057
If your device says USB Input device and then disconnects after a few seconds, There is a potential theory as to how to bypass that.
After buying a "Factory cable" for the moto X for 10$ I plugged it into my computer and nothing, So i noticed that it would 'unplug' after it "installed" the driver. So i plugged it into the USB slot in my pc and found out that the green light not only showed up, but stayed on for a constant hour! This means that the phone must somehow still be alive and charging. The reason behind this is the fact that the TV didn't install the driver, but simply sent current to the cord. The problem is that if you've already installed the driver on your pc once, it will always fetch that same driver to install the device again. The bypass to that would be finding a Windows XP computer that asks if you'd like to install the drivers first. Or a Win 7/8 Pc that hasn't been connected to the Moto X yet. Go to devices and printers: right click my computer -> Driver installations -> Never install using Windows Update. This should allow you to install your own driver which is the one stated in the thread, I'm in the process of finding a Windows XP computer or borrowing a computer from one of my friends, anyone care to try this, or confirm other methods to bypass this?
omarachs said:
This thread is a process of how to potentially get your phone prepared for these steps:
http://forum.xda-developers.com/moto-x/general/tut-resurrecting-bricked-moto-x-corrupt-t2629057
If your device says USB Input device and then disconnects after a few seconds, There is a potential theory as to how to bypass that.
After buying a "Factory cable" for the moto X for 10$ I plugged it into my computer and nothing, So i noticed that it would 'unplug' after it "installed" the driver. So i plugged it into the USB slot in my pc and found out that the green light not only showed up, but stayed on for a constant hour! This means that the phone must somehow still be alive and charging. The reason behind this is the fact that the TV didn't install the driver, but simply sent current to the cord. The problem is that if you've already installed the driver on your pc once, it will always fetch that same driver to install the device again. The bypass to that would be finding a Windows XP computer that asks if you'd like to install the drivers first. Or a Win 7/8 Pc that hasn't been connected to the Moto X yet. Go to devices and printers: right click my computer -> Driver installations -> Never install using Windows Update. This should allow you to install your own driver which is the one stated in the thread, I'm in the process of finding a Windows XP computer or borrowing a computer from one of my friends, anyone care to try this, or confirm other methods to bypass this?
Click to expand...
Click to collapse
Did it work?
I have the same problem and i want to know if it has a solution. Also, is it necessary to have a factory cable?
viversba said:
is it necessary to have a factory cable?
Click to expand...
Click to collapse
Nope. Battery can be disconnected at all
Author, why start new topic? See existing.
+ driver pack for Moto + Qualcomm in attachment, for your needs )
But does this method work?
Could you bring yout Moto x back to life with this method?
viversba said:
Could you bring yout Moto x back to life with this method?
Click to expand...
Click to collapse
Yep. 95% rate, if not a hardware issue
Related
Ever since I rooted I can not get my Epic to connect to a computer period. I'm about to give up and just deal with what I got, hopefully someone can tell me what I'm doing wrong. Before anyone decides to be a smart ass I have used the search function literally for days and have tried tons of things recommended with no result. I am the first to admit I'm an idiot when it comes to anything involving computers but I'm pretty determained to learn.
This has to be the phone because I have tried to connect to 2 desktops (1 running Windows 00 and 1 running the most updated Ubuntu), and 3 laptops (Windows xp, Windows Vista and Ubuntu). When I rooted I used the Vista computer and connected fine (can't anymore). I didn't have the space on the C drive to install the Android SDK so I switched to Ubuntu (first time user btw lol). Somehow when I was backing my SD card I lost any access to it or the notification bar. I never got my SD back til I rebooted but I haven't been able to connect to any PC since. When I charge (even in the car) it always tries to stay in mass storage mode. I basically charge in my car with my phone off hoping it will just charge and not mount my sd card to my car or wall lol. Yes I wiped 3 times, partitioned sd, tried several different cables (but my husband used mine and no problems on his Motorola) I'm sure I've done something wrong when I rooted or mounted to Ubuntu.
I also can't use adb. I followed the directions to the t (a few times lol) but when I run any commands it says "no such file or directory" I didn't have adb on the windows pc when I di noobnl's one click so I never ran the (adb shell ect) commands. I now can't do jack. I am now running noobnl's DI18 ROM with modem.bin flashed thru Clockworkmod.
I have tried all the basics you will find wit 2 days of web search.
My goal is DK28 (dream on Erica lol)...Thanks for any help and for anyone sparing me a lashing ;-)
Sent from my SPH-D700 using Tapatalk
When you plug in on your windows pcs...in Device manager..do you see anything appear? also do you have USB debugging on the phone?
USB debugging on?
Have you tried reinstalling the drivers for the Epic?
Rebooted phone and PC? (Sometimes it helps)
Used Odin?
Something might have been screwed up during one of your downloads, bad file maybe. Try reinstalling your drivers first, use Odin (phone must be in download mode), and see if it recognizes te device. If it does then Odin the stock .tar file and go from there. It'll give you a fresh start.
That's all I can think of right now.
Sent from my SPH-D700 using XDA App
I bet your USB debugging is on since most root's requier it. Even tho it says connect to pc if usb debugging is on it wont connect to my windows 7 box
I would suggest, if you're really having this many issues, just boot into download mode (1 on the keyboard + power button) and odin back to di18.
Just for kicks have you tried Settings > Privacy > Factory data reset? I assume that wiping does the same thing if not more but it's worth it to see if it somehow resets a setting that might be the issue.
What's left - software issue or Hardware issue.
Software:
hmmm...yeah gotta try connecting through Odin which uses downloader mode instead of USB modes...
Can Odin see your phone? Run Odin as admin with antivirus off, and proper samsung drivers installed. Then boot phone holding down 1 key into downloader mode. Connect to computer through USB port on back of computer (i.e. directly to motherboard) - does Odin identify something attached to USB port?
Yes - flash the dk28!
No - with Odin still on, unplug the USB cable, pause, and reconnect it. Still No? Try a different USB port on computer. Also try uninstalling and reinstalling the drivers - be sure to reboot the PC. If still No, then try on another computer, and as you did before, try different cables. Still No?? --> hardware problem with phone.
Hardware problem with phone: Look at the usb port in the phone - is there any junk in there that might interefere with the connection?
Yes - clean it out
No: phone perhaps internally damaged:
Solution for hardware damage:
You and husband clean up and go to sprint store.
At store - tech will know phone is rooted, so:
--Tech more likely to like you? You handle it, maybe even blame husband. Husband can silently attend and look sheepish, playing the part of 'me man, me dominate environment, me break fancy tech of wife, me sorry." Try to get free replacement phone while simultaneously promising never to let your husband root the phone again, or even touch it.
--Tech more likely to like husband? He goes alone, cops to the true story of how you rooted it and then was backing stuff up when it suddenly stopped working [truth from men? so sincere!]. Try to get free replacement phone while simultaneously promising not to let you in the house should you even attempt to root again.
P.S. forgot to add you might turn off the PCs firewall while testing, as well.
quik99 said:
I bet your USB debugging is on since most root's requier it. Even tho it says connect to pc if usb debugging is on it wont connect to my windows 7 box
Click to expand...
Click to collapse
same here. I tried out the free tethering app the other day and with usb debugging on i coudl never get it to install the proper drivers. Without it on and the 64bit drivers installed Odin worked just fine.
I have seen many Galaxy S devices not connect to a computer because of a faulty USB cable. Had my girlfriends sister switch out 3 Vibrants only to accidentally try and connect it to a laptop with a different USB cable and I've seen two others not connect with the stock Samsung USB cable.
How I fixed the tethering issue
I've had the same problem with my galaxy s - connecting to the PC (Win7 32bit) just doesn't do anything. As a test, I had a friend with the same phone/rom (froyo, rooted) connect - and he was able to! It installed the drivers and it just worked. He disconnected, I connected, and now it's fine.
So, see if you can find someone with the same phone and see if they can connect. Makes no sense to me, but it worked.
I've had my Epic fail to mount before. Interestingly any time I had an issue it was with a Mac - it always mounts on a PC. I'll stop now before I open up a can of worms.
Best advice I have is get a Dropbox account. You can use that guy to move files from a computer to the SD card without having to mount to the computer. Perhaps you can get a factory ROM (with root of course) on your phone that way?
You can get a app from the market called SWIFTP (free) & connect to your sdcard via ftp server. This can be a temporary fix till you get your connection error resolved.
I have 1 USB port on my laptop that the Epic shows up as "unknown device" on. Works on every other port, and everything else works just fine on the same port. The factory USB cable is finicky!
hey guys,
I don't know if this still a problem with people. but I'm on win7 64bit and I can't seem to connect my nexus s, to my computer. I always have to upload from computer to dropbox then download the file from DB on my phone... usb plug doesn't work. I tried the same cable with my wifes Samsung vibrant and it recognizes it, but when i plug in my nexus s the debug icon shows up on my phones status bar for like 1 second and disappears. then window on my compter says "USB Device Not Recognized"
need help please.
What does it say in device manager (in windows)? Maybe the driver is wrong...
Sent from my Nexus S using XDA Premium App
do u have a right drivers installed
have a look here and check Google USB Driver
I'm having the same problem. I have tried both my computers and multiple cables but I continue to get the error. When I try to update the drivers or reinstall them Windows says the drivers are up to date. I've tried every USB port on both computers as well.
I even took the phone into a repair place to see if perhaps the USB port on the phone was malfunctioning and they couldn't find anything wrong with it.
solarus2011 said:
I'm having the same problem. I have tried both my computers and multiple cables but I continue to get the error. When I try to update the drivers or reinstall them Windows says the drivers are up to date. I've tried every USB port on both computers as well.
I even took the phone into a repair place to see if perhaps the USB port on the phone was malfunctioning and they couldn't find anything wrong with it.
Click to expand...
Click to collapse
Try installing pdanet, I had a similar issue when I rooted my ns and installing the pdanet drivers solved the problem.
Sent from my Nexus S using XDA App
I've been having the problem also and none of the fixes worked. Not even PDA net. You'd think that the more people have this problem so one would have found a real fix by now.
pnnorth said:
Try installing pdanet, I had a similar issue when I rooted my ns and installing the pdanet drivers solved the problem.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I can't get the PDAnet drivers to install - during the installation process, my phone has to plugged in, which of course the installation program can't see.
Weird thing is if I remove the battery and then plug the usb in and start the phone, the drivers show up in the device manager but they always disappear before I can unlock the phone - appears the USB connection on my Nexus S is broken...can;t think of anything else.
Hello all,
I have a Samsung galaxy S II purchased in Israel from Cellcom.
In my ill advised attempt to unbrand, and thus accelerate, improve memory and battery consumption, I flashed a stock ROM which I believed to be the latest.
The phone works great, with one exception. There seems to be no way to connect it to PC, be it WIN7 32bit or ubuntu 32bit. original usb cable or other cable, my stationary workstation or my laptop, be it USB Storage mode, USB Debugging, that stupid Kies mode, and most importantly because i'd like to flush it back, no Odin Mode. (in win32 - any mode gets "unknown device" status like the device doesn't publish it's name correctly or similar.)
moments before the flash the phone connected in all modes.
I think i've pretty much covered all of the obvious. and there is no problem with my latest sdk and drivers as my Nexus S still connects to both PC's with great success.
SO some info - and what I have already researched.
from http://forum.xda-developers.com/showthread.php?t=1113928, I gather that the PDA on my Cellcome bought SGS2 is either JIKG3 or JIKJ1. and that it's a GT19100T and I gather that denotes some kind of hardware specification.
the ROM I've flushed to my phone has this name:
GT-I9100_XEU_I9100XWKJ3_I9100XEUKH2_I9100XXKI3.tar.md5
everything seems wrong about this ROM in hindsight but, the worst is that it has no T, and probably isn't very hardware compatible. (though the telephony, wifi, camera, sensors and anything I tried works).
The phone is not rooted as after flushing I have lost any USB connectivity. I therefore cannot try and manipulate system files, to try to recover that way.
I have tried to root with the exploit apk. to no effect. I gather it's a statistically challenged way of rooting so I'll try my luck a lot more during the wait for your answer, and report any success.
**Edited**
the "Easy Rooting Toolkit" on http://forum.xda-developers.com/showthread.php?t=1319653
I'll try to run it as best I can, with the shell emulator, instead of on adb, but with debugging enabled.. although it's not a very East Toolkit, when I use it this way..
I'll still report any progress..
**/Edited**
I have seen no one on the internet with this problem. it's really a very stupid problem to have. but a problem nevertheless.
Any insight as to the moves I can try next will be greatly appreciated.
Any information I can add with my limited usb connectivity will be gladly shared. (my "Kies air" works so I can upload to storage that way.. plus i have a shell emulator installed..)
Regards,
Alex.
In ur Device Manager dose it show several unknown devices when connected?
teenvista said:
In ur Device Manager dose it show several unknown devices when connected?
Click to expand...
Click to collapse
just the single one.
There is absolutely nothing wrong with the ROM itself as I have been using it on my phone for a couple weeks now.
The problem exists between your phone and your PC, the PC is stating that it's an unknown device after all.
What I would try is to un-install the device in Device Manager, unplug the device and restart the PC and then plug the phone in again, if that does not work, I would throw in a factory reset of the device itself while repeating the above steps
I think i've pretty much covered all of the obvious. and there is no problem with my latest sdk and drivers as my Nexus S still connects to both PC's with great success.
Click to expand...
Click to collapse
What do you mean by that? The nexus drivers have nothing to do with the galaxy drivers. Only if you run an AOSP rom you will need those drivers. Not if you run a stock rom.
Am I right that your pc sees the phone, but does not recognize it? Did you try reinstalling kies? And then from within kies tried to reinstall the phone drivers?
your PC may not recognize the device after the radio or kernel is changed. what I did was uninstall every single usb device from device manager and reboot, fixed.
Reply to all
jamesyb0i said:
your PC may not recognize the device after the radio or kernel is changed. what I did was uninstall every single usb device from device manager and reboot, fixed.
Click to expand...
Click to collapse
jamesyb0i - I saw that some people have been successful after uninstalling all usb devices, I'm challenged in this task as my keyboard and mouse are USB. I will try it on my laptop as soon as I'll get access to it, though because of the wide range of computer and OS I've tried I'm pretty sure the effort will be ultimately futile.
Lennyz1988 said:
What do you mean by that? The nexus drivers have nothing to do with the galaxy drivers. Only if you run an AOSP rom you will need those drivers. Not if you run a stock rom.
Am I right that your pc sees the phone, but does not recognize it? Did you try reinstalling kies? And then from within kies tried to reinstall the phone drivers?
Click to expand...
Click to collapse
Lennyz1988 - I see your point about the ADB Driver for the Nexus S, but as for the other advice.
As I said, I extensively tried to run it on multiple PC's multiple OS's.
I did try to uninstall / reinstall kies, and kies drivers.
after that didn't help. I got an SGS2 from a friend, just to try it on my computer.
it worked just fine.
achillies400 said:
There is absolutely nothing wrong with the ROM itself as I have been using it on my phone for a couple weeks now.
The problem exists between your phone and your PC, the PC is stating that it's an unknown device after all.
What I would try is to un-install the device in Device Manager, unplug the device and restart the PC and then plug the phone in again, if that does not work, I would throw in a factory reset of the device itself while repeating the above steps
Click to expand...
Click to collapse
The problem I believe is specifically because of the GTI9100/GTI19100T differences
I'm sure as achillies400 said that there is nothing wrong with the ROM itself. BUT the problem is not with my PC's it is more likely the different hardware, and the hardware driver on the phone itself that makes my phone become an "unknown device".
Regards,
Alex.
You could try this exploit.
http://forum.xda-developers.com/showthread.php?t=1296916
Don't know if it will work for you but it's worth a try.
Extract the .zip to /data/local/ on your phone and run the commands.
alex.feigin said:
Hello all,
I have a Samsung galaxy S II purchased in Israel from Cellcom.
In my ill advised attempt to unbrand, and thus accelerate, improve memory and battery consumption, I flashed a stock ROM which I believed to be the latest.
The phone works great, with one exception. There seems to be no way to connect it to PC, be it WIN7 32bit or ubuntu 32bit. original usb cable or other cable, my stationary workstation or my laptop, be it USB Storage mode, USB Debugging, that stupid Kies mode, and most importantly because i'd like to flush it back, no Odin Mode. (in win32 - any mode gets "unknown device" status like the device doesn't publish it's name correctly or similar.)
moments before the flash the phone connected in all modes.
I think i've pretty much covered all of the obvious. and there is no problem with my latest sdk and drivers as my Nexus S still connects to both PC's with great success.
SO some info - and what I have already researched.
from http://forum.xda-developers.com/showthread.php?t=1113928, I gather that the PDA on my Cellcome bought SGS2 is either JIKG3 or JIKJ1. and that it's a GT19100T and I gather that denotes some kind of hardware specification.
the ROM I've flushed to my phone has this name:
GT-I9100_XEU_I9100XWKJ3_I9100XEUKH2_I9100XXKI3.tar.md5
everything seems wrong about this ROM in hindsight but, the worst is that it has no T, and probably isn't very hardware compatible. (though the telephony, wifi, camera, sensors and anything I tried works).
The phone is not rooted as after flushing I have lost any USB connectivity. I therefore cannot try and manipulate system files, to try to recover that way.
I have tried to root with the exploit apk. to no effect. I gather it's a statistically challenged way of rooting so I'll try my luck a lot more during the wait for your answer, and report any success.
**Edited**
the "Easy Rooting Toolkit" on http://forum.xda-developers.com/showthread.php?t=1319653
I'll try to run it as best I can, with the shell emulator, instead of on adb, but with debugging enabled.. although it's not a very East Toolkit, when I use it this way..
I'll still report any progress..
**/Edited**
I have seen no one on the internet with this problem. it's really a very stupid problem to have. but a problem nevertheless.
Any insight as to the moves I can try next will be greatly appreciated.
Any information I can add with my limited usb connectivity will be gladly shared. (my "Kies air" works so I can upload to storage that way.. plus i have a shell emulator installed..)
Regards,
Alex.
Click to expand...
Click to collapse
!!!!!!!!!!!!!!!
I have the same problem, and I couldn't find anyone else w/ it or with answers either.
almost all the same scenario except I have an SGSII AT&T I777 that started out as UCKJ1 and is now UCKH7
My phone started coming up as unknown device. I can not find any remedy to the solution.
Here's my scenario: http://forum.xda-developers.com/showthread.php?t=1372171
My guess is I might try to uninstall "new" programs that I added to the phone and PC, uninstall kies etc. and drivers, and maybe try and do a restore or refresh or something on my phone and see if I can get to "scratch" and re-start from there.
I installed winamp on phone and reinstalled it on PC for wifi, and it kept mounting/unmounting my SD card from phone to computer each time I plugged it in (I think that messed with my card possibly giving it "unknown")
Or also when I changed my Kernel may have made the phone unknown. Those are the only 2 changes I can assume did this to my phone =/
any update on your phone?
UPD: My kernel was causing all my problems. Restored to an earlier backup and it had older kernel. All problems were relieved.
Hey Guys,
Been following threads here for a while; Actually was able to flash my phone to the new froyo that was developed through this forum onto my phone- It's been a great help!
As everyone knows, they finally released the update for our phones. I would like to put mine back to stock and then do the update through Verizon. I am running into a problem though..
I have downloaded the SamsungDriver.exe file and installed it, but when I plug in my phone via USB, my computer does not recognize it, only charges it. Ideas? I am running Windows 7 64-bit. Thanks in advance!
Khammy87 said:
Hey Guys,
Been following threads here for a while; Actually was able to flash my phone to the new froyo that was developed through this forum onto my phone- It's been a great help!
As everyone knows, they finally released the update for our phones. I would like to put mine back to stock and then do the update through Verizon. I am running into a problem though..
I have downloaded the SamsungDriver.exe file and installed it, but when I plug in my phone via USB, my computer does not recognize it, only charges it. Ideas? I am running Windows 7 64-bit. Thanks in advance!
Click to expand...
Click to collapse
You need drivers specifically for our phone. Where did you get the ones you are attempting to use?
Also, check your usb settings, and make sure you are not set to charge only. Finally, check usb debugging in /settings/applications/development. I have a tutorial I made up for flashing to 09 with all the files you need here in the general section. See if it helps any.
Sent from my SCH-I400 using Tapatalk 2
Ok, so I have downloaded the new driver that you said to, but when I plug the phone into my computer, I still only get a charging response from my phone, no new device detection.. Hmm?
Khammy87 said:
Ok, so I have downloaded the new driver that you said to, but when I plug the phone into my computer, I still only get a charging response from my phone, no new device detection.. Hmm?
Click to expand...
Click to collapse
I know with my phone I have to reinstall drivers everytime after I plug my phone into computer, never recognize automatically, try plugging phone into computer then install drivers, see if that works.
Sent from my SCH-I400 using Tapatalk 2
Drivers
I would try getting them from the official samsung site thats where I got my drivers and they seem to work all the time my phone is always detected in odin.
You can get them right here:
http://www.samsung.com/us/support/owners/product/SCH-I400ZKAVZW?tabContent=content2
Khammy87 said:
Ok, so I have downloaded the new driver that you said to, but when I plug the phone into my computer, I still only get a charging response from my phone, no new device detection.. Hmm?
Click to expand...
Click to collapse
First, lets make sure you have the drivers you need.
http://www.samsung.com/us/support/owners/product/SCH-I400ZKAVZW
That is the link to the driver download page at samsung, for our phone. Go down to the bottom, and click on drivers, then download the one that pops up. There is only one set. If these are the drivers you have, then lets make sure of the rest
1. Your phone is set to mass storage, or ask on connection (settings/usb)
2. (and you'll have to do this, anyway, after you check your usb settings) make sure debugging mode is checked (settings/applications/development).
3. Try a different usb port
4. check your cord
Also, when you first plug your phone in, after installing the drivers, give it a few minutes. Both when you are fully booted, and when you are in download mode. If you get a pop up saying 'installing device software' wait a few. When it says 'drivers successfully installed', or 'your device is ready to use' then you are good. But, it will take a minute or so to install.
If none of this works, let me know. Chances are you may have a bad cord. Especially if you are like me, and plug and unplug your phone several times throughout the day.
My problem is basically getting my nexus 7 to connect to the pc... This is what I've done. and what happends...
When I first connected it, I got no message at all, and nothing happened, then I changed the cables around, I changed the USB Pports... and by some mysterious wounder I found a combo of pad, port and cable that made my nexus go your connected as MEdia Device... BUT my computer wont see it.. hmm.. changed it to camera mode, and still nothing. Then I turned off USB Debug. Still nothing, but wen I turned it back on, I got the message that I was connected, and I got to install some drivers, and NExus popped up as a camera in windows 8... Started up the nexus toolkit thingy (I love simplicity) And there it popped up.. rebooted to fastboot, and no luck... windows wont recognize the damn driver. And I have done everything I can think of except install linux and try it there... IT wont connect in Fastboot mode, Not a chance... I've tried to unindatll all the drivers, and their files. everything I can think of... I've followed like 20 diffrendt howto s on the same problem, and no luck...
So how would a guy like me go about doing this in linux... is there a tool made for it? Do I need to do it all by commands? Is there a howto?
In my win8 64bit the nexus 7(2012) does show up as a portable device, but MTP works and there's no issue with sending or pulling files. currently it's running stock kitkat 4.4 (KRT16S).
like you I suspect it's a driver issue with windows. If you could locate the device on device manager (try View\Devices by connection and look under PCI Express Root Complex and comb for USB Host Controller\USB Root Hub\Generic USB Hub), delete the entry for Nexus7 and scan for hardware changes again. This forces the system to look for correct driver(s) for your nexus.
Some guides on updating drivers are in fact concerned with the ADB interface, which is needed for USB debugging. In your case, if it's just accessing the internal storage of your Nexus you want to solve, those info may not be relevant.
krrasmuss said:
My problem is basically getting my nexus 7 to connect to the pc... This is what I've done. and what happends...
When I first connected it, I got no message at all, and nothing happened, then I changed the cables around, I changed the USB Pports... and by some mysterious wounder I found a combo of pad, port and cable that made my nexus go your connected as MEdia Device... BUT my computer wont see it.. hmm.. changed it to camera mode, and still nothing. Then I turned off USB Debug. Still nothing, but wen I turned it back on, I got the message that I was connected, and I got to install some drivers, and NExus popped up as a camera in windows 8... Started up the nexus toolkit thingy (I love simplicity) And there it popped up.. rebooted to fastboot, and no luck... windows wont recognize the damn driver. And I have done everything I can think of except install linux and try it there... IT wont connect in Fastboot mode, Not a chance... I've tried to unindatll all the drivers, and their files. everything I can think of... I've followed like 20 diffrendt howto s on the same problem, and no luck...
So how would a guy like me go about doing this in linux... is there a tool made for it? Do I need to do it all by commands? Is there a howto?
Click to expand...
Click to collapse
Installing fresh SDK won't hurt.
holynoob said:
Installing fresh SDK won't hurt.
Click to expand...
Click to collapse
The USB drivers are available in a zip file here: http://developer.android.com/sdk/win-usb.html
and instructions are here:http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
For drivers and devices on your system browse http://www.nirsoft.net/ for the free utilities
DriverView
USBLogView
DevManView
USBDeView
Update
peterk-1 said:
The USB drivers are available in a zip file here: http://developer.android.com/sdk/win-usb.html
and instructions are here:http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
For drivers and devices on your system browse http://www.nirsoft.net/ for the free utilities
DriverView
USBLogView
DevManView
USBDeView
Click to expand...
Click to collapse
Basically I would like to have ¤.¤ installed on my Tablet. Right now I have 4.2.2 SmoothROM installed, and whilst this works for me, I'd like to get the update.
In the past, I used the Toolkit to root and install stuffies... Until the last update to SmoothROM wheres I used GooManager thingy...
When I started this I got the Tablets to connect using PTP whilest in Android, but not in Fastboot mode. So I downloaded the 4.4.kitkat Offisial ROM and tried to install that in recovery, after a full wipe, BUT that ended in me having to install SmoothROM again. And now the Tablet wont connect at all... I have deleted all drives, and reinstalled them... I've tried 3 diffrent Wondows USB driver, but no luck there... I've tried like 5 diffrent USB data cables, in all 4 of my USB ports, on 2 diffrent machines, both win 7 and win 8... AND still no luck... now all the machine says that it cannot identfy the device...
Tomorrow, I will end up installing linux, and try there... At the moment I loathe all things called windows drivers...!!!!
EDIT:
Great news... I found a cable, I havent used in a long time. THis is the original cable that came with the Nexus, and I havent used it in a long time because it had some bad connections. Felt like the plug was loose, but now it made the whole thing work without any problems at all...
So I found the cable, used USBDeView to delete all drivers assossiated with the nexus. plugged it in while in fastboot, and BANG installed. rebooted it, and BANG installed.