flash_the_hun

The cardinfo.cif from 2017 does not work with F10BT. It took me a while to make my unit work at least with the 2017 SW again, as it was asking all the time for the right SD card. (I used the script before to replace the renewal dlls , and the password was accepted too.) I made a few experiment with patching the cardinfo with the string from 2017, but no success... At the end I removed the USER\RW\RENEWAL\VERINFO.DAT , which was copied from the 2019 update already there (I know because I checked the content), which apparently does not match the 2017 cardinfo, and put in the 2017

The 2013 EU Maps are out on the Navteq homepage. Has anyone already some experience with that update?

You will need a hacked dll (see the hacked update topics) to be able "update the unit again". If the software has the same version (like your case), it won't do anything.

The handsfree mic has nothing to do with this. RTFM.

Worked fine on F10BT with 2.003 too, thanks!

Wow, great news, I would like to see IGO8 running on my F10BT, I only wonder if the speed signal and the gyro signal could be used too, like in the native navi software. It would be also nice to have an own app which can control the volume depending on the speed. I hope the base system is the same for F30/F20/F10, so we could use the same hack on all systems. If you need a beta tester on a F10BT ( I'm running 2.003 Firmware, so basically it is a F20BT), PM me

I have the same kind of problem with navigation sometimes on a F20BT. It happens usually when I make a stop on a long trip (after about 2-3 hours driving). After restart it starts to rotate like you described. I checked once the sensor status, and it really shoved a right turn on a straight road. Probably the G sensor did not initialized correctly, or did not finished the init phase before I moved on. Unfortunately the unit does not have a power-off button, so I had to stop again, wait for the afterrun, and power-up again to have the sensor reseted. After a short while it found and shoved my p

I think that a cap wouldn't help much. Maybe a DC-DC converter or a small backup-battery, which gives stabilized 12V to the HU during cranking.

If you download both updates, you will see, that the map content is completely different. As I already mentioned, only the application is the same (this explains why all languages are available in both) With The v.2.000 update I succesfully installed the new GUI too... By the way, the 2.003 upgrade was indeed succesfull, only the application info screen says it is still 2.000 (probably this is only a platform version) In testmode the application version is displayed correctly as 2.003 So to your question: it brought new maps and new GUI (I don't like the new GUI, but there was no cho

have you tried at the bluetooth settings on your avic, to set again the connection type to handsfree&audio?

I also have daytime running light, and it's kind of annoying that I have to manually dim at night - otherwise I don't see a thing from the display in daylight... I was thinking about to buy a light sensor (my car does not have one) and connect it to the ILL input on the HU (with a relay if necessary), so it could change the color scheme and dim as necessary. But until now I haven't found a suitable and cheap solution...

Seems like we will not need a bypass anymore? Man, running Android with haret sounds so cool it would require a lot more development though, especially without the exact specs, adresses, protocols to use the HW. I would be already happy if using iGO or other apps would be possible, or using an Eye-Fi card and have internet access through an accesspoint...

No risk, no fun For EU there is only the 2.0 EU update(F10->F20) and the 2.003 update available (the 2.003 EU has exactly the same files as the 2.003 US) Nothing more. What made me think that the hack should work, is that the US 1.001 update is also exactly the same as the AU 1.001 update as saiwogjai also mentioned. And also most of the 2.0 update is the same, excluding the maps, and some files which seem to store version numbers regarding the maps. I have no clue about the files of other systems, but if the file-check is the same, you might be right. But I think it is neces

I took a deep breath, and tried the hack on my F10BT (EU). And it worked I was able to install the hacked US 1.001 , then the EU 2.0 update with a random password. Thanks ShortFuse for the hack! It seems, that the application part is the same for both variants. The only strange thing is that after I tried to install the 2.003 update, it still says 2.0000 although it copied the files, and it seemed that it finished correctly (reseted / restarted itself as it should). If I try to reinstall the update, nothing happens. The unit seems to be fully functional, so it's fine for now.

Regarding the img file: it might also be a kind of flash filesystem. (We used this extension during our development process too for files to be flashed.) I will try to mount it in linux as a filesystem, to check it.