xrAgH3lBCk0anL27bi4osNTes3KB3baQXCcTHaa1
Bookmark

Redmi 3S (Land) Fix Sensor Micloud Bootlop And Hang Logo

How to Flashing Xiaomi Redmi 3S and Prime / PRO I intentionally wrote this because maybe there are many who have difficulty in flashing things including myself  This article was written after a failure and my success in flashing redmi 3S belongs to a friend of my friend not my own yaa. This flashing method is for Xiami Redmi 3s / Pro or Prime bootloop or brick and can also be used in your xiaomi redmi 3s normal because the tutorial I will give has been tested using Windows 7 64bit.

Redmi 3S (Land) Fix Sensor Micloud Bootlop And Hang Logo

At the time of flashing I also experienced failures such as bootloop, Error 0x80070026 Hello Packet, Not Enough Storage is Availabel and others, several times failed to flash until using flash through adb was also rejected by HH, let's just finish the story just follow the tutorial on how to flash xiaomi redmi 3S / Prime via Fastboot correctly and please note.

Here is a Tutorial on How to Flashing Xiaomi Redmi 3S in Bootloop or Brick or Normal.


Required: Preinstall



The first step before Flashing is preparation for the installation of materials that you have downloaded above:

  • Install MiFlash Tool,
  • Install QDLoader HS-USB,
  • Extract the Rom Fasboot Global Stable,
  • Redmi 3S is in FastBoot Mode (Press power + volume down)

Xiami Redmi 3s / Pro or Prime Flashing Process:

Redmi 3 is in Fastboot Mode,

Connect your USB or redmi 3 data cable to your computer or laptop,
Open the Adb Folder according to the location during your installation, Ex: (C: / Program file / Xiaomi / MiPhone / Google / Android) then press shift + right click on the mouse select Open Command Window here, see the picture below:

how to open the adb command
In the cmd Window, type fastboot devices to find out if xiaomi redmi 3s. Bloggers friend is detected or not, if detected type fastboot reboot by pressing the volume button - and + then enter and reboot redmi 3 friend with the command "fastboot reboot"

After following the steps above, your redmi 3s will turn off and just blank black, but don't worry, because this way there is a solution for your redmi 3s / pro or your bootloop or can't enter Download Mode,

By installing the HS-USB QDLoader Driver above, your redmi 3s device will be detected on COM3, COM4, ​​COM4 or other PORT (COM & LPT),

Open the MiFlash Tool and refresh it, and look at the device column, COM3, COM4 or other will be detected, Flash in the normal way and wait for the flashing process to finish,

flashing redmi3s bootloop condition

If Flash is finished, there will be a flash done information on the status tab in the MiFlash Tool, unplug your data cable and restart your redmi 3s / pro or prime by pressing and holding the power button until the HH lights up, wait for the boot process until the redmi 3s / pro or prime you light up, usually after flashing the boot process will take longer about 3 to 5 minutes.


Done now xiaomi redmi 3s / pro or prime You can be used again or have been able to change the distributor ROM to global stable ROM.

Mode:normal
Hardware:qcom
Manufactory:XIAOMI
Model:REDMI 3S
-------------------------------------
Operation:Read Device Information

Checking environment ...
System Info
Display ID:MMB29M
System Ver:6.0.1 REL
API Level:23
Incremental:V8.1.1.0.MALMIDI
Model:Redmi 3S
Brand:Xiaomi
Device:land
Platform:msm8937
Product:land
Language:in
Rigion:ID

SDCard Info
SDCARD[1] Q313MB

CID:150100513331334d4206d61ec6708300
CSD:d02701320f5903fff6dbffef8e404000
Type:MMC
Serial:0xd61ec670
Parts:50

Device Info
Serial number:d61ec6707d53
Hardware:qcom
Bootmode:unknown
Bootloader ver:unknown
Revision:0
Main version:
Baseband ver:msm
GSM baseband:ENNS_PACK-1.69259.1.69863.2-V036
GSM sim state:ABSENT,ABSENT
Get Bluetooth info failed
WiFi interface:
WiFi MAC:74:23:44:13:98:6d
WiFi state:SCANNING
Root Access:No root

