oppo a16s after patch boot recovery has been destroyed [Answered] - GSM-Forum

pakistan786 · 06-27-2022, 11:54

Selected model: OPPO CPH2271 (Oppo A16s)
Operation: Repair
Software version: 3.7

Host Power Off... OK
Switch virtual port to NONE... OK
Connect Type-C to HUB... OK
Host Power On... OK
Connect phone to BOX in BROM/PRELOADER Mode
Wait for device connecting... OK
Driver: [MediaTek Inc.,wdm_usb,MediaTek PreLoader USB VCOM_V1633 (Android),usb2ser.sys,3.0.1504.0]
Device found at COM24 [PRELOADER]
Open port... OK
Send start cmd... OK
Get HW code from device... 0766
Get HW & SW version from device... OK
HW VER: CA00, SW VER: 0000, HW SUB CODE: 8A00
Detect chip [MT6765]
Library Version [2]
Select platform... OK
Init BROM... OK
Force Charge... OK
Disable WatchDog Timer... OK
Force switch to BROM... OK
Switch virtual port to USB... OK
Connect Type-C to BOX... OK
Host Power On... OK
Wait for device... OK
Read usbhost speed... HIGH
Read Device Descriptor...
Get VID/PID...0E8D/0003
Send start cmd... OK
Get HW code from device... 0766
Get HW & SW version from device... OK
HW VER: CA00, SW VER: 0000, HW SUB CODE: 8A00
Detect chip [MT6765]
Get sec config... OK [000000E5]
Active sec flags: [SBC DAA]
Advanced Bypass Security... OK
Disconnect virtual port... OK
Connect Type-C to HUB... OK
Wait for device connecting... OK
Driver: [MediaTek Inc.,wdm_usb,MediaTek USB Port_V1633,usb2ser.sys,3.0.1504.0]
Device found at COM25 [BROM]
Open port... OK
Send start cmd... OK
Get HW code from device... 0766
Get HW & SW version from device... OK
HW VER: CA00, SW VER: 0000, HW SUB CODE: 8A00
Detect chip [MT6765]
Library Version [2]
Select platform... OK
Init BROM... OK
Force Charge... OK
Disable WatchDog Timer... OK
Reopen port for libver2... OK
Get ME ID... OK
ME_ID = 0x0251B8F8, 0x0B3041AB, 0x4C9413E1, 0x604264E0
Get Chip ID... [MT6765]
Get SOC ID... [5EADC77B07DE6277F7B2D846766F50D99863A4F3FBA2AE0F4B 462C703683A641]
Get sec config... OK [000000E0]
Load DownloadAgent... OK
Search DA... OK [7]
Send preloader... OK
Start preloader... OK
Check preloader answer... OK
Send bootloader... OK
Start bootloader... OK
Wait for answer from bootloader... OK
Send SYNC signal... OK
Setup device enviroment... OK
Setup device parametres... OK
Receive DA SYNC signal... OK
Set DA parametres... OK
Get device connection agent... [BROM]
Get device info... OK
EMMC_ID: 0x13014E47314A395238101453AB4178FF
Load EMI from phone... OK
Parse EMI config... OK
Init EXT RAM... OK
Send 2nd DA... OK
Get device info... OK
EMMC INFO:
EMMC_ID : 0x13014E47314A395238101453AB4178FF
EMMC_BOOT1: 0x0000400000 (4.00Mb)
EMMC_BOOT2: 0x0000400000 (4.00Mb)
EMMC_RPMB : 0x0001000000 (16.00Mb)
EMMC_USER : 0x0E8F800000 (58.24Gb)
RAM INFO:
INT_SRAM: 0x000003A000 (232.00Kb)
EXT_RAM : 0x0100000000 (4.00Gb)
Check USB status... USB_HIGH_SPEED
Read partitions info from phone... OK
Check A/B state... OK
Read product info... OK
Product Brand : alps
Product Manufacturer : alps
Product Model : oplus_mssi_64_cn
Product Name : sys_oplus_mssi_64_cn
Product Device : oplus_mssi_64_cn
Product Board : oppo6765
Board Platform : MT6765
Build ID : RP1A.200720.011
Build Date : Tue Apr 19 23:49:27 CST 2022
Display ID : RP1A.200720.011 release-keys
Security Patch : 2022-04-05
Version SDK : 30
Version Release : 11
Version Codename : REL
Firmware Version : 1650382511772
Read partition "nvdata"... OK
Read partition "nvram"... OK
Read NVDATA files... OK
Read NVRAM files... OK
Repairing IMEI...
IMEI 1:
IMEI 2:
Write IMEI [NVDATA]... OK
Checking patch type... [2]
Load partiton for patching... OK
Patching CERT... OK
Save patched partiton... OK
Read partitions info from phone... OK
Check A/B state... OK
Read security partition from phone... OK
Decrypt security data... OK
Encrypt security data... OK
Write security partition to phone... OK
Write IMEI [NVRAM]... OK
Write partition "nvdata"... OK
Write partition "nvram"... OK
Repair Security done!
If your phone after repair keeps rebooting - use wipe data option.

after that boot recovery error after write boot recovery file imei nulll

Z3X · 06-27-2022, 12:03

Hello. Write nvdata from another alive phone and repeat operation. Post result.

pakistan786 · 06-27-2022, 12:09

Quote:

Originally Posted by Z3X

Hello. Write nvdata from another alive phone and repeat operation. Post result.

butt after patch again same
try 3 time same

Z3X · 06-27-2022, 12:34

Try with older firmware. If still same - read partitions dump (except userdata and cache) and upload it. We will recheck issue.

pakistan786 · 06-27-2022, 12:50

Quote:

Originally Posted by Z3X

Try with older firmware. If still same - read partitions dump (except userdata and cache) and upload it. We will recheck issue.

canot upload dump becuse poor intenet
if u have downgrade file orking link plz post

pakistan786 · 06-28-2022, 11:57

Quote:

Originally Posted by pakistan786

canot upload dump becuse poor intenet
if u have downgrade file orking link plz post

plz post solution or working downgrade flash file need

Z3X · 06-28-2022, 12:23

https://support.halabtech.com/index....lder&id=128028

mjs001 · 06-28-2022, 13:39

I have cph2271 and only reboot recovery
flash latest file on halabtech but not fixed
please upload a correct file for this model

mjs001 · 06-28-2022, 13:42

no any : c
version for this model
all c version files on halabt3vh for another model

my phone have c version before flashing
but now I cannot find this version��

can any one dump and upload cph2271 file pls ��

pakistan786 · 06-28-2022, 16:31

my a16s version cph2271VF_11_a.15 which firmware suiteable plz sugest
try CPH2271export_11_A.06
and this CPH2271export_11_A.04 butt not working

Z3X · 06-28-2022, 16:52

Not working what? Phone or repair? Try another firmware one by one, untill sucess.

06-27-2022, 11:54	#1 (permalink)
pakistan786 Freak Poster Join Date: Dec 2010 Location: gujrat pakistan Posts: 388 Member: 1462894 Status: Offline Sonork: 100.1609879 Thanks Meter: 47	oppo a16s after patch boot recovery has been destroyed [Answered] Selected model: OPPO CPH2271 (Oppo A16s) Operation: Repair Software version: 3.7 Host Power Off... OK Switch virtual port to NONE... OK Connect Type-C to HUB... OK Host Power On... OK Connect phone to BOX in BROM/PRELOADER Mode Wait for device connecting... OK Driver: [MediaTek Inc.,wdm_usb,MediaTek PreLoader USB VCOM_V1633 (Android),usb2ser.sys,3.0.1504.0] Device found at COM24 [PRELOADER] Open port... OK Send start cmd... OK Get HW code from device... 0766 Get HW & SW version from device... OK HW VER: CA00, SW VER: 0000, HW SUB CODE: 8A00 Detect chip [MT6765] Library Version [2] Select platform... OK Init BROM... OK Force Charge... OK Disable WatchDog Timer... OK Force switch to BROM... OK Switch virtual port to USB... OK Connect Type-C to BOX... OK Host Power On... OK Wait for device... OK Read usbhost speed... HIGH Read Device Descriptor... Get VID/PID...0E8D/0003 Send start cmd... OK Get HW code from device... 0766 Get HW & SW version from device... OK HW VER: CA00, SW VER: 0000, HW SUB CODE: 8A00 Detect chip [MT6765] Get sec config... OK [000000E5] Active sec flags: [SBC DAA] Advanced Bypass Security... OK Disconnect virtual port... OK Connect Type-C to HUB... OK Wait for device connecting... OK Driver: [MediaTek Inc.,wdm_usb,MediaTek USB Port_V1633,usb2ser.sys,3.0.1504.0] Device found at COM25 [BROM] Open port... OK Send start cmd... OK Get HW code from device... 0766 Get HW & SW version from device... OK HW VER: CA00, SW VER: 0000, HW SUB CODE: 8A00 Detect chip [MT6765] Library Version [2] Select platform... OK Init BROM... OK Force Charge... OK Disable WatchDog Timer... OK Reopen port for libver2... OK Get ME ID... OK ME_ID = 0x0251B8F8, 0x0B3041AB, 0x4C9413E1, 0x604264E0 Get Chip ID... [MT6765] Get SOC ID... [5EADC77B07DE6277F7B2D846766F50D99863A4F3FBA2AE0F4B 462C703683A641] Get sec config... OK [000000E0] Load DownloadAgent... OK Search DA... OK [7] Send preloader... OK Start preloader... OK Check preloader answer... OK Send bootloader... OK Start bootloader... OK Wait for answer from bootloader... OK Send SYNC signal... OK Setup device enviroment... OK Setup device parametres... OK Receive DA SYNC signal... OK Set DA parametres... OK Get device connection agent... [BROM] Get device info... OK EMMC_ID: 0x13014E47314A395238101453AB4178FF Load EMI from phone... OK Parse EMI config... OK Init EXT RAM... OK Send 2nd DA... OK Get device info... OK EMMC INFO: EMMC_ID : 0x13014E47314A395238101453AB4178FF EMMC_BOOT1: 0x0000400000 (4.00Mb) EMMC_BOOT2: 0x0000400000 (4.00Mb) EMMC_RPMB : 0x0001000000 (16.00Mb) EMMC_USER : 0x0E8F800000 (58.24Gb) RAM INFO: INT_SRAM: 0x000003A000 (232.00Kb) EXT_RAM : 0x0100000000 (4.00Gb) Check USB status... USB_HIGH_SPEED Read partitions info from phone... OK Check A/B state... OK Read product info... OK Product Brand : alps Product Manufacturer : alps Product Model : oplus_mssi_64_cn Product Name : sys_oplus_mssi_64_cn Product Device : oplus_mssi_64_cn Product Board : oppo6765 Board Platform : MT6765 Build ID : RP1A.200720.011 Build Date : Tue Apr 19 23:49:27 CST 2022 Display ID : RP1A.200720.011 release-keys Security Patch : 2022-04-05 Version SDK : 30 Version Release : 11 Version Codename : REL Firmware Version : 1650382511772 Read partition "nvdata"... OK Read partition "nvram"... OK Read NVDATA files... OK Read NVRAM files... OK Repairing IMEI... IMEI 1: IMEI 2: Write IMEI [NVDATA]... OK Checking patch type... [2] Load partiton for patching... OK Patching CERT... OK Save patched partiton... OK Read partitions info from phone... OK Check A/B state... OK Read security partition from phone... OK Decrypt security data... OK Encrypt security data... OK Write security partition to phone... OK Write IMEI [NVRAM]... OK Write partition "nvdata"... OK Write partition "nvram"... OK Repair Security done! If your phone after repair keeps rebooting - use wipe data option. after that boot recovery error after write boot recovery file imei nulll

