Late 2013 Keyboard / Trackpad still unresponsive AFTER EFI 1.3 update

Question

I thought I would start a new thread / discussion since the previous thread here seems to be riddled with "install the update" suggestions and off topic assistance such as battery life questions. I have also logged detailed information regarding this issue on my professional blog here.
Anyway, here is a short, condensed version of my story. I have had two brand new late 2013 Retina MacBook Pro's with the 2.4/16GB/256 configuration. Since the config I chose is a CTO, this problem has been going on since the day the first model arrived (December 10th, 2013). The EFI update was preinstalled on both systems and I can verify that because the boot ROM version is MBP111.0138.B03 (the boot rom prior to the update ended in B00 or B01). I am also an AASP and an ACMT meaning that I am certified and employed with a company that allows me to fix all Apple hardware under warranty. I am well-versed in technology and Apple hardware and I have never seen anything quite like this.
Here is the quick summary of things I have attempted and I have been able to re-recreate the issue:
The system will not mount the root device when I boot via a known good external hard drive running 10.9.1. Verbose mode and Single user mode reports a still waiting for root device error.
The system (rMBP) will not boot from another system (late 2011 MacBook Pro 13") when said system (late 2011 MacBook Pro) pushed into target disk mode via thunderbolt.
My system, rMBP, will boot up with the internal SSD but will not allow the keyboard and track pad to function. The caps lock key will not illuminate. The keyboard and track pad will work OUTSIDE of 10.9.1, however. I have installed a clean internet recovery version of Mavericks over 4 times.
If I put my system, rMBP, into target disk mode and connect to any other computer via thunderbolt and boot it on the other Apple systems, the operating system running on the internal SSD of the rMBP will work just fine -- keyboard and mouse included (again, as a target disk mode thunderbolt connection to another host).
If I use a remote agent to connect to my rMBP such as LogMeIn or vnc, the keyboard and mouse will work just fine from the remote system which leaves me to beleive that this is not a software issue nor is it fully a hardware issue since the keyboard and mouse work outside of mavericks.
I believe we are still dealing with a firmware issue here. It took several tries to create a bootable device for the late 2013 rMBP since NONE of my other up-to-date and verified working external drives will boot but I finally created a bootable USB stick. When I run the system from the USB stick, the keyboard and trackpad will work but if I touch the keyboard and / or trackpad in 5 second intervals, I will receive the following error:
1/4/14 4:44:41.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:45:00.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:45:43.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:49:03.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:50:20.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:51:24.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:52:49.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:53:00.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:53:10.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:55:25.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:56:07.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:57:06.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:58:40.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
1/4/14 4:59:45.000 PM
kernel[0]
The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
I had actually created a system log query to search for the above. The search string includes "the USB " and any entry after 1/1/2014. The above error should only present itself when waking an Apple system from sleep and instead it happens on every touch after, at least, a 5 second period of non-use.
When I remote into the system using LogMeIn, VNC or even use an application called ShareMouse which shares the keyboard and mouse of my Windows system with any other computer on the network presuming they have ShareMouse also installed, I can use the system as I would expect, without continuous error in the console log. When I check the system information, Bluetooth is completely disabled and the USB hub does not report address information. Since the keyboard, track pad, Bluetooth peripheral and USB ports all sit on the same USB stack / hub this leads me to think there is a firmware / driver failure occurring after Mavericks loads. The only two errors I see when I am using a remote keyboard and mouse via a remote service is as follows:
1/5/14 6:58:16.000 PM kernel[0]: The USB device HubDevice (Port 1 of Hub at 0xfa000000) may have caused a wake by issuing a remote wakeup (2)
1/5/14 6:58:16.000 PM kernel[0]: The USB device Apple Internal Keyboard / Track pad (Port 2 of Hub at 0xfa100000) may have caused a wake by issuing a remote wakeup (3)
Bottom line: Even for those of you who have installed the EFI 1.3 update and have verified that your freezing issues have ceased, for the most part, could you check your console log for the above error. My guess is, you will still see the error repeated there in 5 second intervals if you touch the keyboard, put your hands up for 5 seconds, touch the keyboard and / or track pad again. My concerns is that this is a product line issue since it has occurred on two brand new systems and the log errors appeared on another model on display in an Apple store. (The display model was logged into an Admin account so I took the liberty of checking the console log.)

Answer 1

I'm tired of this message. Bought a Mac 13" retina from bestbuy that was shipped to me on December 24th. The finder took a long time to load 'All My Files' with three to five second delay. My older macbook unibody (late 2009)was instantaneous. My wife's macbook aluminum (2011) also loaded the files instantaneously. Sorry I digressed but while I was trying to research that issue, I was caught up in the console and multiple of these,'The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)' kept showing up whenever I touched the trackpad in intervals of 6-7 seconds.
Called up apple, used screen sharing and after spending an hour was transferred to the second tier tech. The second tier rep troubleshooted and told me it WAS an issue and asked me to go to apple store to run diagnostics and that most likely I'll receive another notebook in exchange since it fell within 14 day period. I told him the internet was filled with this discussion and asked if it was prevalent. He said it was the first time he has come across this issue and most forums on the internet may not be addressing my specific issue. I wasn't convinced and simply returned it at best buy.
The unfortunate thing is I sold my macbook unibody and having owned 2 macbooks for last eight years I caved and ordered another 13". After a week and a half I received it today and guess what, I see the same message filling up my console.
I noted the following,
* Use guest account and you'll never see the message,'The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)'. All admin accounts created will throw that error.
Though off topic I'd like to state what happened with the Finder's 'All my files' issue:
1. Once I upgraded my older macbook unibody to mavericks, the 'All my files' took longer to load as the new macbook pro.
2. I was able to replicate the same slow load times with macbook aluminium(2011) when I upgraded it to mavericks.
Oh, I also showed the slowness to the representatives and all they tried doing was reindex spotlight which did no good.
So much for 1799$ notebook and the "free" OS. Very disappointed.