vivo y17 bootloop after erase user data

bigbag

vivo y17 pin lock, after erase user data with ufi, only hang logo then restart.

Model: Vivo Y17
name: MTK_PLATFORM_CFG
version: V1.1.2
platform: MT6765
project: k62v1_64_bsp
storage: EMMC
bootChannel: MSDC_0
blockSize: 0x00020000
MTK Preloader file info.
Found 4 supported eMMC CID:
[Samsung] RD64MB 15010052 4436344D 42xxxxxx xxxxxxxx
[Samsung] RH64AB 15010052 48363441 42xxxxxx xxxxxxxx
[Samsung] GD6BMB 15010047 4436424D 42xxxxxx xxxxxxxx
[SK Hynix] HBG4a2 90014A48 42473461 32xxxxxx xxxxxxxx
AUTH info: MTK, version: 1
BROM version[1]: 7.1917.3.0
DownloadAgent: DA_PL.bin
hash: f5b40a757b95c0d4e4ab1a1fdbb2522750568e6c, size: 528.48 KiB
version: 3.3001.2018/03/22019/08/22 11:18:23, start addr: 0x40000800
Connecting to BootROM...
Power off the phone, disconnect and reconnect the battery(if possible) and connect USB cable...
Hold the VOL UP to force MediaTek BootROM.
Scanning BootROM or Preloader port(30 s)... Done.
Detected [PL] MediaTek PreLoader USB VCOM_V1632 (Android) (COM57)
Connection status: EHCI:HUB:USB 2.00 High-Speed
USB Driver: [MediaTek Inc.] wdm_usb, version: 3.0.1504.0, date: 1-22-2015
Connecting Bootrom...
Sending Download Agent...
Platform: MT6765, Hw ver: 0xCA00, Sw ver: 0x0000
Secure ver: 0x00, BL ver: 0x00
Secure config: 0x00
SRAM size: 256 KiB
DRAM size: 768 MiB
Storage type: eMMC
Card/BGA: BGA (Discrete embedded)
Manufacturer ID: 0x15 (Samsung)
Product name: DV6DMB (0x445636444d42), rev: 0x02, serial number: 0xA3F96AD9
Manufacturing date: Nov 2018
CID: 15010044 5636444D 4202A3F9 6AD9B50B
Capacity: 116.50 GiB(125,095,116,800 bytes)
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 16384 KiB (key exist)
User area: 116.48 GiB(125,069,950,976 bytes)
USB speed: High-Speed
platform: MT6765, cpu abi: arm64-v8a
manufacturer: vivo
board: k65v1_64_bsp, name: full_k65v1_64_bsp
brand: vivo, model: vivo 1902
build id: PPR1.180610.011, version: 9 Pie (PPR1.180610.011 release-keys)
build description: full_k65v1_64_bsp-user 9 PPR1.180610.011 compiler07090014 release-keys
crypto state: encrypted
AUTH info: MTK, version: 1
BROM version[1]: 7.1917.3.0
DownloadAgent: DA_PL.bin
hash: f5b40a757b95c0d4e4ab1a1fdbb2522750568e6c, size: 528.48 KiB
version: 3.3001.2018/03/22019/08/22 11:18:23, start addr: 0x40000800
Connecting to BootROM...
Power off the phone, disconnect and reconnect the battery(if possible) and connect USB cable...
Hold the VOL UP to force MediaTek BootROM.
Scanning BootROM or Preloader port(30 s)... Done.
Detected [BootROM] MediaTek USB Port_V1632 (COM3)
Connection status: EHCI:HUB:USB 1.10 High-Speed
USB Driver: [MediaTek Inc.] wdm_usb, version: 3.0.1504.0, date: 1-22-2015
Connecting Bootrom...
Sending Download Agent...
Platform: MT6765, Hw ver: 0xCA00, Sw ver: 0x0000
Secure config: 0x00
Error: -1073283068 (STATUS_DA_HASH_MISMATCH)
AUTH info: MTK, version: 1
BROM version[1]: 7.1917.3.0
DownloadAgent: DA_PL.bin
hash: f5b40a757b95c0d4e4ab1a1fdbb2522750568e6c, size: 528.48 KiB
version: 3.3001.2018/03/22019/08/22 11:18:23, start addr: 0x40000800
Connecting to BootROM...
Power off the phone, disconnect and reconnect the battery(if possible) and connect USB cable...
Hold the VOL UP to force MediaTek BootROM.
Scanning BootROM or Preloader port(30 s)... Done.
Detected [BootROM] MediaTek DA USB VCOM (Android) (COM109)
Connection status: EHCI:HUB:USB 1.10 High-Speed
USB Driver: [MediaTek Inc.] wdm_usb, version: 3.0.1504.0, date: 1-22-2015
Connecting Bootrom...
Error: -1073348607 (STATUS_BROM_CMD_STARTCMD_FAIL)
[BROM] Can not pass bootrom start command! Possibly target power up too early.
Please press power button for 10 secs or disconnect and reconnect the battery(if possible) and retry!
(boot_rom.cpp, line:103)
AUTH info: MTK, version: 1
BROM version[1]: 7.1917.3.0
DownloadAgent: DA_PL.bin
hash: f5b40a757b95c0d4e4ab1a1fdbb2522750568e6c, size: 528.48 KiB
version: 3.3001.2018/03/22019/08/22 11:18:23, start addr: 0x40000800
Connecting to BootROM...
Power off the phone, disconnect and reconnect the battery(if possible) and connect USB cable...
Hold the VOL UP to force MediaTek BootROM.
Scanning BootROM or Preloader port(30 s)... Done.
Detected [PL] MediaTek PreLoader USB VCOM_V1632 (Android) (COM57)
Connection status: EHCI:HUB:USB 2.00 High-Speed
USB Driver: [MediaTek Inc.] wdm_usb, version: 3.0.1504.0, date: 1-22-2015
Connecting Bootrom...
Sending Download Agent...
Platform: MT6765, Hw ver: 0xCA00, Sw ver: 0x0000
Secure ver: 0x00, BL ver: 0x00
Secure config: 0x00
SRAM size: 256 KiB
DRAM size: 768 MiB
Storage type: eMMC
Card/BGA: BGA (Discrete embedded)
Manufacturer ID: 0x15 (Samsung)
Product name: DV6DMB (0x445636444d42), rev: 0x02, serial number: 0xA3F96AD9
Manufacturing date: Nov 2018
CID: 15010044 5636444D 4202A3F9 6AD9B50B
Capacity: 116.50 GiB(125,095,116,800 bytes)
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 16384 KiB (key exist)
User area: 116.48 GiB(125,069,950,976 bytes)
USB speed: High-Speed
Erasing userdata [0x1DF800000-0x1D1B0FBDFF]... Done.
Completed in 23.789 s

