[Xiaomi Redmi Note 4 Questions & Answers] Leonelle:
Hello

I received brand new Xiaomi Remi Note 4 (MediaTek) yesterday and I opened the package and wanted to boot the device up and I was shocked that the device is hanging on Mi logo and then restart or it does what known bootloop, the device enters fastboot mode and nothing else, I tasted the device with too many tools and methods so finally I made sure that there is a problem in internal storage or (eMMC) the data stored as RAW data as shown in the following result:

[VKZ5H6QKR4GEC6TC] *** Fastboot mode

(bootloader) max-download-size: 0x8000000

(bootloader) partition-size:flashinfo: 1000000

(bootloader) partition-type:flashinfo: raw data

(bootloader) partition-size:otp: 2b00000

(bootloader) partition-type:otp: raw data

(bootloader) partition-size:userdata: 32000000

(bootloader) partition-type:userdata: ext4

(bootloader) partition-size:cache: 1b000000

(bootloader) partition-type:cache: ext4

(bootloader) partition-size:system: c0000000

(bootloader) partition-type:system: ext4

(bootloader) partition-size:cust: 20600000

(bootloader) partition-type:cust: raw data

(bootloader) partition-size:keystore: 800000

(bootloader) partition-type:keystore: raw data

(bootloader) partition-size:tee2: 500000

(bootloader) partition-type:tee2: raw data

(bootloader) partition-size:tee1: 500000

(bootloader) partition-type:tee1: raw data

(bootloader) partition-size:logo: 800000

(bootloader) partition-type:logo: raw data

(bootloader) partition-size:boot: 1000000

(bootloader) partition-type:boot: raw data

(bootloader) partition-size:lk2: 400000

(bootloader) partition-type:lk2: raw data

(bootloader) partition-size:lk: 400000

(bootloader) partition-type:lk: raw data

(bootloader) partition-size:nvram: 500000

(bootloader) partition-type:nvram: raw data

(bootloader) partition-size:scp2: 100000

(bootloader) partition-type:scp2: raw data

(bootloader) partition-size:scp1: 100000

(bootloader) partition-type:scp1: raw data

(bootloader) partition-size:md3img: 500000

(bootloader) partition-type:md3img: raw data

(bootloader) partition-size:md1arm7: 300000

(bootloader) partition-type:md1arm7: raw data

(bootloader) partition-size:md1dsp: 400000

(bootloader) partition-type:md1dsp: raw data

(bootloader) partition-size:md1img: 1800000

(bootloader) partition-type:md1img: raw data

(bootloader) partition-size:proinfo: 300000

(bootloader) partition-type:proinfo: raw data

(bootloader) partition-size:oemkeystore: 200000

(bootloader) partition-type:oemkeystore: raw data

(bootloader) partition-size:seccfg: 800000

(bootloader) partition-type:seccfg: raw data

(bootloader) partition-size:protect2: d78000

(bootloader) partition-type:protect2: ext4

(bootloader) partition-size:protect1: 800000

(bootloader) partition-type:protect1: ext4

(bootloader) partition-size:metadata: 2000000

(bootloader) partition-type:metadata: raw data

(bootloader) partition-size:nvdata: 2000000

(bootloader) partition-type:nvdata: ext4

(bootloader) partition-size:nvcfg: 800000

(bootloader) partition-type:nvcfg: ext4

(bootloader) partition-size:expdb: a00000

(bootloader) partition-type:expdb: raw data

(bootloader) partition-size:para: 80000

(bootloader) partition-type:para: raw data

(bootloader) partition-size:recovery: 1000000

(bootloader) partition-type:recovery: raw data

(bootloader) partition-size:preloader: 40000

(bootloader) partition-type:preloader: raw data

(bootloader) off-mode-charge: 1

(bootloader) warranty: yes

(bootloader) unlocked: no

(bootloader) secure: yes

(bootloader) kernel: lk

(bootloader) product: nikel

(bootloader) version-preloader:

(bootloader) version: 0.5

I was able to repair system, userdata and cache partitions but that was useless, I'm not sure that the problem could be fixed by software solution or hardware one or it's initially and technical problem

Any one can post working bootloader log here using the command 'fastboot getvar all'