Mifare Classic gen1/gen2 (+ regular) card writing support #399
Conversation
github-actions
bot
added
the
translation changes
|
Selecting "Skip default dictionary" Followed by "Empty 0 Keys" and then trying recover keys gives a index out of range in typed data patch... |
|
Trying to save only the uid of a non mifare classic card (was possible before) causes a null exceptions in saveHFCard |
|
No real error, but trying to write a mifare save to a non mifare card just stalls? maybe displaying a warning message or smthng? |
|
oh yeah, step 3 also needs to be scrollable or else it gets cut off depending on window size... |
|
and writing to non magic cards always gives a "smthng went wrong"... (prob because of block 0 verification) Edit: looks like that one card just wasnt writable? still, the dispaly sounds like a good idea oh and missmatched dump/card sizes also need to be taken into account (eg 4k dump, 1k card) |
|
writing a uid only card gives a invalid value not inclusive range... |
|
writing to gen2/generic is broken in general? got out my 1k magic gen 2, dumped a 1k (not 1k ev1, etc, just 1k), tried writing and theres always a error in card writing |
|
oh yeah and writing needs to give a popup on the lite (just like when reading) or else everything breaks... |
|
Have a log |
| Future<bool> isMagic(dynamic data) async { | ||
| await communicator.send14ARaw(Uint8List(1)); // reset | ||
|
|
||
| Uint8List data = await communicator.send14ARaw(Uint8List.fromList([0x40]), |
There was a problem hiding this comment.
why do it via raw and not the predefined commands? (if there are any)
|
oh yeah, just noticed, card export is borked too? |
|
Works on windows using Mifare Classic 1K Gen1 EV. But only with non corrupted save file (#400). |
Running autodetect on a T55 for example throws a invalid data length... Other than that, everything seems to work fine?
|
|
On iPhone SE(2020) writing card cannot display normally, some are out of screen. |
aw, right, sht... That entire thing needs to be a scrollview... ok, next hotfix or pr ig... @Foxushka |
|
It's really perfect though, thanks for update! |
|
|
Release 1.0 coming right after merging this