galante2123 - I am hoping you can help me in the right direction. I am extremely frustrated as a new user trying to get this to work on my Pi running RaspBMC. It looks like you have experienced exactly what seems to be happening in my case. (details below)
It took me most multiple tries on Windows, Linux and OSX machines to finally get a successful firmware upgrade (to 2.3 in my case.) I too experienced the hanging you describe - in most cases not having any impact on upgrading the firmware. I finally did get a successful upgrade to 2.3. I too configured my Harmony remote with the Flirc device. I also enabled the RaspBMC settings for the IR Remote feature and selected the Windows MC defaults. When that did not work, I tried the lirc setting. Still no go. I also tried the Flirc configuration add-on the allows you to program the flirc on RaspBMC. Despite multiple tries - that utility continues to show disconnected on my Pi. I feel like I've been banging my head against the wall trying to get my new flirc to work on RaspBMC...with no luck. The funny thing is that I can plug the flirc into my windows laptop and it controls xbmc on that PC just fine!
I believe I did this. I added http://xbmc.flirc.tv/ as a source, and installed the addons. from what I can tell this gave me the ability to "program" the flirc via XBMC rather than having to use windows....IF the flirc was identified by my Pi. (But when I am in the configuration interface, it just shows disconnected.)
I am not sure what you mean by "added the udev rule as well." I am wondering if that is my missing piece that is preventing the flirc from being recognized on my RaspBMC...Is that possible? I am not sure how to add that udev rule. Can you help me understand how to add that rule?
Is there anything else I should be looking at to get the flirc recognized?
Thanks a lot for any insight you can provide.
Ed