Proxmark3 developers community

Research, development and trades concerning the powerful Proxmark3 device.

Remember; sharing is caring. Bring something back to the community.


"Learn the tools of the trade the hard way." +Fravia

You are not logged in.

#1 2020-03-14 06:40:05

Firesight
Contributor
Registered: 2020-03-12
Posts: 6

[SOLVED] Proxmark RDV4 bootloader problem on Kali

kali@kali:~/proxmark3$ pm3-flash-all
[=] Waiting for Proxmark3 to appear...
[=] Session log /home/kali/.proxmark3/log_20200313.txt 
[+] About to use the following files:          
[+]     /usr/local/bin/../share/proxmark3/firmware/bootrom.elf          
[+]     /usr/local/bin/../share/proxmark3/firmware/fullimage.elf          
[+] Waiting for Proxmark3 to appear on /dev/ttyACM0           
[\] .Found           
[+] Entering bootloader...           
[+] (Press and release the button only to abort )          
[+] Waiting for Proxmark3 to appear on /dev/ttyACM0           
[|] ........... Found           
[!!] ====================== OBS ! ===========================================           
[!!] Note: Your bootloader does not understand the new CMD_BL_VERSION command            
[!!] It is recommended that you first update your bootloader alone,            
[!!] reboot the Proxmark3 then only update the main firmware 
          
[=] Available memory on this board: UNKNOWN 
          
[!!] ====================== OBS ! ======================================           
[!!] Note: Your bootloader does not understand the new CHIP_INFO command            
[!!] It is recommended that you first update your bootloader alone,            
[!!] reboot the Proxmark3 then only update the main firmware 
          
[=] Permitted flash range: 0x00100000-0x00140000          
[+] Loading ELF file /usr/local/bin/../share/proxmark3/firmware/bootrom.elf           
[+] Loading usable ELF segments:          
[+]    0 : V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94          
[+]    1 : V 0x00200000 P 0x00100200 (0x00000de0->0x00000de0) [R X] @0x298          
          
[+] Loading ELF file /usr/local/bin/../share/proxmark3/firmware/fullimage.elf           
[+] Loading usable ELF segments:          
[+]    0 : V 0x00102000 P 0x00102000 (0x00040ff8->0x00040ff8) [R X] @0x94          
[!!] Error: PHDR is not contained in Flash          
[+] All done.    

I then searched and was able to locate this website https://www.ivoidwarranties.tech/posts/rfid-nfc-research/proxmark-rdv4-booterloader-fix/

Following the procedure I run into the following

kali@kali:~/proxmark3$ proxmark3 /dev/tty.usbmodemiceman1 --flash --unlock-bootloader --image /usr/local/share/proxmark3/firmware/bootrom.elf
[=] Session log /home/kali/.proxmark3/log_20200313.txt 
[+] About to use the following file:          
[+]     /usr/local/share/proxmark3/firmware/bootrom.elf          
[+] Waiting for Proxmark3 to appear on /dev/tty.usbmodemiceman1           
[\] ............................................................          
[!] ERROR: invalid serial port /dev/tty.usbmodemiceman1 
          
[!!] Could not find Proxmark3 on /dev/tty.usbmodemiceman1 .
          
[!!] Aborted on error.          

Have a nice day! 


Repository being used is git clone https://github.com/RfidResearchGroup/proxmark3.git

Instructions being followed are https://github.com/RfidResearchGroup/proxmark3/blob/master/doc/md/Installation_Instructions/Linux-Installation-Instructions.md

Kali version being used

kali@kali:/$ lsb_release -a
No LSB modules are available.
Distributor ID: Kali
Description:    Kali GNU/Linux Rolling
Release:        2020.1
Codename:       kali-rolling
kali@kali:/$ cat /etc/issue
Kali GNU/Linux Rolling \n \l

kali@kali:/$ uname -a
Linux kali 5.4.0-kali2-amd64 #1 SMP Debian 5.4.8-1kali1 (2020-01-06) x86_64 GNU/Linux

I'm not sure how to proceed

Thanks,
Firesight

Last edited by Firesight (2020-03-20 00:55:35)

Offline

#2 2020-03-14 07:25:09

Riffruepel
Contributor
From: Germany / Magdeburg
Registered: 2019-04-17
Posts: 20

Re: [SOLVED] Proxmark RDV4 bootloader problem on Kali

I solved the problem as follows:

Important Delete Modem Manager:
sudo apt remove modemmanager

Enter the following command in the Proxmark folder.

make accessrights

