yashsingh1/xdaforums huggingface dataset:
[Moto 360] bustanut666:
I am getting same thing for last couple updates. Don't even use watch anymore Cuz it just shuts off randomly. Tried clearing everything and reinstalling, etc. No luck so far.
[Moto 360] ykazimir:
Same thing here, but mine shuts down during my run when I listen music off of it, around 75-80% battery, but works fine when I use it normally, without connected Bluetooth headphones
[Moto 360] Dan76:
I've been getting random shutdowns for the last few months.

Sometimes I feel like it's triggered by lots of vibrating on the watch, but no correlation to battery level, most of the time it's in the 60% percentage.

I've done a factory reset and deleted and uninstalled and reinstalled android wear on the phone several times, and it always fixes it temporarily...

Sounds epidemic.

How hard was it to get a replacement?
[Moto 360] waahre:
Anybody able to find a fix? TIA
[Moto 360] MarkCoburn:
Same problem. At first I figured it was a but that came with an update and would get fixed on the next one. I stopped wearing it for a while. Now, months later, still doing it.

I got the 360 the first day it was available. I'm thinking that I'm probably out of warranty now. Should have placed a complaint when it first happened.

Has anyone found a resolution?
[Moto 360] Dan76:
My experience is nearly identical to yours. Bought my Moto 360 on release day, it started having problems about 9 months shutting down. I factory reset, removed apps, eventually upgraded to a different phone, all the problems continued.

When I finally called Moto support, my warranty had expired, but they told me for $100 they'd replace it. I did that and just got my replacement, and I must say it's Awesome. I forgot what it was like to have a smart watch that lasts 18 hours and never shuts down regardless of how much I use it!

So, $100... you can buy a new or refurb Moto 360 for that online, so maybe it's not worth it. It's still a great smart watch IMO though. At this point I feel no need to upgrade to 2nd gen.

For the defects, this appears to be a widespread problem for Moto 360 1st gen. Best of luck to you.
[Moto 360] abdul.kader.sagar:
still any solution

Did anyone find solution to this?
[Moto 360] djbutter:
I've the same problem. In fact, it won't restart until I put if back in the cradle. On top of that, I no longer get any messaging/email notifications.
[Moto 360] Dan76:
Well, about 16 months in to my replacement and it started happening again... OG Moto 360, just like the original. I suppose it's time to upgrade. Still, 16 months for $100 outdated technology smart watch worn every day isn't terrible.
[Moto 360] Rick Butts:
I had the same issue, would randomly shut down and whenever I tried to open an app or settings it would just die. It was the battery, i found a replacement battery on ebay for around $25 replaced it and now it's working as expected.
[Moto 360] Dan76:
Wow, seriously?! I just looked, and sure enough the batteries are all over eBay. How difficult was it to replace?
[Moto 360] Rick Butts:
not too hard to replace... Check out the instructions on YouTube... Took me about 15 minutes
[Connected Car] cm0002:
huh i thought there would be more interest? i mean this could be the key to getting rid of the crappy uconnect software and run android.

Android has already been made to run on the same SoC TI DM3730 here http://elinux.org/Android_on_OMAP
[Connected Car] cilk:
Hi,

This is very interesting! I don't have a Cherokee but I own a 2015 Challenger RT with the 8.4 uConnect. There's so many FCA car that came with this system that could be very good to uconnect owner! I would like so much to see more options, customization, maybe having specificar car option unlocked or the navigation feature or the best would be to have android directly on it!

In the challenger community, we use a dongle called Tazer http://www.zautotech.com/tazer.html that can unlock special feature available only for a specific trim level. Like the Challenger SRT have an ECO Mode in the uConnect for saving gas but after plugging the Tazer you can unlock this feature for a Scat Pack/RT and it's working! I don't know for other FCA car but hacking the uConnect could open a pandora box for us!
[Connected Car] cm0002:
ah yes the dongles, the jeep community also has such things to remove the speed lockouts for the keyboard and add in cameras and such. I have been working a decompiling alot of the programs, but havent got so far yet been busy and all, but what i have noticed is that alot of it is easily decompiled compiled lua 5.1 scripts or just scripts here and there.
[Connected Car] cilk:
The dongle or even lockpick seem very popular. I didn't know the dongle was just some lua script, they make big money for just small hardware and script then! I've also read the PDF document and I find this interesting that we could setup a VM on qnx with uconnect on top of it. This could help people to have more interest for the uConnect if they can simply have a VM available easily. I'm not a developer but a simple IT technician and I find this really interesting, I've just started to read about this, qnx and lua script.
[Connected Car] cm0002:
Yea, this situation is exactly how it was with the ps3, some company found a way in and instead of opening it up they profit on it. The more i go through i have found that the entire uconnect front-end gui seems to be made up of lua scripts, html, flash, and adobe air which call the services for the various systems from the underlying QNX system.
[Connected Car] leothelocust:
Awesome!

I have a 2014 Ram and would LOVE to see some changes to the UI and maybe unlock somethings too. I'm an android developer with mostly web background, and could possibly lend a hand in the code department, but Lua is pretty new to me; however, not real complicated. What amount of flash does the UI depend on? Seems like a pretty terrible language choice, but I suppose uConnect started writing this code several years ago...

Ideally, we'd get a version of android running on this thing!! I don't know about the Jeeps, but the uConnect system on the Ram basically controls everything... I'd lose the ability to do most of my A/C controls :eek: so I'd simultaneously have to be making an app that would be able to interface with other systems in the truck...

I'd like to see what kind of interest there is about this as well [MENTION=2895094]cm0002[/MENTION]. Thanks for your guide!
[Connected Car] bled82:
Anyway to run android off the usb drive , run an upgrade boot and redirect to the android os on the usb and run it without changing the system on local ?
[Connected Car] leothelocust:
I'm sure you could, but you wouldn't have access to any peripherals... That's really the hardest thing here, imo.
[Connected Car] Ireul:
So, QNX will support Android Auto and CarPlay, some implementations are going out the door right now.

By rooting uConnect current versions, it may be possible to backport the future uConnect QNX apps that facilitate Android Auto headunit communication.

The sticking point will be if the QNX kernel that features Android Auto on those newer uConnect models, is backwards-compatible or not with today's uConnect head units. That's questionable at best... but probably the best implementation path.

Frankly there's nothing stopping FCA from doing the upgrade themselves. Would make for a heck of a game changer as a Mopar part.
[Connected Car] Joshwaaa:
Watching this thread, very interesting to me as I have a 2016 Ram 1500 Laramie.
[Connected Car] chowner:
Very interesting!!!!
[Connected Car] zzEvilGeniuszz:
It is a crime this thread has not been given more attention. If we could do-away with the Uconnect overall lands replace it with Android, that would certainly be ideal.
[Connected Car] zzEvilGeniuszz:
Have you seen this?

This is exactly what I am looking for. But they want a crazy $560 US for it. #SmokingCrack

https://youtu.be/67cdq2uiNu0
[Connected Car] CXENTE:
Very interesting!! I have the 2014 chrysler 300 with 8.4 uconnect
[Connected Car] hbernier:
Wery interesting indeed! I've checked the web site of the Swedish guy who made it and unfortunatly he is asking big bucks for his software port.
[Connected Car] bratner:
The "car radio" problem is hard get for car industry people.

The mindset in the car industry is, obviously, not the same as in software industry. You and I see a "better way" to do something but what they see is another version of "computer people nonsense". Most of the decision makers in the industry still see it all as "car radio". Even if they will go for android automotive, they will make the same mistakes.
[Connected Car] cm0002:
Sorry guys i haven't been back to this thread in awhile, i haven't had much time to work on my jeep, i had worked through de-compiling maybe 50% of the compiled lua(? i cant remember ill have to double check) scripts i was going to post the de-compiled versions of the scripts for others but i became busy with work and family and on the other hand is it even legal for me to post de-compiled proprietary code?
[Connected Car] sadffffff:
Also very interested in this, I have a 2015 Cherokee.

I've been looking at all the solutions out there for adding functionality and haven't found a perfect solution yet.

There are dongle solutions with video receivers, (UCONNECT LOCKPICK AIR V2) but this doesn't allow the use of the touch screen

There are the RAX jailbreak products that are just software and add a few camera switching solutions and disable lockouts.

There are complete android systems that patch into the resistive touchscreen. This option is interesting but requires an invasive hardware mod.

I would love to see things like;

unlocking the NAV on the nav-enabled units

changing the default options on certain vehicle functions

reverse the engine auto-start/stop functionality to off by default

set the seat heaters to low by default)

disable lockouts for cameras/GPS

switch to camera on-demand

a web browser would be nice.

android and/or ios device mirroring.
[Connected Car] ramathorn1982:
I'm very interested in this!

---------- Post added at 05:19 PM ---------- Previous post was at 05:15 PM ----------

Check this out. I would love to see some DIY development on this!

Uconnect 8.4 Android system to factory screen (search for this on YouTube)
[Connected Car] nihonjin:
So i have manged to get the wifi hotspot feature to work by copying the productid file from the unit using the script.lua and then a hex editor to modify and re-uploaded the productid file to activate the hotspot function. I dont really know how to ssh into the unit and view or watch any processes let alone access the log files.

Unfortunately I also still dont seem to be able to activate my Sat Nav which is my main goal. I have tried so many different things but cannot seem to get it to work.

My unit is from a 2013 MY14 model laredo that did not have any sat nav pre installed. I have tried copying files from android igo with paid licence and files form older igo maps found online as well as map files and licence from other uconnect files. None of them seem to work. I keep getting the same issue where in the settings my naviserver and map database says undefiend and when clicking on the sat nav icon i get navigation is being activated.

I am using the naviserver2 file posted here by Leighm0 as my unit does not have the orignal naviserver file and also the other files that go with activating the unit are also the ones posted by Leighm0. What else is there to try?
[Connected Car] robert991122:
I've found a modified version and had a quick look inside.

They have two iso's "swdl.iso" and "swdl-fo.iso". The swdl.iso is an old, maybe modified version (like 15.xx.xx) and the swdl-fo.iso seems to be the new one (also modified).

The "local manifest" section "parts=" in manifest.lua is modified. But there is no script call.

Any idea how it works?

I've found also some description of the update process: h t t p s : / / haxor.fi/how-the-firmware-updates-work-on-toyota-touch-go/
[Connected Car] Tooltime:
Hej nihonjin,

as a first step, I would try to get the bare minimum to work first and then step by step add files.

e.g.

delete everything from these folder (take a backup first ;) )

/fs/mmc0/nav/NNG/content/building

/fs/mmc0/nav/NNG/content/dem

/fs/mmc0/nav/NNG/content/phoneme

/fs/mmc0/nav/NNG/content/poi

/fs/mmc0/nav/NNG/content/speedcam

Also delete everything from /fs/mmc0/nav/NNG/content/map folder except the basemap and keep also the corresponding lyc files.

Now see if the your uconnect comes past the activation screen.

If that works you should be able to see the basemap, which is baiscally the different continents.

Now start adding the country maps and corresponding lyc files.

If that also works add the rest step by step..
[Connected Car] nihonjin:
Hi [MENTION=2023777]Tooltime[/MENTION] I have done as you have suggested but still the same result. Will not activate. If you don't mind either here or via pm could you send me your basemap file and lyc file to test on my system. Thanks.
[Connected Car] nihonjin:
So in an effort to try and get the Nav working on my unit i have updated my uconnect to 17.43.01 and my unit is now VP4 version. So I can no longer use the modified swdl.iso post here. Does anyone have a modified VP4 version of swdl.iso i can get a copy of so I can see if my firmware still allows me to load custom scripts. I may find the later firmware has blocked this but i found that the new firmware requires not only the swdl.iso but an update file as well ie swdl.upd as when I used just the modified swdl.iso nothing happened but when I put the swdl.upd file from the 17.43.01 firmware I loaded it detected the USB but said that the stick was vp3 and my uconnect was vp4. So I just chasing if anyone can share a modified VP4 swdl.iso.

thanks in advance.
[Connected Car] itsJRod:
I'm on 17.11.07 and using a 17.43.01 UPD to try and get in. I have been reading these threads here and JEEP Garage for 3 days and I'm hung up on what is probably my own ignorance and lack of knowledge. I'm hoping a few more experienced guys can point out what I'm missing in this process...

I still show the "ota_update" as the last block in the Manifest.lua script. When I edit this to fire a .lua or .sh script from usb (I tried both), I get a hash mismatch between data and header error... From the posts about the 16.13.13 UPD mods I thought I was good to go.

I'm hoping that I'm not formating the lua script correctly to call the script on USB. If that's done correctly do I need to edit an SWF? I vaguely recall reading someone write that the latest versions might require some SWF editing to get a script to fire, but I'm having a hard time locating that post to look into it more.

Do I need to worry about checking the hash with the keys in the /usr/share/IFS/ifs-cmc.bin? then checking again after my edit? I believe it was also mentioned by Han67 that he may need to recompile the ISO after extracting and editing. Is this necessary, or even possible, given the information we have? That would be a strong learning curve for me to find the appropriate software and parameters to accomplish this.

I'm attaching "before", "attempt 1" and "attempt 2" screen shots. It was mentioned to mount and view the script to check that it is successful and formatted correctly (assuming someone knows more than I do about these things)

I did order a D-Link DUB-E100 usb ethernet dongle that matched the one in the Script, but without having ssh opened up, I think I will have a hard time bruit forcing the password once connected... If this version still has ssh enabled as the older versions did. I should have my dongle tuesday, but if I can't figure out this hash error its not going to help...

I'm having fun trying to get my head around these methods... I had given up hope when I saw the OTA pushed itself on my wifes' Durango before I got around to trying this on the 15.x version. When I saw posts about UPD versions being successful, I decided to jump before something got even more difficult.

I didn't get far before hitting a wall for the last 3 days.
[Connected Car] devmihkel:
Yeah, 2nd attempt is much better as last lua block is correctly terminated and your script might actually run, but unfortunately no successful 17.x runs have been reported so far :( SWF scripts are not involved in update/jail-breaking run, these ones become relevant only once you are in (and need to enable some app or wifi or navi features etc). Afaik 17.x blocks ethernet dongle usage as well, but let's see if even the USB driver/link gets activated at all?
[Connected Car] Tajadela:
hello, someone know which jtag interface and which software could connect to a 6.5 uconnect cpu?? I made a couple of photos of internal card ...
[Connected Car] SquithyX:
For those people on here with the uConnect 6.5, i have found a 15.18.00 swdl.iso that can hopefully be modded!!!
[Connected Car] Tajadela:
yes, this version is for 6.5 uconnect, but only for Alfa Romeo Giulietta Uconnect 6.5 (model 940). Non usable in Uconnect 6.5 for Fiat 500X or Renegade... :(
[Connected Car] sofro1988:
where did you find it?
[Connected Car] SquithyX:
Found in on a Alfa Romeo forum, the person that shared it had tried to update their ROW uConnect with the EU uConnect 17.07.55 file and their uConnect was stuck in update mode. They were sent it by a repair company in the US after contacting them as Alfa / FCA did not respond to help requests.

If I have modded the file correctly, the ROW and model specific requirements should have been removed so it should work on any 6.5 uConnect - if they share the same private keys!
[Connected Car] Tajadela:
Hi,

can you share what changes did you make and where?

have not you been able to try the changes yet?

thanks
[Connected Car] m4x23:
Is possible to have the file?

Thanks
[Connected Car] Tajadela:
here the link

https://drive.google.com/uc?id=0B2uxS3LWdHp9S1BKUk1mWlFtWlk&export=download

for m4x23: Sono di bologna, se hai qualche sviluppo fammi sapere... Sono mesi che ci studio. Grazie
[Connected Car] SquithyX:
The changes I have made are to the System_Module_Check.lua and the manifest.lua files, following Leighm0 example from post #106.

I have just finished work, am going to give it a go this eve, so fingers crossed!!!

All the files i have collected so far including the 15.18.00 ROW swdl.iso are all here:

https://mega.nz/#F!kMYjlSKB!MCC6U1jclb0_aHc-NdocrA
[Connected Car] SquithyX:
And...nope, it does not work. I get authentication error when I plug it into the system.

The first time I tried it, it stated it was ROW and not for EU, so quick change to the manifest.lua file and that worked, it no longer shows that error, just the authentication one. I guess the firmware on my uConnect is too new!

I will upload the EU edited one to mega for anybody to try, if they have older than 17.07.55 installed on their uConnect.
[Connected Car] Tajadela:
unfortunately I had already tried something like that ... I have a uconnect 6.5 with firmware 14.03, and I receive the authentication error. The only ways to go are to find the root password, access it with the usb ethernet adapter, or via JTAG.
[Connected Car] sofro1988:
io di ferrara :)
[Connected Car] sofro1988:
in the 8.4 system, users have changed the "root" password through an hex editor. so it should be the same for us. just a question, do you think we are able to use an ethernet to usb adapter to navigate inside the uconnect?
[Connected Car] Tajadela:
If I try to change root password, I receive the usual "Authentication error"...

with the adapter I can have a telnet access, but at login I do not have the root password. With the password you could enter and browse the folders of the operating system,

to find, for example, the private key to calculate the right checksum of any modified swdl.iso...

with the private key, you could create ISO images with any changes ...
[Connected Car] sofro1988:
it would be great for our scopes :)

