Intel ME completely offline

Intel ME is not showing in device manager at all. 1.4 BIOS broke mine as well. I've tried to flash it using the techniques including hunter's in the other threads but it is completely unresponsive even after the CLRP trick. MEinfo doesn't even work. I have reinstalled chipset drivers several times and drivers as well.

I've gone through this thread http://forum.notebookreview.com/thr...-17-r3-or-possibly-other-bgas-as-well.813803/ and noticed at the end there are a few leftovers that are in the same boat as me.

Any help would be greatly appreciated.

UPDATE: We've found the fix and the process to apply it. @Basherwalls was kind enough to write out a step by step for the 15R2/17R3 after we fixed his. Some of the links may be outdated by the time you read this. For current tools/utilities you'll need visit https://www.win-raid.com/t596f39-Intel-Management-Engine-Drivers-Firmware-amp-System-Tools.html or just ask here I guess. Here is his copy/pasted guide as follows:

This is a guide to finally resolve the butchered Bios 1.4.4 that Dell Released to the public for the Alienware Laptops
I have an I7 R2 but I have heard its affected many different Laptops in the R2 and R3 range - Maybe more.
In short the Bios Update, corrupted the Intel ME part of the Bios and no matter what Official Bios you downgrade to the laptop cannot recover the Intel ME part of the Laptop - This means the main thing you will notice on your laptop is the Laptop will no longer shut down (the LED lights will stay on and only a hard press on the power will turn off the Laptop). This issue is also found when waking from sleep.


TAKE NOTE - IF YOU TRY TO DO THIS AND BREAK YOUR LAPTOP THEN ITS YOUR RESPONSIBILITY!
I CANNOT GUARANTEE THAT THIS WILL WORK FOR EVERYONE BUT ITS YOUR CALL IF YOU WANT TO TRY IT.

That all said, I have done this and its fine - Much thanks to @Mofoist, who really worked this out and he was the first to fix the issue so MUCH, MUCH KUDOS to him - He repaired what Dell cannot and their solution is a new motherboard at nearly a grand cost to you.


Okay the Guide - here we go (I did mine when on the BIOS 1.3.12 as I had rolled back to the best working BIOS from Dell) It is recommended you revert your BIOS to 1.3.12. It can be accomplished with a thumb drive and the boot menu.

you will need these downloads -
https://www.sendspace.com/file/gtcmvd - CH341A_Tools.zip (install the driver first on the 'doctor PC' = the PC you will use to run the CH341A usb programmer on) and use the 1.31 software.

https://mega.nz/#!CENzmQIC!elS6967PC17_PRrk4-0cCNYcK1ajfXQ6paCIPRU61fc - Intel CSME System Tools v11 r18 .rar

https://github.com/platomav/MEAnalyzer/releases/download/v1.76.2-r149/ME_Analyzer_v1.76.2_r149.rar - The ME analyser
https://www.win-raid.com/t832f39-Intel-Engine-Firmware-Repositories.html#msg14585 - The Intel ME Repository you will need to find your Intel ME from this to patch in later.

You will also need these actual tools - buy good quality ones - cheap = more risk or not working at all - Amazon sell decent ones in uk and USA for about £10/$10 each.

USB Programmer CH341A Series Burner Chip 24 EEPROM BIOS Writer 25 SPI Flash AE1185
and
SOP8 Flash Chip IC Test Clips Socket Adpter Programmer BIOS

The full info is from this website look under section D2 but you don't need to do every step so the following steps is what I did.
https://www.win-raid.com/t1658f39-G...-CS-TXE-Regions-with-Data-Initialization.html

-------------------------------------------

Watch a youtube video on how to strip your laptop - Just search for your laptop others are available.

You don't need to take off the heat sink in most cases - I didn't.
Top tip - Use ziplock bags and a sharpie pen to mark where you took the screws and bag them up.

