Header Ads Widget

unbrick redmi note 8 ginkgo dead boot full flashing via direct emmc

unbrick redmi note 8 dead

 Redmi note 8 masuk dalam kondisi mati total, menurut keterangan dari user nya gara-gara di pasang custom recovery ketika di reboot dari menu custom recovery si handphone nya gak mau nyala, padahal posisi battery masih penuh jadi gak mungkin karena battery terlalu kosong.

bahkan ketika di coba di nyalain dengan di colok casan pun sama gak ada respon sama sekali, jadi bisa dipastiin redmi note 8 bricked mati total 

kemudian saya coba colok di komputer sama sekali tak terdeteksi, tapi ketika di lakukan test poin langsung terdeteksi qualcom 9008

Untuk flashing nya kita membutuhkan kredit untuk authorisasi bootloader, solusi gratis ya kita lakukan direct emmc nya sekalian tes kondisi emmc dan software nya apakah cuman hilang boot nya aja atau system nya yang rusak

pin out emmc nya bisa lihat gambar berikut

isp redmi note 8 ginkgo

dan hasil test setelah di lakukan direct emmc log nya :

Boot version: 1.03, FW version: 1.12 (Jun  7 2018 00:06:47)

Insertion test... Done

Init bus...

VCC: 3.3 V, VCCQ: 1.8 V

Bus: 1 bit (SDR 4MHz)

Access mode: sector mode

Power supply: dual-voltage (1.70-1.95V, 2.7-3.6V)

 Card/BGA: BGA (Discrete embedded) - High density MMC

 Manufacturer ID: 0x15 (Samsung)

 Product name: DD68MB (0x444436384d42), rev: 0x02, serial number: 0xEC49C409

 Manufacturing date: Nov 2019

CID: 15010044 4436384D 4202EC49 C409B6C4

CSD: D0270132 0F5903FF F6DBFFEF 8E40400C

EXT_CSD revision: 1.8 (MMC v5.1) 

Partition info:

 Boot1: 4096 KiB

 Boot2: 4096 KiB

 RPMB: 4096 KiB

 User area: 29.12 GiB(31,268,536,320 bytes)

Cache size: 64 MiB

Hardware reset function: 1

Partition configuration: 0x00

 No boot acknowledge is sent (default)

 Device is not boot-enabled (default)

Partitioning support: 0x07

 Device support partitioning feature

 Device can have enhanced technological features

 Device partitioning possible

Boot configuration protection: 0x00

Boot bus conditions: 0x00

Boot area write protection: 0x00

 Power-on write protection: possible

 Permanent write protection: possible

 Lock status: not locked

ANDROID System Info:

 platform: trinket, cpu abi: 

 board: ginkgo, name: ginkgo

 brand: xiaomi, model: Redmi Note 8

 build id: , version:   ()

crypto state: encrypted?


Dari log diatas bisa dipastikan system android nya rusak karena build id dan version tak terbaca, maka langkah selanjutnya full flashing di tab factory image 

berikut log flashing factory image menggunakan fastboot rom ginkgo id miui 12

Insertion test... Done

Init bus...

VCC: 3.3 V, VCCQ: 1.8 V

Bus: 1 bit (SDR 48MHz)

Access mode: sector mode

Power supply: dual-voltage (1.70-1.95V, 2.7-3.6V)

 Card/BGA: BGA (Discrete embedded) - High density MMC

 Manufacturer ID: 0x15 (Samsung)

 Product name: DD68MB (0x444436384d42), rev: 0x02, serial number: 0xEC49C409

 Manufacturing date: Nov 2019

CID: 15010044 4436384D 4202EC49 C409B6C4

CSD: D0270132 0F5903FF F6DBFFEF 8E40400C

EXT_CSD revision: 1.8 (MMC v5.1) 

Partition info:

 Boot1: 4096 KiB

 Boot2: 4096 KiB

 RPMB: 4096 KiB

 User area: 29.12 GiB(31,268,536,320 bytes)

Processing file: "gpt_main0.bin"...   Applying patch: Update last partition 87 'userdata' with actual size in Primary Header....Done

  Applying patch: Update Primary Header with LastUseableLBA....Done

  Applying patch: Update Primary Header with BackupGPT Header Location....Done

  Applying patch: Update Primary Header with CRC of Partition Array....Done

  Applying patch: Zero Out Header CRC in Primary Header....Done

  Applying patch: Update Primary Header with CRC of Primary Header....Done

 Writing PrimaryGPT at 0x00000000 (34 sectors)... Done in 0.025 s

