Database Info

[Q] Need help getting my T959V connected for flashing/rooting.

Problem: Cannot get my Samsung T959V to connect to the computer in order to flash/root. Always gives the same "USB Device Not Recognized" error when I plug it in to the computer.
My Progress: Before you guys throw this questions out, let me tell you what I have tried so far. I have been trying to get this damn thing connected to the computer for about 3 weeks now. I have sat down on my computer going through the xda forum in detail trying to find an answer. I know the process of flashing and the xda contributors have some great guides to help us along the way, a big thanks to all ur hard work, but no matter what, I cannot get the phone in download mode or get it connected to the computer.
* I have read the Download Mode post and tried all 5 ways without luck.
* Have read all things related to Keis Mini and how it sucks when it comes to the T959V and other ppl have had the same problem.
* Have tried connecting in Keis mode, usb debugging mode but still the same error.
If someone can help me get my phone connected to the computer, I am sure I can take of the rest since everything is available on the SGS4G Bible, thanks for that also.
Is there anything I have missed or not tried yet? Please help. Thanks in advance for anyone who reads this post as it is my first. Usually I don't have to post since all the documentation is always up-to-date and available but this problem is killing me
Additional Information: Bought the phone from a cell-phone store I use to work at. Has Android 2.3.6 on it. Have done the factory reset and tried to get it to connect, no luck. Not sure if it has been flashed before, pretty sure it hasnt but the flashed download mode method didnt work also. Have android-sdk installed and have tried pointing the .inf file to the google usb-drivers in the sdk, no luck. Download both 32-bit and 64-bit drivers for this phone from multiple locations, still no luck trying to connect. Have also tried multiple computers and multiple v9 cables, no luck.

Have you installed the Samsung drivers? You mention google drivers but samsung has it's own. You should be able to find them in the noobs guide to Odin thread. DL mode should work as well regardless of what drivers you have installed. Pull the battery, plug usb into computer, plug phone into usb, hold down BOTH vol + and -, insert battery. I've never not seen that method work.

hechoen said:
Have you installed the Samsung drivers? You mention google drivers but samsung has it's own. You should be able to find them in the noobs guide to Odin thread. DL mode should work as well regardless of what drivers you have installed. Pull the battery, plug usb into computer, plug phone into usb, hold down BOTH vol + and -, insert battery. I've never not seen that method work.
Click to expand...
Click to collapse
Yup tried both 32-bit and 64-bit drivers on multiple computers. Tried the download mode method u said also. Trust me have tried everything I have read about and know, but no luck.

But the phone charges fine? Could be a bad USB port. Or partially bad. Have you tried a jig? If that doesn't work I'd say your hardware is screwed up somewhere.

hechoen said:
But the phone charges fine? Could be a bad USB port. Or partially bad. Have you tried a jig? If that doesn't work I'd say your hardware is screwed up somewhere.
Click to expand...
Click to collapse
Yup it charges fine. Both when I plug it into the wall and the computer. What's a jig? Don't think I have tried that yet. If something can let me know for sure its a hardware problem, then I will stop obsessing over this, hahaha. Thanks for ur help btw.

A jig is a nifty little device that plugs in to your USB port on the phone and then gets you to DL mode. Their mostly used to recvover from bad flashes(like flashing the wrong phones kernel). Here's a link:
http://www.ebay.com/itm/Download-Mode-USB-Jig-Samsung-Omnia-7-Galaxy-S-4G-/250877662279
If your cheap like me or just wanna make it fast here's a guide to making your own.
http://forum.xda-developers.com/showthread.php?t=1604707

hechoen said:
A jig is a nifty little device that plugs in to your USB port on the phone and then gets you to DL mode. Their mostly used to recvover from bad flashes(like flashing the wrong phones kernel). Here's a link:
http://www.ebay.com/itm/Download-Mode-USB-Jig-Samsung-Omnia-7-Galaxy-S-4G-/250877662279
If your cheap like me or just wanna make it fast here's a guide to making your own.
http://forum.xda-developers.com/showthread.php?t=1604707
Click to expand...
Click to collapse
Awesome bro. I will see if I have time to make the jig, if not i will just order it.
Also, is there any way to flash/root without DL mode or USB debugging or using Keis? My recovery mode works but that's all. Was wondering if there was a way i could flash/root from the 'apply update from sdcard' option in the recovery mode?

