RonS

I tried it with the original sd and got the same error.. going to try your dll here if i get enough strength

If the problem is with a corrupted RenewallFlib.dll then the original 2017 SD won't fix it. When you get rested, try the one I sent (I hope you downloaded it because I deleted the attachment from the post. It had about a dozen downloads, but I didn't want everyone using it.  I didn't want dozens of babies crying if it didn't work.

If you have success I'll post it for everyone. If not, zip-up your original DLL and post it.

 step by step:

1. MMC 1GB fat32 copy two file testmode and NAVI.EXE

2. MMC 4GB fat32 copy MAPS2017

 

We run the device in mode and look for the file in the directory USER\PRG1\APL\Navi.exe  and delete it later copied from the memory card Navii.exe then remove the card and insert with maps. Do I understand correctly? 

Sorry for the mistakes but I use the translator, I'm from Poland

Sorry for the mistakes but I use the translator, I'm from Poland

Forget about Nag screen until you get 2017 installed. Read the Shortfuse hack instructions http://avic411.com/index.php?/topic/83535-map-update-hack-using-shortfuse-method-z110-z140x920-x940/

Hello, I followed the instructions but on RenewallFlib.dll the HxD doesn't find "0350A0E3". What I have to do? Thanks

Why don't you try following the detailed ShortFuse instructions instead of this abbreviated summary. Sounds like your problem is with using HxD. Also, when using Find or Replace make sure you set 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).

ShortFuse hack

I have the original.. I will try yours. As for the .dll in the non-active prg, do you just leave that one how it is? i nly messed with the 1

It shouldn't hurt to replace both. The non-active one will be overwritten during the update install. 

BTW, earlier you said you were going to buy a unit off ebay.  What unit do you now have? Do you know what the current software  version is?

I didnt touch anything on the install card, and got my dll from the unit ... Do you have a .dll you can send me to try?

It boots up, enter the passwordpassword then it reboots, and then gets that error.. it wouldnt go that if it were not fat32

It sounds like you modified a file on the installation SD. The only change to SD files would be to use a different CARDINFO.CIF  if necessary. I hope you didn't replace RenewallFlib.dll on the installation SD. I'd just extract the whole thing from the zip (we know its good) or use the original unmodified one you bought.

Yes, so in reality I only patched the one in prg1. The one in pgr0 is the original file (as mention already "new" offsett)

OK, since the already patched PRG0 had no effect, that's further evidence that we need to get/patch/replace the one in the Active PRG, not always PRG0. I've updated the Shortfuse instructions.

Great. BTW,  that CardInfo patch looks like it covers 3 units, but IDK which specific ones (besides your F20). So - for those who can't get the update to start, you may have to dig a little. I'm not very familiar with the F series, so IDK which models precede the F30.

Psydon, do you recall if PRG0 was the Active one before doing the map update? I'm trying to collect data one which works best: blindly patching PRG0, or patching the Active one. I'm starting to think it needs to be the Active one but need more data. My Active was PRG0 so it doesn't add any info.

AVIC-F20BT Update Success!

 

So, here is what i did:

 

First i have edited CARDINFO.CIF.

You need to search for:

 

OE9R75LQ2MJ2X72EUR

 

and replace with

 

X07EURX27EURX30EUR

 

Then save CARDINFO.CIF and replace the one on update SD Card.

