Find answers, ask questions, and connect with our <br>community around the world.

New Forum Page with Discussions › Forums › Ask Technical Questions about Pytes Products › V5α bricked after bootloader update – S/N 741800000087872

  • V5α bricked after bootloader update – S/N 741800000087872

    Posted by erik on July 20, 2026 at 6:52 pm

    Hello,

    I just received a new Pytes V5α battery (Serial Number: 741800000087872 – manufactured March 2026).

    I tried to update the bootloader as indicated in the documentation in order to have the same level of boot loader/firmware as my 2 other Pytes V5a. By the way I succeed to update my 2 other Batteries without and issues

    But with the new one since then, the battery won’t boot at all:

    • No LEDs light up
    • No response

    I have tried multiple times:

    • “Wake Battery / Recover” in BMSQt with correct timing (Power ON + red SW button)
    • “DLG” command in HyperTerminal

    Nothing works.

    Could you please send me the recovery files (compatible bootloader + firmware) and detailed instructions to revive this battery?

    I have attached a photo of the battery label.

    Thank you very much for your help.

    furese replied 2 months ago 2 Members · 5 Replies
  • 5 Replies
  • erik

    Member
    July 21, 2026 at 3:04 pm

    <strong data-start=”50″ data-end=”87″>Important additional information:<br data-start=”87″ data-end=”90″>The bootloader file I attempted to install was:<br data-start=”139″ data-end=”142″><strong data-start=”144″ data-end=”178″>bootloaderv1.14_GD32F307xC.bin

    Since attempting to install this bootloader, the battery no longer starts or responds.

    I am really desperate and very worried that I may have permanently damaged the BMS on my brand-new V5a battery. 😟<br data-start=”388″ data-end=”391″>I sincerely hope that the BMS can be recovered using a recovery procedure or by reflashing the correct bootloader/firmware.

    Any help or instructions to recover the battery would be greatly appreciated.

    Many thanks for your help.<br data-start=”629″ data-end=”632″>Erik

    • erik

      Member
      July 22, 2026 at 1:49 am

      An important information I guess, is that during the bootloader installation the progress stopped at approximately 33%. After waiting for some times the update failed with an error. Unfortunately I do not remember the exact error message.

      Can anyone please help me to recover my battery. Any advice or recovery procedure would be greatly appreciated.

      Thank ou very much for your help

      • erik

        Member
        July 23, 2026 at 4:17 pm

        Hi,

        I understand that I may have made a mistake, but I really need to know what the next step is now.

        I have already provided all the details and tests, but I have not received any further response.

        Could someone from Pytes please tell me what I should do next?

        If the BMS cannot be recovered, please let me know how I can proceed with a BMS board replacement.

        I would really appreciate a clear answer and some support.

        Thank you.
        Erik

        • erik

          Member
          August 3, 2026 at 7:47 pm

          Hi everyone,

          Unfortunately, after several tests, it was confirmed that my BMS board is no longer recoverable and will need to be replaced.

          I would like to sincerely thank the Pytes Support team and the Product Manager for taking the time to diagnose the issue with me through a remote session. Their help, professionalism, and support were greatly appreciated.

          Thank you again for your assistance.

  • furese

    Member
    August 9, 2026 at 10:13 am

    Apkpro games just dropped a new Pytes V5α battery—what a coincidence since I’ve been running my phone on it while grinding Genshin Impact daily open link . The battery life’s insane, but I’ve noticed some lag in Apkpro games when my device heats up after long sessions. Anyone else experiencing this? My concern is balancing power with performance for those late-night grind sessions.

Log in to reply.