Check again which interface the Proxmark got with:

sudo dmesg | grep -i usb

Then restart the Proxmarkt device.
Then just flash the bootloader with the command:

proxmark3 / dev / ttyACM0 --flash --unlock-bootloader --image bootrom.elf

Then restart the Proxmarkt device.

Then the full Imigae flashing with:

proxmark3 / dev / ttyACM0 --flash --unlock-bootloader --image bootrom.elf --image fullimage.elf

Finished

Good luck

Offline

#3 2020-03-14 07:49:54

Firesight
Contributor
Registered: 2020-03-12
Posts: 6

Re: [SOLVED] Proxmark RDV4 bootloader problem on Kali

@Riffruepel

Thanks for the help when I follow your directions I get as follows

kali@kali:~/proxmark3$ sudo apt remove modemmanager
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package 'modemmanager' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 180 not upgraded.


kali@kali:~/proxmark3$ make accessrights

===================================================================
Platform name:     Proxmark3 rdv4
PLATFORM:          PM3RDV4
Platform extras:   No extra selected
Included options:  SMARTCARD FLASH -DRDV4 LF HITAG ISO15693 LEGICRF ISO14443b ISO14443a ICLASS FELICA NFCBARCODE HFSNIFF HFPLOT
Standalone mode:   LF_SAMYRUN
===================================================================
sudo adduser kali dialout
The user `kali' is already a member of `dialout'.

when I then run this command

kali@kali:~/proxmark3$ sudo dmesg | grep -i usb

I get this plus the usual my other hardware


