Database Develop

Brick? Bad new generic cable? Bad port? -- FIXED

Current Scenario:
Phone is stuck at AT&T screen. Can get to download mode. XP cannot installing drivers.
Questions:
Has anyone encountered anything like this? I know some people report issue with some data cables not being able to connect. But I am surprised I can get to download mode with it so am questioning if the cable could be the issue. Could it be a bad port? Since my original cable has gone bad could it have messed up my port? I saw a posts about this but no follow up.
Notes:
Cognition 2.3b6
USB Drivers from (http://forum.xda-developers.com/showthread.php?t=731989) I've obviously have been able to connect prior to these issues to upgrade my ROM.
Kies and Kies Mini were previously installed. I since deleted since having these issues.
Uninstalled iTunes as suggested in other posts.
History:
My phone is stuck at the AT&T boot screen. Using my original Samsung cable I could not get my phone into download mode. So I went out and made the jig to get it into download mode. This worked but win XP won't recognize the phone once I put my original cable in. I realized that my original cable might be internally frayed, so I went out and bought a generic USB cable. Now I can get my phone into download mode (without using the jig) which shows that my original cable has been damaged at some point. This would also explain that when my phone is off and I plugged it in using the old cable the phone would turn on.
Anyway, using this new generic cable, XP/ODIN won't recognize my phone. When trying to put it in download mode (two button/insert cable/no SIM/no SD), I see XP popup: Found New Hardware, USB device, Samsung USB Composite Device, USB device, Samsung USB Composite Device, then get the Found New Hardware Wizard with message Cannot Install the Hardware, problem installing this hardware: USB Device.
Thanks in advance.

Oh and not sure if it matters but I cannot get into recover mode either. Cannot get past AT&T boot screen.

Um... make sure you remove all traces of the Kies stuff.
Re-install USB drivers over the top of the existing ones.
I might suggest buying a "sumsung" cable from an AT&T dealer.
AND - make sure your using the USB port that is on your mobo - apparently it makes a difference.
I had my phone in a "bricked" state and had to re-install drivers on my Win7 box. it found the phone and recognized it enough for ODIN to start up.
Also.... to find out if the phone is being recognized - I would recommend d/l'ing the Android SDK and doing the ADB command - adb devices and see what pops up.
Heh - last thing.. please say you had the phone in "USB Debugging" mode before things went south?

Here's a link to a thread containing another variant of the Captivate USB Drivers:
http://androidforums.com/captivate-.../123644-captivate-usb-drivers-links-here.html
I can't remember which I used, but if the above suggestions don't work for you, it won't hurt to try these!
And for what it's worth, I don't believe the problem to be within the USB cable. I use everything EXCEPT the Samsung USB cable. Anything from Monoprice.com cables, to my old Blackberry cable... A MicroUSB cable is just that...generic or not. As long as it's a 5 pin cable, you should be good.

@avgjoegeek
avgjoegeek said:
Um... make sure you remove all traces of the Kies stuff.
Click to expand...
Click to collapse
Uninstalled and deleted program files/samsung/kies*. Would I need to look through registry as well?
Re-install USB drivers over the top of the existing ones.
Click to expand...
Click to collapse
Done. Multiple times. Even tried drivers from Samsung support site. Currently I'm using the ones from the Stock ODIN thread. (Uninstalled all. Rebooted. Installed drivers from ODIN thread. Rebooted.)
I might suggest buying a "sumsung" cable from an AT&T dealer
Click to expand...
Click to collapse
Called AT&T said they didn't carry any data/sync USB cables. Which I found was odd. Have one coming from Amazon soon that looks-like and is listed to be OEM.
AND - make sure your using the USB port that is on your mobo - apparently it makes a difference.
Click to expand...
Click to collapse
Tried all of them.
I had my phone in a "bricked" state and had to re-install drivers on my Win7 box. it found the phone and recognized it enough for ODIN to start up.
Also.... to find out if the phone is being recognized - I would recommend d/l'ing the Android SDK and doing the ADB command - adb devices and see what pops up.
Click to expand...
Click to collapse
Returns: List of devices attached (nothing else)
Heh - last thing.. please say you had the phone in "USB Debugging" mode before things went south?
Click to expand...
Click to collapse
Upgraded to Cog v2.3b6 before things went south. I normally keep USB Debugging mode as defaulted. Wondering if the update would have caused it to be unchecked. I think I checked that once and rarely make changes. Either way, are you suggesting that if that option is not set that I am pretty much hosed?
@norcal einstein: I will have to try your suggestion from a new machine. My work just locked (McAfee) our machines due to virus going around.

Hi there ... I've run into this similar problem before.. The link you posted's instructions:
"plug usb then open odin"
NO!!!!
#1 odin oneclick must be open before you connect your phone. (and i didnt see in previous posts that you did this?)
Here's the rest....
From a soft-bricked state the Samsung I897 displays a "gadget" screen involving
icons of a phone + exclamation + computer. It is still possible to boot into download mode from this point (which is before the att logo) there your phone can.
Apparently you've been able to get into download mode .
When my phone was soft-bricked and I finally figured out how to put it in download mode I got the "gadget serial device driver not found" bs. I had already opened odin-oneclick and it said "added". So I tried and it worked.
There is no better source for drivers than the manufacturer. So i suggest using those drivers instead. Also the usb port on a captivate IS a generic usb plug.... it's just offset to the side a little bit to add STYLE.

Thanks to everyone that replied. I just want to provide a my resolution for others that might be search for similar issues.
My Captivate is now back up and running. Loaded with Cog2.3b6.
The generic cable proved not to be the issue. I know some people reported having issues with cables but I believe as long as the cable is labeled to be a sync or data cable you should be fine. Avoid the charger cables as it will be just that - a charger cable only.
The jig worked like a charm to get to download mode. Just connect the two leads (4 and 5; closest to the center of the phone) using 301k resistors worked. I used 3x100k and 1x1k. Although, I later learned that my OEM cable went bad on me and just getting a new cable I can get into download mode fine. If some of you are having issues might want to consider keeping a extra cable just to rule out cable issues before trying out the jig. The jig IS very easy to do but finding a micro-b USB plug or adapter that gives easy access to the 4 and 5 leads might be hard.
Out of ideas what was wrong (being stuck at AT&T boot screen, being able to get to download mode, my laptop not being able to detect my phone) I borrowed a laptop running Vista. This worked! Vista and ODIN detected my phone and I was able to get back to stock.
So still not sure what's wrong with MY laptop. Hoping to get it resolved by the time they get the AT&T Froyo update out. But I am very much guessing our tech department tightening up McAfee restrictions (like being able to download exe(cutables) might be the culprit. I will have them remove the restrictions so I can re-install the USB drivers and see if that works.
If you are looking for instructions for how to get download / ODIN working, all the instructions from all the many threads work. I will not repeat those instructions here. But a couple notes: I didn't find any difference with leaving SIM card in or out. Might be best to just leave it out. I've tried both inserting cable last and inserting battery last. Both ways works. So if you can't get one way working chances are you probably won't be able to get it working the other way either. I personally use the battery first, both volume buttons then cable. Once I had to wait 10 mins before getting it to work. That was probably once in about 10 times I've done download mode.
And BIKERBOY8989 is correct, if you can get to the AT&T boot screen chances are you SHOULD be able to get into download mode. Might want to check cables and/or try on another machine. As I mentioned already.
Good luck!!!

[Q] Modem / COM port Access on G1

Is there a way to get a G1 into a diagnostic mode so the Qualcomm modem will show up over USB to a PC. I've tried various USB HTC drivers, including ones which include COM port over USB drivers (namely sync/diagnostic stuff for the Hero) but haven't had any luck getting anything but ADB composite device to show up.
I'm sure I'm getting the drivers to install, as the composite device changes its name depending on where the USB/ADB driver came.
Is there something I am missing here?

Thanks
I'm not steady handed enough to try your ribbon cable approach, though I think for a total investment of about $12 with shipping I can have a full homebrew cable. Much cheaper than the suggested component parts are by themselves.
I will update if the following work, I'm going off of supposition here:
This should be sufficient for getting the ExtUSB connector. Great part in my opinion is it already has wires going to a break out box.
www_amazon_com/HTC-Multifunction-Adapter-T-Mobile-Shadow/dp/B001QD3MQE/ref=lh_ni_t_
For the 3.3v CMOS compliant serial cable, I'm going to try this:
www_amazon_com/Data-Cable-Nokia-3585-CA-42/dp/B000BI4HQY/ref=pd_cp_cps_1
(replace _ in www_amazon_com with .)
Thanks for getting me started down the right road Xsite_01.
I know serial interfacing with most HTC phones isn't a top priority with ADB/ActiveSync (and JTAG for the hardcore), but someone should get Xsite's links added to the Wiki.

Xsite_01 said:
Diagnostic mode is entered from blue led mode using htc extusb to serial cable.
Qualcomm modem will show but with serial cable not regular usb. Here is the link on how to build one. If you need info on how to build it from home parts click here to view my tutorial, or contact me.
You acces serial port using serial cable and putty. Also you can acces the phone using PSAS/QMAT, Link 1, Link 2 for how to do it. But be wery careful accesing this, some command might damage the phone. I suggest that you read more about it before atempting anything.
You should not atempt this with regular usb cable becouse you can send the phone in some boot mode that can only be accessed using serial cable and you will be stuck(until you build serial cable).
Click to expand...
Click to collapse
I would like to communicate with the HTC Dream (G1) using the (qualcomm) diagnostic mode. By this, I mean the one that the QPST/QXDM softwares are using to talk to the baseband (radio). As I understand, it is possible to build the serial to USB cable (using the ExtUSB adapter needed for the G1) to do so. I would really appreciate if someone could confirm that he tested that for this purpose. I tried to build one by myself (using your instructables tutorial, great by the way, thanks Xsite_01 !) but did not managed to use it in diagnostic mode (neither in other mode actually, I may have broken some part of the chips so I would need to double check what I did and/or rebuy components to try again. The procedure is not difficult by itself, it is just the soldering pins that are really small...).
What I tried is to go to fastboot mode (default bootloader mode for the G1), issue the "fastboot oem rtask c" command (using the HTC standard USB cable). The command never returns so I disconnected it and plugged the serial cable (the one I made) but I did not see any diagnostic mode.
To compare, I managed to use the diagnostic mode on the HTC Desire Z using the following procedure:
* issue the "fastboot oem rtask c". The command returns an error but it is ok, it is because it gave the handling of the USB content to AT interpreter of the baseband
* issue the AT$QCDMG command to the AT interpreter of the baseband. You now get the diagnostic mode.
If someone has some hints, don't hesitate. I will come back as soon as it is working...

P9 eMMC data recovery?

I am trying to recover files from the built-in (32GB) eMMC of a water damaged Huawai P9 (motherboard is corroded and no longer boots..). I'd like to somehow create a logical dump of the contained file system preferably using the least intusive method suitable for the task.
(unfortunately I am not allowed to link to the photo here.. so you'll have to manually patch the respective URL: www-wothke-ch*p9*motherboard.jpg )
Looking at the schematics ("14. eMMc AND LpDDR3") I see that various eMMC related test points are exposed on the PCB (i.e. DAT0, CLK, VSP1, VSP2, VSP3, VSP4) and I might be able to directly patch into those, to directly connect to some SD adapter (like this one: %&&ç - unfortunately I am not allowed to post the link - but you can google for "dumping-the-emmc-nand-on-the-nintendo-switch").. eventhough those pads are terribly small and I guess I'd still have to find CMD, 1v8 & 3v0 somewhere else on the PCB. however I have no experience if the remaining stuff on the PCB might just interfere too much for a respective patch to actually work.. any thoughts? Would I rather need to desolder the eMMC chip and to directly connect to the SD adapter?
Is Huawai actually using the on-chip (eMMC) controller or are they using some separate controller, so that using the on-chip one would not actually recover the logical image (if the on-chip controller was even functional and not some cheaper defective version that Huawai might be sourcing to save money - like those 1$ eMMC/SD adapters that can be found on aliexpress)?
The phone supposedly was *not* password protected. Does this automatically mean that the data on the eMMC is not encrypted or does Huawai use some kind of additional built-in/proprietary encryption scheme?
I found the JTAG pads on the PCB but if I understand it correctly those would at best allow me to recover a physical dump. So I'd need addtional hardware to even connect to those and then some expensive analyzer software to transfrom the physical dump to the logical image that I actually need... right?
There are also some ISP related test points exposed on the PCB.. but I guess using those (if they even still work on the damaged board )would lead to situation similar to the JTAG one, right?
Anything I have missed? Any recommendations?

USB data jumper for SM-G110B - Galaxy Pocket 2 Duos

Hello,
I have a Galaxy SM-G110B, or Galaxy Pocket galaxy 2 duos that is:
1- Password locked;
2- Touchscreen not working;
3- Not recognized by PC if connected by usb;
4- No OTG support.
I have data like PRICELESS photos and videos of my engagement that I CAN'T ADMIT TO LOSE.
I would like to try 2 options:
A) Try to recover the touchscreen;
B) Try to recover the USB data connection.
I have an electronics degree and have already made repairs on SMD components without problems.
However:
1st - All troubleshooting tests related to the touchscreen (according to the service manual of the device), show everything normal (tests of tension of some components and of the module's charge and even replacement of the complete module).
2nd - I can not find jumper schemes for the data pins of the USB connector that work.
I need a good person to enlighten me with:
* a jumper scheme of the USB connector data pins THAT WORKS,
or
* more tests for touchscreen
or
* a way to recover data from the internal memory in any way, via hardware or via device's stock recovery.
I'll be absurdly grateful !!!
I'll answer any question if it helps.
Thanks in advance!!!

Surely you already thrown the phone to the trash, but I'll post if anyone in the future needs this (not so useful though)
A "common" way for recovering data on such cases is to just replace the eMMC of another (same model) phone with the one which has the data. A funnier way would be connect the eMMC into a box which supports it (most of them should do).
Oh, and you can also flash CWM, make an script which copies the /data partition into a SD, flash it using volume buttons and GG ez (this all asumming USB works on flash mode or you already have cwm lol)

what fastboot cable should i buy?

I have a soho device that i just updated from 3.2.5 all the way to 4.5.5.3 but one by one (not sure how many times) and now it runs so slow and is constantly rebooting itself and freezing... Maybe I did something wrong but I just connected it to wifi and click on search + update until it was on the latest version (it rebooted many times while downloading the different updates).
So I was trying to flash TWRP but I wasn't able to enter in fastboot mode so I started searching and reading and it looks like these devices need a special cable (pin 1 shorted to 4...). I could try to make my own but I just saw fastboot cables in ebay for as low as $2.37, my question is: why does it say it only works for motorola devices when a fastboot/factory/etc cable is just shorting pin 1 to 4?
Thanks, and excuse my ignorance