If You Have Any Problem Using Box Or Any Problem Recover Set Post Here

Ahmadaim1

Product Supporter
Aug 10, 2018
209
109
Nigeria
oppo A7 cph1901 emmc change process plz help mi
Dump Security file from old emmc if possible

Download supported dump full or bootrepair

Then write it on your new emmc and write your backup security files

If it's boot repair file u need to write full flash after repair
 

Asif Mansuri

Junior Member
Apr 20, 2019
2
0
Dump Security file from old emmc if possible

Download supported dump full or bootrepair

Then write it on your new emmc and write your backup security files

If it's boot repair file u need to write full flash after repair
i have only security file i dont have dump for old emmc can posibal to set alive
 

Msnoman

Junior Member
Jul 6, 2020
2
0
Hassan
Connection status: EHCI:HUB:HUB:USB 2.00 High-Speed
Interface: UFI High-Speed
Serial number: 0011-8840-1705
Boot version: 1.04, FW version: 1.13 (Aug 19 2019 23:46:09)
Insertion test... Done
Init bus...
VCC: 3.3 V, VCCQ: 2.8 V
Bus: 1 bit (SDR 3MHz)
Access mode: sector mode
Power supply: dual-voltage (1.70-1.95V, 2.7-3.6V)
Card/BGA: BGA (Discrete embedded) - High density MMC
Manufacturer ID: 0x15 (Samsung)
Product name: R821MB (0x523832314d42), rev: 0x00, serial number: 0x31FFCE10
Manufacturing date: May 2015
CID: 15010052 3832314D 420031FF CE1052EE
CSD: D0270132 0F5903FF F6DBFFEF 92404008
EXT_CSD revision: 1.7 (MMC v5.0, v5.01)
Partition info:
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 4096 KiB
User area: 14.56 GiB(15,634,268,160 bytes)

moviNAND rewrite CID ... failed!
 

Msnoman

Junior Member
Jul 6, 2020
2
0
Hassan
onnection status: EHCI:HUB:HUB:USB 2.00 High-Speed
Interface: UFI High-Speed
Serial number: 0011-8840-1705
Boot version: 1.04, FW version: 1.13 (Aug 19 2019 23:46:09)
Insertion test... Done
Init bus...
VCC: 3.3 V, VCCQ: 2.8 V
Bus: 1 bit (SDR 24MHz)
Access mode: sector mode
Power supply: dual-voltage (1.70-1.95V, 2.7-3.6V)
Card/BGA: BGA (Discrete embedded) - High density MMC
Manufacturer ID: 0x15 (Samsung)
Product name: R821MB (0x523832314d42), rev: 0x00, serial number: 0x31FFCE10
Manufacturing date: May 2015
CID: 15010052 3832314D 420031FF CE1052EE
CSD: D0270132 0F5903FF F6DBFFEF 92404008
EXT_CSD revision: 1.7 (MMC v5.0, v5.01)
Partition info:
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 4096 KiB
User area: 14.56 GiB(15,634,268,160 bytes)

Current partition access:
Access to boot partition 1
Writing random bytes to boot1, sector: 0... Failed to write block 0x00000000:1024 (return code: 36, Transmission Error: Data CRC fail)
cmd response: 0xD00, card status: 0x0, card state: 6 (Card is receiving operation information)
status: unknown (0)
NAND storage "boot1" partition test failed!
all emmc write error
 

amr ibrahim

Junior Member
Jul 12, 2020
2
0
egypt
Suddenly this message appeared to me with many phone
 

Attachments

  • 32ceec12-18d9-400a-8954-a7ac31af214c.jpg
    32ceec12-18d9-400a-8954-a7ac31af214c.jpg
    72.4 KB · Views: 13
  • f968ad95-3a1a-446d-ac98-12a63362cd27.jpg
    f968ad95-3a1a-446d-ac98-12a63362cd27.jpg
    53.3 KB · Views: 13

jasheer

Active Member
Dec 4, 2018
21
0
cant partition

