Hello All,
I recently bought an Xecuter 2.6 LITE with an Xapter solderless adapter. I followed the Xapter install tutorial, and everything was install right, but when I went to boot up my box, it FRAGed. It works fine with the chip off. The only thing wrong I did was I put the chip on backwards (meaning the holes with no pins inserted faced the controller ports).
Soon after that, I placed the chip on correctly. I began to think the chip was fried, but had already ordered a pc flasher before I realized this. So, I plugged on the chip on the programmer and it read the memory. Then I flashed X2 bios on bank 1 and 2, and Flashbios 3.03 on banks 3 and 4. Wrote ok, but when plugged into the box, it still fragged. My question to you is could the chip be fried? Or is there a way to repair it? If it's toast, my new Xecuter 2.6 (and the new Xapt3r since the Xapter broke shortly after flashing via pc
) will be here on Monday. NOTE: I looked through the forums for a problem like mine, but I couldn't find that occured with my version of box (I only found problems on 1.0, 1.1, and 1.6, no 1.2-1.5).
Thanks,
-Njh
I recently bought an Xecuter 2.6 LITE with an Xapter solderless adapter. I followed the Xapter install tutorial, and everything was install right, but when I went to boot up my box, it FRAGed. It works fine with the chip off. The only thing wrong I did was I put the chip on backwards (meaning the holes with no pins inserted faced the controller ports).
Soon after that, I placed the chip on correctly. I began to think the chip was fried, but had already ordered a pc flasher before I realized this. So, I plugged on the chip on the programmer and it read the memory. Then I flashed X2 bios on bank 1 and 2, and Flashbios 3.03 on banks 3 and 4. Wrote ok, but when plugged into the box, it still fragged. My question to you is could the chip be fried? Or is there a way to repair it? If it's toast, my new Xecuter 2.6 (and the new Xapt3r since the Xapter broke shortly after flashing via pc
) will be here on Monday. NOTE: I looked through the forums for a problem like mine, but I couldn't find that occured with my version of box (I only found problems on 1.0, 1.1, and 1.6, no 1.2-1.5).Thanks,
-Njh
Last edited:
