Diagnostic VDI, VNCI, MDI with MG4

The weather doesn't work for me with R59 either, I downgraded to R46 again, it could be because we can't update the MCU of FICM. The step 7 says: Update the MCU of FICM to the latest version by SIPS. The FICM MCU was also updated during my last inspection, maybe it works now with R59.
 
The weather doesn't work for me with R59 either, I downgraded to R46 again, it could be because we can't update the MCU of FICM. The step 7 says: Update the MCU of FICM to the latest version by SIPS. The FICM MCU was also updated during my last inspection, maybe it works now with R59.
Yes it could be. It's what i was asking here:
 
I wasn't sure this would work, but i've heard it has on other cars before.
Turns out it at least gets a connection to my router going!

This is a TP-Link USB to Ethernet adapter and a long cable from my router to the car.

It's at least enough that I can ping the car!

IMG_7508.jpeg
 
I wasn't sure this would work, but i've heard it has on other cars before.
Turns out it at least gets a connection to my router going!

This is a TP-Link USB to Ethernet adapter and a long cable from my router to the car.

It's at least enough that I can ping the car!

View attachment 31513
Another dream machine prosumer mg owner. I guess they have a market audience ?

Be interesting what can connect to remotely. Wonder if there is an SSH into the cars OS somewhere
 
Any opened ports?
Code:
PORT      STATE    SERVICE         VERSION
53/tcp    filtered domain
2011/tcp  filtered raid-cc
5555/tcp  filtered freeciv
6300/tcp  open     bmc-grx?
7000/tcp  filtered afs3-fileserver
7777/tcp  filtered cbt
63012/tcp filtered unknown
63014/tcp filtered unknown

But it looks like they thought of this. The ARP_update.sh file has a bunch of iptables rules to filter things:
Code:
#!/system/bin/sh

echo " " >> /data/iptables.txt
echo ".... iptables rule setting start ......" >> /data/iptables.txt

#disable audio prot
iptables -t filter -I INPUT -p tcp --dport 63012 -j DROP
iptables -t filter -I INPUT -p tcp --dport 63014 -j DROP

#disable adb prot
iptables -t filter -I INPUT -p udp --dport 5555 -j DROP
iptables -t filter -I INPUT -p tcp --dport 5555 -j DROP
ip6tables -t filter -I INPUT -p udp --dport 5555 -j DROP
ip6tables -t filter -I INPUT -p tcp --dport 5555 -j DROP

#disable upgrade prot
iptables -t filter -I INPUT -p tcp --dport 7777 -j DROP

#disable natp prot
iptables -t filter -I INPUT -p tcp --dport 2011 -j DROP

#disable carplay prot
iptables -t filter -I INPUT -p tcp --dport 7000 -j DROP
iptables -t filter -I INPUT -p upd --dport 5353 -j DROP
ip6tables -t filter -I INPUT -p tcp --dport 7000 -i !usb0 -j DROP
ip6tables -t filter -I INPUT -p upd --dport 5353 -i !usb0 -j DROP

#disable dns masq prot
iptables -t filter -I INPUT -p tcp --dport 53 -j DROP
iptables -t filter -I INPUT -p udp --dport 53 -j DROP
ip6tables -t filter -I INPUT -p tcp --dport 53 -j DROP
ip6tables -t filter -I INPUT -p udp --dport 53 -j DROP

#disable IPv6 data packet for ethenet
ip6tables -t filter -I INPUT -i eth0* -j DROP
ip6tables -t filter -I FORWARD -i eth0* -j DROP
ip6tables -t filter -I OUTPUT -o eth0* -j DROP

iptables -t filter -I INPUT -i lo -j ACCEPT

echo ".... iptables rule setting start ......" >> /data/iptables.txt
 
Last edited:
Code:
PORT      STATE    SERVICE         VERSION
53/tcp    filtered domain
2011/tcp  filtered raid-cc
5555/tcp  filtered freeciv
6300/tcp  open     bmc-grx?
7000/tcp  filtered afs3-fileserver
7777/tcp  filtered cbt
63012/tcp filtered unknown
63014/tcp filtered unknown

But it looks like they thought of this. The ARP_update.sh file has a bunch of iptables rules to filter things:
Code:
#!/system/bin/sh

echo " " >> /data/iptables.txt
echo ".... iptables rule setting start ......" >> /data/iptables.txt

#disable audio prot
iptables -t filter -I INPUT -p tcp --dport 63012 -j DROP
iptables -t filter -I INPUT -p tcp --dport 63014 -j DROP

#disable adb prot
iptables -t filter -I INPUT -p udp --dport 5555 -j DROP
iptables -t filter -I INPUT -p tcp --dport 5555 -j DROP
ip6tables -t filter -I INPUT -p udp --dport 5555 -j DROP
ip6tables -t filter -I INPUT -p tcp --dport 5555 -j DROP

#disable upgrade prot
iptables -t filter -I INPUT -p tcp --dport 7777 -j DROP

#disable natp prot
iptables -t filter -I INPUT -p tcp --dport 2011 -j DROP

