@Pilgrimsmaster thanks for that Wiki page, Yes the Zeekr does support apple wallet using UWB, and this support is supposed to be coming to android in the near future. But nothing yet.
@optedoblivion perfect. thanks for that. From my resesarch, there is no functional difference between the NeXt and the NeXT2. I’m not sure how i feel about the LED, so might go the NeXt. But am undecided on this specifically yet. I guess that the LED at least gives an indication that its all working as expected.
@HelenMarsh Thanks for that detailed answer.
I agree on your approach. That does make sense. I will need to look into what the car will accept. A cursory search on aliexpress shows that i can just get NFC cards from there, and local Zeekr groups have mentions from people who have done this and added their cards to the car with success. But I have not tested this personally. The car came with 1 RFID card that was paired already. But there is a section in the menu that allows you to add more cards in. you just tap it onto the phone charger when in pairing mode (based on my reading of the owner manual)
Unfortunantly, there are no RFID / biohacking type groups that im aware of in Brisbane. Im happy to drive to someones place if they have a proxmark and are able to assist in determining what its doing.
Im happy to pull the trigger on the NeXT / NeXT2 and cross the EV bridge afterwards.
Is there any real differences between the genuine proxmark units, and the clones on Ali? Also, is there any real benefit to going the non-lite? and stepping it up to some of the more expensive units?
unlocking my computer would be handy also. From my reading, because this is done by just reading the serial number of the card and the KBR1, this should be fine to do with a populated ndef partition also?
This is the output from TagInfo when i scan it. I guess, i can just order a card and try writing it into the car. Do i just get a java card? what would be some ideal suggestions i can purchase and see what the car does with it?
** TagInfo Scan (version 6.2.0) 01-Sep-26 21:31:12 **
Report Type: -- IC INFO ------------------------------
# IC Manufacturer:
NXP Semiconductors
# IC Type:
Unknown IC implementing ISO/IEC 14443-4
# Card OS type:
Java Card
# Application information:
Global Platform card manager present
Visa card manager
-- NDEF ------------------------------
# No NDEF Data Storage Populated:
-- EXTRA ------------------------------
# ATS historical bytes details:
ISO/IEC 7816-4 coding
Category: [RFU]
# Global Platform information:
Java Card version 2.2
Global Platform version 2.1.1
GP Secure Channel Protocol: 02 option 15
Max. length APDU data field: 255 bytes
Visa card manager
* FCI: 0x6F108408A000000003000000A5049F6501FF |o..............e..|
# Card Production Life Cycle data (CPLC):
IC Fabricator: [not set]
IC Type: [unknown]
OS ID: [unknown]
OS release date: [not set]
OS release level: 0x0000
IC Fabrication Date: [not set]
IC Serial Number: 0x00000000
IC Batch Identifier: 0x0000
IC Module Fabricator: [not set]
IC Module Packaging Date: [not set]
ICC Manufacturer: [not set]
IC Embedding Date: [not set]
IC Pre-Personalizer: [not set]
IC Pre-Perso. Equipment Date: [not set]
IC Pre-Perso. Equipment ID: 0x00000000
IC Personalizer: [not set]
IC Personalization Date: [not set]
IC Perso. Equipment ID: 0x00000000
IC Personalizer: [unknown]
IC Personalization Date: [not set]
IC Perso. Equipment ID: 0x00000000
# File Control Information:
Default selected AID
0x6F108408A000000003000000A5049F6501FF |o..............e..|
# TagInfo Version:
Version :6.2.0
# Device Info:
Device Model :samsung ( SM-G965F )
Android OS Version :10
-- FULL SCAN ------------------------------
# Technologies Supported:
ISO/IEC 7816-4 compatible
ISO/IEC 14443-4 (Type A) compatible
ISO/IEC 14443-3 (Type A) compatible
# Android Technology Information:
Tag description:
* TAG: Tech [android.nfc.tech.IsoDep, android.nfc.tech.NfcA]
* Maximum transceive length: 65279 bytes
* Default maximum transceive time-out: 2000 ms
* Extended length APDUs supported
* Maximum transceive length: 253 bytes
* Default maximum transceive time-out: 618 ms
# Detailed Protocol Information:
ID: 6E:38:F4:AD
ATQA: 0x0800
SAK: 0x20
ATS: 0x6F00
* Max. accepted frame size: 16 bytes (FSCI: 0)
* Supported receive rates:
- 106 kbit/s
* Supported send rates:
- 106 kbit/s
* SFGT: 302.0 us
* FWT: 4.833 ms
* NAD not supported
* CID supported
* Historical bytes: [none]
--------------------------------------
Many thanks