[rond79]

My buddy has a clone ICOM A2 that itools cannot see. Only way to see it, is if I input the icom ip address manually into itools and ista-p. I told his him he needed to restore back to factory spec. He tried and said it was not possible. So he brought it to me and I tried. I follow the instructions on how to do it. First three lights (Comm,WLAN and LAN) go green but when it gets to the system light, it never goes green. It just stays red. Here is the Restore Log.

"Builddate 2014-04-17 16:25
mount: mounting /dev/mtdblock/config on /config failed
mount: mounting /dev/mtdblock/config on /config failed
=> Updating boot image 1
=> Updating app image 1
mount: mounting /dev/mtdblock/app1 on /app failed
tar: can't open 'BUILDDATE': Read-only file system
umount: cannot umount /app: Invalid argument
=> Resetting u-boot parameters
Current Mac:"

USB is FAT32. Could it be I have a bad ICOM_RESTORE.bin file?

Cheers.

[willisodhiambo]

Bad ICOM. I tried to restore a clone and it hanged. Now not giving IP and shows @UNsupport.
Decided to get a genuine one after three useless Chinese clones. They used to make them very well. Of late they are all junk.

[danyro]

I had an issue too with my icom “a3” clone - not having ethernet link/network and resulted that the os rom was faulty. Replaced wirh a new samsung one from aliexpress and reflashed with icom restore.bin successfully

[rond79]

I had an issue too with my icom “a3” clone - not having ethernet link/network and resulted that the os rom was faulty. Replaced wirh a new samsung one from aliexpress and reflashed with icom restore.bin successfully

Samsung? Could you please elaborate on that. Thanks.

[yanko]

what s samsung faulty please explain more ... I have same problem ...

[danyro]

i've got fro AE this type of chip - K9F2G08U0B
this was the seller - https://www.aliexpress.com/item/32829491...4c4dEcx1Cp

i've this type of icom a3 - https://www.aliexpress.com/item/32352591...st=ae803_4

[Rooster330i]

How do you upload the restore file to ICOM? ICOM_RESTORE.bin must be in the root directory itself, the usb drive will be connected to ICOM, and then you plug the ICOM plug into the OBD and wait.

I also have a firewall problem. Try turning it off.

I also found it useful to disable DHCP and enter a permanent IP address.

My buddy has a clone ICOM A2 that itools cannot see. Only way to see it, is if I input the icom ip address manually into itools and ista-p. I told his him he needed to restore back to factory spec. He tried and said it was not possible. So he brought it to me and I tried. I follow the instructions on how to do it. First three lights (Comm,WLAN and LAN) go green but when it gets to the system light, it never goes green. It just stays red. Here is the Restore Log.

"Builddate 2014-04-17 16:25
mount: mounting /dev/mtdblock/config on /config failed
mount: mounting /dev/mtdblock/config on /config failed
=> Updating boot image 1
=> Updating app image 1
mount: mounting /dev/mtdblock/app1 on /app failed
tar: can't open 'BUILDDATE': Read-only file system
umount: cannot umount /app: Invalid argument
=> Resetting u-boot parameters
Current Mac:"  

USB is FAT32. Could it be I have a bad ICOM_RESTORE.bin file?

Cheers.

[rond79]

How do you upload the restore file to ICOM? ICOM_RESTORE.bin must be in the root directory itself, the usb drive will be connected to ICOM, and then you plug the ICOM plug into the OBD and wait.

I also have a firewall problem. Try turning it off.

I also found it useful to disable DHCP and enter a permanent IP address.

My buddy has a clone ICOM A2 that itools cannot see. Only way to see it, is if I input the icom ip address manually into itools and ista-p. I told his him he needed to restore back to factory spec. He tried and said it was not possible. So he brought it to me and I tried. I follow the instructions on how to do it. First three lights (Comm,WLAN and LAN) go green but when it gets to the system light, it never goes green. It just stays red. Here is the Restore Log.

"Builddate 2014-04-17 16:25
mount: mounting /dev/mtdblock/config on /config failed
mount: mounting /dev/mtdblock/config on /config failed
=> Updating boot image 1
=> Updating app image 1
mount: mounting /dev/mtdblock/app1 on /app failed
tar: can't open 'BUILDDATE': Read-only file system
umount: cannot umount /app: Invalid argument
=> Resetting u-boot parameters
Current Mac:"  

USB is FAT32. Could it be I have a bad ICOM_RESTORE.bin file?

Cheers.

 "ICOM_RESTORE.bin must be in the root directory itself." May you please elaborate on this? Cheers Mate.