I have a BT338 bluetooth GPS adapter it will not get a lock on and I have been looking for a flash program for it to see if I can reflash it.
I followed a link from a site to this sites ftp server that used to have it but it looks like it has been taken down.
Does anyone know if flashing is possible and if so does anyone have a program to do so?
Thanks for any help.
Packrat,
I have had a BT-338 for two years and I love it. I don't recall that I was ever able to find a method to upgrade the firmware. I will watch this thread in case some one has an answer.
On the other hand, I did have problems when I first got this unit. If I played with changing setting between WAAS/normal and/or Sirf/NMEA modes, sometimes this thing was not get a lock. To fix it I would use a laptop tool to reset the unit to factor setting. I think it was GPSInfo connecting via a BT dongle.
Let me know if this might help and I will look into the exact detail if you need it.
whbell said:
Packrat,
I have had a BT-338 for two years and I love it. I don't recall that I was ever able to find a method to upgrade the firmware. I will watch this thread in case some one has an answer.
On the other hand, I did have problems when I first got this unit. If I played with changing setting between WAAS/normal and/or Sirf/NMEA modes, sometimes this thing was not get a lock. To fix it I would use a laptop tool to reset the unit to factor setting. I think it was GPSInfo connecting via a BT dongle.
Let me know if this might help and I will look into the exact detail if you need it.
Click to expand...
Click to collapse
Thanks for the reply, I tried to reset it to factory via the SirDemo program, but that didnt help. Hopefully I can find a way.
Yes reflash is possible...
You can use SirfDemo and SirfFlash
The procedure is almost the one described here....
http://web.mac.com/tomtastic/site/log/Entries/2007/6/18_Holux_GPSlim236_boot_mode.html
You can download the needed tools here...
http://www.falcom.de/support/software-tools/sirf/
To flash
- First you have to connect your bt-338 using SirfDemo.
- In Action/ Transmit Serial Message select NMEA and send this message
'PSRF100,0,38400,8,1,0' without quotes. This will put the GPS in SIRF Mode.
- After that choose Action / Transmit Serial Message select SIRF this time and send '94' without quotes. This will put the GPS in boot Mode.
- Disconnect now SirfDemo using the button and start SirfFlash without powering down the GPS.
- Choose the correct port and 38400 Baud and - very important -select 'external boot mode'. Browse for the new firmware .bin file and select 'program flash'.
- Execute and enjoy.
Cheers!
I have now (finally!) successfully read the firmware from my two BT338 and a TomTom Mk2 BT mouse. Also important to notice is the following:
- Address Range is 0x0 to 0x7ffff (4 times an "f") resulting in a 512kB bin file.
- Any other speed than 38400 will NOT work!
Did not dare yet to flash actually... I have now:
TomTom Mk-II
GSW3.0.2TomTom1.1_3.0.00.03-C3P1.02b
BT338 (NaviLock labled in Germany)
GSW3.0.2_3.0.00.03-C16P1.02a
GSW3.1.1LowV_3.1.00.07-C23B1.00
I know there must be newer one for BT338 as you can see from the FAQ at Globalsat USA at: http://www.usglobalsat.com/gpsfacts/bt338_gps_facts.html
The mention even different versions there (QA 38):
BT-338_GSW3V3.1.1LowV_F-GPS-03-0506222 and
BT-338_GSW3.1.1TO_F-GPS-03-0510032
I noticed that reading out the SW sometimes delivers different results after 7d008 when some time has passed. I suspect that some data is stored there which may vary over time (satelite positions, routes or whatever may be stored depending on the time).
bye
tobbbie
I can report success now in upgrading my BT338 from the old (3.0.2) FW to the later one (3.1.1) I have retrieved from my other BT338.
Main gain for me is the availability of geoid correction for the height.
Anynone has a later firmware for the BT338 or the TomTom MK2?
You can PM me if you don't want to post here.
bye
tobbbie
GSW3.0.2TomTom1.1_3.0.00.03-C3P1.02b
Hi tobbie,
have you managed to get some new firmwares , I am searching if there is a new one for the tomtom ( there is still some issues between the treo and the tomtom related to the bluetooth stack ). Is there a way to use the BT-338 or a part of the BT-338 firmware in the tomtom ?
thanks
Laurent
look here: http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=27925&whichpage=11
please read all posts and follow the wohle story. My TomTom MkII currently runs the 3.2.2 of the latest BT338.
Thanks tobbie,
I have red the full thread, downloaded your dumps of the firmware, and dump my tomtom firmwarewith the sirf tools.
I have compared the dump from your tomtom and mine ( same version 302 ) and they are quite different beiginning in 6D008 :
your firmware :
6D008 : 06 3E 00 00 01 00 00 00 41 46 31 41 39 53 D8 19 ....
my dump :
6D008 : 20 C6 00 00 99 00 00 00 41 46 31 41 39 53 D8 19 ....
Is this part a variable part ( so may be a factory reset and a new dump will give a more comparable result ), or is there a real difference for two same version of the firmware ??
Can you tell me for upgrading the firmware of the tomtom have you used the full 3.11 firmware from 0 to 7FFFF or have you used a dump from 0 to 79999 ?
seeing the various problems some got after flashing their units I am a bit worried before flashing mine..
thanks
Laurent
Just do a system reset of your device and dump it again.
Depending how fast you are getting it into bootmode you have some data there (and not all default empty data). Doing the same after some time (e.g. after a fix was established) will again deliver different data there.
I think the main thing here is that the WHOLE data are dumped and then later flashed to another device. This may also be the rootcause of the failure to use the 0-79999 dump - where after 79999 data may confuse the device to get back online (very sad - it already cost 2 devices one BT338 and one TomTom MkII).
I have used my own dumps to crossupgrade from BT338 to TomTom and the 3.2.2 from antineutrino. After some back and forth I am on 3.2.2 again currently for all devices (living with the green-LED off until a fix).
BTW: I am quite sure that the bluetooth part is not touched by these updates.
The names of the devices as they are recognized on bluetooth are not changing after a FW update.
thanks tobbie ,
as I need this gps in the coming next weeks, I will not take the chance to do the upgrade just now. I will wait a quiter period of time to try it ( so if I brick it I will have time to make a replacement ).
thanks, I will come back for detailled instructions in some weeks.
Laurent
Hi Tobbbie,
I have a Globalsat BT 338, I would like to update the firmware. I downloaded your dumps from http://www.gpspassion.com/forumsen/t...5&whichpage=11, the 3.1.1 version.
Do I understand well that even exists a 3.2.2 version?
If yes where could I find it?
Thanks
patek
It's in the same forum a few post further down - it comes from another member there - just look it up.
Edit: just checked - it seems only the 3.2.4 of the BT368 is there.
I have edited my old post there with a new link that has all info - also for short here:
http://rapidshare.de/files/41287744/Firmware_Globalsat.zip.html
Please read the GPS passion forum entries very thoroughly - it MUST be complete dump that you insert - anything less than 512kB will kill your device (as a poor forum member there had to suuffer)..
Tobbbie,
Thank you for your prompt answer,
I checked my software version, Sirfdemo says: GSW3.1.1LowV_3.1.00.07-c23B1.00 - the same what yours was before upgraded.
I read your opinion about changing to 3.2.2 :
>As mentioned earlier I have yet to discover advantages of 3.2.2 or 3.2.4 over 3.1.1. I >think some trickle power options are more flexible and the DGPS could work - but so far I >could never get a DGPS fix.
So do you think is it worth enough to upgrade? (green lamp!)
Is the WAAS enabled in the 3.2.2 ? (maybe silly question)
Thanks
tobbbie said:
It's in the same forum a few post further down - it comes from another member there - just look it up.
Edit: just checked - it seems only the 3.2.4 of the BT368 is there.
I have edited my old post there with a new link that has all info - also for short here:
http://rapidshare.de/files/41287744/Firmware_Globalsat.zip.html
Please read the GPS passion forum entries very thoroughly - it MUST be complete dump that you insert - anything less than 512kB will kill your device (as a poor forum member there had to suuffer)..
Click to expand...
Click to collapse
hmm, i haven't used my trusty bt338 in quite some time, i might upgrade it just to see what happens..
Download: lineage-16.0-20190707-UNOFFICIAL-treble_arm64_bvN.img.xz
Original Post: HERE
Note: you will need some program to extract the .img file from the downloaded .xz file.
How to install
To install use this tutorial HERE
Note: You will need to install the gapps
Known Bugs
Fingerprint not work
Slide functions not work
Automatic brightness not work
Fixing the 4G
1) Call to *#*#4636#*#*
2) Phone information
3) In "Set Preferred Network Type" select "LTE / UMTS auto (PRL)"
4) Finish
Fixing the Faceunlock(Smart Lock): Delete folder: /system/app/FaceLock/lib (Backup before removing)
Fixing the Bluetooth Audio A2DP: HERE
Fixing the NFC: HERE
Note: if you have a password on the device, in order to access TWRP you need to remove your password.
I'm the author for https://club.lenovo.com.cn/thread-5630610-1-1.html "Z5 Pro GT Successfully Flashed LineageOS 16 GSI" posted on 4th July.
Since your "bugs" and "Fixing the 4G" sections are 100% same as mine (except different languages lol) --
Thank you for translating my post & sharing the information with the XDA forum but just a friendly reminder: next time cite sources!
lulujyc said:
I'm the author for https://club.lenovo.com.cn/thread-5630610-1-1.html "Z5 Pro GT Successfully Flashed LineageOS 16 GSI" posted on 4th July.
Since your "bugs" and "Fixing the 4G" sections are 100% same as mine (except different languages lol) --
Thank you for translating my post & sharing the information with the XDA forum but just a friendly reminder: next time cite sources!
Click to expand...
Click to collapse
You just tested the GSI rom. I had already tested it before and after the post and went behind bugs solutions and realized by its post that it is the same as mine and basically the same of any Rom GSI in the Lenovo Z5 Pro GT, a matter of fixing the 4G already had done this before to set up the own 4G of the ZUI that comes from the factory. I just created the post now that I did not actually find any bug fixes.
4G Tutorial: https://forums.oneplus.com/threads/definir-tipo-de-rede-preferido.689181/
Brightness Issue
Hello and thank you for this nice rom... I have a brightness issue... The brightness never goes above 50% even though the slider is at 100%. I know it is not hardware because in TWRP the brightness is normal !
Thank you in advance for your help and sorry for my English (I'm French).
Eban
UPDATE : I found the reason for this bug... Indeed I had tried to install lineage os 17 (without success the first time). This problem comes in fact from a kernel update problem ... found
Hello Fellow OP9 Pro users
I just wanted to start a thread for anyone interested in a OP9/Pro in australia that wanted to get Volte, VoWIFI, and 5G working.
I have tested this and confirmed that it is 100% working for Telstra & Vodafone, I have good word that this method will also work on Optus but don't actually have an Optus sim to test this with.
Huge shout out to happiboi from the OP8 forums for the methods used to get this all working with A11.
First step is to download the oneplus logkit from this link: https://downloadmirror.co/1MW9/com.oem.oemlogkit_1.0-1.apk
Once this has been installed, open the dialer on the phone and type in *#800#, tap on the "oneplus logkit" button, scroll down and tap on "Function switch", then tap on "VoLTE switch" but do not click restart click cancel. Then Tap on "VoWiFi switch" this time press reboot.
Once the phone has rebooted open settings, Wi-Fi & Network, SIM & network, SIM 1, then enable both the toggles for VoLTE and VoWIFI. This is probably also a good time to ensure 5G is enabled under "Prefer network type".
Now what we have done so far is essentially just enable the toggles for everything to work, what we still need to do is actually configure the phone to work on the Australian mobile networks, this is where the information and hard work from happiboi really comes in. I have quoted the guide from happiboi below as it is very well written anyway.
happiboi said:
Code:
Prerequisites:
* Need ADB suite available on PC & enabled "ADB debugging" on phone via developer options
* When you permit your PC adb access to the phone after first adb command, make sure you tick always permit this device. When the phone boots after "adb reboot ftm", the screen is inactive so you can't authorise the device when you try to adb shell and are stuck
* Need QPST suite of apps installed on PC (needed PDC tools + EFS explorer)
* If on custom firmware - probably a good idea to backup your phone before you do this. On custom firmware after the first "adb reboot ftm" rebooting again puts the device in a boot loop until you format data
Process:
- Open command prompt on PC & navigate to where your ADB suite is located
- Type command without "":
"adb devices" (I like to do this to ensure adb can speak with phone/computer)
- Should display:
List of devices attached
<if working, your device should be listed here (else, it'll be blank)>
- Type command without "":
"adb reboot ftm"
--> This puts phone into field test mode
- Type command without "":
"adb shell"
--> Creates dialogue for shell command on phone
- In the shell (OnePlus8Pro:/ $ ) type command without "":
"setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb"
--> This opens up ports that we used to be able to in Android 10
- Phone Screen is still blank - but it's OK.
- Start up PDC Tool in Admin mode on PC
- Click drop down, select phone connection (there's only 1 in the list)
--> ** If the drop-down box is empty and no phone/device listed, you cannot proceed.
--> ** Other users have foudn this to be related to a Qualcomm driver issue.
--> ** Delete the drivers you have currently installed and get a new one from here:
--> ** https://gsmusbdriver.com/install-qualcomm-usb-driver.
--> ** Also once the device shows up in PDC don't click on it, open efs explorer and let it start searching directories --> ** before going back to PDC and clicking on the device in the drop down.
--> ** The window may say 'not responding' just leave it until the carrier list populates then carry on with below steps
- Do the profile activation stuff for Telefonica_UK_Commercial:
- Look for "Telefonica_UK_Commercial", right click and SetSelectedConfig for both Sub0 and Sub1
- Click on the above profile again and click on Activate
- Do not restart your phone
- Don't close PDC yet (don't know if it make a difference but I didn't close)
- Open EFS Explorer (I opened in Admin mode too)
- Navigate to "\nv\item_files\ims\"
- Replace ims_user_agent file with one supplied
--> The supplied one has Telstra VoLTE Qualcomm as header instead of Telefonica
- Navigate to "\policyman"
- Replace carrier_policy.xml & carrier_policy.xml_Subscription01 with ones supplied.
--> Just take carrier_policy.xml and make a copy named "carrier_policy.xml_Subscription01"
--> ** Caveat, I further modified the carrier_policy.xml file as it wasn't enabling 5G for me on my IN2020 (Android 11) Oneplus 8 Pro.
--> ** I changed the nr5g_sa_bands base & nr5g_nsa_bands base values to be "hardware" rather than specifically band n78.
--> ** This changes config to allow whatever 5G bands the hardware has available rather than specific bands
--> ** You can't enable bands that the hardware doesn't support anyway so makes sense to enable all
--> ** This gave me the needed 5G access with Telstra
- Type command without "":
"adb reboot"
After phone boots back up, 5G + VoLTE + VoWiFi are all intact and in working order!
[/QUOTE]
Click to expand...
Click to collapse
I am extremely interested to see if anyone running the A12 beta would try this and see what sort of results they are able to achieve.
Cheers guys.
Thanks for this. Can confirm that this works for the UK as well. I'm on VOXI (Vodafone) and saw no option for wifi calling. Just followed the first part to download the logkit, enabled switch, wifi calling working
mhall156 said:
Hello Fellow OP9 Pro users
I just wanted to start a thread for anyone interested in a OP9/Pro in australia that wanted to get Volte, VoWIFI, and 5G working.
I have tested this and confirmed that it is 100% working for Telstra & Vodafone, I have good word that this method will also work on Optus but don't actually have an Optus sim to test this with.
Huge shout out to happiboi from the OP8 forums for the methods used to get this all working with A11.
First step is to download the oneplus logkit from this link: https://downloadmirror.co/1MW9/com.oem.oemlogkit_1.0-1.apk
Once this has been installed, open the dialer on the phone and type in *#800#, tap on the "oneplus logkit" button, scroll down and tap on "Function switch", then tap on "VoLTE switch" but do not click restart click cancel. Then Tap on "VoWiFi switch" this time press reboot.
Once the phone has rebooted open settings, Wi-Fi & Network, SIM & network, SIM 1, then enable both the toggles for VoLTE and VoWIFI. This is probably also a good time to ensure 5G is enabled under "Prefer network type".
Now what we have done so far is essentially just enable the toggles for everything to work, what we still need to do is actually configure the phone to work on the Australian mobile networks, this is where the information and hard work from happiboi really comes in. I have quoted the guide from happiboi below as it is very well written anyway.
I am extremely interested to see if anyone running the A12 beta would try this and see what sort of results they are able to achieve.
Cheers guys.
Click to expand...
Click to collapse
Hey there,
I'm glad this is working for you too - the credit really goes back to all the XDA users who have helped to give guidance in creating these steps
For anyone reading and interested, it has now been confiremd working on OP6, 7, 8 and 9 series phones (as well as Nord).
Great way to get features that should be 'enabled' from OP themselves and remember you will need to do this after every system/OTA update to re-enable these functions.
Happy days, cheers all!
Thanks so much! This worked perfectly for me with an 8pro on Telstra. I work in an area with a 4G only tower so haven't been able to make calls for the last 6 months!
Could the same methodology be followed for my colleague's Xiaomi mi 10t pro 5g?
happiboi said:
Hey there,
I'm glad this is working for you too - the credit really goes back to all the XDA users who have helped to give guidance in creating these steps
For anyone reading and interested, it has now been confiremd working on OP6, 7, 8 and 9 series phones (as well as Nord).
Great way to get features that should be 'enabled' from OP themselves and remember you will need to do this after every system/OTA update to re-enable these functions.
Happy days, cheers all!
Click to expand...
Click to collapse
jbell87 said:
Thanks so much! This worked perfectly for me with an 8pro on Telstra. I work in an area with a 4G only tower so haven't been able to make calls for the last 6 months!
Could the same methodology be followed for my colleague's Xiaomi mi 10t pro 5g?
Click to expand...
Click to collapse
There's no harm in trying on the Xiaomi.
The other way to attempt this was the original process outlined here: https://forum.xda-developers.com/t/volte-and-vowifi-in-australia.4095097/post-82847027
The only reason we (OnePlus users) had to change our method was because OP closed off access to the efs ports after the android 11 updates.
Not working whit Ho mobile Italy carrier
Ho can restore the original versione of. com.oem.oemlogkit
Regards
Thanks a lot for this! thought I was being screwed by Telstra the whole time.
Confirmed working on LE2123, Oxygen build 11.2.6.6.LE15BA with Telstra 5G, VoWIFI & VoLTE, though when installing the Qualcomm driver in Device Manager I had to use the "Qualcomm HS-USB WWAN Adapter 9091" option to make my phone show up in QPST.
happiboi said:
Hey there,
I'm glad this is working for you too - the credit really goes back to all the XDA users who have helped to give guidance in creating these steps
For anyone reading and interested, it has now been confiremd working on OP6, 7, 8 and 9 series phones (as well as Nord).
Great way to get features that should be 'enabled' from OP themselves and remember you will need to do this after every system/OTA update to re-enable these functions.
Happy days, cheers all!
Click to expand...
Click to collapse
Hey there! I have a Nord (EU AC2003 model) and I'm in Bulgaria on the Telenor network. I don't care about VoLTE or VoWIFI but I do want to be able to use 5G as my carrier supports it (and should be compatible with the phone as they are using the n78 band according to Wikipedia and the phone supports it).
On the phone Telenor said it needed no special activation on their side so this is an issue with the device. I don't have the 5G option in preferred network selection at all so I thought this guide would help until I saw that the XML files are for Telstra.
You said that it has been confirmed to work on Nord, my question is, would this guide work specifically to force the phone to use 5G (I have already tried enabling it through the engineering menu via dialing *#*#4636#*#* but that doesn't work for me)? My second question is whether it would be possible for someone show me how to modify the XML files for my carrier (Telenor BG)/modify them for me if that's the case?
mhall156 said:
Hello Fellow OP9 Pro users
I just wanted to start a thread for anyone interested in a OP9/Pro in australia that wanted to get Volte, VoWIFI, and 5G working.
I have tested this and confirmed that it is 100% working for Telstra & Vodafone, I have good word that this method will also work on Optus but don't actually have an Optus sim to test this with.
Huge shout out to happiboi from the OP8 forums for the methods used to get this all working with A11.
First step is to download the oneplus logkit from this link: https://downloadmirror.co/1MW9/com.oem.oemlogkit_1.0-1.apk
Once this has been installed, open the dialer on the phone and type in *#800#, tap on the "oneplus logkit" button, scroll down and tap on "Function switch", then tap on "VoLTE switch" but do not click restart click cancel. Then Tap on "VoWiFi switch" this time press reboot.
Once the phone has rebooted open settings, Wi-Fi & Network, SIM & network, SIM 1, then enable both the toggles for VoLTE and VoWIFI. This is probably also a good time to ensure 5G is enabled under "Prefer network type".
Now what we have done so far is essentially just enable the toggles for everything to work, what we still need to do is actually configure the phone to work on the Australian mobile networks, this is where the information and hard work from happiboi really comes in. I have quoted the guide from happiboi below as it is very well written anyway.
I am extremely interested to see if anyone running the A12 beta would try this and see what sort of results they are able to achieve.
Cheers guys.
Click to expand...
Click to collapse
i previously had 5g working and volte but ever since i updated firmware for the 8t i lose it i also did the steps which got me 5g before still with no success hopefully this will help which you editing stuff for telstra. the ims whch you put for telstra do i need it im with optus
Just wanted to say this guide is working with an Optus network sim card in Australia!
Carrier: Moose Mobile (Optus)
Device: One Plus 8 Pro (In2020)
Android version 11
As @LordFigTree mentioned I also had to use the "Qualcomm HS-USB WWAN Adapter 9091" driver.
Other than that flawless guide, thank you very much to everyone who made this possible!
error:S
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
By.TRabZonLu™ said:
error:S
View attachment 5405019
Click to expand...
Click to collapse
Might be something to do with the special characters in your user file name? Not sure but it might be worth trying to copy the file from the root of your drive.
Lofty248 said:
Might be something to do with the special characters in your user file name? Not sure but it might be worth trying to copy the file from the root of your drive.
Click to expand...
Click to collapse
Unfortunately it has nothing to do with it. The problem still persists, I couldn't fix it, I gave up.
Lofty248 said:
Just wanted to say this guide is working with an Optus network sim card in Australia!
Carrier: Moose Mobile (Optus)
Device: One Plus 8 Pro (In2020)
Android version 11
As @LordFigTree mentioned I also had to use the "Qualcomm HS-USB WWAN Adapter 9091" driver.
Other than that flawless guide, thank you very much to everyone who made this possible!
Click to expand...
Click to collapse
did you change anything with the carrier policy and carrier_policy.xml_Subscription01? also the ims file? im on optus aswell
Unfortunately this guide doesn't seem to work anymore, the after the last two updates (now on Oxygen OS 11.2.10.10.LE15BA) try the same process but it i don't see it working.
LordFigTree said:
Unfortunately this guide doesn't seem to work anymore, the after the last two updates (now on Oxygen OS 11.2.10.10.LE15BA) try the same process but it i don't see it working.
Click to expand...
Click to collapse
Hey Mate,
I'm running 11.2.10.10.LE15BA and is working flawlessly for me, have tried both Vodafone AU and Telstra sims with no issues.
Damn ok i'm doing something wrong then, i'll try again, thanks for the info.
LordFigTree said:
Damn ok i'm doing something wrong then, i'll try again, thanks for the info.
Click to expand...
Click to collapse
East as mate, let me know how you go!
I'm just here hoping OOS12 doesn't break this method lmao
mhall156 said:
East as mate, let me know how you go!
I'm just here hoping OOS12 doesn't break this method lmao
Click to expand...
Click to collapse
Weird, just did it exactly the same as I did last time but it has now worked, showing i have full 5G connection.
Thanks @mhall156 i wouldn't have tried again if you didn't say it's still working for you, not sure how i screwed it last time but glad i got 5G back.
Awesome, I'm glad it's working! I have had some attempts not work for seemingly unknown reasons. I've just restarted the phone and tried again and have always seemed to make it work.
It's a shame we have to go through this to make our otherwise great phones work properly.