If You Have Any Problem Using UFI Box Or Any Problem Recover Set Post Here
- Thread starter Deepesh Sharma
- Start date
Öncelikle ufi dongel satın aldığım tercümeyi kullandığım için özür dilerim sonra 30 kontör aldım 23 kontör kestim ama işlem yapmadığım için olumlu sonuçlar aldım Bugün 13 kontör daha yükledim yine 4 kontör yükledim redmi note 8 pro cihaz ne bootloader ne de micloud hesabı Kredilerimi kaldıramadım lütfen kredilerimi iade et
Failed on initializing library, error 2
help me please. I often get such an inscription, because of this inscription, during the withdrawal of my account or other operation, the Ufi software unexpectedly closes ... I have Windows 10. Please help me solve the problem ..
help me please. I often get such an inscription, because of this inscription, during the withdrawal of my account or other operation, the Ufi software unexpectedly closes ... I have Windows 10. Please help me solve the problem ..
Attachments
-
Безымянный.png
Miriletisim
Member
soc(CPU): Qualcomm Technologies, Inc MSM8953
memory(RAM): 4 GB
flash locked: yes
secure boot: yes (unlocked)
boot state: green
crypto state: encrypted (block)
boot serial no: 3bcb91fa0904
serial no: VT811Y066552
product serial no: 17197/00367313
boot region: cn
rom zone: 2
boot hwc: CN,
rpmb state: 23
baseband version: 953_GEN_PACK-1.174284.1.194887.2
ril version: Qualcomm RIL 1.0
sim state: ABSENT,ABSENT
android id: a3a5a8715c8217b9
client id: android-xiaomi-rev1
bt addr: 9c:2e:a1:59:fb:72
wifi mac: c:2e:a1:19:fb:6f
imei[1]: 866764034869218
imei[2]: 866764034869226
meid: 99001182143460
region: TR
locale: tr-TR
battery level: 88%
superuser: yes (18.0:MAGISKSU (topjohnwu))
selinux: enforcing
Enabling DIAG mode... Done
Waiting for COM to be ready... Done
Using Port: Qualcomm HS-USB Diagnostics 903A (COM3)
New imei[2]: 356336090709039
Writing new imei... failed to write imei[2] , error: 0 (Request completed okay)
Done
memory(RAM): 4 GB
flash locked: yes
secure boot: yes (unlocked)
boot state: green
crypto state: encrypted (block)
boot serial no: 3bcb91fa0904
serial no: VT811Y066552
product serial no: 17197/00367313
boot region: cn
rom zone: 2
boot hwc: CN,
rpmb state: 23
baseband version: 953_GEN_PACK-1.174284.1.194887.2
ril version: Qualcomm RIL 1.0
sim state: ABSENT,ABSENT
android id: a3a5a8715c8217b9
client id: android-xiaomi-rev1
bt addr: 9c:2e:a1:59:fb:72
wifi mac: c:2e:a1:19:fb:6f
imei[1]: 866764034869218
imei[2]: 866764034869226
meid: 99001182143460
region: TR
locale: tr-TR
battery level: 88%
superuser: yes (18.0:MAGISKSU (topjohnwu))
selinux: enforcing
Enabling DIAG mode... Done
Waiting for COM to be ready... Done
Using Port: Qualcomm HS-USB Diagnostics 903A (COM3)
New imei[2]: 356336090709039
Writing new imei... failed to write imei[2] , error: 0 (Request completed okay)
Done
hi
VCC: 3.3 V, VCCQ: 1.8 V
Failed to initialize eMMC (return code: 17, CMD Error: Timeout) !!!
CMD1 error, cmd response: 0x0, card state: 255 (Card is in unknown state)
SEND_OP_COND command failed.
--- Check eMMC pins and connection ---
--- Try to select correct VCC/VCCQ manually ---
--- Try to decrease the clock speed ---
VCC: 3.3 V, VCCQ: 1.8 V
Failed to initialize eMMC (return code: 17, CMD Error: Timeout) !!!
CMD1 error, cmd response: 0x0, card state: 255 (Card is in unknown state)
SEND_OP_COND command failed.
--- Check eMMC pins and connection ---
--- Try to select correct VCC/VCCQ manually ---
--- Try to decrease the clock speed ---
devthakur81
Active Member
i have a problem i need to recover data from mobile i tried with jumpers as well as emmc steps but everytime it not show file browser. what will i do. i have changrd win 7 32 and 64 both then win 10 32 and 64 both in every window ufi not showing file browser. is there any other software which i have to install. even i have tried with old ufi setup 1155. still i have the same problem . is there anyone in the team who can help me please
devthakur81
Active Member
hello. Meizu M8 5 credits, but not flashing. [email protected]
AUTH info: MTK, version: 1
Firmware package: 20181017221214_intl_russia_prd_stable_fvcs_rebuilt_stable_7.1.5.0RU.rar
BROM version[1]: 7.1917.3.0
DA: MTK_AllInOne_DA.bin
hash: 888483ce39bfccd068caf3cef6d70fe2116c3d6d, size: 537.33 KiB
version: 3.3001.2018/06/12020/10/19 16:39:29, 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 to force MediaTek BootROM.
Scanning BootROM or Preloader port... Done
Detected [BootROM] MediaTek USB Port (COM19)
Connection status: IUSB3HUB:USB 1.10 High-Speed
USB Driver: [MediaTek Inc.] usbser, version: 2.0.1136.0, date: 11-6-2014
Connecting Bootrom...
Requesting flash signature from server...
[SERVER] MEIZU_FL [M1813,15d3ffa0a09c9e66] ref id: MF01535938770, cost: 5, your balance: 5
Sending Download Agent...
Platform: MT6765, Hw ver: 0xCA00, Sw ver: 0x0000
Secure ver: 0x00, BL ver: 0x00
SRAM size: 256 KiB
DRAM size: 4 GiB
SOC ID: 15d3ffa0a09c9e668d5259e4bf39598c3b3060f4a011e73544ca5a8a55e925e5
ME ID: 00e58f21514262c1ba88ac664fe51e1e
Storage type: eMMC
Card/BGA: BGA (Discrete embedded)
Manufacturer ID: 0x90 (SK Hynix)
Product name: HCG8a4 (0x484347386134), rev: 0xA2, serial number: 0x4DA29A32
Manufacturing date: сен 2018
CID: 90014A48 43473861 34A24DA2 9A3295E7
Capacity: 58.25 GiB(62,549,655,552 bytes)
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 4096 KiB (key exist)
User area: 58.24 GiB(62,537,072,640 bytes)
USB speed: High-Speed
Verifying Soc: passed
Verifying Storage ID: passed
Writing preloader: preloader_K91813AA1.bin, size: 221.88 KiB
Error: 0xC0050003 (STATUS_DOWNLOAD_EXCEPTION)
Error while flashing images at 0x00000000, please make sure your USB connection is stable.
AUTH info: MTK, version: 1
Firmware package: 20181017221214_intl_russia_prd_stable_fvcs_rebuilt_stable_7.1.5.0RU.rar
BROM version[1]: 7.1917.3.0
DA: MTK_AllInOne_DA.bin
hash: 888483ce39bfccd068caf3cef6d70fe2116c3d6d, size: 537.33 KiB
version: 3.3001.2018/06/12020/10/19 16:39:29, 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 to force MediaTek BootROM.
Scanning BootROM or Preloader port... Done
Detected [BootROM] MediaTek USB Port (COM19)
Connection status: IUSB3HUB:USB 1.10 High-Speed
USB Driver: [MediaTek Inc.] usbser, version: 2.0.1136.0, date: 11-6-2014
Connecting Bootrom...
Requesting flash signature from server...
[SERVER] MEIZU_FL [M1813,15d3ffa0a09c9e66] ref id: MF01535938770, cost: 5, your balance: 5
Sending Download Agent...
Platform: MT6765, Hw ver: 0xCA00, Sw ver: 0x0000
Secure ver: 0x00, BL ver: 0x00
SRAM size: 256 KiB
DRAM size: 4 GiB
SOC ID: 15d3ffa0a09c9e668d5259e4bf39598c3b3060f4a011e73544ca5a8a55e925e5
ME ID: 00e58f21514262c1ba88ac664fe51e1e
Storage type: eMMC
Card/BGA: BGA (Discrete embedded)
Manufacturer ID: 0x90 (SK Hynix)
Product name: HCG8a4 (0x484347386134), rev: 0xA2, serial number: 0x4DA29A32
Manufacturing date: сен 2018
CID: 90014A48 43473861 34A24DA2 9A3295E7
Capacity: 58.25 GiB(62,549,655,552 bytes)
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 4096 KiB (key exist)
User area: 58.24 GiB(62,537,072,640 bytes)
USB speed: High-Speed
Verifying Soc: passed
Verifying Storage ID: passed
Writing preloader: preloader_K91813AA1.bin, size: 221.88 KiB
Error: 0xC0050003 (STATUS_DOWNLOAD_EXCEPTION)
Error while flashing images at 0x00000000, please make sure your USB connection is stable.
Attachments
-
1603115646669.jpg
devthakur81
Active Member
what happen guys yesterday when i was briefing the problem nobody shows in this site and now too i am lonely in this site . i dont understand why
maysamrast
Junior Member
hi
i have problem with g610f set
i changed emmc but set just show boot logo j7 prime and after that black screen
what is problem?
i have problem with g610f set
i changed emmc but set just show boot logo j7 prime and after that black screen
what is problem?
oppo a5s 2020 pattern reset failed...
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: 3V6CMB (0x335636434d42), rev: 0x02, serial number: 0x016F6A9C
Manufacturing date: May 2019
CID: 15010033 5636434D 4202016F 6A9C56BC
CSD: D0270132 0F5903FF F6DBFFEF 8E40400C
EXT_CSD revision: 1.8 (MMC v5.1)
Partition info:
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 16384 KiB
User area: 116.48 GiB(125,069,950,976 bytes)
Cache size: 64 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 possible
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
Custom moviNAND command is not supported for this device(MMC51).
Detected: SAMSUNG moviNAND KM3V6000CM-BXXX/128G
Factory Reset...
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 13/16384 inodes and 2091/65536 blocks
Writing cache... Wrote 70557892 blocks, expected to write 65536 blocks
Done
Creating filesystem with parameters:
Size: 113728401408
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 27765723
Block groups: 848
Reserved block group size: 1024
Created filesystem with 11/6946816 inodes and 484123/27765723 blocks
Writing userdata... Unknown chunk type 0x0000 at 0x00E160C4
Wrote 50417292 blocks, expected to write 27765723 blocks
Done
Done
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: 3V6CMB (0x335636434d42), rev: 0x02, serial number: 0x016F6A9C
Manufacturing date: May 2019
CID: 15010033 5636434D 4202016F 6A9C56BC
CSD: D0270132 0F5903FF F6DBFFEF 8E40400C
EXT_CSD revision: 1.8 (MMC v5.1)
Partition info:
Boot1: 4096 KiB
Boot2: 4096 KiB
RPMB: 16384 KiB
User area: 116.48 GiB(125,069,950,976 bytes)
Cache size: 64 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 possible
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
Custom moviNAND command is not supported for this device(MMC51).
Detected: SAMSUNG moviNAND KM3V6000CM-BXXX/128G
Factory Reset...
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 13/16384 inodes and 2091/65536 blocks
Writing cache... Wrote 70557892 blocks, expected to write 65536 blocks
Done
Creating filesystem with parameters:
Size: 113728401408
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 27765723
Block groups: 848
Reserved block group size: 1024
Created filesystem with 11/6946816 inodes and 484123/27765723 blocks
Writing userdata... Unknown chunk type 0x0000 at 0x00E160C4
Wrote 50417292 blocks, expected to write 27765723 blocks
Done
Done
devthakur81
Active Member
4 days gone nobody taking interest in rectify the problem. no mentors no team no members. is this really a gsm product or a normal product which we can take it like milk on another shop. so proud of you team. wake up wake up team
Ufi box me kb aayega ufs chip support' I waiting
Sent From CPH1859 Using Martview Forum App
Sent From CPH1859 Using Martview Forum App
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