Once you have the motherboard out - look for the BIOS Chip - It will be marked something like 25Q128FVSO 1535
That was my Chip - from that we can see its the 25Q (25 SPI Flash) / 128 (16mByte/128MBit) / FVSO 1535 - I am not sure but I think it says its a bios chip and version. My chip was just below the Cpu area near the memory DDR sockets and using a torch or camera read the chip info first - PAY CLOSE ATTENTION TO THE LITTLE DOT ON THE CORNER OF THE CHIP as you will need this knowledge later.

You are now ready to go to work -

1. Clip on the SOP8 clip matching the red wire to the corner where the little dot is on the BIOS chip - ensure its on right using a torch for good lighting and get a good look.
2. Connect the other end of the SOP8 clip wire to the CH341A USB programmer (into the 25 set up holes as you match from your chip info) and lock down the holder for the USB programmer.
3. Install the driver for the CH341A on the Doctor PC and then plug in the USB Programmer - If all is good you will see a red led on the USB programmer, you may see a yellow 'run' led but if you don't there's no need to worry yet.
4. Open the CH341A software (version 1.31) - and click on the 25 SPI FLASH option and choose the 16MByte/128MBit (info from your bios chip) and click detect button - your chip should show up and yellow led should flicker.
5. If your chip is detected then you are ready to read the BIOS on the Alienware Motherboard. Click on Read and wait, it will take a little bit. Once read you can click on Verify if you wish to be sure - the yellow LED will flash when doing any operation to show its working.
6. Now you are happy its read the BIOS then you are ready to save it. Click on safe and name it to what you want as a BIN file - I named mine AW13R2.bin and it will safe to the same folder as the USB Programmer.
7. As a safety net - close the USB Programmer software - unplug the CH341A USB Programmer and plug back in. Open the software again and copy steps 4, 5 and 6 again but this time save the BIOS as BACKUPAW13R2.bin.
You now have two different copies which should be the same and copy both of these files to a spare usb drive and keep as MASTER spares. If anything goes wrong from here, you can always flash either of these Bin files and be where you started.

We are now ready to start the cleaning process - Go get a cup of tea/coffee or have a Ciggy Break.

8. Open the ME Analyzer folder and drop a copy of the AW13R2.bin (BIOS) into the ME Analyzer file it will open the dumped SPI/BIOS image and you will see what major/minor version you need as well as SKU. Press enter to see your info.
I saw my Bios was the CSE ME / Version 11.8.50.3426 / SKU Consumer LP / File System State should show Initialized
9. Using the above info look in the Firmware Repository folder and find your Intel ME file - it should match your ME Analyzer info - I chose 11.8.50.3426_CON_LP_C0_NPDM_PRD_RGN.bin (CSE ME match/ Version match/SKU match) and make a copy to your Doctor PC's desktop so you can find it soon. Rename this bin file as ME Region.bin as it will save time later.
10. From the System Tools folder, go to Flash Image Tool > WIN subfolder and run fit.exe. Drag & drop the dumped SPI/BIOS image you want to clean. Go to "Build > Build Settings", select "No" at the option to "Generate Intermediate Files", leave all other settings intact and click Close.
11. Go to "File > Save As" and save the configuration xml file, in this case it's named "config.xml". You may get a Secure boot pop up box, just click on OKAY, I did and it worked fine. Afterwards, close the FIT window.
12. At the FIT folder there should now be a folder named after the inputted file, in this case it's named "AW13R2". Enter "Decomp" subfolder. There should be a number of files there (BIOS Region, Flash Descriptor, OEM Region etc) including a "ME Region.bin" file. Take the previous "ME Region.bin" file you saved at step 9 on the desktop and copy it where the current "ME Region.bin" file is, effectively replacing it.
13. Run FIT again. From "File > Open" select the saved config.xml file from step 11 and open it.
14. Click the "Build Image" icon (or "Build > Build Image") and it should complete successfully.
15. At the FIT folder you should now see a file named "outimage.bin" which is the dumped CSME image with an Engine region which has a Configured DATA section without any unneeded "Initialization" information stored.
16. Drag the outimage.bin into the ME Analyzer.exe again and press enter - check the info. It should now show the same as before and some details have changed - Main one is File System State is now configured so it should be good to go.
17. Copy the outimage.bin to the CH341A folder where the programmer software and Original Read Bios is.
18. Plug in the USB CH341A Programmer into the Doctor PC again and open the 1.31 CH341A Programmer software again (I did mine in admin mode / right click program when opening). Click the 25 SPI Flash and choose the 16/128 again and click detect - should show the chip.

