sy628109

Has anyone else had any issues copying the flash disk to their SD card? I have f-900bt, maybe 1.5 years old. I am trying to get a more recent backup before doing the 3.0 update. I am able to boot into testmode; the f-series reads the SD card just fine but appears to not be able to write to it anymore (used to work). The progress bar displays, then sits at the "preparing to copy disk" message for about 10 minutes before I cancel it. I do not remember it taking this long, am I just being impatient? I have tried two different SD cards, my computer is able to write to both of them s

Does anyone know of a good online tutorial for Photoshop that will help us create our own splash screens? I have searched online and in photoshop's help and haven't been able to come across anything.

It has been done and it does work Actually, doesn't work, since it breaks checksum on the upgrade... Thanks Boris.

I have DL the 2.006 firmware......does anyone see a problem with replacing the data.zip/sys.txt files in the firmware with my hacked data.zip/sys.txt before I even load the firmware to my avic? To me it seems to be the same as overwriting it once it's on the unit, it just saves me a few steps.....any thoughts?

OP, that was stupid, I hope you never need any real help....you just insulted one of the most knowledgable people in this forum.

OP, that was stupid, I hope you never need any real help....you just insulted one of the most knowledgable people in this forum.

Has anyone tried splicing a factory back-up camera and connecting it to the F-series? I have an '08 f-150 and the camera comes up in the rear view mirror when I reverse, would be cool if I could use that and view it through the F-series.

This is resolved.

I was able to fix this issue...hopefully you made a backup of your flashdisk to take some files from. 1. Go to your backup flash disk and save a copy of the "USER" folder to an SD card (I am doing this from memory and I think it is the top level) Then go to APL2-->iGo and save a copy of ezrider.exe to your SD card. 2. If you log into the APL2-->iGo folder on the HU iteself you will see a file named "crash," delete this file, it should not be there. If you look at your clean flash disk you will see it is not there. 3. Overwrite the corrupt ezrider file that is currently in

Do you have a steering wheel controller connected? I could not use the touchscreen after I moved the volume, it was the steering wheel controller causing it.

sounds good, I am going to give it a shot......I am having the ezrider.exe problem, hopefully it works if I overwrite the existing corrupt ezrider file and put my original back on there. Thanks

I've asked this elsewhere but never received a response: Why do you need to load the original iGo folder back on after the update? I know my problem is stemming from that folder, wouldn't I just be reloading the problem on there if I put it back? Thanks.

Couple of questions: Wont reverting back to the original iGo after the update cause the same problems? My ezrider.exe file seems to be corrupt, will that cause issues going back to the same iGO folder? I am asking because right now I have access to testmode and dont want to do something where I cant get back into it and really be screwed.

This is the other option available, does anyone think it will work? http://avic411.com/forum/viewtopic.php?t=20119 To me the ez rider file in the current iGo folder is corrupt, and copying it back in after updating will cause the same issue, right? Based on that threa it sounds like if you dont copy the original back in that the fix does not work. Does anyone have any ideas? Does anyone have the previous update to revert back to so I can reinstall the 2.0? I am trying to avoid having to send this in to Pioneer, so if I can do what they are going to do anyway, that would be

has anybody tried going this route? http://avic411.com/forum/viewtopic.php?t=20119

I started getting the ez rider error, which is causing a loop of the splash screen. I already have the 2.0 update so I can't reload that without trying the procedure found on the forum (since I can still get into testmode and it involves deleting your flashdisk I am not willing to try that yet). Do you think just copying a clean APL2-->Igo folder onto my flash disk will correct it? Has anyone figured out what causes this error? When it started last night I thought I had done something in my DATA.zip but after looking at it and switching back to a previous DATA.zip which worked

I am having the same problem, I am going to try it with the engine on like mentioned. PAC has told me that it means a bad ground wire, so I would check your wires carefully. In my case that is not the issue as I have tested it with a multi meter and it is grounded to my units ground which I know is good. Their one tech support guy is more than willing to help. (Jose) another guy there was a joke, he gave me the wrong instructions and if I were an idiot would have completely screwed up my factory harness and PAC module. Be careful when talking to them that you are clear on all de

I figured mine out, it was the PAC steering wheel control module. Do you guys have that connected? If so disonnect it and perform all three resets. (1. nav menu-restore factory defaults 2. reset button 3. hold reset button and eject button for 10 seconds simultaneously) The wires are still connected to my factory harness, I disconnected the blue box from the head unit and the PAC harness. If that wouldn't have worked my only option according to Pioneer would have been sending it in as a defect. Hopefully this works for you guys.

I do not have a remote starter, but I am having the same kind of touchscreen problems. I have narrowed the cause down to the volume control on my unit. Every time I move the volume up/down doesnt matter, I lose control of the touchscreen. The only way to get it back is to press the map or menu key then it works again, until I move the volume of course. Does this sound similar to your problems? I never had the problem before doing some mods (probably a coincidence) but I have a PAC audio module connected and my last test is to disconnect it; I have been working with Pioneer and if

I've narrowed this issue down, it seems the touchscreen does not work only after using the volume knob, regardless of the change up/down. At that point I must use one of the hard buttons (menu or map) to reset the touchscreen. I ask this on here because Pioneer's support is pretty much useless, all they can tell me to do it reset the unit.

Not that this helps solve anything.....but I noticed that as well, original version that was loaded as "map version" seems to have changed.

Not that this helps solve anything.....but I noticed that as well, original version that was loaded as "map version" seems to have changed.

I have made a few mods; bypass and some changes to the navigatemap.ui file.....ever since doing so my touchscreen has been acting funky. If I do not touch the screen for a few minutes the only way to get the touchscreen to work is to hit the map key and then go back to whatever I was trying to do. (almost like the map key is resetting the touchscreen) It could just be a coincidence that this is happening after the mods, afterall my girlfriend's D-series does the same thing. Is anyone else having this problem, any ideas on how to fix it? Thanks

Tried that, everything seems to be a little quicker, the button response issue is still occurring though. It's getting pretty annoying, no one else is having this problem? My girlfriend actually has the same problem with her D series......

Has anyone been having any touchscreen button response issues since making these changes? My touchscreen will not work until I hit the map key. (almost like it resets the touchscreen) I have to do this whenever I want to change anything via the touchscreen......... 900BT, only other mod is the software bypass.