Unfortunately absence of update.log means the Ldr.bin has tried to initiate the write process without successfully even starting it although 'Loader' showed on the screen, but 'Loader' presence indicates at least something happened. It may be that Ldr.bin has written the correct 2077 boot info to regions 5 and 43 now, so best you try it again just in case because if it's now got correct bootloader and x-loader on board it should write the firmware bin files to their correct regions next attempt. First check that there isn't a file named 'last_id.bin' created in the 1947 folder from the failed write, if it's there remove it before trying again. I'm unsure at what point 'last-id.bin' is created, but if it's at the the very start when 'Loader' appears then it should be there.

If it sticks on Loader again kill the process as before but let it go for an hour or so to be absolutely sure it's not doing anything. I should tell you that i'm not a programmer so i cannot help with complex firmware/bin file manipulation, therefore anything we can try from here will only involve more of the same guesswork and basic potential solutions from me.

Let's have the results please before we go further with this 'blind man's bluff'. If the miracle happens and it boots with touch this time, immediately [Only registered and activated users can see links. ] several times. I've uncertain from your earlier posts exactly how far it's been booting, but because you reported that you were able to look at the GarminDevice.xml therefore it has Mass Storage Mode or Media Transfer Protocol available and that indicates to me it's been booting to the main screen. So please check the xml file again if nothing happens when you re-insert the microSD and if it now shows '2077' instead of '1947' in the xml then change the name of the 1947 folder to 2077 in the card and try that.