Seems like a driver error have u tried one of the heimdall one clicks http://forum.xda-developers.com/showthread.php?t=1358498
They will put u back to stock with a modified rooted kernel .
If anything try and manually point to the drivers in device manager. Or download android sdk and use the google drivers ?

rangergiya said:
Also, is there any way to flash/root without DL mode or USB debugging or using Keis? My recovery mode works but that's all. Was wondering if there was a way i could flash/root from the 'apply update from sdcard' option in the recovery mode?
Click to expand...
Click to collapse
There was with Froyo but with GB it's all been put into the kernel. So not that I'm aware of. However one of the GB leaks changed the key mapping of the phone. I forget which one but that might be the issue. Go to settings>about phone>build number and let me know what that says. post the base band as well.

hechoen said:
There was with Froyo but with GB it's all been put into the kernel. So not that I'm aware of. However one of the GB leaks changed the key mapping of the phone. I forget which one but that might be the issue. Go to settings>about phone>build number and let me know what that says. post the base band as well.
Click to expand...
Click to collapse
As requested,
Build number: GINGERBREAD.VUVKJ6
Baseband version: T959VUVKJ6

Well that is the official GB release so now I officially have no idea why you can't get into DL mode. Get the jig and let me know if that works. Good luck.

hechoen said:
Well that is the official GB release so now I officially have no idea why you can't get into DL mode. Get the jig and let me know if that works. Good luck.
Click to expand...
Click to collapse
Will do. Thanks for ur help.
I downloaded the terminal emulator app and tried doing 'reboot download' but says 'operation not permitted,' any way to get around that? Or any other non-button or non-adb way to get into download mode? Other than the jig? Or is it possible to get su privileges on an unrooted device for the 'reboot' command to work in the terminal emulator app?

It's giving you "not permitted" because you don't have root. Have you tried Super One Click to root? If you can get SOC to root it you can use terminal to force DL mode.
If you haven't hears the link.
http://shortfuse.org/
DL 2.3.1. It should come with the android drivers as well. Worth a shot. If it doesn't work it doesn't damage the phone at all.

hechoen said:
It's giving you "not permitted" because you don't have root. Have you tried Super One Click to root? If you can get SOC to root it you can use terminal to force DL mode.
If you haven't hears the link.
http://shortfuse.org/
DL 2.3.1. It should come with the android drivers as well. Worth a shot. If it doesn't work it doesn't damage the phone at all.
Click to expand...
Click to collapse
Im trying it now but for SOC to work, i have to have the proper drivers to get my phone connected. Will see whether the drivers that come with SOC work for my phone.

No luck with the SOC 2.3.1 drivers. They r the same as the android-sdk drivers
Will try the jig. Hope it works.

Have you tried using this DRIVER SWEEPER to remove the drivers?

eollie said:
Have you tried using this DRIVER SWEEPER to remove the drivers?
Click to expand...
Click to collapse
And then what? I've tried to get the phone connected on multiple computers without any luck. Uninstall and reinstall didnt give me any results.

rangergiya said:
And then what? I've tried to get the phone connected on multiple computers without any luck. Uninstall and reinstall didnt give me any results.
Click to expand...
Click to collapse
Im sorry I am having mouse issues that deleted part of my response..
Sometimes a residual driver will not allow you to properly install the drivers. I had a LG driver from my old phone that was conflicting with Samsung driver.
Also this is a new root process. I do not know if it will work or not. But Hell its worth a try right?
http://forum.xda-developers.com/showthread.php?t=1652825&highlight=root

eollie said:
Im sorry I am having mouse issues that deleted part of my response..
Sometimes a residual driver will not allow you to properly install the drivers. I had a LG driver from my old phone that was conflicting with Samsung driver.
Also this is a new root process. I do not know if it will work or not. But Hell its worth a try right?
http://forum.xda-developers.com/showthread.php?t=1652825&highlight=root
Click to expand...
Click to collapse
Thanks for that link. I will try it out and give an update here.

rangergiya said:
No luck with the SOC 2.3.1 drivers. They r the same as the android-sdk drivers
Will try the jig. Hope it works.
Click to expand...
Click to collapse
Just to make sure you had usb debugging and allow non market apss both CHECKED right?

Need help

I relocked my bootloader and tried running a RUU but it keeps telling me that my phone is not connected. I'm using parallels for mac, I installed the drivers and I notice that when i connect the phone it doesn't say "fastboot usb" but when i push volume down is changes yet it still is unable to detect the phone. I installed the htc drivers but when I connect the phone is shows i dont have the drivers for " HTC Remote NDIS based device"
Could this be because im using parallels instead of a full windows pc?
please help, this is my very first android device and im scared I already ruined it

Yeah parallels is touchy. It works in VMware. Make sure in vm settings the usb device for the phone is set to always available to windows. If it is set to ask then it can lose connection.

Ok, Ill give a try.

I still have another problem. When I try to install the htc drivers, I get an error saying device not found. How am I able to install the drivers now?

I found the best way to get the driver installed is to install HTC sync

Thanks for the replies gunnyman, I have one last problem and hopefully theres a fix. I have a low battery and unable to flash the RUU. Is there a fix?

Is there battery actually low? Just shut down the phone and charge it up.

When I plug in the phone, it boot up on its own into fastboot and it says "fastboot ac". Is it charging?

Jaykelso said:
When I plug in the phone, it boot up on its own into fastboot and it says "fastboot ac". Is it charging?
Click to expand...
Click to collapse
Sorry. No idea. Sounds like it.

Fastboot Not Recognized

Ok guys, sorry to start another thread on this but I have been going through thread after thread and searching endlessly for a solution and nothing has worked for me.
I was getting ready to do the S-Off procedures and my device is recognized by computer to transfer files, and adb recognizes the device as well, I was able to get the device ID. Reboot into bootloader and fastboot just hangs there and no fastboot usb. try to enter fastboot command and it just hangs at "waiting for device"
I started going crazy and uninstalled drivers. Installed HTC Sync, (never needed it before). Now when I plug in USB while in Fastboot computer recognizes device but says it is not working properly.
Under device manager > Android USB Devices > (Yellow triangle) My HTC > Device Status ( This device cannot start Code 10), (A request for the USB BOS descriptor failed). Driver version 2.0.7.14. I try to update the driver manually and it says "It appears the right driver is already installed." Tried disabling enabling. Unistalling, plugging back in. Nothing seems to work.
Running Viper 3.2.3
Windows 8 (didnt have the problem before using fastboot)
Sorry for long post. Thanks in advance.

chriscerv90 said:
Ok guys, sorry to start another thread on this but I have been going through thread after thread and searching endlessly for a solution and nothing has worked for me.
I was getting ready to do the S-Off procedures and my device is recognized by computer to transfer files, and adb recognizes the device as well, I was able to get the device ID. Reboot into bootloader and fastboot just hangs there and no fastboot usb. try to enter fastboot command and it just hangs at "waiting for device"
I started going crazy and uninstalled drivers. Installed HTC Sync, (never needed it before). Now when I plug in USB while in Fastboot computer recognizes device but says it is not working properly.
Under device manager > Android USB Devices > (Yellow triangle) My HTC > Device Status ( This device cannot start Code 10), (A request for the USB BOS descriptor failed). Driver version 2.0.7.14. I try to update the driver manually and it says "It appears the right driver is already installed." Tried disabling enabling. Unistalling, plugging back in. Nothing seems to work.
Running Viper 3.2.3
Windows 8 (didnt have the problem before using fastboot)
Sorry for long post. Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2066805
Hope this helps.
AT&T HTC OneX
Android 1.1.1
ViperXL

Venomtester said:
http://forum.xda-developers.com/showthread.php?t=2066805
Hope this helps.
AT&T HTC OneX
Android 1.1.1
ViperXL
Click to expand...
Click to collapse
Thanks for the reply. That linked me to all the threads I went through by searching myself. I was just taking a stab to see if anyone had a new solution. Weird that this just started for me. VERY FRUSTRATING.

Windows XP makes life easier

