travisgoodspeed / goodv Goto Github PK

I was successfully at erasing tag. After that I send 02 A0 07 . It returned 00DC000300538A. What does last two bytes mean and why they aren't in wiki?
Also, is there any information on how to interpret result from A1 command?

About 8 minutes after A0 command was sent, sensor changed state from "Warming up" to "To Activate". I tried 2 different ones, and all of them had the same behavior. What does it mean? What am I doing wrong? Is it even possible to reactivate sensor after erasing it?

When trying to get info about tag, dump, erase or program I see error message: programming, read or erase error.
I'm using RF430TAL152H tag (used) and OnePlus 7 Pro. Also, NXP TagInfo says that there are some errors communicating with tag. Though I was able to read it content with proxmark3
logcat.txt

Hi Guys,

I've been working with TAL chips for last two/three weeks.
As already described in many areas the FRAM part of memory is pretty well known.

Other areas of memory are still not fully clear.
I wonder if there is anything that much related to sensor live cycle in SRAM part of the memory.

Currently my sensor managed to survive for 28 days, now suddenly crashed and I cannot restore it back to working state.
The maximum lifetime was set to 31 days, but still it crashed on 28. (for the whole time, until last minute sensor was in amazing condition, results were almost same to glucometer)

During my tests on dead other sensors I was able to bring back the sensor to alive from 0x06 status, however on this one which reached 28 I cannot anymore. Full memory import from fresh not used sensor also do not help here. Right after activation it becoming to 0x06 state.

Since I cannot find a method to replace SRAM part of memory I can't play that much there.
But SRAM seems to be changing even on sensor that is not yet unpacked/started.

I wonder what else can be causing the sensor to dead except for the FRAM which is earased to sensor from box state.

Any ideas?

Currently the RF430TAL152H backdoor password, which is only needed for medical devices and not for the GoodTag or other devices that use the publicly documented RF430 chips, is replaced by 0xFF bytes. To use those chips, the backdoor behavior must be repaired by inserting the proper password.

It would be easier if the app would load the password from a file or SQLite database in the SDCard's partition, so that there is no need to edit the source code. Close this issue when that is cleanly implemented and documented.

Close this issue when the user is presented with a menu of prebuilt firmware images, imported from GoodTag with each release. Raw TI-TXT images from the SD card should also be supported.

When I was reading a sensor of RF430TAL152H, Tag was lost when calling transceive method. Before this, It also threw a PerfMonitor binderTransact:Time =1004ms interface=android.nfc.INfcTag code=6 Exception.
Before this, I use ISO15693 general command 20 to directly read all blocks can be read, is there anything to set?

I tried to program a GoodTag11 with GoodV.
The app returned a "PROGRAMMING ERROR :(" and logcat shows:

01-28 14:51:44.379 32494 32494 D GoodV   : Tag tapped to program.
01-28 14:51:44.381 32494 32494 V GoodV   : Writing 1952 bytes to 0xF860.
01-28 14:51:44.381 32494 32494 E GoodV   : No block number for address: 63584
01-28 14:51:44.381 32494 32494 E GoodV   : Illegal block adr.

Hi! I know I am late to this, but just came across this and would try to restart a glucose monitor as shown here:
https://www.youtube.com/watch?v=HcA-X8sEB8o
I got the app on my Android (downloaded APK from Releases).
But it says the glucose monitor is locked. And as such, i can't erase it. What is the solution?

Video references some speeches for instructions, but I am unable to find those speeches.

Close this issue when we have a proper icon for the app.

Could you post the assembled APK of the application or the instructions for building it?

Hi bro,

I am trying to perform memory dump of RF430TAL152H but unfortunately it keep failing at some point.
Looking at the android studio seems it hang on different sections each time.

Phone is near to the sensor, but it keep failing.

2021-03-20 13:34:27.471 25056-25056/com.kk4vcz.goodv D/GoodV: read(): address=@4678 len=8
2021-03-20 13:34:27.485 25056-25056/com.kk4vcz.goodv D/GoodV: read(): address=@4680 len=8
2021-03-20 13:34:27.499 25056-25056/com.kk4vcz.goodv D/GoodV: read(): address=@4688 len=8

Do you have any ideas? or maybe we can divide the memory into few parts?