Search results

Hi folks, a sidenote to those who have a failed eMMC and (before the fail) a version < 2019.40 (I'm unsure of it had been already mentioned): If you restore your data, also restore the file "/var/lib/usbutils/usd.ids" (it can be found in "/usr/deploy/cid-var-files/lib/usbutils/usb.ids")...

They were able to access the data from my broken eMMC (which was not accessible through the normal interface at all).AFAIK they only charge you for successful recovery. So you pay only for shipping if it fails.

Have a look at this article, it also covers the boot process and how the content of NOR and eMMC interact: Reverse Engineering the Tesla Firmware Update Process | Pen Test Partners

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...

If you still have the old EMMC a recovery might be possible via direct NAND access by someone who does flash data recovery. I learned in TFF forum that one austrian guy managed to force tesla into providing the VPN and Certificate data by pointing towards EU anti-trust regulations related to...

Partition Type is 0x83 (Linux), Filesystem in P3 and P4 is ext3. If you experience errors than you might have had read errors when creating the image and/or the filesystem is already damaged.

Maybe try to force the filesystem type to ext3 when mounting (additional parameter „-t ext3“, see help or the manpage (man mount) for details ).

As far as I can see, there are only 3 connections between your laptop and the CID - I suppose CLK, CMD and D0. You are missing Ground/VSS. That needs to be connected to all 3 devices (Laptop/Reader, CID and Power Supply).

Then you better not park your car outside during wintertime ;) Seriously, things (complex electronics) don't break that easy when its getting cold, most parts only start to misbehave (for example flash memory takes a lot more time to erase). I know because I use the climate chamber I talked...

Still - In some cases the controller inside the eMMC is bust - then even cooling down the chip down to -40°C in a climate chamber won't help (ask me how I know ;) ). But recovery of the files directly from the NAND array could still be possible.

Well you could do a trial-and-error process and just install different versions to the eMMC until it boots.

Hi everyone, I just accessed another eMMC (of another CID) using another reader than last time, and made some observations I would like to share. But first I have to correct an older post of mine regarding the required connections to the eMMC. After obtaining the eMMC specifications (JEDEC...

Either use "sudo su" once to become root before executing the desired commands or use "sudo " before any command that requires elevated privileges.

Of course that is a possibility. But one thing is for sure - without a proper conection between reader and eMMC you won't even get data if the eMMC is NOT toast.

An eMMC is basically a solder-version of an SD-card, they have the same interface (except that the eMMC provides up to 8 data lines, whereas a normal SD card provides only 4 data lines). An SD-card can be accessed either in 4-bit (MMC) mode or single-bit SPI mode and so can an eMMC. See the...

Well you need to connect it to the corresponding output of your reader. The following lines are the minimum required: CLK, CMD(DI), D0, D3(CS), Power (Vdd/Vcc/whatever you call it) and Ground (Vss/GND). Power is provided by an external Supply set to 2.7V - Do NOT connect that to your reader...

Your missing the connection to "D3" (which acts as CS in 1-bit mode). Add the wiring and it should work.

I would not describe that as an incompatibility (because protocol-wise the Hynix eMMC can talk to an SD-card reader) but rather as an example of inadequate HW design on the side of AllSocket which causes the thing to fail due to power delivery issues. (At least it can be fixed by increasing the...

The overall power supplied to the board in my case was about 2 W (2.7V * 0,75 A). This did only generate a moderate amount of heat.

Just a thought: If the CID contains multiple power converters (to generate different voltages like 3.3/1.8/1.2 etc.), then there is most likely something like a power monitoring device which keeps the SoC in reset until all the power rails are stable. It would probably be easier to search for...

Is there a voltage where the current decreases below 1 A? Did you double check your wiring?

The pinning is exactly that what was shown in the beginning of this thread: Successful data recovery of broken eMMC chip MCU1 Except that I used multiple VSS/GND connections (just to be on the safe side). I used ddrescue on Ubuntu 18.04 LTS and on macOS 10.13 (HighSierra) ... The USB device is a...

One goes to power supply ground, the other one to the SD-card reader ground. Furthermore if you take a close look, you can see that I used multiple ground wires. Between adjacent signal lines coming from the SD card reader I always put one VSS/GND or VCC line. For practicality reasons I...

I suppose it's a matter of signal integrity and power-delivery. Normally (in-system) there are capacitors close to the eMMC (and every other IC in the system) to buffer the power rails (VCC & VCCQ in this case) and the eMMCs connection to ground are short and in high numbers (and thus posess low...

For doing the onBoard/in-System readout I used this kind of Device: %product-title% kaufen and did some soldering: This was the setup I wrote earlier about which gave me a good read-out of a non-defective (!) eMMC. For writing the new eMMC chip, I thought about the Allsocket Adapter but...

Well, it basically did work, I just had to restart a couple of times on the big partitions. Could very well have been an issue with the "el-cheapo" kind of card-reader. The USB device would simply bail and be rediscovered again. I did multiple readouts on Linux and macOS (using ddrescue) and...

I managed to dump a whole (intact) eMMC last week using the shown wiring and an el-cheapo SD-Card reader on Linux. The transfer speed was around 22 MB/s. The same setup only yielded around 6 MB/s when using a Macbook Pro, also producing read-errors on some occasions. The CID was powered with 2.7...

I got lucky today and managed to dump the eMMC partitions. So if anyone might want have a look, I'm willing to share (except partition 3 of course).

Hi there, a while ago I managed to buy an IC and (matching) MCU1. I kind of had the idea to use it as a dev/staging system when playing with the software (which until now is just a plan) in order to not brick my precious car when something goes wrong. I powered it up for the first time during...