Restore MPC X SE factory content

The Akai support team has first send me the wrong recovery files (MPC X, Live) and after I’ve pointed out their mistake I’ve received another .zip download for the MPC X SE. The file is named content.img

But I’ve received it without any instructions. Does anyone know the instructions of how to use this file?

Firmware updates are .IMG. I'd assume you hit update and usb update and it will do it's business.

Don't take that as Correct. I'm just speculating

eLuSiVeMiTe wrote:Firmware updates are .IMG. I'd assume you hit update and usb update and it will do it's business.

Don't take that as Correct. I'm just speculating

Thanks, but I’ve already tried that..

zangetsu01 wrote:

eLuSiVeMiTe wrote:Firmware updates are .IMG. I'd assume you hit update and usb update and it will do it's business.

Don't take that as Correct. I'm just speculating

Thanks, but I’ve already tried that..

viewtopic.php?p=1836058

Any use?

Haha schadenfreude!!!

I have the recovery image for the Live and have used it on mine awhile ago.. If I remember correctly, put the img on a USB drive, plug it in, and I think the MPC recognized it and asked me if I wanted to restore the device right then and there. It was either that or you boot with it in the MPC and it will see it on boot and run it. It was a few years back so can't really remember. I did it around 2.11 trying to see if it would 'fix' some of its issues hah.

Same issue here. MPC X SE does not recognize content.img (I know, I know, file needs to be in root directory) no matter how I try to use it (SD or USB, with or without SSD installed.)

File isn't recognized/working on MPC 3, or any of the firmwares below that (currently rolled back to 2.15)

What's kind of ridiculous is that if I change the name of the file from "content.img" to something like "mpc-x.x-update" (the Xs represent diff version numbers) my MPC X SE sees the file and offers to update from it, although the update fails after reboot

OCD is a Real Thing lol. Its Ridiculous to think we have to Delete Factory Content that we're not Using

I'm just trying to sell my MPC X SE in the stock condition it came in. The on device reset is basically just a settings initializer (it doesn't even scrub your previous wi-fi credentials after reset, which says a lot about how "soft" the reset is)

Damn dude did you ever get it fixed? this post is from a year ago now.

substantialRip wrote:Same issue here. MPC X SE does not recognize content.img (I know, I know, file needs to be in root directory) no matter how I try to use it (SD or USB, with or without SSD installed.)

File isn't recognized/working on MPC 3, or any of the firmwares below that (currently rolled back to 2.15)

content.img, apart of the actual content, contains three files:

1.
AUTORUN - which is executed when your pendrive is inserted. It contains set of basic startup rules and path to a proper script that's being run, for example:
{
"value0": {
"files": [],
"scripts": [
{
"askQuestion": true,
"path": "install-content.sh",
"message": "Install content? This will only install on an MPC One.",
"noButtonText": "no",
"yesButtonText": "yes"
}
]
}
}


2.
*.sh script which can run any arbitrary code as root. Basically, inside of it you may put any bash script which will be executed, no matter if it's a fork bomb, rm -rf or whatever - everything goes as root. This file contains instructions as to what to copy and where during the update.

3.
AUTORUN.CHECK - This is the most important file out of all of them, it contains hash of two previous files and it's should be generated after previous files are in their final form. Any further changes to the script files will result in a different hash and your mpc won't run the updater. If the hash inside the file must be the same as what mpc is generating based on two script files. In other words - this file opens your mpc without even tampering with the firmwares SSH stuff.