Time used : 6.9 s

Performed by BST V3.51.00, time used 6.9 s

Storage type: eMMC
Card/BGA: BGA (Discrete embedded)
Manufacturer ID: 0x15 (Samsung)
Product name: Q313MB (0x513331334d42), rev: 0x06, serial number: 0xD61EC670
Manufacturing date: Agu 2016
CID: 15010051 3331334D 4206D61E C6708300
CSD: D0270132 0F5903FF F6DBFFEF 8E404000

platform: msm8937, cpu abi: arm64-v8a
manufacturer: Xiaomi
hardware: qcom
board: msm8937, name: land
brand: Xiaomi, model: Redmi 3S
build id: MMB29M, version: 6.0.1 Marshmallow (MMB29M), mod: land_global (MIUI8)
build date: Tue Nov 8 11:47:48 CST 2016, security patch: 2016-09-05
build description: land-user 6.0.1 MMB29M V8.1.1.0.MALMIDI release-keys

soc(CPU):  Qualcomm Technologies, Inc MSM8937
memory(RAM): 2 GB
secure boot: yes (locked)
boot state: green
crypto state: encrypted (block)
boot serial no: d61ec6707d53
serial no: 2A637W097595
wt board id: S88537AA1
wt build version: SW_S88537AA1_V066_M20_MP_XM
device model: XMP-2016030
baseband version: ENNS_PACK-1.69259.1.69863.2-V036
ril version: Qualcomm RIL 1.0
sim state: ABSENT,ABSENT
android id: 8a44aed34e58d0c8
client id: android-xiaomi
bt addr: 74:23:44:13:98:6c
wifi mac: 4:23:44:13:98:6d
imei[1]: 8627560372276**
imei[2]: 8627560372276**
region: ID
locale: en-GB
battery level: 0%
superuser: no


Scanning for Qualcomm HS-USB QDLoader 9008 device...
Download Port: Qualcomm HS-USB QDLoader 9008 (COM38)
Connection status: EHCI:HUB:HUB:HUB:HUB:USB 2.00 High-Speed
USB Driver: [Qualcomm Incorporated] qcusbser, version: 2.1.2.2, date: 3-25-2016
Initializing...
MSM Serial number: 0x00e803e8
MSM HW ID: 0x0004f0e1 (MSM8937)
OEM Public Key Hash: 0x57158eaf1814d78fd2b3105ece4db18a817a08ac664a5782a925f3ff8403d39a
SBL SW version: 0
Firehose: prog_emmc_firehose_8937_ddr.mbn

hash: 073194efa95eed11b89f22b2fc6787b86179afb7, size: 371.46 KiB
QC_IMAGE_VERSION: BOOT.BF.3.3-00148
IMAGE_VARIANT: FAADANAZA
OEM_IMAGE_VERSION: modem-ci

Sending firehose loader... Done
Handshaking...
Sending ping... Done
Sending configurations...

TargetName: 8937
MemoryName: eMMC
Version: 1

Firehose configured.
Storage type: eMMC
Manufacturer ID: 0x15 (Samsung)
Product name: Q313MB (0x513331334d42), rev: 0x06, serial number: 0x00000000
Capacity: 14.57 GiB(15,646,851,072 bytes)
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 4096 KiB
User area: 14.56 GiB(15,634,268,160 bytes)

platform: msm8937, cpu abi: arm64-v8a
manufacturer: Xiaomi
board: msm8937, name: land
brand: Xiaomi, model: Redmi 3S
build id: MMB29M, version: 6.0.1 Marshmallow (MMB29M) (MIUI8)
build description: land-user 6.0.1 MMB29M V8.1.1.0.MALMIDI release-keys

crypto state: encrypted

