Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Salvage Car Owners Support Group.

This site may earn commission on affiliate links.
My understanding is that in the Model 3, the STORAGE is encrypted (the eMMC), and this is not the case for the Model S/X. This would severely hamper abilities to compromise the car, even with access to the hardware.

Have you successfully rooted a Model 3?

Actually what I learned (off the record) speaking with some people that have been messing with the MCU2 is that it is NOT encrypted, but I'm not really sure myself.
 
Can you guys share what you guys did for (Voltage supply too low) ?. The car was drivable and was able to unlock the charging port but while I was waiting for the airbags to be delivered couple of things happened as below :
  • v10 got installed.
  • Took off the airbag module to reset the crash code.
  • Installed the airbags.
Around those the car started throwing voltage supply too low and shutdown. Replaced the v12 battery and checked the fuses/pyrofuse but still can’t find the problem.

Any help will be appreciated.
No way to know the exact cause for sure without diagnostics, and you aren't saying enough about symptoms, like are the contactors even closing? Without diagnostics, you are relegated to expensive parts swapping. If the contactors are closing, but you still have that alert, then I'd guess the DC-DC.
 
That's what everyone is pointing to as well, I got the service manual from Tesla. I thought it would be an easy one but I will need to remove the HV battery to access the DC-DC converter which I need to take the car to a shop with a proper lift.

The service manual shows that the fuses in the Forward Junction Box.. I wish there was an easy way to that area.
 
Hi friends i have problem with drive inverter come fault - DI_f072 , before update 2020.4 this error can be reseted but now gear display on instrument cluster is red and when i engage D car dont move . Error is : Rear motor disabled - OK to drive but i have only rear motor and in fact is not more OK to be driven ( Tesla S P85 '13 ) .
Do someone can help with this situation ?
 
Last edited:
Yes, Tesla will program keys, but you first have to create a Tesla account (if you don't already have one) and transfer the car into it by submitting a picture of the Title or valid registration, and a copy of your DL/ID, and the name on it MUST match the name on the title/reg. Then they will enable the app on the car and it can be driven. Then it's a simple matter to drive the car to Tesla and they will program a key.

I can also do this, but it's a bit more complicated, as it requires root access. Best bet is to go to Tesla.
 
  • Helpful
Reactions: markwj and MP3Mike
[SIZE=4 said:
psyched[/SIZE]]Hi rooter,

at first I have to say that your postings on TMC are very interesting for me, thanks for sharing you knowledge.
As far as I can remember you've been the first one sharing real informations than just small bits - and it seems you're the first one and also the last one because most the other 'specialists'(in hiding informations) disappeared.

At the moment I'm working on a MCU1 that I've purchased just for bench. But how life goes the emmc from my own car also wrecked last week.
With the bench MCU I'm starting with an empty image because I don't care about keys&certs, just firmware (2019.20.4.2) on p1/p2 and empty p3/p4.(I could dd/ddrescue the old emmc without errors but it's not readable, fsck and gparted data rescue couldn't help - I only can mount p1 and see directory strucure and files but no information inside.)

I also want to obtain root and I really have read your 'manual' several times but I've still some questions.
- according to the situation that I'm starting with empty p3/p4 directory/file structure is created on first boot as I've heard - so I'm not able to find the files you've described in your step-by-step instructions.
- since 2019.4.x tesla is mounting a tpmfs over cron - what's the best workover for this issue?

I always try to find as much as possible informations on my own - before questioning. But I don't want to make to much try and error especially when it leads to resoldering the new emmc on tegra board ;)

Well, first thing is to get a good backup. I have an article for that.

I haven't gotten to describing kpartx yet on the whole image.

If you can consistently dump a good whole image of the eMMC (compare multiple dumps with sha256sum):
# kpartx -a {mmcblk0}.image
# mount /dev/mapper/loop1 /mnt (I'm going from memory here)
etc...
# umount /mnt
# kpartx -d {mmcblk0}.image

If you can confirm good images this way, then get images also of the individual partitions.
# dd if=/dev/mmcblk0p1 of=mmcblk0p1.image
... etc

Then check the versions of your partition 1 & 2 images, and the newer one is the one you're currently running, so this is what you'll put on both partitions in the new image.

Then install your parts 3 & 4 to the main image. (kpartx it, then dd to the /dev/mapper/p3 & p4)

I haven't had time but at some point will add this to the articles.