yashsingh1/xdaforums huggingface dataset:
[Connected Car] drizze99:
I just bought a 2016 Challenger RT+ which comes with the 8.4 RA4 touch screen. I also just bought the Z Automotive Tazer OBDII dongle.

I'll start by saying that I HATE Uconnect! I want to unlock the Performance Pages and I've done it twice now after restoring the radio to factory defaults and after about 30 sec, Uconnect flags the app and deletes it making me one pist off Challenger owner.

I would love to neutralize Uconnect. Every though I don't have an active Uconnect account, I feel like the radio is communicating with FCA to delete that app.
[Connected Car] drizze99:
[MENTION=2023777]Tooltime[/MENTION] you seem to be the only user in this thread that has a Dodge Challenger. Do you have the Performance Pages activated and working on your car? It looks like the Uconnect firmware that is on my Challenger is 16.09.09 according to the engineering menu. V850 App is 16.7.0 and the V850 Boot is 13.1.0...
[Connected Car] :
asdfasfsfsadgasgsdag
[Connected Car] devmihkel:
Hey, version 16.09.x sounds very much rootable (anything lower than 16.51.xx they say) and once you have wifi and ssh root access, I guess you can just as well block any unwanted connections with packet filter. Though I did not have to do that as 8.4 RA4 of mine is very much outside of Sprint coverage :o

In my case it was just enough to poke with preferences file in Performance Pages app folder to make it appear in the menu (to make the car model string match). Some sensors show nothing in my case (like G-force), but that's kind of expected considering the car model at hand. App itself appears to work fine though.
[Connected Car] drizze99:
Well I think I might have screwed myself. I was working with another MY16 Challenger owner who updated his firmware to the latest version (17.43.01) and since he was working just fine, I went and updated my system and I thought I had it since the Performance Pages lasted an entire day. My happiness was squished quickly the next day when the pages were gone again. Now I think I am on an un-rootable version of Uconnect. :(
[Connected Car] Mousie123:
Hi Folks, I need to get a DRM.jar file out of a jeep that had off road maps by default. Does anyone know which jeep type I need to look out for so I can download the ISO? Because if I use the touch disable DRM on my 14.25.5 I find that my standard settings and engineering menu disappear so that option will not work for me. Thankyou
[Connected Car] skoriy88:
Guys greeting from Ukraine! I looked through the different topics at different forums but still have a problem. I have a 2015 Dodge Durango from the USA. UCONNECT_8.4A_RA3_17.11.07_MY15_NAFTA is now installed, the official site offers an update to UCONNECT_8.4A_RA3_17.43.01_MY15_NAFTA.

But, I have a strong desire to have European localization (Radio frequencies, Russian lenguage, if possible activate navigation). I have decompiled some lua files from the archives of version 17, looked through all the scripts, but so far I can’t figure out how to install for example UCONNECT_8.4AN_RG4_17.09.07_MY15_EMEA or UCONNECT_8.4AN_RG4_17.46.01_MY15_EMEA on my car?

Maybe someone can post step-by-step instruction - it would be great! Any help is greatly appreciated !!!

Thanks a lot!
[Connected Car] marx232:
Hi

I download firmware UCONNECT_8.4AN_RA4_17.43.01_MY15_NAFTA

and problem with Embedded Air Card

Possible in update skip?

I have problem with stop in 1%, now uconnect is only restarting with info about insert usb stick.

Reset no working.

edit file manifest.lua only need?

or after editing need checksum?
[Connected Car] quid246:
Maybe slightly OT... but has anybody ever been able to activate HD Radio on the VP3 units?

This is supposedly only available on the VP4 radios, but the FCC certification documents from Harman says the VP3 and VP4 are exactly the same hardware, the only difference is in the software.
[Connected Car] SquithyX:
From my understanding, the vp3 units are 5" and made by Continental, the vp4 units are 6.5" made by Harmon.... Or at least that's how it is with Alfa's.

I know some of the 8.4 units get referred to as vp3 or vp4 and the difference between them is software / proxi only.
[Connected Car] quid246:
This should clear up any misunderstanding... at least for the 8.4's as submitted to the FCC
[Connected Car] jawz101:
Did you ever monitor the network traffic. I'm curious who all it connects to
[Connected Car] Yugiro:
hello my car has fiat 500x blend vp4 6.5 radio and it doesn't open anymore as a result of wrong update only very low level of light what should i do my friends : Ağlayan: [IMG="https://imgyukle.com/i/V3lQwY"]
[Connected Car] lden:
Hi Yugiro,

Have a look here :

https://xdaforums.com/showpost.php?p=81546447&postcount=724

I have VP3 but similar approach might work with VP4
[Connected Car] radsliwa:
I am heartbroken. For four days I have been trying to change the USA version to Europe in my Cherokee 2015. I think I drove with a USB stick about a million kilometers from home to the garage :silly: Unfortunately, the version in it is 18.11.07. I have read that it is not possible to downgrade to 16:xx:xx to use your software. Do you have any idea? I'm not a programmer, but maybe someone would modify version 18.11.07 or newest 18.45.01? What do U think about it?
[Connected Car] nihonjin:
Well after updating my original MY14 uconnect 8.4 beyond what would allow me to bypass run custom scripts I have since bought a 2nd hand MY16 8.4 uconnect radio and would like to try again to activate some of the custom hacks and new maps. It is currently running vs14 software and I would like to update to whatever is the latest software that still allows for running custom scripts. However I can't seem to find much info or a download for the MY16 radios. Does anyone have a link they can share. Also the files shared here I can't seem to get the boot.luascriot to run which turns on DAB and performance pages etc. It's been a while since I last tried and maybe I have forgotten how to do it properly but it appears the MY16 radios are slightly different so anyone with a MY16 that has done it and can offer any advice or tips would be greatly appreciated. Thanks
[Connected Car] nihonjin:
So I am trying to follow markkpatel guide on changing the units for tyre pressure as for some reason when selecting metric it gives the tyre pressure in bar yet here in Australia we use psi. I have managed to get the personalConfiguration.lua file from the uconnect unit and decompiled it and made the edits necessary but it seems that the code posted by markkpatel is not allowing me to replace the original file on the unit.

This is the code he posted:

#!/usr/bin/lua

local os = os

os.execute("chmod 777 /usr/bin/cmc/service/platform/vehicle/personalConfiguration.lua")

os.execute("cp -f /fs/usb0/decompiled.lua /usr/bin/cmc/service/platform/vehicle/personalConfiguration.lua")

os.execute("chmod 555 /usr/bin/cmc/service/platform/vehicle/personalConfiguration.lua")

So i know for a fact that despite changing the file permission to writable no matter what I do i cannot replace the original code with my modified code. Any ideas of what i could be doing wrong or how to fix it.

thanks.
[Connected Car] devmihkel:
I think bin folders are mounted read only by default, so try:

os.execute("mount -uw /fs/mmc1/")

to make filesystem writable first (or perhaps it is fs/mmc0 not sure where /usr/bin is mapped to, you can safely try both ;)
[Connected Car] nihonjin:
Thanks for the suggestion I tried to mount both mmc1 and mmc0 but neither allowed for the file to be replaced with my edited version.

Now I am running this from the script.lua should it be from the booter.lua or any other ideas? Thanks
[Connected Car] devmihkel:
Yeah, my bad, I regarded that "bin/" folder to be something writable like /fs/mmc0/app/bin, which /usr/bin/ & friends definitely are not - sorry about that.

This sounds like your unit is newer than MY15 and many of these "old tricks" don't work anymore, as partition or folders layout was changed and many previously writable files are now read only (on the IFS image). Or you have the same 16.16.13 version as op?

On the other hand the "overlay trick" linking to replace files always works, but this needs to be done somewhere early in the boot (e.g. if you are using modified media.sh), you can then try something like this instead and the file gets replaced:

ln -sP /fs/mmc0/decompiled_something /usr/bin/cmc/service/platform/vehicle/personalConfiguration.lua

I have no idea when this personalConfiguration.lua file is read or run, so original (read only) file may get executed before the overlay linking is in place. But this may be something worthwhile to try :)
[Connected Car] nihonjin:
So I need to copy my decompiled lua file to mmc0 first? Do I name it the same ie personalConfiguration.lua or any name is ok? I then paste your script and replace the decompile_something with the name of my file I have copied in the media.sh file and upload my new media.sh file and try my luck?

Thanks.
[Connected Car] devmihkel:
Yes, that should do it :good: The symbolic link is created "in-memory" only, so it needs to be re-created on every boot. And you need to store the modified file on writable persistent storage somewhere (mmc0 or mmc1). Source file name can be whatever, I would even keep it different on purpose for clarity.
[Connected Car] nihonjin:
So far nothing has worked. I have copied my decompiled.lua file to "/fs/mmc0/app/bin" and added the following commands to the bottom of my media.sh file:

ln -sP /fs/mmc0/app/bin/decompiled.lua /usr/bin/cmc/service/platform/vehicle/personalConfiguration.lua

That didnt work then I tried the following code in my media.sh file:

cp -f /fs/mmc0/app/bin/decompiled.lua /tmp

ln -sP /tmp/decompiled.lua /usr/bin/cmc/service/platform/vehicle/personalConfiguration.lua

That hasnt worked either. I am at a loss as to what else to try. Any other thoughts or suggestions?
[Connected Car] nihonjin:
So it seems trying to modify the personalconfiguration.lua is not working so Im now working on a different project.

I had another unit i softbricked with an incorrect swf file copy and i would like to get this unit back up and working. I believe i need to hexedit the manifest.lua file from a iso file. I have tried both a modified iso that has firmware lower then my unit and a unmodified iso file that is same firmware as my unit. however both times i get error load manifest file.

The only part I am not really sure about in the instructions left by markkpatel is at the end before he closes with return manifest he has above that **** LOTS OF SPACES HERE ****

I am not sure if i type that in hexedit or just leave a bunch of ...... or actually put spaces. The file size does not change when i edit so i am at a lost as to what to do. Any ideas?
[Connected Car] Diabollon:
I also have the Android Extension V4 with 7.1.2 Android built into UConnect 8.4 VP3.

Has anyone successfully get root access? When yes how?
[Connected Car] nihonjin:
never mind i worked out how to successfully edit the manifest.lua file and get it to run my script before having to update.
[Connected Car] devmihkel:
Coronita results:
[Connected Car] nihonjin:
Do share how have you loaded the uconnect software?
[Connected Car] devmihkel:
It takes a Dingleberry to load it :D Rooting a Playbook was probably a hot topic some 8 years ago... Otherwise it is to copy the files out from your HU and to figure out which of the 600 lines of boot.sh would not drive the Playbook QNX completely nuts :D
[Connected Car] devmihkel:
Here's one way how to get to the splash screen of your homebrew qnx car platform on Dingleberry-book.

First copy some full folders off your HU ( bin etc lib usr ) and ( fs/mmc0/app/bin fs/mmc1 fs/etfs ). Hint: create tarballs to maintain symlinks, but copy tar&gzip along as binaries, those are missing on PB.

(For direct usbnet connection one might need to switch PB storage&sharing USB connection to Mac setting)

Then run your own sshd instance at another TCP port on PB so that you can slay qconn and friends while connected on root shell. As root you can create new folders on PB including, yeah, under root folder. Also /fs/ appears to be persistent, so clone mmc0, mmc1 and etfs folders there, but have rest of folders ready in say /uconnect.

At this point ensure your PB screen is awake, as power manager or something needed to wake up screen gets killed along:

/base/scripts/startup.sh runlevel 0

You may kill even more of the still running PB services, but these keep her alive ( screen hid filesystem pty net usbmgr ).

RUN_LEVEL_0_SERVICES="bootinfo pps simconfig powerman lpddrmon phyctrl battery bootreason logging splashscreen rtc dumper drmclock authman random coreservices perimeter audio dtminit certmgr vpn wpa radio"
for i in $RUN_LEVEL_0_SERVICES; do /scripts/startup.sh $i stop; done

Now did you kill too many, did you? Test and take a look at your PB: /fs/mmc0/app/bin/gles1-gears :cool:

Create new symlink within HU usr folders, say /uconnect/usr/lib/graphics/ omap4430 -> /base/usr/lib/graphics/omap4430/

Now overlay HU folders to PB root folder in-memory non-persistent qnx style:

ln -sfP /uconnect/usr/ /usr
ln -sfP /uconnect/lib/ /lib
ln -sfP /uconnect/etc/ /etc
ln -sfP /uconnect/bin/ /bin

Export variables:

export LD_LIBRARY_PATH=/lib:/lib/dll:/usr/lib:/fs/mmc0/app/lib
export LUA_PATH='./?.lua;/usr/bin/?.lua;/usr/bin/?/init.lua'
export PATH=.:/bin:/usr/bin:/fs/mmc0/app/bin
export CONSOLE_DEVICE=/dev/stdout

Ready or not, you can actually run the main HMI ui with AIR launcher now:

/bin/adl -runtime /lib/air/runtimeSDK /fs/mmc0/app/share/hmi/main.xml

And there you have it, ladies & gentlemen - the splash screen! Most probably you cannot get any further, because of all the skipped services (and missing DBUS and PPS). Those are expected to be ready and running, before UI gets ready to show. So you are left here now with this:

1) either create fake or clone from HU some ( dev fram ipc ) entries and launch all LUA bundles in boot.sh;

2) patch MainSupplement.swf Peripheral.class and pushfalse to skip peripherals you do not need;

