I do not think you understand.....your SLIC will not work with the new Certificate....We have to match the SLIC with the Certificate or else it will not activate windows.
Arrows mod the biosx86 with SLP: TOSHIBA-TOSCPL.XRM-MS and work ok but i want mod the biosx64 with the SLP: TOSHIBA-TOSCPL.XRM-MS. Please help. Thanks you very much.
Thank you rbjack, I think I know the problem of Digital signature error in SLIC Dump ToolKit now. As you mention above SLIC 2.1 from the modded 1.20 bios is 53 4C 49 43 76 01 00 00 01 00 41 43 52 53 59 53 SLICv.....ACRSYS 41 43 52 50 52 44 43 54 01 00 00 00 41 4E 4E 49 ACRPRDCT....ANNI 01 00 00 00 00 00 00 00 9C 00 00 00 06 02 00 00 ................ 00 24 00 00 52 53 41 31 00 04 00 00 01 00 01 00 .$..RSA1........ B3 6D 83 60 8D 83 65 6E E6 4B A7 6F 38 04 31 C1 .m.`..en.K.o8.1. This mod bios v1.20 already has SLIC 2.1, however after I flashed this mod bios and use SLIC Dump Toolkit or RWEverything to see the SLIC table, there is an Additional alphabet "C" in front of "ACRSYS" Mod Bios v1.20 SLIC 2.1 53 4C 49 43 76 01 00 00 01 00 41 43 52 53 59 53 SLICv.....ACRSYS Mod Bios v1.20 SLIC 2.1 (After I flashed and use SLIC Dump ToolKit) 53 4C 49 43 76 01 00 00 01 43 41 43 52 53 59 53 SLICv....CACRSYS The Mod Bios v1.20 SLIC 2.1 is fine but the problem is after I flashed this mod bios there is an additional "C" in front of "ACRSYS" which will give the Digital Signature Error in SLIC Dump ToolKit report. This is the method I use to flash this mod bios 1) I format Thumb drive and create USB Bootable Disk 2) Copy PHLASH16.EXE and TH120.WPH files in the Thumb drive 3) Restart my NB and flash this mod bios in dos by using command PHLASH16 /x /s /c /mode=3 /o TH120.WPH 4) I can flash this mod bios without any problem 5) After that I use SLIC Dump ToolKit to check and got the digital signature error, slic version is 0.0 The SLIC Table is also wrong 53 4C 49 43 76 01 00 00 01 43 41 43 52 53 59 53 SLICv....CACRSYS Is there anything wrong with my flashed bios method ? Please help to solve this problem....
That "C" is a checksum correction..It has nothing to do with the RSDT OEM ID or TABLE ID..You have to understand the physics of the SLIC table. I dont think you are there yet...... If you would post a RWEverything report from the flashed bios, it may be a bit easier. I have not seen one, but would be more than happy to look at it if you point me in the right direction....(i.e. I anit lookin for it...) There is more wrong here than a checksum byte. it is not even figured in the ID checks.. I would even take a SLICdump screenshot at this point. Preferrably of the slic table and the RSDT/XSDT IDs...
Thanks 911medic, I am waiting for someone who can figure out the problem of this mod bios. I really want to use window 7.
I know this bios has been a PITA.. I can take a look, but it will be a while..week or so maybe. I can offer some quick pearls, but I will not have time to analyse anything until then..sorry....
If it's inserted only, then shouldn't that mean the device will continue to be blocked? If I understand it correctly the change is to remove the whitelisting? Also how would BusyKid know the vendor ID and the device ID? The device is a Sierra AirCard MC8781. BTW I am totally an idiot in BIOS ROM patching so excuse my limited knowledge if I am not making sense...
I thought the error was trying to use a different Wifi card in the computer..my apologies.. What error are you experiencing..Not a supported device???
Maybe i have confused you as well my friend. Here's the whole issue: I have a HP dv2 that does not come with a 3G wireless modem. I found a good deal on a Sierra MC8781 and plugged it into the empty mini PCI slot. When the laptop boots, it shows "105-unsupported wireless broadband device detected" prior booting to Windows, and I have to unplug the card and restart the machine in order to go back to Windows. With my research I learned that HP locked the BIOS so it only allows HP-branded 3G wireless modem to be used. And that's how I end up seeking a solution in this forum. Am I on the right path to ask experts like you to help me to get this device on the whitelist? I appreciate all the info and help you guys have been giving so far