Now its time for another break - Cuppa, Ciggy, Chocolate, whatever is your pleasure as its the nervous part next!.

Time to Barry Allen this Bios - Flash time this Mother 'Board'

19. If the chip is detected then you are ready. Click on Wipe - YES you are wiping the BIOS off that motherboard so ensure you have your Original BIOS safe as you cannot get it back.
20. Click on Blank - This verifies that the BIOS is now completely wiped and its blank.
21. Click on open and choose the outimage.bin (your cleaned fixed BIOS)
22. Now you see the new cleaned, fixed bios in the USB software - Click on WRITE and wait...……
23. Once complete then click on Verify and wait.
24. Close the USB software, remove USB Programmer and remove the clip on motherboard.
25. Rebuild Laptop time - Use the Video and thank me now for those zip lock bags idea!

All being well you have a repaired Laptop. Start it up and it will take a little while to start, BIOS beeps means something is not connected properly so you may need to strip the laptop again and recheck your connections. You don't need to remove the CMOS battery so you should not have any BIOS Beeps from battery being off.

26. Press F2 at BIOS screen and check the BIOS set up loads up. Alter any settings you want to alter but I just left mine and exited.
27. Load up Windows and Install the INTEL ME drivers from the Dell Support website. This is the Driver which would not load before - It will load up now hopefully.
28. Restart Windows
29. Right click device manager and check you have no conflicts - If you do you will fix these with a BIOS Update to 1.6.1. Download the 1.6.1 BIOS from Dell support and run it in Windows - Hopefully if your BIOS Clean and Fix is good the Laptop WILL shut down and run the BIOS 1.6.1 update.
30. BIOS 1.6.1 Update complete and your LAPTOP IS NOW FIXED!
Device manager should show no issues and you can enjoy shutting down your Alienware Laptop once again.


I hope I have covered everything here - I did this yesterday so its all still fresh in my mind so I thought I would share for those affected. Sorry its a long post but its worth it.

FULL RESPECT to @Mofoist who was the person who first fixed his and assisted me with this fix.
This is the guide that I have shared but I do stress - ITS YOUR OWN RESPONSIBILTY IF YOU TRY THIS AND IF YOU BREAK YOUR LAPTOP ITS ONLY YOUR OWN FAULT. YOU KNOW THE RISKS!!!!

All being well though, you have a fully updated and working Alienware Laptop once more!

ENJOY!!!

 

Maybe @Falkentyne can help.

 

Delete please. Thought this was a MSI post about 'temporarily' disabling the ME corrupting it.

 

I thought so.
@Mofoist I don't think your MEI is offline, its just that its staying dormant. Can you post your specs?

 

Sure it's an Alienware 17r3 with 6700hq.

 

So its same config as mine w/ 8GB 980M or 6GB 970M?

 

Same as you apparently as it 980m.

 

Can you check in services.msc whether you see Intel HECI or DAL loader?

 

Plutomaniac over at Win-Raid seems to think it's a corrupted firmware and I'm going to have to do some pinmodding. In way over my head at this point

 

Pin modding is overriding a 'read only bit' to allow reflashing the firmware, avoiding the write protection. If you ever did a CPU pin mod to allow a newer CPU using the same socket to work on an older motherboard that didn't properly support that CPU (along with a proper ucode update to make the CPU POST) it's basically like that.

Without a pin mod, you need SPI tools to force flash the ME firmware region.....if you can find it...

 

Edit: Ok so opened it all the way up to see mobo and Alienware 17R3 has the Creative CA0132 audio chip onboard. Anybody know where I can get ahold of a pinout?

 