thedaos

bigbag maybe you got the wrong way, try again "factory reset" not "erase userdata".
Or try flashing again

bigbag

madgoeslim

bigbag Hello,
For vivo phones, avoid using factory reset for clearing the user lock problem.
Write userdata.img from firmware to fix such issue.

bigbag

flashing firmware failed

AUTH info: MTK, version: 1
Firmware package: [firmware27]PD1901F_EX_A_1.11.0_vivo_mtk_alps-release-p0.mp3-pre3_mtk6771
BROM version[1]: 7.1917.3.0
DownloadAgent: DA_PL.bin
hash: f5b40a757b95c0d4e4ab1a1fdbb2522750568e6c, size: 528.48 KiB
version: 3.3001.2018/03/22019/08/22 15:58:06, start addr: 0x40000800
Connecting to BootROM...
Power off the phone, disconnect and reconnect the battery(if possible) and connect USB cable...
Hold the VOL UP to force MediaTek BootROM.
Scanning BootROM or Preloader port(30 s)... Done.
Detected [PL] MediaTek PreLoader USB VCOM_V1632 (Android) (COM57)
Connection status: EHCI:HUB:USB 2.00 High-Speed
USB Driver: [MediaTek Inc.] wdm_usb, version: 3.0.1504.0, date: 1-22-2015
Connecting Bootrom...
Sending Download Agent...
Platform: MT6765, Hw ver: 0xCA00, Sw ver: 0x0000
Secure ver: 0x00, BL ver: 0x00
Secure config: 0x00
SRAM size: 256 KiB
DRAM size: 768 MiB
Storage type: eMMC
Card/BGA: BGA (Discrete embedded)
Manufacturer ID: 0x15 (Samsung)
Product name: DV6DMB (0x445636444d42), rev: 0x02, serial number: 0xA3F96AD9
Manufacturing date: Nov 2018
CID: 15010044 5636444D 4202A3F9 6AD9B50B
Capacity: 116.50 GiB(125,095,116,800 bytes)
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 16384 KiB (key exist)
User area: 116.48 GiB(125,069,950,976 bytes)
USB speed: High-Speed
Verifying SoC: passed
Verifying CID: passed
Writing preloader, size: 244.63 KiB
Writing recovery, size: 64 MiB
Error: 0xC0020029 (STATUS_SEC_IMGHDR_TYPE_MISMATCH)

bigbag

thedaos yes maybe, but in older vivo erase userdata always successful,
I have tried flashing but come error "Error: 0xC0020029 (STATUS_SEC_IMGHDR_TYPE_MISMATCH)"

thedaos

ok bro, and have you tried factory reset on ufi ?

bigbag

thedaos yes i already factory reset but still bootloop.

bigbag

problem solved. just install updater.zip via sdcard.

thedaos

Good idea, good job 😆

bigbag

madgoeslim yes that was a mistake, i erase user data. but for MTK flashing the error always appears
"Error: 0xC0020029 (STATUS_SEC_IMGHDR_TYPE_MISMATCH)" I tried it on two different phone Vivo Y17 and Oppo F5 new security.

ianmorh

Hi i have the same problem with vivo y1s but mine seems worse. After formating the phone with sp flash tool, it went dead. I then flashed the stock rom but pre loader, recovery etc were successful but the survival, and cust image files could not showing verified boot is enabled. Now the phone only reboots and can access recovery but not fast boot mode. Any assistance or help would be highly appreciated!