How to Find Out What Firmware on Uconnect

How to Find Out What Firmware on Uconnect

Howdy!

Well from what I have seen about the new uConnect 7, is that at that place are 2 variables in the dev log that demand irresolute to activate the navigation. I believe they’re:

If this is bachelor to modify via the proxi alignment, then that should do you proficient
:D

From my side, I will investigate the firmware on the VP2R7 and come across the hardware variants and what organisation paradigm the Uconnect installer installs.

uConnect VP2R7 hardware variants:

Code:

            
              <HARDWAREMAP>002000010104+.i...........0.........i........ VP2_HIPACK</HARDWAREMAP> <!-- all HiRes samples with 1GB RAM/seMMC -->         <HARDWAREMAP>002000010104+.1.........................ane.... VP2_HIPACK</HARDWAREMAP> <!-- all HiRes samples with full eMMC     -->         <HARDWAREMAP>002000010104+.1...........1.................. VP2_STPACK</HARDWAREMAP> <!-- all HiRes samples with 512MB RAM     -->         <HARDWAREMAP>002000010104+.......................0...0.... VP2_STPACK</HARDWAREMAP> <!-- all samples westward/o eMMC                 -->         <HARDWAREMAP>002000010104+.0.............................. VP2_STPACK</HARDWAREMAP> <!-- all LowRes samples                   -->         <HARDWAREMAP>002100010104+.1...........0.........1........ VP2_HIPACK</HARDWAREMAP> <!-- all HiRes samples with 1GB RAM/seMMC -->         <HARDWAREMAP>002100010104+.one.........................1.... VP2_HIPACK</HARDWAREMAP> <!-- all HiRes samples with total eMMC     -->         <HARDWAREMAP>002100010104+.i...........i.................. VP2_STPACK</HARDWAREMAP> <!-- all HiRes samples with 512MB RAM     -->         <HARDWAREMAP>002100010104+.......................0...0.... VP2_STPACK</HARDWAREMAP> <!-- all samples west/o eMMC                 -->         <HARDWAREMAP>002100010104+.0.............................. VP2_STPACK</HARDWAREMAP> <!-- all LowRes samples                   -->         <HARDWAREMAP>002000010105+.1...........0.........1........ VP2_HIPACK</HARDWAREMAP> <!-- all HiRes samples with 1GB RAM/seMMC -->         <HARDWAREMAP>002000010105+.1.........................i.... VP2_HIPACK</HARDWAREMAP> <!-- all HiRes samples with full eMMC     -->         <HARDWAREMAP>002000010105+.1...........i.................. VP2_STPACK</HARDWAREMAP> <!-- all HiRes samples with 512MB RAM     -->         <HARDWAREMAP>002000010105+.......................0...0.... VP2_STPACK</HARDWAREMAP> <!-- all samples w/o eMMC                 -->         <HARDWAREMAP>002000010105+.0.............................. VP2_STPACK</HARDWAREMAP> <!-- all LowRes samples                   -->            <PROJECTMAP>0008..01 VP2_ECE</PROJECTMAP>   <!-- all CHR ECE samples   -->           <PROJECTMAP>0008..02 DUMMY_PRJ</PROJECTMAP> <!-- all CHR NAFTA samples -->           <PROJECTMAP>0008..05 DUMMY_PRJ</PROJECTMAP> <!-- all CHR ROW samples   -->           <PROJECTMAP>0008..ff VP2_ECE</PROJECTMAP>   <!-- all CHR ROW samples   -->           <PROJECTMAP>000a..01 VP2_ECE</PROJECTMAP>   <!-- all FGA ECE samples   -->           <PROJECTMAP>000a..ff VP2_ECE</PROJECTMAP>   <!-- all FGA ROW samples   -->           <PROJECTMAP>000a..02 DUMMY_PRJ</PROJECTMAP> <!-- all FGA NAFTA samples -->           <PROJECTMAP>000a..05 DUMMY_PRJ</PROJECTMAP> <!-- all FGA APAC samples  -->        <!-- BEGIN ### QT modules - 4010159 (04 = SWL_NORMAL_INSTALL, 01 = MMP REF, 01 = AUTOHOST, 59 = Id) ######################## -->       <FRAGMENT_ID FragmentID="4010159">         <HARDWAREMAP>002000010104+.1.............................. VP2_QT</HARDWAREMAP>       <!-- all HiRes samples                   -->         <HARDWAREMAP>002000010104+.0........................11.... VP2_QT</HARDWAREMAP>       <!-- all NAV samples                     -->         <HARDWAREMAP>002000010104+.0........................00.... VP2_QT_DUMMY</HARDWAREMAP> <!-- all LowRes samples w/o GPS and EMMC -->         <HARDWAREMAP>002000010104+.0........................01.... VP2_QT_DUMMY</HARDWAREMAP> <!-- all LowRes samples with EMMC        -->         <HARDWAREMAP>002000010104+.0........................10.... VP2_QT_DUMMY</HARDWAREMAP> <!-- all LowRes samples with GPS         -->         <HARDWAREMAP>002100010104+.ane.............................. VP2_QT</HARDWAREMAP>       <!-- all HiRes samples                   -->         <HARDWAREMAP>002100010104+.0........................11.... VP2_QT</HARDWAREMAP>       <!-- all NAV samples                     -->         <HARDWAREMAP>002100010104+.0........................00.... VP2_QT_DUMMY</HARDWAREMAP> <!-- all LowRes samples w/o GPS and EMMC -->         <HARDWAREMAP>002100010104+.0........................01.... VP2_QT_DUMMY</HARDWAREMAP> <!-- all LowRes samples with EMMC        -->         <HARDWAREMAP>002100010104+.0........................10.... VP2_QT_DUMMY</HARDWAREMAP> <!-- all LowRes samples with GPS         -->         <HARDWAREMAP>002000010105+.one.............................. VP2_QT</HARDWAREMAP>       <!-- all HiRes samples                   -->         <HARDWAREMAP>002000010105+.0........................11.... VP2_QT</HARDWAREMAP>       <!-- all NAV samples                     -->         <HARDWAREMAP>002000010105+.0........................00.... VP2_QT_DUMMY</HARDWAREMAP> <!-- all LowRes samples w/o GPS and EMMC -->         <HARDWAREMAP>002000010105+.0........................01.... VP2_QT_DUMMY</HARDWAREMAP> <!-- all LowRes samples with EMMC        -->         <HARDWAREMAP>002000010105+.0........................10.... VP2_QT_DUMMY</HARDWAREMAP> <!-- all LowRes samples with GPS         -->
          

