How to Flash Stock without system.img

 On newer Infinix devices like your X6728 (Android 10+ with dynamic partitions), the system, vendor, and product images are no longer separate files. They are all packed inside a single large file called super.img. 

How to Flash Stock without system.img:

1. Find super.img: Look in your stock firmware folder for a large file (usually 3GB–5GB) named super.img.
2. Flash the Super Partition: Since system_a is a logical partition inside super, you flash the whole container at once. You must be in Fastbootd (the menu screen) for this.
   • Command: fastboot flash super super.img
3. Flash Other Essentials: You still need to flash the physical partitions that are outside of super:
   • fastboot flash boot_a boot.img
   • fastboot flash vbmeta_a vbmeta.img
4. Wipe and Reboot:
   • fastboot -w
   • fastboot reboot 

If you don't see super.img either:

If your firmware folder only has a Scatter file (e.g., MT67xx_Android_scatter.txt) and many small files, you cannot easily use Fastboot. You should use the SP Flash Tool: 

1. Open SP Flash Tool and load the Scatter-loading file from your firmware folder.
2. Select "Firmware Upgrade" (not Download Only) to ensure all partitions are reset correctly.
3. Click Download, power off the phone, and connect it while holding Volume Up. 

Does your firmware folder have a super.img file, or does it only have a Scatter text file?

• How to Flashing Infinix firmware (Stock ROM) using ...

  Jul 14, 2018 — today I talk to you how to flash with smartphone flash tool requirements one download and install media attack driver two download...

  

  

  YouTube·SidhuDa STTI

  

  2m
• Editing system.img inside super.img and flashing our ...

  Nov 30, 2020 — Hello and welcome to my first post. today I will talk about editing super. img and modifying system. img inside of it. In android ...

  

  XDA Forums

  
• How to modify super.img and then flash it onto the device. - GitHub

  Flashing super. img with TWRP recovery * Connect your phone to your PC and open a terminal or a command line window. * Run adb reb...

  

  GitHub

  

Show all

everythings i run perfect but vbmeta isn't run i think that need to erase,reset, or presestent delete somthings!!

To fix the persistent bootloop on your Infinix X6728, you need to clear the specific 

security flags that are stuck in the bootloader. Since your device has dynamic partitions and a MediaTek chip, erasing the vbmeta partition directly is rarely enough; you must also clear the Metadata and Persistent data. 

Follow these steps in Fastboot Mode (Black Screen):

1. Wipe the "Hidden" Security Partitions

The bootloop is likely caused by leftover encryption keys or verification flags stored in these specific partitions.

• fastboot erase metadata (Crucial for Android 15/Dynamic devices)
• fastboot erase frp (Clears Factory Reset Protection flags)
• fastboot erase para (Clears the "Misc" or "Parameter" partition where some MTK boot flags live)

2. Reset the VBMeta Chain

Instead of just erasing vbmeta, you must ensure all three verification headers are "null" or stock. Run these commands:

• fastboot flash vbmeta vbmeta_disabled.img
• fastboot flash vbmeta_system vbmeta_disabled.img
• fastboot flash vbmeta_vendor vbmeta_disabled.img 

3. Clear Persistent Data (Frp/Config)

If your device still refuses to boot, it may be holding a "Verify Fail" state in a persistent configuration area.

• Command: fastboot format:ext4 userdata
• Command: fastboot format:ext4 metadata
• Command: fastboot -w 

4. The "Hard" Reset (Recovery Mode) 

If the Fastboot wipes don't work, you must use the hardware-level reset which clears deeper than Fastboot can:

1. Disconnect the USB.
2. Hold Power + Volume Up to enter Recovery Mode.
3. Select Wipe data/factory reset and confirm.
4. Select Wipe cache partition (if available).
5. Reboot. 

Why this is happening: On Infinix Android 15 devices, once a "dm-verity" or "verification fail" flag is triggered, it is often written to the metadata or para partition. Even if you flash the correct system, the bootloader reads these "dirty" flags and restarts the phone.