06-28-2022, 16:31	#10 (permalink)
pakistan786 Freak Poster Join Date: Dec 2010 Location: gujrat pakistan Posts: 388 Member: 1462894 Status: Offline Sonork: 100.1609879 Thanks Meter: 47	my phone version cph2271VF_11_a.15 my a16s version cph2271VF_11_a.15 which firmware suiteable plz sugest try CPH2271export_11_A.06 and this CPH2271export_11_A.04 butt not working

06-27-2022, 12:03	#2 (permalink)
Z3X Product Supporter Join Date: Feb 2008 Location: z3x Posts: 15,935 Member: 706257 Status: Offline Thanks Meter: 5,057	Hello. Write nvdata from another alive phone and repeat operation. Post result.

06-27-2022, 12:34	#4 (permalink)
Z3X Product Supporter Join Date: Feb 2008 Location: z3x Posts: 15,935 Member: 706257 Status: Offline Thanks Meter: 5,057	Try with older firmware. If still same - read partitions dump (except userdata and cache) and upload it. We will recheck issue.

06-28-2022, 12:23	#7 (permalink)
Z3X Product Supporter Join Date: Feb 2008 Location: z3x Posts: 15,935 Member: 706257 Status: Offline Thanks Meter: 5,057	https://support.halabtech.com/index....lder&id=128028

06-28-2022, 13:39	#8 (permalink)
mjs001 Crazy Poster Join Date: Mar 2015 Location: iran Posts: 50 Member: 2365404 Status: Offline Thanks Meter: 9	I have cph2271 and only reboot recovery flash latest file on halabtech but not fixed please upload a correct file for this model

06-28-2022, 13:42	#9 (permalink)
mjs001 Crazy Poster Join Date: Mar 2015 Location: iran Posts: 50 Member: 2365404 Status: Offline Thanks Meter: 9	no any : c version for this model all c version files on halabt3vh for another model my phone have c version before flashing but now I cannot find this version�� can any one dump and upload cph2271 file pls ��

06-28-2022, 16:52	#11 (permalink)
Z3X Product Supporter Join Date: Feb 2008 Location: z3x Posts: 15,935 Member: 706257 Status: Offline Thanks Meter: 5,057	Not working what? Phone or repair? Try another firmware one by one, untill sucess.