Hi @amghwk - sorry that I didn't notice your earlier post.
Edit: Your problem may be different, but you might try my way anyway.
There are also mysterious cases where "fastboot boot" does not work but "fastboot flash" and then regular boot does work. If you have backups you should be able to play safely.
Hi @Machinus
If you have access to a (real, not virtual) Windows box, I can probably help you. I have an EDL utility for Windows. What you are trying to do is very simple, and it should be simple.
Go to the website in my signature and navigate to the EDL page. It's a bit of a beta, but I'm willing to work with anybody that is having problems.
Step 0: Download edl.exe, it's 132kB with no dependencies.
Step 1: Get into EDL (05c6/9008) mode
Step 2: Got a driver for it? If not download "Zadig" and give it one.
Step 3: Got a loader for it? If not download this, it should be the correct one if you have the same model as the OP:
https://github.com/bkerler/Loaders/r...4665_FHPRG.bin
Oh, you were looking forward to downloading 100 Megs of loaders that you will never use. Sorry to disappoint you.
Step 4: Rename the file something sensible.
Step5:
Code:
C:\>edl.exe /lsomething-sensible
He, he, I was only kidding about something sensible, don't forget the "/l" before it.
Step 6: Since you're running A/B you have to know which boot_x is the right one:
Step 7: One of them is inactive, choose the other one:
Code:
C:\>edl.exe /u /r /pboot_a boot.img /t
And the result should be the (correct) ~20Megs and not 20Megs + 80Megs of zeroes.
Step 8: If you are in doubt what you have just downloaded, get my ImgUtil.exe and do:
Code:
C:\>imgutil.exe /v boot.img
Header: 596 (00000254)
Kernel: 12,937,496 (00C56918) @ 00008000
Payload: 12,636,840 (00C0D2A8)
DTB: 300,656 (00049670)
Ramdisk: 0 (00000000) @ 01000000
Second: 0 (00000000) @ 00F00000
(Or something similar, the numbers will be different for you.)
Good luck!