EXT_CSD revision: 1.8 (MMC v5.1)
Partition info:
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 4096 KiB
User area: 58.24 GiB(62,537,072,640 bytes)
Cache size: 1 MiB
Hardware reset function: 1
Partition configuration: 0x00
No boot acknowledge is sent (default)
Device is not boot-enabled (default)
Partitioning support: 0x07
Device support partitioning feature
Device can have enhanced technological features
Device partitioning completed
Boot configuration protection: 0x00
Boot bus conditions: 0x00
Boot area write protection: 0x00
Power-on write protection: possible
Permanent write protection: possible
Lock status: not locked
User area write protection: 0x50
Password protection features: enabled
Power-on write protection: possible
Permanent write protection: not possible
Lock status: not locked
eMMC 5.x HEALTH report:
Device lifetime: Urgent (Consumed 90% of the reserved block)
Estimation of the device lifetime (SLC): 0% - 10% device life time used
Estimation of the device lifetime (MLC): 30% - 40% device life time used
Selected: [HYNIX] H9TQ52ACLTMCUR/64GB (BGA221)
 

jasheer

Active Member
Dec 4, 2018
21
0
after partitio show like this again sir

VCC: 3.3 V, VCCQ: 1.8 V
Bus: 1 bit (SDR 24MHz)
Access mode: sector mode
Power supply: dual-voltage (1.70-1.95V, 2.7-3.6V)
Card/BGA: BGA (Discrete embedded) - High density MMC
Manufacturer ID: 0x90 (SK Hynix)
Product name: HCG8a4 (0x484347386134), rev: 0xA4, serial number: 0x4905E9A5
Manufacturing date: Aug 2018
CID: 90014A48 43473861 34A44905 E9A585FC
CSD: D0270132 8F5903FF FFFFFFEF 8A400026
EXT_CSD revision: 1.8 (MMC v5.1)
Partition info:
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 4096 KiB
User area: 58.24 GiB(62,537,072,640 bytes)

Writing eMMC partition settings...
Device is already partitioned



PMB: 4096 KiB
User area: 58.24 GiB(62,537,072,640 bytes)
Cache size: 1 MiB
Hardware reset function: 1
Partition configuration: 0x00
No boot acknowledge is sent (default)
Device is not boot-enabled (default)
Partitioning support: 0x07
Device support partitioning feature
Device can have enhanced technological features
Device partitioning completed
Boot configuration protection: 0x00
Boot bus conditions: 0x00
Boot area write protection: 0x00
Power-on write protection: possible
Permanent write protection: possible
Lock status: not locked
User area write protection: 0x50
Password protection features: enabled
Power-on write protection: possible
Permanent write protection: not possible
Lock status: not locked
eMMC 5.x HEALTH report:
Device lifetime: Urgent (Consumed 90% of the reserved block)
Estimation of the device lifetime (SLC): 0% - 10% device life time used
Estimation of the device lifetime (MLC): 30% - 40% device life time used
Selected: [HYNIX] H9TQ52ACLTMCUR/64GB (BGA221)
 

Buharee Dole

Junior Member
Oct 5, 2017
2
1
Accra
Please help,
After #keepworking#staysafe update, can't do any operation again. Can't identify device, can't flash, can't view my account and credit. Always authentication aborted by user request.
Please check it for me experts.
 

Attachments

  • 1598214192692824251343724693763.jpg
    1598214192692824251343724693763.jpg
    230.6 KB · Views: 9

Wilmer85

Member
Aug 17, 2019
8
0
Goodnight. I have a problem with a Xiaomi Redmi Note 8 Pro. Perform an operation to unlock the Bootloader to unbrick the phone. But I did not carry out the process and I consumed credits. What should I do to get my credits refunded and redo the process. I attach the log of the process. If you need photos, I can also send them

