yashsingh1/xdaforums huggingface dataset:
[Fascinate Q&A, Help & Troubleshooting] doctorslack:
Solution for this issue. Running out of options.

I have a Verizon fascinate,

hardware version i500.04,

firmware 2.1 update1,

build sch-i500.di01 ( i tried this with dl09 as well ).

When I check the box to see unknown qpst will see the ports but it will not see a phone on it. I have also searched a variety of different forums and have found other people with this issue but no resolutions other then to start with usb connected. Diagnostic mode is enabled and so is usb debugging. I have tried a variety of different combinations of settings with no luck.

Is there another solution for this issue other then booting with qpst and usb cable. Currently I have tried qpst with the following.

1: installing Samsung_Mobile_USB_Driver_V1.3.550.0_SCH-i500_Fascinate and rebooting.

2: installing SAMSUNG_USB_Driver_for_Mobile_Phones_x86.msi and rebooting

3: removing com ports and modem and reinstalling in every way i know how to.

4: used odin to flash back to dl01

5: Taken this to a fresh computer and installed only the fascinate drivers and qpst with no luck.

Any help would be greatly appreciated.
[Fascinate Q&A, Help & Troubleshooting] dandog96:
Does rebooting the phone with QPST on help? It doesn't for me. Im on the verge of giving up.
[Fascinate Q&A, Help & Troubleshooting] garywojdan81:
I know this may sound stupid but do you have debugging on and dial up networking checked? Sorry if this is painfully obvious but I've found that most most of my troubles have come from details that I might've missed. Also, the reboot with the usb connected & qpst on is what did the trick for me.
[Fascinate Q&A, Help & Troubleshooting] Insomnisoul:
Are you saying to disable those or make sure their enabled. I'm looking into performing the steps to get the work around for free mobile hotspots myself. Still doing a lot of reading as I'm new to Modding my phone but have learned a lot in the few days I've been teaching myself and was amazed at how easy a lot of this is especially with great guides on these forums and others.
[Fascinate Q&A, Help & Troubleshooting] dandog96:
Yes, lol. I've enabled diagnostic mode through dial up networking, and even debugging. I've also tried diagnostic mode through **usbui in the dialer, no luck. Right now I have to use a program to update my prl, because I need to update the prl to a cricket one. Maybe my problem is that the phone is not activated? What I mean by that is in order to even use the phone, I have to enter a code into the emergency dialer that allows me to use the phone w/o activation. I just don't know. My problems started when I used Odin to flash my first rom, Super Clean. But I messed up, and installed the DJ05 rom onto DI01. But since then I have used adrenalynes stock rom to restore, so that shouldn't be a problem. :confused:
[Fascinate Q&A, Help & Troubleshooting] doctorslack:
Yes I have dial up enabled and usb debugging enabled. This worked one day and now qpst will not see the phone. it sees the ports but not the phone. I am however able to use odin to flash it but that hasn't seemed to help either.

I also tried the **usbui and verified uart mode was set. The thing is this worked one day and just refused to the next. Nothing else is visible wrong with the phone. At this time I have a pretty expensive paperweight unless I want to switch to Verizon.

It seems dandog96 and I have exactly the same problem and have tried pretty much the same solutions to no avail.

Thank you for your time.
[Fascinate Q&A, Help & Troubleshooting] doctorslack:
OK i solved it!!!! ( well for me anyways. )

Do this.

1: dial **33284

2: Enter 000000 for spc

3: Port map and make sure you have HFK, DIAG set and NOT HFK, NULL.

There are some other handy options in those menus but I did this and relaunched qpst and added the ports and my phone was found!!!!

Please let me know if this works for you.
[Fascinate Q&A, Help & Troubleshooting] dandog96:
thank you so much!!!! I owe you so much!!! How did u out. You are a hero
[Fascinate Q&A, Help & Troubleshooting] doctorslack:
Your welcome, I'm glad that helped. I'm also glad I can finally contribute back a little bit. I know I sure have gotten a lot from other peoples hard work from this forum.

I figured it out by playing around in hidden menus for a day or so. I saw the port mapping and got lucky. I think that the software you and I are using somehow corrupted that bit when we saved our nv data. Anyways at least we have a solution.

Thank you.
[Fascinate Q&A, Help & Troubleshooting] akaine2001:
+1 for the helpfulness... I almost paid 70 bux just to get my two fascinates flashed to cricket... hopefully this will work so my computer will see the phone now
[Fascinate Q&A, Help & Troubleshooting] flip_guy69:
Thanks a lot!!! I had a feeling it was just a setting in the phone. I completely forgot about **33284.
[Fascinate Q&A, Help & Troubleshooting] pahlevy:
this might be old stuff but i'm very helped by your solution... finally able to connect on qpst... great stuff dude...
[Captivate Q&A, Help & Troubleshooting] jbwray:
Phone is ATT captivate SGH-I897 1008

