Y20s (PD2034F) Cannot Remove Screen Lock ;(

[..::GMSR::..]

******* Dongle Info *******
Version : Hydra Tool v 1.2
Serial : 200900008395
Initialize : OKAY
Status : Activated
Life : 0 [0-0-0-0-0]

PreOperation Configuration
Brand : VIVO Model : Y20s (PD2034F) Storage : Auto
Loader: Vivo_Y20i_PD2034F_ddr.elf
Port : Auto

Searching for Qualcomm 9008 Device...Found
FriendlyName :Qualcomm HS-USB QDLoader 9008 (COM23)
SymbolicName :\??\USB#VID_05C6&PID_9008#5&27c6eb94&0&1#{a5dcbf1 0-6530-11d2-901f-00c04fb951ed}
Driver Ver :02/05/2018,3.0.0.0

Getting device info......
Serial No.: 0x0675285B
HW_ID : 001360E100730003
MSM ID : 0x001360E1,
MODEL_ID : 0x0003
OEM_ID : 0x0073 - VIVO
PBL Ver : 00000000
PK HASH : a7df36ffd7ab557c67a6c26675e2795c922cf671308cfd7169 bedb84424c862b

Firehose Loader[Vivo_Y20i_PD2034F_ddr.elf]
--------------------------------------------------
Header Type : New
TargetMSM :
Tag : _ona
Version : 6
Code_size : 816
Signature_size : 256
fhVendor : VIVO
HW_ID : 0000000000730003
Vendor : VIVO
OEM_ID : 0073
MODEL_ID : 0003
SW_ID : 00000003
APP_ID : 00000000
pk_hash : a7df36ffd7ab557c67a6c26675e2795c922cf671308cfd7169 bedb84424c862bc7b646907dd79989578590fb6370a940
OEM_VERSION : comsz01078164
IMAGE_VARIANT : KamortaPkgLAA
QC_VERSION : BOOT.XF.4.1-00170-KAMORTALAZ-1
--------------------------------------------------

SaharaBoot... Ok
Sending .................................Ok
Connecting to Firehose...
Ping......................... Ok
Configuration........
Identifying Chip........UFS
Ok
Chip Configuration :
MemoryName : UFS
MaxPayloadSizeToTargetInBytes : 1048576
MaxPayloadSizeToTargetInBytesSupported : 1048576
MaxPayloadSizeFromTargetInBytes :
MaxXMLSizeInBytes : 4096
TargetName :
Version : 1
DateTime : Aug 21 2020 - 23:37:55

*** STORAGE DEVICE INFO ***
Memory Type : UFS
Block Size in Bytes : 4096
Page Size : 4096
Manufacturer ID : 300
Serial Number : 1129467726
Firmware Version : 109
Product Name : MT064GASAO2U21 0109
Physical Partitions : 6
Total Logical Blocks:
Drive [0] 15335424[58,5 GB]
Drive [1] 2048[8 MB]
Drive [2] 2048[8 MB]
Drive [3] 8192[32 MB]
Drive [4] 262144[1024 MB]
Drive [5] 8192[32 MB]

Protocol : Universal
Running : Ok
Reading GPT[6]
Drive [0] <?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" rawmode="false" /></data>ERROR: The operation is not allowed for read...
Drive [1] <?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" rawmode="false" /></data>ERROR: The operation is not allowed for read...
Drive [2] <?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" rawmode="false" /></data>ERROR: The operation is not allowed for read...
Drive [3] <?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" rawmode="false" /></data>ERROR: The operation is not allowed for read...
Drive [4] <?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" rawmode="false" /></data>ERROR: The operation is not allowed for read...
Drive [5] <?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" rawmode="false" /></data>ERROR: The operation is not allowed for read...

Processing Zero Wipe....
Operation Not Allowed..
You may try other method
Action Result : Failed

Elapsed Time : 00:00:07

[Dipendra Pathak]

use VIVO tab --> Force erase method


BR
Dipendra Pathak