They're different sizes so the checksums aren't identical, but the first page of characters looks identical. Should I go ahead with flash? Basically the BIOS file is 1.04MB, while the chip's dump is 1.0MB Well, I've tried writting to the chip, but get a verify failed error after the write. Now I'm just wondering if I should put the chip back on and see if the PC boots... and if it does maybe I should reflash via the PC to be sure??? ...and if it doesn't boot, well then I guess it's time to pay for some repairs. last edit... I take it back, after a third try (erase, blank check, double write) now the verify passes... guess it's time to reinstall and cross my fingers I haven't damamged something or we got the chip wrong.
I'm not clear what file you ended up with last. edit: From what I understand you got a modded BIOS with the assumption it was one MDL giving him that mfg. BIOS reference but in fact the model was acctually different is that correct? Are you currently trying to get back to Mfg. BIOS or modded for SLIC 2.1?
BIOS file?... I've programmed the chip with a modded file from the BIOS mod request side... it was a v34 BIOS from the HP website for the DV6915nr.... originally I had flashed the incorrect BIOS for a DV6700 CTO (v58 BIOS) due to HP printing "DV6700 CTO" on the case of this DV6915nr laptop.
What ROM file was last flashed. Modded or factory? That was my question. It doesn't matter it sounds like your ready to put it back together. Good job. You really hung in there.
First was factory v34... then I flashed the mistaken modded v58 which caused all the problems... and now I've flashed a modded v34 onto the chip. When I compared the chip's data (before writting data just now) to the modded v58 the check sums weren't equal with the modded BIN being 1.04MB and the chip's data being 1.0MB. But I assumed it's the correct chip because the first page of data was the same between the the file and chip's... and since the chip is a 1MB chip I also assumed that the data wouldn't be equal. I know it's a lot of assuming... but what choice did I have, lol. The chip is back on the board, so not the laptop is being put back together... hope it boots.
WOO-F'n-HOO!! It's alive!!!! Thanks for all the help, research and encouragement!! I certainly couldn't have done it without you guys looking stuff up on the net while I tore things apart and soldered. Thanks a ton!! You really have no idea how this makes me feel right now.
May have spoke too soon... I can get the laptop on, enter the BIOS, etc... but there's no HDD activity and Windows won't load up.... hmmmm... EDIT, never mind... while I was typing and letting the laptop sit, Windows started to load.. whew... not sure why there's such a delay, but I don't care at this point, lmao.
Basically, the delay for HDD access was about 45-75 seconds because it was searching for bootable USB floppy and the CD-Rom... once I disabled those as boot options there's no longer a delay. I was concerned because this isn't my laptop and have never seen it boot up before and didn't know about the delay.
thank god for spi !.. btw why did u get gq-4x programer while back? u do a few recoveries before ? your first spi i assume. the delay of boot was uuid was reset.
Oh, I got the GQ-4X for a few reasons... I own several arcade machines and needed a programmer to keep those up and running and to be able to reprogram game data to EEPROMs as needed I've also needed to reprogram some removable BIOS chips in the past due to faulty BIOS code on beta BIOS a few years ago. This was my first surface mount BIOS that I had to de-solder though. I used to hand solder medical devices at an electronics company so I'm not a total noob, but it's still a pain without the super expensive equipment I got used to and the skilled de-solder people, lol. My first programmer was a TopWin2048, but I grew tired of the lack of support and bad drivers/software so I found the GQ-4X and have been happy since. It doesn't do everything, but for the price it does plenty... and I think today it just paid for itself, lmao
funny i fixed a dv 6605us and bios was f.34 . i found one and it didnt work. i had to flash orig then make rw report and flash it. then slic 2.1 was there. on side note.. the bios chip 8 pin spi is missing.. but has the longer one about 2 inches away top left of ricoh/ene chips.. was glad flash didnt fail as its not spi.
Sometimes it's a real risky proposition but no guts no glory, right? It's cool you got it. Now your in OEM heaven
bios recovery for hp dv6500 After spending 6 hours finding a way to recovery my friend's HP Pavilion Entertainment dv6500 (dv6500T), I've finally found the correct combinations. It all started from a bad flash within Windows 7 trying to install the latest BIOS version F.5A with SLIC 2.1. The flash seemingly was correct, and the laptop seemed to shutdown properly. But after turning it back on, all that was present were the blue LEDs and a black screen with the fan running. The correct way to recovery the dv6500, at least for my laptop, is discussed below. Make/model: HP Pavilion Entertainment dv6500 (dv6500T) Processor: Intel Core 2 Duo Graphics: NVIDIA 8400MGS Original BIOS version: F.22A System board: 30D2 I found the oldest possible BIOS version to recover was F.22A since it added support for new Intel Core 2 Duo processors. Since the laptop came with the more recent Intel CPU, I opted to recover to this version. Not surprisingly, this is the same version that the laptop came with. A. Preparations 1. Find a good USB floppy drive 2. Find a good floppy disk 3. Don't bother with USB flash drive - it didn't work for me even after 6 hours 4. Use a Windows XP or 2003 computer 32-bit. Don't use Windows Vista/7. B. Preparing Phoenix Crisis Disk 1. Download this Crisis Disk with F.22A included: 1a. http // www dot mediafire dot com/?y6xw2ynm6vkyvxs (mirror below) 1b. http // www dot sendspace dot com/file/0b80fv 2. Extract downloaded zip file to a folder in C:\Crisis 3. The zip file contains the F.22A BIOS that's named "BIOS-DV6500-F22A.WPH" 4. Depending on your laptop configuration, you can rename that file to BIOS.WPH or download another BIOS of your choice 5. If you download a BIOS, it'll be an .EXE file. This needs to be extracted with 7-zip. After extraction, look for a file with extension .WPH. If you can't find the .WPH file, then there may be another .EXE file. Find another file .EXE file that starts with "30CCFXXX.EXE" where XXX is the BIOS version. Extract that file with 7-zip. There now should be a .WPH file. 6. Copy that file into the folder C:\Crisis, and then rename it to BIOS.WPH 7. The included PHLASH16.EXE is version 1.6.9.5 with SHA-1 # 00C603842F6C37369837191396B19086A44D40D6 8. The newer versions 1.7.0.21 did NOT work for this laptop. You may've to try other versions included in the zip file. C. Running WINCRIS.EXE 1. Plug in the USB floppy drive and let Windows installs the necessary drivers 2. Put in an empty floppy disk 3. Open up Event Viewer from the Control Panel>Administrative Tools>Event Viewer and navigate to Windows Logs>System. Keep this open. 4. Run WINCRIS.EXE by double-clicking on it and WINCRIS should see the drive A:\ as 1.44MB 5. Leave every options at default. Since the BIOS for the dv6500 is about 1MB, it'll fit on the floppy just fine. 6. Click on "Start". WINCRIS will automatically open up Windows' disk format dialog. Select FAT & default allocation. Leave the checkboxes UNCHECKED. 7. On the format dialog, click "Format" to begin and accept the warnings. 8. After formatting is completed, click OK but don't click Close yet. Now, go to the Event Viewer, refresh it, and look for the most recent red icons with white X indicating a critical error that has the word "floppy". Open it if you see it and it should say something like bad block detected on floppy. 9. You want to find a floppy that DOES NOT have these errors after being formatted. Even new floppies can have these bad blocks. 10. If there're no errors, then click "Close" on the format dialog and WINCRIS will automatically write the boot sector and copy over MINIDOS.SYS, BIOS.WPH, & PHLASH16.EXE 11. Once WINCRIS successfully created the disk, go to Event Viewer again and refresh it. Look for floppy bad block errors. If none exist, move to Step D. If there'r errors, then use another floppy disk and repeat Step C. D. Booting the floppy disk 1. Disconnect the AC plug and remove the battery from the dead laptop 2. Plug in the USB floppy drive on the USB port next to the power connector 3. Put in the floppy disk 4. Get a stopwatch 5. While holding down WinKey+B, plug in the AC plug. Immediately, press the power button while still holding down the WinKey+B. Once the blue LEDs turn on, release the power button but keep the other two buttons pressed. Released all buttons when you hear two beeps or so, then start the stopwatch now. 6. If the floppy is created properly and the recovery is being executed, then the floppy drive activity light should be on immediately. The blue LEDs will remain on and there will be a repeating beep from the speak with no particular pattern. The beeps have various interval. After about 2min00sec, there'll be a brief pause for about 3sec followed by more beeping. At about 2min30sec, the laptop should turn itself off. If it doesn't, then let it sit for about 10 minutes more and it should turn off automatically by then. If not, manually turn off the laptop. 7. After the laptop shuts itself down, disconnect the floppy drive, disconnect the ac plug, reinsert the battery, and then reinsert the ac plug 8. Turn-on the laptop as normal. The screen should turn on. If it does, then you're home free. If it doesn't, then repeat Steps D and/or Step B with different versions of PHLASH16.EXE. Lesson learned: 1st. do not flash a computer for a friend, unless the friend understands all risks and you're not liable for any bad flashes. 2nd: flash in DOS whenever possible