Now I want to reactivate my XA2, the installer recognizes it, USB debugging is activated in the developer options and then I should activate the boot loader. But this has already been done. This is the end of the installation.
Should I dispose of it or is there a solution?
Install twrp using the fastboot boot twrp-xa2.img command and then sideload the iode 6.4 zip file as per usual twrp installing. adb sideload nameof file.zip Or am I missing something here?
Hi Bellini,
Have you tried using another USB cable ?
If you are on Windows, when you go into device manager, do you see a /!\ warning sign on the device called “Android” ? If so you need to install android_winusb.inf drivers using this guide : https://droidwin.com/android-usb-drivers/
The error with the installer is USB cable independent.
I no longer used the installer, but went through the flash-all.bat manually. The installation worked, but errors appeared in the log.
Result log:
mke2fs 1.46.6 (1-Feb-2023)
Creating filesystem with 5242880 4k blocks and 1310720 inodes
Filesystem UUID: 3818f34c-3f9d-11f0-912c-e9eb1db75c8e
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
Warning: skip copying userdata image avb footer due to sparse image.
Sending 'userdata' (4360 KB) OKAY [ 0.100s]
Writing 'userdata' OKAY [ 0.001s]
Finished. Total time: 0.479s
Der Befehl "tOTO" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
--------------------------------------------
Bootloader Version...: 1310-0301_X_Boot_SDM630_LA1.0_O_121
Baseband Version.....: 1311-2845_50.2.A.0.400
Serial Number........: CQ30003KNA
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Setting current slot to 'b' OKAY [ 0.006s]
extracting fastboot-info.txt (0 MB) to RAM...
archive does not contain 'super_empty.img'
archive does not contain 'super_empty.img'
extracting boot.img (28 MB) to disk... took 0.065s
archive does not contain 'boot.sig'
archive does not contain 'super_empty.img'
Warning: skip copying boot_b image avb footer (boot_b partition size: 0, boot_b image size: 30060544).
Sending 'boot_b' (29356 KB) OKAY [ 0.655s]
Writing 'boot_b' OKAY [ 0.000s]
archive does not contain 'super_empty.img'
extracting system.img (2511 MB) to disk... took 10.984s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/5 (518068 KB) OKAY [ 11.419s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 2/5 (516208 KB) OKAY [ 15.366s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 3/5 (516208 KB) OKAY [ 15.406s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 4/5 (516208 KB) OKAY [ 15.436s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 5/5 (504636 KB) OKAY [ 15.146s]
Writing 'system_b' OKAY [ 0.000s]
archive does not contain 'super_empty.img'
extracting vendor.img (390 MB) to disk... took 1.668s
archive does not contain 'vendor.sig'
archive does not contain 'super_empty.img'
Warning: skip copying vendor image avb footer due to sparse image.
Sending 'vendor' (400368 KB) OKAY [ 8.805s]
Writing 'vendor' OKAY [ 0.000s]
Finished. Total time: 99.369s
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.002s
Press any key to exit...
I tried to install iode on a pixel 7a and encountered the same problem, i am stuck on the OEM unlocking! Is there already a solution to the problem? i don’t want to install it manually 
but i also wanted to try out iode, but it isn’t a good start if the installer doesn’t work… thanks in advance
Unfortunately, I don’t have a pixel and don’t want to give you the wrong advice. If I were you, I would try this:
scroll to the middle. That’s exactly what I did with my XPERIA XA2.
Maybe @Nolan could have a better idea than the question about the USB cable.
I had not the same but similar issues.
Both “OEM unlocking” and “USB debugging” must be activated in developer settings.
Looking for other Android drivers in advanced options of Windows Update helped here. (I installed via Windows.)
In this forum in my experience you only get support of other users. If nothing helps I recommend to contact the iodé support. There eventually I received the help I needed to accomplish the installation.
support@iode.tech or
kundenservice@iode.tech (German speaking)
However, it took 2 weeks to get an answer.
Many thanks for the answers 
The installer needs your phone to have both “USB Debugging” and “OEM unlocking” toggled to proceed with the installation. The latter is true even when the device has already been unlocked.
If you want to bypass enable OEM unlocking (maybe because the options does not show up in the developper options), you could reboot to fastboot manually.