I told you this as an answer to your previous question. It has nothing to do with the nRF51 development kit the ARM Cortex processor in the nRF series is little endian. It's documented in the nRF series manual, even if it weren't, although ARM allows for big or little endian, I can't think of one I've seen which is big, and even if you weren't absolutely sure from the documentation and the usual practice, there's a register you can read in the processor which tells you what the endianess is.
You appear to still be trying to solve a problem you don't have.
How the data is transferred over the BLE link has nothing whatsoever to do with whether the nRF51 (which is an ARM Cortex-M0) is big or little endian.
As already noted in the previous thread, the BLE link is simply a stream of bytes - it gives no significance to what those bytes represent, nor how they are to be interpreted (other than as defined in any standard Profile you may be using).
It's just the same as sending data over a UART link: you can send the low byte first, or the high byte first; it makes absolutely no difference whatsoever to the UART - they are all just bytes.
If you were to display that on a terminal, it would just show the first byte first - it would have no idea whether it formed part of a larger value nor, therefore, what part it represented.
