Jump to content


  • Content count

  • Joined

  • Last visited


About RonS

  • Rank
    Established Member
  • Birthday May 30

Profile Information

  • Gender
  • Location
    Belleair Beach, Florida

Recent Profile Visitors

17110 profile views
  1. Sorry, I don't know anything about the MRZ series. I see lots of posts regarding them (mostly about changing the language), but it isn't an area of interest for me.
  2. According to Italian section of the map installation manual, the prompt to enter the password is preceded with this screen: I don't speak or read Italian (or Dutch), but this is probably equivalent to what you described for your installation. After responding "Si", it prompts the user to enter the password. I think the image @maunav90 posted is after he entered "PASSWORDPASSWORD" and it was rejected. So it was asking the user to re-enter the password. I suspect that he never (or incorrectly) installed the Shortfuse hack, so the password it was expecting was the "real" one registered for this unit's serial number. Not the hacked one "PASSWORDPASSWORD".
  3. It won't work on a NEX unit. Totally different systems. Try this method: Alternate method - service password screen.
  4. F10BT Maps and or firmware

    "Here" is the official supplier of Pioneer maps. I'm not sure what your question is. It says clearly on the Here map page (in your link) that it is 2019 map, and is a "map of Europe", and it works for AVIC-F10BT. Keep in mind that the maps are often 1 yr old when they are released as an update product. So it won't be up-to-the-minute.
  5. No power to unit

    All double-din units mount the same, but the trim removal for each model vehicle will be different. If it isn't obvious how yours is removed you'll probably need to post question on some forum for your specific make.
  6. No power to unit

    There's a 10A fuse on the back of the unit. If you don't have an installation manual, you should download one. AVIC-X930BT_InstallationManual040511.pdf What is a "main fuse"? You need to check check that both power wires have 12VDC (red=switched, yellow=constant). They would be on two separate circuits - so two fuses. A voltage/multi meter would be useful. However, I suspect someone screwed-up when replacing the car battery. Maybe + and - wires got switch or shorted. You don't normally blow a fuse when properly replacing a battery. If something did that, it could easily of fried sensitive electronics.
  7. Z140bh Bluetooth Audio Problem

    Although my old Nexus 5 worked fine with 3.32 firmware, I had to roll-back my BT firmware to 3.24 get my Samsung Note 10+ to work right.
  8. Remove that file (\NAND\SYSTEM\SECURITY\SECURITY.DAT) and the password will go away. Just to be safe, copy it somewhere first.
  9. So you had a backup with /USER, including PRG0 and PRG1? That's good. I'd keep that SD in a safe place. One thing I forgot to mention. After a firmware update, if something isn't working - try disconnecting all power to the unit for 30 seconds. Easiest way is to disconnect the battery. Alternatively, pull the fuses for both the yellow and red power wires. For an F920, I believe v2 was the original stock firmware. If so, the files in PRG0 and PRG1 should be identical. One thing you could try is to change the "current" program directory. You do this by adding or deleting (if already present) /USER/PRG.FLG (an empty file is OK - or just create a file on your PC named PRG.FLG and copy it to the F9220. Then reboot and see if it loads OK. At that point it would be running the backup version. If it doesn't load OK, there is something wrong with the currently active PRG files or an issue with the physical storage. Either way, you could try installing 2017 maps (after running shortfuse if necessary). Unless you are not running stock Pioneer firmware or there is some hardware problem, this should work.
  10. First, get an 8GB SD and make a backup of /USER so you can recover from any mistakes. Also, if you have the original SD that you used to install the Shortfuse hack, save it. It would have the original APL\RenewalIFLib.dll files found in PRG0 and PRG1. Next, when you said "avic-f9220bt. v2.0", I assume you mean your old firmware was v2.0. At first I thought you were saying there was a V2 hardware. I also assume that F9220bt is the same hardware as f920bt. What do you mean by "used test mode to use backup"? Did it boot back into the old firmware OK? I don't have an answer to why V7.0 isn't running. I don't know much about the F series in general and the F9220bt in particular. But I think there must of been some other changes/hacks made on your unit.
  11. If you ran it in 2017, it wrote the hacked RenewalIFLib.dll file in PRG0/APL and PRG1/APL. Only one of those files got overwritten by the 2017 update. When you install an update, it overwrites the "non-active" PRGn files with the new update's files. Then it makes the new PRGn the active directory by setting or deleting /USER/PRG.FLG. So I'd guess the hack needs to be installed again since the non-hacked one is in the "active" PRGn/APL However, that's all just theory. No one that I know of has even tried the hack with 2019. So I guess we'll find out soon.
  12. HackMode 2.2 remove F930BT 2015

    Why not just install the 2017 update? As for 2015, you can use the av.exe from the US/Canada version. The program files are identical. I have it for US. See attached zip. Av.zip
  13. HackMode 2.2 remove F930BT 2015

    I never recommend using hack mode because you have a 50% chance to having this problem. Someone who uses hackmode should bee able to help you uninstall it. But your original issue with the keyboard probably was because the parking brake was not detected.
  14. To install the hack? A few seconds. If your question is about installing the map update, it belongs in the map update thread. Should take around 20-30 minutes.
  15. You might try re-pairing the BT connection first. Sometimes it is necessary to do a hard restart after a bluetooth upgrade. Simple surefire way is to disconnect the battery for 30 seconds. Or, if you know both fuses that power the radio, you can just pull them. If that doesn't fix it then try older BT firmware. maybe even re-installing 3.32.