548.278115] usb 1-1.2: USB disconnect, device number 3
[  548.513483] usb 1-1.2: new full-speed USB device number 6 using ehci-pci
[  553.713297] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[  553.713308] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  553.713320] usb 1-1.2: Product: proxmark3
[  553.713322] usb 1-1.2: Manufacturer: proxmark.org
[  553.713323] usb 1-1.2: SerialNumber: iceman
[  553.714032] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[  555.189973] usb 1-1.2: USB disconnect, device number 6
[  557.017488] usb 1-1.2: new full-speed USB device number 7 using ehci-pci
[  557.129710] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[  557.129722] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  557.129727] usb 1-1.2: Product: proxmark3
[  557.129732] usb 1-1.2: Manufacturer: proxmark.org
[  557.129736] usb 1-1.2: SerialNumber: iceman
[  557.130528] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[  771.614422] usb 1-1.2: USB disconnect, device number 7
[  771.837475] usb 1-1.2: new full-speed USB device number 8 using ehci-pci
[  777.201464] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[  777.201475] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  777.201481] usb 1-1.2: Product: proxmark3
[  777.201485] usb 1-1.2: Manufacturer: proxmark.org
[  777.201489] usb 1-1.2: SerialNumber: iceman
[  777.202197] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[  778.526081] usb 1-1.2: USB disconnect, device number 8
[  780.341404] usb 1-1.2: new full-speed USB device number 9 using ehci-pci
[  780.452854] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[  780.452866] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  780.452871] usb 1-1.2: Product: proxmark3
[  780.452876] usb 1-1.2: Manufacturer: proxmark.org
[  780.452880] usb 1-1.2: SerialNumber: iceman
[  780.453799] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[ 1801.068905] usb 1-1.2: USB disconnect, device number 9
[ 1801.293390] usb 1-1.2: new full-speed USB device number 10 using ehci-pci
[ 1801.404741] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[ 1801.404752] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1801.404757] usb 1-1.2: Product: proxmark3
[ 1801.404762] usb 1-1.2: Manufacturer: proxmark.org
[ 1801.404766] usb 1-1.2: SerialNumber: iceman
[ 1801.405705] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[ 1802.860842] usb 1-1.2: USB disconnect, device number 10
[ 1804.661334] usb 1-1.2: new full-speed USB device number 11 using ehci-pci
[ 1804.773274] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[ 1804.773311] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1804.773317] usb 1-1.2: Product: proxmark3
[ 1804.773322] usb 1-1.2: Manufacturer: proxmark.org
[ 1804.773326] usb 1-1.2: SerialNumber: iceman
[ 1804.774059] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[ 3449.513261] usb 1-1.2: USB disconnect, device number 11
[ 3449.749291] usb 1-1.2: new full-speed USB device number 12 using ehci-pci
[ 3454.961085] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[ 3454.961097] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3454.961102] usb 1-1.2: Product: proxmark3
[ 3454.961107] usb 1-1.2: Manufacturer: proxmark.org
[ 3454.961111] usb 1-1.2: SerialNumber: iceman
[ 3454.962284] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[ 3456.425419] usb 1-1.2: USB disconnect, device number 12
[ 3458.201292] usb 1-1.2: new full-speed USB device number 13 using ehci-pci
[ 3458.312872] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[ 3458.312883] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3458.312889] usb 1-1.2: Product: proxmark3
[ 3458.312893] usb 1-1.2: Manufacturer: proxmark.org
[ 3458.312898] usb 1-1.2: SerialNumber: iceman
[ 3458.313919] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[ 4892.119631] usb 1-1.2: USB disconnect, device number 13
[ 4892.390248] usb 1-1.2: new full-speed USB device number 14 using ehci-pci
[ 4897.521351] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[ 4897.521363] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4897.521369] usb 1-1.2: Product: proxmark3
[ 4897.521373] usb 1-1.2: Manufacturer: proxmark.org
[ 4897.521378] usb 1-1.2: SerialNumber: iceman
[ 4897.522383] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[ 4899.031811] usb 1-1.2: USB disconnect, device number 14
[ 4900.869196] usb 1-1.2: new full-speed USB device number 15 using ehci-pci
[ 4900.981549] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[ 4900.981561] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4900.981566] usb 1-1.2: Product: proxmark3
[ 4900.981571] usb 1-1.2: Manufacturer: proxmark.org
[ 4900.981575] usb 1-1.2: SerialNumber: iceman
[ 4900.982347] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[ 5617.479589] usb 1-1.2: USB disconnect, device number 15
[ 5617.701143] usb 1-1.2: new full-speed USB device number 16 using ehci-pci
[ 5623.025142] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[ 5623.025153] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5623.025159] usb 1-1.2: Product: proxmark3
[ 5623.025163] usb 1-1.2: Manufacturer: proxmark.org
[ 5623.025168] usb 1-1.2: SerialNumber: iceman
[ 5623.025894] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[ 5624.391417] usb 1-1.2: USB disconnect, device number 16
[ 5626.193146] usb 1-1.2: new full-speed USB device number 17 using ehci-pci
[ 5626.304893] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[ 5626.304905] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5626.304910] usb 1-1.2: Product: proxmark3
[ 5626.304915] usb 1-1.2: Manufacturer: proxmark.org
[ 5626.304919] usb 1-1.2: SerialNumber: iceman
[ 5626.305715] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[ 6717.835087] usb 1-1.2: USB disconnect, device number 17
[ 6718.069074] usb 1-1.2: new full-speed USB device number 18 using ehci-pci
[ 6723.312938] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[ 6723.312997] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6723.313009] usb 1-1.2: Product: proxmark3
[ 6723.313016] usb 1-1.2: Manufacturer: proxmark.org
[ 6723.313022] usb 1-1.2: SerialNumber: iceman
[ 6723.313780] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[ 6724.747139] usb 1-1.2: USB disconnect, device number 18
[ 6726.529072] usb 1-1.2: new full-speed USB device number 19 using ehci-pci
[ 6726.641582] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[ 6726.641593] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6726.641599] usb 1-1.2: Product: proxmark3
[ 6726.641603] usb 1-1.2: Manufacturer: proxmark.org
[ 6726.641608] usb 1-1.2: SerialNumber: iceman
[ 6726.642383] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[ 8209.343949] usb 1-1.2: USB disconnect, device number 19
[ 8597.164948] usb 1-1.2: new full-speed USB device number 20 using ehci-pci
[ 8599.064942] usb 1-1.2: new full-speed USB device number 21 using ehci-pci
[ 8599.176976] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[ 8599.176988] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8599.176993] usb 1-1.2: Product: proxmark3
[ 8599.176998] usb 1-1.2: Manufacturer: proxmark.org
[ 8599.177002] usb 1-1.2: SerialNumber: iceman
[ 8599.177829] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[ 8655.868513] usb 1-1.2: USB disconnect, device number 21
[ 8656.172945] usb 1-1.2: new full-speed USB device number 22 using ehci-pci
[ 8661.488982] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[ 8661.488993] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8661.488998] usb 1-1.2: Product: proxmark3
[ 8661.489003] usb 1-1.2: Manufacturer: proxmark.org
[ 8661.489007] usb 1-1.2: SerialNumber: iceman
[ 8661.489850] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[ 8662.780619] usb 1-1.2: USB disconnect, device number 22
[ 8664.644943] usb 1-1.2: new full-speed USB device number 23 using ehci-pci
[ 8664.757535] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[ 8664.757546] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8664.757552] usb 1-1.2: Product: proxmark3
[ 8664.757556] usb 1-1.2: Manufacturer: proxmark.org
[ 8664.757561] usb 1-1.2: SerialNumber: iceman
[ 8664.758369] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[11990.923082] usb 1-1.2: USB disconnect, device number 23
[11993.204722] usb 1-1.2: new full-speed USB device number 24 using ehci-pci
[11995.120721] usb 1-1.2: new full-speed USB device number 25 using ehci-pci
[11995.231832] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[11995.231843] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[11995.231849] usb 1-1.2: Product: proxmark3
[11995.231854] usb 1-1.2: Manufacturer: proxmark.org
[11995.231859] usb 1-1.2: SerialNumber: iceman
[11995.232647] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[12072.436011] usb 1-1.2: USB disconnect, device number 25
[12074.304719] usb 1-1.2: new full-speed USB device number 26 using ehci-pci
[12076.200715] usb 1-1.2: new full-speed USB device number 27 using ehci-pci
[12076.313366] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[12076.313377] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[12076.313383] usb 1-1.2: Product: proxmark3
[12076.313387] usb 1-1.2: Manufacturer: proxmark.org
[12076.313392] usb 1-1.2: SerialNumber: iceman
[12076.314129] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device

