Jump to content
AVIC411.com

RonS

Moderators
  • Content Count

    1,857
  • Joined

Everything posted by RonS

  1. http://avic411.com/index.php?/topic/83592-security-password-removal-script-for-z110120130140-x920930940-some-older-f-series/
  2. 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 it 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?
  3. 0x is simply a notation that the following number is hexadecimal (base 16), as opposed to octal (base 8 ), decimal (base 10), binary (base 2) ....
  4. I think I followed most of that. But I'm not sure what files you think were deleted or why. Were you doing a Delete or a Paste? Did you intentionally copy from one PRG directory to the other? If so, you just made things worse. You can't accidentally overwrite files with testmode. What do you mean "I have a prg.flg file but it sits in the root= user\ (not in the prg folders)". If PRG.FLG is present, it would be in \USER along with the PRG0 and PRG1 folders. Than may be what you were saying. OK, here's the first rule of hacking - have a backup. So I recommend getting a 16GB (8GB might work)
  5. I hate to get involved with this mess. I'm sure I'll regret it. Don't "replace some files from prg1 in prg0". Those are different, and possibly incompatible versions. What exactly did you do? It might be easier to fix if you explained what files you corrupted. I don't know how to force installing the same version onto itself. But there may be easier ways to fix this once you say what you did. Also, it would help to know whether after installing v7.0, if USER/PRG.FLG exists. It might be possible to temporarily set the system back to the previous version then re-install v7.
  6. Everything points to a problem with Parking Brake detection. If it isn't that, you've got a hardware problem. So hope that's it. We know it worked at one time (maybe from a different car) since a previous owner actually paired his phone. So maybe it got disconnected. If a previous owner did the bypass wiring in the harness, the moved wire sometimes loosens. IDK if there was ever a software PB bypass hack for this unit, but it would get overwritten by the next map update. Software PB hacks haven't been engineered in several years. So, I think you need to pull the unit and check the PB wire
  7. By cannot "use GPS", do you mean you don't see your location on the map? Or that you can't enter a destination? Or something else? Disconnecting the battery does not clear BT settings. However, installing new (or the same) firmware does. But that won't help you because you can't get to that menu. Can you get to Settings/Navi Settings/System Status? If so, what does the Parking Brake status say? If it is always OFF, the parking brake wire is not connected correctly. That is the most likely explanation for these issues.
  8. Set the parking brake. BTW, do you have a user's manual? You can D/L one from Pioneer. Tje PDF is better than a paper manual because you can search for key words.
  9. I wouldn't have any faith in Pioneer help desk to diagnose this. They can't even handle simple things. Assuming you are still stuck with the tuner error, it could be a hardware or software problem. Not as simple as a boot sector error. I recommend sending the unit for repair. But a unit that old might not be worth the expense. I'd look at replacing it with newer unit with new technology/features.
  10. 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
  11. I have no idea why it failed. Looks like you will have to do the manual method. You don't need to patch/edit your RenewallFlib.dll file. use the one that came in the script zip. Download and extract Supertestmode. Copy that Testmode.key to your SD and insert in the Avic. Test Mode should start. Go into file maintenance, then delete the existing RenewallFlib.dll files from both APL folders (\USER\PRG0\APL and \USER\PRG1\APL). Then copy and paste the RenewallFlib.dll I included into both APL directories. Good luck - Testmode is a pain to use for many of us.
  12. You're welcome and glad to help. I'm deleting your quote of the entire post #1 since it is redundant and, from time-to-time, I update and/or clarify instructions based on feedback. I don't want to have to go looking for other copies.
  13. The hack is installed. The map installation is not part of this thread. Your problem is with the map update files. Discuss that in the F-Series 2017 update thread.
  14. Ready the 3rd paragraph (in red) of post #1. The hack was already installed by the script. You are done. If you use the script, you don't edit the files. Just go ahead and install your map update using PASSWORDPASSWORD for the Pioneer password.
  15. Sorry nezfotnemom, old thread - but we've got another Z110 throwing this error after the 2017 update. Also doesn't have the traffic tuner. How was your buddies problem resolved?
  16. To get out of testmode I just eject the SD then turn off the ignition. I've never found a way of gracefully exiting.
  17. Yes, but it is a pain to do because TestMode is so un-friendly. I just remembered, I wrote a script that will do this. Just download and copy the included 3 files to SD, and insert. PRG-FLG-Script.zip
  18. It can be an empty file. Doesn't really matter since the presence/absence of the file is all that matters. The case of the file name doesn't matter since windows is case insensitive. Oh, another cause of that "no applicable program" error is installing Condi's Hackmode. Has that ever been installed on this unit?
  19. I hope there are also directories named PRG0 and PRG1. If not - game over. That "no applicable program" error means the unit can't find NAVI.EXE which is in both PRG0 and PRG1. The one it tries to load depends on whether PRG.FLG exists. If it is not there, it runs the files in PRG0, otherwise PRG1. To create the file - on your PC open a text editor like Notepad and immediately save as PRG.FLG.
  20. Sounds like you deleted more than just one file. There's no way deleting just PRG.FLG would cause that. If it did, the file is easily replaced. It is just an empty file indicating which of the two latest software versions to load.
  21. You may be able to back-out the BT version buy installing 3.10 and then the 3.32 you got from the 2017 maps. The Bluetooth firmware update function does not seem to care if the version is older than the current one. Are you still getting the tuner error message? If you want to go back to the original Z110 software, you will need to use TestMode to delete (or add if necessary) the file /USER/PRG.FLG. You will need to download and unzip http://mybyteideas.com/x9310bt/supertestmode.zip, then copy TestMode.key to an SD and insert it. Once your unit reboots, you will see a menu. It is too c
  22. The only issue is - as I mentioned above, you are supposed to update BT firmware in 2 steps: 2.5 to 3.10, then to 3.32. Unfortunately, the FIRMWARE directory that was posted is 3.32. There was a separate SD shipped with the update that had 3.10. So I don't know if that will cause you BT problems in the future. ​As far as service manual, you have and always will have a Z110. However, you might want to download and use the Z140 operation manual. https://www.pioneerelectronics.com/StaticFiles/Manuals/Car/AVIC-X940BT_OperationManual030212.pdf
  23. Go ahead and try a factory reset. I doubt it will fix the problem but it is simple to try and you've nothing to loose at this point. Are you saying that you disconnected the gex-p920xm? Rather than trying to re-install firmware, you might be able to go back to the previous version by going into testmode and deleting /USER/PRG.FLG If that file does not exist, then you should create an empty file on your PC and copy it to /USER.
  24. The original Z110 had support for the MSN traffic tuner. That support was removed when the Z120 came out and it causes this error. So, it appears that the headunit thinks you have that tuner. Make sure it is not installed. I'd even temporarily unplug the XM tuner. Turn the car on and see it it clears-up. If not, disconnect your battery for 30 seconds. This will reset the unit. BTW, I hope you read the 2017 release notes for instructions on updating the Z110 BT firmware. It requires a 2-step process - first updating to v3.10, then to 3.32. I don't know what problems could be caused by ski
  25. Is this the first time your system has been updated? Do you have the MSN traffic tuner installed? If you bought the car with the headunit already installed, you might not be aware that the old tuner is installed.
×
×
  • Create New...