Hi, guys. I was just wondering if it would be worth the effort to learn to update this device. I learn by doing, but first read and google and read some more and google some more… 
To be certain I understand what I am going to do.
I’ve attached an image of a few MEA results I have gotten though I haven’t figured out yet how to interpret the bin file results. I got results from all the bin files in the group, but the ones shown were the only ones that had a “Yes”…
Also, I’ve googled and “think” that the HMRFPO (shows as locked) can be unlocked.
And I’ve gotten hits on the site here for the 1.0.4.1090, just wondered if I should pursue.
BTW even if it just makes a small improvement I would learn to do it, simply because I like to learn new things and it wouldn’t be the first time I have bricked something so I know the risks involved.
|addpics|5no-1-0ea6.png-invaddpicsinvv|/addpics|
You currently have TXE 1.x firmware which is Bay Trail so TXE 2.x (Braswell, Cherry Trail) is not relevant. Since you have TXE 1.x firmware you can update to latter 1.x releases only. If you check the TXE thread > Section B > TXE 1.x Upgradeability, you will see that unless your Flash Descriptor is unlocked, you cannot upgrade to anything after 1.0.x using FWUpdate even though the latest compatible firmware is indeed 1.2.x. To check if your flash descriptor is unlocked, run Flash Programming Tool with the command fptw -dumplock. If you see 00 00 FF FF for both CPU and TXE then you have an unlocked descriptor and thus can (after some hoops, not with FWUpdate) update to the latest TXE 1.x firmware which is the one you run through MEA. If the descriptor is locked and you want to unlock it, the easiest thing to do is to use a cheap programmer. The other method requires shorting two pins of the audio chip while the system boots to temporarily disable the flash descriptor protection and thus allow TXE read/write access. The HMRFPO message you mentioned is only relevant if the OEM has implemeted it at the BIOS, usually by an option such as ME Disable, ME Reflash Enable/Disable and so on.
Thank you for the reply plutomaniac!
If I understand correctly my TXE FW is 1.0.4.1090 and if I read the pdf from Intel on upgrade-ability then 1.0 cannot be upgraded to 1.1 and they are only supporting 1.0 updates for critical matters. And if I get the progression of updates then I "might" be able to update to either Intel TXE 1.0 1.25MB Firmware v1.0.5.1120 BYT-M/D or Intel TXE 1.0 3MB Firmware v1.0.7.1133 BYT-M/D?
Depending on whether or not my device SKU is thin or full?
Contrary to ME or TXE 2.x, TXE 1.x was very complicated for no reason. To explain: TXE 1.x had two firmware releases based on Platform, Mobile/Desktop (M/D) or Tablet/IVI (T/I). For each platform (M/D or I/T) the SKUs change according to minor version.
* TXE 1.0 had two SKUs: 1.25MB and 3MB. If you have 1.25MB you upgrade to a latter 1.25MB and if you have 3MB you upgrade to a latter 3MB.
* TXE 1.1 merged those two SKUs into one: 1.375MB which fully supplements/replaces both the older 1.25MB and 3MB SKUs.
* TXE 1.2 is the same as 1.1, meaning one 1.375MB SKU which suplements/replaces both 1.1 and 1.0 SKUs.
In theory you can upgrade from 1.0 all the way to 1.2 firmware no matter if your current 1.0 SKU is 1.25MB or 3MB. Same for 1.1 to 1.2 upgrade, very much possible. The problem is, to upgrade from one minor version to another, the full TXE region needs to be reflashed which requires an unlocked flash descriptor which in turns grants full read/write access to the whole TXE region. FWUpdate updates the TXE partially (where it counts, meaning CODE/Version) and does not need the flash descriptor to be unlocked. So it’s only usable to update within a specific minor version, either 1.0, 1.1 or 1.2.
You currently have 1.0 firmware. I don’t know what SKU you have (1.25MB or 3MB) as ASUS doesn’t include the TXE region at their BIOS images and so I cannot check with MEA. Try running TXEInfo -verbose and TXEManuf -verbose, hopefully one or the other will mention the SKU somewhere. I also don’t know what firmware platform your system has, M/D or I/T. However, it’s almost always M/D even at Tablet systems, I don’t know what Intel was thinking honestly.
As far as upgradability is concerned, you have two options. If your flash descriptor is locked then you can only update via FWUpdate to latter 1.0 firmware, either 1.25MB or 3MB based on what your system is using. If it’s unlocked you can upgrade to the latest 1.2 firmware (1.375MB) by Flash Programming Tool (FPT). I need to give more details for the 2nd case but only if indeed your flash descriptor is unlocked or you plan to use a programmer. I have mentioned how to determine the lock state of the flash descriptor at my previous reply.
For example:
→ If I assume you have a) M/D firmware , b) 1.0 current firmware , c) 1.25MB SKU for 1.0 , d) Locked flash descriptor: FWUpdate with “Intel TXE 1.0 1.25MB Firmware v1.0.5.1120 BYT-M/D”
→ If I assume you have a) M/D firmware , b) 1.1 current firmware (1.375MB) , c) Locked flash descriptor: FWUpdate with “Intel TXE 1.1 1.375MB Firmware v1.1.4.1145 BYT-M/D”
→ If I assume you have a) M/D firmware , b) 1.0 current firmware , c) 1.25MB or 3MB SKU for 1.0 , d) Unlocked flash descriptor: FPT+FITC with “Intel TXE 1.2 1.375MB Firmware v1.2.1.1153 BYT-M/D”
It looks like mine is locked. I am off to do some more reading. It seems your site is having connection problems… We are too with our internet.
|addpics|5no-2-7556.png-invaddpicsinvv|/addpics|
I’ve just finished reading through a bunch of pdf’s from intel to see if I missed something. I have looked for the SKU in both tools mentioned but cannot seem to find any reference. Does any of this make sense or suggest what the SKU is?
TXEinfo -verbose
Intel(R) TXEInfo Version: 1.0.2.1065
Copyright(C) 2005 - 2013, Intel Corporation. All rights reserved.
FW Status Register1: 0x1F0000C5
FW Status Register2: 0x60000000
CurrentState: Normal
ManufacturingMode: Disabled
TXEMemoryInvalid: Valid
OperationalState: Power Gated
InitComplete: Initializing
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Normal
Phase: HOSTCOMM Module
Windows OS Version : 6.2.9200 “”
OS BIOS Support : UEFI
Table Type 0 ( 0x 00 ) found, size of 24 (0x 18 ) bytes
Get TXE FWU info command…done
Get TXE FWU version command…done
Get TXE FWU feature state command…done
Get TXE FWU platform type command…done
Get TXE FWU feature capability command…done
Get TXE FWU OEM Id command…done
FW Capabilities value is 0x20101040
Feature enablement is 0x20101040
Platform type is 0xFF0080
Intel(R) TXE code versions:
BIOS Version: T200TAC.205
VendorID: 8086
SOC Version: D
FW Version: 1.0.4.1090
TXEI Driver Version: 2.0.0.1067
FW Capabilities: 0x20101040
Intel(R) Anti-Theft Technology - NOT PRESENT
Intel(R) Capability Licensing Service - PRESENT/ENABLED
Protect Audio Video Path - PRESENT/ENABLED
Intel(R) Dynamic Application Loader - PRESENT/ENABLED
Intel(R) NFC Capabilities - NOT PRESENT
Last TXE reset reason: Power up
Local FWUpdate: Enabled
Get BIOS flash lockdown status…done
BIOS Config Lock: Disabled
Get flash master region access status…done
Host Read Access to TXE: Disabled
Host Write Access to TXE: Disabled
SPI Flash ID #1: EF6017
SPI Flash ID VSCC #1: 20052005
SPI Flash BIOS VSCC: 20052005
Protected Range Register Base #0 0x0
Protected Range Register Limit #0 0x0
Protected Range Register Base #1 0x0
Protected Range Register Limit #1 0x0
Protected Range Register Base #2 0x0
Protected Range Register Limit #2 0x0
Protected Range Register Base #3 0x0
Protected Range Register Limit #3 0x0
Protected Range Register Base #4 0x0
Protected Range Register Limit #4 0x0
BIOS boot State: Post Boot
OEM Id: 00000000-0000-0000-0000-000000000000
Capability Licensing Service: Enabled
Get TXE FWU OEM Tag command…done
OEM Tag: 0x00001043
Global Valid FPF: Valid
PTT FPF: Enabled
Perform Secure Boot FPF: Enabled
OEM Public Key Hash FPF: D376BC9F0C4504508F18113C63790F6E697B5A5BFA9A5653EB6230540ADFA92C
Key Manifest ID FPF: 00
Alternative BIOS Limit FPF: 07DE
Secure Boot Status: Executed
Secure Boot Recovery Status: Not Executed
PTT Lockout Override Counter: 10
PS C:\windows64>
TXEManuf -verbose
Intel(R) TXEManuf Version: 1.0.2.1065
Copyright(C) 2005 - 2013, Intel Corporation. All rights reserved.
FW Status Register1: 0x1F0000C5
FW Status Register2: 0x60000000
CurrentState: Normal
ManufacturingMode: Disabled
TXEMemoryInvalid: Valid
OperationalState: Power Gated
InitComplete: Initializing
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Normal
Phase: HOSTCOMM Module
Get FWU info command…done
Get FWU version command…done
Get FWU feature state command…done
Get TXE FWU platform type command…done
Get TXE FWU feature capability command…done
Feature enablement is 0x20101040
gFeatureAvailability value is 0x1
Request Intel(R) TXE test result command…done
TXE initialization state valid
TXE operation mode valid
Current operation state valid
TXE error state valid
Verifying FW Status Register1…done
Request Intel(R) TXE test result command…done
vsccommn.bin was created on 03:31:21 08/05/2013 GMT
SPI Flash ID #1 TXE VSCC value is 0x2005
SPI Flash ID #1 (ID: 0xEF6017) TXE VSCC value checked
SPI Flash ID #1 BIOS VSCC value is 0x2005
SPI Flash ID #1 (ID: 0xEF6017) BIOS VSCC value checked
FPBA value is 0x0
Request Intel(R) TXE Runtime BIST test command…done
Get Intel(R) TXE test data command…done
Total of 1 Intel(R) TXE test result retrieved
MicroKernel - Internal Hardware Tests: Internal Hardware Tests - Passed
Clear Intel(R) TXE test data command…done
TXEManuf Test Passed
PS C:\windows64a>
Thanks for any help. I am learning a lot
which is a plus, even if its making my head spin a little.
Ok, it’s impressively stupid of me to have forgotten such an easy thing. Run FWUpdate -save txe.bin command. Attach it here or input it at MEA, it should tell you what platform (M/D or I/T) and SKU you currently have (1.25MB or 3MB). Complete brain fart on my part… 
Also, you can use the latest v1.x tools as provided at the TXE thread. They are fully compatible with 1.0 firmware releases.
That’s OK I was just going to ask what might be a dumb question 
I found a whole set of tools via googling that contains everything (including the PDF’s from Intel) TXEI_Intel_Win81_64_VER1021050 and while dated allowed me to play around a bit.
I read the System_Tools_User_Guide_1.2.pdf and it explains how the FITC Flash image is composed of 4 regions DESC, TXE, PDR and BIOS and how if space is not allocated the regions will use only the space they need and if space remains TXE will expand to fill it, or BIOS or DESC.
So I was thinking if the Flash device reports its size as 8192… I dumped the BIOS and its 5MB the DESC is small at 4Kb and the PDR region has not been set.
Would that perhaps “Suggest” that the TXE is the remaining 3MB?
I am pretty sure its M/D as all the documents I have read suggest so, but I’ll try what you suggested as I haven’t gotten as far as the FWUpdate tool to see what the supported commands are.
Thanks again plutomaniac.
PS: After following your advice above
--------- ME Analyzer v1.4.10 ---------
File: txe.bin
Firmware: Intel TXE
Version: 1.0.4.1090
Release: Production
Type: Update
SKU: 3MB M/D
VCN: 4
PV: Yes
Date: 08/01/2014
Latest: No
Those tools and documentation are part of the System Tools packages as they are called. Since I search for these as well, you can find the latest at the TXE thread (section C), both tools and documentation.
As you correctly read, the remaining SPI space is taken by the TXE region. If for example that remaining space is 6MB, then no matter the SKU, it will be 6MB. You can find 1.25MB firmware at a TXE region of 6MB, it doesn’t have to be 3MB. Generally, don’t trust size but actual SKU as analysed from the firmware image when run through MEA.
You have 1.0 firmware, 3MB M/D and a locked flash descriptor so your only option is to use FWUpdate with Intel TXE 1.0 3MB Firmware v1.0.7.1133 BYT-M/D. If at some point you decide to unlock the flash descriptor or similar you could upgrade to 1.2.x via FITC+FPT but for now only what I said above.
I tried but got the following error;
Intel (R) Flash Programming Tool. Version: 1.1.4.1145
Copyright (c) 2007 - 2015, Intel Corporation. All rights reserved.
Platform: Bay Trail
Reading HSFSTS register… Flash Descriptor: Valid
— Flash Devices Found —
W25Q64DW ID:0xEF6017 Size: 8192KB (65536Kb)
Warning: Not all of the file data will be written to flash because
the file is longer than the flash area to be written to!
File: “1.0.7.1133_3MB_MD_PRD_RGN.bin”
File Length: 3145728
Write Length: 3141632
Do you want to continue? Y/<N> or q to quit : n
FWUpdate (FWUpdLcl.exe) and not Flash Programming Tool (fptw.exe). Completely different tools. If the flash descriptor was not locked and you accepted, you could have bricked the system. In this case, if you had accepted, it would have shown Error 26, no CPU access to the TXE region due to the locked flash descriptor but that doesn’t mean that the initial tool choice was correct in any way.
Whoops… My bad 
Thanks for the smack to the back of my head!
Crossing Fingers and Rebooting…
Intel (R) Firmware Update Utility Version: 1.1.4.1145
Copyright (C) 2007 - 2015, Intel Corporation. All rights reserved.
Communication Mode: TXEI
Checking firmware parameters…
Warning: Do not exit the process or power off the machine before the firmware update process ends.
Sending the update image to FW for verification: [ COMPLETE ]
FW Update: [ 100% (Stage: 17 of 17) (/)]
FW Update is complete and a reboot will run the new FW.
SUCCESS!
File: txe.bin
Firmware: Intel TXE
Version: 1.0.7.1133
Release: Production
Type: Update
SKU: 3MB M/D
VCN: 13
PV: Yes
Date: 16/12/2014
Latest: Yes
Press any key to continue . . .
Great. It’s not really needed in your case but as an extra step you can also run fptw -greset command to reset the TXE for good measure. After the reset, make sure to also run TXEInfo (no red errors) and TXEManuf (green “TXEManuf Operation Passed”) in order to verify that everything is alright as far as TXE health is concerned.
I have been studying that option. It seems fairly straight forward though I have much more to learn about BIOS Modding if I am going to attempt that.
I have been working on figuring out how to undo something that ASUS did to these tablets.
They basically connected an internal drive connector to an extra USB port in the base/keyboard and then told the system it’s an external USB device. The problem is that whether an HDD or worse an SSD is connected the OS doesn’t properly identify it nor support it. So my SSD is seen as an external HDD, no Trim support or SMART support etc. Its top speed is SATA 6, but at best it gets about half that, and I cannot boot to it.
ASUS is no help they even try to deny doing that, even though one of their BIOS updates says that they did just that…
Anyway… Thanks again for your help.
Unlocking the descriptor is very easy but a programmer is required so that’s why it’s usually out of reach for most people. Other than that, all that’s required is changing 6 bytes at the Flash Descriptor offset 0x60. If you ever want to do it, you can let me know. You’ll probably find the answer yourself as well since you seem to search a lot contrary to most other people that require assistance. For the BIOS issue I don’t really have the knowledge to be of any assistance. Maybe if you open a new thread about that someone like CodeRush might pitch in but (justifiably) don’t hold your breath.