Search the Community
Showing results for tags 'boot loop'.
Found 3 results
-
Hello. After a catastrophy (power glitch I guess), I'm stuck in a boot loop with the Line 6 screen being displayed, then flashing, then Line 6 screen again (in a loop). My POD HD500X returns a bad USB ID, so I cannot connect via USB to install firmware. The USB ID I read is USB\VID_04B4&PID_8613&REV_:001, which is the Cypress USB chip's ID. I cannot connect to restore the firmware (with monkey) because Windows does not recognize it as a HD500X. I gather this might be a case for an EEPROM or Flash reprogram. Thing is I'm a bit far from the service center. Is there any way I could get something (software) to reprogram the EEPROM or flash ? or get replacement chips ? (I gather not, but hey, it's worth a try). Otherwise, does this sound like something the service center could (easily) help with ? Additionally: all diagnostics pass (right arrow on power up) What might also help is if someone could check the IDs they get in Windows Device Manager for the HD500X (I suspect something like 0E41&PID_4159). Thanks. Dan
-
A couple of weeks ago the USB quit in my HD 500. Now the unit is in a boot loop and when I run the diagnostics the SDRAM test never finishes. Is there a document that tells how to use the diagnostic mode? Monkey can't see it to re-flash. There are no service center within 300 miles of here. Is there a document that tells which chips are the SDRAM? Is there a document that tells how to use JTAG To diagnose this? or am I stuck and now just need a new unit? Since I am a loyal Line 6 Customer (POD 2.0 , SPIDER VALVE I and II, POD HD and HD 500, JT Variax) maybe they can cut me a deal on a helix? Does anyone know what the reliability of the helix unit is like?
-
Hello, i have a problem with my pod hd. The pod hd has a starting loop!!!! It chrashes and starting new, then the POD crashes again and starts new.... I have the pod connected to my win10 pc and i can record some takes, so long as the POD crashes again :( I have the newest firmware and usb drivers. I have tested older firmware via rollback but nothing helps. The porblem also occur when the pod is not connected to my pc. Can anyone help me?