I don't remember the MEI/BIOS BIOS chip no. @VICKYGAMEBOY Any ideas?
This is my meinfo verbose info.

 

Without a pinout my only option is to buy the stuff to physically flash. How in the hell is there no pin layout for that chipset anywhere on the internet. I searched for hours

 

That's because its copyrighted material.
Did you try downgrade to 1.3.12 using BIOS recovery method?

 

I manually downgraded via boot menu and flash drive several times.

Does the emergency bios recovery actually flash ME section or just main and boot like the boot menu method

 

ME can't be downgraded but BIOS can be downgraded.
*OFFICIAL* Alienware 13 R3 Owner's Lounge

 

Yeah it won't matter which BIOS I'm on at this point. Still trying to figure out a pinout. Might just try pins 1 and 5 for the hell of it.

 

Ok so to be clear where the troubleshooting has led to:

Intel ME firmware is corrupt.
FWupd , MEinfo, all that jazz is unable to communicate at all with the corrupted firmware.
My flash descriptor is locked which makes it impossible to flash the firmware via software unless I can successfully pinmod the onboard Creative audio chip.
There are literally no references on the internet of the pin layout for creative's chips (wtf)
That leaves me to physically reading, repairing, reflashing the chip using a CH341A flash programmer and SOIC8 test clip cable.

Haven't bought it yet.

 

@Vasudev

Ok this ME may be alive after all. I uninstalled all "intel" programs, and started reinstalling chipset drivers. After the integrated intel graphics reinstalled, I got a "Legacy Device" in system devices. The A13A is the MEI controller!

Unfortunately, when I try to install different MEI driver versions, I keep geting a code 10
The I/O device is configured incorrectly or the configuration parameters to the driver are incorrect.

 

Try the older inf first https://mega.nz/#!bVVyCQiZ!ng90yM81ElZHKB8Xw-bf8F1xdXcRd7n13EapiUCkDKI
If it works then update to latest inf https://mega.nz/#!zUdCUCQL!STm030NFXmt65J4LV9MvPCOIC30RHy-TY-XgmiygJqs
If ME is corrupt your PC might have a reboot every 15 minutes.

 

@Vasudev

11.7.0.1057 is also giving me Code 10
The I/O device is configured incorrectly or the configuration parameters to the driver are incorrect.

 

Try Driverstore explorer and try force deleting heci.inf

 

Deleted all the heci.inf entries. Trying multiple older 11 series drivers 1 at a time then deleting but all give same error.

Would legacy mode change anything?

And maybe I need to downgrade BIOS?

 

Try it and let us know.

 

Ok, reverted bios to 1.3.12 and tried a bunch of different version drivers but all giving the exact same error as before. Did it in both secure boot and am now in legacy rom. Ran the setupme.exe that dell provided and forced it with -preinst. Forced drivers as well. Even afterwards it will fail repair after the forced install.

