I bricked an asus x553 laptop when trying to boot a usb with multiple efi partitions. I had created a usb that had multiple efi partitions inserted into the usb port hit the power button, hit the esc key so the laptop would find the multiple efi partitions for booting. At this point the laptop locks up. Did a hard power shutdown. When I turned the laptop back on it would hang at the Asus logo, no option to get into the uefi/bios firmware. Tried every key imaginable esc, f1-f12, delete, fn ctrl alt with various f-key/key combinations, still nothing.

I then removed the battery power pack, let it sit for a day, held down the power button without any power attached, to make sure all residual power was gone. When I turned the computer back on, the backlight would come on with just a blank black screen, no logo, no press this button message, no blinking cursor. Went to hitting ever key combination imaginable again without any results

Removed the hard drive and looked for any other batteries(found none) that might be attached to the motherboard, powered up, still the same results. Booting from a good cd or usb doesn't work either. The laptop acts like it is attempting to access harddrive, usb, cd, but after about a second or two stops.
The hard drive is good as I am able to boot it on another computer.

It maybe just a coincidence that the laptop broke, but I suspect I may have some how corrupted the firmware when trying to boot a usb with multiple efi partitions, Anybody know of a way to reload the firmware when no key combinations works, without replacing the firmware chip or the motherboard. or maybe some key combination that I may have overlooked.

You've tried hard. I did find this, but have no clue how good it is
As you've tried everything else, this is probably worth a shot.

Tried that already, several times ever left it unplug for a week without battery installed. Thanks anyways for the suggestion

Ring Asus then. If you have a guarantee or warranty, you need it now.

warranty is already out, it is over two years old

One last idea: use Rufus to burn specifically an AntiX64bit UEFIonly/GPT usb (iso, not dd).


I'm wondering whether the uefi-bios is 32bit or 64bit (not meaning the cpu)

Another remote-maybe, from some unfortunate keystrokes coincidence, maybe it tried to do a bios update, and erased the bios, which appears to be a dead-end. http://forum.notebookreview.com/thre...machine.174395

Yea, a sad loss; my sympathy. A few more random links: (yes, samsung != asus)
https://bbs.archlinux.org/viewtopic.php?id=157196
https://linux.slashdot.org/story/13/...sung-notebooks

https://unix.stackexchange.com/quest...ios-from-linux
https://www.phoronix.com/scan.php?pa...root-directory
https://www.reddit.com/r/thinkpad/co...d_linux_brick/
https://forums.theregister.co.uk/for...nux/#c_2765888
https://www.bleepingcomputer.com/for...-some-laptops/
https://www.eevblog.com/forum/chat/m...en-systems/75/
Note well: these may not be exactly relevant here, but were interesting reading.

Interesting reads. It is 64bit efi. I quess I found another way to brick efi firmware. You would think that the firmware people would protect the core components of the firmware better.

Update, I end up replacing the motherboard. Ordered it on line, had the new motherboard installed and the laptop up and running in about 20 minutes. I'll mark this as solved because business_kid's post has been found useful by others, from the research I did on my problem, and the links posted by GentleThotSeaMonkey make for some good reading..