View Full Version : I flashed my X1900 Crossfire with an X1300 bios
W1zzard
Jan 28, 2007, 07:11 PM
lolz stupid me *shoot self in head*
http://reference.techpowerup.com/Fixing_a_completely_gone_wrong_ATI_BIOS_flash
sneekypeet
Jan 28, 2007, 07:12 PM
nice one.......lol
DaMulta
Jan 28, 2007, 07:17 PM
http://w1zzard%20.justgotowned.com/
LOL At lest you had an idea on how to fix it.
W1zzard
Jan 28, 2007, 07:20 PM
LOL At lest you had an idea on how to fix it.
i didn't .. but i didn't want to accept "paperweight" either
DaMulta
Jan 28, 2007, 07:23 PM
ATI's flashing programs query the device ID to know which GPU to expect
Could you of edited the program to identify the the new ID code?
Steevo
Jan 28, 2007, 07:31 PM
Brave soldier. Or is that solder?
Anyone ever figure out what the extra molex connectors are for the on these cards however?
W1zzard
Jan 28, 2007, 10:04 PM
Could you of edited the program to identify the the new ID code?
yep i looked into that as well but it was more complicated because i would have to find all places and there are also some places where it checks for 42** which are extremely hard to find
AshenSugar
Jan 28, 2007, 10:12 PM
good thing you had the skillz to recover from that lol.
i flashed an 9800 with 9500bios, but i was able to recover that by hot swaping cards using an old card i had laying around (ati something or other) i know, hotswaping cards for such reasions isnt the best idea but i was depret, i wanted my 9800se>pro@xt back :P
Zubasa
Jan 29, 2007, 12:52 AM
lolz stupid me *shoot self in head*
http://reference.techpowerup.com/Fixing_a_completely_gone_wrong_ATI_BIOS_flash
Aiya:respect:
Hope you can flash it back:p
i_am_mustang_man
Jan 29, 2007, 01:30 AM
so you fixed it already? gnar dude
you'da had the fastest x1300 evah
Frogger
Jan 29, 2007, 04:20 AM
lolz stupid me *shoot self in head*
http://reference.techpowerup.com/Fixing_a_completely_gone_wrong_ATI_BIOS_flash
:respect: going to file that fix for future ref :respect:
AshenSugar
Jan 29, 2007, 04:33 AM
humm, i remmber when u could rename ur card in the 9800 days, i made mine say it was a 9600 and had people freaking out on another forum (they where all posers i wanted to mess with them ;) )
tkpenalty
Jan 29, 2007, 09:53 AM
Oh dear... I can't imagine someone like W1zzard doing something like this T_T.
EDIT: I did something this stupid once... backing up data on my mobile rack drive, it then finished (I thought) and I PULLED THE MOBILE RACK OUT WHILE THE PC WAS ON. Saving grace was that the data wasnt lost, but I had to merge some files (lol half an EXE) together.
{Sniping}Waste
Jan 29, 2007, 03:40 PM
Thats much easier then what Im doing. I unsolder the 8 pin EEPROM and hot flash it on another card then solder the EEPROM back. THank for finding a easier way.
bokis
Feb 7, 2007, 01:35 PM
lolz stupid me *shoot self in head*
http://reference.techpowerup.com/Fixing_a_completely_gone_wrong_ATI_BIOS_flash
This is very interesting could you read my posts in this tread and tell me your opinion
http://forums.techpowerup.com/showthread.php?t=699
post #35 #39
niko084
Feb 7, 2007, 04:02 PM
Heh now figure out how to flash my x1300 to a x1950! And make it WORK! :)
Donk23
Feb 13, 2007, 12:31 PM
IT'S ALIVE!!!!
THANKS MAN!!!
I hade a X800Pro AGP flashed with an PCI-E bios...
http://forums.techpowerup.com/showthread.php?t=23637
And now it is back working by doing you pin-1-8 soldering trick!
THANK MAN!!!
sobol
Aug 23, 2007, 09:55 PM
W1zzard
First of all, I had bad flash on my X1900XTX with X1950 PRO bios.
I was curios about this atiflash options:
-scansii , siireset and siiuprog
My card was reporting this:
atiflash -ai -sst
Adapter 0 (BN=01, DN=00, PCIID=72C1102, SSID=E190174B )
ASIC Family : RV5XX
FLASH TYPE : SiI 1930
Firmware Version : 0.0
Firmware Variant : 0
And then I've done that:
atiflash -p 0 orig.rom -siiresrt=1 -siiuprog=1 -scansii
Actually that reported fail and that 0% was flashed but probably it was enough.
After this I've tried your method as above didn't work and I think I've screwed my card.
I used your pin reset method and mange to flash back to original bios.
Now the card is working and booting up but I've got serious screen corruption.
Any ideas ?
Thing is that just before that pin flash I've tried normal flash:
Chat1000
Dec 29, 2007, 05:31 PM
I have the same problem. I have flash a BIOS on my new GeCube 3850 TurboX III, and now atiflash/ flashrom says "ati adapter not found".
Somebody know where i can find the bios chip of the 3850?
Can be that one?: http://www.datasheetcatalog.com/datasheets_pdf/A/T/2/4/AT24C08AN-10SI-2.7.shtml
tigger
Dec 29, 2007, 05:39 PM
Look for a small 8 pin chip like this-
http://img.techpowerup.org/071229/ASUS009.jpg
It could be a st chip,maybe 25PXXXXX number.
Can you post a pic of the back of your card?
Chat1000
Dec 30, 2007, 09:39 AM
There are 6 8pin chps on the back side of the card :cry:
first: 2times
LM137
PALGL
second: 2times
uP7706U8
PCP78H
third: 1time
uP6101BU8
V6U797
fourth: 1time (on that one, there is the nuber 58 writed from hand on it)
ATMEL702
25F512AN
SO27 or SU27
[img=http://img508.imageshack.us/img508/7381/img0283aja7.th.jpg] (http://img508.imageshack.us/my.php?image=img0283aja7.jpg)
This is not my card, but it looks almost like mine.
tigger
Dec 30, 2007, 11:39 AM
I think the eeprom is this one-->25F512AN
http://www.datasheetcatalog.net/cgi-bin/helo.pl?field=Nume&type=C&text=25F512A&producedby=&action=Search
Chat1000
Dec 30, 2007, 11:45 AM
I think the eeprom is this one-->25F512AN
http://www.datasheetcatalog.net/cgi-bin/helo.pl?field=Nume&type=C&text=25F512A&producedby=&action=Search
I think so too.
I have connected pin 1 and 8, but atiflash still says no adapter found. :(
Is it allways pin 1 and 8 or it can be other too? Im from garmany and dont understand the data sheet
tigger
Dec 30, 2007, 12:01 PM
Try asking w1zzard.that is a differant eeprom to the ones on the 1900/1950 cards.
Chat1000
Dec 30, 2007, 12:05 PM
ok thank you, i will write w1zzard a PM
I have a idea:
If i connect the Output of the eeprom with ground, then the voltage on Output is 0V and this is like the eeprom is empty. And then i can flash the original bios and otherwrite so the old data.
Is it possible that that work?
Arcanis
Jul 21, 2008, 12:14 PM
Hi!
I'm new around here and visited this thread because my X1800GTO died from a bad flash.
Same problems, can't be detected by atiflash, but I did your trick and indeed the flashing program now detects it! That gives me a little hope of repairing it :D, I'll try to flash it when I get back home :eek:
Anyway, you can't bridge the output with ground, that would fry the eeprom. The only thing you could do is disconnect the output from the card, but that means lifting a pin, out of the question I guess.
Disabling the chip is a secure manner, because you can safely feed the CSn input with either Vcc or GND (3.3/0 [V]). God bless the eeprom works with the spi protocol :D
Edit: Eww, didn't see I posted on a really old thread, google's fault!
mullered07
Jul 21, 2008, 12:19 PM
Edit: Eww, didn't see I posted on a really old thread, google's fault!
lol talk about brought back from the dead, wiz will be pleased :laugh:
mystikl
Apr 12, 2009, 02:09 PM
I'm resurrecting this thread because the page: http://reference.techpowerup.com/Fixing_a_completely_gone_wrong_ATI_BIOS_flash is empty, and I ran out of ideas on how to flash my 2400 XT. The EEPROM on it is a PM25LV512 chip, if that helps in any way.
Vargtass
Apr 12, 2009, 03:39 PM
Hi there,
article text below.
PM me, I'll send you a PDF of the guide (incl. images)
Fixing a completely gone wrong ATI BIOS flash
From TPU Reference
The other day I was trying to recover a Radeon X1300 which was flashed with the wrong X1300 BIOS.
To do that I put an X1900 CrossFire (first card I had handy) into the primary PCI-E slot and the X1300 into the secondary
slot.
As always I was in a hurry so I ran: atiflash -f -newbios -p 0 x1300.bin
Heart Attack!! Realize what just happened?
The 0 stands for adapter 0 which is the PRIMARY card, so my X1900 CF now had an X1300 BIOS on it.
So I thought, I'll just flash it back... Problem: the X1900 CF PCI device ID changed from 7249 to 7346. ATI's flashing
programs query the device ID to know which GPU to expect, so the software can use the right flashing method.
Unfortunately a device with 7346 doesn't exist at all so ATIFlash didn't even show the card as installed.
The only way I could imagine how to fix this is by disconnecting the flash memory somehow so that the device ID does
not get changed (all ATI GPUs have a default value which can be overwritten by the ROM. Not all bits can be changed,
that's why I ended up with 7346 instead of a real X1300 device ID).
This is the flash ST 25P05 flash chip of the X1900 CrossFire. It is identical to the M25P05 for which you can easily find
the datasheet online.
Unsoldering the chip was out of question, it is way too small to do with my equipment. Another idea I had was
unsoldering just one pin, but that's very hard as well with all the other components around. Also when trying to lift a pin
you often lift the PCB trace with it which pretty much means dead card.
Fixing a completely gone wrong ATI BIOS flash - TPU Reference http://reference.techpowerup.com/Fixing_a_completely_gone_wrong_A...
2 of 2 30.12.2007 17:53
The datasheet was talking about pin 1 being "Chip Select". When a low voltage is present at pin 1, the flash memory is
active and will respond to read/write requests. When a high voltage is present it will go to sleep mode - exactly what I
need.
The "high" voltage can be grabbed from pin 8 which is the +3.3V supply voltage of the IC. So I soldered a wire from pin
1 to pin 8 in hopes that the card would now be unable to read the flash memory. Problem: after booting the flash chip
can't be accessed for _writing_ the backup flash because I disabled the whole flash chip with the wire. So I deliberately
created a weak solder joint on pin 8 that would break with a very slight twist.
After crossing fingers and powering on (this time CF card in secondary slot, another card in master to boot from)
ATIFlash did indeed detect the card. Yay I can flash my old BIOS back! Before starting the flashing process I wiggled on
the cable and the pin 8 connection did come off and the chip could be accessed by the flashing program.
Woohooo. Card is alive again and can be abused now for further benchmarking.
Retrieved from "http://reference.techpowerup.com/Fixing_a_completely_gone_wrong_ATI_BIOS_flash"
Category: Guides
This page was last modified 20:57, 16 December 2007 by Jimmy 2004. Based on work by W1zzard and Anonymous
user(s).
This page has been accessed 2,507 times.
Privacy policy
About TPU Reference
Disclaimers
mystikl
Apr 12, 2009, 09:21 PM
Just to make things clear: all I have to do is connect pin 1 and pin 8 on the chip, then disconnect them before flashing the card?
And can someone tell me how do I tell which pin is 1 and which pin is 8?
largon
Apr 13, 2009, 10:19 AM
Unfortunately, finding which pin is 1 and which 8 are the easiest steps of the process.
Hitting "M25P05" in Google (http://www.google.fi/search?&q=M25P05&) will get you started.
mystikl
Apr 13, 2009, 02:54 PM
The card is up and running, soldering the wires was a pain in the a** but it worked like a charm.
Couldn't have done it without W1zzard's crazy technique and Vargtass's help.
Zigu
Nov 26, 2011, 10:49 AM
Hi, could someone please help me? I have 2 cards: ati 4890 and 5970 which both have the wrong bios. I tried to solder the wires connected to the pins, but i`m not sure if they are the right ones (pin 1 and 8). How can i recognise the right pins? Do i need to connect pins 1 and 8 of all the chips on the card or just some of them? Sorry, I know this is an old thread but i`m getting a bit desperate..
NdMk2o1o
Nov 26, 2011, 10:52 AM
Hi, could someone please help me? I have 2 cards: ati 4890 and 5970 which both have the wrong bios. I tried to solder the wires connected to the pins, but i`m not sure if they are the right ones (pin 1 and 8). How can i recognise the right pins? Do i need to connect pins 1 and 8 of all the chips on the card or just some of them? Sorry, I know this is an old thread but i`m getting a bit desperate..
I cannot help you with your problem, however I suggest you start a new thread as opposed to resurrecting a 4 year old thread with little relevance.
vBulletin® v3.8.6, Copyright ©2000-2013, Jelsoft Enterprises Ltd.