[Please help] Remove FRP on ECOPAD/COLORROOM E30_Pro tablet (Unisoc T606)
[Please help] Remove FRP on ECOPAD/COLORROOM E30_Pro tablet (Unisoc T606)
24-09-2026, 07:52 PM
Device: ECOPAD-branded tablet (retail rebrand), real ODM/build info shows COLORROOM/E30_Pro/E30_Pro
Android build: 15/AP3A.240905.015.A2/20250328
Chipset: Unisoc Tiger T606, board silkscreen reads "W30-T606-V2.Q"
USB ID in Android/recovery mode: 1782:d001 (Spreadtrum Communications Inc, Unisoc Phone)
Situation: I got this secondhand in a giveaway, was locked with a PIN from the previous owner,
I factory reset it not realizing this would trigger FRP since the Google account wasn't removed first. Now stuck on the FRP setup screen.
What I've tried:
- adb devices while sitting at the main recovery screen: nothing detected
- adb devices while in "Apply update from ADB" mode: detected, but only as
"sideload" state — adb shell returns "error: closed" as expected for minadbd
- Looked into spd_dump (open source SPD flash tool) for a persist-partition
erase, but I don't have FDL1/FDL2 loader files for this exact
chipset/board and can't find public firmware for this ODM/brand
Does anyone recognize this board or have FDL1/FDL2 files for a T606/UMS9230 device that might work here? Or any other suggestions for an obscure white-label board like this? Happy to provide more photos/logs if useful.
Thanks in advance for your help
07-10-2026, 07:54 AM
(24-09-2026, 07:52 PM)Aztarot Device: ECOPAD-branded tablet (retail rebrand), real ODM/build info shows COLORROOM/E30_Pro/E30_Pro
Android build: 15/AP3A.240905.015.A2/20250328
...
Thanks in advance for your help
Try the FDLs and addresses (referenced in the unlock batch file) and see if spd_dump detects the device.
Attached Files
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
13-10-2026, 07:54 PM
spd_dump --wait 300 exec_addr 0x65015f08 fdl fdl1-dl.bin 0x65000800 fdl fdl2-dl.bin 0x9efffe00 exec r splloader r uboot e splloader e splloader_bak reset
FDL1 loads and runs successfully: the full file transfers, the device responds with BSL_REP_VER: "Spreadtrum Boot Block version 1.1", and both CMD_CONNECT FDL1 and KEEP_CHARGE FDL1 complete normally.
Then it hangs completely on the FDL2 handoff. Right after KEEP_CHARGE, spd_dump sends the FDL2 start-of-transfer packet (SEND fdl2-dl.bin to 0x9efffe00), and the device gives zero response — not a partial/corrupted transfer, just silence, timing out immediately on the very first packet. This is consistent across three attempts, two different USB cables, and two different ports, so I don’t think it’s a cable/connection issue.
Device info again for reference:
COLORROOM/E30_Pro/E30_Pro, Android 15/AP3A.240905.015.A2/20250328
Board silkscreen: W30-T606-V2.Q (Unisoc Tiger T606)
Does this look like a known FDL1/board-compatibility mismatch, or possibly a wrong FDL2 base address for this board revision? Happy to share the full verbose log if useful.
Users browsing this thread:
1 Guest(s)
1 Guest(s)
Users browsing this thread:
1 Guest(s)
1 Guest(s)