Search Archive

Firmware update headache

By majellin · Apr 15, 2017in NEX Series💬 26 posts👁️ 19,183 views
Page 1 of 2
Posted Apr 15, 2017 · 03:49 UTC#1

I'm surprised I only see just a couple of posts "sort of" close to the issue I'm having and the ones that are there seem to have some really strange resolutions... I'm an intelligent person and this one just escapes me.

 

Has anyone been successful in updating an AVIC-8000NEX running 1.01 FW to the latest 1.14?  Or even making a jump from 1.01 to the version just before 1.14?  I cannot get my unit to recognize that I have a FW update on my USB stick or SD card.  It recognizes the actual devices and I've tried three different USB drives (4 GB, 8 GB, and 32 GB) and one SD card (8 GB). So here's what I've tried so far, with every time the unit saying "Update file error" along with make sure the update file is the only thing on the USB drive blah blah...

 

Downloaded the correct AVIC-8000NEX firmware file from the Pioneer firmware website.

Unzipped the file using a Windows 8.1 PC (and the built-in zip extraction) onto a 32 GB USB flash drive (formatted FAT32 like instructions say) exactly as is (AVIC5000NEX folder being the only thing on the drive).

Tried to update... failed with error above.

Thinking 32 GB was too large, I switched to an 8 GB drive, repeating the same process, same error.

After some research I came across two possibilities, that maybe FAT16 was better than FAT32, and that there might be an issue with hidden files/folders.

Tried deleting the hidden "System Volume Information" folder... same error.

Tried formatting as FAT16 instead of FAT32... same error.

Tried a 4 GB drive... same error.

Then I got a Windows 7 PC and re-downloaded the firmware from the website, tried all of the above, all resulted in the same error.

I went and grabbed an 8 GB SD card, formatted it, copied the folder from the zip file onto it... same error.

I downloaded 7zip to use a different program to unzip the zip file, used both the USB drive and SD card... same error.

The last thing I've tried now is I've seen the "AVIC5000NEX" folder named slightly different either in forums or even the 1.14 update documentation--in one of the posts on this site I've seen it called "AVICNEX5000" which was likely just a typo by the author, but then in the documentation it shows "AVIC-5000NEX" as the folder name.  So I tried renaming the folder to either one of those... same error.

 

