Uncle Paul
Well-Known Member
Imagine Tesla engineers are cringing when they read what creative independent individuals and companies are trying to do on these cars.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
It's a fact that Tesla offers the worst possible service to independent repairers/operators in the whole automotive world.
I don't know any other company that refuses the access to diagnostic software, tools and parts in that way.
I'm working on this on behalf of a friend, and i believe he called them and told them the screen was black. They tried to diagnose over the air but could not connect to it, so he was told he needed to get an appointment with a service center.
This is the partition table from my read: isk /dev/loop0: 7.3 GiB, 7818182656 bytes, 15269888 sectors Units: sectors of 1 - Pastebin.com
I shipped my old eMMC to Poland to see if they could do NAND direct recovery. If I'm recovering all 0s, I'll be surprised if they find anything different. But here's hoping.
Tried the MCU with p1 and p2 restored and p3 and p4 empty save for apn-file and folders. MCU did not start up, tried the steering wheel reboot methods a couple of times. Desoldered the new emmc again today to verify i didn't damage it while soldering it. It was fine. Read the syslog file created on p3 which contained over a million lines of squashfs read errors. Turns out that p1/p2 wasn't ok after all. Unsquashfs confirms that they are toast (i should have tried this before..).
Any ideas on getting MCU operational without intact p1/p2?
Any ideas on getting MCU operational without intact p1/p2?
The way I understand it, older Instrument Clusters have p1/p2 on their eMMC as well. Speaking of, anybody willing to remove an eMMC from a daughterboard for me? I pulled apart an IC that I replaced a long time back, curious what's on the chip, but I haven't ever tried pulling off a chip and I'd rather not f' it up. I'm located near El Paso, willing to ship and also willing to pay.
Hi folks,
finally I am able to report that my recovery (albeit delayed somewhat) was successful. I accessed the eMMC again last week (this time using 1-Bit mode - because I was lazy and thought 3 wires + supply are enough soldering this time) and installed the openvpn credentials and mcu_commands_key (recovered within 1 weeks time by multi-com.eu).
My car now reports back to mothership, is accessible via the app for the first time since february, my spotify songlist was restored (most important
) and the update for the current version is pending.
I wish to express my gratitude to everyone around who supported me in this quest.
finally I am able to report that my recovery (albeit delayed somewhat) was successful. I accessed the eMMC again last week (this time using 1-Bit mode - because I was lazy and thought 3 wires + supply are enough soldering this time) and installed the openvpn credentials and mcu_commands_key (recovered within 1 weeks time by multi-com.eu).
My car now reports back to mothership, is accessible via the app for the first time since february, my spotify songlist was restored (most important
) and the update for the current version is pending.I wish to express my gratitude to everyone around who supported me in this quest.
Any updates on this? I was just about to contact them to get my keys from the chip.
I have the same issue: only zeros. The new chip is already changed with default sw without the keys.
