Device: Miyoo Flip V2 (RK3566, 128MB SPI NAND, no eMMC), previously running KNULLI Tools: RKDevTool + drivers from the spruceOS MiyooFlipUnbricker.zip package, Windows PC

Summary

Bricked the device via a failed unbrick attempt on Linux (rkdeveloptool likely targeting the wrong storage medium). Moved to Windows and successfully recovered it once — then bricked it again during a KNULLI reinstall, and now can't get RKDevTool to talk to the flash chip at all.

Timeline

1. Original brick: Device got stuck in Maskrom mode after a failed unbrick attempt on Linux using rkdeveloptool. Suspected the tool was targeting eMMC instead of SPI NAND (this device has no eMMC — confirmed 128MB SPI NAND + dual microSD).
2. First successful recovery (Windows):
   • Installed drivers via DriverInstall.exe from MiyooFlipUnbricker.zip
   • RKDevTool detected "Found One Maskrom Device"
   • Set storage medium to SPI NAND in Advanced Function
   • Flashed stock firmware — no confirmation dialog appeared, but log showed completion and device booted to stock OS successfully
3. Second brick: While reinstalling KNULLI, interrupted the GammaLoader bootloader install mid-process (didn't know it needed to run uninterrupted through multiple reboots). Device got stuck on a modified Miyoo OS boot logo.
4. Recovery attempt #2 — failing:
   • Re-entered Maskrom successfully (device detected fine)
   • Attempted stock reflash → "Download Boot Fail"
   • Tried Erase All → "Get Flash Info Fail"
   • Since then, every flash attempt either fails outright or completes suspiciously fast (seconds, not minutes) with no real write happening

Troubleshooting already tried (no change)

• Reconfirmed storage medium set to SPI NAND (not eMMC)
• Swapped USB cables (multiple)
• Swapped USB ports, including direct rear motherboard ports (no hubs)
• Fully closed/reopened RKDevTool between attempts
• Cold-replugged into fresh Maskrom state multiple times
• Reinstalled RockUSB drivers from the unbricker package
• Rebooted the PC

Current state

• Device reliably enters and stays in Maskrom mode (BootROM responds)
• RKDevTool detects the device as present
• RKDevTool cannot successfully query flash info or complete a boot/erase operation
• Same exact hardware + software combo produced one clean successful flash earlier in this process — nothing hardware-side should have changed between then and now

Questions

• Is "Get Flash Info Fail" after a previously successful flash cycle a known issue with this device's SPI NAND chip specifically?
• Could a different RKDevTool version (vs. the one bundled in MiyooFlipUnbricker.zip) resolve a flash-info query failure like this?
• Any chance the interrupted GammaLoader write left the SPI NAND in a state that needs a different recovery approach than a standard stock reflash?

Happy to provide RKDevTool logs, exact error screenshots, or anything else that'd help diagnose this.

Device: Miyoo Flip V2, RK3566
Tool: rkdeveloptool on Linux (no Windows/RKDevTool available)

What happened: GammaLoader install glitched after a game freeze/hard shutdown, ended up stuck (loading screen → black, even with no SD card). Followed the spruceOS unbrick guide, got the device into Maskrom mode successfully.

What I've tried:

• Unpacked official update.img (RKFW → embedded RKAF) via afptool-rs → got MiniLoaderAll.bin, uboot.img, boot.img, rootfs.img, userdata.img, parameter.txt
• db MiniLoaderAll.bin → succeeds
• gpt parameter.txt → succeeds
• wlx uboot/boot/rootfs/userdata → all report 100% success
• ul MiniLoaderAll.bin (permanent loader) → runs, but device still shows Maskrom afterward, not Loader mode
• rd (reset) → fails
• Device still shows zero signs of booting (no LED change, no logo, black screen)

Noticed parameter.txt references spi-nand0 in CMDLINE — tried cs 9 (SPINOR) to make sure writes were targeting the right storage type, but that command failed too.

Any idea what I'm missing? Willing to provide full command output if helpful.

Device: Miyoo Flip V2, stuck in maskrom mode after failed GammaLoader/KNULLI install
Chip: RK3566 (confirmed via unpacked firmware)
Tool: rkdeveloptool on Linux
What I've done:

• Unpacked official update.img (RKFW → embedded RKAF) using afptool-rs, got MiniLoaderAll.bin, uboot.img, boot.img, rootfs.img, userdata.img, parameter.txt
• db MiniLoaderAll.bin → succeeds ("Downloading bootloader succeeded")
• gpt parameter.txt → succeeds
• wlx uboot/boot/rootfs/userdata → all succeed at 100%
• Device still won't boot — LED unchanged, no logo, screen black
• ul MiniLoaderAll.bin (permanent loader write) → runs, but device still shows as Maskrom afterward, not Loader
• rd (reset) → fails

the battery on my gpi 2w case randomly died, and I need a replacement. does anyone know where I can buy one?

https://preview.redd.it/7ctl2ztp6vgh1.png?width=531&format=png&auto=webp&s=768ac76140b71c8c22d6f5defe938051fa11ad8d