Howdy y’all, back again. I recently got a bunch of work done recently (shout out to Shawn O’Hare), including putting in a flexUG4 and dUG4T I grabbed this past August. The flex in in the back of my hand is where my flexM1 used to be and the dUG4T is on the dorsal side of my right wrist. Neither were particularly traumatic installs and everything seemed to go in pretty smooth and it healing up nice. I’ve attached a picture with install outlines.
I’ve been getting some weird read issues on both of them using my Proxmark3 Easy with latest Iceman software. I can’t get a read at all on the flexUG4, whether through the Proxmark3 or through my phone. I’ve tried a few different orientations and still couldn’t get anything with an auto or an hf search. I also tried with my Pixel 11 to just see if I can get any NFC activity, but the NFC coil on the phone is also pretty temperamental given its placement. I will say the dUG4T reads alright now after some issues I had and its now emulating a 1k fine.
I tried hf 14a reader -@ and moved around, but it couldn’t find the flexUG4, but it found the dUG4T just fine. Any other commands I should try to see if it’s just in a soft-locked state and not just dead?
Got them all in on August 19th so we’re about 2.5 ish weeks out, with most of my swelling gone (it was actually the dUG4T that took the longest and made it look like my wrist was dislocated).
I think I did as well as I could try, I put the Proxmark into reader mode and tried every orientation of parallel I could. I tried making the Proxmark and implant coil orthogonal to each other, dead center on the Proxmark, underside and topside of the Proxmark, but no dice on any hits.
I had a lot of difficulty reading my flex UG4 that I got installed first week of Aug until just recently. I think the product page says 3-4 weeks of healing and that’s seeming to hold pretty true for me. I’d give it a little more time. It’s also taken me a little more practice in finding the antenna compared to my NeXT which is way more visible through the skin.
Both flex installs are traumatic, and importantly more traumatic than an xSeries.
where we often cite 2 weeks healing, that is more accurate for xSeries.
Where it throws it of, is with Flexies.
Though Flexies have better coupling, there is also more trauma.
There is probably a loose correlation between the Coupling vs Healing but as far as I am aware, this has never been conceptualized here on the Forum.
We coukd do this by looking at antenna geometry, surface area, and fluid interference
Reliable reads = (Surface Area of Antenna) / (Tissue Displacement Volume + Fluid Inflation Depth [from antenna to skin surface to reader])
I mean, it’s a bullshit calculation, but understanding the theory might help to explain that conclusion
@tac0s and @Pilgrimsmaster hate to be the bearer of bad news, but I believe that it is the current orientation. My flexMT in my other hand is still going strong though, granted that is spread out over a wider area. How much longer should I give it before I need to look at warranty’ing this and swapping it out (if that’s even a possibility)?
Although, I would still suggest you remove it.
Test it
Reinstall in 90⁰ orientation.
I don’t know the answer to this, so take the following with a pich of salt, but I would suggest, IF it is now damaged, your positioning MAY have voided the warranty.
I gave this a go, but weirdly it seems like my hf tune is not showing any voltage drops when I put any tags near it, whether they are working magic cards, original entry fobs, or the working dUG4T. The lf tune works fine and drops accordingly when I put a tag on it, going from 27V down to 7/8V. The hf tune just sits at 36V, but I can see on the diagnostic card that the HF is lit up, so it seems as if there may be a bug in the firmware.
Nah wood table and running the latest firmware, the hardware is a few years old but I’ve never run into any major issues with it.
[usb] pm3 --> hf tune
[=] Measuring HF antenna
[=] Press pm3 button or <Enter> to exit
[=] 36281 mV / 36 V / 36 Vmax
I also tried in a mixed style just to see if it was a display error but seems like the voltage is pretty consistent. I also reflashed the BootRom and Image but no dice.
I believe so, although the LED for the Easy line is not uncommented:
# If you want to use it, copy this file as Makefile.platform and adjust it to your needs
# Run 'make PLATFORM=' to get an exhaustive list of possible parameters for this file.
# By default PM3 RDV4 image is generated.
# Comment the line below and uncomment further down according to which device you have
#PLATFORM=PM3RDV4
# For PM3 RDV1, RDV2, Easy or rysccorps etc
# uncomment the line below
PLATFORM=PM3GENERIC
# For ICOPY-X and PM3 Max:
# uncomment the two lines below
#PLATFORM=PM3ICOPYX
#PLATFORM_EXTRAS=FLASH
# For PM3 Ultimate:
# uncomment the line below
#PLATFORM=PM3ULTIMATE
# If you want more than one PLATFORM_EXTRAS option, separate them by spaces:
#PLATFORM_EXTRAS=BTADDON
#PLATFORM_EXTRAS=FLASH
#PLATFORM_EXTRAS=SMARTCARD
#PLATFORM_EXTRAS=BTADDON FPC_USART_DEV FLASH
#STANDALONE=HF_UNISNIFF
# Uncomment the line below to set the correct LED order on board Proxmark3 Easy
# Only available with PLATFORM=PM3GENERIC
#LED_ORDER=PM3EASY
# Uncomment a line below to change default USART baud rate
# defaults to 115200 used by HC-05 in Blueshark
#USART_BAUD_RATE=19200
# Uncomment the lines below in order to make a 256KB image
# and comment out the lines above
#PLATFORM=PM3GENERIC
#PLATFORM_SIZE=256
#STANDALONE=
#SKIP_LF=1
#SKIP_HITAG=1
#SKIP_EM4x50=1
#SKIP_EM4x70=1
#SKIP_ZX8211=1
#SKIP_HF=1
#SKIP_ISO15693=1
#SKIP_LEGICRF=1
#SKIP_ISO14443b=1
#SKIP_ISO14443a=1
#SKIP_ICLASS=1
#SKIP_FELICA=1
#SKIP_NFCBARCODE=1
#SKIP_HFSNIFF=1
#SKIP_HFPLOT=1
# To accelerate repetitive compilations:
# Install package "ccache" -> Debian/Ubuntu: /usr/lib/ccache, Fedora/CentOS/RHEL: /usr/lib64/ccache
# And uncomment the following line
#export PATH := /usr/lib64/ccache:/usr/lib/ccache:${PATH}
# To install with sudo:
INSTALLSUDO=sudo
