View Single Post
Old 01-29-2021, 05:44   #1102 (permalink)
Dipendra Pathak
Product Manager
 
Dipendra Pathak's Avatar
 
Join Date: Apr 2008
Location: Whitehole throught Blackhole!
Posts: 9,582
Member: 747989
Status: Offline
Sonork: 100.1593052
Thanks Meter: 8,621
Vivo Y20 PD2034F Forced Erease to remove FRP and userdata successfully done by Hydra

Vivo Y20 PD2034F Forced Erease to remove FRP and userdata successfully done by Hydra Tool

Screen Short:



Logs:

Quote:
PreOperation Configuration
Brand : VIVO Model : Y20 PD2034F Storage : Auto
Loader: Vivo_Y20i_PD2034F_ddr.elf
Port : Auto
Connection :

Searching for Qualcomm 9008 Device...Found
FriendlyName :Qualcomm HS-USB QDLoader 9008 (COM43)
SymbolicName :\??\USB#VID_05C6&PID_9008#8&3b333475&0&3#{a5dcbf1 0-6530-11d2-901f-00c04fb951ed}
Driver Ver :08/02/2017,2.1.2.7

Getting device info......
Serial No.: 0x25537092
MSM ID : 0x001360E1,
PBL Ver : 00000000
PK HASH : A7DF36FFD7AB557C67A6C26675E2795C
922CF671308CFD7169BEDB84424C862B

Firehose Loader[Vivo_Y20i_PD2034F_ddr.elf]
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 : 462
Serial Number : 1297306958
Firmware Version : 300
Product Name : KM5H80018M-B424
Physical Partitions : 6
Total Logical Blocks:
Drive [0] 15337472[58,508 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] ERROR: The operation is not allowed for read...
Drive [1] ERROR: The operation is not allowed for read...
Drive [2] ERROR: The operation is not allowed for read...
Drive [3] ERROR: The operation is not allowed for read...
Drive [4] ERROR: The operation is not allowed for read...
Drive [5] ERROR: The operation is not allowed for read...

Processing Forced Erase....
- Forced Erase frp Ok
- Forced Erase userdata Ok
Action Result : Ok

Elapsed Time : 00:00:33
BR
Dipendra Pathak

  Reply With Quote
 
Page generated in 0.07901 seconds with 7 queries