You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
Looks like you're correct, I went back to 2018.48 today and still no connectivity. So now it looks like anything before 2019.40 causes a problem with internet connectivity when downgrading firmware. I wonder why
verygreen said:The only precautions you should be taking:
- Stop odin-engine (the real spyware) and hermes-teleforce.
- You can also stop hermes-grablogs and the like. The vpn components
of hermes are called hermes-client and hermes-proxy - have those two up
and Tesla cannot log into your car but you get all mothership functionality.
There were reports that salvage Model 3 cars were able to supercharge about a week ago, but that stopped working after a few days. Please check again, and let us know if it still works for you. If it does, I suggestso I just went to the supercharger and it worked for the first time! it even auto-billed my card for the session. I'm not sure why this is, but now my car seems to do everything a normal tesla should apart from the warranty!
Has anyone experienced anything similar?
might want to disable your updates ASAP while you still have supercharging capability..I have been driving a salvage model x 100d for the last 19 months that I repaired, the car is unsupported, no software updates or supercharging
a few months ago I took it to tesla to get the ccs2 retrofit installed, expecting them to say this cant be done. they fitted it and then it could ccs charge on third-party chargers! (but supercharging was still blocked) also after they were done installing the ccs upgrade, the car started to software update as well and has been receiving regular updates since!
a few days ago I noticed that the "trip planner (beta)" option reappeared under the navigation tab, this was previously not there, so I just went to the supercharger and it worked for the first time! it even auto-billed my card for the session. I'm not sure why this is, but now my car seems to do everything a normal tesla should apart from the warranty!
Has anyone experienced anything similar?
it is still working, my car did just download a new software update, I'm too scared to install it now. ill update what happens if i do!might want to disable your updates ASAP while you still have supercharging capability..
Signed up for T-Mobile's new home service and have been waiting for the wireless cylinder, which arrived yesterday. Should be back on the air shortly. No more teathering to phone.
-1-All chime sounds are all distorted; basically anything that would typically result in a chime...an mcu reboot, putting the car in Reverse, signal indicators, park assist, and even navigation sounds have been replaced by some noise which is best described as static/distortion/interference. I'm not sure how to fix this...in thinking that this is a software problem, my first thought was to do a service-redeploy ....but therein lies another discovered issue:
-2-Running service-redeploy or any firmware update hosted locally via telnet 192.168.90.100 2596 ....fails. Everything leading up to the failure...file not served...tail -f syslog---monitored downloaded software...gostaged seems as normal but then after the install starts...screen reboots...comes back with a.."update did not complete successfully...wait for new update...." digging through syslog and combing through the logs...the below seem most relevant to the failure:
...
Hoping the above is clear enough or indicative of the issue...seems the gateway release file that fails to generate is the cause of the failure and I am not sure how to go about resolving this...Any help as usual here is much appreciated Rooter...whenever you have any time.
rooter said:1. I've has this static-instead-of-chimes, and it was because a gateway config file had me designated as having standard stereo rather than premium. Don't remember whether it was hwid or internal.dat.
2. Actually I'm presently having a very similar problem -- gateway boots and I can ping it, but service-redeploy fails after 45 seconds at "Starting". I work on this a few minutes each week as I have time. What happened was my MCU failed so I bought another which was very close in revision, and put in my old CID of course. BUT the gateway firmware (large SD) is the wrong rev causing the failure.
I have two versions of my original firmware, and laying down the first has failed this way. So now I've laid down the second and need time to put the MCU back together and try.
I'm assuming you're rooted. Don't bother to try and get your present gateway firmware from parts 1 or 2, as they hold the firmware for many versions. The place to look is part 3 in 'staged'. Hopefully that will be the same version as is in parts 1 & 2 so you should be able to lay that down on the MMC and succeed hopefully. Make a dd backup image of what you have first though. I haven't done it this way, so only theory.
1-I did see audioType in internal.dat file which could’ve standard or premium and did update that to what I had in my old emmc - rebooted the gateway but no dice :-(. I shall check again…I have not checked in HWIDs…i have gxfer the hwids file and checked it out but did not see anything in there that stood out. Should you think of anything else please do let me know…I’ll keep checking the settings in there though.
2-good points…I did completely change the daughterboard and not just the emmc chip on my original board…the original’s processor actually died. I did restore the backup of the original emmc onto a swissbit and that’s what I have running now. I did not see anything on p3 in the staged folder…in that original chip, I’m assuming you mean /cid-updater/staged? There were unpacked http files in CID-updater/ but nothing in staged; no release.tgz file…hoping I understood you right though? Logging on to the gw and running ls I do not even see a release.tgz file there and there is no /DAS folder either…which maybe explains why I’m also swing DAS_w048 unavailable? It just seems to me that something is awry with my gateway…is there any other way to restore that?
rooter said:2. You've understood correctly. meh, nothing in staged. Look for a gwy.img or .bin or somesuch in part 3.
DAS, fwiw is 'Driver Assist System', IOW Autopilot, and it's only a 'w', warning. The warning would probably be resolved with a successful service-redeploy and install.
Yes something's awry with my gateway too. I've laid down a different original image but must reassemble my MCU and try an update. I'm still learning this myself, and I have virtually no free time.
Ahh! You are clearly some sort of wizard...I found the .img and laid it down...that allowed the successful redeploy...so...whatever ambrosia you are drinking...keep doing it! If I can ever help you sort out anything Rooter please...should you ever need spare parts lemme know as I more than likely can get some.
On another note though...that did not resolve the chime issue or the 048 das---in diagnostic mode for DAS it does throw out the RaddcCommissue...I did follow your documented instructions for calibrating the vertical of the Radar but it did not seem to have an effect. Is there an Odin equivalent on Model S' that would allow the calibration tasks per chance? I dug around the directories but did not find anything there...
Thank you a million for your time again!
Well done.
It doesn't seem to be a calibration issue, and BTW you must calibrate both x and y axes. It seems to have a problem communicating with the radar. Check the connections and consider replacing the radar.
Can't explain the chimes any further than I have. It's all I know.
Actually I'm also very interested in this. Can someone share the eMMC image?Can anyone help with the latest Navigation Data Update EU-2021.8-1287 files please? I need to install manually as my car can't get OTA updates from Tesla.