Can you wipe a USB flash drive so securely that it’s impossible to recover deleted files through forensic analysis?

Internal SSD can be wiped with TRIM, but USB sticks are external SSD. They’re apparently difficult to wipe securely enough to make forensic analysis of the device impossible. This question has been asked before, about 4 or 5 years ago and the information is probably outdated. Looking for up-to-date advice on how to securely wipe files on a USB from a bootable media.

Is it possible to have a setup that can securely wipe USB with TRIM? Anyone know of any programs that will securely shred files on USB, making them impossible to recover via forensic recovery software?

Software to transfer files from one large hard drive to multiple smaller hard / flash drives?

Any suggestions of a software that would allow copy files from a large drive to multiple smaller drives, preserving all attributes of the files, such as created/modified date?

I’m looking for something that would fill one drive up and ask for another destination to copy remaining files until that drive is full and so on until all files are copied.

FastCopy almost works, except it doesn’t allow changing destination without resetting of what already was copied (I could be wrong though)

Odin custom bootloader flash fail (but original stock bootloader flash successful)

This question is regarding my Samsung J5 running Android 5.1.1.

I am able to flash the bootloader (BL) with original stock bootloader. Odin clearly shows the boot partition being flashed and then auto-reboots. The phone boots normally.

However, following a minor edit of the init ram fs, I am not able to flash the bootloader using the new edited bootloader (see below for Odin PC terminal output and phone Odin mode output).

I turned the custom boot.img into boot.tar and did not apply an MD5 sum. This is the exact same format/method as I used for the original stock bootloader.

I have ensured that I recreated the boot.img correctly by extensively comparing hex-dumps of original boot.img and my custom boot.img.

OEM unlocking is enabled in Developer Options.

Seeing as I am able to flash the bootloader using the original “stock” bootloader, it is my guess that it is being rejected because the generated MD5 sum is not matching the one in the low-level firmware.

I have tried with Heimdall but it fails to read the PIT successfully.

My only remaining solution is to root the phone and write my edited bootloader to the boot partition (using cat or dd). However, I feel that this may be missing the point (custom fails numerous times and original was successful numerous times using Odin).

Thanks in advance!

Added!! Odin engine v(ID:3.1203).. File analysis.. SetupConnection.. Initialzation.. Get PIT for mapping.. Firmware update start.. SingleDownload. ./boot.img FAIL! Complete(Write) operation failed. All threads completed. (succeed 0 / failed 1)


Unsupport dev_type

Is camera flash actually harmful to infants or newborns?

I just got a new off-camera flash, and the instruction manual says:

Never fire the flash unit closer than 1 meter from infants.

This was a little startling to me, since one of the main reasons I bought the flash was to take photos of my newborn son.

On the other hand, knowledgeable sources on the internet seem to say otherwise:

Q: What long/short term risks are there to using camera flash in photographing a 2-month old?

A: None, shoot away. — John C Hagan III, MD, FACS, FAAO,ATD011008

Q: Can a camera flash harm an infant’s eyes?

A: No, it cannot. Actually infants have more protection from a flash than adults since they are usually not interested in being photographed and do not look right at the camera. Also, they typically have smaller pupils. This means less light reaches the retinas. — Don Bienfang, M.D.

Q: Can a camera flash harm an infant’s vision?

A: The flash of a camera, even if used to take many, many pictures of your newest family member, should not harm an infant’s vision. Although the flash seems very bright, it actually isn’t much different from normal daylight. — Leann M. Lesperance, M.D., Ph.D.

So what’s going on here? Are the makers of the flash just avoiding a lawsuit? Is this a myth? Or are the doctors just thinking about little on-camera flashes and neglecting to think about more powerful flashes?

(And if it’s NOT a myth, can I assume that bounce flash is acceptable?)

Ubuntu 18.04 on UNetbootin bootable 16GB USB Flash Drive will install on PC but not on new Laptop

I have a new, Metabox laptop with a 500GB SSD on which Windows 10 is installed and a 2TB HDD. My 4 year old PC has a 180GB SSD running Windows 10 and a 2TB HDD for storage. I originally intended installing Ubuntu on the laptop’s HDD but now believe it may be best to install it on the SSD. Both computers have good specs with regards to RAM, etc.

I have followed the advice of various Ubuntu website contributors and created a bootable USB Flash Drive using Rufus, then Universal USB Installer, then UNetbootin, all having the ability to install Ubuntu 18.04 LTS to Dual Boot with the Windows 10 O.S. installed by the laptop’s manufacturer, Metabox. I attempted to disable Secure Boot as repeatedly advised, only to find it was already disabled, obviously by the Windows 10 installer.

On every occasion, when booted from the USB Flash Drive, it has failed to run or install Ubuntu. It crashes/freezes and I have to shut it down by holding down the power button. I finally tried the current, UNetbootin version on my PC, expecting the same but it displayed a thorough tour of Ubuntu 18.04, no worries. I did not try to Install it but have no doubt it would have installed had I attempted it.

Can someone please explain how I might install Ubuntu 18.04 on my new laptop, preferably to Dual Boot with Windows 10, as it seems the problem is with my laptop and not the bootable USB Flash Drive. Thank you.

How does full disk encryption cater for overprovisoned disk space in flash devices and can this result in data leakage?

My understanding is that flash based devices such as SSDs are over-provisioned and do not advertise the additional blocks of storage available to the operating system. The over-provisioned blocks of storage is to support effective distribution of data via wear leveling.

Assuming my understanding is correct, how does full disk encryption cater for over-provisioned of storage if the additional block of storage isn’t advertised or accessible by the operating system?

If the distribution of data is limited to the drive’s controller, is there a risk of data flowing from encrypted blocks to unencrypted blocks e.g. over-provisioned storage?

Flash Player loads object/videos slow on all browsers

So i have a user who is trying to load an E-Learning course that uses Flash as a slideshow type of thing and it takes forever to load on his PC. I tried it on another PC that is in the building and it too took forever to load no matter what browser you launch the course on.

Now i tried the same website on my office PC that’s offsite elsewhere and it loaded the flash objects instantly.

The user claims that he had the same issue last time and claims it was the firewall but based on the past tickets he’s submitted, it was not. They have a Cisco ASA 5505 and the only thing that would, if any, affect it would be traffic policing but its only policing up to their total bandwidth.

I have tried:

  1. Clearing Temp with CLEANMGR.
  2. Clear Browser Cache, History, Cookies.
  3. Try IE, Chrome and Firefox (IE so far is doing way better).
  4. Double Check firewall to make sure nothing is being blocked.
  5. Ran speed test to make sure he doesnt have slow internet, currently has ~40mbps x 40mbps.
  6. Tried different user accounts.
  7. Toggle on/off HW Acceleration on Flash setings and on Browser settings.

None of this has ever made flash load fast enough compared to my office PC.

Any ideas what could be the cause and if there is a fix for this?