R-link 2 Boot-loop after upgrading from V8.0.32.506 to V9

[izmirlibo]

Hello,
I am the owner of a 2016 Renault Talisman 1.6 DCI 160 HP. The R-Link 2 software version I am using is 8.0.32.506.
I want to upgrade to V9. It enters the update loop 6 times and gives the warning "Installation failed. The current version is still in use." It continues to work normally.

The error given in the log file is "[upgradeimage][1002]Error: Recovery partition change to 11: -159"

Despite doing a lot of research, I couldn't find a solution to this. I await your help. Thank you in advance.

https://youtube.com/shorts/SST-AKG5p4M?si=7XJb8Lmk36R1v8aG

Upgrade0.log

[AlMeu]

Your unit memory is damaged.
You have continue use the unit as it is until will fail boot once or change with another new unit. I recommend branch new unit with v9.0 native as long still can be found. I can help you with that, if you wish.

[izmirlibo]

Which memory module is damaged in the device? I upgraded from V7 to V8 just a week ago without any problems. The suggestion to buy a new device isn't a solution, unfortunately.

[Renotech1]

Try update official with can clip./ auto configuration/ reset ecu If not work try some pyren macro scripts If not not work replace radio ecu. Mosly you can get this working. Just an update boot loop error i guess Op za 14 mrt 2026, 20:17 schreef izmirlibo ***@***.***>:

…

*izmirlibo* left a comment (cedricp/ddt4all#1701) <#1701 (comment)> Which memory module is damaged in the device? I upgraded from V7 to V8 just a week ago without any problems. The suggestion to buy a new device isn't a solution, unfortunately. — Reply to this email directly, view it on GitHub <#1701 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BNOTOHQX5CIYFCANCVKWVDD4QWV3BAVCNFSM6AAAAACWRSG6LOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DANRRGE3TMMRSHE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[izmirlibo]

Thank you for your help and interest. The V7 update was performed via CAN Clip, and subsequently updated to V8 via USB. I suspect the V8 update might be a modded version. What I'm wondering is: could the company that performed the last update have somehow software-locked the write permissions to the memory, just to ensure that I have to return to them for future updates?

[AlMeu]

There is a NAND memory which like all components have a limited life time. This units starts/stops every day several times at temperatures -20C to +40C. This is affecting.
As your car is 2016 build, and beginning with 2015 in which many units fail working from a while.
Try rewrite v9.0, and if you get same error, as I said, use it as it is .... or change the unit.
Good luck

[izmirlibo]

There is a NAND memory which like all components have a limited life time. This units starts/stops every day several times at temperatures -20C to +40C. This is affecting. As your car is 2016 build, and beginning with 2015 in which many units fail working from a while. Try rewrite v9.0, and if you get same error, as I said, use it as it is .... or change the unit. Good luck

It's definitely a software-related error. The vehicle has only been updated once in 10 years. Also, it’s practically unused, with only 40,000 km on the clock. Thank you again for your response and interest.

[AlMeu]

Car from 2016 with 40.000Km on odometer ... you are child to believe that is true.
How you know sure that it's software error?

[izmirlibo]

Car from 2016 with 40.000Km on odometer ... you are child to believe that is true. How you know sure that it's software error?

This issue occurred right after upgrading from V2 to V7 using a CAN device, followed by a USB update to V8. In other words, the problem surfaced entirely after a software intervention. By the way, I’m not exactly a stranger to software myself. Logic and common sense clearly point to a software-related fault; you’d have to be blind not to see it. Also, I don't understand why a 2016 model with only 40,000 km is seen as 'funny' or hard to believe.

[izmirlibo]

Car from 2016 with 40.000Km on odometer ... you are child to believe that is true. How you know sure that it's software error?

A similar error appeared while upgrading from V2 to V7 using a CAN device. I believe my current issue is directly linked to that specific error.

[AlMeu]

That you show up is related to wrong settings done in Developer mode in your unit. This is software logic error.
the previous one is hardware error, totally different.

[izmirlibo]

That you show up is related to wrong settings done in Developer mode in your unit. This is software logic error. the previous one is hardware error, totally different.

Today, I visited the independent shop that performed the update. They claimed I needed to install a 'crack' file (around 300 MB) before upgrading, but strictly warned me against moving to V9, saying it would brick the unit. Despite their warnings, I insisted on trying the V9 update. We plugged in the USB containing the so-called crack, and the update finished successfully, although the version and boot numbers remained unchanged.

To me, this is proof that there is no hardware failure. If there were truly a hardware issue or a fault in the recovery memory, the system wouldn't have successfully installed that so-called crack software either. This is why I'm convinced this independent shop has somehow software-locked the upgrade process. It's even possible they don't know how to unlock it themselves.

If there were a physical 'bad sector' or a 'read-only' mode error in the R-Link 2 unit's eMMC memory, the installation bar for that 300 MB file would never have reached 100%, and the system would have thrown an error. The successful installation of this file proves that the file system and the memory writing process are fully operational.

Now, I ask you: If this were truly a hardware issue, how was the system able to successfully install this so-called 'crack' software? If the memory were faulty, that installation would have failed too.

[bz-gt]

You're probably right, and it was a software issue. However, there's a better chance of successfully writing 300MB to a damaged memory than 2GB- you might not "hit" the damaged cells