public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "rcpax" <rcpax@digitelone.com>
To: <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] My bluetooth dongle is dead after flashing-help pls
Date: Sun, 5 Dec 2004 03:00:20 +0800	[thread overview]
Message-ID: <002101c4da33$88bef620$0102a8c0@mammoth> (raw)

[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]

Good day to all,

First off, I'd like to apologize if I'm posting the wrong stuff here. I am a Windows user but I am trying to seek the wisdom of Linux users on this matter

Here's the story of my problem:
I flashed my BT dongle [Epox BT-DG02A] with one of those GenericCSR.dfu files using WIDCOMM's btdfuapp.exe under WindowsXP. It flashed succesfully, but after flashing, I noticed I can't pair with my other device (Nokia 3650), and the effective range of this Class 1 BT dongle was down to only 1meter.

After searching through a lot of webpages looking for a working solution to revive my dongle, I have came accross a link from jonsguides forum to this mailing list

I am looking for an appropriate firmware that will work with my Epox BTDG02A dongle. Since no Windows application (that I know of) has the ability to read and backup the dongle's firmware, I was not able to save a back-up of my firmware.

Does any of you have the appropriate firmware for my dongle? I believe this is the only solution to make it work again. Or is there any other solution to this problem?

My BT dongles original firmware # is 828 HCI 1.1 033C LMP 1.1 033C.

Any help is greatly appreciated.

rcpax

[-- Attachment #2: Type: text/html, Size: 2314 bytes --]

                 reply	other threads:[~2004-12-04 19:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='002101c4da33$88bef620$0102a8c0@mammoth' \
    --to=rcpax@digitelone.com \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox