Edit: I am not promoting this, nor am I seeking traffic—I couldn't care less about such things. I simply wanted to offer a friendly reminder to those who might be rushing to use this based on just one or two recommendations, without realizing the potential security risks involved. I sincerely apologize for any misunderstandings that may have arisen from this💀

I used machine translation, so the phrasing might be a bit awkward or contain errors

My view is that while the enhancements offered by TrollStore ReMod are certainly appealing, it is not FOSS (Free and Open Source Software). This means that, barring reverse engineering, you can never know for certain what operations it is performing in the background. Given that both the applications installed via TrollStore and the tool itself can obtain root privileges, this factor alone makes it impossible to place full trust in it; even if it is actually safe, relying on it requires placing blind trust in the developer—a trust that offers no guarantee of absolute security. After all, you certainly wouldn't want to grant root privileges to a closed-source tool, would you?

I am not saying that closed-source software is bad—FOSS carries its own risks, too—but in most cases, closed-source software is indeed not as trustworthy as FOSS (due to issues regarding code transparency).

Hi everyone, I’d like to know if unlocking the bootloader—or relocking it using avb_custom_key—results in any features being crippled or broken TEE on Nothing devices. Is their implementation of avb_custom_key actually functional?

I plan to get a Phone (3) next year; I intend to relock the bootloader and then use the patch mode in TEESimulator-RS to spoof Play Integrity, aiming to achieve at least "Device" integrity status :D

Hi fellow jailbreakers on iOS versions older than 17! I’ve found a workaround to solve the unsupported shortcut issue. Hopefully, this can help out other poor souls like me :)

You don't strictly have to follow the steps below—you can also just download my shortcut and script and tweak them yourself.

Steps:

1. Get AutoTouch: Install AutoTouch. Then, either download the script I’ve uploaded or record one yourself. (The script just needs to open AltStore, switch to the "My Apps" tab, and hit "Refresh"). Note: If you use my script, make sure to move it to AutoTouch's default directory, or you'll need to modify the URL in the shortcut later.
2. Enable WebServer: Go to AutoTouch Settings > Turn on "WebServer".
3. Install Powercuts: This is highly recommended if you use a lock screen passcode and want your device to auto-resign your apps in the middle of the night.
4. Enable On-Device Signing: If you want to resign directly on your device without connecting to a computer, install AltDaemon or emp0ry/AltDaemonModern.
5. Shortcut & Automation Setup: Here’s what the basic setup looks like:
   • Automation:
     • Choose your trigger time (e.g., time of day).
     • Turn on Wi-Fi (if you usually turn your network off).
     • Run "Shortcut A".
   • Shortcut A:
     • Action: Get Contents of URL
     • URL: "http://127.0.0.1:8080/control/start_playing?path=Records/refresh.lua"
   • Done!

Important Notes:

1. Passcode & Unlocking: Since this method requires physically opening the app, if you have a passcode but want the script to run hands-free without touching the device, install Powercuts. Add "Unlock Device" to your automation and enter your passcode (please be careful not to leak your passcode!).
2. Package Name Tweaks: My .lua script is set to open the stable version of AltStore. If you're using the beta version or SideStore, you will need to modify the package name inside the script.
3. Loading Delay: My .lua script includes a one-second pause right after opening AltStore to prevent the script from running before the app fully loads.
4. Background App Refresh: You must allow the Shortcuts app to use Background App Refresh.
5. Disclaimer: I am not responsible for any data loss or damage! I am simply sharing my own personal workaround!
6. My English is poor, so I used an LLM for the translation; please bear with me.
7. My train of thought was a bit scattered while I was writing this, so there might be some omissions or errors—sorry!💀

shortcut: https://www.icloud.com/shortcuts/217ff1876ef84136954450c143d033c8

lua: https://gofile.io/d/lSLopsma

Hi everyone,

I recently installed LiveContainer 2 on my jailbroken iPhone X (running iOS 16.7.15, so no CoreTrust for me—TrollStore Lite in a jailbroken environment is my only lifeline).

