Samsung Galaxy S7 stuck in boot loop after failed installation of 2.4.1

This is really driving me crazy as there doesn’t seem to be a direct link between where the phone “says” the file is and where it “actually” is, from the adb perspective. As an example I have an update image on the sd card and I should be able to use adp pull to download it to the PC as it exists. The phone says the file is on sdcard1 and /storage/3935-6237 but adb pull fails miserably:

[xxxx ]$ adb pull /storage/3935-6237/
adb: error: failed to stat remote object ‘/storage/3935-6237/’: No such file or directory

Is there a way to list the S7 directories from an adb perspective ?