Had my phone for 4 months or so, most of the time with cognition 2.x on it. Tried to update to 3.02 yesterday, and it had an error in the middle, left me at a recovery screen of sorts, and I chose to reboot from the possible selections. It got stuck on the ATT worldcom splash screen.

I tried several things. First, I tried to boot into recovery mode (vol up+power, then release) stays on splash screen. However, in this mode, if I connect my phone via USB, an adb devices command shows as connected. From there I tried both an adb reboot recovery, and adb reboot download command. The adb reboot recovery reboots into the worldcom splash screen just like the key combo does. I can't recall what the download option did, though I think it worked.

Secondly, I realized I could reliably get the phone into download mode, so I decided I would try the download mode, and restore to stock. I found an ODIN on the seminal ODIN thread, downloaded it, and started it up. Put the phone into download mode (hold vol + and vol -, plug in the usb) and that worked fine, however, ODIN doesn't see my phone. I left the phone in this mode for a couple hours just to make sure, and tried disconnecting, and reconnecting, and initialized the procedure from the beginning several times -- no go.

So, I am stuck, and coming to the experts. Hopefully, someone has some good suggestions. I was unable to find someone in a similar predicament, so maybe I am SOL.

Thanks in advance for any help.

UPDATE:

I rebooted my laptop (windows XP) and when I plugged in my phone, it saw "new" hardware and the name of the hardware it sees is "gadget serial." This might explain, if it is not initializing the right drivers why ODIN can't see the phone. The only problem is I don't have any clue how to redirect it to see the right hardware now.

Success Update

After reading the seminal ODIN thread a bit more careful, I came across someone who had similar issues with the gadget serial device. Apparently the drivers I got (I think from the Samsung site) are not good enough to cover that aspect of use. I installed with the drivers from links on the ODIN post and my phone was recognized! As I type, I am installing back to stock.

Thanks everyone for their efforts, and I hope my experience could be useful.
[Captivate Q&A, Help & Troubleshooting] mcord11758:
Desk top or laptop, have you tried all the ports
[Captivate Q&A, Help & Troubleshooting] trekie86:
I would test to see if adb recognizes your device first during normal operations. I'd that doesn't work, your usb port may not have enough power or you have a bad usb cable. I think adb can also restart right into download mode but check around first.
[Captivate Q&A, Help & Troubleshooting] jbwray:
I have tried on my laptop mostly. But I did a cursory try on a desktop as well (the desktop has the drivers installed)
[Captivate Q&A, Help & Troubleshooting] jbwray:
I tried two differing cables, both of good quality. One was the cable that came with the phone, the other was a mini-usb cable with a micro adapter. Neither worked. I can't do normal operations right now (that I know of), seeing how the phone is in a bad state.
[Captivate Q&A, Help & Troubleshooting] mcord11758:
Use rear usb ports on desktop. Make sure you are using original oem cord

Have you used odin before
[Captivate Q&A, Help & Troubleshooting] trekie86:
Sorry, didn't read your first post close enough. I'm not sure what you can do, someone suggested the battery pull method in another thread, but that was just to get their phone in Download mode. It had nothing to do with ODIN after it was in download mode. Hopefully someone will have a suggestion for you. Good luck.
[Captivate Q&A, Help & Troubleshooting] Phateless:
I'm having a similar issue except that odin sees the phone when booted into the rom, which I find odd.

Would you be so kind as to link the drivers?
[G Tablet General] stanglx:
1. Install Sun JRE and SDK

Unfortunately Ubuntu no longer hosts the SUN SDK/JRE so you will need to obtain this from an alternate source:

Run these commands:

sudo add-apt-repository ppa:sun-java-community-team/sun-java6

sudo apt-get update

sudo apt-get install sun-java6

2. Define your JAVA HOME and PATH:

Edit your .bashrc

Run this command:

sudo gedit $HOME/.bashrc

Add these lines to your .bashrc. Please ensure where you installed the Java libraries and your android sdk. The below reflects default installation directories. (Note last line that includes the Android SDK. You can add this now and install the SDK later. Just make sure if you change the default installation directory that you update your .bashrc file)

export JAVA_HOME="/usr/lib/jvm/java-6-sun-1.6.0.22;"

export PATH=$PATH:$JAVA_HOME/bin

export PATH=$PATH:$HOME"/android-sdk-linux_86/platform-tools"

Run this command to reload your .bashrc:

source ~/.bashrc

3. Install Android SDK:

Goto http://developer.android.com/sdk/index.html

Extract and Install By default, the SDK files are unpacked into a directory named android-sdk-<machine-platform> under your HOME directory.

Navigate to the Android Manager and launch:

cd ~/android-sdk-linux_86/tools

./android update sdk

This will automatically run the android manager and add/update the SDK. I typically install all the packages (for development) but typically for ADB connectivity all you need is the Android SDK Tools and Platform Tools. ADB will not be working properly until you configure the USB driver for the tablet. Thats next.

4. Configure USB Driver

We need to modify your device rules:

sudo gedit /etc/udev/rules.d/99-android.rules

Then, paste the following line into the file 99-android.rules file

SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", SYMLINK+="android_adb", ODE="0666" GROUP="plugdev"

Save and Close gedit (or any other text editor)

Restart the device manager:

sudo restart udev

Launch adb:

adb kill-server

nohup adb start-server

adb devices

If you see your device your done... PM me if you have any questions...
[G Tablet General] agodom:
Thanks, I will try this when I get home.:p
[G Tablet General] guisar:
One additional step is needed I believe in order to get adb (aka platform tools). When you start android to test it in your second step, launch it with : ./android update sdk. When the UI starts you'll see an option to download and install Android SDK Tools revision 8 (as of 22 Jan). Click this and it will download and install the platform tools including adb referenced in the rest of the excellent HOWTO.
[G Tablet General] stanglx:
Added.. Thanks! I took some steps for granted as I did it from memory...
[G Tablet General] tekrhino:
Questions about Ubuntu

Is it possible to install Ubuntu onto a W7 machine with a partitioned HD to develop apps and Roms?

Or would it be better to install Ubu on a VM?

Is this the correct thread for this? If not, sorry.

tia.
[G Tablet General] stanglx:
Yes it is possible..either approach will work. All my development environments are vm as I move between various machines. Vms give portability...now a days as long as your running a multicore machine with enough ram, performance is not an issue.
[G Tablet General] TheNinjaMan:
Thanks for this.

A couple of changes I had to make on my system (ubuntu 10.10)

I had to remove the ; at the end of the first export and had to add x on the last export to look like this.

export JAVA_HOME="/usr/lib/jvm/java-6-sun-1.6.0.22"

export PATH=$PATH:$JAVA_HOME/bin

export PATH=$PATH:$HOME"/android-sdk-linux_x86/platform-tools"
[G Tablet General] nzaw4:
I've used adb before in windows, but ohh man, im having some issues with ubuntu...

so i just tried the java home part where i edit the bash file. Not sure if this is supposed to happen....

after i edit the file, i get this in terminal:

----------------

Also,

would this be the correct location to add that command?

alias imdb-up='find ~Videos* -type f | while read -r line ; do imdb-thumbnailer -u "$line" ; done'

export JAVA_HOME="/usr/lib/jvm/java-6-sun-1.6.0.22"

export PATH=$PATH:$JAVA_HOME/bin

export PATH=$PATH:$HOME"/android-sdk-linux_x86/platform-tools"

and when i try to goto /platform-tools dir, i see abd listed when i ls, but when i type adb i get this :

I hope the rest not in bold for the bash file is what it should look like... i kinda messed up while copying the code and wipe it........ anyone chime it would be awesome. i am a linux Noob.. i just switched over from windows 7 a this weekend.

thanks for any help!
[G Tablet General] nzaw4:
err, figured it out! wrong dir... sorry for the noobness, im a command line virgin

:P

one last question, so when i pull up the :

sudo gedit /etc/udev/rules.d/99-android.rules

is it supposed to be blank in the text editor?

also, now since i got adb up and running, i cannot get connection to device..

g@g-N80Vm:~/Downloads/android-sdk-linux_x86/platform-tools$ adb push flash_image /data/local/bin/flash_image

error: device not found

its in download mode.. also tried via USB when it booted, and was not detected also..
[G Tablet General] stanglx:
Yes your creating a new file...so it will be empty

What did it say when you type in adb devices at the command?

Did you first the adb srver? adb start-server
[G Tablet General] nzaw4:
Yea, i started a new ADB server,

g@g-N80Vm:~/Downloads/android-sdk-linux_x86/platform-tools$ sudo restart udev

udev start/running, process 6665

g@g-N80Vm:~/Downloads/android-sdk-linux_x86/platform-tools$ adb kill-server

g@g-N80Vm:~/Downloads/android-sdk-linux_x86/platform-tools$ nohup adb start-server

