Jump to content
AVIC411.com

RonS

Moderators
  • Content count

    1652
  • Joined

  • Last visited

Everything posted by RonS

  1. Sorry, never tried it. If it boots from USB (do you mean into testmode?) seems like you could try copying the upgrade files into the root of and empty memory stick. There's also the possibility of using Force Program Write in Testmode. I think you can specify the source device as USB.
  2. 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.
  3. Power antenna control for X920bt

    I have it in ANT CTRL in AV System Settings (Power or Radio). Since I have a traffic tuner, I set it to Power. But my antenna is just a wire in the windshield, so nothing to wear out.
  4. 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.
  5. The splash screen doesn't get changed. You wouldn't want it changing if you had a custom image. You may be able to refresh it manually in System Settings/Splash Screen. If you were running firmware v1.x, there would be big differences and new functions (Pandora and AHa). Don't forget to update the Bluetooth firmware in the BT settings. It uses this same SD image.
  6. On your map update SD, replace CARDINFO.CIF with this one. CARDINFO.cif
  7. 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
  8. F930bt test mode

    This http://avic411.com/index.php?/topic/83597-security-password-removal-script/
  9. 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 many years ago 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 Easy method for an 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. 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 the "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: 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.
  10. Parasitic Battery Drain - AVIC 8200 NEX

    A disclaimer: I know nothing about a 8200, so I can't help much. But I was wondering if you leave anything plugged-in to the USB (an iPod maybe) that could consume power even if the ignition is off.
  11. Pin 38 in your wiring diagram looks promising. I checked my 987 diagram and it looks comparable to my pin 19 (both BRN/WHT and go to a module on the right side of the frunk). To access you'll have to remove some of the liner plastic trim. Probable just held by a few screws.
  12. I have a 987.2. so your 981 wiring may be different. Is that a 981 wiring diagram? I have printed instructions from the EuroMotorSpeed kit. It says to remove the cover over the brake fluid reservoir and you'll find a black 46 pin connector with all the wires for ABS. On mine, it was the BRN/WHT wire going to pin 19. Your's looks different. Basically, any wire that pulses when any wheel rotates will work.
  13. Maybe if you stated the model and yr someone could tell how to connect VSS to a pulse wire. Hint - it is in your ABS harness below the brake fluid reservoir. Probably White/Brown for Porsche.
  14. Yes. you can undo it if you kept the SD that you used intact. But it is not necessary and would have no effect. You can not redo the update. What troubleshooting are you referring to?
  15. OK, I didn't realize you'd installed the 2012 update. That's why no PRG.FLG file. The unit has two sets of files under USER. PRG0 and PRG1. Initially they are identical copies and PRG0 is the "active" one. Each successive map/app update alternates between the two directories. So 2012 overwrote PRG1. And 2017 overwrote PRG0. The way the boot loader knows which one is "active" is by the absence (PRG0) or presence (PRG1) of PRG.FLG. Initially PRG.FLG didn't exist, so PRG0 was "active". When you installed 2012, PRG1 became "active" and the installationer created PRG.FLG. Then you installed 2017, which overwrote PRG0 and deleted PRG.FLG. PRG.FLG is just an empty file. So you might try making a file on your computer and copying it to /USER. It is worth a try, and if it doesn't help, it can easily be undone. -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Above is the last time I had posted. I mistakenly created a new account as I couldnt remember the previous one. RonS was attemting to help me, but sadly, life got in the way and the fix was never completed. As far as "creating" a PRG.FLG file, I'm a bit lost. I can create a text document and name it PRG.FLG if thats what you're saying here. Otherwise, please instruct me on what to do. It's been over a month since I reached out to the community, and havent heard anything. I hope this forum hasnt died as it would be missed greatly by those that need it. Thanks, JaxBadDad a.k.a. synapse911 : ) Yes, you can create PRG.FLG many ways. Open an editor and save a file. Just make sure it is named PRG.FLG. I'm not sure it will make any difference. Pioneer Bluetooth is kind of flakey. Always has been. It works for me only if, on startup, I set the audio source to some non-bluetooth source - like iPod. Then wait for the phone to get connected (BT) to the head unit. I can then switch over to Pandora (or any other source that uses BT). If none of the above helps, I guess that's all I can do.
  16. SD Video Question - x940bt

    Doesn't work (never has). From the manual section regarding rear display settings:
  17. Kartenupdate/Mapupdate 2017 AVIC F930BT

    I do not know what your problem was, but what you said is not generally true. I have never uncompressed directly to the SD. There should be no difference in the files if done correctly.
  18. External hard drive compatibility

    A spinning hard drive might require more power than the HU provides. Also, check the owners manual appendix for limitations on format, size, and the number of files.
  19. I have no idea. I don't think it would even work (new firmware with old maps). They are built together. Also I don't think there would be any noticeable benefit. Keep in mind that 2015 maps aren't exactly obsolete. Maybe someone with F series hardware has been able to install a 3rd party app (such as igo). I don't get involved with that.
  20. Nope. No idea about Aus maps or where to get them. You might have to find your local Pioneer web site and buy them. Maybe someone else has a better idea.
  21. It should, but I don't have one. Running this won't hurt - so go ahead.
  22. Although I can't read the message, I've never seen that screen. I have two thoughts. It is possible that commando's navi.exe file did not patch all the calls to "nag" screen instances. You could manually copy my patched navi.exe to both prg0 and prg1. Sometimes weird things happen after a firmware update. You can do a hard reset by disconnecting the battery for ~30 seconds. If neither of those fix it, I've got no ideas.
  23. I have the same hardware (Z110) and i use a wired iTouch with the 30pin connector. I have never seen a nag screen using my iTouch. Are you using the iPod app (source) or are you using App Mode?
  24. Looks like they removed them from Navigation.com web-site. Their link does the same thing. Here's the files: Pioneer_2017_maps-Z110-CRD5009A.pdf Pioneer_2017_maps-Z130-CRD5006A.pdf
  25. Did you replace the Cardinfo.cif file on the SD? The one in the ZIP is for Z130 or Z140
×