Evil Computers
T-dåks & his w.p.s. Lyrics


We have lyrics for these tracks by T-dåks & his w.p.s.:


Blood (Don't look now, we're coming) I plug the ladies in Mum …
I Only Live Everybody at the party's so lonely In a room full of…
Intro [Master P] Where is romeo? Where is romeo? [Lil' romeo] …
Rainbows Yo, yo, yo Ridin' on my boat Yo, yo Ugh, Storm is on…



Skulls I move too fast I can't slow down I think too much No…
Yesterday (Hey baby) Yesterday has just departed Yet tomorrow hasn't…


The lyrics are frequently found in the comments by searching or by filtering for lyric videos
Genre not found
Artist not found
Album not found
Song not found
Most interesting comment from YouTube:

marcan

Ideally the first thing you do on a device like this is take a full backup of the raw flash (which can be tricky depending on exactly what kind of flash it is - eMMC and other high-level interfaces are easy and standard, but NAND flash like in this case is trickier and requires specific tools). However, in lieu of that, there is a universal method of doing proper file-level backups on Linux. This is less ideal for backup/restore purposes, but it's great to get a dump of all the files off the device and into a form you can look into on a PC (and in a pinch it'll still save your ass if you break something, though restoring might be more involved). It has the advantage that it can create mostly-consistent backups while the system is running (individual files that are changing might not perfectly match, but you won't get any wide-spread corruption like if you tried to take a raw disk image of a running system).

What you want to do is make a tar archive of the various filesystems on a device. Doing it directly doesn't work, because various filesystems are mounted on top of each other and pseudo filesystems will ruin your day. The trick is to use bind mounts.

mkdir /mnt/root
mount --bind / /mnt/root
cd /mnt/root
tar cvzpf /mnt/sdcard/root.tar.gz .
cd /
umount /mnt/root

... will make an "alias" of the root filesystem (/) at /mnt/root, but, crucially, without any of the other filesystems that are mounted below it. So you get the root filesystem and only the root filesystem. Then it gets archived into /mnt/sdcard/root.tar.gz, which you can extract on a PC (assuming you mounted the SD card on that directory in advance). The 'p' ensures that filesystem permissions are properly preserved. After you're done, undo the bind mount.

You'll want to repeat this for any other filesystem mounts shown by the 'mount' command, that aren't pseudo filesystems (usually anything that has a "real" device name). /dev may or may not be a temporary filesystem, but it is safe to archive if you want to take a look at the device node tree. /proc and /sys are system information filesystems; always ignore those, as they are not real and will probably result in errors as their contents change all the time and are dynamically constructed. Anything with type "tmpfs" is a ramdisk, but safe to archive if you feel like peeking at whatever files are there.

You can skip the bind mount part if a given filesystem has no other filesystems mounted at subdirectories. This is often the case for most things other than the root filesystem itself.



All comments from YouTube:

Knuckx

Canon DryOS is well known and hacked on by both the Magic Lantern (for EOS) and CHDK (for PowerShot/IXUS) projects, in case you want to try to play with the Canon units software. It's also used in Canon's scanners (CanonScan/LIDE) and video cameras (Legria). It will probably have a development boot mode as well, most Canon DryOS products do.

Andrew Nambudripad

Whoa Mike, 1: depending on the file system, you can probably recover the deleted data (odds are the files' inodes were marked for deletion and wont actually get removed until more content replaces it), 2: that NAND bug seems to be repairable also (if it's just a SMD flash device, you can throw a new unit on, partition it and be right as rain.. didnt seem like those were critical hardware faults, so don't continue using the second unit as a parts salvage...)

donpalmera

Hey Andy boy. If you had looked a little harder instead of trying so hard to get that unfunny reiser joke into a comment finally you would have noticed that almost all the options for ubifs are set at creation and not mount time. ubifs is a lot more complicated than jffs etc. I doubt Mike is going to spend a ton of time working through all the structure etc to find some files off of the NAND.

If it was a secure boot situation there would have been noticeable messages about it from uboot as it would be responsible checking the kernel and initramfs signatures after itself was checked by the boot rom in the chip. Google "uboot FIT" if you want to know more.

Andrew Nambudripad

Fair point there Donny boy. I'm no Reiser (for one, I've yet to murder my wife) but I took a look at the docs on Ubifs and it looks pretty bog standard. It has options for LZO but other than that it's about as complicated as one would expect for a flash FS (i.e. not very) re: recoverability. I'd need to see what mount parameters are there (it's in /etc/fstab) to ensure there wasn't anything crazy wasn't configured in, along with the boot parameters (check initramfs and the bootloader) like encryption it is a medical device after all) out-of-the-box wasn't configured but a byte-for-byte recovery. (Each write file i/o the kernel pushes to flash reduces his chances by uh I'd guess disksize-exp(1/ops) hence why putzing around in a blind attempt to fix it might be bad, unless he's configured to mount in -ro) Assuming he hasn't monkeyed with it since then his chances are very high.

That being said, even if he has mucked it all to hell, he might have some way to salvage it -- this looks promising -- http://midsamsung.com/download/system-software/ has a dl for a set of firmware (in the "Detector firmware.zip" there are 43x43, 35x43 and 30x25 subfolders with two bin's eah so I'm assuming there are revisions for different sizes), but I'm not sure if it matches his model etc.

The third avenue I'd pursue is actually contacting a Samsung medical reselelr and asking for a copy. These are high dollar items so the CSR's are generally pretty helpful if you posture as though you actually legitimately purchased this device (and the aux components) and you've been "really happy with them thus far, and are looking to upgrade our units soon enough, but this is really chaffing me!!!". Dr Mike from Massachusetts General Hospital's Radiology is quite upset

(I was previously watching that on my Nexus w/ a 4" screen & my dog was hogging my bed at the time, but by all means if you've got a spare GSM phone with a larger screen to replace it, I'd readily welcome it it ;))

donpalmera

>depending on the file system, you can probably recover the deleted data

You wrote a lot but didn't spend the 2s to look at the text and see it's ubifs..

Alex Wood

Hi Mike, really interesting stuff!
I reverse engineer embedded systems for a living, got to admit it’s fun to watch someone else wrestle with the same issues I do, day in and day out lol. As for recovering your lost files, I have a couple of suggestions. First off, if you can, use the nand subsystem in uBoot to extract the entire raw contents of the flash memory via the serial port. It’s slow, but reliable and easy to write a script to do it for you, page by page and store the results. Once you have that backup, try and find a firmware update package online and attempt to update the device. If this works, it will replace your missing files. If not, you might be able to extract the update package using a tool called binwalk and find your missing files, put them on an SD card and transfer them back over to the DUT.
If you can’t find an update package, it’s a bit harder! You need to use the nandsim kernel module for Ubuntu to create a simulation of the nand flash device on the DUT in your PCs ram, then copy the raw data from the nand device you extracted into the simulation. You can then mount that simulation on your pc and run a suit of data recovery tools on it to “undelete” the data. I have done this successfully once or twice. There are some really easy to follow online tutorials. Good luck! I look forward to seeing your next video on these.
Alex

Alex Wood

There are probably easier ways of extracting the raw flash given that you have an sd card socket on the DUT. UBoot can mount sd cards and transfer data, but it’s not uncommon for manufacturers to nerf the stock uBoot and remove most of the functionality for “security” reasons. Daft really as the most secure option would be to just remove the uBoot CLI all together. I’m used to systems where the only data extraction option is the serial port, so I like that method even if it takes over night.
Also, if the flash is in a friendly package, you could just desolder it and use a chip programmer to extract its contents (I use this method a lot too).

Moon Moon

DRYOS is a realtime OS used by Canon in mostly their digital cameras, high end webcams, that sort of thing. It replaced VxWorks donkeys years ago, and supposedly has a simulated dev environment for debugging. It has a USB interface and drivers for remote file systems and network services like a video server. There is a small hacking community for some of their digital cameras through a project called Magic Lantern. Unfortunately, my 7D Mk II is not supported and may take a very long time, if it ever is. Something about reversing the architecture of three (yes, three!) seperate CPUs - two DIGIC 6 CPUs that do the heavy lifting, and a either another DIGIC 6 or a DIGIC 5 dedicated to autofocus and exposure. Each of these DIGIC processors contains an ARM Cortex R4 and 3 other smaller ARM variants apparently, but reversing of this chips is only in it's infancy.

Hope this helps clarify one or two things about DRYOS, and what it tends to be used on.

liljasere

Your videos are always great examples of quality over quantity please never change mike

John Wilson

I had always wondered what was behind those strips on the sides of the canon image receptors. I had been told it just had something to do with being able to tell when it had been dropped. Supposedly you could drop one from waist height and it would be ok. I think I remember the cost of a new receptor was around $80,000 usd for the hospital in 2014.

More Comments