Fitness Foundry (Coach Julio)
@Fitnessfoundry@mas.to  ·  activity timestamp last month

Just hit 1K followers on Instagram—grateful. 🙏🏽

This milestone feels extra special given the path I’ve walked – from experiencing #homelessness to becoming a #smallbusiness owner. My commitment to advocating for #health equity, #mentalhealth, and #recovery has only grown stronger.

Your support helps amplify voices that need to be heard and enables me to continue volunteering, both locally and in 🇺🇦 #Ukraine.

Here’s my link: http://www.instagram.com/fitnessfoundryusa

Let’s keep making a difference together!
Fitness Foundry (Coach Julio)
@Fitnessfoundry@mas.to  ·  activity timestamp 2 months ago

💟 Mental Health Matters.

I live with clinical depression. I’ve lost a family member to suicide.
I know how real—and how silent—that pain can be. But help is available.

If you’re struggling in any way, please bookmark or share these lifelines.
You never know who might need them.

You are worth it.
You are not alone.

#MentalHealth #depression#SuicidePrevention#LGBTQ#Veterans#CommunitySupport #publichealth #latinos#SelfLove #recovery #addiction#thetrevorproject#Boston
Dendrobatus Azureus
@Dendrobatus_Azureus@mastodon.bsd.cafe  ·  activity timestamp 3 months ago

Do you make backups? Do you run ZFS? Do you use Bacula? Do you use dd?

Your method is important for you. What's also important is testing how a restore works.

I lost a partition less than 30 minutes ago. I have a simple tgz backup of the important data on another drive, not an SSD, no a HDD.

I lost zero bytes of data.

Please make sure your backup and restore systems work.

When your recovery tool says the partition is lost, only your backup will save you.

Mine did

#OpenSource#Backup#Restore#Data#Recovery

The image shows a terminal window displaying the output of the TestDisk 7.1 data recovery utility. The utility is running on a Linux system The top of the window contains the utility's name, version, and copyright information, along with the author's email address and website. Below this, the utility is analyzing a hard disk identified as /dev/sdb, which is reported to have a capacity of 250 GB, but the utility suggests it might be 232 GB, 323 GB, or 300 GiB. The utility notes that the hard disk size seems too small and suggests checking the hard disk size, HD jumper settings, and BIOS detection. The output lists three partitions that cannot be recovered, all labeled as "MS Data" and formatted as NTFS with a block size of 4096. The partitions are shown with their start and end sectors, and their sizes in sectors. The first partition starts at sector 488392703 and ends at sector 630994935, with a size of 142602233 sectors. The second partition starts at sector 488396792 and ends at sector 631003120, with a size of 142606329 sectors. The third partition starts at sector 488396799 and ends at sector 631003127, with a size of 142606329 sectors. The total size of these partitions is 73 GB, but the utility notes that it is 67 GiB. At the bottom of the window, there is a prompt asking the user to "Continue," indicating that the user can proceed with the recovery process or exit the utility. Ovis2-8B 🌱 Energy used: 0.410 Wh
The image shows a terminal window displaying the output of the TestDisk 7.1 data recovery utility. The utility is running on a Linux system The top of the window contains the utility's name, version, and copyright information, along with the author's email address and website. Below this, the utility is analyzing a hard disk identified as /dev/sdb, which is reported to have a capacity of 250 GB, but the utility suggests it might be 232 GB, 323 GB, or 300 GiB. The utility notes that the hard disk size seems too small and suggests checking the hard disk size, HD jumper settings, and BIOS detection. The output lists three partitions that cannot be recovered, all labeled as "MS Data" and formatted as NTFS with a block size of 4096. The partitions are shown with their start and end sectors, and their sizes in sectors. The first partition starts at sector 488392703 and ends at sector 630994935, with a size of 142602233 sectors. The second partition starts at sector 488396792 and ends at sector 631003120, with a size of 142606329 sectors. The third partition starts at sector 488396799 and ends at sector 631003127, with a size of 142606329 sectors. The total size of these partitions is 73 GB, but the utility notes that it is 67 GiB. At the bottom of the window, there is a prompt asking the user to "Continue," indicating that the user can proceed with the recovery process or exit the utility. Ovis2-8B 🌱 Energy used: 0.410 Wh
The image shows a terminal window displaying the output of the TestDisk 7.1 data recovery utility. The utility is running on a Linux system The top of the window contains the utility's name, version, and copyright information, along with the author's email address and website. Below this, the utility is analyzing a hard disk identified as /dev/sdb, which is reported to have a capacity of 250 GB, but the utility suggests it might be 232 GB, 323 GB, or 300 GiB. The utility notes that the hard disk size seems too small and suggests checking the hard disk size, HD jumper settings, and BIOS detection. The output lists three partitions that cannot be recovered, all labeled as "MS Data" and formatted as NTFS with a block size of 4096. The partitions are shown with their start and end sectors, and their sizes in sectors. The first partition starts at sector 488392703 and ends at sector 630994935, with a size of 142602233 sectors. The second partition starts at sector 488396792 and ends at sector 631003120, with a size of 142606329 sectors. The third partition starts at sector 488396799 and ends at sector 631003127, with a size of 142606329 sectors. The total size of these partitions is 73 GB, but the utility notes that it is 67 GiB. At the bottom of the window, there is a prompt asking the user to "Continue," indicating that the user can proceed with the recovery process or exit the utility. Ovis2-8B 🌱 Energy used: 0.410 Wh
Felix Palmen :freebsd: :c64:
@zirias@mastodon.bsd.cafe  ·  activity timestamp 3 months ago