nohup: ignoring input and appending output to `nohup.out'

g@g-N80Vm:~/Downloads/android-sdk-linux_x86/platform-tools$ adb devices

List of devices attached

g@g-N80Vm:~/Downloads/android-sdk-linux_x86/platform-tools$
[G Tablet General] thebadfrog:
g@g-N80Vm:~/Downloads/android-sdk-linux_x86/platform-tools$ adb kill-server

g@g-N80Vm:~/Downloads/android-sdk-linux_x86/platform-tools$ sudo ./adb start-server
[G Tablet General] iWeasel410:
Just a quick tip since I just did this with Ubuntu 10.10 and VMWare:

To run adb without have to ./adb every time, execute the following:

sudo cp ~/android-sdk-linux_x86/tools/adb /usr/bin

sudo chmod +x /usr/bin/adb
[G Tablet General] the3dman:
Here is a much easier way for those who do not want the whole sdk and just want ADB. With this method there is no reason to modify or add rules for your device. You must have usb debugging enabled for this to work. I found a glitch in tnt lite where when you have usb debugging checked it is not actually on, I had to plug in my usb then uncheck usb debugging then re-check it and it worked fine.

(This Guide assumes you do not have ADB installed)

1) open the terminal and type: wget dl.google.com/android/android-sdk_r07-linux_x86.tgz (Downloads The SDK with ADB)

2) Then type: tar xvfz android-sdk_r07-linux_x86.tgz && cd android-sdk-linux_x86 (Extracts the archive)

3) After that type: sudo mv tools /usr/local/share/android-tools (Moves the sdk tools to your local system folder)

4) Now type: sudo ln -s /usr/local/share/android-tools/adb /usr/local/bin/ (Makes a symbolic link to the adb executable)

5) Then type: sudo adb devices (This will start the adb server and search for connected devices)

You should now see this in your terminal:

List of devices attached

171440424240f1d7	device

Everytime you stop the adb server or restart your session if you wish to open adb again you will need to repeat step 5 or type: sudo adb start-server in the terminal.
[G Tablet General] dantrevino:
minor nit

Sun's Java is hosted in the Partner repo. You can enable the partner repository in the software center and wont need the ppa install.

Thx for the guide.

dan@chaos:~$ apt-cache show sun-java6-jdk
Package: sun-java6-jdk
Status: install ok installed
Priority: optional
Section: partner/java
[G Tablet General] rajeevvp:
Stanglx,

There is a minor typo in your first post. In step 4.,Configure USB Driver

the line:

SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", SYMLINK+="android_adb", ODE="0666" GROUP="plugdev"

should actually be:

SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", SYMLINK+="android_adb", MODE="0666", GROUP="plugdev"

ie. MODE is misspelled.

Some additional hints that you might find useful.

You don't need to restart udev to get it to recognize the new rule. You can use this command instead to reload the new rule:

sudo udevadm control --reload-rules

Here's a script I use to connect to my gTablet which you might find useful. Of course, you'll have to change the PATHs to suit the locations of your java and adb:

PATH=$PATH:/opt/java/bin
PATH=$PATH:/mnt-system/android/android-sdk-linux_x86/platform-tools
PATH=$PATH:/mnt-system/android/android-sdk-linux_x86/tools
PATH=$PATH:/mnt-system/android/toolchain/bin
export PATH

FILE=/etc/udev/rules.d/99-android.rules
RULE='SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", SYMLINK+="android_adb", MODE="0666", GROUP="plugdev"'

if [[ ! -f $FILE ]]
then sudo sh -c "echo '$RULE' >$FILE"
sudo chown root.root $FILE
sudo chmod 600 $FILE
sudo udevadm control --reload-rules
fi

adb -d forward tcp:4444 tcp:23
adb -d shell 'exec /system/xbin/telnetd -F -b 127.0.0.1 -l /system/xbin/ash' &
sleep 1
telnet localhost 4444
adb kill-server

I run the above command and it telnets me into the gTablet via a dynamically run adb shell. This way, I have command line editing, I can run full-screen programs like less and vim (in CM7), and, finally, when I quit telnet, everything is shut down cleanly.

One thing: You need a version of busybox which has the telnetd applet compiled into it for the shell script to work. If you don't compile busybox yourself, just install JRummy16's "BusyBox Installer" from the Market and select v1.19 (the beta version) as the version to be installed.
[G Tablet General] Lloir:
I LOVE YOU DUDE!!!!!! been trying for 3days getting ADB working on 10.10 my google foo had failed then came across this, your awesome nice one dude
[G Tablet General] mukptl:
thanks

i was unable to install from ppa but from software center installed
[G Tablet General] sdnick484:
Big thanks for the instructions; I also wanted to post to confirm that these instructions without much modifications on Gentoo.
[G Tablet General] Bhups:
Does anyone know if I can do this with Fedora?

I cannot see my device when I run adb devices.

Also, is it worth working on Fedora if I want do dev work for Android or is Ubuntu better designed for this?
[G Tablet General] rajeevvp:
The distribution you use shouldn't matter. Try:

sudo adb devices

to see if its just an insufficient permissions problem.

There shouldn't be too much of a difference between the two.
[EVO 4G Q&A, Help & Troubleshooting] thekingofmean:
I find it hard to hold the phone steady and tap the onscreen shutter.
[EVO 4G Q&A, Help & Troubleshooting] polkadots:
Vignette, which is about the best camera app out there - a must have - can do this. Though, pressing down on a button would cause more shaking than tapping the screen, IMO.
[HTC Aria Q&A, Help & Troubleshooting] vicmora5:
I want a launcher that I can have the option to hide or remove the dock and icons so I can place a widget in that area is there any such option in launcherpro? Or do I have to get something else.
[HTC Aria Q&A, Help & Troubleshooting] CallMeAria:
Adw has this option. launcher pro does not.
[HTC Aria Q&A, Help & Troubleshooting] zedbra:
yes, and ADW Ex has even more customization. definately worth a few dollars:)
[HTC Aria Q&A, Help & Troubleshooting] vicmora5:
Alright I found the setting (:

Is there any way to have a shortcut or something that would pull up the app catalog without having the dock?

The only way I could do it was by enabling one icon but that defeats the purpose of me doing this since Im trying not to have any icons on the bottom of the screen where the dock is so I can make my own shortcut with minimalistic text
[HTC Aria Q&A, Help & Troubleshooting] CallMeAria:
You should be able to set that as a swype gesture in the adw settings. Or set the home button to open close the app drawer.
[HTC Aria Q&A, Help & Troubleshooting] vicmora5:
Yeah I actually figured out something I was doing wrong in trying to get the look. It wasn't minimalistic text it was actually a dock and with launcher pro i just made some blank icons and set swipe feautures and it came out how I wanted. Thanks
[Captivate Q&A, Help & Troubleshooting] yentlequible:
Recently, I had a very long discussion with some helpful users regarding how my market disappeared in the Android Themes section. After never recovering my stock market application, I finally just flashed to the cognition rom that is built for 2.1.

This was a huge risk for me because for some reason my phone is not found in Odin when it is in download mode. I have already tried everything to get it recognized, but nothing was able to get it recognized. If I were to brick my phone, I don't think I could fix it. I soft bricked it during the problem with the Market, but luckily I was able to get the phone working again through recovery.

I am thinking of flashing to the new cognition so that I can get my phone running on a 2.2 based rom and then quit flashing until I get a better phone or figure out my Odin problems.

I just have a few questions. I know a lot of people recommend flashing to stock first (which I can't do), while others don't flash stock. I should be able to just disable Voodoo and hopefully flash successfully to a new rom, correct? Also, what are the chances of a permanent brick? As long as I could get into recovery I could probably get the phone back up again without the use of Odin, right?
[Captivate Q&A, Help & Troubleshooting] lrs421:
Well, first, this belongs in Q&A :) but...

It sounds like you have nothing to lose at this point. A lot of people flash roms without going back to stock, myself included. Disabling lagix is recommended though. I've seen a few people have issues going from 2.2.1 to 2.2 so keep that in mind if you're currently running 2.2.1.

As far as bricking your phone, it's always a possibility. Proceed with caution.

As a side, did you try to battery pull method to get Odin to recognize your phone?
[Captivate Q&A, Help & Troubleshooting] yentlequible:
Is 2.2.1 the same as 2.1update-1? Thats what I have...

What is the battery pull method? I may have tried it, but I can't remember.
[Captivate Q&A, Help & Troubleshooting] lrs421:
Sounds like your running eclair. Do this to get into download mode.

Open stock Odin.

Power off the phone.

Remove the battery.

Connect your phone to your computer via USB.

While holding down the volume up and down buttons simultaneously re-insert the battery.

Odin should now recognize your phone and allow you to flash back to stock.

I haven't done that in a while.
[Captivate Q&A, Help & Troubleshooting] yentlequible:
Ok, ill try this out.

Also, I apologize for making this in the wrong forum. I got confused and thought that it would be a good place if I was discussing a roms.
[Captivate Q&A, Help & Troubleshooting] lrs421:
Good luck :). Their friendly in q&a too ;)
[Captivate Q&A, Help & Troubleshooting] yentlequible:
Wasn't recognized.... :(

Ill go take this over to the Q&A section...