infinity problems

[dogrusty]

its weird. i just recently got the inifnity chip in my ps2 and the first time i tried it the chip didnt work. Later on i put a burnt game in and it did. It just radomly works and doesnt work and most of the time it doesnt. Is there neting i can do myself 2 fix this

[EspeN]

What about check if any connetion is loose? sounds like it.
Is this a real Infinity or clone?

Your ground wire or power wire might be too long.

[danwood76]

yes as tony said shorten the gound wire, you should try and keep all the wires as short as possible to reduce the amount of interferance

regards,
Danny

[exwilliam]

I had this pb w/ clones(MoboV1.1,V1.2).If you're using clone MI so there's nothing you could do.but if the chip is the real Mi so dont worry,just reduce the length of ground wire and/or Vcc wire and it will be OK.

[ps2dragon]

Originally Posted by dogrusty

its weird. i just recently got the inifnity chip in my ps2 and the first time i tried it the chip didnt work. Later on i put a burnt game in and it did. It just radomly works and doesnt work and most of the time it doesnt. Is there neting i can do myself 2 fix this

I seem to be having the same problem. When I leave my system off for a while and then turn it back on, it doesn't detect any backups. Then later when I try it works again. Although the time it takes to work seems to be getting longer. Can you lay down some specs about your PS2 system and the chip etc? My PS2 was purchased as a pre-mod.

Originally Posted by ps2dragon

I seem to be having the same problem. When I leave my system off for a while and then turn it back on, it doesn't detect any backups. Then later when I try it works again. Although the time it takes to work seems to be getting longer. Can you lay down some specs about your PS2 system and the chip etc? My PS2 was purchased as a pre-mod.

Who did you buy it from? The installer might have done a sloppy job making the chip unstable.

[ps2dragon]

I got this pre-mod from a Chinese guy in a flea market nearby in Scarborough, ON. I know I should never of bought it from a flea market, but he said he would give me 3 months warranty, I got four free games and he sounded like he knew what he was talking about at the time. Guess I have to learn the hard way. He's already replaced the original cloned mod, with an original Matrix Infinity v1.39. It originally had a clone with firmware 1.38, until I realized it was a clone after changing the settings and then it malfunctioned. I've been having nothing but problems ever since I bought this thing from him. The problem is I don't have a receipt for it. I know now I should of gotten one, but I never bought anything big like this from a flea market before. What makes it worse is it's only open on Saturdays and Sundays from 10am-6pm. He says he told me it was a clone before I bought it, but that was only just before I left and was asking if it was a Matrix (cause it said "Infinity" at the loading screen). At the time I didn't know clones existed, and he definitely didn't warn me that changing the settings would stop the chip from working. I had to pay up an extra $50 CAN for the original Matrix Infinity (which is what I wanted in the first place). He told me the Romeo MOD would fix all the laser issues and version 9 was the best version to install the Matrix Infinity in, which is why he used the version 9 and not a version 7 console. After I got the system I upgraded the firmware to v1.54, and shortly after I started having the loading problems. This is why I started the thread "Matrix Infinity - Problems with Firmware 1.54?", because I wasn't sure if the firmware would cause this to happen or not. I wanted to isolate the cause, so I can tell him when I bring it back and know what I'm talking about. At this point I'm ready to demand my money back for this piece of junk he sold to me.

I recently ran a test using games from different sources. After leaving my system off for a day I immediately tried a backup I made (burned at 4X with my Sony DW-D22A burner) which has worked fine before on this system. I immediately got the red screen asking for a valid disc. Second I tried a backup I bought from this Chinese guy at the flea market, and I got the red screen again. Then I tried an original game that worked of course. Then I tried my backup again and it immediately worked. It seems like I need to get the laser to read something before reading backups now. Previously when trying it a few days ago, I first tried my backup which never worked even after approx. 7 tries. Then I tried the backup I bought from this Chinese guy and it worked, then I tried my backup again and it worked. But now I have to put in an original game first, just to get my backups to load. What would cause this?

I believe this is the whole story now... : /

[EspeN]

This is a little off topic, but the same thing happend to a GameCube i modded once with the Qoob SX chip.. After 30 minutes - 1 hour, if you tried to reboot the machine it didnt work with backups untill it was "cold".

