Asus Winflash Chip

= advertisement =-ASUS WinFlash permits you to check the BIOS file before initiating the flash operation on ASUS motherboards.All the steps are provided through a quick wizard that will walk you through step by step making it a very straightforward option for upgrading/downgrading the BIOS system without needing to utilize bootable or removable tools. It is a good practice to always have the most current version on your ASUS Netbook to ensure that any known bugs or potential hardware compatibility problems are fixed before they become an issue.After you open and launch it, ASUS WinFlash scans your machine checking for an active Internet Connection, whether or not the adapter is connected as well as if the remaining battery power (ASUS Notebooks) is enough for the operation at hand. You are then given the option to flash a BIOS file direct from the ASUS servers or via your USB drive and also from your machine's GUI.

You will be given feedback regarding your the current BIOS state against the loaded update for comparison. After you verify the accuracy of the BIOS version, you can then commence the flash process.

Tl;dr: don't try downgrading T100 series UEFI.BIG FAT WARNING: do it at your own risk, I can't guarantee that everything will work fine.BIG FAT WARNING #2: it seems I was lucky not to let the magic smoke out of the motherboard. Flash chip is designed to work at 2V maximum so level converter is very highly recommended.I've bricked my Asus T100TA UEFI when trying to downgrade. Symptoms: after powering on the white led near the camera blinks only once, right after the blink HDD is powered down (kind of Android's bootloop). I got several reports that flash chip in T100 is designed to work at maximum 2V VCC. So either I was lucky or motherboard has good overvoltage protection. Exact chip used in mine T100 (I've checked today) is Winbond W25Q64FWIG which is not supposed to get more than 2V.

Winflash Win7

However it survived flashing twice:)Also, after the sucessfull resurrection I found a.docx file which seems to be a service center document-Document has embedded archives, one of them contains an old (2xx) experimental/debugging UEFI which is a full 8MB file suitable for debricking (bonus- you get service software for all sensors onboard). at 12:52. I finally had some time to take a look at flash dump and to compare it with 'untouched' UEFI image.Best guess- NVRAM was unreadable for the UEFI.It seems that NVRAM is stored within the UEFI starting at 0x10358- untouched 314 image on the left, backup on the right:I also guess that default setup values are stored just before NVRAM, starting (possibly) at 0x10060However data dumped form the flash chip differs from the default image:- several bytes also in (possibly) default NVRAM data area have different values (eg. 0x10064, 0x1007B and some other bytes after that)- starting at 0x1010F data seems to be almost the same in both images but written with a growing offset- at the beginning it's just one byte but later (0x10358) offset grows to 10 bytes(314 image on the left side, dump on the right)But this is exactly how 227 image looks like (as before- original on the left side, dump on the right):My guess:Asus WinFlash utility moved NVRAM data (and default setup values) to the place compatible with provided UEFI image and after the reboot UEFI's built-in flasher was responsible for image update. But in my case it refused to work (although I forced WinFlash not to check image build date) and I'm not surprised that T100 didn't want to boot without access to proper NVRAM data.If only there was a good old 'clear cmos' jumper somewhere.Enjoy this project?Share.

Wow, I can't belive it. After 1 week of flashing, editing-reading many bios files, 'witchcrafting',yesterday T100TA decided to wake up again.but, as soon as Win 8.1 loaded I notice WiFi is not working. 'Boradcom Code 5'.Of curse, I bricked tablet when flashing bios v 314 in bios(SecureFlash or sth) and version of bios that 'fixed' the tablet was v223.I was afraid this Wifi thing can not be fixed but later today I found driver from Dell and the problem with wifi was fixed as well.

(Dell Update Package: Broadcom BCM43241 WiFi Driver, 5.93.102.19, A00)About Flashing:VCC voltage had to be 2.15v -2.20v, than Winbond, bios chip was detected.CLK - (pin13 on arduino) - voltage was around -0.35V. At around -0.45v.(negative)It was very interesting process, learning process as well. Had to use Trimmer 50k at first, later I used 100K trimmer to slowly rasing V from 3.3V pin.Voltages on other pins, thru logic level, were around 2.20v, -2.30. Sometimes I mesured even 2.50V.When I was raing Voltage on VCC, I tried at 2v, but bios wasnt detected. When I reached around 2.40V or a bit more on VCC, it looks like bios chip turned on becouse V intantly droped to 2.10V on VCC and to -0.45V on CLK.If CLK voltage is the same or close to VCC voltage it will not detect bios.Thanks a lot for the project, helped me a lot.Here are few pics:Are you sure?. Your work is brilliant, wonder how you know a lot about this device in deep.By the way this is the most useful search that i have been searching for 2 days, i have done what you had done exact the same except i downgrade it due to my keyboard not working properly after i upgrade to Win 10 and the Asus Live update the latest bios for me. After i hit my keyboard ctrl or win key or alt key.

The keyboard will not function until i hit the '8' key again.Btw i will give it a try, if anything goes wrong i will just replace another motherboard:D. I have a arduino UNO but not sure if it compatible, will come back to read your project once again in details.Once again nice work!Are you sure?. Thanks:)Luckily I had made dumps from unprotected UEFI regions before I even started with downgrade. T100 runs on Intel hardware so almost all information and tools for UEFI image manipulation floating in the Net are helpfull.Seriously don't try downgrading unless all other possibilities won't work.As the first thing I'd recommend you to download this docx-it has embedded 'production tools' archives including keyboard firmware with usage description ('9. MCU FW update'). Also there is full and ready to flash UEFI image ('11. Onboard Memory'- 213, seems like 'experimental' build).

Asus Winflash Windows 10

Side note- I wish I had found this before downgrading.If the keyboard already has the latest firmware:1. use Produkey to read Win10 key2. Use MS's Media Creation Tool to make a bootable USB wint Win10 install3. Download drivers from Asus (at least Wifi driver), drivers for Win8.1 will do4.

Asus Bupdater

Wipe everything and do a clean install using the key from step 1Arduino UNO alone is not enough- UEFI chip requires 3.3v signals (4V max ) while UNO outputs are 5V. Check out Flashrom wiki how to do level shifting. Also chipset will interfere with flashing if UEFI in flash is in working state- this is a known problem with Intel hardware and is also descriped somewhere in Flashrom wiki.Anyway I strongly recommend to try first with keyboard firmware and/or clean Windows install before diving into UEFI.If you have any questions feel free to askAre you sure?.