I tried clearing the CMOS by removing the battery. It was a long shot but no go. Hopefully here in the next few days the programmer will arrive in the mail. I.will dump the contents of the BIOS.

Try small 128MB-2GB FAT32 formatted USB. There is probably some specific clear CMOS pads you can short, but you'd have to hunt that info down in google, if it's even out there.

I looked in the platform.ini file like you said had BIOS.fd , AA, BB, intel.fv, ME.fd, 7.fd, 9.fd. but still no go. I am still waiting for the USB programmer to come in the mail.

Also, tried Andy's tool. The pop up screen just give SLIC and key info. The log didn't say anything either about what the recovery name is supposed to be. So I am at a loss on where to look in that tool for BIOS name.

That is the correct name already, but none of that matters if there is not a specific setup recovery method. Did you find some method outlined somewhere for this model or Toshiba in general?
Not all systems have a recover mode or method, and like I said the way BIOS bricked may not allow recovery anyway Best to not stress on this and just wait for programmer to arrive

Ok, finally got the programmer in the mail and dumped the contents of the Winbond 25Q32BVS. Which required me to disassemble the entire laptop because it's on the bottom of the board. Oh well, fun, fun... Luckily I didn't have to remove the heat pipes and fan to get to it. To test from here on out I will not be putting any screws back in but until it forced into submission. LOL

I have attached the BIOS dump.

@JoeCowboy - This is corrupted dump, not due to BIOS you flashed in either. What version software did you use? Try another instead. I can fix BIOS now and send to you, but write back to BIOS will fail, until you find version that properly dumps the BIOS first.

Maybe similar instance as issue I ran into with W25Q64FV, I need to use BV - so could be similar for you but reversed, something to try >> W25Q32FV instead
Try 1.30 and 1.34, dump with both versions and both ID's, name file with ID-Version, so you know what's what, then pack all four up and send to me.

Did you read that off the chip itself, or only get it by auto detect from software? Check the chip itself if you didn't already, so we can be sure it's actual ID
I can't even see the chip in your image, but even if I could I wouldn't be able to read it

If you continue to have errors, we try ASProgrammer 1.40 choose after choose brand, and BIOS ID, hit "Unprotect" function, then read and save and send to me.
https://github.com/nofeletru/UsbAsp-flash/releases/

Yes, I physically saw the name on the BIOS chip itself and all three software packages detected the chip. I have attached the three files dumped by the three different version using Windbond 25Q32BV since the chip had the name 25Q32BVS.

@JoeCowboy - Thanks for confirming you checked BIOS ID yourself. Detecting the chip is good, but what ID do you choose is what matters.

Please dump also using 25Q32FV too as mentioned, then package all three of those BIOS into a single zip or 7zip package and attach here, or upload to any free file host. This way we get it all checked at once
What version was the first dump made with? May also need to try 1.18 with both BIOS ID's too since this is old BIOS chip, new version should work, but you know how that goes

And while you're at it, go ahead after all dumps mentioned above, do the ASProgrammer dump too as I mentioned. All BIOS in post #22 corrupt, same as first one you sent. This either software issue, BIOS ID Issue, or protection (hence ASProgrammer unprotect method, do last)

Ok, I did as you requested AsProgrammer I put those in one zip file. I clicked this time the unprotect button and then the read button and saved two different BIOS versions 25Q32BV and 25Q32FV . Far as the other programmer dump v1.18 all it had was 25Q32BV and 25Q32V but it detected the chip as the latter but I dumped both versions. For versions V1.30 and v1.34 I dumped 25Q32FV this time and zipped all them in one zip file.

Hopefully one of these dumps will work but if not, I can unclip and re-clip the BIOS chip again and do it all over until I get it right for you.

Thanks, I will check this out this afternoon! I know it's a pain, but this is process you have to do at first for any system, so you can find the correct working method to read and write, before you erase anything and try to write.
Usually not this much hassle, but sometimes it takes several tries and different versions until you find the proper working version/method.

Hmmm, I had a quick look, all = same/same! Give me some time later today to look into this in hex and see if maybe it is actually corrupted BIOS region and not just due to software/ID issues.
If it is corrupted BIOS region, then when you wrote that FPT file that initially broke it, either it did not write in properly, or on reboot it scrambled the BIOS which isn't normal but I guess it can happen.
Don't worry though, I'll get it sorted out for you!

@JoeCowboy - Here, please test - erase, blank check, then open BIOS file, write/verify - http://s000.tinyupload.com/index.php?fil...310552401820661
Since we don't know what software is working, try 1.30 I suppose

I will test in a couple days when I get back home. I had to leave to complete a network install. Thank you for your hard work.

I apologize for not getting back with you sooner on testing this. Ok, to let you know version 1.30 wrote the file you had me download perfectly back to the bios chip and the laptop booted and I was able to get into the BIOS just fine. So now what is the next step you want me to try?

Thank you again for all your hard work!!!

I went ahead and retested all three of the first BIOS mods you created both.bin, fisrt.bin and last.bin. All three failed to post. So what do you want to try next?

@JoeCowboy - No problem about any delays, I'm always behind too!
It's great tools have arrived, and you've recovered now! Time to carry on with testing, much less stressful now though, since you have programmer in hand and know you can recover and you know how now too.

For now, carry on with FPT testing where you left off from post #10, but be ready to recover after each

* Edit - disregard above, sorry, I had tab open to reply and didn't see your post directly above until I replied
Please wait, let me look again and see if I can get next set made for you to try. Sorry all those are fail, I hate Insyde BIOS

Looking forward to the testing.