Seems as though the activity for this device has dropped off, but I'm hoping there are still answers to be found.
I have a new device with firmware 3.3.2 that I am trying to root, but it's not quite going as planned.
I got as far as patching the extracted boot image, but I'm somewhat stuck there. The testing phase sort of doesn't work. To begin with, fastboot doesn't see the device... fastbogus thankfully does. However the device is unimpressed with the boot command.
Code:
>fastbogus.exe boot magisk_patched.img
Sending 'boot.img' (39000 KB) OKAY [ 0.894s]
Booting OKAY [ 0.119s]
Finished. Total time: 1.052s
The device just sits there as though nothing happened. I can reboot back into fastbootd or the main OS, but when in the bootloader it just doesn't care that it was sent the boot command.
Though there was no error, I thought maybe it didn't like the file for some reason so I tried telling it to boot the extracted image:
Code:
>fastbogus.exe boot boot_orig.img
Sending 'boot.img' (38520 KB) OKAY [ 0.888s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
Of course this error could happen for many reasons, but oddly enough it did reboot immediately. Unfortunately it is now stuck in an early stages bootloop. Never shows more than the ONYX screen before resetting a few seconds later. Plugged into a PC, it never shows as a USB device and adb/fastboot/fastbogus wait forever when trying to catch a device.
I was going to wait it out and hopefully it would run out of batteries and undo whatever went wrong... but I got bored waiting and tried some more. If I hold power until the blue LED turns off and immediately release, it stops bootlooping and stays on the ONYX screen. It connects as yet another USB device(05C6 900E)/QUSB_BULK_SN:#######. Forcing it to use WinUSB technically works but doesn't really work.
Code:
>edl /zf
Found EDL 900e
Requesting reset to fastboot... No response
All commands return no response. So I'm back to waiting for it to run out of batteries while bootlooping and hopefully fix itself somehow. I'm not completely new at this, but I'm not an expert either. I wouldn't have thought that just using the boot command while never flashing anything could cause something like this.