Action start 15:33:50: IIF_PREPINSTALL.
** InstallDrivers **: Processing driver table
** InstallDrivers **: Read: 'HECI_REL_WIN7_HECI'
** InstallDrivers **: Condition Condition - 'VersionNT<=601': FALSE
** InstallDrivers **: Flags: 20
** InstallDrivers **: DID:
** InstallDrivers **: Uninstall Sequence: 0
** InstallDrivers **: Read: 'HECI_REL_WIN10_HECI'
** InstallDrivers **: Condition Condition - 'VersionNT>601': TRUE
** InstallDrivers **: Flags: 20
** InstallDrivers **: DID:
** InstallDrivers **: Uninstall Sequence: 0
** InstallDrivers **: Driver root folder: C:\Users\Charlie\AppData\Local\Temp\IIFFAF4.tmp\
** InstallDrivers **: Scanning all active devices
** InstallDrivers **: Scanning HECI_REL\win10\heci.inf (Name: HECI_REL_WIN10_HECI, Version: 11.7.0.1045)
** InstallDrivers **: Section with the best match: Intel.NTamd64.10.0
** InstallDrivers **: Device: PCI\VEN_8086&DEV_8C3A (Intel(R) Management Engine Interface )
** InstallDrivers **: Device: PCI\VEN_8086&DEV_9C3A (Intel(R) Management Engine Interface )
** InstallDrivers **: Device: PCI\VEN_8086&DEV_8D3A (Intel(R) Management Engine Interface )
** InstallDrivers **: Device: PCI\VEN_8086&DEV_9CBA (Intel(R) Management Engine Interface )
** InstallDrivers **: Device: PCI\VEN_8086&DEV_8CBA (Intel(R) Management Engine Interface )
** InstallDrivers **: Device: PCI\VEN_8086&DEV_9D3A (Intel(R) Management Engine Interface )
** InstallDrivers **: Device: PCI\VEN_8086&DEV_A13A (Intel(R) Management Engine Interface )
** InstallDrivers **: Device: PCI\VEN_8086&DEV_A2BA (Intel(R) Management Engine Interface )
** InstallDrivers **: Device: PCI\VEN_8086&DEV_A1BA (Intel(R) Management Engine Interface )
** InstallDrivers **: Device: PCI\VEN_8086&DEV_A23A (Intel(R) Management Engine Interface )
** InstallDrivers **: MUP OS bits: 0x0
** InstallDrivers **: Scanning HECI_REL\win7\heci.inf (Name: HECI_REL_WIN7_HECI, Version: 11.7.0.1045)
** InstallDrivers **: Section with the best match: Intel.NTamd64.6.1
** InstallDrivers **: Device: PCI\VEN_8086&DEV_8C3A (Intel(R) Management Engine Interface )
** InstallDrivers **: Device: PCI\VEN_8086&DEV_9C3A (Intel(R) Management Engine Interface )
** InstallDrivers **: Device: PCI\VEN_8086&DEV_8D3A (Intel(R) Management Engine Interface )
** InstallDrivers **: Device: PCI\VEN_8086&DEV_9CBA (Intel(R) Management Engine Interface )
** InstallDrivers **: Device: PCI\VEN_8086&DEV_8CBA (Intel(R) Management Engine Interface )
** InstallDrivers **: Device: PCI\VEN_8086&DEV_9D3A (Intel(R) Management Engine Interface )
** InstallDrivers **: Device: PCI\VEN_8086&DEV_A13A (Intel(R) Management Engine Interface )
** InstallDrivers **: Device: PCI\VEN_8086&DEV_A2BA (Intel(R) Management Engine Interface )
** InstallDrivers **: Device: PCI\VEN_8086&DEV_A1BA (Intel(R) Management Engine Interface )
** InstallDrivers **: Device: PCI\VEN_8086&DEV_A23A (Intel(R) Management Engine Interface )
** InstallDrivers **: MUP OS bits: 0x0
** InstallDrivers **: INF 'HECI_REL_WIN7_HECI'
** InstallDrivers **: DriverFeature install condition not met.
** InstallDrivers **: Will not be installed
** InstallDrivers **: The INF was not found in the package but install condition was false
** InstallDrivers **: INF 'HECI_REL_WIN10_HECI'
** InstallDrivers **: Will not be installed
** InstallDrivers **: !!!Win32 Exception: (0x103) No more data is available.

 

@Mofoist Try Revo or BCuninstaller to uninstall Intel chipset SW and MEI driver completely. You need to check Protected items or system components to see them. And see if the link helps you https://www.dell.com/community/Alie...river-cant/m-p/5612971/highlight/true#M114558
Make sure Intel SGX is disabled in BIOS and VT-d enabled in BIOS.

 

Did as you said with Revo (now a 2nd time.) Same results, I/O error when installing any driver to MEI which is showing up as a legacy device. I've ordered the tools to read/clean/rewrite the ME section...will be here 1 November

 

@Vasudev

If you are willing to test this, if you delete all of your ME driver/software, what does Win10 detect it as?

 

IIRC, it was shown as Legacy device Intel ME Plugin or something.
I saw your post at Win-raid.
Edit:
After removing heci.inf

After installing heci.inf:

 

