No idea why, just do it and you will know if its a clone or not. If it flashes fine you dont have a clone

It it flashes and stops 30% through flashing the chip, its a clone. Problem solved
QUOTE
just do it and you will know if its a clone or not.
Well I have news for you. Some of the Blue genuine ones do this when flashing through evox (not through any other flash app)
Before you say it, They are NOT clones and yes I do know the difference and I also know my supplier personally.
Tested on 2 out of a batch. will try some more when I have time
Hippo or anyone else that knows a hell of alot about flashing (techs only) ,
OK. Urm i don't understand .. i mean i program PIC chips and the like all the time , i understand the gates and the software and eeprom etc. But how can one 512k BIOS ( which is just 0's and 1's ) flash ok (X2 4981) for example but a new bios not flash ( which is also 0's and 1's ).
Clock cycles and timing would be down to cpld code problems not SST chip contents. Unable to flash in evox should not only happen with certain bioses ( in my opinion anyway )
I have had a few too many right now so i will quit rambling any further untill tomorrow !
Hack !
Ya know everyone's modchip is sort of secret you would have to ask them what they have in mind.
Here's a bump for those that may have missed this. The Duo X2 lite should hopefully take care of the cloners.
Just out of interest I believe that I have a genuine (or very, very, very good clone) with the same can't-flash-me (Write Protected 0x09, 0x00) errors.
It looks as if they are genuine because:
Has XILINX FPGA
Has what appears to be genuine AMD Flash chip
Switch is flush with 3 x holes underside
Gold Pads & Gold Logo
I purchased 2 x Duox2 Cromwell edition from mod-chip.com - results:
Chip #1:
Can't flash using Eurasia or Flashbios 3.0.3 - on 1.6 Xbox using either M8 or M8_1.6 BIOS - error is "Read Only?? manuf 0x09 device 0x00"
Can't flash using Eurasia or Flashbios 3.0.3 - on 1.4 Xbox using either M8 or M8_1.6 BIOS - error is "Read Only?? manuf 0x09 device 0x00"
Can't flash using hotswap on 1.6 or 1.4 with EvolutionX latest (Slayer or X-Wizard disc) - using either M8 or M8_1.6 BIOS - error is "Flash is protected"
Chip #2:
Chip works fine in all above scenarios ...
So I'm wondering if there might be either:
a) an inherent programming fault in the FPGA/CPLD
-OR-
an inherent design problem with the board itself where one or more signals aren't fed to the chip ...
-OR-
c) something completely different
Just my 2c
interesting feedback but you should post a picture...
All it takes is one bad (cold) joint on the female headerpin that is soldered directly to the duox2 and this would cause this condition !
HackDaBox !
I agree with Hack, I had a bad lpc pin on an Alladin that was keeping it from flashing.
QUOTE(knives77 @ Jul 4 2005, 09:49 AM)
2 Clones DuoX2 killing 2 Xbox, 1 v1.4 and 1 v1.6
I've noticed any clone talk at all in the other forum sections gets a thread closed.
QUOTE
I've noticed any clone talk at all in the other forum sections gets a thread closed.
Threads promoting clone chips are closed. This thread appears to be warning people how to identify a clone rather than promoting sale and distribution of Clones.
If you have a specific issue with this thread you can use the report button and state what and I will look at it for you
No problems when put under that light except it was started by a clone dealer so it makes it a tad confusing if it's to enlighten or promote. I wouldn't report the thread though it's pretty harmless.
Also that doux 3 scares the hell right out of me. Do you know how much more expensive it is to make? Holy cow.