for me i guess is the only way where i can go since my firmware version is 18 already. what about estrapolating the password from the iso with the hex editor?
[Connected Car] Tajadela:
yes, you can find the password in the iso image, but is crypted.

To decrypt you need the key to uncrypt it.

I am not an expert in this type of encrypted software. but if someone is able to do reverse engineering,

knowing that "root" encrypted is "8CNGLiYvSaCbg", you could try to find the key to decrypt the current password. but it's not easy at all ...

in version 15.21.37 and 16.05.32 it is, for example, "Yvx4SWAOZ7Pcw"

in the iso files you have to look for the pattern "root:xxxxxxxxxxxxx:", where xxxxxxxxxxxxx is the encrypted password...
[Connected Car] sofro1988:
what about the other tool you mentioned before? i mean the jtag
[Connected Car] Tajadela:
in simple terms, it is an hardware interface, which allows you to connect directly to the main CPU.

It is used for the development of hardware prototypes and with this you have direct access to all the registers, ram and rom of the CPU itself.

In uconnect 6.5, which I disassembled, I see two cpu: a NEC v850 and another cpu DRA579BCUS, which I still could not find info.

For the first cpu, NEC, there is a JTAG interface, but I'm not sure it's the right CPU to connect to, because, as I understand, it's the one that manages the CAN network and not the graphics and navigation.
[Connected Car] robert991122:
I checked your modified EU version. I found that manifest.lua was changed ( variant_market = "EU", ) before the 2048 byte mark. This may be a problem with the ISO authentication.

As far as i know, they do a small, fast integrity check with the first 2048 bytes of each file.

See: h t t p s : / / jeepgarage.org/f155/uconnect-15-26-1-is-buggy-i-want-to-downgrade-89382-20.html
[Connected Car] itsJRod:
ETFS_RAW dump

Found what I needed was not the ETFS_RAW dump done through the engineering menu, but I needed the cmc_ifs.bin on the iso for the version I'm running.

devmihkel posted it here:

https://xdaforums.com/showpost.php?p=76798798&postcount=140

Do you know how to mount this raw image? I've been tinkering with it in Ubuntu with no success...

I've also been hoping to find someone with the QNX tools now that they don't like giving out the trials anymore...
[Connected Car] itsJRod:
USB Ethernet

The USB ethernet doesn't load, However, it may be only becuase the HW version is newer than the driver that is present in the Uconnect. I believe the Product ID i am showing is "1A02" and the embeded driver in QNX is "3C05" (I am going from memory so correct me if I'm wrong."

I'll post updates if I have any news with ISO runs or Ethernet access. Even if I get USB ethernet or WiFi I still need to decrypt the SSH password or see if I can brute force it... I'm not sure what to look for in the SSH settings to see if it will reject or disconnect brute force attempts. If I'm confident I can crack SSH I'll pay for a month of WiFi to get initial access...