My chip is obviously set too low, the clip just about clips on but then drops off. I am going try a few other avenues before stripping the laptop again.
I had given up on this laptop and have an 17” Hp Omen I7 7700k with GTX 1060 6gb now so no real rush, just annoyed that Dell have no responsibility here.
-
-
There's a new MEFW update at win-raid which fixes some issues like ME going offline after FW upgrade and fixes lot of security issues.
-
Do you have a link for the one I need to use?
Cheers, I will give it a go. -
-
If you have a unknown intel ME from the buggered bios, how can you install this Fw?
I get the platform error message. -
-
I didn’t think I could.
Looks like the hunt continues...
I did find it surprising yesterday that I bumped a topic on the official Dell forum as an Alienware moderator was on - Alienware-Eimy - asking if Dell have issued a memo to all Dell staff to no longer interact with anyone about the 1.4.4 bios issues.
My comment stating this was flagged as Spam within a minute, deleted and no answer from Alienware-Eimy.
I may have struck on something here.
If your Laptop is broken by Dell’s 1.4.4 bios you are bang out of luck as no one at Dell will help you.
Just my thoughts from recent events.Vasudev likes this. -
@Basherwalls Tag me with the @ sign so I know to look here! There are no other options for your problem due to the firmware being corrupt and locked, no software based update will reach it.
First, are you confident you connected the cable to the programmer correctly? That mini pcb that the programmer comes with is not needed.
Also, what lights lit up on the programmer exactly when you clipped on? It's going to be a pretty fragile connection but if you're able to read/have both lights, which will be safe to attempt, don't move anything and carry on.
Could you send a picture of the bios chip?Last edited: Jan 1, 2019Basherwalls and Vasudev like this. -
@Basherwalls
There's mine for simplicity since you put yours back together. It should be the same?
https://www.win-raid.com/file.php?u...E_not_responsive_or_showing_in_device_manager -
@Mofoist I know I have the right bios chip, it’s the Winbond 25Q128FVSO 1535
It’s right next to the ram slots, near the cpu, not under the heat sink but you do have to strip the laptop to get to it.
The other Winbond chip bear is next to the gpu and it’s a different code so that’s not it - my Winbond code is very similar to yours that you posted as a photo on another forum.
I have connected the clip pcb and pins to the 25 setup on the usb and I get a red light on the usb, no yellow run light.
If I connect to the 24 setup I do get a run light but I know that this chip is a 25 as it’s written on the bios chip.
If I really wiggle the clip about I get an occasional flicker on the run light but never when clamped on in the usb 25 mode.
I have thought about using a Stanley blade and slightly scraping the pins so maybe to attract a connection but I would have to strip the laptop again.
I may try it again, I am currently on bios 1.3.12 and it’s running great with fast boot but only the shutdown issue.
I will try one more time but selling this in a semi working state may be the best option.
It’s annoying as Dell have really pee’d me off to the point I will never buy Alienware again.
I like to feel I can fix this, so I will try once more. -
@Basherwalls It could very well be the clip being poor quality. I've still got my cable attached to my programmer so I'll double check it's on 25 too.
-
Okay, I have 3 or 5 old laptops which I can test the clip on, I should have thought of that the other day.
If I clip on and get lights, I know the clip is good. If not then I need to source another clip.
I did get both lights on when the usb is set to a 24 set up but the flasher only has about 6 lines of code, I change that to the 128 on the settings and do a read (with both lights on) and I get the code reading 00 in every line.
So it’s obvious it’s the 25 set up. -
Attached Files:
Vasudev likes this. -
-
Bought a new clip, chip now detected.
Not sure which 25 spi flash I should be on.
Is it the 8mbyte/64Mbit or the 16mbyte?
In the ch341a programmer software?
Cheers in advance @Mofoist -
-
So yeah, read it, verify you have a good read, then make a backup copy of that file for a fail safe. Then proceed step by step as we talked about earlier
-
Cheers I just read and verified a 8 and 16(128) as I wasn’t sure.
Now I have that file, I am tempted to wipe and install the 1.6.1 bios straight away (without cleaning the bin file I have - it’s saved so it’s safe after all) I know the 1.6.1 bios has the Intel ME on it for sure as it’s the update.
If it doesn’t work, I could always put back on the cleaned or original bios as I have it saved. -
You're so close just go with the guide from here. Regardless of what BIOS you have/install, you are stuck with the corrupted ME region you currently have until you follow section D2 and fix it. Just go step by step and if you have any questions ask. I'm at work and have nothing to do so I'm watching this thread
-
I fixed it while still on 1.31 or whatever it was so I could at least boot fast
-
-
I do not get the run light on the usb when i plug in but I can detect the chip, I then get the run light when reading the chip and info is there after a read.
Going to start the guide but reading and saving chip twice with different names just to be safe. -
Yeah, you're communicating with the chip and getting verified data so thats all that matters
-
@Mofoist which Intel me version did you use on bios 1.3.1?
-
Here are the system tools you'll need:
https://mega.nz/#!CENzmQIC!elS6967PC17_PRrk4-0cCNYcK1ajfXQ6paCIPRU61fc
To find out what corrupted ME version you have, drag the .bin file you dumped onto ME analyzer:
https://github.com/platomav/MEAnalyzer/releases/download/v1.76.2-r149/ME_Analyzer_v1.76.2_r149.rarVasudev likes this. -
Windows Defender is going crazy with false detects on ME Analyzer for me. Just disable real time protection on Defender so that you can open ME Analyzer then drag the .bin to it
Vasudev likes this. -
Yes, I just allowed the threat
-
So my version shows as 11.8.50.3456
So do I download that one then? -
Grab the 11.8 repository pack and proceed with the guide. Almost there
-
Post a screenshot of your ME Analyzer info if you want to verify you picked the right ME file.
This is the one I'd go withAttached Files:
Last edited: Jan 3, 2019 -
-
@Basherwalls On step 6, remember you're actually working on a full SPI/BIOS image so disregard the note. (Sorry just preempting questions I had going through the guide)
-
mine was showing as CON LP in the analyser not Con H so I need the LP version.
I am stuck at the D2 part 6 - the bit after the spoiler - do I need to change the additional settings?
lol just read your post -
at the building image stage - I got a message about bootguard profile 5 - do I continue?
its a yes or no -
I don't recall getting that...What does it say?
-
it was about bootguard settings I just clicked proceed and it built the image - in section 7 it was talking about platform intergrity but I did not have that heading, so I skipped as it said
-
I skipped 7 as well. And I guess I just forgot about it but searching the guide forums thats a normal prompt and is safe to ignore
-
So you can skip 13 too
Once you verify it's "configured" you should be done. Next is the scary part. Zero your chip and write your outimage back to it. Then reassemble, (dont miss any fan cables like I did in a hurry) and it should fire right up -
okay, step 14 all good, showing configured.
do I need to do step 15 or do I wipe and flash first?
it looks like I flash, put system together and then run the command ftp -greset -
15 is for after you put it together again and it's running ok.
-
okay then - time to unleash 'Barry Allen' and Flash this mother (board)
-
Godspeed lol
-
So I have read, do I now erase, then write?
Did you use blank? -
Ah blank check before write.
-
blank just checks that its blank. So, erase, write, and verify if you'd like...I didn't even verify though cause at that point it's either good or not
-
Black check complete, running the write now, then verify and then rebuild and fingers crossed. Lol
Did you do the last step after the rebuild?
Is it important for what we are doing? -
Yeah, it just forces a reboot so no big deal. After that, you'll be clear to update to 1.61. Ensure you don't have throttlestop or any underclocking/overclocking software active during BIOS updates as a general FYI
-
Nah, I use my HP Omen I7 7700k with GTX 1060 6gb for heavy gaming. The Alienware has been stuck in a drawer as I got pissed off with it. It may become the ultimate retro emulator..
If it lives the next 30 minutes. Lol
It’s nearly 3am here in Newcastle -
Ah nice. I have the 17R3 which as a 980M. I have a lot of downtime at work so I just go with high end laptops for gaming. Other than this problem, it's been a great machine.
Vasudev likes this. -
The suspense is killing me!
-
The 13 R2 is at the bios screen. No beeps or errors.
Everything looks good.
Now to risk the windows loading and complete step 15 and then see if this thing shuts down.Vasudev likes this. -
I did a shutdown to see if it worked before I did 15
Intel ME completely offline
Discussion in '2015+ Alienware 13 / 15 / 17' started by Mofoist, Oct 25, 2018.