FELix icon indicating copy to clipboard operation
FELix copied to clipboard

Fails to execute commands

Open leonidofsparta opened this issue 4 years ago • 1 comments

Hello. I've go an x64 WIndows machine on which I managed to execute felix,, but it still gives me touble. this is what I get if I for example ask for info: ruby felix --info FELix 1.0 RC6 by Lolet Warning: I don't give any warranty on this software. You use it at own risk! ────────────────────────────────────

  • Connecting to device at port 2, FEL device 1@6 1f3a:efe8 [OK]
  • Getting info [FATAL] Failed to get the data ( An unexpected answer length (8 <> 32))
  • Cleaning up

I have a XIaomi MiReader with an Allwinner B300 chipset.

leonidofsparta avatar Aug 17 '20 07:08 leonidofsparta

same with an older A13 device--I see output like this:

./felix -v --info
FELix 1.0 RC6 by Lolet
Warning: I don't give any warranty on this software. You use it at own risk!
────────────────────────────────────
* Connecting to device at port 2, FEL device 1@57 1f3a:efe8	[OK]
--> (   32) USBWrite	(Prepare for write of 16 bytes)
--> (   16) FESInfo (0x203): 03 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00
<-- (   13) AWUSBResponse	0x0, status ok
--> (   32) USBRead	(Prepare for read of 32 bytes)
<-- (   13) AWUSBResponse	0x0, status ok
<-- (    8) FELStatusResponse	mark 65535, tag 0, state 1
[FATAL]	
Failed to get the data (
An unexpected answer length (13 <> 32))
* Cleaning up                                            	[OK]


./felix -v --read boot.img --item boot
FELix 1.0 RC6 by Lolet
Warning: I don't give any warranty on this software. You use it at own risk!
────────────────────────────────────
* Connecting to device at port 2, FEL device 1@57 1f3a:efe8	[OK]
--> (   32) USBWrite	(Prepare for write of 16 bytes)
--> (   16) FESUpload (0x207): 07 02 00 00 00 00 00 00 00 40 00 00 00 00 00 00
<-- (   13) AWUSBResponse	0x0, status ok
--> (   32) USBRead	(Prepare for read of 16384 bytes)
<-- (   13) AWUSBResponse	0x0, status ok
<-- (    8) FELStatusResponse	mark 65535, tag 0, state 1
[FATAL]	
Failed to get the data (
An unexpected answer length (13 <> 16384))
* Cleaning up                                            	[OK]


the --status flag works and outputs this:

./felix --status
FELix 1.0 RC6 by Lolet
Warning: I don't give any warranty on this software. You use it at own risk!
────────────────────────────────────
* Connecting to device at port 2, FEL device 1@57 1f3a:efe8	[OK]
  magic                  AWUSBFEX
  board                  Allwinner A13/A10s (sun5i), revision 0
  fw                     1
  mode                   fel
  data_flag              0x00000044
  data_length            0x00000008
  data_start_address     0x00007e00
  reserved               [0, 0, 0, 0, 0, 0, 0, 0]
* Cleaning up                                            	[OK]

it is possible to dump memory by address and length--I spose I'll just figure out the addresses and dump it that way in my case...

./felix --read test.img --address 0 --length 65536
FELix 1.0 RC6 by Lolet
Warning: I don't give any warranty on this software. You use it at own risk!
────────────────────────────────────
* Connecting to device at port 2, FEL device 1@57 1f3a:efe8	[OK]
* fel: Reading data (65536/65536 bytes)                  	[OK]
* Cleaning up                                            	[OK]

combs avatar Nov 24 '20 17:11 combs