chriscerv90 said:
Thanks for the reply. That linked me to all the threads I went through by searching myself. I was just taking a stab to see if anyone had a new solution. Weird that this just started for me. VERY FRUSTRATING.
Click to expand...
Click to collapse
Did you try searching resolutions at Microsoft?
http://technet.microsoft.com/en-us/library/cc725873(v=WS.10).aspx
AT&T HTC OneX
Android 4.1.1
ViperXL

Venomtester said:
Did you try searching resolutions at Microsoft?
http://technet.microsoft.com/en-us/library/cc725873(v=WS.10).aspx
AT&T HTC OneX
Android 4.1.1
ViperXL
Click to expand...
Click to collapse
Thanks for the tip lol
I tried similar steps.
I did a fresh install of windows too. I know I am a little obsessive. Still can't get the dang thing to be recognized in fastboot.

chriscerv90 said:
Thanks for the tip lol
I tried similar steps.
I did a fresh install of windows too. I know I am a little obsessive. Still can't get the dang thing to be recognized in fastboot.
Click to expand...
Click to collapse
I know this may sound silly at this point but did you try moving it to a different usb port? I have seen that work before.
AT&T HTC OneX
Android 4.1.1
ViperXL

try using this application if you think your device drivers are dirty but installed correctly for usb devices
USBDeview just uninstall whatever devices you want reinitialized especially since they can change even with rom changes so it is good to clear some old ones out by sorting them based on Last Plug/Unplug Date.

I had to use a different Micro-USB cable to get it work. Try that.

Yeah I actually have tried all those steps. Thanks for the replies guy. I check out that application.
I'm starting to think something is wrong with my HOX
Sent from my HTC One X using xda app-developers app

DvineLord said:
try using this application if you think your device drivers are dirty but installed correctly for usb devices
USBDeview just uninstall whatever devices you want reinitialized especially since they can change even with rom changes so it is good to clear some old ones out by sorting them based on Last Plug/Unplug Date.
Click to expand...
Click to collapse
This FREAKING WORKED!!!!!!!!!! HAHAHA Thanks man ... I've only had 2 hours of sleep trying to fix this stupid problem... I owe you one man. :highfive:

glad you got it fixed, check out his other apps they are life savers and they work how "real" windows apps should work.

I have the same problem
chriscerv90 said:
This FREAKING WORKED!!!!!!!!!! HAHAHA Thanks man ... I've only had 2 hours of sleep trying to fix this stupid problem... I owe you one man. :highfive:
Click to expand...
Click to collapse
I have the the same problem my computer does not recognise the device ( htc one x endeavour) and in fastboot mode it does not work.
pls help
how you solved this ??

abhilashlinge said:
I have the the same problem my computer does not recognise the device ( htc one x endeavour) and in fastboot mode it does not work.
pls help
how you solved this ??
Click to expand...
Click to collapse
If your on Windows 8 problems will occur but there are methods you need to look into. Windows 7 is your ally.
First Uninstalled the drivers for the device using the program in the previous post. Second, make sure your cable is working correctly. Third, make sure you have the correct drivers for you phone on the computer - - HTC Sync causes problems sometimes. Fourth, plug in the phone in while it's on and let the drivers install correctly. Fifth, place the phone in fastboot and let drivers install. Should work.
Remember sometimes you need to restart your computer and try different USB ports. Some users have said 3.0 ports cause problems.
Good luck.
Sent from my SM-N900A using XDA Premium 4 mobile app

chriscerv90 said:
Ok guys, sorry to start another thread on this but I have been going through thread after thread and searching endlessly for a solution and nothing has worked for me.
I was getting ready to do the S-Off procedures and my device is recognized by computer to transfer files, and adb recognizes the device as well, I was able to get the device ID. Reboot into bootloader and fastboot just hangs there and no fastboot usb. try to enter fastboot command and it just hangs at "waiting for device"
I started going crazy and uninstalled drivers. Installed HTC Sync, (never needed it before). Now when I plug in USB while in Fastboot computer recognizes device but says it is not working properly.
Under device manager > Android USB Devices > (Yellow triangle) My HTC > Device Status ( This device cannot start Code 10), (A request for the USB BOS descriptor failed). Driver version 2.0.7.14. I try to update the driver manually and it says "It appears the right driver is already installed." Tried disabling enabling. Unistalling, plugging back in. Nothing seems to work.
Running Viper 3.2.3
Windows 8 (didnt have the problem before using fastboot)
Sorry for long post. Thanks in advance.
Click to expand...
Click to collapse
I ws installing a Ruu zip but process got failed and hboot version changed to 1.54.000 . my device is in now relocked status and bootloader is not reconised by hp envy. adb still showing my device my i lost fastboot mode completely. Any solution there???
I already tried several drivers method. Error is something HTCAND4 in driver events log.

