Forum Replies Created
If BIOS detects the drive but Windows doesn’t, the issue is likely with how the drive is set up or recognized by the operating system. The drive might be unallocated, not initialized, or using a corrupted file system that Windows can’t read. In some cases, the necessary drivers may be missing or outdated, preventing proper detection. It’s also possible that the drive is hidden or marked as offline in Disk Management. To fix this, open Disk Management to check the drive’s status. From there, you can initialize the drive, assign a drive letter, or format it if necessary.
In Disk Management:
RAW means the drive has a partition, but the file system is missing or corrupted.
Unallocated means there’s no partition on that space—it hasn’t been set up yet.
It’s safe to disable or delete the FTDI device if you don’t use it. If you do, it will stop working until reinstalled.
Deleting the Ngc folder removes your PIN and may disable fingerprint or face login. It won’t affect your password. You can still log in with your password and set up a new PIN later.
What if BIOS detects the drive but Windows doesn’t?
What’s the difference between RAW and unallocated in Disk Management?
Is it safe to delete or disable the FTDI device?
Is there any risk or consequence of deleting files from the Ngc folder? Could it affect other authentication features?
Check the trash or recycle bin in your recorder or call recording app (they usually keep deleted stuff for 30 days). If it’s not there, check Google Drive or Samsung Cloud if you had backup on. Still nothing?
Try android data recovery software, they generally work without rooting, and you can scan for just audio files. It’s actually pretty simple to use, and you might just get those recordings back.
I accidentally deleted some really important voice recordings from my Android phon, itwas a mix of personal notes and a few call recordings I really didn’t mean to lose. I’ve checked the usual places (like my file manager and apps), but no luck so far. I’m not even sure if I had backups enabled. Is there any actual way I can still get those recordings back without rooting my phone or doing something super technical?
Don’t panic yet. If the screen’s dead but the phone still powers on, try connecting it to a PC (AutoPlay might pop up and let you grab the photos).
If touch is busted but USB debugging wasn’t on, you can use an OTG cable and a mouse to navigate.
Also, check Google Drive or Google Photos..they often have backups running in the background. If your pics were on the SD card, just plug it into a new phone or a card reader.
In Worst case, you’ll need an android data recovery software or take it to a pro, but definitely try the simple stuff first.
A sudden battery drain on your iPhone may be caused by background apps, a recent iOS update, or some type of settings has changed. First, check Settings > Battery to see which apps are consuming the most power. Disable Background App Refresh and Location Services for non-essential apps. Reduce screen brightness and turn off Bluetooth or Wi-Fi when not needed.
Next, restart the phone and see if the issue continues.
My Android phone fell and the screen’s completely shattered. I can’t tap anything, the display is either black or glitchy, and I’m freaking out because I had all my family photos on it. Is there any way I can still recover those photos without going straight to some expensive data recovery service?
Check the Trash in the Files by Google app (if it had file access before deletion). It stores stuff for 30 days. If it’s not there, stop using your phone to avoid overwriting data. You’ll need to try an android data recovery software that scans internal storage. No root needed for some of them, just follow the steps carefully. And yeah, backing up to cloud next time saves a lot of stress
The RAID 10 array on your MSI PRO X670 motherboard became inaccessible after a single drive failed. Even though three drives are still online, the system doesn’t detect the array or show any partitions, not even after loading the correct AMD RAID drivers.
This could be due to RAID metadata corruption, a bad connection to the failed drive, or BIOS changes. Do not rebuild or initialize the array — that can wipe the data.
Start by checking the physical connection of the removed drive. Reseat cables or swap ports. Then enter the AMD RAID BIOS (RAIDXpert2) and check if the array can be imported or viewed without initializing.
If that fails, try using a Linux live USB with mdadm or dmraid to assemble and access the array. If Linux doesn’t detect it, use RAID recovery software like Stellar Data Recovery Technician, R-Studio or UFS Explorer to scan and recover the data.
Once the data is safe, replace the failed drive and rebuild the array. For future reliability, consider using software RAID or a dedicated RAID card instead of motherboard-based RAID.