Imatrix i just open BB.Rom with hex editor to understand what is the pubkey in BB.rom i just see that : View attachment 6528 View attachment 6527 So i don't know if its the problem . I would like to test this but i dont know how exactly change ID : Phoenix: -Open bios.wph or bios.rom with Phoenix BIOS Editor The bios will be decompressed, all parts are in Phoenix BIOS Editor\TEMP folder now. You can open them with winhex to edit. -Search for "SLIC" to find a already present SLIC tabe. If found DO NOT modify try to activate first. If it doesn't activate check Everest. No SLIC present at Everest, modify bios -Copy file with slic table into Phoenix BIOS Editor\TEMP and rename it to the next higher ACPIn.ROM. (n ist the next higher acpi number). -Open rom.scr with notepad and add a line "ACPI ACPIn.ROM -X", save it. -Search for "RSDT" and if present "XSDT" string. Overwrite string next to "RSDT" and "XSDT" with your OEM table and OEM table ID you want. They are usually found at BIOSCOD1.ROM file. Save changes. -To enable save button (now is gray) change something random in Phoenix BIOS Editor and restore its original value -Save bios and check log for errors If the bios shows log errors on rebuild, be careful testing. Note: There are bioses that contains slic table already, but it is not active or only mapped a half. There are built-in routines that change the OEM table id to a fixed one. It's difficult to find them and to disable. I'm working on this issue and found a way regarding already present SLIC. To circumvent this "problem" do this: Rename the already present SLIC to TEST by editing the SLIC string (title / name) of the ACPI table to TEST. Search for all further SLIC strings at ALL MODULES. (Found sometimes at MOD_5100.ROM) and rename it to TEST as well, except those SLIC strings that are a part of the SLIC table itself!!! Now insert a complete new SLIC table as described above. Done! The clue: The original table is named now TEST table and is mapped incomplete into RAM while a COMPLETE new SLIC table is mapped into RAM as well! To circumvent the "problem" with a locked OEM table / table ID you have to disable the code that makes those fixed OEM table / table ID equal at RSDT = XSDT=SLIC or even at ALL tables. It's a routine best to find with a debugger....difficult to explain here........at Sony Vaio I never found it so far..........If somebody is interested please PM me. Always keep in mind: Some of the mods are not working cause of this issue. Some of the mods brick Laptop without any known reason. Newer results are that it probably is caused because of PBE isn't decompressing the modules completely (data lost). To check, repeat it more times and compare the decompressed modules......... Thanks I just think its necessary to modifi the acpi table because i see that : RSDP Root System Description Pointer: 0x000F7A60 52 53 44 20 50 54 52 20 DD 4D 41 54 42 49 4F 00RSD PTR .MATBIO. 4C C6 67 CF L.g. Signature"RSD PTR " Checksum0xDD (221) OEM ID"MATBIO" Revision0x00 (0) - ACPI 1.0 RSDT Address0xCF67C64C RSDT Root System Description Table: 0xCF67C64C 52 53 44 54 48 00 00 00 01 83 4D 41 54 42 49 4FRSDTH.....MATBIO 43 46 31 39 2D 31 20 20 00 00 04 06 4D 45 49 20CF19-1 ....MEI 00 00 00 00 D0 4C 68 CF 54 4D 68 CF 8C 4D 68 CF.....Lh.TMh..Mh. 02 4F 68 CF 6A 4F 68 CF A6 4F 68 CF CE 4F 68 CF.Oh.jOh..Oh..Oh. DD CF 67 CF 94 C6 67 CF ..g...g. Signature"RSDT" Length0x00000048 (72) Revision0x01 (1) Checksum0x83 (131) OEM ID"MATBIO" OEM Table ID"CF19-1 " OEM Revision0x06040000 (100925440) Creator ID"MEI " Creator Revision0x00000000 (0) Entry00xCF684CD0 (FACP) Entry10xCF684D54 (HPET) Entry20xCF684D8C (SLIC) Entry30xCF684F02 (APIC) Entry40xCF684F6A (MCFG) Entry50xCF684FA6 (BOOT) Entry60xCF684FCE (TCPA) Entry70xCF67CFDD (SSDT) Entry80xCF67C694 (SSDT) I dont know if my bios his modable so its possible that my only solution his to use Wat . I have 25 days
Sorry I don't know what happened there I was enquiring if the SLIC BIOS request for the Samsung NP R70 worked. I didn't notice any confirmation. Thanks.
Dv2617us It's odd because it's still not activating. I've run through the process and it's something I've done before. I'm still getting the "this copy has not been activated."