Jump to content


  • Content count

  • Joined

  • Last visited

Everything posted by RonS

  1. 2017 new maps for avic

    The map upgrade installs the latest firmware (v7.0).
  2. 2017 new maps for avic

    No need to upload anything. Yes, you'll need to do some reading and put more effort in to using the files here.There is a thread started by user godzilla that has everything you need.
  3. 2017 new maps for avic

    I hate to see bootleggers make a profit selling pirated software. You can get the same maps free just looking around here. Or you can give them your money and hope for the best.
  4. Yeah, that doesn't seem like something to try when you don't know what it does. Did I forget to mention TestMode is very dangerous? Even the manual is vague about what that does.
  5. Yes Navi.exe needs to be in the APL sub-directory. PRG.FLG is just an empty file. Its sole purpose is to tell the boot loader which is the active PRG directory under \USER (if PRG.FLG is present Active == PRG1, otherwise PRG0). So you can actually use any file renamed to PRG.FLG. I just create one by opening Notepad and Save As. I can only guess now but if you hadn't madly starting moving files areound you should of fixed it by putting ing the original Navi.exe into USER\PRG1\APL. I wonder if you accidentally deleted something. It's easy to do in TestMode. You said you tried re-installing the update. Did it actually do anything? I thought it would not re-install over itself (same version number).
  6. Sounds like everything you try just keeps making things worse. Law of Holes. Make a backup of USER before doing anything. I'm guessing you ignored my advice in the Nag Screen thread and didn't make a backup. Since you said you deleted USER\PRG.FLG that would indicate that PRG1 was the active directory after after installing v7.0. Correct? So create again a USER\PRG.FLG. Then delete USER\PRG1\NAVI.EXE. Then copy NAVI.EXE from the original 2017 image and put it in USER\PRG1. If that doesn't fix the "No Applicable Program error, you deleted other things and I doubt I can help. BTW, you didn't install HackMode, did you?
  7. I don't know. I assume it would work with any SD with the FIRMWARE folder in root.
  8. Reading your other post, it seems you were saying your BT was not functional even before installing the new maps/BT. These BT modules have been known to fail. I remember seeing some for sale recently but I don't remember where. You can do a Forced Program Write of the BT firmware. I suspect the actual drivers are stored in some other file system not directly accessible via Testmode file maintenance. See if you can find a Service Manual for your unit. I have one for a Z110 which also is a manual for TestMode. There are several diagnostics for testing the BT module. Here's the Z110-BT Service Manual
  9. Heads-up! The Navigation.com website now has the new 2017 maps for Z130BT, Z140BH, X930BT, X940BT and for earlier models Z110bt, Z120BT & X920BT. http://www.navigation.com I suggest reading the installation instructions found on the above website before installing. Note: I posted the same message in the X series forum and requested that they post any discussion on this update here. The F series guys (which use the same firmware but EU maps) usually are ahead of us on finding hacks, so keep an eye over there.
  10. Make sure in the SD root, ithere is only CardInfo.CIF, and the directories UPDATE & FIRMWARE (optional since you already updated BT). Then, if nothing happens (not even the first update screen), it would have to be the wrong CARDINFO file.
  11. Two most likely guesses: 1. You don't actually have a X930bt. What does it say on the face? Loading 2015 maps doesn't change that model number. 2. Something is wrong with your SD. What files/folders are in root? What size is the SD? Is it FAT32?
  12. A simple way to permanently delete your unit's security password. No Condi Hackmode or TestMode needed. I wrote a simple script that will delete the security PASSWORD for most Win CE based F, Z, and X series units. I can't say whether it will work with the very old units, and it won't work with the model numbers ending in 50 or greater, or Nex units. If your model isn't included, look elsewhere (don't post here) -there's probably already a thread in the proper sub-forum for your unit. Format a smallish SD (32 GB or less) FAT32. Download and Unzip the attached file. Copy into the root of the SD the TestMode.key and ScriptExec.ini from my zip. No other files on the SD. Eject it from your PC and insert into your AVIC. If nothing happens after 5 seconds. turn off your ignition for a few seconds, then turn it on. You should see a prompt to press any key. Press any button (volume-+ or trk <,>). Done. Remove the SD and restart your unit. No more password. Note that the TestMode.KEY I use here is only used to run scripts. It will not put your unit into the Maintenance menu. Also note that the script copies your existing PASSWORD.DAT file to the SD - just in case. So make sure it is not write-protected. And a word of advice - In the future, don't set a password. It is no deterrent to a thief since there is no visible indicator that it has a password lock.(he will smash your window and destroy your dash regardless). Plus, he'll find this thread and unlock it. So save yourself the hassle a year from now when your car battery dies and you can't remember the password. Password Removal Script.zip
  13. You don't need testmode. The BT firmware for this release is on the SD in the \Firmware directory. You didn't give any detail on what you did and what went wrong doing the BT update through BT settings.
  14. No -just as it says in my post. Do not change anything. Must be something wrong with your SD. Otherwise it is very foolproof. What exactly does it say? Make sure it is FAT32 formatted and it is not write protected (the slide switch on the side of the SD).
  15. This is a hack to prepare your unit to install a map/firmware update. Confirmed to allow firmware updates for all Z110, Z120, Z130, Z140, X920, X930, X940 - and probably their corresponding rest-of-the-world units. I can't say whether it will work with the very old units, and it won't work with the model numbers ending in 50 or greater, or Nex units. This should work with the following F series models: F10BT, F20BT, F30BT, F40BT, F840BT, F8430BT, F920BT, F930BT, F940BT, F9210BT, F9220BT, F9310BT Abstract: This was an early method used to hack map update releases. I believe it was published by member ShortFuse. Use this hack to allow installation of new update releases without requiring a unique password from Pioneer (which binds the update's unique media serial number to a specific headunit's serial number). It involves patching a DLL on the headunit prior to installing the update. UPDATE: See post #15 for an easy automated installation of a pre-hacked file. No Testmode or hex file editing needed. I'll leave the rest of this original post here for educational purposes. If you use the script method, steps 1 - 4 below can be skipped. But read 5 & 6. I only recommend this hack for those experienced with modifying/hacking their AVIC units. This is just an interim method to install the maps/firmware until a more "user friendly" way has been engineered. It requires familiarity with use of TestMode to copy/paste/delete files on your headunit. TestMode's user interface is not intuitive and very frustrating and error prone. I recommend watching JasonH's youtube tutorial - but do not install Condi's Hackmode. Just download supertestmode.zip; unzip it; copy TESTMODE.KEY to your SD; insert in your headunit. I also recommend making a backup of all the files/folders on your headunit in the USER folder before trying anything. Put that SD away and keep it. If you brick your headunit with no backup, I won't be helping you. Let me be clear here. The danger isn't that this hack will damage your unit. The danger is that you will inadvertently delete something important using TestMode. If you use care it is perfectly safe. 1. First Boot into TestMode. You'll need to identify the "active" set of files. There are two \USER\PRGx directories on your HU. The active one is indicated by the presence or absence of a file named \USER\PRG.FLG If this file is not present, the active application files are in \USER\PRG0\APL. Otherwise, the active files are in \USER\PRG1\APL. Upon further research I see most people using this hack say to use the USER\PRG0\APL file. From now on I'll just call it the APL_Directory. 2. Get a copy of APL_Directory/RenewallFlib.dll. If you still have the files from the last map update installation, you can also get it from there. Actually I don't know if it matters where you get the file. Copy it to an SD and then move it to your computer. 3. Using a hex file editor (like HxD.exe) apply these changes to your copy of RenewallFlib.dll. Using HxD.exe - when using Find or Replace make sure you set to it to Hex Values. It defaults to String data type. Also, put spaces between the hex bytes (a byte in hex has two numbers....03 50 A0 E3). (Note: if the expected values are not found at that offset location, do not continue - your firmware is not compatible). See Alternate Patch Method below. Offset 000019F0: 0350A0E3 replace with 0050A0E3 Offset 00001A10: 0350A0E3 replace with 0050A0E3 Offset 00001A3C: 0350A0E3 replace with 0050A0E3 Offset 00001AD8: 0350A0E3 replace with 0050A0E3 Offset 00001C1C: 0250A0E3 replace with 0050A0E3 Offset 00001C24: 0150A0E3 replace with 0050A0E3 IMPORTANT - do not modify the file on your new map/firmware installation SD - this will cause the installation to fail. Use a different SD with Testmode.key and the patched file. 4. Copy the file back to your HU into the same APL_Directory. Hint: you must delete the old one before you can "Paste" the file back. TestMode silently ignores overwrites. It is a very good idea to keep a copy of the original file. This DLL (library) only gets used during firmware updates. Edit: It wouldn't hurt (and might help) if you copied the modified file into both APL folders (\USER\PRG0\APL and \USER\PRG1\APL). This way you are sure the hacked DLL will be used. 5. Install the unmodified map update. (see separate thread for map updates and instructions) When you are ready to install a map update for your supported AVIC model, just restart your head unit and insert the map update SD. With this "ShortFuse" hack installed on your head unit, the update will work as described in the release documentation. When prompted for the password from Pioneer, the password you enter will not be validated in the normal manner. I suspect you could enter anything that is 16 characters long but I recommend entering PASSWORDPASSWORD just because I know that works. If the update software rejects that password, you did something wrong. 6. If the map update fails to complete and you are stuck with a wrong or incorrect SD message: boot into testmode. go into file maintenance remove the file USER\SYSTEM\Download\StartKnd.log This will kick the unit out of upgrade mode, and it should restart into regular mode on next power up (remember to remove the TestMode SD). You should still be running with your previous firmware and maps. Enjoy! ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// Alternate Patch Method. There are multiple version of the RenewalIFLib.dll file. For some the offsets of this patch could be slightly different. In that case, try using this method. Using HxD (hex editor), load up the RenewalIFLib.dll file you copied from PRG0\APL Enter the Search/Replace dialogue and make sure Datatype is Hex-values[/size] Search For: 03 50 A0 E3 Replace with: 00 50 A0 E3 In Search Direction select All Then click Replace All You should see a dialog box saying Replaced 4 occurrences of "03 50 A0 E0". Press OK. Now, the fuzzy part. Search at or nearby these addresses and replace:[/indent] At or near Offset 00001C1C: find 0250A0E3 replace with 0050A0E3 At or near Offset 00001C24: find 0150A0E3 replace with 0050A0E3 If the above worked, save the file and continue at step 4 above. If not, something is wrong. Do not save the file.
  16. Avocado 930bt

    Security Password Removal Script for Z110/120/130/140, x920/930/940
  17. I honestly don't know what is needed for Lightning support. I'd suggest following Pioneer's upgrade instructions - upgrading a Z130 from the original firmware to 7.0. Don't forget to update BT drivers.
  18. Works fine for me. Windows 10. When I click "Download Anyway" it starts D/Ling to my Downloads folder and displays the progress in the bottom left of my screen. The whole thing takes < 5 min on my 100Mb connection. Done by the time I write this message.
  19. If you are asking me - no ideas. I don't know anything about an F320-BT but it was never stated in the instructions that this hack would work on it. You should start a new thread in the F series forum to see if anyone knows. I don't want this thread to get side-tracked for every incompatible model. Good luck
  20. z110bt upgrade

    Your Z110 is, and always will be, a Z110. It is in the hardware. Using the link above you can find out how to upgrade the firmware to the current versions (v7 and BT v3.32) and maps to 2017 versions.
  21. AVIC Z130BT Tuner issue

    I have no affiliation with Pioneer so I wouldn't know. I'm sure it is in their documentation or on their web site.
  22. AVIC Z130BT Tuner issue

    So, that eliminates software and installation issues. The only thing left is hardware. Some component regarding the FM tuner is failing - possibly due to heat sensitivity. Seems the only resolution is the have it repaired.
  23. Need help x930bt

  24. I'm surprised it worked on a X910, that's an older model. If the script worked it copied a file to SD called PASSWORD.DAT. Then if deleted the file from the head unit, which should unlock your unit during the next reboot. Windows doesn't know what to do with a .DAT file. If you want to view what's in the file, right-click and select "open with" and choose Notepad. I'm confused - you just said you ran the script. What does "Source" have to do with it?
  25. For those who have installed the 2017 release (v7.0), here is the Nag Screen Removal hack. Requires supertestmode.zip (unzip it; copy TESTMODE.KEY to your FAT32 SD). This should work for Z110, Z120, Z130, Z140, X920, X930, X940. It should also work for F-series comparable models and likely others that have v7.0 firmware. This is dangerous - especially for noobies. Make a backup of any files you change - in fact making a backup of all files under \USER is a good idea. Keep the original file(s) until you are sure everything is working correctly. It is very easy to accidentally delete files or whole directories in TestMode. Copying and Pasting files is a real PITA and is very error prone. I recommend watching the YouTube video by JasonH on using TestMode (even though he calls it HackMode for historical reasons). Do not install Hackmode! Note: Install the 2017 map update before installing this hack. Do not change the file on the 2017 installation SD. If you do, the installation will fail. You will get the dreaded "Wrong SD" error. Note: I have no way ATT to verify that the F series NAVI.EXE is the same binary, so it would be helpful if someone could verify the bytes below are correct at that location. If not, more research will be necessary. Make a copy of the NAVI.EXE file on the 2017 update SD (in \UPDATE\USER\PRG\APL) to patch. Then using a hex editor (such as HxD): at offset 0xBEC18 change 05 00 00 0A to 00 00 A0 E1 and save the file. HxD also has a binary file comparison that can be used to make sure that only the above 4 bytes were changed. Then use a separate SD with TESTMODE.KEY and the patched NAVI.EXE on it. With your headunit turned on, insert the above SD. It will boot into TestMode. Go into File Maintenance. First, you need to identify the "active" set of files. There are two \USER\PRGx directories on your HU. The active one is indicated by the presence or absence of a file named \USER\PRG.FLG If this file is not present, the active application files are in \USER\PRG0\APL. Otherwise, the active files are in \USER\PRG1\APL. From now on I'll just call it the Active directory. The goal is to replace the Active NAVI.EXE with the patched one using File Maintenance. Since TestMode will not allow you to overwrite an existing file, you need to delete the one already there. Using TestMode, go to the Active directory and delete NAVI.EXE. Then go to the SD and select the patched NAVI.EXE and select Copy. Then go back into the Active directory and select Paste. It might take a minute to complete. Then remove the SD and reboot your head unit. The app should start and allow you to see the map without presenting the annoying Nag Screen.