Processing file: "qupv3fw.elf"...  Writing qupfw at 0x00029000 (97 sectors)... Done in 0.020 s

Processing file: "qupv3fw.elf"...  Writing qupfwbak at 0x00039000 (97 sectors)... Done in 0.018 s

Processing file: "vbmeta.img"...  Writing vbmeta at 0x00049000 (8 sectors)... Done in 0.002 s

Processing file: "vbmeta.img"...  Writing vbmetabak at 0x00059000 (8 sectors)... Done in 0.002 s

Processing file: "xbl_config.elf"...  Writing xbl_config at 0x00069000 (97 sectors)... Done in 0.019 s

Processing file: "xbl_config.elf"...  Writing xbl_configbak at 0x00089000 (97 sectors)... Done in 0.019 s

Processing file: "devcfg.mbn"...  Writing devcfg at 0x000A9000 (84 sectors)... Done in 0.017 s

Processing file: "devcfg.mbn"...  Writing devcfgbak at 0x000C9000 (84 sectors)... Done in 0.016 s

Processing file: "storsec.mbn"...  Writing storsec at 0x00100000 (40 sectors)... Done in 0.008 s

Processing file: "rpm.mbn"...  Writing rpm at 0x00180000 (437 sectors)... Done in 0.160 s

Processing file: "rpm.mbn"...  Writing rpmbak at 0x00200000 (437 sectors)... Done in 0.085 s

Processing file: "hyp.mbn"...  Writing hyp at 0x00280000 (723 sectors)... Done in 0.206 s

Processing file: "hyp.mbn"...  Writing hypbak at 0x00300000 (723 sectors)... Done in 0.136 s

Processing file: "km4.mbn"...  Writing keymaster at 0x00380000 (465 sectors)... Done in 0.090 s

Processing file: "km4.mbn"...  Writing keymasterbak at 0x00400000 (465 sectors)... Done in 0.089 s

Processing file: "cmnlib.mbn"...  Writing cmnlib at 0x00480000 (770 sectors)... Done in 0.166 s

Processing file: "cmnlib64.mbn"...  Writing cmnlib64 at 0x00500000 (1000 sectors)... Done in 0.192 s

Processing file: "cmnlib.mbn"...  Writing cmnlibbak at 0x00580000 (770 sectors)... Done in 0.152 s

Processing file: "cmnlib64.mbn"...  Writing cmnlib64bak at 0x00600000 (1000 sectors)... Done in 0.190 s

Processing file: "abl.elf"...  Writing abl at 0x00880000 (296 sectors)... Done in 0.073 s

Processing file: "abl.elf"...  Writing ablbak at 0x00980000 (296 sectors)... Done in 0.058 s

Processing file: "BTFM.bin"...  Writing bluetooth at 0x00B80000 (1752 sectors)... Done in 0.336 s

Processing file: "BTFM.bin"...  Writing bluetoothbak at 0x00C80000 (1752 sectors)... Done in 0.333 s

Processing file: "misc.img"...  Writing misc at 0x00D80000 (2048 sectors)... Done in 0.478 s

Processing file: "imagefv.elf"...  Writing imagefv at 0x01180000 (40 sectors)... Done in 0.008 s

Processing file: "imagefv.elf"...  Writing imagefvbak at 0x01380000 (40 sectors)... Done in 0.008 s

Processing file: "uefi_sec.mbn"...  Writing uefisecapp at 0x01580000 (252 sectors)... Done in 0.049 s

Processing file: "uefi_sec.mbn"...  Writing uefisecappbak at 0x01780000 (252 sectors)... Done in 0.048 s

Processing file: "xbl.elf"...  Writing xbl at 0x01F80000 (6892 sectors)... Done in 1.324 s

Processing file: "xbl.elf"...  Writing xblbak at 0x02300000 (6892 sectors)... Done in 1.315 s

Processing file: "tz.mbn"...  Writing tz at 0x02680000 (3912 sectors)... Done in 0.900 s

Processing file: "tz.mbn"...  Writing tzbak at 0x02A80000 (3912 sectors)... Done in 0.742 s

Processing file: "logfs_ufs_8mb.bin"...  Writing logfs at 0x05000000 (32 sectors)... Done in 0.007 s

Processing file: "metadata.img"...  Writing sparse image metadata at 0x06200000 (32768 sectors)... Done in 0.019 s

Processing file: "dtbo.img"...  Writing dtbo at 0x09000000 (16384 sectors)... Done in 3.269 s

