Help needed with xm1+

simon_beer · August 3, 2020, 8:31pm

Thank you
I dont know for shure its on that port but also tried it on al my. Ports everywhare the same error

And it migt indeed be for the rdv4 whare could i find the latest firm ware for the easy?

I compiled it my self that went good this time with no errors

cexshun · August 3, 2020, 8:33pm

Did you clone the repo and compile it yourself? Or did you download a precompiled version? If you compiled it yourself, you have to specify that it’s not for the RDV4. Assuming you used the RRG port?

simon_beer · August 3, 2020, 8:37pm

I followed these steps

github.com

RfidResearchGroup/proxmark3/blob/master/doc/md/Installation_Instructions/Linux-Installation-Instructions.md

# External resources

You might want to follow one of these external resources to get an overview, but please still read carefully this page as some instructions may have evolved.

* [Kali Video Installation guide](https://youtu.be/t5eBPS6lV3E "Kali Linux Installation Tutorial")
* [Ubuntu Video Installation guide](https://youtu.be/DThmkH8CdMo "Ubuntu Installation Tutorial")
* [ParrotOS Video Installation guide](https://youtu.be/Wl9AsrU4igo "ParrotOS Installation Tutorial")

![Linux Installation Video Screenshot](https://github.com/5w0rdfish/Proxmark3-RDV4-ParrotOS/blob/master/screenshot-www.youtube.com-2019.03.17-20-44-33.png)

* ParrotOS: some further notes can be found at @5w0rdfish repo [Proxmark Installation for Parrot OS](https://github.com/5w0rdfish/Proxmark3-RDV4-ParrotOS)


# Install the required dependencies

## On Debian / Ubuntu / Kali / ParrotOS / Raspbian

First what we want to do is get an update for the system. If you need to upgrade do this **before** the install. An upgrade was carried out prior to following these instructions. 

Update the packages list

This file has been truncated. show original

I just started using linux for a couple of months now and to be honest I dont know about RRG port

cexshun · August 3, 2020, 8:42pm

All good. We’re here to help. RRG is RFID Research Group, which is what you used.

You need to do a

make clean

This will clean out the bad compile you did.

Then edit the Makefile.platform.

Change

PLATFORM=PM3RDV4

to

PLATFORM=PM3OTHER

Then recompile it. Alternatively, I believe you can also

make PLATFORM=PM3OTHER

when compiling if you don’t want to edit the Makefile.platform file.

Now reflash BOTH the bootrom and fullimage.

simon_beer · August 4, 2020, 7:49am

I did this as far as i could this morning and when i wanted to flash the proxmark it told me to first do the bootloader and then do the fulimage

But i couldn’t find the commands for that so quickly this morning

cexshun · August 4, 2020, 2:32pm

github.com

RfidResearchGroup/proxmark3/blob/master/doc/md/Use_of_Proxmark/0_Compilation-Instructions.md

# Compilation instructions

## Tuning compilation parameters

The client and the Proxmark3 firmware should always be in sync.
Nevertheless, the firmware can be tuned depending on the Proxmark3 platform and options.

Indeed, the RRG/Iceman fork can be used on other Proxmark3 hardware platforms as well.

Via some definitions, you can adjust the firmware for a given platform, but also to add features like the support of the Blue Shark add-on or to select which standalone mode to embed.

To learn how to adjust the firmware, please read [Advanced compilation parameters](/doc/md/Use_of_Proxmark/4_Advanced-compilation-parameters.md).

## Get the latest commits

```sh
cd proxmark3
git pull
```

This file has been truncated. show original

simon_beer · August 4, 2020, 2:58pm

when i try to update the bootloader on it self it gives me this

simon@simon:~/Documents/proxmark/proxmark3-master$ pm3-flash-bootrom
[=] Session log /home/simon/.proxmark3/logs/log_20200804.txt
[+] About to use the following file:
[+] /usr/local/bin/…/share/proxmark3/firmware/bootrom.elf
[+] Waiting for Proxmark3 to appear on /dev/ttyACM0
59 found
[+] Entering bootloader…
[+] (Press and release the button only to abort)
[+] Waiting for Proxmark3 to appear on /dev/ttyACM0
49 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 (0x00000d50->0x00000d50) [R X] @0x298

[+] Flashing…
[+] Writing segments for file: /usr/local/bin/…/share/proxmark3/firmware/bootrom.elf
[+] 0x00100000…0x001001ff [0x200 / 1 blocks]
. OK
[+] 0x00100200…0x00100f4f [0xd50 / 7 blocks]
… OK

[+] All done

Have a nice day!
simon@simon:~/Documents/proxmark/proxmark3-master$

if i read that i think it dident work

cexshun · August 4, 2020, 3:01pm

Worked perfectly fine. Now reboot the proxmark and flash the fullimage(main firmware).

simon_beer · August 4, 2020, 3:08pm

so now its not reacting any more when i do this
ik keeps hanging here

simon@simon:~/Documents/proxmark/proxmark3-master$ pm3-flash-fullimage
[=] Waiting for Proxmark3 to appear…

and it keeps waitng so i maybe fucked somthing up i hope its stil safe able

cexshun · August 4, 2020, 3:15pm

I never rely on anything automated to update hardware that can be bricked. Use the manual command to flash the firmware. Per the link I posted

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

Assuming the device is ACM0. If modemmanger is running, it could increment that number when the device restarted.

simon_beer · August 4, 2020, 3:27pm

thats also isnte working

the red and green light are also burning

as far is i can see it is on the wright port its is on ttyACM0

if helps i can screes share somwhare or somehow ?

simon_beer · August 4, 2020, 3:34pm

and sometimes al the lights flash once in a minut or 2

cexshun · August 4, 2020, 3:40pm

Unplug it, hold the button on the proxmark down, plug it back in while holding the button down. KEEP HOLDING DOWN THE BUTTON.

Run the flash command again. When it’s done, then and only then, release the button.

simon_beer · August 4, 2020, 3:48pm

thank you so verry much for replying so quikly

it did responde again it gave me this

simon@simon:~/Documents/proxmark/proxmark3-master$ proxmark3 /dev/ttyACM0 --flash --unlock-bootloader --image bootrom.elf --image fullimage.elf
[=] Session log /home/simon/.proxmark3/logs/log_20200804.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
59 found
[=] Available memory on this board: 256K bytes

[=] 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 (0x00000d50->0x00000d50) [R X] @0x298

[+] Loading ELF file /usr/local/bin/…/share/proxmark3/firmware/fullimage.elf
[+] Loading usable ELF segments:
[+] 0: V 0x00102000 P 0x00102000 (0x0003d788->0x0003d788) [R X] @0x94
[+] 1: V 0x00200000 P 0x0013f788 (0x00001964->0x00001964) [RW ] @0x3d81c
[!!] Error: PHDR is not contained in Flash
[+] All done

Have a nice day!
simon@simon:~/Documents/proxmark/proxmark3-master$ pm3

cexshun · August 4, 2020, 3:51pm

Oof. That’s a problem.

256kb Arm chip devices: The compiled firmware image from this repo may/will be too large for your device.

Let me see what I can find. Getting closer.

Compgeek · August 4, 2020, 3:55pm

Older PM3 Easy models had 256K instead of the more common these days 512K. I believe the only option for them is to run the official fork of Proxmark instead of the Iceman release. You won’t get some of the nice features, but should have enough to do what you need to do.

cexshun · August 4, 2020, 3:56pm

Yeah, was hoping whomever hooked him up with the proxmark easy sent him the modern 512. That’s rough.

simon_beer · August 4, 2020, 3:56pm

i want to use it to clone my card from my building to my xm1+ it has al the keys changed

so if i can do that with my proxmark when it works i wil be veryy happy

Compgeek · August 4, 2020, 4:04pm

Should definitely be able to do that.

Just incase you weren’t aware (i dont mean to be condecending, just want to be clear!) there are two ‘forks’ of the proxmark firmware and software.

We usually recommend you use the RFID Research Group version (also known as Iceman)

In this case, you can’t use that version, but you can use the official version.

Read through this wiki and follow the instructions for your platform and you should be good to go.

Guessing the one you got from @Vicarious was his older one from before he moved to an RDV 4, so that would explain it being a little bit of an earlier version.

simon_beer · August 4, 2020, 4:16pm

thank you i wil go and look at that

i dident know that but i am glad to know now
i rather have somthing clear then cloudy and stil not knowing

i wil post if that worked

it was indeed the one from @Vicarious