Quote:
Originally Posted by jljtgr
... I'm hoping there are still answers to be found.
|
There are! Hopefully. There are many different issues here.
"fastboot boot whatever.img" is great when it works, but unfortunately it doesn't always work for all devices and all images. I think that it has to do with how the cmdline that gets handed to the kernel is generated but I've never had a chance to deep dive. The "gold standard" for system images is always to flash and then reboot. Of course there is some risk with this too.
Just as an aside, I rip out my hair every time I see "FAILED (Status read failed (Too many links))". What is happening is that your device is disconnecting. That is reported internally in Windows as "A device attached to the system is not functioning", which returns an error code of 0x0000001f. A bad (since years) implementation of fastboot.exe is blithely (and ignorantly) converting that to a Linux error code of 31 (EMLINK). Then it happily tells you that you have used a chain of too many symbolic links.
Qualcomm actually has many different USB test modes, the most famous are 9008 and its stupid cousin 900e. 900e is mostly incapable of doing anything useful. I don't think you want to even waste your time talking to it.
Even within 9008 there are still two personalities, Mr. Hyde and Dr. Jekyll. The first rude and ignorant character only speaks "Sahara". You offer him a Firehose loader and then he begins to eloquently speak "Firehose". One of the problems is determining to whom you are speaking.
In your example you were speaking to 900e (doesn't work at all), trying to use the /z command (only works once you have loaded a Firehose loader) and were trying to do it with /zf (I've only seen Motorola supporting reboot to bootloader).
So, where does that leave you? Power dying might get you out of the loop since you didn't actually flash anything. Worst case is opening the device.