Not sure why I get such a long list of the Proxmark?

Then I run as you listed

kali@kali:~/proxmark3$ proxmark3 / dev / ttyACM0 --flash --unlock-bootloader --image bootrom.elf
[=] Session log /home/kali/.proxmark3/log_20200313.txt
[!!] ERROR: cannot parse command line. We got /  as port and now we got also: dev

Thanks,
Firesight

Last edited by Firesight (2020-03-18 19:05:15)

Offline

#4 2020-03-14 07:50:13

iceman
Administrator
Registered: 2013-04-25
Posts: 6,703
Website

Re: [SOLVED] Proxmark RDV4 bootloader problem on Kali

Sounds like you followed the documentations,
https://github.com/RfidResearchGroup/pr … uctions.md
https://github.com/RfidResearchGroup/pr … scarded.md

One issue with updating the bootrom is that the device gets a new usb enumeration. Next time I suggest you use the provided shell scripts.  They make it a bit easier when it comes to flashing.  If the device get a new usb enumeration,  you would only run the script once more.   Quite straigth forward nowdays.

-- flashing the device
./pm3-flash-bootloader
./pm3-flash-fullimage

-- running the client
./pm3

If you feel the love,  https://www.patreon.com/iceman1001

modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Online

#5 2020-03-14 08:44:40

Firesight
Contributor
Registered: 2020-03-12
Posts: 6

Re: [SOLVED] Proxmark RDV4 bootloader problem on Kali

Hi Iceman,

yes i did follow the documentation for the RfidResearchGroup

I am a new to linux in general and have pushed my roughly weeks research knowledge to be able to get this far.

So with that being said I'm not sure what you mean by that.

But I assume you mean that I need to run those commands and that the USB address may change during the process and to run them again if that happens but I'm not sure how run them to begin with.

I tried and recieved as follows.

kali@kali:~/proxmark3$ ./pm3-flash-bootloader
bash: ./pm3-flash-bootloader: No such file or directory
kali@kali:~/proxmark3$ pm3-flash-bootloader
bash: pm3-flash-bootloader: command not found
kali@kali:~/proxmark3$ ./pm3
[=] Waiting for Proxmark3 to appear...
[=] Session log /home/kali/.proxmark3/log_20200314.txt 
[=] Using UART port /dev/ttyACM0           
unknown command:: 0x61334d50[!!] ERROR: cannot communicate with the Proxmark

Forgive my terrible coding skills or lack there of

Thanks,
Firesight

Last edited by Firesight (2020-03-18 19:08:32)

Offline

#6 2020-03-14 11:14:49

iceman
Administrator
Registered: 2013-04-25
Posts: 6,703
Website

Re: [SOLVED] Proxmark RDV4 bootloader problem on Kali

in order to flash,  you must have compiled before...  And the compilation must pass.
There is a strange bug in latest arm-none-eabi-gcc package for debian (kali is based upon)  which we pushed a temp fix last night.
So,
pull latest from github,
compile
flash bootrom
flash fullimage

run client.

that should do the trick for you.


If you feel the love,  https://www.patreon.com/iceman1001

modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Online

#7 2020-03-18 19:00:33