Thanks. Man I'm 99% sure it's corrupt firmware. Tools come tomorrow to reprogram

 

ITS FIXED!

Flashing the firmware with a CH341A programmer with SIOC8 test clip cable did the job! Win-raid.com is pretty legit.

 

So, you used original stock BIOS rom file to flash all parts?
So Dell wrecked everyone's PCs?

 

I dumped the entire bios chip contents into a bin file, used flash image tool to splice in a clean DATA section of ME component, recompiled and reflashed.

https://www.win-raid.com/t1658f39-G...-CS-TXE-Regions-with-Data-Initialization.html

Section D2 is what I followed after I dumped the chip using the programmer.

And yeah, their BIOS update 100% did it for me.

I fixed all this while still sitting on 1.31 BIOS. After the ME firmware was fixed, I ran the 1.61 BIOS and it installed all sectors including ME.

 

Glad someone finally got a solution to this issue. Then if I understand you correctly, the 1.6.1 bios is in fact good and was what 1.4.4 always should have been? Only sad that 1.4.4 was released to the public....

 

Yeah 1.61 seems ok to me.

 

I have also had no problems at 1.6.1. For me, it is one of the most stable next to 1.2.8 and 1.3.12.
May add that I updated to 1.4.4 without experiencing problems with intel ME, but good to be on a stable bios as 1.6.1 has proven to be.

Only if the bios 1.6.1 had fixed all the mess that 1.4.4 brought with it. But after reading your process, that is not possible/not likely to do for a normal bios flash....

 

I know this is a long shot but Mofoist, do you still have the bios file that you ‘fixed’
I am at a dead end here and I would take full responsibility on flashing the bios if it breaks my laptop.
I see it as my bios is broke anyway.
So do you still have the altered ‘fixed’ bios?

I am guessing that you need a special tool to flash the bios though after re reading this thread.

 

Is the ME bricked like mofoist?
@Mofoist Did you use BIOS programmer to flash rom file or bin file? I am thinking of modding the BIOS to unlock the limits of my PC.

 

@Vasudev I used the 1.31 tool found here:

https://www.sendspace.com/file/gtcmvd

Here is a thread talking about using the tools:

https://www.win-raid.com/t796f16-Gu...ogrammer-to-flash-SPI-EEPROM-14.html#msg60679

@Basherwalls I do have the file but highly recommend you dump your own bin and repairing using this guide:

https://www.win-raid.com/t1658f39-G...egions-with-Data-Initialization.html#msg24423

I'd be more than happy to walk you through it in Discord or something...your serial number, service tag, LAN MAC ID etc are going to be all wrong if you used my file.

Yes, these 2 items were the exact ones I ordered from amazon and they worked perfectly.

https://www.amazon.com/gp/product/B01I1EU9LG/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1
https://www.amazon.com/gp/product/B00V9QNAC4/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1

This procedure will require a 100% teardown of your laptop due to the chip placement behind the laptop case.

 

I have looked into the parts - I live in the UK so one part (the USB module) is cheap enough at £9 but the test clip is £40 delivered on amazon uk - not $13 that amazon uk has. boo.

I am not afraid of stripping down the laptop but I really don't want to chuck £50 to just get the tools to do the job. grr.
I found this - would it do for the clip?
https://www.amazon.co.uk/HALJIA-Tes...JK7C07FYJNZ&psc=1&refRID=APRC1XFGGJK7C07FYJNZ

I did ring dell uk and they would accept a return for diagnosis but I would have to pay for parts (which I know they will sting me for a motherboard - for their own mistake). grr.

Definately interested in a repair - I am fairly technically minded so I would be open to doing this if the other part would work.

As for my Laptop - Its the Alienware R2 intel I7-6500U with 16gb ram and 256gb ssd
I have the same ME unknown issue and SV 0 in the SA00086 tests
So my MEI is goosed thanks to the Bios upgrade 1.4.4
My laptop does not shut down and my device manager has the TPM 2.0 error - currently on Bios 1.6.1

I can downgrade to 1.3.12 bios which sorts out all of the device manager conflicts but MEI is still goosed.