(I'm providing already edited CARDINFO.CIF, so you can just overwrite it)

 

Then i used TestMode to get RenewalIFLib.dll from HU to edit it.

I copied one from following location \USER\PRG0\APL

Then edited it on PC with HxD.exe and made following changes:

 

Replaced all (hex) 0350A0E3 with 0050A0E3.

 

Saved the file, copied to SD Card, then back on HU copied on:

\USER\PRG0\APL

and

\USER\PRG1\APL

 

Booted SD Card with 2017 update, then for update password entered: PASSWORDPASSWORD

 

and bam, update installed after 25 minutes. 

 

Thanks to Godzilla for providing update files and to RonS for instructions.

Today I copied the one from pgr1, it was not patched. Did that, and now everything works!

Did you put the patched one back in PRG1?

I downloaded the Supertest for my F840BT but opens the menu of copy files for the update... how can i solve this?

From what I understand from your post, that's what it is supposed to do. If you don't understand the details of these instructions, you shouldn't be attempting this hack. It is easy to damage your unit.

To get an understanding of TestMode see several of the videos on Youtube. Like this one https://www.youtube.com/watch?v=ipoK6dfCp_Q

Suksess!!!!!!!!!!

Update complet on f-930bt Had to goto prg1  and change offset. Did try prg0 first, but it had allready been pached? Yes RonS, the file I copied from unit prg0 and zipped down.

 

Thank you godzilla and RonS

Great news. I'm glad you used persistence. Sometimes you just need to try other things to get it to work. First rule is - don't make it worse.

I want to make sure I understand what you did that worked. You got the file from PRG1 and patched it. Did you put it back into PRG1 or PRG0?

The reason I'm asking is I've found conflicting information in posts over the years. Some say patch & install in PRG0, some say to use the Active PRG directory. Of course, PRG0 has a 50-50 chance of being the actual Active PRG. So that may have worked for many, but not all.

In my case, I've been using this hack for the last couple updates instead of VERINFO. I think that I patched PRG1 last time w/2015 (the Active PRG). So that meant it installed 2015 into PRG0 and that was my active dir.  This time I patched my active PRG0 file and copied into PRG0 & PRG1. And it worked but I wasn't sure whether it was because it always uses PRG0 or it used PRG0 because it was the the Active PRG.

So depending on what you reply, it seems the correct way is to hack and replace the current active file. It would be useful if some other people posted which PRG they patched. Once we've got more data points, I'll clarify the ShortFuse instructions.

Ok, found the part of what needs to be replaced.

Thing is the part to be replaced is a little different than that from previous 2013 or 2015 update.

In 2017 CARDINFO.CIF one need to replace:

 

OE9R75LQ2MJ2X72EUR

 

with

 

X07EURX27EURX30EUR

 

This way i got update recognised in my AVIC-F20BT, but now it asks me for update password.

I guess we need to wait for someone to hack the VERINFO file...

Great. Post a zipped copy of your Cardinfo.cif file so other's can use it.

Did you apply the ShortFuse hack to your file copied from your unit USER\PRG0\APL ???

Update Comlpete!

Thanks for your Support, RonS!

Great news. AFAIK you're the first to verify it works on F series.

Hi RonS, I'm stuck with "Wrong SD" message. I used an old VERINFO.DAT on the new SD. My bad. But I don't have a file in the Download folder. It's empty. Any tips or tricks?

 

Thanks in advance!

Did it actually ask for a password and start the update? What happens if you eject the SD and reboot? I'd go back to the correct (original) VERINFO.DAT. That file is tied to a specific update version, and might be what triggered the Wrong SD message.

Hey guys,

is for what version is this update?

Europe 2017 Pioneer MY09/10 AVIC-F10BT, F20BT, F920BT, F9210BT, F9220BT

or

Europe 2017  Pioneer MY11/12 AVIC-F30BT, F930BT, F9310BT, F40BT, F940BT, F840BT, F8430BT This theard names units from two versions of Pioneer F20BT F30BT F40Bt F920BT F930BT F840BT Etc 2017

 

thanks for your help and best regards

 

It is just like 2015, where you only have to use the correct CARDINFO,CIF file to get it to work with either set of units. Godzilla should post which version he bought. 

so, if i have never hacked my unit.....then i should not have to worry about this shortfuse or the backup camera hack

I'm not sure if that was a question or a statement. Nothing to worry about, as long as you're careful. Don't delete anything without a backup copy.

If you were asking if you needed to do ShortFuse, yes. Or it won't get past the installation password. Hopefully someone (pionara) will come up with a super-easy method that won't require manual hacks.

I still patched the same offset locations. Just my first byte on a few strings were off.

Just finished doing the nag screen mod and BT updates. Backup cam next.

Are you saying that at the specified offset the first bye was different? I wouldn't be surprised if the machine code moved a little in some versions of the DLL.

The rest of you beware. I'm very leery about blindly patching in bytes if the expected source file doesn't match. Realize these are machine instructions and/or addresses. Put in the wrong location  it could easily crash your unit.

If you need to break out of the update use the method at the bottom of the ShortFuse method instructions.

In reality, I think some of those patched sections aren't necessary. If you don't see the specified original bytes, I'd recommend just skipping that line of the patch instructions. Then the worst that could happen is that the update won't like your password. At that point you could look for the expected values near the expected location and try again. Maybe then you could post alternate patches to help others.

I think the version of the DLL I used was from the 2015 update (v6.0). I'm not certain if you could just use my patched version if the firmware in PRG0 was different. If someone wants to try that, I'll upload it. Be sure to post your results. This stuff can easily be undone if you keep a backup. Anyone feel adventurous?

NOTE: I have added a new section Alternate Patch Method.at the bottom of the ShortFuse instructions. Use this if your file offsets/data don't match the original instructions. But save the original file, just in case.

Hi I have just purchased a Second hand car with a Pioneer AVIC F910BT, How do I  Map updates for the F910 BT.

I don't know, but you'll have better luck asking in the F series sub-forum. Maybe spending some time reading there 1st you will find your answer.

Glad to hear it worked. I was afraid that there would be different DLL versions with different offsets. I guess it all depends on what software version happens to be in PRG0. That's why I didn't post a pre-patched file. 

Here's a pre-patched version of Navi.exe. Unzip then follow the instructions above to install on your unit. I can only recommend using this replacement file on North American units at this time. If you want to try it on F Series units, please report back if it works. Keep a backup of your old file just to be safe.

Navi_NoNag.zip

I strongly recommend reading the installation documentation linked to in post #15.  Things of interest:

• The tables indicating changes between different software versions.
• Instructions on updating the Bluetooth firmware - especially if you currently have older than v3.10.
• Various settings that may be affected.

Keep in mind that your model number doesn't change by installing updates. If you have a Z110 from 2009 and previously installed 2015 maps - its not a Z140. Its still a Z110 just running updated software. The tables also show differences between update software versions.

With every update, some will have odd issues. Often with wired iPods or phone connection; issues with Pandora or AHA; App Radio, etc. First thing to try is to do a hard reset by removing all power (easiest is to disconnect the car battery but you could also pull both fuses that power the unit.). Also make sure the App Connection settings are correct for your usage.

For those who have a backup camera installed, I've posted a method to remove the "OBJECTS MAY APPEAR REVERSED"  text.

Link

This mod is for Z110BT/Z120BT/Z130BT/Z140BH. It also works for X920/X930/X940 and the F series equivalents of the same hardware. It only works for the 2017 v7 firmware.

If you have a backup camera and are tired of that stupid message "Objects may appear reversed", here is the way to remove it for this release (v7.0). This is for English language text only. I'm sure the same thing can be done for other languages. For those interested, I got the info needed for this hack from Here. I think this works for both US English and EU settings. If you only care about US English, you can ignore replacing the EUGBENG.LNG file.
 
You'll need TestMode to install this hack. TestMode can be 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. It is very easy to accidentally delete files 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).
 
Note: Do not modify the files on the 2017 update SD before installing the update. If you do, the installation will fail.
 
After the 2017 installation, use a separate SD with TestMode.key and the patched EUGBENG.LNG and UCUSENU.LNG. Insert the SD into your headunit. It will boot into TestMode.
 
 When TestMode starts enter File Maintenance.
 
The goal is to replace the existing two language specific files with the patched ones. Since TestMode will not allow you to overwrite an existing file, you need to delete the ones already there.
 
First, you need to identify the "active" set of files. There are two \USER\PRG 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 language files are in \USER\PRG0\APL\LANGDATA\StringData. Otherwise, the active language files are in \USER\PRG1\APL\LANGDATA\StringData. From now on I'll just call it the Active Language Directory.
 
Navigate to the Active Language Directory and delete EUGBENG.LNG and UCUSENU.LNG
 
Navigate to your SD card and copy the 'hacked' EUGBENG.LNG and UCUSENU.LNG.
 
Then go back into the Active Language Directory and select Paste. It might take a minute to complete. If you are having trouble selecting multiple files for copying/pasting, do them one at a time.
 
Then remove the SD and reboot your headunit. Done.
 
If you decide to revert back to the original files, you can just copy them off the original installation SD or your backup copy (you kept a copy, didn't you?).

Objects Reversed Warning Delete 2017.zip

so for the Z140, we still need to swap cardinfo files?

Not if this is really  T1000-25818. That should work for Z130/Z140/X930/X940 with no changes. Note that the ShortFuse hack does not involve changing any files on the installation SD (other than CardInfo.CIF for the Z110/Z120/X920).

Sorry guys had strep and hit me hard all week.. here you go:

https://drive.google.com/open?id=0B5KpUvEq0nCnb29SZFVlNTZrZUk

 

hopefully somone cracks it! Password: avic411s

Oh man, I feel for ya. Strep can knock the $hit out of you.  Rest up.

From the zip file name I see this is T1000-25818, which is for Z130/Z140/X930/X940. So older units will need a new Cardinfo. See the attachment.

Need a guinea pig to try installing on a Z110/Z120/X920. After unzipping, replace the existing CardInfo.CIF. No fears - if it is wrong, the update will not run. 

For now, everyone will need to do the ShortFuse hack to get past the installation password. Hack

Z110Z120X920CARDINFO.zip