Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14

Thread: Discover Pro (MIB2.5) Stuck on boot splash screen

  1. #11
    Join Date
    Jun 2010
    Location
    Sydney
    Posts
    4,081
    Users Country Flag

    I've been away on holiday.
    I'll send you some docs via email.
    2011 Skoda Octavia vRS TDI DSG wagon|Revo Stage 1|Race Blue|Leather|Dynamic Xenons w 6000K|9w7 BT|THA475 Amp+active sub|Whiteline ALK|RVC|
    2009 R36 wagon|Biscay Blue|RVC|Tailgate|ECU and DSG tune|LED DRL/Indicators|3D colour cluster|Quad LED tail rings|Climatronics upgrade|Dynaudio retrofit|B7 RLine Flat Steering Wheel|3AA CCM|TPMS Direct|B7 Adaptive Cruise with Front Assist|Discover Media retrofit|PLA 2.0|Lane Assist|BCM retrofit|High Beam Assist|DQ500

  2. #12
    Join Date
    Dec 2021
    Location
    Launceston, TAS
    Posts
    9
    Users Country Flag Thread Starter
    Just to provide a resolution in this thread...

    Huge thankyou to kamold and his efforts and numerous answers via email in trying to get the issue resolved.

    Eventually I got it fixed today with the help of a user who contacted me via my post on jilleb's (MIB2 Toolbox's dev) github. We were about to re set the skin using long coding through the serial terminal interface into emergency boot mood.

  3. #13
    Join Date
    Apr 2020
    Location
    Poland - Europe
    Posts
    7
    Users Country Flag
    Quote Originally Posted by leifalbor View Post
    Just to provide a resolution in this thread...

    Huge thankyou to kamold and his efforts and numerous answers via email in trying to get the issue resolved.

    Eventually I got it fixed today with the help of a user who contacted me via my post on jilleb's (MIB2 Toolbox's dev) github. We were about to re set the skin using long coding through the serial terminal interface into emergency boot mood.
    Can you provide me with information you got? I am in the same situation. I changed skin and I can see starting logo only.

  4. #14
    Join Date
    Sep 2013
    Location
    Victoria
    Posts
    1,819
    Users Country Flag

    @wachu153: Hmm....... if your problem has resulted from coding changes and you have used a diagnostic device like OBD11, or VCDS - the software will contain a record of the details of the tweak.

    So, a way of often (and easily) fixing this problem is to simply revert the coding change the caused the fault back-to the original setting!

    As I say, you already have the necessary data for this fix if you have used a good diagnostic device - why not try?

    Don
    Please don't PM to ask questions about coding, or vehicle repairs. The better place to deal with these matters is on-line, in the forum proper. That way you get the benefit of the expertise of the wider forum! Thank you.

Page 2 of 2 FirstFirst 12

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
| |