1. 06 Aug, 2018 1 commit
  2. 05 Apr, 2018 1 commit
  3. 04 Apr, 2018 4 commits
  4. 05 Feb, 2018 1 commit
  5. 30 Jan, 2018 1 commit
  6. 03 Jan, 2018 7 commits
  7. 29 Dec, 2017 1 commit
  8. 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
  9. 14 Dec, 2017 1 commit
  10. 11 Dec, 2017 1 commit
  11. 10 Dec, 2017 2 commits
  12. 07 Dec, 2017 6 commits
  13. 04 Dec, 2017 3 commits
  14. 30 Nov, 2017 2 commits
    • steadfasterX's avatar
      testing: new approach for disk_fd · 8f4989d7
      steadfasterX authored
      problem: on LP there was absolute no issue in writing big partitions like
      system but beginning from MM on it fails on different sizes like
      at ~268MB for H815v20p and on H815v29a that limits seems to be
      at ~786 MB.
      tested: doing a challenge/response before each CHUNK write (!) so for
      each 16 KB or in my case 1 MB. result: nothing. still failing at the same
      step.
      this commit instead will open a new disk file descriptor after a given size
      (max_fd_size in bytes). The whole commit is marked as testing as the
      comm.close does not work since a while for the G4. Regardless I was
      able to write the full 4 GB partition after that change (on H815v20p).
      More tests needed!
      8f4989d7
    • steadfasterX's avatar
      testing: new approach for disk_fd · c4350e0e
      steadfasterX authored
      problem: on LP there was absolute no issue in writing big partitions like
      system but beginning from MM on it fails on different sizes like
      at ~268MB for H815v20p and on H815v29a that limits seems to be
      at ~786 MB.
      tested: doing a challenge/response before each CHUNK write (!) so for
      each 16 KB or in my case 1 MB. result: nothing. still failing at the same
      step.
      this commit instead will open a new disk file descriptor after a given size
      (max_fd_size in bytes). The whole commit is marked as testing as the
      comm.close does not work since a while for the G4. Regardless I was
      able to write the full 4 GB partition after that change (on H815v20p).
      More tests needed!
      c4350e0e
  15. 24 Nov, 2017 1 commit
  16. 23 Nov, 2017 4 commits
  17. 22 Nov, 2017 2 commits