The dump of nonvol region 41 seems ok, it's of the expected size and appearance. That doesn't mean for sure there's no bad data in there, that's still possible but if so it's incidental and not what's causing the bootloop.

As for the dump of region 14, it's only a partial copy at 6.67 MB (6,995,968 bytes) when the full region size is 16.0 MB (16,777,216 bytes). Note that a region dump also includes empty space, i.e. rgn14 is always larger than the fw_all.bin that's been flashed to it. V6.30's fw_all.bin's size is 8.90 MB (9,340,160 bytes), the remainder up to 16 MB is empty space which would just copy as multiple FFs in hex. So that dumping has failed less than half-way through, under 7 MB, thus the 'error' note in update.log for it. Region 127 has dumped zero bytes and therefore failed immediately, also showing 'error'.

I think it's probably pointless but you could try to erase all 3 regions, if successful the device will stop bootlooping and stick on "System Software Missing" message and default to persistent preboot mode. However even then there's no guarantee that regions 114 & 127 will be re-flashable, they may still refuse to accept being written, like now. Region 41 will be re-constructed with essential data if the device can fully reboot anyway.

If you want to attempt to erase them, be sure to remove last_id.bin, optionally you can remove any of the other BINs still on the card or leave them there. Change the content of update.txt as follows:
Code:
Please Login or Register to see the links
You know the rest of the flashing routine by now. Likely only 41 will erase and 14 &127 will return an error in update.log.