You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SALT should allow flashing a KDZ while in download mode.
Requirements:
a secureboot off / unlocked device*
(*)The goal was always to allow flashing for locked devices, too. Flashing will work perfectly fine as long as your LAF protocol version is v100002 or lower but on later versions more work is required to workaround the new implemented protocol checks.
The whole implementation is W.I.P (while there is no one actually working on it atm) and should NOT be used until finished.
The following is required to finish the implementation:
pre-check ARB on device
extract KDZ + DZ
pre-check ARB of the chosen KDZ
warn user about any diff between those ARB's
detect/get/.. (how ?/ where?) what partitions of the KDZ should be flashed[1]
offer option to factory reset (wipe userdata + keystore)
flash all good partitions
verify flashing + warn if smth failed
[1] The most critical part because it differs between devices and sometimes models. There must be a way to identify which partitions are required or as a workaround flash only known partitions. The latter will require to make known lists of partitions for each device/model and warn / abort if there is none. not very useful but the only way to avoid bricks which can happen very easily if a partition is named slightly different etc.
If you still want to experiment with that (you have been warned) enable flashing support with:
./salt --experimental
then choose Flash (kdz)
note: for Flash (folder) see #17
The text was updated successfully, but these errors were encountered:
SALT should allow flashing a KDZ while in download mode.
Requirements:
(*)The goal was always to allow flashing for locked devices, too. Flashing will work perfectly fine as long as your LAF protocol version is v100002 or lower but on later versions more work is required to workaround the new implemented protocol checks.
The whole implementation is W.I.P (while there is no one actually working on it atm) and should NOT be used until finished.
The following is required to finish the implementation:
[1] The most critical part because it differs between devices and sometimes models. There must be a way to identify which partitions are required or as a workaround flash only known partitions. The latter will require to make known lists of partitions for each device/model and warn / abort if there is none. not very useful but the only way to avoid bricks which can happen very easily if a partition is named slightly different etc.
If you still want to experiment with that (you have been warned) enable flashing support with:
./salt --experimental
then choose
Flash (kdz)
note: for
Flash (folder)
see #17The text was updated successfully, but these errors were encountered: