PLEASE HELP With New Version of the Qin F21, Different Hardware and ROM

Phones Qin F21 Pro
1

i just received a new batch of qin phones and right away noticed that the boot logo was different (locked bootloader) i used mtkclient to unlcok the boot loader and then tried spflash tool and i couldnt even get sp dlash tool to respond with an error at least. so i comapered the printgpt results with my working qin aand ran it through claude and heres what i got

 Perfect! Now I can see the exact issue. Let me create a comparison table:

  Critical Difference: The Super Partition

  Working Device (old batch):
  - Line 161: super: Offset 0x0000000030000000, Length 0x0000000100000000 (4GB = 4,294,967,296 bytes)
  - Line 63: EMMC ID: RX1BMB

  New Device (new batch):
  - Line 173: super: Offset 0x0000000030000000, Length 0x00000000e0000000 (3.5GB = 3,758,096,384 bytes)
  - Line 75: EMMC ID: GD6BMB

  The Root Cause:

  Different eMMC chips = Different partition layouts

  1. Old devices: Samsung eMMC (RX1BMB) with 4GB super partition
  2. New devices: GigaDevice eMMC (GD6BMB) with 3.5GB super partition

  The super partition is 512MB smaller in the new batch, which causes a cascading effect on all subsequent
  partitions:

  Address Shift Comparison:

  | Partition       | Old/Working Device   | New Device           | Difference                |
  |-----------------|----------------------|----------------------|---------------------------|
  | super           | 0x30000000 (4GB)     | 0x30000000 (3.5GB)   | -512MB                    |
  | vbmeta_b        | 0x130000000          | 0x110000000          | -512MB                    |
  | vbmeta_system_b | 0x130800000          | 0x110800000          | -512MB                    |
  | vbmeta_vendor_b | 0x131000000          | 0x111000000          | -512MB                    |
  | userdata        | 0x131800000 (24.6GB) | 0x111800000 (25.2GB) | -512MB start, +600MB size |

  Why SP Flash Tool Fails:

  Your scatter file tells SP Flash Tool to write to addresses that don't match the actual GPT table on the new
  devices. When it tries to write to 0x130000000 for vbmeta_b, it's actually trying to write 512MB beyond where the
  partition actually exists. This causes:

  1. Address validation failure - SP Flash Tool detects the mismatch
  2. Connection rejection - The tool refuses to proceed with invalid addresses
  3. Partition boundary errors - Writing to wrong offsets would corrupt data

  Solution:

  You need a new scatter file specifically for the GD6BMB eMMC variant. Would you like me to generate one based on
  the new device's printgpt output?

i tried the new scatter it made and nothing at all. i have confirmed using mtkclient and claude that both devices are mt6761 but they seem to still have differnt chips and the super is smaller…. i also tried flashing using mtkclient and now the phone shows rainbow colors and the flashlight turns on when i try to boot it and then it just turns off anyone know wht i can do to flash 1.1.1 and have it work on this device.

Qin F21 Pro Plus
ROM - F21 Pro USA v6.1.3 (Verizon MMS Fixed)
2

You should probably pick up a cm2 dongle and do a readback

3

what the point of cm2 dongle i can fo a readback with mtkclient no. i already made a full backup

4

Ah I didn’t get that. In general it’s just a better tool. What’s the build number of the new batch?

5

2.0.2

6

anyone ever had this

7

Mt6761?

8

yes

9

confirmed using mtkclient

10

You willing to possibly brick a device?

11

I recently was in touch with one of the Chinese sellers and was told that the new phones have “new software”, got a sample, and the stock ROM for it. Don’t think the version was 2.0.2 though, so not sure if that will help you

12

Also why don’t you try flashing in fastboot?

13

i already soft bricked one - what do you have in mind - i kind of desperate it was 2000$

14

ill try that but dont wont to brick to many if possible. not dure though why fastboot will help

15

i have a full backup can i flash it and relock the bootloader to see if it boots

16

Two ideas…

Less risky, make your own ROM from stock.

Or, completely delete partitions and recreate with parted, probably a bad idea.

There’s probably an easier way

17

if i recreate rom from stock what do i need to replace to have it like the 1.1.1 asumming the files still work on the new device like services and framework

18

claude suggested this

  Using MTKClient, you would need to:
  # DANGEROUS - DO NOT RUN WITHOUT FULL BACKUP
  python mtk.py w gpt --image=old_gpt_backup.bin  # Write old GPT table
  python mtk.py reset  # Reset device

  But this assumes:
  - The eMMC physically supports the old layout
  - You have a backup of the old GPT
  - You're willing to risk bricking
1 Like
19

Dunno about framework (probably, but I don’t know the new device changes) and services.jar

And gapps

20

I’d try it but I break a new phone every day.

I’ve rewritten partition tables on the OnePlus 6t with parted.