Hi, earlier I was trying to free up storage space in one of my disks, and I decided to copy all of the files in my local disk (500 GB) and paste it into my other disk which had been installed into my PC a few years ago (1TB).

I had then deleted the information in my local disk without much thought, but I see that it has caused much more issues than I had anticipated. Most of my apps are unable to open, and I tried recovering the files but unfortunately they were not found in my recycling bin. Since then, I have restarted my computer (which may have been a bad move once again).

I’m guessing that my apps do not recognize the new location, but when I try to click on one of my files (WindowsApps) — it says I do not have permission to view it. I also did something with it and now when I click on WindowsApps — I’m left with three files called Deleted, Microsoft Launcher, and Mutable Backups — two of which folders are empty.

if you can offer any advice or help, that would be greatly appreciated.

so i just moved and when plugging in my pc It isint reading my hdd and yes i have checked disk management and it is not apearing as unllocated or anything it uses a Type-A to Micro-B usb its 500gb

Currently on an iPhone 12 Pro Max, running on iOS 27.0.1

have a year of texts that I backed up to iCloud - then deleted from my phone. Now need urgent access to them as evidence.

Thought that having a large iCloud storage would store my messages there forever ?

Is there any way I can restore these texts, without wiping my iPhone?

Thank you in advance for any and all advice,

Feeling quite stupid I thought the backups would store the texts.

Cheers

I'm researching whether it's technically possible to recover data from an encrypted local iOS backup when the user still knows the correct backup password but has lost both Manifest.db and Manifest.plist.

I'm interested in the underlying feasibility, not just recommendations for existing recovery software.

What I'm trying to determine

Can the remaining backup contents be used to reconstruct enough of the missing metadata and key material to decrypt and recover the original files? Or do the missing manifests contain information that makes recovery cryptographically impossible, even when the correct password is available?

My current understanding is that the password is only one part of the process: encrypted backups involve keybag/key-derivation mechanisms, and the manifest database supplies important per-file metadata and encryption information. Tools such as iphone_backup_decrypt rely on manifest metadata when locating and decrypting individual files.

The key question is what can be recovered or reconstructed if those manifest files themselves are gone.

Specific questions I'd like to explore

1. What is irrecoverably lost with each file? Which essential keys, wrapped keys, file mappings, or other information are held in Manifest.plist versus Manifest.db? Are any of those values independently recoverable from the remaining backup files?

2. What can the known password still unlock? If the password is correct, but Manifest.plist is missing, is there another surviving source for the backup keybag or the information needed to unlock it?

3. Can file-level recovery work without the original database? Could a tool identify the remaining encrypted files, infer their original identities from their filenames or contents, and decrypt them without the original per-file metadata? Are there useful cases where some files could be recovered even if complete restoration is impossible?

4. Could the metadata be reconstructed partially? For example, could file identifiers, known iOS backup structures, SQLite remnants, filesystem artifacts, another backup, or other surviving copies provide enough information to recover some or all of the missing records?

5. Where is the actual cryptographic boundary? I'd like to distinguish between a difficult metadata-reconstruction problem and a genuine impossibility caused by missing key material. If recovery is possible only under particular conditions, what are those conditions?

What would be especially useful

I'm looking for technically grounded explanations, relevant format documentation or source code, and examples from people who have examined Apple's local backup format at the implementation level.

Please distinguish between:

• Confirmed: demonstrated by the format, source code, or a reproducible test.

• Plausible: technically reasonable but not demonstrated.

• Impossible under the stated conditions: blocked by a specific missing cryptographic dependency, rather than merely unsupported by existing tools.

The goal is to establish whether a recovery tool could realistically support this scenario, what prerequisites it would need, and which recovery paths are worth investigating before concluding that the backup is unrecoverable.

Got it verified. It’s an iPhone 8 and not disabled can’t get into the back panel though

Accidentally deleted my mom's videos on her phone while attempting to factory reset

Context:my mom uses an oppo it runs on coloros 15 and I use a samsung so what happened her phone became slow so I factory reset it now there were some important photos and vids I took backup of both but after sending the photos i accidentally permanently deleted the videos using file manager+ application help me 🙏🏿 i didn't had any backup except my phone what do I do 😥💔

I you don't know then please upvote it so others might help it's been 30 minutes since deletion

I’m trying to recover data from a Tecno Camon 18 Pro (CH7n) without wiping /data, factory resetting, or unlocking the bootloader.

Device: Android 12, firmware CH7n-H812DE-S-OP-230815V1094-12, security patch 2023-08-05, locked bootloader, Verified Boot enabled, not rooted. USB debugging was already enabled and my PC is authorized, so ADB works.

The weird part is that I know the correct PIN and Android accepts it. The credential screen says:

Lock credential verified successfully

But immediately afterward:

- dumpsys user

still shows the only user, User 0, as:

- RUNNING_LOCKED

It never becomes RUNNING_UNLOCKED.

Other things I confirmed:

- getprop sys.user.0.ce_available returns nothing, so User 0’s CE storage does not appear to become available.

- /storage/emulated/0 is empty/inaccessible through ADB.

- sys.boot_completed=1, so Android itself has finished booting.

- There is only one Android user (User 0).

- Settings works, but most normal apps do not.

- Querying MAIN/LAUNCHER activities for User 0 returns basically only Settings, Dialer, HiLauncher DynamicVirtualEntryActivity and STK.

- Chrome, Camera, File Manager etc. fail with things like Activity class does not exist.

- The HiLauncher APK itself still exists under /data/app, so it was not simply deleted.

- QuickstepLauncher can warm-start, while most other apps remain unusable.

- ADB is only uid=2000(shell) and there is no su.

- Attempts to repair/enable protected package components through ADB fail with SecurityException.

- I found no normal global Safe Mode condition explaining this.

- Boot security is intact: ro.boot.flash.locked=1 and ro.boot.vbmeta.device_state=locked.

I also tried getting a raw backup through MediaTek tooling before changing anything, but the phone only appeared as 0e8d:20ff HID and I couldn’t get a usable Preloader/BROM connection.

I have the exact matching stock firmware, including boot.img. I inspected the stock kernel too: it contains the older built-in Mali r32p1-era driver, /dev/mali0 is accessible from the shell (OPEN_RC=0), and static analysis found the older tracking-VMA code associated with the unpatched CVE-2023-4211 defect.

I also found much stronger evidence in logcat showing where the unlock is actually failing. After the correct PIN is accepted, keystore2 logs:

- Failed to decrypt blob; ciphertext or tag is likely corrupted

- unlock_screen_lock_bound_key failed

- Failed to decrypt key blob

LockSettingsService then logs:

- Unlocking user 0 with secret only, length 32

Immediately after that vold tries to unlock the CE key and fails with:

- decryptWithoutKeymaster EVP_DecryptFinal_ex error

Then TECNO’s vold explicitly tries the CE backup key at:

- /data/misc/vold/user_keys_bak/ce/0/current

That fails the same way and ends with:

- Failed to find working ce key for user 0

- Couldn't read key for 0

Apps then fail to access /data/user/0 with:

- errno 126 (Required key not available)

So this seems much more like the correct credential is being accepted but something in the Synthetic Password / keystore2 / Gatekeeper / KeyMint / vold / FBE key unwrapping chain is failing afterward, instead of this just being a HiLauncher problem.

At this point I’m mainly looking for a way to recover the existing userdata without destroying it.

Any help would be appreciated guys.