To clarify, the IPA wasn't downloaded from an external site; I generated and shared it directly through the main LiveContainer app's built-in installation prompt for LiveContainer 2, and then installed that exported IPA via TrollStore Lite.

Here is the cursed part: ReProvision Reborn somehow picked up LiveContainer 2 and marked it as a target that needs to be re-signed.

I'm not even worried about standard expiration or "revokes" right now. What keeps me up at night is: If ReProvision actually forces a re-sign on this thing when the timer hits, what kind of unholy, reality-breaking magical bugs are going to happen?

How does an app installed via TrollStore Lite in a jailbroken state even trigger ReProvision's radar like this? Has anyone else fallen victim to this absolute witchcraft? Should I be screaming, or is there a way to exorcise it from ReProvision before it shatters the fabric of space-time?

Thanks!

Hi, I’m currently using the Windows version of Helium (0.15.2.1), and I’ve been running into an issue where Google’s servers seem to be acting up—repeatedly flagging me as a bot and logging me out of my account. This has been happening for several days now, multiple times a day. I’m not necessarily looking for a fix; I just wanted to see what everyone else thinks about this.
Since my English is poor, this post was translated using Google Translate.

Note: I've already tried turning off fingerprint tracking protection, but that clearly isn't the issue.

Hi everyone, I'm curious what you all use to complement uBOL. I was wondering, what do you think of using it alongside the AdGuard Extra (userscript) + Unwall combination?

Note: My English isn't great, so this post was translated by an LLM.

By the way, please stick to the question and don't suggest other alternatives—for the sake of this discussion, let's assume uBOL is strictly the only primary blocker being used.

Hi everyone / devs,

I recently switched from the standard Shizuku (thedjchi) to thejaustin/ShizukuPlus. The service is running fine and already authorized, but Morphe Manager still fails to detect it.

I haven't checked the source code, but I suspect the app might be looking for a hardcoded package name. Would it be possible to make the Shizuku detection logic more dynamic (or expand it to support popular forks like ShizukuPlus)?

Thanks in advance!

BTW,Since my English isn't great, this post was translated with the help of an LLM.💀

Hi everyone, this is my first time posting here. Since my English isn't great, this post was translated by an LLM.

I'm a rooting newbie and I'm currently stuck on a very frustrating issue with my Samsung Galaxy Tab A 8.0 (SM-T295).

My Goal: Root the device using Magisk.

What I've done so far:

1. Confirmed that the Bootloader is fully unlocked.
2. Samsung USB drivers are properly installed on my Windows 11 PC.
3. Because this tablet only has 2GB/3GB of RAM, I was worried it would run out of memory (OOM) if I let Magisk patch the entire multi-gigabyte AP.tar file directly on the device.
4. Instead, I extracted boot.img and vbmeta.img from the stock firmware.
5. I transferred boot.img to the tablet and successfully patched it via the Magisk app.
6. I used vbmeta-disable-verification to process the vbmeta.img.
7. I moved both patched/modified .img files back, compressed them into .lz4 format, and replaced the original files inside the extracted stock AP folder.
8. Finally, I re-tarred the whole folder into a new custom_AP.tar using 7-Zip on Windows (Tar format, Store/no compression).

I manually booted the tablet into Download Mode (the screen text/info displays perfectly fine, and I confirmed the stock firmware package is 100% healthy).

However, whenever I try to flash my custom_AP.tar using either stock Odin (v3.13.1) or SamFw Tool, it instantly fails.

Here is the exact log from stock Odin:

<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> FAIL! LZ4 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)

(Note: I also tried using Heimdall on both Linux and Windows as an alternative, but Heimdall completely fails to detect or recognize the device, even though adb works fine when booted.)

It seems Odin is rejecting my repacked .lz4 files during the file analysis phase. Did I compress the .img files into .lz4 using the wrong parameters or tool? What is the correct way to compress these images back into an LZ4 format that older Odin engines will accept?

Any advice would be greatly appreciated. Thank you!