-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Preventive eMMC replacement on MCU1
- Thread starter widodh
- Start date
@keon my HowTo's may help. I'm in the process of moving to Wikiversity, since DIYE uses Cloudflare which stupidly bans me for daring to deconstruct the shadow file.
De/resoldering the eMMC requires a good deal of skill, and:
- JBC infrared soldering station
- Kester solder balls
- NC-256 flux
Right, if you can mount them they're Ok. If you can do that check the firmware version in each one:
# cat /mnt/deploy/platform.ver
You must not change versions on these respective partitions, as one or the other is active and is keyed to the boot flash using code-signing. If the system is running you can get the running version by pressing 'T' at the top.
For parts 3 & 4, set aside copies of the files and use e2fsck to check them. Forget fsck for ext* filesystems.
PS - widodh are you the author of that image-building script? If so have you tested it in practice?
Last edited:
I understand what you are saying. The SC indicated this was not normal but said on exit it was operating normally. Who knows what they put in they replaced it for yellow border (before UV trick).
LuckyLuke
Model S P90DL
You can check the integrity of p1/p2 very easy on a Windows pc with the tool 7-zip, use the "Test archive" function.
You should get only one warning/error "There are some data after the end of the payload data", this is good/normal:
If you get any other errors like these then I would strongly suggest to search for a copy of the firmware file so you can use that instead of the corrupted dump.
Ok I saw, but if you look at the hex of a stock image, a ways in there's a block of gibberish. Yours doesn't provide for that. Who knows what it is?
If you're sure that's the version you need, it's easy. There's a complete library of firmware images (which I don't have access to anymore). Maybe someone will front you the image.
However do -not- try to write just any dd'ed image. They must be trimmed first using a hex editor. The images are only signed, and the signature is 64 bytes of non-zero data close to the end of the first or second partition. Cid-updater validates the signature after download. To be valid as an installed image, all you have to do is trim the file -AFTER- the signature. There is an area with 00 before the signature, and then after the 64 byte signature... cut this latter.
Also remember, on the new chip you can't just create partitions starting at block 0. There is null space before partition 1. wido has made a script to set up the parts, although there's a mystery block of gibberish within that null space. Best to restore a full image of the chip.
However do -not- try to write just any dd'ed image. They must be trimmed first using a hex editor. The images are only signed, and the signature is 64 bytes of non-zero data close to the end of the first or second partition. Cid-updater validates the signature after download. To be valid as an installed image, all you have to do is trim the file -AFTER- the signature. There is an area with 00 before the signature, and then after the 64 byte signature... cut this latter.
Also remember, on the new chip you can't just create partitions starting at block 0. There is null space before partition 1. wido has made a script to set up the parts, although there's a mystery block of gibberish within that null space. Best to restore a full image of the chip.
ok
If there is someone who can help me with these 2 partitions and a friend will win forever in Spain.
LuckyLuke
Model S P90DL
The screws have Loctite on it, and some paint, Don't think it's an issue thought?
Similar threads
