1. 14 Sep, 2018 1 commit
  2. 12 Sep, 2018 1 commit
  3. 05 Sep, 2018 1 commit
  4. 23 Aug, 2018 3 commits
  5. 22 Aug, 2018 1 commit
  6. 27 Jul, 2018 1 commit
  7. 09 Apr, 2018 1 commit
  8. 08 Apr, 2018 3 commits
  9. 06 Apr, 2018 2 commits
  10. 04 Apr, 2018 7 commits
  11. 05 Feb, 2018 1 commit
  12. 30 Jan, 2018 1 commit
  13. 03 Jan, 2018 7 commits
  14. 29 Dec, 2017 1 commit
  15. 20 Dec, 2017 2 commits
    • steadfasterX's avatar
      fix: CR_NEEDED and not using as global · 26f1e804
      steadfasterX authored
      26f1e804
    • steadfasterX's avatar
      fix: detection of challenge/response · 6a4365fa
      steadfasterX authored
      previously we thought the protocol version is enough to identify
      if the KILO etc is needed or not. Unfortunately this is not true as
      we have devices like the H811 running on MM (20v) which requires
      KILO but still using protocol 1.0.0.1 !
      Same goes for some H815 firmwares running MM (20g) while other
      MM versions on H815 (20p) have the newer protocol implemented.
      regardless of which firmware flashed the need of using KILO or not
      can be done on the G4 by the USB product ID (633e do not need it
      while 633a need it).
      
      Adding other USB product IDs who needs KILO can be simply done
      by adding them to the new function:
      kilo_lg_product_ids
      6a4365fa
  16. 14 Dec, 2017 1 commit
  17. 11 Dec, 2017 1 commit
  18. 10 Dec, 2017 2 commits
  19. 07 Dec, 2017 3 commits