UFI Software version: 1.5.0.1818
PC Info: 832A,PGNELM3NM87DRG
User Info: UFIBox/0011-8841-9131,0011-8553-3153
Processor: Intel(R) Core(TM) i5-7200U CPU 2.71 GHz (4 CPUs)
Memory: 7.92 GiB (59 % free)
OS: Windows 10 (Build 17763, Version: 1809, 64-bit)
---------
AUTH info: MTK, version: 1
> Credit confirmation status: 1
BROM version[1]: 7.1922.6.0
DA: MTK_AllInOne_DA[1].bin
hash: 29541b6af15c397977fb6c85df452c0add11ca18, size: 1.01 MiB
version: 3.3001.2019/06/02020/12/04 01:11:36, start addr: 0x40000800
Connecting to BootROM...
Power off the phone, disconnect and reconnect the battery(if possible) and connect USB cable...
Hold the VOL DOWN or VOL UP + DOWN(for newer model) to force MediaTek BootROM.
Scanning BootROM or Preloader port(30 s)... Done
Detected [BootROM] MediaTek USB Port_V1632 (COM56)
Connection status: XHCI:HUB3:USB 2.00 High-Speed
USB Driver: [MediaTek Inc.] wdm_usb, version: 3.0.1504.0, date: 1-22-2015
Connecting Bootrom...
> Session confirmation status: 1
Requesting flash signature from server...
[SERVER] XIAOMI_FL [begonia,b660eb0d005a5434] ref id: XF06413122162, cost: 4, your balance: 2
Sending Download Agent...
Platform: MT6785, Hw ver: 0xCA00, Sw ver: 0x0000
Secure ver: 0x00, BL ver: 0x00
SRAM size: 512 KiB
DRAM size: 6 GiB
SOC ID: b660eb0d005a5434909aab13432ef8a668fdf50b9028b64eea80736ab7b23207
ME ID: 0a8a739179614fc5290d29e280d40e84
Storage type: UFS
Storage id: H9HQ16AECMMDAR
Fw version:
Capacity: 119.18 GiB(127,968,215,040 bytes)
LUN0: 4096 KiB
LUN1: 4096 KiB
LUN2: 119.17 GiB(127,959,826,432 bytes)
USB speed: High-Speed
Verifying Soc: passed
Verifying Storage ID: passed
Writing preloader: preloader_begonia.bin, size: 313.57 KiB
Writing recovery: recovery.img, size: 64 MiB
Writing vbmeta: vbmeta.img, size: 4 KiB
Writing efuse: efuse.img, size: 512 bytes
Writing md1img: md1img.img, size: 58.93 MiB
Writing spmfw: spmfw.img, size: 14.97 KiB
Writing audio_dsp: audio_dsp.img, size: 1.26 MiB
Writing scp1: scp.img, size: 1.68 MiB
Writing scp2: scp.img, size: 1.68 MiB
Writing sspm_1: sspm.img, size: 645.44 KiB
Writing sspm_2: sspm.img, size: 645.44 KiB
Writing cam_vpu1: cam_vpu1.img, size: 1.10 MiB
Writing cam_vpu2: cam_vpu2.img, size: 8.53 MiB
Writing cam_vpu3: cam_vpu3.img, size: 6.05 MiB
Writing gz1: gz.img, size: 13.79 MiB
Writing gz2: gz.img, size: 13.79 MiB
Writing lk: lk.img, size: 1.16 MiB
Writing lk2: lk.img, size: 1.16 MiB
Writing boot: boot.img, size: 64 MiB
Writing logo: logo.bin, size: 2.73 MiB
Writing dtbo: dtbo.img, size: 32 MiB
Writing tee1: tee.img, size: 2.42 MiB
Writing tee2: tee.img, size: 2.42 MiB
Writing vendor: vendor.img, size: 894.71 MiB
Writing system: system.img, size: 3.32 GiB
Writing cache: cache.img, size: 176.19 KiB
Writing gsort: gsort.img, size: 16 KiB
Writing oem_misc1: oem_misc1.img, size: 16 KiB
Writing exaid: exaid.img, size: 16 KiB
Writing userdata: userdata.img, size: 811.29 MiB
Completed in 3 mins 38.110 s
 

omer1950

Junior Member
Dec 31, 2020
1
0
turkey
Hi, I have flashed 4 times by ufi dongle and the flashing method was failed also I havd lost 12 credit for flashing and nothing done so I am waiting you to take a look and refund my credit
 
Top