| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
cm-12.1
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
It seems newer devices need more weird empty transfers in order to
function.
|
| |
| |
| |
| |
| |
| | |
The Loke protocol supports 32-bit unsigned for the size of files being
flashed. However, POSIX file commands only support 32-bit (signed). As
such we now have platform specific support for larger files.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| | |
| | | |
Fix error condition check on finding correct usb interface.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
- Removed the "--delay <ms>" argument.
- Improved Action usage info.
|
| | |
| | |
| | |
| | |
| | |
| | | |
After each bulk transfer sent containing an Odin/Loke protocol packet, we now
send through a zero length bulk transfer. This is required for newer devices to
function correctly.
|
| |/ |
|
| |
| |
| |
| |
| |
| | |
AOSP does not support C++11
Change-Id: Iaf2e09cc05f8f867fa776b62313af6774ce47a56
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
Linux/README
OSX/README.txt
heimdall-frontend/doc-pak/README
heimdall/doc-pak/README
Change-Id: Ib5867d7a2be030290a3896ab82fe48a7f0a97e63
|
| |
| |
| |
| | |
release.
|
| |
| |
| |
| | |
boot, not download mode.
|
| |
| |
| |
| | |
100 MiB to 30 MiB.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- As a result of the above two points, there are no "known boot
partitions", and hence boot partitions are not automatically flashed
last.
- Made partitions flash in the order in order in which partition arguments
are specified. Hence, it's recommended that you specify boot partitions
last.
- Added --usb-level argument that can be used for debugging libusbx, or
flashing issues in general.
- Removed generally non-functional firmware dumping behaviour.
- Removed auto-resume functionality - Although this feature was definitely
nice to have; I believe it may be responsible for flashing compatibility
issues for a variety of devices.
- As a result of the above. In order perform another action after a
--no-reboot action, you must provide the --resume flag.
- Heimdall Frontend also has support for specifying the --resume flag
via a GUI. Heimdall Frontend also tries to keep track of your actions
and enable "Resume" automatically after a "No Reboot" action.
- Refactored quite a few of the actions, and code responsible for flashing
(particularly PIT file flashing).
- Bumped version to 1.4RC3 *however* this commit is not yet an official
release candidate. It's still a WIP. In particular build files still
have not been updated for Linux and OS X.
|
|/
|
|
|
|
| |
Heimdall detect: add more detail on verbose option.
Change-Id: I3858289a6270c8a7105b9e32dd4f124bbc7c1acd
|
| |
|
|
|
|
|
| |
care" to "unsupported".
- Changed block size in libpit to mean either block size or block offset.
|
|
|
|
|
|
|
|
|
| |
- Massive refactoring.
- Support for Qualcomm based devices.
- Print PIT from file.
- Use partition names as arguments e.g. --HIDDEN, --KERNEL, --MOVINAND etc.
- Heimdall Frontend UI improvements.
- And much more...
|
| |
|
| |
|
|
|
|
|
|
| |
reverse engineering of the flashing protocol. Turns out all I needed to do
was send the sequence size in bytes rather than performing weird
calculations (which when packed) end up representing the same thing!
|
|
|
|
| |
from the device's PIT)
|
|
|
|
|
|
|
| |
- Improved the no-reboot functionality, you no longer have to reboot to
flash more files.
- Fixed repartitioning functionality (thanks XDA user psych0phobia
for finding the problem!)
|
|
|
|
|
| |
- Made sure Heimdall command line always returns 1 if a device is not detected.
- Minor interface tweaks for Heimdall Frontend.
|
|
|
|
|
|
|
| |
- Fixed Heimdall command line support for PIT files without a reference to themselves.
- Added tool tips to Heimdall Frontend.
- Added heimdall 'info' and 'download-pit' actions.
- Made 'detect' action return 0 if a device is detected, 1 otherwise.
|
| |
|
| |
|
| |
|
|
|
|
| |
functionality and better support for more devices.
|
|
|