Processing file: "dtbo.img"...  Writing dtbobak at 0x0A800000 (16384 sectors)... Done in 3.122 s

Processing file: "dspso.bin"...  Writing dsp at 0x10000000 (65536 sectors)... Done in 12.904 s

Processing file: "dspso.bin"...  Writing dspbak at 0x12000000 (65536 sectors)... Done in 12.603 s

Processing file: "boot.img"...  Writing boot at 0x1E000000 (131072 sectors)... Done in 26.413 s

Processing file: "boot.img"...  Writing bootbak at 0x22000000 (131072 sectors)... Done in 25.195 s

Processing file: "recovery.img"...  Writing recovery at 0x2E000000 (131072 sectors)... Done in 25.392 s

Processing file: "NON-HLOS.bin"...  Writing modem at 0x5A000000 (237859 sectors)... Done in 45.770 s

Processing file: "NON-HLOS.bin"...  Writing modembak at 0x6A000000 (237859 sectors)... Done in 45.774 s

Processing file: "cust.img"...  Writing sparse image cust at 0x93000000 (2097152 sectors)... Done in 3 mins 29.430 s

Processing file: "vendor.img"...  Writing sparse image vendor at 0xD3000000 (3145728 sectors)... Done in 6 mins 12.154 s

Processing file: "system.img"...  Writing sparse image system at 0x133000000 (9437184 sectors)... Done in 25 mins 32.313 s

Processing file: "userdata.img"...  Writing sparse image userdata at 0x253000000 (20971520 sectors)... Done in 5 mins 46.872 s

Processing file: "gpt_backup0.bin"...   Applying patch: Update last partition 87 'userdata' with actual size in Backup Header....Done

  Applying patch: Update Backup Header with LastUseableLBA....Done

  Applying patch: Update Backup Header with CurrentLBA....Done

  Applying patch: Update Backup Header with Partition Array Location....Done

  Applying patch: Update Backup Header with CRC of Partition Array....Done

  Applying patch: Zero Out Header CRC in Backup Header....Done

  Applying patch: Update Backup Header with CRC of Backup Header....Done

 Writing BackupGPT at 0x8F7FFFBE00 (33 sectors)... cmd response: 0x80000940, card status: 0x80000000, card state: 4 (Card is in transfer state)

 status: The command’s address argument was out of the allowed range for this card.

Walaupun dari log diatas ada eror pas write backupgpt tapi ketika test identify lagi hasilnya build id dan version sudah terbaca 

ANDROID System Info:

 platform: trinket, cpu abi: arm64-v8a

 manufacturer: Xiaomi

 board: ginkgo, name: ginkgo

 brand: xiaomi, model: Redmi Note 8

 build id: QKQ1.200114.002, version: 10 Alpha ()

crypto state: encrypted?

 untuk mengetahui apakah redmi note 8 nyala apa gak, selanjutnya copot semua jumperan isp dan test di nyalain ternyata hp nya langsung nyala normal sukses luar biasa

ada masalah lain yang timbul yaitu frp dan mi cloud nya aktif, maka sekalian test remove frp dan remove mi cloud nya sekali lagi menggunakan direct emmc 

Insertion test... Done

Init bus...

VCC: 3.3 V, VCCQ: 1.8 V

Bus: 1 bit (SDR 4MHz)

Access mode: sector mode

Power supply: dual-voltage (1.70-1.95V, 2.7-3.6V)

 Card/BGA: BGA (Discrete embedded) - High density MMC

 Manufacturer ID: 0x15 (Samsung)

 Product name: DD68MB (0x444436384d42), rev: 0x02, serial number: 0xEC49C409

 Manufacturing date: Nov 2019

CID: 15010044 4436384D 4202EC49 C409B6C4

CSD: D0270132 0F5903FF F6DBFFEF 8E40400C

EXT_CSD revision: 1.8 (MMC v5.1) 

Partition info:

 Boot1: 4096 KiB

 Boot2: 4096 KiB

 RPMB: 4096 KiB

 User area: 29.12 GiB(31,268,536,320 bytes)

Clear FRP Lock... Done

[Xiaomi] Reset MI Account Lock... Done


Dan hasil akhirnya frp dan micloud ternyata bisa hilang menggunakan direct emmc .

bagi sobat yang butuh fastboot rom redmi note 8 silahkan sedot langsung


Demikian sharing pengalaman kali ini semoga bermanfaat buat sobat yang mendapati kasus yang sama redmi note 8 ginkgo deadboot











Posting Komentar

0 Komentar