Ro2rw issues

General
1

When you do ro2 RW it saves in user a backup of the super and then you’re supposed to flash the super so I did that and now I’m having issues deleting the backup it’s about 5 GB of files and using up most of my space if anyone has a fix please let me know
@TripleU @FliphoneBochur
Thanks

2

factory reset

3

And ro2rw will stay?

4

yes

5

Any other alternative? It will be very hard for me to reinstall all my apps and restore all my data…

6

The RO2RW new depleted super is somewhere in data/local/tmp.
the exact path is said in the script when it says “the script is now paused”.
delete it. It’s a decompiled super…

7

Nah before I ask the question I tried chatgpt and it just wasn’t working I finally got it… Through termux…
Here’s what chatgpt told me we did during the process I do not know what it means but just in case you’re curious

Absolutely! Based on everything we’ve seen, the main issue was a corrupted folder entry in Fuse-managed storage that refused to be deleted due to broken metadata. The "Math result not representable" error usually happens when the filesystem can’t properly reference or calculate the size/location of a file, often due to corruption or incorrect attribute handling.

Key Problems You Faced:

  1. Fuse restrictions – /storage/emulated/0/ is managed by Fuse, making direct deletion harder.
  2. Root ownership conflicts – The folder was owned by root:media_rw, preventing normal access.
  3. SELinux enforcement – Likely blocked some of your deletion attempts until switched to permissive mode.
  4. Filesystem corruption – The "Math result not representable" error signals corrupted file metadata.
  5. Persistent shell lock – The shell process (sh) was stuck inside the folder, preventing deletion.
  6. Unlinked but undead files – Files were removed but still referenced due to Fuse caching.

How We Fixed It:

  • Exited the directory and killed locking processes (sh was holding onto it).
  • Tried direct deletion via /mnt/pass_through/0/emulated/.
  • Used find to remove files first, then wiped the empty folder.
  • Forced media refresh (am broadcast …) to clear cached references.
  • Attempted low-level removal (unlink and dd to zero-out files).
  • Recovery mode (e2fsck) helped clean up residual corruption.