Welcome
|
You have to register before you can post on our site.
|
|
[REQUEST] Asus A550JK & K550JK & X550JK BIOS Unlock
|
Posts: 1,776
Threads: 0
Joined: Aug 2018
Reputation:
42
04-15-2019, 01:59 AM
(This post was last modified: 04-15-2019, 02:00 AM by Lost_N_BIOS.)
Yes, if you proceeded after a Red FPT error in red then you probably did, why did you go ahead after it gave you a warning in red (meaning stop and think or ask)?
Size mismatch error cannot happen if you use the command I gave you above and the provided file, sounds like you used the stock BIOS file or some other file, or forgot to put the -bios flag in your entered command.
Nothing you can do now except purchase CH341A flash programmer + SOIC8 test clip cable, these are $2.50 + $3.50 on ebay, but long wait on delivery, you can find at other places (and ebay) that are close to you, or will ship faster for more $$
Posts: 39
Threads: 1
Joined: Apr 2019
Reputation:
0
Aw, well.. I have no way other than that, ain't I?
Posts: 1,776
Threads: 0
Joined: Aug 2018
Reputation:
42
Yes, that is only way to recover from this. Don't worry, you can fix it once you have the tools!
So what happened, did you use wrong file, or leave out the -bios flag?
Posts: 39
Threads: 1
Joined: Apr 2019
Reputation:
0
04-15-2019, 02:12 AM
(This post was last modified: 04-15-2019, 02:17 AM by shong57.)
Nothing, I did exactly what you did. But I chose the fptw64.exe. I also noticed that the size of the bios file was identical, that's probably why I didn't ask earlier. Thinking that it was just a small error.
Posts: 1,776
Threads: 0
Joined: Aug 2018
Reputation:
42
04-15-2019, 02:18 AM
(This post was last modified: 04-15-2019, 02:19 AM by Lost_N_BIOS.)
It has to be one of the two things I mentioned, typed in wrong file name and fed it some other BIOS or a stock/encapsulated BIOS file, or didn't put in the -bios flag, only those things would cause size mismatch error. Using FPTwx64 wouldn't make a difference in this or any other regard, it's same as regular 32 bit version
Sorry this happened to your system, for the next guys reading any time you see a warning in red, stop and do not proceed, take a screenshot and ask someone to advise on how to proceed
Posts: 39
Threads: 1
Joined: Apr 2019
Reputation:
0
04-15-2019, 02:21 AM
(This post was last modified: 04-15-2019, 04:15 AM by shong57.)
Well, I put all the flags in too. And the file I used to flash was exactly the one you sent me.
EDIT: I'll give it another shot later once I get my laptop fixed. Or make another bios mod request if I get a new laptop, just in-case the shop ever decided to just give me a new one. It was still under warranty of that shop.
Posts: 1,776
Threads: 0
Joined: Aug 2018
Reputation:
42
04-15-2019, 04:55 AM
(This post was last modified: 04-15-2019, 04:59 AM by Lost_N_BIOS.)
No need to RMA, unless you're close and it's easy to do, etc, you can fix it for under $5 with flash programmer.
All the flags? There was only one, the -bios flag which tells it to flash the BIOS region only. This is how you dumped the BIOS as well, and is why it's impossible to get a size warning when using this flash since it only dumps the BIOS region, or flashes it, and it's always same size on your BIOS. -f means flash, so not really a flag but command to flash the file
The BIOS I sent you would not give you a size warning in FPT, unless flashed without the -bios flag
Maybe it's possible that FPTx64 caused some abnormality, but I highly doubt that, it's 100% same as the 32bit only able to run x64 coding. If you try it again once fixed, and it gives you warning again, stop when you see the warning, show me an image and close the tab and use the normal FPTw.exe as I have said all along - I help 100's of people a week use this without issue on Win7-10 x64 systems, the only reason you had issue initially was not using admin command prompt, nothing to do with using 32 vs 64 bit FPT
Posts: 39
Threads: 1
Joined: Apr 2019
Reputation:
0
04-15-2019, 08:50 AM
(This post was last modified: 04-15-2019, 08:56 AM by shong57.)
Yeah, I will. And well, I don't want to wait for that, since service shops are near me locally. Even if it means I would be able to fix it when I brick it again if I decide to buy it, but I learned a hard lesson today. Which made me learn to stop and think, or ask when in doubt. I also used admin command prompt this time though.
Also, a question. If I stopped before restarting the laptop and flash the original bios with winflash tool that came with it? I mean, would it prevent me from bricking the laptop?
(Sorry for slightly bad english, I'm a little stuck with vocabs sometimes.)
Posts: 1,776
Threads: 0
Joined: Aug 2018
Reputation:
42
Well at least you have local place to RMA to quickly then, that makes RMA easier, tell them it died on reboot after "Some Asus Updates via auto-updater" that way they can't blame you for bad BIOS flash.
Yes, if after that bad flash went in (After the size warning and then flashed anyway), and you did not reboot, then you could have reflashed your original FPT dump and it would have been fixed. No Winflash tool to be used here.
Posts: 39
Threads: 1
Joined: Apr 2019
Reputation:
0
04-16-2019, 07:01 AM
(This post was last modified: 04-16-2019, 07:02 AM by shong57.)
Mhm, but I think it's safer to use winflash and flash the original bios from the asus support site. Makes me feel more comfortable to see a ui than command prompt interface.
But yeah, thanks for being here with me and providing help!
|
Users browsing this thread: 2 Guest(s)
|