uConnect VP2R7 partitions:

Read:  La Gard Basic Series 3802 Firmware Dual-handed Swing Bolt Lock or Dead Bolt

Code:

            
              <FRAGMENT_ID>4010187</FRAGMENT_ID> <!-- PreSwlExecution -->       <FRAGMENT_ID>4010154</FRAGMENT_ID> <!-- EBoot -->       <FRAGMENT_ID>4010151</FRAGMENT_ID> <!-- Bootloader / UDLR -->       <COMMAND>BOOTMODE_SWL</COMMAND>    <!-- Switch to SWL context -->       <FRAGMENT_ID>4010160</FRAGMENT_ID> <!-- Picture Firmware -->       <FRAGMENT_ID>4011201</FRAGMENT_ID> <!-- Front Firmware -->       <FRAGMENT_ID>4010591</FRAGMENT_ID> <!-- SDARS Firmware -->       <FRAGMENT_ID>4010489</FRAGMENT_ID> <!-- DAB Firmware -->       <FRAGMENT_ID>401015d</FRAGMENT_ID> <!-- Secure Bootloader (Bootloader two) / Backup UDLR -->       <FRAGMENT_ID>4010152</FRAGMENT_ID> <!-- Application image (NK) -->       <FRAGMENT_ID>4010167</FRAGMENT_ID> <!-- DSP data -->       <FRAGMENT_ID>4010157</FRAGMENT_ID> <!-- TFAT1 (filebased)-->       <FRAGMENT_ID>4010161</FRAGMENT_ID> <!-- Diagnostic Server -->       <FRAGMENT_ID>4010181</FRAGMENT_ID> <!-- Old-style HMI app  -->       <FRAGMENT_ID>4010182</FRAGMENT_ID> <!-- Old-style HMI resource (ROW) -->       <FRAGMENT_ID>4010183</FRAGMENT_ID> <!-- Old-manner HMI resources (APAC) -->       <FRAGMENT_ID>4010184</FRAGMENT_ID> <!-- New-style HMI app -->       <FRAGMENT_ID>4010185</FRAGMENT_ID> <!-- New-fashion HMI resources -->       <FRAGMENT_ID>4010188</FRAGMENT_ID> <!-- Splash Animation -->       <FRAGMENT_ID>40101a1</FRAGMENT_ID> <!-- Preloaded apps (preinstalled third political party applications) -->       <FRAGMENT_ID>40101c0</FRAGMENT_ID> <!-- Speech, dun eng LowRes languages, module loader based -->       <FRAGMENT_ID>40101c1</FRAGMENT_ID> <!-- Speech, frf plp LowRes languages, module loader based -->       <FRAGMENT_ID>40101c2</FRAGMENT_ID> <!-- Speech, ged iti LowRes languages, module loader based -->       <FRAGMENT_ID>40101c3</FRAGMENT_ID> <!-- Speech, ptb ptp LowRes languages, module loader based -->       <FRAGMENT_ID>40101c4</FRAGMENT_ID> <!-- Speech, rur spe LowRes languages, module loader based -->       <FRAGMENT_ID>40101c5</FRAGMENT_ID> <!-- Speech, enu LowRes linguistic communication, module loader based -->       <FRAGMENT_ID>40101c6</FRAGMENT_ID> <!-- Speech communication, frc spm LowRes languages, module loader based -->       <FRAGMENT_ID>40101c7</FRAGMENT_ID> <!-- Oral communication, trt LowRes language, module loader based -->       <FRAGMENT_ID>40101c8</FRAGMENT_ID> <!-- Speech, rec all ECE languages, module loader based -->       <FRAGMENT_ID>40101c9</FRAGMENT_ID> <!-- Speech communication, rec all NAFTA languages, module loader based -->       <FRAGMENT_ID>40101aa</FRAGMENT_ID> <!-- Oral communication, rec all APAC languages, module loader based -->       <FRAGMENT_ID>40101ca</FRAGMENT_ID> <!-- Oral communication, dun1 HighRes languages, module loader based -->       <FRAGMENT_ID>40101cb</FRAGMENT_ID> <!-- Speech communication, dun2 HighRes languages, module loader based -->       <FRAGMENT_ID>40101cc</FRAGMENT_ID> <!-- Speech, eng HighRes languages, module loader based -->       <FRAGMENT_ID>40101cd</FRAGMENT_ID> <!-- Speech, frf1 HighRes languages, module loader based -->       <FRAGMENT_ID>40101ce</FRAGMENT_ID> <!-- Spoken language, frf2 HighRes languages, module loader based -->       <FRAGMENT_ID>40101cf</FRAGMENT_ID> <!-- Speech, plp HighRes languages, module loader based -->       <FRAGMENT_ID>40101b2</FRAGMENT_ID> <!-- Spoken communication, ged1 HighRes languages, module loader based -->       <FRAGMENT_ID>40101b3</FRAGMENT_ID> <!-- Speech, ged2 HighRes languages, module loader based -->       <FRAGMENT_ID>40101b4</FRAGMENT_ID> <!-- Spoken communication, ptb HighRes languages, module loader based -->       <FRAGMENT_ID>40101b5</FRAGMENT_ID> <!-- Voice communication, ptp HighRes languages, module loader based -->       <FRAGMENT_ID>40101b6</FRAGMENT_ID> <!-- Speech, rur1 HighRes languages, module loader based -->       <FRAGMENT_ID>40101b7</FRAGMENT_ID> <!-- Speech, rur2 HighRes languages, module loader based -->       <FRAGMENT_ID>40101b8</FRAGMENT_ID> <!-- Speech, spe HighRes languages, module loader based -->       <FRAGMENT_ID>40101ac</FRAGMENT_ID> <!-- Speech, iti HighRes languages, module loader based -->       <FRAGMENT_ID>40101af</FRAGMENT_ID> <!-- Speech, trt HighRes languages, module loader based -->       <FRAGMENT_ID>40101ab</FRAGMENT_ID> <!-- Speech, arw HighRes languages, module loader based -->       <FRAGMENT_ID>40101a4</FRAGMENT_ID> <!-- Speech, ena HighRes languages, module loader based -->       <FRAGMENT_ID>40101b9</FRAGMENT_ID> <!-- Speech, enu1 HighRes languages, module loader based -->       <FRAGMENT_ID>40101ba</FRAGMENT_ID> <!-- Speech, enu2 HighRes languages, module loader based -->       <FRAGMENT_ID>40101ad</FRAGMENT_ID> <!-- Speech, frc HighRes languages, module loader based -->       <FRAGMENT_ID>40101ae</FRAGMENT_ID> <!-- Oral communication, spm HighRes languages, module loader based -->       <FRAGMENT_ID>40101a9</FRAGMENT_ID> <!-- Speech, jpj HighRes languages, module loader based -->       <FRAGMENT_ID>40101a8</FRAGMENT_ID> <!-- Speech, kok HighRes languages, module loader based -->       <FRAGMENT_ID>40101a7</FRAGMENT_ID> <!-- Speech, mnc HighRes languages, module loader based -->       <FRAGMENT_ID>40101a6</FRAGMENT_ID> <!-- Voice communication, jpj kok LowRes languages, module loader based -->       <FRAGMENT_ID>40101a5</FRAGMENT_ID> <!-- Speech, mnc LowRes languages, module loader based -->       <FRAGMENT_ID>40101bb</FRAGMENT_ID> <!-- Speech, common TTS files LowRes, filebased -->       <FRAGMENT_ID>40101bc</FRAGMENT_ID> <!-- Spoken language, common TTS files HighRes, filebased -->       <FRAGMENT_ID>40101bd</FRAGMENT_ID> <!-- Speech, VDE files, filebased -->       <FRAGMENT_ID>40101be</FRAGMENT_ID> <!-- Speech, radio files, filebased -->       <FRAGMENT_ID>40101bf</FRAGMENT_ID> <!-- Voice communication, common files, filebased -->       <Control>RESTART_SYSTEM</COMMAND>  <!-- Restart system to rebuild the NAND transaction log -->       <FRAGMENT_ID>4010153</FRAGMENT_ID> <!-- Bootstrap -->       <FRAGMENT_ID>4011151</FRAGMENT_ID> <!-- GPS Firmware -->       <FRAGMENT_ID>4010158</FRAGMENT_ID> <!-- TomTom/Navigation apps (filebased)-->       <FRAGMENT_ID>4010159</FRAGMENT_ID> <!-- QT runtime -->       <FRAGMENT_ID>401015a</FRAGMENT_ID> <!-- TomTom/Navigation apps back up Code (filebased, eMMC)-->       <FRAGMENT_ID>401015c</FRAGMENT_ID> <!-- Navigation Canned Voices (filebased, eMMC)-->       <FRAGMENT_ID>4010180</FRAGMENT_ID> <!-- Digital Radio apps (DAB/SDARS) -->       <FRAGMENT_ID>4010179</FRAGMENT_ID> <!-- Development tools -->       <FRAGMENT_ID>401015b</FRAGMENT_ID> <!-- TSW -->       <FRAGMENT_ID>40101b0</FRAGMENT_ID> <!-- System configuration -->       <FRAGMENT_ID>4010189</FRAGMENT_ID> <!-- Certificates -->       <FRAGMENT_ID>4010190</FRAGMENT_ID> <!-- PostSwlExecution -->
          