3) combine 1 and 2, works for me :good:
[Connected Car] karlonch0:
Force Update Uconnect NON "NA" Market

Hey Guys, i have an older 14.47.1 version of uconnect, i'm trying to update at least to 16.XX but the error "system market mismatch, stick contains NA, but target is RW." shows after trying to update.

Is there a possibility to use your code/hack to bypass the market check and update?

*** EDIT***

I managed to install 17.43.01 version, but it looks like this is the higher version for ROW (Same Zone as Australia) can you confirm if this is the latest version in Australia, or how can i bypass the market check when trying to install a 18 US version?
[Connected Car] karlonch0:
I’m also interested in this version, not EU but ROW, did you solve this?
[Connected Car] SquithyX:
Not now.

The v14 software has been well well hacked, however the v17 firmware you have updated to is not hacked or currently hackable.
[Connected Car] Mousie123:
And to share your pain, the Aussie reseller of RAM's in Brisbane has their vehicles going out the door with USA map and Radio increments (bugger). Always 25K to New York and there is no workaround unfortunately, best way is access to fix these issues however I will have to await the work of others to see what can be done or not. If I cannot get to the product ID, we cant solve this one.
[Connected Car] devmihkel:
Holy cow - it's in the book :cowboy: How to stop a fast moving Jeep in augmented reality in a YA science fiction book?! Well if you can send red beams by the swipe of your hand and your name is Charlie, you know what to do :) Spoiler alert - all you need is new firmware for V850 (and strictly speaking, memifs2 not necessary at all :D

https://www.goodreads.com/en/book/show/37858133-the-god-game
[Connected Car] Tooltime:
Hey,

I found a used uconnect 8.4 VP4 EU MY15 (on Firmware 16.16.13) for a really good price, that I have put in my Dodge Challenger MY15 (US Version).

FM Radio, Nav, setting the language to german works fine. Only issue is that I fail to enable the DAB Button ( I have added a DAB splitter). I have set DAB_PRSNT to 1 (ppsVehCfg:write("DAB_PRSNT",present)), but the DAB button does not appear. I guess because the car is a US Version, so some settings seems to be wrong. I also noticed that I can tune the even frequencies in FM Mode when searching for the next station, but not when I go into the screen where you can enter the frequency. I guess this is related to the wrong setting. Does one know from where the DAB button get's added to the Radio screen? Or what conditions beside setting DAB_PRSNT to 1 needs to be met?
[Connected Car] Diabollon:
If you have a DAB antenna input, then you can activate the DAB button with AlfaOBD.
[Connected Car] Tooltime:
Hello Diabollon,

thank you for your answer.

I think enabling through AlfaOBD (BodyComputer->Car configuration change->ECUConfig 3-DAB/DMB Present) does the same thing as ppsVehCfg:write("DAB_PRSNT",present). However I tried that as well and there was no difference, the DAB button was not appearing. When I run dc.sh from Engineering menu, I can see in the output file on the USB stick that a couple of DAB processes are running (dev-tuner-dab, dabService,..). So I think the background processes are running, just the DAB button does not appear. But obviously something must be missing...

Maybe one knows in which swf file the DAB button is getting added to the GUI? I guess there must be some pre check that is currently not met and preventing from showing the DAB button?
[Connected Car] devmihkel:
I have not tried myself, so not really sure if those switches make any difference, but on 16.33.x version something there is this code in boot.sh:

# Starting dabLauncher
# DR: Temporary until DAB_PRSNT is added to canservice
# ST: This lua script exits, and even with the -b option it was taking 3 sec. to continue the boot.sh
# ST: Removing -b option and using & to put it in the background
if [ -e /var/override/forceDABStart ]; then
lua -s /usr/bin/cmc/dabLauncher.lua -v -f &
else
lua -s /usr/bin/cmc/dabLauncher.lua &
fi
[Connected Car] Tooltime:
Just want to update the Thread. I got the DAB button appearing and DAB working, it was the "Country of Destination" setting which was still set to united states and causes the DAB button from not appearing before. This causes main.swf to load TunerRegion NorthAmerica. After I have set it to Germany the Tuner Region in main.swf was switched to Europe and the DAB button appeared (after 2 cycles of rebooting the uconnect to pick up the setting). As a side effect I can now also type in even frequencies in FM mode...

Just to add some more details, the main.swf is loading the fram/hmi file for the settings. At pos 127dec is the DestinationCode, which I have now set via AlfaOBD (BodyComputer->Car configuration change->ECUConfig 3: Country of Destination) to Germany, this updates fram/hmi to the country code for germany (7).

