I tried the T2_BIOS with the same results as the first one. The bios remains unchanged.
Also, the computer then proceeds to the windows loading screen then crashes and restarts then loads fine. This has happened for all of the bios.cap's (I just forgot to mention it woops).
I am fairly certain that I am using a FAT32 USB stick since I formatted it and checked under its properties where it says file system.
Could it be a problem with the USB stick?
It's fine, if Windows crashes with a BSOD it mean that bios is loaded from FAT32 successfully because it expects your windows to be configured in ATA mode, not AHCI. But it sure is strange ... I've changed lots of bytes, it must've affected something.. but it does not.
Mind taking couple of pics of the advanced setup tab from your bios ? I want to see how the menus are nested.
Thanks, I will look into finding more IFR_SUPPRESS-like sequences in your setup module now that I at least know what menus are there by-default.
It seems like even though unicode strings for pretty much everything are there in the module they are not attached to anything (meaning there is no way to make these menus visble) and at this point we don't know how this is done. we have a similar situation on previous gen Dells where we have some menus like ATM or OC in the module which potentially could be unlocked, but they're not tied to anything...
There are string like these: 29 02 29 02 29 02 0A 82 40 84 7B
01 45 0A 00 00 00 00 00 00 00 00
So I thought maybe it's worth to try enabling similar string which have this byte disabled, eg:
29 02 29 02 0A 82 40 84 20
00 45 0A 00 00 00 00 00 00 00 00
Try this one ..
https://dl.dropbox.com/u/2573233/T3_BIOS.rar
If it doesn't do any justice then sadly i'm of no help here ..
Luckily we were at least able to figure the recovery process .. it appears that 2nd get Tianos don't require removing of initial padding layer (280000h bytes in your case).. so extracting the capsule part from WPH and naming it as BIOS.cap it enough.
Unfortunately the T3_BIOS did not change anything either.
Thanks for your effort.
Oh, so the Inspiron 7720 cannot be unlocked ??
I will pay $$ for this bios to be unlocked!
Well, as per Phoenix's wiki we have this in the bios ..
Code:
0A 82 40 84 99 02 45 0A 00 00 00 00 00 00 00 00 2F 02 29
0A == EFI_IFR_SUPPRESS_IF_OP
82:1:0000010 L2 // Scope
40 == EFI_IFR_QUESTION_REF1_OP
84:1:0001010 L10 // Scope
9902 // EFI_QUESTION_ID
45 == EFI_IFR_UINT64_OP
0A:0:0001010 L10 // Scope
0000000000000000
2F == EFI_IFR_EQUAL_OP
02:0:0000010 L2 // Scope
29 == EFI_IFR_END_OP//
02:0:0000010 L2 // Scope
There are a few occurrences of this structure (7 to be precise) which is something similar to what we had in our BIOSes.. 7 occurrences of 00 00 00 00 00 00 00 00 45 0A (1 for Languages, 1 for most of the menus, 2 for ME, 1 for Thermal settings and 2 more for SBIOS logging -- 7 total), but the suppress check was based on a simple UINT64 boolean swap 00 to 01.. while here there's is Question to be answered ...
Quote:Question Identifier (EFI_QUESTION_ID). An unsigned integer which uniquely identifies the question within the form set in which it appears. The Question Identifier, along with the device path and Form Set Identifier, uniquely identifies a question within a system.
I'm not sure if boolean questions can be presented in such a form, but let's hope they can ..
Quote:Boolean questions are those that allow a choice between true and false. The question’s value is Boolean. In general, construct questions so that the prompt text asks questions resulting in ‘yes/enabled/on’ is ‘true’ and ‘no/disabled/off’ is ‘false’.
So it's only a matter of figuring how to return the answer to this question as 01 and you will most likely get unlocked menus. Unfortunately I'm not that skillful do do this :<