[LG G5 ROMs, Kernels, Recoveries, & Other Developme] autoprime:
going in order...

you mention "Uppercut was working at that time".. was this for the downgrade from N to M? or once you downgraded to M you tried UPPERCUT?

and once on M.. you used dirtysanta to exploit your phone and install the ADB root debug boot img?

Which H860 M build are you on at this point? 10A, 10B etc?

and ADB root is working on your phone.. but the issue is you can't access storage?

did you do anything besides flash the debug boot img to your phone.. any other images flashed? did you change the model anywhere?

does the phone still boot into android (with the debug boot img)? you just cant do much once booted into android because storage cant be accessed? or does the phone no longer boot into android?

so to try and fix your phone and access storage again.. you are trying to flash a KDZ in LGUP to get back to 100% stock?

and you are trying LGUP 1.10/1.11 while on M but all KDZs fail? Which KDZ build versions are you trying to flash? 10A, 10B etc? And all of these are H860 KDZs?

LG Flash Tool doesn't seem to work for people on G5 despite the cracked version bypassing some security measures. Ive at least never seen someone mentioning a successful flash on G5. Some have reported it working with other models (not G5).

If LGUP 1.11 isn't working with any KDZ I'm not sure if LGUP is your solution here.

I would try multiple different H860 KDZ versions for M... 10B.. 10C.. 10E.. etc. whatever is available.

And you are using a dll msi to install the DLL or placing the H860 dll manually in the LGUP folder? I'm wondering if a different H860 dll version placed in the LGUP folder may allow it to get past the "4% error" in LGUP.

also when flashing KDZ after KDZ in LGUP... always reboot the phone back into download mode before trying to flash the next KDZ.

dont try to flash a KDZ.. have it fail then immediately flash another KDZ... if there is no powering down and booting back into download mode after an error then you may be messing with a possibly successful combo. this wont always make things work.. but it will rule out any extra errors.

Besides fiddling with LGUP and every possible variable.. I see maybe 2 other ways of making progress... but they are potentially risky and you may end up losing root (which could make things even worse)... but hopefully you can still re-root if that were to happen. Both possibilities require you to still be able to boot into android.. and that any harm that may happen is all on you ;)

possibility #1: zero out your misc partition using adb root shell while booted in android... then immediately power off the phone (pull battery) then boot right into download mode and try reflashing in LGUP.. both 1.11 and 1.14+UPPERCUT. this shouldnt mess with your ability to boot into android (as long as u can already) or mess with root. safest of 2 choices.

run the following commands below in windows command prompt then power off.. boot to download mode and try again with LGUP.

adb root
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc

possibility #2: flash the original stock boot.img back to your phone instead of using the debug boot img (which may or may not be breaking access to storage)... and hopefully with a stock boot img you get access to storage back.. or it somehow makes LGUP work again. But discussion for possibility #2 is more suited for the ADB root thread, not here.

but you would have to obtain the original boot.img for the exact build you're on.. so if you're using H860 10M.. you need a H860 10M stock boot.img (this can be extracted from the stock KDZ you used to flash your phone to M using tools found on XDA).

then you would have to put the stock boot.img onto the phone.. then using adb root shell.. flash the stock boot.img you placed on the phone into the boot partition. commands for that would look something like the following:

adb push stock-boot.img /data/local/tmp
adb root
adb shell
dd if=/data/local/tmp/stock-boot.img of=/dev/block/bootdevice/by-name/boot

at this point you have just flashed the stock boot.img back to the boot partition.. removing the debug boot img.

when you reboot the phone.. android will now be running your stock boot.img and not the debug boot img.

you will no longer have access to adb root... but stock boot img MAY fix access to storage.. and it MAY fix flashing a KDZ in LGUP.

it also may not fix anything because something from the adb root procedure has messed things up even more than I've assumed.

wont know for sure until someone tests. Id assume you could re-run the adb root steps to get the debug boot img back in the future.