viper lid detection bypass problem
|
|
sonnytv
Newbie
|
10. February 2005 @ 18:51 |
Link to this message
|
I just got and installed my viper chip but the problem I am having is that it wont read a disk with the cover off. Any suggestions would be great. Thanks.
|
Advertisement
|
|
|
Lazycus
Newbie
|
10. February 2005 @ 19:46 |
Link to this message
|
Go into your COBRA configuration menu and change the lid sensor setting to 'closed'.
|
sonnytv
Newbie
|
10. February 2005 @ 20:13 |
Link to this message
|
I cann't get the gc to recognize the viper chip. When I program the chip my computer doers recognize the gc. When I boot it up it just goes directly to the game. No viper screen or anything. Have checked my connection with muti meter multiple times. Going to check them again. Starting to get very frustrated. Any other suggestions would be appreciated.
|
Lazycus
Newbie
|
10. February 2005 @ 20:28 |
Link to this message
|
Well now, that's a different problem entirely. If you are sure your soldering is good on the GC mainboard then make sure the connector is firmly in place on your Viper chip board and test the connections all the way back to that board. Double check that you made all soldered connections to the proper locations. Is your programmer still connected? If it is make sure it's not in stealth mode (programmer DIP switch 1 in ON position).
|
sonnytv
Newbie
|
10. February 2005 @ 20:50 |
Link to this message
|
I have checked my connections all the way to the cobra chip connector and they seem to be fine. I must be missing something simple I am sure. I have the 3 connections and the bridge on the top of the mother board and the yellow wire to the second leg on the bottom of the mother board. I don't see any cross connections or anything. I am wondering if maybe I have a corrupted flash. Or woul thw gc still at least recognize it with a black screen. Thanks for your help.
|
speedi
Junior Member
|
11. February 2005 @ 00:27 |
Link to this message
|
Check if the Cables are perfecty connected in the vper Chip (that thingy with all the cables sticking out of it)
then It should be Ok .. or else I have no logical explination
Greetings
Speedi
|
sonnytv
Newbie
|
11. February 2005 @ 07:57 |
Link to this message
|
Anyone have any other suggestions?
|
Lazycus
Newbie
|
13. February 2005 @ 07:28 |
Link to this message
|
Fire it up with the cover off and take a look. Is your Viper chip getting power (red & black wires) when measured with your multi-meter? Did you verify your chip was flashed correctly? If your BBA is connected try pulling it out just to experiment.
|
sonnytv
Newbie
|
13. February 2005 @ 07:42 |
Link to this message
|
I will check the power but I believe it is working because viper loader sees the gc when the power is on. But from what I am reading I think it may be a flash problem. Is there a way to verify for certain that the chip is flashed?
|
grmbl
Member
|
13. February 2005 @ 09:37 |
Link to this message
|
Had this problem too... just change the 2 dipswitches on the Viper Programmer.
grtz
Writer: Lite-on DVDRW LDW-851S
Media: Memorex Pocket DVD-R 1.4GB
Cube: PAL Revision 1.0 (Platinum Version w. LoZ:TWW)
Drive version date is 23/08/2002 (61)
GC version code 18 DOL-001
ViperGC BIOS version 1.0 =)
|
sonnytv
Newbie
|
13. February 2005 @ 11:32 |
Link to this message
|
I have tried to switch dip switches all different ways. Nothing. I tried on a differnt cpu. Nothing. I have no idea. About ready to fix it with a BFH.
|
Lazycus
Newbie
|
13. February 2005 @ 12:15 |
Link to this message
|
Quote: Is there a way to verify for certain that the chip is flashed?
Use the 'compare' function in the Viper flash utility.
Try these before you take the hammer to it:
- Remove the programmer entirely.
- Recheck the yellow wire again. Make sure it is connected to the correct pin on the correct chip on the correct type of mainboard (A/B or C). Make sure it does not touch any other pins, anywhere on the board or any metal at all.
- Remove your BBA if it is plugged in.
- Remove the Viper connections and re-solder.
Hammer time?
|
grmbl
Member
|
15. February 2005 @ 04:21 |
Link to this message
|
Yep, check soldering and lid bypass connection in your gamecube...
Writer: Lite-on DVDRW LDW-851S
Media: Memorex Pocket DVD-R 1.4GB
Cube: PAL Revision 1.0 (Platinum Version w. LoZ:TWW)
Drive version date is 23/08/2002 (61)
GC version code 18 DOL-001
ViperGC BIOS version 1.0 =)
|
indienemo
Account closed as per user's own request
|
15. February 2005 @ 05:03 |
Link to this message
|
apprntly 1 in 5 viper chips are faulty from the start.
"Life is like a box of chocolates, whenever it comes to me all that is left is toffee logs" - Me.
------------------------------------------------------
PC: Athlon 64 X2 4200+ @ 2.4Ghz, 2GB DDR2, X850 PE GFX.
GC: Viper GC w. Cobra bios 1.2
X360: Kreon 1.0 Drive, Softmodded console
|
grmbl
Member
|
15. February 2005 @ 05:15 |
Link to this message
|
Hell, i hate my lack of a digital camera!!!
First priority: buying one.. lol
update: got myself a Casio Exilim EX-S2 today!
Writer: Lite-on DVDRW LDW-851S
Media: Memorex Pocket DVD-R 1.4GB
Cube: PAL Revision 1.0 (Platinum Version w. LoZ:TWW)
Drive version date is 23/08/2002 (61)
GC version code 18 DOL-001
ViperGC BIOS version 1.0 =)
This message has been edited since posting. Last time this message was edited on 16. February 2005 @ 11:01
|
morphx
Junior Member
|
17. February 2005 @ 00:26 |
Link to this message
|
I have checked my connections all the way to the cobra chip connector and they seem to be fine. I must be missing something simple I am sure. I have the 3 connections and the bridge on the top of the mother board and the yellow wire to the second leg on the bottom of the mother board. I don't see any cross connections or anything. I am wondering if maybe I have a corrupted flash. Or woul thw gc still at least recognize it with a black screen. Thanks for your help.
I read your post and from what i gather,you have a Dol101 version gamecube aka C board not a Dol001 aka a/b board vipers are not compatible with the board you have,i picked up on it when you said the second leg where you solder the yellow wire was on the "bottom" of the board and not on the top of the board like a/b boards.
I don't know of any fix for this issue,just hope and pray tha the viper team and cobra address it.
premodded playstation 2 w/magic 3.1 mod chip installed
premodded xbox w/duox2 modchip installed
1.5 modded PSP
|
zerman
Newbie
|
17. February 2005 @ 09:09 |
Link to this message
|
I have exactly the same problem: gamecube works like original BIOS. I don't know what to do... should i return the modchip? I don't understand, many people have problems, but videogame news webpages reviews are good, it seems nobody in that pages had problems, like in the few guides that exist to help installing it... is just "now install, now write it, now play! 10/10" :s
My gamecube is a DOL-001 (europe)
|
zerman
Newbie
|
23. February 2005 @ 10:58 |
Link to this message
|
OK i have a friend that installs modchips, he came at my house, installed the modchip as it should be, verified every connections, if there were broken wires, etc etc, everything looked good... but machine run the original bios... he took my cube to his home to try to see what's happening. He also tried with a diferent chip, nothing :(
I thing the chip can't overrun original BIOS. I say this because when i turned on the cube after his installation, the original BIOS started with a bit of interference, but then it stabilized.
Anyone does know anything about this? Not power enough maybe? Morphx, are your chip alright?
|
molton
Junior Member
|
23. February 2005 @ 12:14 |
Link to this message
|
I thought my mod chip was dead, I couldn't get a hold of the flasher program because every link for it went to ps2ownz, and apparently they have a problem with hotmail, anyway, I thought the viper chip was supposed to do something right off the bat, but it loaded as if I hadn't installed it, and the flasher I could get, that open source one, said it couldn't see my modchip. Eventually I found the right flasher and put the cobra bios on the mod chip, I really wish they told you it didn't do anything until you re-flash the bios. Now none of my games work for longer than a couple minutes before the read errors start, but I guess that's another topic altogether.
|
Advertisement
|
|
|
indienemo
Account closed as per user's own request
|
23. February 2005 @ 12:27 |
Link to this message
|
Im getting loads of those bloody errors as well... and i cant even write those mini dvd-r discs 75% of the time, I was so pissed off I even started a thread on it
"Life is like a box of chocolates, whenever it comes to me all that is left is toffee logs" - Me.
------------------------------------------------------
PC: Athlon 64 X2 4200+ @ 2.4Ghz, 2GB DDR2, X850 PE GFX.
GC: Viper GC w. Cobra bios 1.2
X360: Kreon 1.0 Drive, Softmodded console
|