#disable carplay prot
iptables -t filter -I INPUT -p tcp --dport 7000 -j DROP
iptables -t filter -I INPUT -p upd --dport 5353 -j DROP
ip6tables -t filter -I INPUT -p tcp --dport 7000 -i !usb0 -j DROP
ip6tables -t filter -I INPUT -p upd --dport 5353 -i !usb0 -j DROP

#disable dns masq prot
iptables -t filter -I INPUT -p tcp --dport 53 -j DROP
iptables -t filter -I INPUT -p udp --dport 53 -j DROP
ip6tables -t filter -I INPUT -p tcp --dport 53 -j DROP
ip6tables -t filter -I INPUT -p udp --dport 53 -j DROP

#disable IPv6 data packet for ethenet
ip6tables -t filter -I INPUT -i eth0* -j DROP
ip6tables -t filter -I FORWARD -i eth0* -j DROP
ip6tables -t filter -I OUTPUT -o eth0* -j DROP

iptables -t filter -I INPUT -i lo -j ACCEPT

echo ".... iptables rule setting start ......" >> /data/iptables.txt
Yep, unfortunately they wrote almost everything well :)

ip6tables -t filter -I INPUT -p tcp --dport 7000 -i !usb0 -j DROP
ip6tables -t filter -I INPUT -p upd --dport 5353 -i !usb0 -j DROP

When they enable CarPlay via USB, they wrote "upd" instead of udp.
It still seems like a dead end.


Checking on R46 files the also misspelled the "upd" on the DNS server port 53. So that should be opened.

#disable dns masq prot
iptables -t filter -I INPUT -p tcp --dport 53 -j DROP
iptables -t filter -I INPUT -p upd --dport 53 -j DROP
ip6tables -t filter -I INPUT -p tcp --dport 53 -j DROP
ip6tables -t filter -I INPUT -p upd --dport 53 -j DROP
 
Last edited:
Still waiting on my MG4 to turn up, and am finding this thread very interesting.
quick question, the adaptor you've used, is that in the USB A only, or can you get the same behaviour in the USB C (the carplay/auto port) as well?


is there a hacker community around this? or is this thread it?
 
Still waiting on my MG4 to turn up, and am finding this thread very interesting.
quick question, the adaptor you've used, is that in the USB A only, or can you get the same behaviour in the USB C (the carplay/auto port) as well?


is there a hacker community around this? or is this thread it?
I've posted on xdaforums, but haven't really picked up any traction yet.

Carplay / Android Auto only work on the A port. There's no real end user purpose to the C port.
As we know it can have debugging turned on, but I have no idea why that's still not working.

I've seen someone on the ZS forum got into their ADB via their C port.
I don't get why it doesn't work here once turned on. I feel like i'm going around in circles at this point.

And before anyone mentions it, the rear USB A port only has power to it, no data. So that's not it.
 
Last edited:
Yep, unfortunately they wrote almost everything well :)

ip6tables -t filter -I INPUT -p tcp --dport 7000 -i !usb0 -j DROP
ip6tables -t filter -I INPUT -p upd --dport 5353 -i !usb0 -j DROP

When they enable CarPlay via USB, they wrote "upd" instead of udp.
It still seems like a dead end.


Checking on R46 files the also misspelled the "upd" on the DNS server port 53. So that should be opened.
That is pretty funny. Might be why carplay is so flakey sometimes
 
Keep the folder structure, when I did move AVN_MPU out it didn't detect.

When you do the infotainment make sure foot is on the brake so its in ready mode. AVN_MPU needs power to begin with but seems doesn't need it consistently just for the check.
I want to update my R19 (without ext temp) to R33 I got some USB R33 files for usb update (from this forum) there are 2 files : 1 zipped OTA archive and 1 file called payload.bin Can someone advise how the folder structure of these files shall be on the usb?
My MG4 car is a EH32 X1 (SE EU) with ismart lite.
 
I want to update my R19 (without ext temp) to R33 I got some USB R33 files for usb update (from this forum) there are 2 files : 1 zipped OTA archive and 1 file called payload.bin Can someone advice how the folder structure of these files shall be on the usb?
My MG4 car is a EH32 X1 (SE EU) with ismart lite.
I noticed this Windows magic thing, if you unpack the MG4 SE - R33.rar file using the extractor built into windows it creates this structure
1729720863170.png

It seems to automatically extract usb_ota_update.zip as well

Please extract the rar file with 7zip. The usb_ota_update.zip needs to stay zipped.


I've never worked on the SE, but the structure in the pendrive should be one of these:
1729721102456.png
1729721469047.png
 
@leonkernan I found your post in XDA, there is a development and it looks promising
 

Are you enjoying your MG4?

  • Yes

    Votes: 911 77.7%
  • I'm in the middle

    Votes: 171 14.6%
  • No

    Votes: 90 7.7%
Support us by becoming a Premium Member

Latest MG EVs video

MG Hybrid+ EVs OVER-REVVING & more owner feedback
Subscribe to our YouTube channel
Back
Top Bottom