1
62
submitted 1 day ago by xelar@lemmy.ml to c/technology@lemmy.ml

Ben Werdmuller, a tech leader at ProPublica, discusses the trust crisis in Meta's Threads app after his comment about the Internet Archive's legal issues unexpectedly attracted a hostile audience. He was surprised by accusations of engagement farming, prompting him to question the assumptions behind such claims. Werdmuller discovered that Meta has been paying certain creators up to $5,000 for viral posts, leading to a climate where all content is viewed with suspicion.

2
28
3
3
submitted 21 hours ago by yogthos@lemmy.ml to c/technology@lemmy.ml
4
12
submitted 1 day ago* (last edited 1 day ago) by yogthos@lemmy.ml to c/technology@lemmy.ml
5
-4

I'm looking for a way to dump raw data from an entire phone or at least the sda block to a PC, using a method other than adb pull.

When I run adb pull /dev/block/sda sdaDump.img, it creates a dump file. To find what I need, I have to search through this raw data using a Hex Editor. If the dump comes from a fully functioning phone, I can usually find what I’m looking for because all the data is still intact.

However, I accidentally wiped the metadata partition on my phone, so the decryption keys/files are gone. Now, because of that, some folders appear empty when checked with TWRP's File Manager, even though the actual files are still there.

If I create a dump now, the raw data in the file won't be the same as when the metadata was present, and those folders weren't showing as empty.

Running adb pull /dev/block/sda sdaDump.img now results in a dump where the Hex Editor shows zeroes (no data) where these files should be.

Is there any alternative method to create a raw data dump of the sda block or entire phone storage, that will capture that data as it is (not empty folders, but the data in them), even if it's encrypted?

I don't want to create the raw data dump onto the phone storage and then transfer it to a PC, but something that works like adb pull, in the sense that it pulls the data from the phone directly onto a PC.

Thanks a lot in advance to everyone!

6
29
submitted 2 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml
7
336
submitted 2 days ago by moe90@feddit.nl to c/technology@lemmy.ml
8
23
submitted 2 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml
9
0

cross-posted from: https://lemmygrad.ml/post/5599990

A new browser with a "new engine" apparently ("that being chromium, gecko and webkit" according to one comment).

Your overall thoughts on it? The video is less than 20 minutes so far. Looks 'ight so far too, afaik. But I'm no expert.

10
14

I need to ask a small favor from the good people of Lemmy.ml Community.

In short, I accidentally wiped the metadata partition on my Poco F3 and now I can't boot into the OS and access my data. I have a lot of pictures, videos and other stuff that I would hate to lose, because of a mistake. But all that is still on the phone, I just can't boot the phone to access it.

Thankfully, there is a way to fix this by creating a full backup of the phone with adb, then using a HEX Editor to manually look through that gigantic file and try to find the files that were in that metadata partition.

A huge thanks to bluet33th, a user from XDA Forums, without whom I would be helpless and couldn't do any of this. It might be a bit complicated and manual process, but it is possible. He explained everything in great detail here, so check it out, especially if you are facing the same problem, this will help you tremendously: https://xdaforums.com/t/how-to-recover-data-if-metadata-partition-was-deleted.4686789/

In order to find these files and put them back where they belong, I need your help, because I have to know their names, exact sizes and at least part of their content, so that I can search for it. Because I'm searching for a specific text in a text file that is 128 GB in size.

I have already tried this on another Xiaomi phone, to make sure this procedure works on Xiaomi phones and it does, but that phone had HyperOS with Android 14 and since every phone and android version is probably different, in order to be sure, I need this information specifically for Poco F3 with Android 13.

It doesn't take long, but if you don't have the time to look inside your metadata partition and tell me which files are inside of that partition and their sizes in bytes, you can just make a backup of the metadata partition and sent it to me, and I'll do the rest of the work.

Here are the steps on how to create a backup:

  1. Turn on your phone and boot into TWRP, then connect your phone to a PC, type cmd inside Windows search and run cmd, then position cmd into your platform-tools folder (if you flashed your ROM, you should already have the necessary drivers installed for the next steps to work). For example, if your platform-tools folder on Windows is inside C:\platform-tools, all you need to type into cmd is: cd C:\platform-tools

You can also just go inside your platform-tools folder and type cmd in the address bar and the cmd will start already positioned inside that folder.

  1. Then type adb devices and you should see your device, if you do, that means that all the drivers are successfully installed and your phone is detected.

  1. Type adb pull /dev/block/by-name/metadata

  1. After that, you should see a file named metadata inside C:\platform-tools. That is the file that I'm looking for and as you can see, it takes just a few minutes to get it.

You can skip the next steps (5 and 6), but I'll explain them, just in case someone wants to extract these files for themselves, so that you have them in case something like this happens to you. Of course, you can also proceed to extract the files and tell me their names and sizes.

Here is what you need to do:

  1. Extract the content of the metadata file, you can use a software like 7-Zip. Go inside that extracted folder, then into vold > metadata_encryption > key

  2. Inside of that key folder, you should see a few files. These are the important files and save them somewhere safe in case you ever need them. Since I don't have them anymore, in order to recreate them, I need to know their exact names and sizes in bytes. You can check the size of every individual file by right clicking on the file and choosing Properties. Then look under Size, not Size on disk, and in parenthesis, you should see the size in bytes.

Please, if you could check the size of every file and write down which file has what size. I would really appreciate it.

I'm specifically looking for someone who has a Poco F3 with Android 13 and MIUI, because I'm not sure if HyperOS changed something, so maybe the number of files or their size is different. But feel free to post the information even if you have HyperOS, but please mention that, so that I am aware of it.

Thanks a lot for your help, it really means a great deal.

11
177
submitted 3 days ago by schizoidman@lemm.ee to c/technology@lemmy.ml
12
70
submitted 3 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml
13
49
Android 15 is released to AOSP (android-developers.googleblog.com)
14
48
submitted 3 days ago by schizoidman@lemm.ee to c/technology@lemmy.ml
15
13
submitted 2 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml
16
11
submitted 2 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml
17
47
submitted 4 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml
18
45
submitted 4 days ago by schizoidman@lemm.ee to c/technology@lemmy.ml
19
240
20
9
submitted 4 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml
21
17
submitted 4 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml
22
29
submitted 5 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml
23
14
submitted 6 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml

This demonstrates the waning relevance of Western influence upon the world's economic landscape. The success of top-tier technology firms is now attainable without necessitating involvement within the confines of the United States marketplace.

24
72
submitted 1 week ago by yogthos@lemmy.ml to c/technology@lemmy.ml
25
5
submitted 1 week ago by yogthos@lemmy.ml to c/technology@lemmy.ml
view more: next ›

Technology

34356 readers
125 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.


Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.


Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 5 years ago
MODERATORS