Yes, thank you for this warning I'm going to be very careful. Aslo I think Yen just confirmed that the block I copied is the right one! So we are very close to figure out how to mod this - just these 00 bytes that have to be patched seem to be a little problem since I don't know which ones to change.
Hello caudex, I have a question for you. Since you laptop is already a little messed up would you wanna try to flash your bios with one where i will change OEMID and OEMTableID? You said the one you modded you have successfully flashed right? So I could try to change those IDs there. What do you think?
Ok YEN! I think i found the solution! This doesn't have to be HP slic right? We can use Dell which seems perfectly fitting the Sony VAIO pattern - DELL + 00 00 & FX09 + 00 00 00 00. Or there is another Dell - DELL + 00 00 & B10K + 00 00 00 00 I'm 99% sure this will work
Oh, yeah you are right! I got too excited and didn't notice it Yen can you please help here when you have your tools? we are so close...
I'm not at home.. can't do anything cannot open your dump....in about 2 hours I'll be at home again... ........what was the reason why a Sony Notebook bricked already???
Is MS Has been BANED the 22TKD serial i'm not sure,i have heared some news in other forum everyone can tell me ???
Hi Yen, I actually don't really know what happened exactly with bricked Sony - I think he used a modded bios with Lenovo slic and after flash has got a blank screen. Anyhow he did alright at frist when he changed pubkey and marker himself but forgot about OEMID OEMTableID in the slic header. And that's where I'm stuck also modding another Sony bios - like you said earlier it's easy to identify Sony and VAIO but i'm not sure about those extra 00 bytes. Well I'll come back in a coupla hours to check what you think about this. If we figure this out (which i'm sure we will ) then we can mod insyde sonys with no problem. Thank you for your time Yen.
Code: Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F 00000000 00 89 42 14 48 8B 05 A5 39 00 00 8B 48 04 89 4A .‰B.H‹.¥9..‹H.‰J 00000010 19 8B 05 A1 39 00 00 89 42 28 48 8B 05 97 39 00 .‹.¡9..‰B(H‹.—9. 00000020 00 8B 48 04 89 4A 2D 8B 05 93 39 00 00 89 42 3C .‹H.‰J-‹.“9..‰B< 00000030 48 8B 05 89 39 00 00 8B 48 04 89 4A 41 8B 05 85 H‹.‰9..‹H.‰JA‹.… 00000040 39 00 00 89 42 50 48 8B 05 7B 39 00 00 8B 48 04 9..‰BPH‹.{9..‹H. 00000050 89 4A 55 4C 8B 05 76 39 00 00 81 7A 01 43 46 47 ‰JUL‹.v9..z.CFG 00000060 44 74 15 41 8B 40 04 48 FF C2 49 03 C0 48 3B D0 Dt.A‹@.HÿÂI.ÀH;Ð 00000070 0F 86 77 FF FF FF EB 06 41 8B 01 89 42 06 33 C0 .†wÿÿÿë.A‹.‰B.3À 00000080 C3 CC CC CC 48 53 4C 8B DC 48 83 EC 30 49 8D 43 ÃÌÌÌHSL‹ÜHƒì0IC 00000090 10 C7 41 0A 48 50 51 4F 66 C7 41 0E 45 4D 48 C7 .ÇA.HPQOfÇA.EMHÇ 000000A0 41 10 53 4C 49 43 49 89 43 F0 48 8B 05 2F 3A 00 A.SLICI‰CðH‹./:. 000000B0 00 48 8B D9 4D 8D 4B 18 48 8D 15 29 36 00 00 48 .H‹ÙMK.H.)6..H 000000C0 8D 0D 2A 30 00 00 45 33 C0 49 C7 43 18 04 00 00 .*0..E3ÀIÇC.... 000000D0 00 C7 44 24 40 2D 4D 50 43 FF 10 48 85 C0 78 07 .ÇD$@-MPCÿ.H…Àx. 000000E0 8B 44 24 40 89 43 18 48 83 C4 30 5B C3 CC CC CC ‹D$@‰C.HƒÄ0[ÃÌÌÌ 000000F0 48 8B 15 B9 38 00 00 8B 42 04 48 03 C2 EB 11 80 H‹.¹8..‹B.H.Âë.€ 00000100 3A 14 75 09 81 7A 03 5F 50 43 54 74 0A 48 FF C2 :.u.z._PCTt.Hÿ 00000110 48 3B D0 76 EA EB 3D 8A 42 01 0F B6 4A 02 C1 E1 H;Ðvêë=ŠB..¶J.Áá 00000120 04 83 E0 0F 03 C1 48 03 C2 EB 17 80 3A 82 75 0F .ƒà..ÁH.Âë.€:‚u. 00000130 80 7A 04 10 75 09 81 7A 07 00 80 00 00 74 0A 48 €z..u.z..€..t.H 00000140 FF C2 48 3B D0 76 E4 EB 0B 0F B7 05 54 38 00 00 ÿÂH;Ðväë..·.T8.. 00000150 48 89 42 07 33 C0 C3 CC 48 53 48 83 EC 20 48 8B H‰B.3ÀÃÌHSHƒì H‹ 00000160 D9 E8 62 2D 00 00 66 89 05 6B 39 00 00 E8 EE 2E Ùèb-..f‰.k9..èî. This is the only solution that makes sense to me.....but it's NOT confirmed!
Thank you for yor quick response Yen. Also what do you think : how big is the chance that the part "-MPC" was also split in two? Like "-M"+"PC"?
Don't worry, tell me please exactly what you've did. It's important to know, we can learn from your attempt! I'll check it again!!! st8 is right we need to check for 4+2+4+2+2 also!
I saw that block earlier when searching... but they didn't match the pattern 4+2+4+4 or sometimes 4+2+8 plus no MSFT in there, usually they close together in the block... what I search is space (20) not zero... so the one that match is this one : Code: Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F 01DC6590 01 00 00 00 44 00 00 00 38 00 00 19 44 42 47 50 ....D...8...DBGP 01DC65A0 34 00 00 00 01 00 53 6F 6E 79 20 20 56 41 49 4F 4.....Sony VAIO 01DC65B0 20 20 20 20 24 08 07 20 4D 53 46 54 40 42 0F 00 $.. MSFT@B.. 01DC65C0 00 00 00 00 01 40 00 01 F8 03 00 00 00 00 00 00 .....@..ø....... 01DC65D0 99 40 C0 AF 39 0D 5D 40 BE 46 84 6F 08 C5 1A 31 ™@À¯9.]@¾F„o.Å.1 So I patch this one with LENOVO.. since it use MSFT too... Guess its my bad now caudex board got bricked
Don't be sad, you did your best. To make that sure you have to run that through IDA pro disassembler...I'm not quite sure myself and I'm not able to disassemble.......
Thanks yen for the comfort... I hope caudex managed to recover the bios using his backup... Once again I'm so so sorry caudex
bgage, I'm sure your place is not the right one, but I'm also sure to edit there should be a good place, since you've edited text strings only...it's not your fault it was an accident...I cannot advise to try my idea if you are not able to recover, too.