Thanks for all those who tried to help me out. Problem solved. The problem was the F - F adapter, it was wrongly wired ...
Bought a new one and everything seems to work smoothly!
Especially thanks to Joerg / Docscrutinizer on IRC for debugging!

Funny part: this caused vboost to always trip overcurrent protection as all devices got wrong VBUS polarity and luckily all shorted VBUS with internal protection diode, so probably nothing got destroyed. Some probably chinese fools connected the two USB-F end to end with not crossing the wires so left and right pins got swapped. A second adapter bought was of same brand and had same problem. Luckily the augmented booston script helped a lot to diagnose what's been wrong. Otherwise we probably never would have found out, assuming it's a data connection issue.

cheers
/j

If we are on topic of augmented booston - any luck finding how to incorporate into it a fix for "standby current"? It's especially hurting during train travels, when one want to use external USB keyboard, and no wall sockets are available to fix it.

I can confirm than running booston (via console), killing it (ctrl+c or killall from other terminal window) then boostoff fix it, but sometimes it's somehow "unstable" process. Once, it locked my6 device in constant vbus booston (including execution of vboostpattern), and no booston/boostoff, killing it or trying with HEN GUI solved problem - reboot was needed. Other time,s it work at second or third try, so after every booston/kill/boostoff combination, checking current is a must.

It consumes time and power, while connecting briefly to a charger solves it 100% times at first try. So, part in augmented booston, that "cheat" device about connected charger - for a while - would be really useful.

Again, thank for all great work joerg_re and others - BTW, MAG, we're keeping thumbs for HEN GUI package update

for first time use the a-a adapter must be checked with an usb optical mouse.
red led is ( always) connected to vbus by an resistor ( LE: or driven by inside chip ) and without any datalines or software control the led will light. this can be checked by cutting the green and white wires
so if no light >> something is dangerously wrong

i am using kernel-power-bootimg v48 ,when i am starting h-e-n, it shows stopping BME,after this i am attaching the F-F adapter with the flash drive. i select full speed host mode then selecting VBUS boost on then enumerate & then mount,its not mounting at all i looked at kernel messeges of h-e-n its shows
unable to connect no file system available
kernel message is [1113.860809] usb 1-1 :khubd timed out on ep0in len=0/64
please take a look at text file if any one knows what the wrong with wth h-e-n please give me solution

Don't connect (physically) Your device, before enabling vbus booston. Has been stated countless of times in this thread, including one page ago...

i did same as one page ago now i getting diffrent kernel messages like below, device not appear on file manager or filebox
usb1-1 new full speed USB device using musb_hdrc and address 6
usb 1-1:device not accepting address 6 error-71
hub 1-0:1-0 :unable to enumerate USB device on port 1
hub 1-0:1-0 : stat 7 ports 1 chg 0000 evt 0002
hub 1-0:1.0 : port 1 enable change status 00000101

Seems like some "generic" error. Are You using augmented booston by joerg_rw (search H-E-N announcement thread for it)? If no, you should try it. Anyway, just close H-E-N, open it again, and try again - slowing down. Once Your device (pendrive) will be properly recognized as High-speed, it should work.

Keep in mind that this problems seems to be non-existant, when using augmented booston. anyway, I'm getting everything connected at the first time for 100% of cases (aka totally hassle-free).

BTW

I've observed other thing, while using charging during hostmode. Randomly, devices connected to USB and powered externally, may become "unavailable" - only re-enabling vbus and enumerating (and boostoff/charge, if we want to charge while hostmode again) fixes that. It's hard to reproduce - sometimes, it happens few times during a 30 minutes, other day You don't get any problems for hours.

I've experienced this using very low-current devices (like generic USB keyboard), and on very reliable power sources - in fact, tested this with whole range, from regular 5V 2A ones, through stabilized ones, to ATX's modified to serve as power sources.

Talking about keyboard, when it happens, no LED's (like caps lock) works, device is literally disconnected on software level.

joerg_rw, any clues? It isn't high priority problem (well, unless it happens also with externally powered HDDs, during file transfer...) and I can live with that. Still, I would like to make it more reliable, if it's possible.

// Edit

Of course everything was done through Y-cable, so faulty powered HUB is filtered out.

Can any one guid me which kernel needs to install for h-e-n,i am using kernel-power-bootimg, is this ok for h-e-n?

Yes.

Ten chars.