In theory you don’t need a soic clip since your chip is already removed from the motherboard but it might be useful later down the line so it’s not a bad idea to have it. When you have the programmer you will dump the old chip to first see the contents. You may also be able to move any board sensitive data from the old bios to the new using CodeRush’s FD44Editor if it’s compatible but ok, that is not that important.
Hmm… when i dont need the soic clip, how do i need to attach that small chip into the ZIF socket then ?
I thought the soic clip was for programming those tiny chips, even when it’s not soldered onto the board anymore.
The only thing i could see was soldering it onto the tiny board that is delivered with the programmer
Yes you are right, the clip is needed. I forgot how small the chip was.
No problem, it’s ordered anyway, and i couldn’t cancel it anymore.
Now some other stuff, i had some mail contact with the webshop where i ordered the chip. Tried to explain them what was going on with this chip,
I will post the mail contact over here, maybe it’s something to look at, since maybe people want to order a chip over there also.
Here was the conversation starting
" Thanks for the quick response on everything.
I’ve received the chip, and installed it in the laptop, which is working again !!
Now there’s a slight little problem.
Since the chip is installed, the computer will run pretty good, but it only runs on 933Mhz, instead of the stock 1,79 Ghz.
I’ve done some research, and found it this has something to do with the BD PROCHOT bit. This can be shut off by running Throttlestop, and uncheck BD PROCHOT.
Also the fan of the laptop is running at full speed all the time, and sometimes the laptop shuts down immediately.
The picture added is the one of my Hardware management in windows.
So I’ve done some more research, and found out it’s a little problem with the bios chip :
I’ve translated it to English to clear it a little up: (This is from a source on the internet)
Asus N53Jq laptop was completely dead after flashing the BIOS. After consulting with Arthur Flash Bios Developments I sent the machine. I got this soon, however, back at the start there was a message about the Intel ME FW (Management Engine firmware), the CPU fan at full speed continued to run and the machine was used after about half an hour completely. It was possible to switch it on again. After some research on the Internet revealed that the BIOS chip on an Intel-based system includes today echelons 4 dozen. One for the descriptor, one for the Intel ME FW, one for the Gbe (Intel Gigabit LAN), one for the PDR (platform features) and one for the BIOS itself. Only flash the BIOS region was in my case insufficient. Arthur is go search and found a company against which the BIOS chip fully able to deliver flashed. So the laptop yet again sent and at cost is then replaced the chip. After this, the laptop was working as usual. I have contact with Arthur as well experienced, became more informed and reached a solution, thanks to the enthusiasm of Arthur is eventually.
This was his response :
Hello Chris,
“Arthur from Flash Bios Developments” is one of our customers.
“Arthur is go search and found a company against which the BIOS chip fully able to deliver flashed.” - Yes, the chip from us. 
"Also the fan of the laptop is running at full speed all the time, and sometimes the laptop shuts down immediately. " - contact problem or thermal Problem.
regards,
Eugen Müller
Then i sent this mail :
Ok, i did some further research to the bios chip delivered by you.
Also checked out if there where contact or thermal problems.
None of these things is an issue, so i landed back on a forum with information about biosses.
Here i found out that the ME region of the bios chip never has been written.
Only the system bios was written, so the notebook would power up, and can do the basic things.
BUT the ME firmware is not written onto it, that’s wat causes the problem. IMEI is also a part of the power management etc.
Maybe it’s usefull to read back this thread about the chip you delivered.
N53JQ Management Engine file.
Then this was the response :
Hello Chris,
IT’S NOT OUR FIRST CHIP.
"…BUT the ME firmware is not written onto it " - It’s Bullshit !
regards,
Eugen Müller
So he doesn’t want to know anything of it.
I hope the people who order here will be aware of this.
Greetings, Chris
The ME region is written, otherwise it would’t even post. The problem is that they used a different chip without knowing how to configure the firmware (Flash Descriptor & ME VSCC) to work with it. So the 4MB image they flashed is not meant for a 8MB spi chip and not made for that specific chip as it’s missing from ME VSCC tables.
You can try telling them that they used a bigger sized chip and not the same model which causes problems. But honestly, you cannot expect much from a “company’s” support when they use Capital letters to refuse any wrongdoing and terms such as “bullshit” or even worse. Shame on them, that’s all I have to say.
i don’t think i’m even going to try anymore to mail him back. As i said, i ordered my own programmer, and with a little help of this forum, it’s going to be ok again 
But thanks for all the effort till now 
Greetings, Chris
OK, finaly my programmer has arrived!! Now i can start trying to reflash the original bios chip again and hope it works.
Hopefully you can help me with reprogramming the chip, and what software i need etc. I hope you can provide me with a complete bios image file, with the IMEI firmware included.
And i really don’t know yet how to connect the testclip and how i need to connect the chip to the testclip.
Greetings Chris
Ok, I suppose we will use the BIOS of the pre-flashed chip as that worked. The one at the old chip is corrupt and the stock ASUS probably lacks any board info. The ME will be recreated based on the settings of your old chip’s ME dump (or the dump I found online in case the former is not possible or the data are deleted/corrupted in it). So, I need a dump of the pre-flashed chip and a dump of the old chip.
If you don’t want to dump two chips, you can use FPT -d bios.bin -bios on your current system to get the BIOS of the new chip which is all we really need from it. Then I can use the other dump I’ve found for all the other regions, including ME settings for the recreation of a clean/configured ME region. It’s your choice.
For the programmer, once you have the chip you want to read/write, connect the clip to the doughterboard (seems connected at the picture) and then connect that to the correct programmer slot, meaning the 25xx one. These programmers tend to have a small diagram that point one slot as 24xx whereas the other as 25xx. At your picture I can’t see it but look underneath as well. For orientations, check the chip pinout from the manufacturer and locate the dot to figure out how to connect the doughterboard to the programmer correctly. Based on the dot and pin1 as well as the little diagram at the programmer, it should be easy. For the clip/chip orientation I’m not sure, I’m thinking that maybe the pink-colored wire is pin1 and thus you need to clip the chip accordingly, again based on the dot.
For software, you should be able to use the one provided by CodeRush at his CH341A thread.
Ok, i managed to read the original chip, and made a dump (.BIN) file from it. I will make a new post for the other chip when i managed to desolder it again 
Original 4Mbyte W25Q32V.rar (644 KB)
Great, I can verify that the Flash Descriptor & ME firmware/settings of the dump you provided and the dump I found online are the same with the obvious difference being the BIOS region which is corrupted at your dump as UEFITool can’t parse it. When you have the proper BIOS dumped, we can create a full SPI image to flash back to the original chip.
Ok, also managed to get out the new (faulty) chip, and the BIN file will be over here.
Faulty 8Mbyte W25Q64BV.rar (1.5 MB)
Oww, and this is the modification i made to my notebook, so i don’t have to take it apart anymore, the flat cables really don’t like the disassembly each time
![IMG_6685 [65175].JPG](/uploads/default/original/2X/e/e27ec508d944d266c596697b33e468983f8bcd56.jpeg)
Ok, the image is ready. What I’ve done based on what we were discussing:
1) Unlocked the Flash Descriptor so you won’t have to open the laptop and resolder in case of further fixes/modding. If you consider that a security risk, you can lock it any time you want via FPT.
2) Cleaned & Configured the ME with settings from your 4MB SPI dump (same as the other dump I found online). I used version 6.0.40.1215 which is the last clean region (RGN) we have, something needed for the guide I linked. If you want to later update to the latest 1.5MB 6.2.50.1062 firmware, you can use FWUpdate.
3) Used the BIOS from the 8MB SPI chip dump you provided which is proven to work fine on your system.
Hopefully I haven’t forgotten something. If you use the old 4MB SPI chip, no more actions should be required. After you erase the old 4MB SPI chip and reflash it with the programmer and the attached image, run Flash Programming Tool with command fptw -greset which is always needed after reflashing the ME region.
N53JQ_Fix.rar (1.5 MB)
Ok, thanks a 1000 times!!! I reflashed the chip with the provided SPI dump. Soldered the chip back in (which was verry easy now) and installed the memory etc back. When i started the notebook, everything seemed to be working again!! The fan is not running at 100% anymore, and the processor is not limited anymore at 900Mhz I also sealed the flat cables with epoxy Glue now. After powering on the laptop i did the FPTW -GRESET command, and the notebook shutted down immediately. After restarting everything still seemed to run fine.
Waiting for the glue now to dry, and then i will test the notebook for several hours.
Greetings, Chris