[bassme]

Thanks for the reply Renate! The detail was great. And so fast, I feel bad I couldn't back at this sooner. I had a little time to work on this some more, with no headway.

Originally Posted by Renate

Don't

Yeah.... I realized during later commands, and looking back at the previous posts, that was unwise. And with your further explanation here it makes even more sense.

Originally Posted by Renate

First, make sure you have the latest edl.exe, it's 132,608 bytes.

The edl.exe I have is 132,608 bytes.

Originally Posted by Renate

So, in the first phase if anything doesn't work for any reason you must do a reset and get a fresh EDL.

I assume reset here is holding the power button down until the Air C reboots back into normal commands, then run

adb reboot edl

I'm fairly certain I was doing that the first time (I read another of your posts saying that), but definitely did when I was working on things this time. If I didn't get the response you indicated I would reset.

Originally Posted by Renate

There could also be a problem with bad USB cables or flakey hubs. If the desktop machine crashes, there is clearly a problem there because it should not happen under any circumstances.

The reboot I mentioned was an update reboot. I had forgotten I had turned the option to reboot right after an update back on for a specific purpose, I turned that option back off right after that. I tried several different USB cables, all with the same result. I'm plugging these straight into my laptop, so no external hub. I used every port, both USB A and USB C.

Originally Posted by Renate

Next you should do a sanity check and list the partitions:

edl.exe /g

I tried this and got

Found EDL 9008
Configuring...
Could not write device

I then reset, and tried

edl.exe /u /g

with the same result.

Next, thinking maybe before I try listing the partitions that I should do the loader command first I reset then tried

edl.exe /lq662.elf

and got

Found EDL 9008
Could not read device

So, the only question remaining is whether you have the right loader in the first part. If there is an issue you should quote the HWID and Hash (but not the serial number) that it spit out at the beginning and the size and MD5 (if you can) of the loader.

I assume since I'm not getting any response from edl.exe that I can't list the HWID and Hash, if I'm wrong and I'm just showing my ignorance here please tell me how to get that. The MD5 of what was renamed q662.elf matches the OP.

I'll keep trying things later when I get off work.