Pocket Pod stuck with "FlashUpdate 1.00" on display
by TomasLarsson on 2009-07-25 23:18:40

I made an attempt to update the firmware of a recently bought Pocket Pod. Although following the instructions in the manual the update failed and now it is not possible to get the thing up and running again. The only thing shown on the display is "FlashUpdate 1.00". How can I fix this?

I run Windows XP and use Vyzex Pocket Pod 1.10. The Pocket Pod used to work before my update attempt...

The delivered installed firmware revision was 1.00 and a rev. 1.01 was on the CD. Using Vyzex rev. 1.10 there is under the MIDI roll-down an choice called "Transmit MIDIX (.SYS) file...", which I used to install it. Finally I got it all to work after unchecking the three boxes under the Oprions-preferences-studio tab! This info was kind of hidden inside one of the manuals...

Sorry if my last post came off a little snippy. I had a working Pocket POD before I tried the Flash Update to 1.01 thru Monkey. Now my Pocket POD just says "FlashUpdate 1.00". I've tried every button and unplug and replug procedure I can think of, and the only result I got is that when I press the TAP button the message changes to "FAILED". It's not very encouraging.

Frankly, I don't care about Monkey and Line Edit anymore. I just want my Pocket POD with factory presets to work again. Is there a button I can press or procedure I can do to make it get out of FlashUpdate mode?

Thanks for looking into it, but TomasLarsson said in his original post that he's running Windows XP, not Vista, as am I. Also, I've tried re-installing the firmware update from a USB port (I have confirmed it's a port not a hub) - Line Monkey just gives me an error and my Pocket POD says "FlashUpdate 1.00" no matter what I connect or disconnect.

- Line Monkey looks pretty much like it did when I started (see "Line Monkey 8.jpg").

- I unplug the USB mini cable from my Pocket POD and my computer. I plug my guitar into my Pocket POD, and it's display reads "FlashUpdate 1.00" and I can't access tones. I unplug the everything from my Pocket POD, plug everything back in and the display *still* reads "FlashUpdate 1.00". I press every button combination on the Pocket POD to try to get it out of flash update mode. The only visible affect is that when the TAP button is pressed the display reads "FAILED" (see "Line Monkey 9.jpg"). Encouraging o_O

- I unplug the guitar from the Pocket POD. I plug the USB mini cable into the Pocket POD and the computer and try the firmware update again. Same result. I unplug everything, turn everything off, turn everything back on, plug everything back in, and try again. Same result.

I don't know what else to do. If I could get Version 1.00 with the factory presets back and never have access to Custom Tone or Line Edit, I would prefer that to having an inert Pocket POD, as I do. Please can someone help?

I haven't done the update to my PocketPod yet...wondering if I should now I was just making sure the OP had seen the resources that were available out here. I'd love to help but don't know how. Line 6 has been pretty good about jumping on issues on the forum. I'm surprised no one has piped up yet to help you out

I've been fighting this exact scenario for half a day now. repeated attempts to stop and start and restart..etc... all failed and my POD was stuck in the 1.00 nightmare. However...for some reason or another I just decided to restart my pc (running XPSP3) and then restarted Monkey..and the firmware update.

Amazingly it went right through?! Update complete?! Weird...but that seems to have fixed my problem. Hope that may work for others having this problem.

It was apparently a conflict with the USB drivers due to Logitech hardware !!!

Here is the procedure I followed :

Correcting Windows Logitech (or other 3rd party) Driver Conflicts If you are connecting Pocket POD to a computer running Windows XP or Vista but cannot see any ports in the Ports dialog, there is a possibility that you also have Logitech (or other company’s) webcam, laser mouse or wireless mouse drivers that are conflicting with the Windows USB MIDI driver. The problem Logitech driver is called LVUSBSTA.SYS. Here is a procedure to clear out this driver from your Windows XP system, but bear in mind that it involves editing your registry which requires extreme care. Psicraft Designs and/or Line 6 will not be responsible if you mess up your windows installation while following these instructions , so if in doubt have a qualified friend perform these steps! 1. Run Regedit from the Windows Start->Run… Menu. 2. Navigate to the following key: HKEY LOCAL MACHINE /SYSTEM /CurrentControlset /Control /Class / {6BDD1FC6-810F- 11DO-BEC7-08002BE2092F} 3. Click on this key and delete the "LowerFilters" item. 4. Navigate to the folllowing key: HKEY LOCAL MACHINE /SYSTEM /CurrentControlset /Control /Class / {6BDD1FC5-810F- 11DO-BEC7-08002BE2092F} 5. Click on this key and delete the "UpperFilters" item. 6. Return to the root of HKEY LOCAL /MACHINE /SYSTEM /CurrentControlset /Control /Class / 7. Launch a search (i.e Ctrl-F with the option to search in "Data") and type "LVUSBSTA". Any time this is found in the "Control / Class" area of the registry, only delete the "LowerFilters" item (which is where LVUSBSTA will be found). Now your class-compliant USB MIDI port driver should be operational.

So, I got it fixed, and I think what made the difference was manually downloading Flash Memory 1.01 and loading the file from my computer into Line Monkey. You ca find the update file by in the downloads Downloads section. Select Pocket Pod from the list of products and you'll find it in the results.

I had same problem and I manually dowloaded the flash memory file and updated from file as was describe above. Thanks to God it went smooth and now it is working. Guys just do what I have done. Download manually from web page and upload from file than try. After it finishes new pop up screen say restart the POD but on POS's scree it says wait for reboot. So Do not forget to wait for reboot after update and Do not disconnect ust wait. When it is rebooted it will be fine.

The information above may not be current, and you should direct questions to the current forum or review the manual.