Flash Redmi 4X Gagal

Flashing memang sangat menyenangkan untuk membersihkan device dari file-file tidak jelas dan merefresh handphone.

Tetapi, apa jadinya bila ROM sudah benar, MiFlash sudah benar, driver sudah benar, tetapi ternyata ada muncul error seperti di bawah ini?

Errornya adalah : Unspecified Error 0x80004005 : FAILED (remote : data too large). Alangkah pusingnya apabila ROM Global pun menghasilkan error seperti ini. Akan tetapi tidak usah terlalu cemas. Sebenarnya MiFlash hanyalah menjalankan batch "FLASH_ALL.BAT". Lanjutkan secara manual baris-baris yang belum terjalankan.

Mari kita intip sebentar isi "flash_all.bat" tersebut

echo "santoni Fastboot Tool Ver 3.0"

fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *santoni" || echo Missmatching image and device

fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *santoni" || exit /B 1

fastboot %* flash partition %~dp0images\gpt_both0.bin || @echo "Flash tz error" && exit /B 1

if exist "%~dp0images\crclist.txt" (fastboot %* flash crclist %~dp0images\crclist.txt 2>nul)

if exist "%~dp0images\sparsecrclist.txt" (fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt 2>nul)

fastboot %* flash tz %~dp0images\tz.mbn || @echo "Flash tz error" && exit /B 1

fastboot %* flash sbl1 %~dp0images\sbl1.mbn || @echo "Flash sbl1 error" && exit /B 1

fastboot %* flash rpm %~dp0images\rpm.mbn || @echo "Flash rpm error" && exit /B 1

fastboot %* flash aboot %~dp0images\emmc_appsboot.mbn || @echo "Flash emmc_appsboot error" && exit /B 1

fastboot %* flash tzbak %~dp0images\tz.mbn || @echo "Flash tzbak error" && exit /B 1

fastboot %* flash sbl1bak %~dp0images\sbl1.mbn || @echo "Flash sbl1bak error" && exit /B 1

fastboot %* flash rpmbak %~dp0images\rpm.mbn || @echo "Flash uboot rpmbak" && exit /B 1

fastboot %* flash abootbak %~dp0images\emmc_appsboot.mbn || @echo "Flash abootbak error" && exit /B 1

fastboot %* flash devcfg %~dp0images\devcfg.mbn || @echo "Flash devcfg error" && exit /B 1

fastboot %* flash lksecapp %~dp0images\lksecapp.mbn || @echo "Flash lksecapp error" && exit /B 1

fastboot %* flash cmnlib %~dp0images\cmnlib.mbn || @echo "Flash cmnlib error" && exit /B 1

fastboot %* flash cmnlib64 %~dp0images\cmnlib64.mbn || @echo "Flash cmnlib64 error" && exit /B 1

fastboot %* flash keymaster %~dp0images\keymaster.mbn || @echo "Flash keymaster error" && exit /B 1

fastboot %* flash devcfgbak %~dp0images\devcfg.mbn || @echo "Flash devcfgbak error" && exit /B 1

fastboot %* flash lksecappbak %~dp0images\lksecapp.mbn || @echo "Flash lksecappbak error" && exit /B 1

fastboot %* flash cmnlibbak %~dp0images\cmnlib.mbn || @echo "Flash cmnlibbak error" && exit /B 1

fastboot %* flash cmnlib64bak %~dp0images\cmnlib64.mbn || @echo "Flash cmnlib64bak error" && exit /B 1

fastboot %* flash keymasterbak %~dp0images\keymaster.mbn || @echo "Flash keymasterbak error" && exit /B 1

fastboot %* flash dsp %~dp0images\adspso.bin || @echo "Flash dsp error" && exit /B 1

fastboot %* erase boot

fastboot %* erase mdtp

fastboot %* flash modem %~dp0images\NON-HLOS.bin || @echo "Flash modem error" && exit /B 1

fastboot %* flash system %~dp0images\system.img || @echo "Flash system error" && exit /B 1

fastboot %* flash cache %~dp0images\cache.img || @echo "Flash cache error" && exit /B 1

fastboot %* flash userdata %~dp0images\userdata.img || @echo "Flash userdata error" && exit /B 1

fastboot %* flash recovery %~dp0images\recovery.img || @echo "Flash recovery error" && exit /B 1

fastboot %* flash boot %~dp0images\boot.img || @echo "Flash boot error" && exit /B 1

fastboot %* flash misc %~dp0images\misc.img || @echo "Flash misc error" && exit /B 1

fastboot %* flash splash %~dp0images\splash.img || @echo "Flash splash error" && exit /B 1

fastboot %* flash cust %~dp0images\cust.img || @echo "Flash cust error" && exit /B 1

fastboot %* reboot

pause

Apabila tertulis "remote : data too large". Kemungkinan paling besar, adalah ketika flash system.img, karena system.img adalah file yang paling besar.

Jangan panik, toh sudah masuk mode fastboot. Apapun yang terjadi, meskipun brick, kita masih bisa mengakses fastboot.

Langkah selanjutnya adalah, kita lakukan sisa-sisa baris yang belum terjalankan, yaitu yang diarsir kuning di atas. Bukalah command prompt, masuk ke folder tempat dimana *.img tersebut berada. Jalankan satu persatu 

fastboot flash system system.img

fastboot flash cache cache.img

fastboot flash userdata userdata.img

fastboot flash recovery recovery.img

fastboot flash boot boot.img

fastboot flash misc misc.img

fastboot flash splash splash.img

fastboot flash cust cust.img

kira-kira hasilnya seperti di bawah ini

apabila selesai, ketik fastboot reboot. Redmi akan reboot kemudian ditunggu saja.

At least, works for me.