Read:  Galaxy Note 3 Stock Firmware for at&t Sm-n900a Download

Then there are actually a lot of hardware variants for the newer uConnect seven:
Features:

  • Howdy-Res / Low-Res screen models (namely HIPACK and STPACK)
  • Non-nav west/o gps&fEMMC
  • Non nav w/o gps (but with the right EMMC)
  • nav models (with GPS and EMMC)

EMMC types (High Res models):

  • 1GB RAM/seMMC
  • full eMMC
  • no eMMC + 512mb ram

Low res models practise not have this specified.

Region Models:

  • CHR ECE
  • CHR NAFTA
  • CHR ROW
  • FGA ECE
  • FGA ROW
  • FGA NAFTA
  • FGA APAC

Models with carplay/car:

  • ProjectionDevice back up (VP2_PD)
  • No phone mirroring —>>> VP2_NOPD

TomTom variants:

  • VP2_NAV_DUMMY <!– all non NAV due west/o GPS/fEMMC samples–>
    Installs navapps dummy 4010158_DUMMY.FRG
  • VP2_NAV_POSONLY <!– all non NAV with GPS samples–>
    Installs navapps package 4010158_POSONLY.FRG (POS – Maybe points of interest??)
  • VP2_NAV <!– all NAV samples–>
    Installs navapps package 4010158.Germany

And other packages which you can find in xml.

So its quite possible to have eMMC space limitations also with some variants. Try the proxi alignment and and so a firmware update if this doesn’t sort information technology out, last resort is to change the file of the dummy and it’s signature file in folder with 1 of the navigation with signature replaced with the filename of the dummy. This will very likely brick it and then big take chances tho.

How to Find Out What Firmware on Uconnect

Check Also

How to Roll Back Firmware Update on Hp Laser Jet Printer M476nw

How to Roll Back Firmware Update on Hp Laser Jet Printer M476nw

How to Roll Back Firmware Update on Hp Laser Jet Printer M476nw [German language]In this …