RT6 CD noise issue, I cloned the card and it didn't work

[mkaszycki]

Hi.

I have the dreaded RT6 no boot issue with CD noise every 13 seconds. I felt it was developing problems with the internal SD card for a few years now, and it finally failed to boot today.

I unplugged the + terminal of the battery, then removed the radio from the car and removed the micro SD card from the RT6.

I used a card reader in exclusive USB device mode in a Linux VM, and made an exact copy of the entire card with the dd (disk dupe) utility. It actually succeeded in copying data off the card with no errors.

The cloned card mounts successfuly and shows all the directories correctly. I tried browsing through the folders and I can see that the files are not corrupt. I had memory failures and flash card failures due to old age and wear-out and the corruption was always evident.

So I thought I'd give it a shot and put the cloned card in the head unit and install it in the car, figuring it's just the old card that's faulty.

You can see where this is going, it failed to work.

My question is this: Was there ever a chance of this working, or is that hopeless unless Mirascripts are used?

Out of curiosity, I'm now retesting the card read and so far, every dump has the same checksum, but the older ones had different. I figure it's because mount time was recorded, but maybe there's a different thing at work here and maybe there is silent corruption in some critical binary file.

[mickthemaverick]

I think a read through this thread may help you: viewtopic.php?p=610017#p610017

[mkaszycki]

I did read that main thread, it's just that I thought that if my radio's card is not corrupt per se, I can copy its contents to another card and get the radio to boot up.

Later, I made several copies of the card and compared them, they're all identical, so at least the card itself can be read without faults. It doesn't mean that there isn't any corrupt data, but as I said, it appears that even the most recently modified files aren't corrupted.

But if Mirascripts are an obligatory part of this, then I'll run them as soon as I have some time.

[mkaszycki]

The upgrade was successful.

I finally had time today to do the upgrade. I first used a CD. It loaded okay and rebooted after upgrading the front panel.

It then failed CRC check. And again. And I figured I need to look into it. I kept the engine running anyway, and the RT6 ejected and reloaded the CD time and again.

I went back upstairs and loaded the firmware to a USB stick that I had handy. I removed the System Volume Information folder and took the USB stick to the car.

In the meantime, the CRC check succeeded from the CD and it was happily loading the firmware. It failed on one of the last steps.

I figured, it won't hurt to remove the CD and try the USB stick, right?

RIGHT!

RT6 accepted the firmware from the USB stick and loaded the firmware very quickly with no CRC problems reported.

Since I already had the correct data on the microSD card, all the functions initialized properly (at least the rear view cam and the maps all loaded correctly).

I'm going to have to drive around now for the GPS unit to recalibrate itself, but it appears it worked with no real issues.

[mickthemaverick]

A result for perseverence, well done!

[Rhothgar]

The upgrade was successful.

I finally had time today to do the upgrade. I first used a CD. It loaded okay and rebooted after upgrading the front panel.

It then failed CRC check. And again. And I figured I need to look into it. I kept the engine running anyway, and the RT6 ejected and reloaded the CD time and again.

I went back upstairs and loaded the firmware to a USB stick that I had handy. I removed the System Volume Information folder and took the USB stick to the car.

In the meantime, the CRC check succeeded from the CD and it was happily loading the firmware. It failed on one of the last steps.

I figured, it won't hurt to remove the CD and try the USB stick, right?

RIGHT!

RT6 accepted the firmware from the USB stick and loaded the firmware very quickly with no CRC problems reported.

Since I already had the correct data on the microSD card, all the functions initialized properly (at least the rear view cam and the maps all loaded correctly).

I'm going to have to drive around now for the GPS unit to recalibrate itself, but it appears it worked with no real issues.

Well done!

I have just about to attempt this again on my partner's unit.

The process appears a little different to Marc's original post as when the USB stick is recognised:-

"When prompted, it will ask to execute the script, choose 'Yes'."

It did this.

"The script will ask to launch the 'Write' command, answer 'No' to this."

It didn't really appear to ask "Do you want to write?" so I am not sure it did this. I answered YES anyway because it wouldn't really do any harm.

"The script will then ask if you want to launch the 'Read' command, select 'Yes'."

It didn't appear to do this as the screen returned to its normal state so I am guessing I clicked YES to the write command.

So now I am moving onto the next phase in the next few minutes so if anyone is online?

Maybe I should wipe the USB and run the process again and video the RT6 screen? What does anyone think? @Mick.

I did a test run earlier and plugged the USB into a PC again to see if there were additional files and there were so I repeated Part A again and have obviously NOT plugged it back into PC again to check if files are there.

[Rhothgar]

Config files appear to be there