Firmware package: land_global_images_V8.1.1.0.MALMIDI_20161108.0000.00_6.0_global
Scanning for Qualcomm HS-USB QDLoader 9008 device...
Download Port: Qualcomm HS-USB QDLoader 9008 (COM38)
Connection status: EHCI:HUB:HUB:HUB:HUB:USB 2.00 High-Speed
USB Driver: [Qualcomm Incorporated] qcusbser, version: 2.1.2.2, date: 3-25-2016
Initializing...
MSM Serial number: 0x00e803e8
MSM HW ID: 0x0004f0e1 (MSM8937)
OEM Public Key Hash:
0x57158eaf1814d78fd2b3105ece4db18a817a08ac664a5782a925f3ff8403d39a
SBL SW version: 0
Firehose: prog_emmc_firehose_8937_ddr.mbn

hash: 073194efa95eed11b89f22b2fc6787b86179afb7, size: 371.46 KiB
QC_IMAGE_VERSION: BOOT.BF.3.3-00148
IMAGE_VARIANT: FAADANAZA
OEM_IMAGE_VERSION: modem-ci

Sending firehose loader... Done
Handshaking...
Sending ping... Done
Sending configurations...

TargetName: 8937
MemoryName: eMMC
Version: 1

Firehose configured.
Storage type: eMMC
Manufacturer ID: 0x15 (Samsung)
Product name: Q313MB (0x513331334d42), rev: 0x06, serial number: 0x00000000
Capacity: 14.57 GiB(15,646,851,072 bytes)
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 4096 KiB
User area: 14.56 GiB(15,634,268,160 bytes)

Processing rawprogram0.xml
Writing PrimaryGPT at 0x00000000 (34 sectors)... Done
Writing modem at 0x04000000 (172032 sectors)... Done
Writing sbl1 at 0x0C002400 (665 sectors)... Done
Writing sbl1bak at 0x0C082400 (665 sectors)... Done
Writing rpm at 0x0C102400 (332 sectors)... Done
Writing rpmbak at 0x0C182400 (332 sectors)... Done
Writing tz at 0x0C202400 (2647 sectors)... Done
Writing tzbak at 0x0C402400 (2647 sectors)... Done
Writing devcfg at 0x0C602400 (104 sectors)... Done
Writing devcfgbak at 0x0C642400 (104 sectors)... Done
Writing dsp at 0x0C682400 (32768 sectors)... Done
Writing splash at 0x14000000 (10802 sectors)... Done
Writing aboot at 0x18000000 (1134 sectors)... Done
Writing abootbak at 0x18100000 (1134 sectors)... Done
Writing boot at 0x18200000 (41235 sectors)... Done
Writing recovery at 0x1C200000 (42975 sectors)... Done
Writing system at 0x20300000 (5586461 sectors)... Done
Writing cache at 0xE4000000 (12497 sectors)... Done
Writing persist at 0xF4000000 (9433 sectors)... Done
Writing mdtp at 0x100180000 (2000 sectors)... Done
Writing lksecapp at 0x104000000 (113 sectors)... Done
Writing lksecappbak at 0x104020000 (113 sectors)... Done
Writing cmnlib at 0x104040000 (386 sectors)... Done
Writing cmnlibbak at 0x104080000 (386 sectors)... Done
Writing cmnlib64 at 0x1040C0000 (484 sectors)... Done
Writing cmnlib64bak at 0x104100000 (484 sectors)... Done
Writing keymaster at 0x104140000 (442 sectors)... Done
Writing keymasterbak at 0x104180000 (442 sectors)... Done
Writing cust at 0x108082000 (852750 sectors)... Done
Writing userdata at 0x128082000 (278414 sectors)... Done
Writing BackupGPT at NUM_DISK_SECTORS-33. (33 sectors)... Done
Applying DISK patch... Done
Reset power ... Done

Flashing completed in 4 mins 56.943 s


Post a Comment

Post a Comment

Comment with your Google account if you’d like to be able to manage your comments in the future. If you comment anonymously, you won’t be able to edit or delete your comment.