If the ME is sorted, does this repair the shut down issue?

Overall how hard would you say it is to complete this fix, I checked the link and there's a lot of reading there - any way you could post exactly what you did with these tools?
Thanks in advance as you have given me far more hope than anything I read on Dell's forums.

 

@Basherwalls That part you have found will work fine. There are plenty of videos out there of people using the programmer and clip cable so you can watch those to make sure you're attaching the cable to pins appropriately.

FYI just a new motherboard will probably be around 800-1000.

The teardown is fairly simple, there are plenty of breakdown videos online to help you along. Of all the ones I watched they really didn't highlight taking the monitor off well...which is required to get the mobo out.

The most difficult part is obviously dumping the data to a file and then following that guide. The guide is expertly written so with some attention to detail I completed it without bricking my mobo. (I've built plenty of machines but have no programming software/firmware knowledge.)

Here's the software to use with the parts you'll order:
https://www.sendspace.com/file/gtcmvd
There are multiple versions in that file, I used the 1.31 (and installed drivers included.) The UI was a little glitchy, but all you're looking for is it to read the data off the chip, let it verify by reading again. I used youtube to find video tutorials of people using the tools/software to get me comfortable enough to do it.

Once you verify you have good data, you take that .bin file and move on to section D2 here:
https://www.win-raid.com/t1658f39-G...-CS-TXE-Regions-with-Data-Initialization.html

The scary part is then zeroing the chip with the tools/software and then flashing the new and improved file (with fixed ME firmware now) to it. As long as you keep that original verified .bin file you can always just flash that back if somehow you screwed up and want to restore it to where you began.

Anyway, that guide is written so precisely that you shouldn't screw up (worked for me) and after flashing, all functionality was restored as in Sleep/Wakeup and Shutdown working again.

Total process took about 1.5 hours.

Again, if you want to go through with it I am willing to give you a hand as well.

 

Thanks very much, I may as well look at giving this a go as Dell has washed their hands with this whole affair as it’s been nearly a year since they broke many peoples laptops and they now deny that the Bios Firmware 1.4.4 ever existed - or they did to me on the phone two days ago.

 

More like Dell cuts their hands off to avoid giving free mobo replacements!

 

I am guessing once it’s stripped down the bios chip is easy enough to identify on this motherboard?
I have watched a video on how the programmer works and the stuff is due tomorrow.
I have already tried the jumper behind the memory and a bios install (in the past) but it never touched the ME - guessing as it cannot be seen as it’s been locked.

 

okay, Laptop is stripped down and motherboard in hand.
Waiting on the programmer tomorrow and then the fun will start.
Looking at the motherboard on the Alienware r2 13, I have no clue which chip the bios is...

I have four which look like they could be the bios - UE2, UC2, UT2 and UT6
not sure which is the bios though. I have not removed the heatsink but watching the video of an r2 13 teardown, I couldn't see a similar chip under it.
Does the bios chip have something to know that its the bios chip?

This is the exact motherboard I have (follow the link) - just don't know the chip which is the bios and I can access all four chips which look like the bios without removing the heat sink.
Does anyone have any idea which is the bios?

https://www.parts-people.com/index.php?action=item&id=20975


Oh and Mofoist, According to the dell service manual the Service tag is actually printed to the system board and not on the bios, so your fixed image should work on any R2 bios chip.
I need to work out which is my bios chip and I will dump my image.

 

Tried the clip, but my bios chip is fitted too low to fit the clip on to register the chip as connected (clip keeps on popping off).
I know I have found the right Winbond chip - 25Q128FVSO near the processor chip but the damn clip will not register as connected.

Put the laptop back together and will try and see if I can find a different solution.

 

Try selecting the chip and then attempt to read it.

 

I did I got a no response message.
The usb reader would not light up yellow for running, I got it to flick on but not enough to feel confident enough to do a read, definitely not a wipe or write.
Looks like that option is out for me.

 

Try to uninstall the driver and install it again whilst the ch341a being connected to usb port.