What did u do?

[Q] Unbricked successfully, ADB broken?

Howdy, folks. I recently bricked my tablet thanks to a bad install of CWM, but following Buster's guide I was able to successfully reflash stock firmware and the device runs fine when booted up now.
However, now ADB is not detecting my device. At all. I have tried running the kill-server and start-server commands to see if that would do the trick to no avail. I'm not even receiving an error saying "device not found." Rather, the device listing is left blank whenever I enter the devices command into the command prompt. I can still send commands via fastboot, but I'm concerned that there's something here that I'm missing, or that I have somehow managed to completely bork the motherboard. I have already tried uninstalling and reinstalling the Asus usb drivers, in addition to the ADB drivers/software to no avail.
Does anyone have any suggestions to getting ADB to work for my tablet again? I have scoured the web, particularly these forums, for days looking for an answer, but haven't turned anything up yet. Any help would be greatly appreciated.

Does usb debugging is on?

Graiden05 said:
Does usb debugging is on?
Click to expand...
Click to collapse
Yes, USB debugging is enabled; yes that was the first thing I checked.
Any other ideas?

If You use asus drivers it worth to try universal naked driver.

Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I'll give that a shot this evening.

Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I just installed the naked drivers and tried again, but that didn't work either. Fastboot still works just fine, but I'm still at a complete loss as to how to get adb working again.
Thanks for your help thus far.

Hmm... How windows show tablet when You connect it to PC?

Graiden05 said:
Hmm... How windows show tablet when You connect it to PC?
Click to expand...
Click to collapse
Yeah everything *looks* normal, and appears to be acting normally whenever I have the tablet plugged in. When my tablet is booted up and connected to my pc, I can transfer files to and from with no issue. Also when it's plugged in, there are two different entries under the device manager (one for adb and the other for the tablet itself). It's only when I have my tablet running in bootloader mode that things don't seem to want to work correctly.
I even ran netstat last night to see if there were any programs/services using the same port as adb, and even that turned up nothing. Is it possible that I somehow inadvertently altered the settings on my tablet's motherboard when I installed a bad version of CWM, per my original post?

It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?

Graiden05 said:
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Click to expand...
Click to collapse
It wasn't a problem until I flashed the wrong version of CWM, got stuck in a boot-loop and fixed the problem using fastboot to completely wipe my tablet and start over from scratch.
Edit: I suppose I could try a fresh install of Windows.

Try first remove all drivers and software for tablet. Then install universal naked driver.

Graiden05 said:
Try first remove all drivers and software for tablet. Then install universal naked driver.
Click to expand...
Click to collapse
Update: finally got adb to detect my device. Ended up removing everything Android-related from my desktop and re-downloaded/installed everything, including usb drivers. That did the trick.
Thanks again for the help.

Phone unrecognized in download/recovery

So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.

chaosrde said:
So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.
Click to expand...
Click to collapse
Strange suggestion but try a different pc. My phone isnt recognised when I try to install magisk on my phone on my home pc but it works on my work pc.
I got about 9 different USB ports on my home PC and none work
Also download platform-tools_r29.0.2-windows for fastboot etc.

While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.

Icculus760 said:
While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.
Click to expand...
Click to collapse
I am using the OEM cable, straight out the box. I'm gonna try meddling with it again when I get home and see if I can get it working.

bigAL99 said:
Also download platform-tools_r29.0.2-windows for fastboot etc.
Click to expand...
Click to collapse
Ive done a fair bit of searching but I can't find anywhere to download older version of platform tools, I have the current build 29.0.5.