I sent Pioneer an message from their support website a couple days ago, haven't heard from them--wondering if I will anyway.  Guess I'll probably have to call their support number on Monday but I just can't believe I can't get this figured out.  It's either that you can't make the jump from 1.01 to 1.14 (which I doubt because they don't make any of the intermediate updates available) or I'm missing something completely stupid.

 

Anyone run into anything remotely close to this? I'll take any and all ideas that I haven't tried yet.

 

Thanks.

 

Posted Apr 15, 2017 · 04:11 UTC#2

Are you plugged into USB1? The device won't recognize the update on USB2 or the SD card.

Posted Apr 15, 2017 · 04:45 UTC#3

Yeah I've been using what I assumed was USB1 because my installer labeled the cable that way.  Just in case, since I hadn't tried it, I just tried plugging in the USB drive to what was labeled as "2" just in case the installer accidentally swapped them... still no luck.

Posted Apr 15, 2017 · 10:33 UTC#4

seems correct what you are doing. Folders (AVIC5000NEX) and all, and USB1.

 

tried formatting the usbsticks in another computer or OS (fat32)? or use a third party format program? Some Mac and windows users have problems after format with new files and such been added. The Unit is also kinda picky when it comes to USBsticks, but you have tried alot it seems....

 

other tip: windows built in zip extraction may brake the folderstructure. it does not preserve file paths by default.  Make sure the "Use folder names" checkbox is checked when extracting the files from the update zip file. or use one like WinRar etc.

 

Try upgrading to an lower firmware.

 

Here is asd255 megashare folder with them:
https://mega.nz/#F!nE4jFBrJ!q51j1RVr7g5QfFU5IDzFOA

 

look in the x000 folder and choose the one you want and  works with your unit

 

 

but i think your problem is the way the usbstick/SDcard is formatted or the unzip program/way that you are using.

try to format with this one:
https://www.partitionwizard.com/free-partition-manager.html

 

->Root of usb -> AVIC5000NEX folder -> file               (do not rename anything, may brake structure)

 

Also WHEN you manage to upgrade, you also have to upgrade the Bluetooth firmware afterwards. (use the same stick and content)

Edited Apr 15, 2017 by SpecTrax
Posted Apr 15, 2017 · 13:07 UTC#5

I have a 6200 but the update is the same. When I updated my firmware I formatted the USB and did everything accordingly but had similar issues installing. I then realized the problem was how I copied the file from my computer to the USB.

 

You have to copy and paste the file, you cannot use the "send to" method and you also have to OPEN THE MAIN UPDATE FOLDER (in my case) named 7200NEX, 6200NEX,5200NEX_FW-Update_v1.01_8G 

 

COPY ONLY the AVICAVH16 folder (The 8000 may have a different name) that's within the main folder.

 

And you do have to use Number 1 USB.

 

You will also need to reformat the USB to FAT32 which will delete the first copy.

 

Good Luck!

Edited Apr 15, 2017 by Duke
Posted Apr 15, 2017 · 21:11 UTC#6

Thanks guys. Duke, I've done exactly what you've said... at first I screwed up by copying the files out of the (in my case) AVIC5000NEX folder into the root of the USB drive.  I learned quickly that you actually have to copy the AVIC5000NEX folder itself onto the root and leave the files inside it alone.  I've been trying things that way ever since.  I have tried both USB ports with no joy.

 

SpecTrax, thanks a lot you had me pretty enthusiastic that an older firmware might work.  I tried 1.11.  I even then downloaded WinRAR (though I had started to use 7zip as an alternative to the built in Windows method).  And then I even downloaded the Partition Manager program you posted to format the drive as FAT32.  Can you believe this... still no luck!!!  I thought for sure I was going to get it this time.  I just don't understand how I could be doing anything differently. Oh and thanks for the tip on the Bluetooth--yeah hopefully if I ever get to that point.

 

I'll keep tinkering I guess but I'm running out of combinations of things to try.  The only thing left maybe is that all of my USB drives are SanDisk.  I have one non-SanDisk drive but it's too small.  Maybe I'll run out and pick up a cheap non-SanDisk drive and see what happens.

Posted Apr 15, 2017 · 21:49 UTC#7

you could try with an SDcard again? Your unit is in "off-mode" when trying to flash? i myself have used sandisk and they worked great. they come with some software sometimes but after a format thats usually solved. the cruizer ones comes with this, so if you have them, try some without the softwarebundle.

 

 

bet you've tried and know this already but :)

 

post-119583-0-95499500-1492293505_thumb.jpg

post-119583-0-76245300-1492293510_thumb.jpg

Edited Apr 15, 2017 by SpecTrax
Posted Apr 15, 2017 · 23:13 UTC#9

Yeah I saw that post... that's where I was playing around with folder names thinking maybe that was the problem.

 

But guess what? And I have no explanation for this...

 

I went over to Target and picked up a Lexar USB drive... 8 GB.  Formatted as FAT32 using Partition Manager (deleting what was on it completely and adding a brand new partition).  Copied the files directly to the USB drive using 7zip as to not have to move/copy anything after the extraction was done.  Went into my car, expecting it to not work to be totally honest... and then it worked!  Plugged into what my installer labeled as "1" (so at least I know that's right) and sure enough the "Reading..." flashed way longer than it ever did before and then went into the process.

 

Of course I ended up using 1.11 so now I have to go do 1.14.....maybe.... lol.

 

That makes zero sense.  The brand really shouldn't matter because I'm reformatting it the same.  I followed the same process I did with my 4 GB Sandisk (and the 8, and the 32 lol).  I'm pretty sure that I've tried extracting the files directly to the flash drive but...maybe not...I tried so many things.

 

I really just don't know.... I'll let you guys know if the 1.14 update goes the same.  I may first try to extract the files the way that I did before, rather than straight to the flash drive...in the interest of science.

Posted Apr 16, 2017 · 07:19 UTC#10

Sounds great :) Bad batch of USBdrives maybe? Just remember after the upgrade to 1.14 (or 1.11...if you stop there :) ) to do the BT upgrade also :)

Edited Apr 16, 2017 by SpecTrax
Posted Apr 16, 2017 · 17:47 UTC#11

Sometimes manufacturers put their proprietary crap ware on the USB stick. I don't remember if Sandisk is one of them but probably something like that. Certain versions of windows see it as executable and run the autorun.ini which is hidden by default.

I'm guessing that's part of the problem.

Posted Apr 21, 2017 · 06:03 UTC#12

You'd think so but I reformatted those drives a few times each.  I even wiped every partition on them and created a new FAT32 (and FAT16 just for grins) partition from scratch--and it was the only partition on the drive.  Just a quick update to that... I went back and used one of the SanDisks for the 1.14 update and it worked.  So I really have no idea.

Got the Bluetooth updated too thanks Spec... :)

 

So now I'm all up-to-date and working... and have a whole bunch of flash drives laying around with Pioneer firmware on them lol.

 

Thanks guys.

Posted Apr 21, 2017 · 14:11 UTC#13

Just an FYI because i didn't see it mentioned here for anyone else who might read this thread:  You have to make sure all your audio sources are turned off before it'll allow you to update.

Posted May 01, 2017 · 21:18 UTC#14

Also as an FYI, I was able to update my 8200NEX using a sd card with no problems despite the instructions saying you have to use usb port 1.

Posted May 01, 2017 · 23:12 UTC#15

Also as an FYI, I was able to update my 8200NEX using a sd card with no problems despite the instructions saying you have to use usb port 1.

 

I did as well. Had to get a low-life cheap 16GB SD card.  Formatted to FAT32 on the Mac and it worked great for both the unit firmware and the Bluetooth.

I also tried using a USB flash on USB 1, both worked...

