• kratoz29@lemm.ee
    link
    fedilink
    English
    arrow-up
    5
    ·
    3 days ago

    And there is me using a 2019 (dying) device which I heat up with a termux command to get it back in working state 😁

    For the curious the device is a Poco F2 Pro, known for IMEI and charging flex issues, the termux command I use to bring alive my IMEI, Wifi and USB data transfers is:

    for i in $(seq 1 32); do sh -c ‘while :; do a=$((a+1)); done’ & done; for i in $(seq 1 32); do yes > /dev/null & done

    This paired with fast charge will heat the SOC and make it work like the 1st day without an issue lol.

      • kratoz29@lemm.ee
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 day ago

        Yep, loops to heat up the CPU, in combination with fast charge to make it hot quicker.

        CPU loses contact with the board or something like that making it not able to read modem, efs, and whatever is the responsible to transmit data through the USB port (charging works normally, even fast charge), it needs a reflow or reballing to fix this for good, but technicians nearby are… Simply put, thieves lmao.

        So I’d rather keep doing this until the phone dies (the workaround makes it work for an undefined amount of time, which can be hours, days or almost a week) or change the motherboard myself.

        I got the idea along with ChatGPT when a user in telegram told me that he got USB data transfers working again (in order to escape from MIUI once again) by heating up the SOC with a hairdryer, yes, that worked for me too to fix all above, thus I decided to create a software solution in the meantime 😅

        • squaresinger@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          15 hours ago

          I hope you already got all your data off the device. While this might work in the short term, this will very likely fail very soon.

          • kratoz29@lemm.ee
            link
            fedilink
            English
            arrow-up
            2
            ·
            15 hours ago

            I have been like this for a month with this workaround, and yeah, I backup with Google backups and rooted Swiftbackup nightly 👍🏻

              • kratoz29@lemm.ee
                link
                fedilink
                English
                arrow-up
                1
                ·
                2 hours ago

                Me too, sometimes I feel it is a software issue, but if that was it wouldn’t happen in all the ROMs I tried, on top of that a restore of efs and modem partitions should be enough (at least for IMEI and Wifi), but sadly it isn’t.

                • squaresinger@lemmy.world
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  2 hours ago

                  On some devices pretty much all custom roms are built on the same kernel published by the device manufacturer. So if there’s a bug in that (e.g. with power saving options) that could actually lead to symptoms like yours.

                  • kratoz29@lemm.ee
                    link
                    fedilink
                    English
                    arrow-up
                    1
                    ·
                    12 minutes ago

                    Yeah, but it happens with different kernels as well, it happened to me in the stock ROM actually, moved to a custom ROM and it didn’t fix it (I needed to heat it up first in order to flash it with adb sideload 😂).

                    Also, not everyone who shares these newer A15 ROMs suffer from this, this is a very documented hardware issue I am afraid, but I am totally with you that this workaround shouldn’t make it last for something more than a mere hours perhaps.