|
|
Post by algabe on Nov 25, 2023 17:30:50 GMT
Greetings, sorry for my English, I have a 2016 Seat leon xperience 2.0 TDI in Spain, with full link audio system, hard disk and navigator, my current infotainments version is this: SW Train installed: MHI2_ER_SEG11_SG2130 and SW MU version installed: 0355. I downloaded the update from mibsolution.one/, version MHI2_ER_SEG11_P4709_MU1447. Una vez descargado lo puse en una tarjeta SD, lo introduje en la ranura para instalación y le di a actualizar, al principio parecía que todo iba correctamente actualizando sin ningún problema, pero al reiniciar el sistema la pantalla se quedó permanente en el SEAT. logo de xperience y de ahí ya no pasa, he dejado la pantalla así durante horas para ver si termina la actualización sin resultado, con el auto apagado, quitado la llave y cerrado, se queda la pantalla encendida con el logo, lo he quitado y reemplacé el fusible del radio por un tiempo para ver si la instalación podía continuar sin resultado tampoco, ya no sé que hacer más, ¿alguien sabría si hay alguna solución a este problema?, tengo el OBDeleven Ultimate, es posible solucionar el problema con el OBDeleven, si es posible que pasos debo seguir, gracias por la ayuda. |
|
|
|
Post by dv52 (Australia) on Nov 25, 2023 21:36:49 GMT
hmm.......... making software updates to the dataset in the MIB usually is final (I'm fairly certain the MIBsolution doesn't make a copy of the original operating system). I assume that you have tried re-setting the MIB by holding-down the ON/OFF switch
As for using OBD11 for this problem - I'm not sure that OBD11 will help much. OBD11 should be able to confirm the type of error that has resulted from the update exercise via the SCAN report.
My only other suggestion is try finding a copy of MHI2_ER_SEG11_SG2130 (SW 0355) and revert the dataset back to original using the same process
Don
|
|
|
|
Post by algabe on Nov 29, 2023 15:26:12 GMT
Greetings, if you read my message carefully, you will see that I say that the screen does not pass the Seat logo, ie, that the interface with its functions are not functional, so even if you find a copy of the previous version does not make possible its reinstallation, my query was if the OBDeleven would be possible to restore the factory module 5f to the previous values or also if there was a coding failure, if it is possible to recode module 5f, thanks.
|
|
|
|
Post by dv52 (Australia) on Nov 29, 2023 22:36:07 GMT
Greetings, if you read my message carefully, you will see that I say that the screen does not pass the Seat logo, ie, that the interface with its functions are not functional............................. hmm.......... this is how your original Spanish words were translated: Once downloaded, I put it on an SD card, inserted it into the installation slot and clicked on update. At first it seemed that everything was updating correctly without any problem, but when the system restarted the screen remained permanently on the SEAT. xperience logo and from there it doesn't happen, I have left the screen like this for hours to see if the update finishes without result, with the car turned off, removed the key and closed, the screen remains on with the logo, I have removed it and I replaced the radio fuse for a while to see if the installation could continue without result either, I don't know what to do anymore, would anyone know if there is a solution to this problem? I have the OBDeleven Ultimate, it is possible to solve the problem with it OBDeleven, if possible, what steps should I follow, thanks for the help. The fact that the unsuccessful update resulted in identifying this car as a SEAT really doesn't provide any information in a diagnostic sense. So having the SEAT logo isn't helpful in solving your problem - I think! ............................... my query was if the OBDeleven would be possible to restore the factory module 5f to the previous values or also if there was a coding failure, if it is possible to recode module 5f, thanks.
As said - OBD11 won't help in fixing the underlying cause of this error - which appears from your words to be an unsuccessful update of the module firmware. If you can solve the fundamental firmware problem (perhaps by reloading the original software back into the MIB) by using another method - OBD11 then can be used to change long-code and adaptation channel settings. However, these OBD11 coding changes can ONLY be done manually - meaning that you need to know what the original coding values were. OBD11 does not have any information about the original (factory) values in the MIB unless you previously made a Back-up of the MIB. But even if you did make a MIB Back-up before your unsuccessful firmware update attempt - restoring the original values is still a manual process
|
|
|
|
Post by algabe on Dec 1, 2023 6:23:50 GMT
Greetings, I have scanned with OBDeleven the car and the fault in the 5f module is as follows: OBDeleven data log Date: 2023-12-01 06:51 VIN: VSSZZZ5FZGR138637 Car: Seat Leon X-Perience Year: 2016 Body type: Sports Tourer Engine: CUNA Mileage: 85135 KM --------------------------------------------------------------- 5F Information Electronics 1 System description: MU-H-ND-EU Software number: 5F0035020K Software version: 1447 Hardware number: 5F003502020 Hardware version: H50 Serial number: A678C0GB002183 ODX Name: EV_MUHig6C3Gen2HBAS ODX version: 001001 Codificación larga: 04730301FF0A000011111101008C0A002F0205C4012001005E Error codes: U101400 - Incorrectly coded control unit. Sporadic Date: 2023-11-30 06:57:39 am Mileage: 85088 km Priority: 4 Malfunction frequency counter: 1 Mismatch counter: 247 Dynamic environmental data: 028677101755551555555555A9 B106813 - Right rear tweeter Interruption Sporadic Date: 2023-11-30 07:05:55 am Mileage: 85088 km Priority: 6 Malfunction frequency counter: 2 Mismatch counter: 249 Dynamic environmental data: 028677 U11B800 - Interface for external media without communication Sporadic Date: 2023-11-30 06:55:29 am Mileage: 85088 km Priority: 4 Malfunction frequency counter: 2 Mismatch counter: 247 Dynamic environmental data: 02867818E8FF
|
|
|
|
Post by dv52 (Australia) on Dec 1, 2023 19:28:01 GMT
hmm.........I'm not sure that the SCAN extract helps much!! Clearly the MIB is not happy with its coding - which given your explanation is caused by the unsuccessful attempt to update the module firmware.
The U11B800 error perhaps provides further insight into this problem. I'm guessing of course - but the failure of the "Interface for external media" likely means that the updated MIB firmware can't talk to the screen module - past the initial boot-up process which displays the car logo (which I suspect is a low resolution picture).
I guess you could try comparing the long-code string in your SCAN extract with the value from a past SCAN - but I suspect that there has been no changes made by the attempt to update the MIB firmware.
Don
|
|