Posted May 23, 2017 · 16:28 UTC#16

New forum member here, just to clarify: despite the directions telling you to use USB1 a standard SD card inserted into the front of the unit can be used to update as well?  So if the unit is installed there's no need to uninstall it from the dash before updating?

Posted May 23, 2017 · 22:58 UTC#17

New forum member here, just to clarify: despite the directions telling you to use USB1 a standard SD card inserted into the front of the unit can be used to update as well?  So if the unit is installed there's no need to uninstall it from the dash before updating?

Ive used the sd card for updating. Try both and see what you like.

Posted Jun 06, 2017 · 01:51 UTC#18

I was able to successfully update my 8100 NEX via USB1 from firmware 1.05 to 1.09.. However, I tried updating my Bluetooth per the firmware directions and it's not working. I was on 03.41.10 and I get an ERROR in the process.    I used the exact same USB drive to do the firmware update and it doesn't work.  I tried to do the Bluetooth update via the SD card and same issue, it says it's updating don't turn off the engine and then I get an ERROR screen.  Does anybody have any idea what's going on before I call Pioneer?

Posted Oct 08, 2017 · 09:17 UTC#19

Hi all, Spec just referred me to this thread. I have just got a 2014 model F60DAB. It's got old firmware on. I am about to try doing the flash myself after reading this useful thread, thanks to all who contributed. Quick question - just in case it ends up taking me a while, is there a reason why upgrading the firmware will benefit me in some way, or is it just for security or to be "up to date"? I mean, will the unit run better, faster, more reliable, or anything else useful?

Once I have done that, I am hoping to find a way to update the maps without going through NaviExtras as their support wasted 4 hours of my time yesterday, they don't even make their website compatible for Safari browser, or their software compatible for mac computers, what a joke. I know macs are a minority, but its a big minority now, and they cut out 10% of the population when even the most basic software sellers can do a mac compatible version now for just about any program on the market! Not impressed with them at all, and the prices of their maps just had me bent double with laughter :D

Posted Mar 25, 2018 · 21:23 UTC#20

All I can say is wow, you would think for 1000$ or 750$ now , we would have never had to have any of these problems right? Well , I personally bought this deck and was happy with it, all of a sudden, o look an update, kool, lets do it...what is today? Yea my deck is still stuck reading the upload, still says fail, did everything that you all have up to the point I read this post...omg im going to do exactly what you said, nd im going to cross all fingers nd toes...I jus wanted to say good job and thanx for sharing !!! That was an awesome journey with a great ending , hope mine turns out the same!

 

Posted Oct 07, 2018 · 02:39 UTC#21

This is not "bad USB" cards this is fully due to Pioneer fragile update system and their failure to clarify on this issue or to fix bugs with their product.

I have tried half a dozen SD cards all different brands and several USB cards using Window 10, MacOS and Linux with no success.

If anyone here has enough computer experience to use dd to image a SD card or USB drive that does work for this it would be appreciated.  While I love the product I have avoided other Pioneer products because of this issue.  Unfortunately both BT and android auto are starting to have issues and I need to upgrade but I am tempted to just rip out the deck and change brands.

I am in this industry and reading FAT file systems or at least making a process that isn't this fragile is not a high bar and there are simple tools they could have used to package an update image if they cared.  I hate to be so negative about such an otherwise great product but don't let  Pioneer's development teams off the hook there, this common technical issue probably points to a severely broken culture and little desire to fix a long term pain point for customers.

This problem is not caused by various storage card/thumb drive vendors but is completely within Pioneer's development team's responsibility to fix.

Edited Oct 07, 2018 by seagreg
Posted Oct 10, 2018 · 23:30 UTC#22

I'm having exactly the same error updating my AVIC6100-NEX. I have a bag of USBs that threw off the error. I have double checked it is trying USB1. I have edited my registry to avoid t he creation of the folder "System Volume Information" that normally happens with all any USB on a standard Windows machine. 

The Pioneer support person said basically, "I did it and it worked for me, your problem." I am stuck. I really want this update to 1.11 because it is supposed to help CarPlay. Any other ideas?

 

Posted Nov 24, 2018 · 18:09 UTC#23

You guys have me spooked.  This thread is exactly what's keeping me from updating from 1.03, lol to 1.11. 

I remember receiving an email from Pioneer on September 2017 advising to keep iOS 10.  I finally got my 8100NEX reinstalled recently and it's working ok.  I just know if I try to update it'll fail.  I think I successfully downloaded the update to an otherwise empty thumb drive & using iOS 12.1

Posted Feb 12, 2019 · 05:17 UTC#24

Trying to update the firmware on a new AVH-W4400NEX and having issues as well.  I've tried USB and SD card with no luck either way.  USB doesn't seem like it wants to work for anything.  Can't get USB to recognize anything.  Does anyone have any suggestions?? 

Should have bought the Kenwood I wanted instead of this crap! 

Posted Feb 15, 2019 · 12:41 UTC#25

format USB as Fat32 and insert into USB1

 

Page 1 of 2