The new #Xiaomi phone with #HyperOS2 is now fully #rooted, with #Magisk installed plus some modules, including a de-bloater that, if I understand that correctly, gets rid of system apps using filesystem overlays (so, they're still there in the system partition, but really unaccessible on a very low layer). The other modules are there for fixing integrity checks, I got google wallet, paypal and my bank's app to work flawlessly. 🥳

Now it should be possible to install some linux dist in a chroot, will probably test that soon.

There were quite a few issues on the way, e.g. a weird location of the init-boot that needs patching to install magisk: a cpio archive inside vendor-boot, unsupported by vanilla magisk, so I had to patch the magisk app first to move on 🤯. Getting magisk installed and the necessary tweaks in place for certain apps to work again took me half a day. Well, the phone model isn't the most widespread one, so finding infos took some time.

And there's still the same general issue with #android #modding community that I already observed 15 years ago, although back then, things were generally simpler: It seems most of the time, people only share some step-by-step instructions without ANY explanation, and people are also only looking for that. It's weird, you see forum posts from people doing the dumbest things by varying these instructions if they don't work for them, because they have no background knowledge whatsoever. What's even worse now, people started putting crappy videos on youtube and tiktok. Don't ever watch any of them, it's a pure waste of time. Instead, work through all the stuff on XDA, it's also full of that pointless "do that, then do that, type foo, click here" nonsense, but occasionally you will find the background info you need to understand what's going on and how to fix your own issues. 🤪
Felix Palmen :freebsd: :c64:
@zirias@mastodon.bsd.cafe replied  ·  activity timestamp 3 months ago

What I'm still missing is a custom #recovery that can actually do any useful stuff (especially full #backup).

My device has recovery as a #ramdisk in vendor_boot, and there are some prebuilt vendor_boot images with #twrp around, which I don't want to use directly because there's also an init-boot ramdisk in there that needs patching for root with #magisk ... and as far as I understood now, these ramdisks are userland only, using the shared #kernel from the boot partition, so it's unlikely a recovery built for #HyperOS1 (#Android 14, #Linux 5) will work with #HyperOS2 (Android 15, Linux 6).

What I did try nevertheless was modifying my vendor_boot using Magisk's #magiskboot utility, replacing ONLY the recovery ramdisk. It resulted in #bootloop trying to boot the normal system, so there seems to be something I still don't understand (I thought this ramdisk would only ever be loaded when booting to recovery).

For now, I'll live with the useless stock #Xiaomi recovery. Attempting to do my own build of twrp or orangefox really is too much hassle 🙈