It probably can be set via a LUA script, but as I had AlfaOBD it was easier that way for me... :)
[Connected Car] Simforov:
Hello, guys!

I've read the thread, but I still have no understanding - what is the last modifiable firmware version?

Tried 16.23 and got nothing...
[Connected Car] nihonjin:
I've never used past 16.13 bit depending on MY the versions are slightly different. What is your currently installed firmware as indicated in your settings info on the unconnect?
[Connected Car] Simforov:
It's 16.23.21
[Connected Car] devmihkel:
So far everything 16.x has been reported rootable on 8.4 head units (but starting with 17.x not anymore). What have you tried, modified UPD image to run some script from USB?
[Connected Car] devmihkel:
Serial pinout on VP4 is on the inner board, in my case without header, only pads:

It's fun to have it, sometimes also super useful to monitor what all goes wrong in custom update mode (i.e. bricked ;) Sure you can also login on the console (that is if your HU is rooted :)

Now, even more useful would be to access serial boot menu, but googling for similar qnx platforms brought up only one suggestion of shorting rx/tx at power on to try - that seems to not work on VP4.

Anyone?
[Connected Car] lden:
No need to solder - the pins are available in socket on the other side of the board
[Connected Car] devmihkel:
Lucky you, with your board full of sockets for serial and eMMC flash and all :)

I got stuck in boot loop with OTA update experiment, due to incorrect SWDL boot flag in fram. Without access to serial boot menu "Press 'S' to Clear Software Update flag" I was able to use some physical harassment on the fram chip at the boot time to get past the boot mode check. When successful in shorting data lines of the chip, something like this is shown:

QNX Neutrino Initial Program Loader for Texas Instruments OMAP3730 CMC HW Boards
IPL Version 3.01 -- ECC protect spare area + OMAP CPU Clock 800MHz or 1000MHz
omap_i2c_wait failed
omap_i2c_read: register access not ready
fram_readmem omap_i2c_read failed
...
omap_i2c_wait_status: errono Connection timed out(260), dev->status 0, stat reg 0
BOOTMODE.SH: Bootmode flag is
UNKNOWN BOOT MODE ()

Hereby I would like to thank Cypress Semiconductor for building abuse resilient chip :cool:
[Connected Car] Alex772211:
Hello everyone, tell me the pinout of the board
[Connected Car] devmihkel:
Just some update in 2021 - to all ya already-rooted or lucky offline out-of-date (ver <= 16.34.x) owners of RAx head units - wondering if latest available 18.45.01 version can be installed while already rooted and without losing root... And without serial console nor taking radio apart, just good old USB stick way... Yes! (y)

Successfully done from 16.x first to version 17.11.07 and then 18.45.01. I did not attempt direct update from 16 to 18, as some service bulletins suggested dealer visit with my existing 16.x version number. Also comments in some (OTA) update scripts had pretty special mention for V850 IOC behaviour during the update, so I tried to play safe and follow "natural" update path :)

Let me collect some diffs and post more details, if this will be of some interest.
[Connected Car] Tajadela:
excellent @devmihkel !! About downgrade of Uconnect 6.5 units, from version18, to 17, is there the possibility, through the serial port, to inject the old firmware 17.xx.xx ?? thanks
[Connected Car] devmihkel:
By looking at IPL binary strings (nand-ipl-omap3730cmc.bin) one would definitely hope to have all sorts of magic happening on serial :) Unfortunately I am not aware if any of this actually works or if there are any means to enter the serial boot menu. There is just one post in uConnect 6.5 Alfa thread claiming yes serial can be done (somewhere close to Torino I guess) and confirming the knowledge seems not going to be shared :confused:
[Connected Car] Tajadela:
thanks. can you post the uConnect 6.5 Alfa thread link??
[Connected Car] devmihkel:
The link below is not what you hope to see, sorry about that ;) But I haven't seen any updates in searching "serial" since then:

https://xdaforums.com/t/uconnect-6-5-alfa-fiat-root-access.3828426/post-78536913

(oh and not Torino, it would be Ferrera or Bologna instead... but still close enough for strong Fiat vibes I guess 😁
[Connected Car] Tajadela:
hello, did you manage to get the serial port to work? I tried to connect this port to my pc, on a uconnect 6.5, but it shows no signs of life ...
[Connected Car] Mousie123:
Hi Folks, does anyone have a copy of the Leighm0's MY16 modified ISO for USB script work and willing to share, the mega site links no longer work? Thankyou
[Connected Car] obd1976:
Hello, I also need files and description for my 2 vehicles. uconnect 8.4 old FW. Conversion USA - EU . Thanks
[Connected Car] mobista:
Never mind :)