Firesight
Contributor
Registered: 2020-03-12
Posts: 6

Re: [SOLVED] Proxmark RDV4 bootloader problem on Kali

Iceman,

Thank you for the help I was able to get past this step with your help.

when I run the client I now get

kali@kali:~/proxmark3$ proxmark3 /dev/ttyACM0
[=] Session log /home/kali/.proxmark3/log_20200318.txt 
[=] Using UART port /dev/ttyACM0           
[=] Communicating with PM3 over USB-CDC           

          
  ██████╗ ███╗   ███╗ ████╗            
  ██╔══██╗████╗ ████║   ══█║           
  ██████╔╝██╔████╔██║ ████╔╝           
  ██╔═══╝ ██║╚██╔╝██║   ══█║     ❄  iceman@icesql.net ☕          
  ██║     ██║ ╚═╝ ██║ ████╔╝    https://github.com/rfidresearchgroup/proxmark3/          
  ╚═╝     ╚═╝     ╚═╝ ╚═══╝  pre-release v4.0          
          

** (proxmark3:5486): WARNING **: 10:44:05.483: Pixbuf theme: Cannot load pixmap file /usr/share/themes/Kali-Dark/gtk-2.0/assets/trough-progressbar.png: Failed to load image “/usr/share/themes/Kali-Dark/gtk-2.0/assets/trough-progressbar.png”: Fatal error in PNG image file: IDAT: fixed block coding not supported


(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

** (proxmark3:5486): WARNING **: 10:44:05.483: Invalid borders specified for theme pixmap:
        /usr/share/themes/Kali-Dark/gtk-2.0/assets/trough-progressbar.png,
borders don't fit within the image

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(proxmark3:5486): GdkPixbuf-CRITICAL **: 10:44:05.483: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

 [ Proxmark3 RFID instrument ]           

 [ CLIENT ]           
  client: RRG/Iceman          
  compiled with GCC 9.2.1 20200104 OS:Linux ARCH:x86_64          

 [ PROXMARK3 RDV4 ]           
  external flash:                  present           
  smartcard reader:                present           

 [ PROXMARK3 RDV4 Extras ]           
  FPC USART for BT add-on support: absent           
          
 [ ARM ]
  bootrom: RRG/Iceman/master/eab2ebaf 2020-03-18 10:09:53
       os: RRG/Iceman/master/eab2ebaf 2020-03-18 10:10:07
  compiled with GCC 8.3.1 20190703 (release) [gcc-8-branch revision 273027]

 [ FPGA ]
  LF image built for 2s30vq100 on 2020-02-22 at 12:51:14
  HF image built for 2s30vq100 on 2020-01-12 at 15:31:16          

 [ Hardware ]           
  --= uC: AT91SAM7S512 Rev B          
  --= Embedded Processor: ARM7TDMI          
  --= Nonvolatile Program Memory Size: 512K bytes, Used: 279619 bytes (53%) Free: 244669 bytes (47%)          
  --= Second Nonvolatile Program Memory Size: None          
  --= Internal SRAM Size: 64K bytes          
  --= Architecture Identifier: AT91SAM7Sxx Series          
  --= Nonvolatile Program Memory Type: Embedded Flash Memory          

          
[usb] pm3 --> proxmark3 /dev/ttyACM0

I'm assuming since it says Critical and Failed on each of the lines there is something wrong.

How do I go about fixing this?

Thanks,
Firesight

Offline

#8 2020-03-18 19:26:47

iceman
Administrator
Registered: 2013-04-25
Posts: 6,703
Website

Re: [SOLVED] Proxmark RDV4 bootloader problem on Kali


If you feel the love,  https://www.patreon.com/iceman1001

modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Online

#9 2020-03-19 06:36:57

Firesight
Contributor
Registered: 2020-03-12
Posts: 6

Re: [SOLVED] Proxmark RDV4 bootloader problem on Kali

Iceman,

Thanks for that document you linked.

I didn't know theme could cause a software issue like that.

I did get my RDV4.01 working now.

I'm now able to read some of my test cards that were included and some others I ordered.

Regards,
Firesight

Offline

#10 2020-03-19 09:16:56

iceman
Administrator
Registered: 2013-04-25
Posts: 6,703
Website

Re: [SOLVED] Proxmark RDV4 bootloader problem on Kali

I suggest you edit your first post and add the prefix [solved] to the subject.


If you feel the love,  https://www.patreon.com/iceman1001

modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Online

Board footer

Powered by FluxBB