I was pretty sure it was the chip that got too much heat, so i got it back, dissassembled it and found out that i had accidently removed a resistor on the board. I didnt notice before i inspected the board.. But the console worked anyways, but i guess it had heat issues. I have no idea about this, just wanted u to know exact same happend to me with a gamecube. I replaced the customers mobo with a brand new chip and gamecube, just for the record

Originally Posted by ps2dragon

I got this pre-mod from a Chinese guy in a flea market nearby in Scarborough, ON. I know I should never of bought it from a flea market, but he said he would give me 3 months warranty, I got four free games and he sounded like he knew what he was talking about at the time. Guess I have to learn the hard way. He's already replaced the original cloned mod, with an original Matrix Infinity v1.39. It originally had a clone with firmware 1.38, until I realized it was a clone after changing the settings and then it malfunctioned. I've been having nothing but problems ever since I bought this thing from him. The problem is I don't have a receipt for it. I know now I should of gotten one, but I never bought anything big like this from a flea market before. What makes it worse is it's only open on Saturdays and Sundays from 10am-6pm. He says he told me it was a clone before I bought it, but that was only just before I left and was asking if it was a Matrix (cause it said "Infinity" at the loading screen). At the time I didn't know clones existed, and he definitely didn't warn me that changing the settings would stop the chip from working. I had to pay up an extra $50 CAN for the original Matrix Infinity (which is what I wanted in the first place). He told me the Romeo MOD would fix all the laser issues and version 9 was the best version to install the Matrix Infinity in, which is why he used the version 9 and not a version 7 console. After I got the system I upgraded the firmware to v1.54, and shortly after I started having the loading problems. This is why I started the thread "Matrix Infinity - Problems with Firmware 1.54?", because I wasn't sure if the firmware would cause this to happen or not. I wanted to isolate the cause, so I can tell him when I bring it back and know what I'm talking about. At this point I'm ready to demand my money back for this piece of junk he sold to me.

I recently ran a test using games from different sources. After leaving my system off for a day I immediately tried a backup I made (burned at 4X with my Sony DW-D22A burner) which has worked fine before on this system. I immediately got the red screen asking for a valid disc. Second I tried a backup I bought from this Chinese guy at the flea market, and I got the red screen again. Then I tried an original game that worked of course. Then I tried my backup again and it immediately worked. It seems like I need to get the laser to read something before reading backups now. Previously when trying it a few days ago, I first tried my backup which never worked even after approx. 7 tries. Then I tried the backup I bought from this Chinese guy and it worked, then I tried my backup again and it worked. But now I have to put in an original game first, just to get my backups to load. What would cause this?

I believe this is the whole story now... : /

Ok, you made your first mistake and you learn something from it.

I don't know if it's the laser or not but it certainly sounds like it. You should try media like Ritek or Verbatim and burn it at 2x. Try that see if it works.

[ps2dragon]

---------------------------------------------------------------------------
Unique Disc Identifier : [DVD-R:RITEKG04]
---------------------------------------------------------------------------
Disc & Book Type : [DVD-R] - [DVD-R]
Manufacturer Name : [Ritek Co.]
Manufacturer ID : [RITEKG04]
Disc Application Code : [Unrestricted Use : Consumer Purpose]
Recording Speeds : [1x , 2x , 4x]
[6x And Higher Might Not Always Be Detectable]
Blank Disc Capacity : [2,298,496 Sectors = 4,489.3MB = 4.38GB (4.71GB)]
---------------------------------------------------------------------------
[ DVD Identifier - http://DVD.Identifier.CDfreaks.com ]
---------------------------------------------------------------------------

It's not the media, because I have been burning on Ritek, it's labled Ri-Data but the info for the DVD says it's manufactured by Ritek. I also have been testing the discs I bought from the guy who sold me the PS2. He also says to use Ritek or RiData which is what his backups are burned on also. The point is it used to work right away when i first bought it.. but now I have to wait for it to work. I also asked him yesterday if maybe his wiring was too long, but he said it was just enough to fit meaning it should be good. I'm going to have to bring it back to him later today for a week to see if he can find what is wrong with this damn thing.

I tested his backups and mine which both gave the same results when first trying it after it's been off for a long time. Non of his customers have problems with his backups, if they did, he wouldn't be able to sell them. I also tried going back to firmware 1.39, which still gave me the same problem when testing the backups.