2-cents (now i'm broke) I am trying to think back to when I flashed my bios, it never showed the final part# of part#, it just went straight to a "rebooting in 10 seconds" type message (I did mine in Win7) What I mean is, my bios only had 16 parts, so the last # of # it showed was 15 of 16, then the reboot warning. I never got a 16 of 16 message. Doesn't phlash16 have a command to make it restart? what i'm saying is, if you didn't specify that switch, would it reboot on it's own? or would it finish and sit there like it is at the moment and you have to power-off/power-on manually? I am not saying power-off/power-on !!! lol stick with what Yen suggested I am simply throwing my 2-cents out there
I never flashed a Phoenix bios. But should at least a 'update has performed successfully' message appear? To switch off / reboot he has to do anyway...maybe it's nothing about, but I've got a strange feeling in my stomach...
Just an update... Things booted just fine... even though I powered off in the middle of a bios update; probably since it wasn't writing?
giggly giggly goo!!! lol giggly giggly goo!!! lol trying to break the tension in the room this bios stuff is high risk, big pay-off go big or go home type stuff not for the light of heart yeah, it seems no one ever reports on how they recovered, just the questions up to it... it's like once they get it recovered reality sinks in as to how close they came to losing their computer/money and they walk away never to be seen again I wish laptops were as easy to recover as desktops... i bricked my desktop AT LEAST 8~9 times learning how to mod my computer... I reported my experience and instructions in the recovery post, if you're wondering if i did my part this is the reason i stress so hard for people to make recovery disk and try to test them BEFORE they flash, because it's so nerve wrecking to do it afterwards... and all of us reading hate to see this happen to people, ESPECIALLY with a bios that is proven and we know works...
It did work!!!!!! Hah, I wish the process was less scary but I am rockin the SLIC 2.1 Thanks you both for your help and responses. Have a good night
thanks for your contribution... the image is hard for me to read, but i think it says the RSDT doesn't match the other 2... because i can see the hex... and both are CB-01. I guess I have more to learn... i thought i patched the RSDT in the remake... oh well, i'll look at it again maybe someone with more experience can have a look at it and instruct me at an offset and i don't exactly understand the reason why it matters that the RSDT has to match, as long as the OS activates (but only because i obviously can't get it ) i can see the possibility of WGA using this to validate, but it hasn't happened yet, has it? but on a serious note, i understand that if i'm going to be doing this for other people i need to have it exactly right because if not then we could possibly have a catastrophic and abrupt freak-out of forum members if wga does check this thanks
When i flashed my x60t the program hung up and after a min or 2 it said to reboot. I have the 32bit version, im not sure why its freezing but it finishes.
There was nothing wrong with the original mod (except that it had two SLICs active - 2.1 and 2.0, which could be fixed as it leads to activation problems in certain cases). Windows is activated because XSDT OEM ID and OEM Table ID match with the SLIC (even though RSDT doesn't. I read somewhere that with ACPI revision 2.0 onwards, XSDT gets preference). RW-Everything doesn't show this, nor does SLIC Dump toolkit. But you can install acpiscope, go to File -> Load ACPI information -> From BIOS. Then click on XSDT and you'll see OEM ID and OEM Table ID are correctly set to "LENOVO" and "CB-01 ". Did you try running SLIC dump toolkit before flasing this mod (with the factory bios)? I'm quite positive you would have got the same results and the pre-installed vista wouldn't have had any problems with activation/wga. Also Chad, the place where you changed the RSDT OEM Table ID descriptor is really just a place holder and has no affect on how it's loaded in memory. If Windows 7 activated with the original mod, stick to it. If it did not, request a mod with SLIC 2.0 deactivated. Cheers, YYZ
If you really really want to satisfy the SLIC dump toolkit, change BIOSCODE01.ROM at offset 0xD720 but honestly, this is totally pointless.