I am trying to unbrick my coolpad 3622a. When I enter downloading mode and start it gives me all these errors. I am using YGDP Tool. Please help!
08:38:31 CELL2: Device connected, start to download ...
08:38:31 CELL2: Get bootloader information ...
08:38:31 CELL2: Bootloader is old !
08:38:31 CELL2: Bootloader will not use CRC while system img!
08:38:31 CELL2: Bootloader supports querying CID!
08:38:31 CELL2: Bootloader supports querying Secure !
08:38:31 CELL2: Check device ...
08:38:31 CELL2: Check CID failed.
08:38:31 CELL2: Check CID fail!
08:38:31 CELL2: Download faile,please try again!!
08:38:31 CELL2: Total download time elapsed: 0 min : 0 sec
08:38:31 CELL2: Downloading all files: Failed!
Related
i have a problem when i use srk tool to unlock bootloader on my mate 8 nxt-l29
it fail and write " failed (status malformed (1 bytes) "
how can i solve it ?
and another thing was happen to me ... when i installed twrp it Requests password when i open twrp to install nougat update.zip
need MTK6737 cpu .....nv data
please give me any read nv file for mt6737 cpu.....
Raj_App said:
need MTK6737 cpu .....nv data
please give me any read nv file for mt6737 cpu.....
Click to expand...
Click to collapse
That's not a wise request (and I don't think it's legal).
NVDATA contains IMEI information (and you know it). An IMEI is unique for a device. One device, one IMEI. What you're asking is requesting someone else to share their IMEI with you. Two phones with the same IMEI is not legal.
Restore your ORIGINAL NVDATA to get back your original IMEI.
Nonta72 said:
That's not a wise request (and I don't think it's legal).
NVDATA contains IMEI information (and you know it). An IMEI is unique for a device. One device, one IMEI. What you're asking is requesting someone else to share their IMEI with you. Two phones with the same IMEI is not legal.
Restore your ORIGINAL NVDATA to get back your original IMEI.
Click to expand...
Click to collapse
Wait for phone...
Phone found! [ 16 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6737
BB_CPU_NME : [MediaTek] MT6737M|MT6737_S00
BB_CPU_EXT : 0xCB00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
Running DA ver.4.2 on BBID : 0x93
NAND Flash : NOT INSTALLED
eMMC Flash : 510001154D333238E8020042AF2EBAF4
Initialize Memory ...
DRAM already initialized by Preloader
DAgent sent , init HW now
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0x15 , OEM : 0100
[eMMC] : FLASH_INF : [SAMSUNG] , BM328
[eMMC] : FLASH_CID : 150100513832334D420002E8F4BA73AF
[eMMC] : FLASH_BRT : 0x00400000 , 0x00400000 , 0x00400000
[eMMC] : FLASH_LEN : 0x00000003A3E00000
[eMMC] : FLASH_UCP : 14910 MiB [eMMC 16 GiB]
DEV RID : 0xEF0B331D1BA71095953C8F7CFAA875FB
INT RAM : 0x00020000
EXT RAM : 0x80000000 [2 GiB]
BOOT TYPE : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!
[Info] : BaseBand : MT6735_S00_MOLY_LR9_W1444_MD_LWTG_MP_V79_P20_1_lwg_n
Read Error , NVRAM area is blank or damaged
Operation Failed
Elapsed: 00:00:29
Reconnect Power/Cable!
Raj_App said:
Read Error , NVRAM area is blank or damaged
Operation Failed
Click to expand...
Click to collapse
Use SP Flash Tools to flash your stock rom.
Nonta72 said:
Use SP Flash Tools to flash your stock rom.
Click to expand...
Click to collapse
bro i tired ..not found rom
please help me
Raj_App said:
bro i tired ..not found rom
please help me
Click to expand...
Click to collapse
Find it on your manufacturer's website or needrom.com
Hello
I've bricked Oppo F1s when I've tried to flash it
this is infinity read info log
Wait for phone...
Phone found! [ 1087 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6755
BB_CPU_NME : [MediaTek] Helio[P10]|MT6755_S00
BB_CPU_EXT : 0xCB00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x01000000
BromVer : 0x0005
BLVersion : 0x00FE
PreLoader : NOT Active [ Erased ]
BootLdrSS : SIGNED with SPRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
DAgent configured successfully
Connection agent : BROM
[DA_ERROR] : DRAM Configure failed!
ErroCode : 0x2122and I get this message error if I try to flash it with MT6750
Error: STATUS_INSUFFICIENT_BUFFER
EMICFG_NOT_ACCEPTED_CONFIG
Boot Error!
Operation Failed
Elapsed: 00:00:52
Reconnect Power/Cable!
Click to expand...
Click to collapse
it says that's an MT6755 processor , but when I try to flash it with Mt6755 with sp flashtool and NCK mtk soft it says that's version mismatch and it's and MT6750 device
Can you help to choose the right firmware please ?
octopus82 said:
Hello
I've bricked Oppo F1s when I've tried to flash it
this is infinity read info log
it says that's an MT6755 processor , but when I try to flash it with Mt6755 with sp flashtool and NCK mtk soft it says that's version mismatch and it's and MT6750 device
Can you help to choose the right firmware please ?
Click to expand...
Click to collapse
I have pretty much the same problem with my MOTO M (XT1662). It happened after I did the "Format whole flash" in SP flash tool.
Now the SP flash tool is giving me the following,
Chip Info
=======
Chip name: MT6755
Chip Version: 0x0000cb00
Ext Clock: EXT_26M
Extern RAM Type: DRAM
Extern RAM Size: 0xc0000000 (!!!)
SRAM Size: 0x00040000
EMMC Flash
=========
Boot 1 Size: 0x400000
Boot 2 Size: 0x400000
RPMB Size: 0x400000
GP1 Size: 0x0 (same for GP2, GP3 and GP4)
UA Size: 0x747c00000
No matter what ROM I'm trying to flash (stock or custom) , I always get the error "STATUS_INSUFFICIENT_BUFFER (0xC0010007)".
It looks like it has to do something with the External RAM Size (0xc0000000).
I found this firmware "XT1662_Kungfu_m_MT6755_USR_S0924_1612291517_mp7V2.3_CN (RepairMyMobile.in)", which seems to be what I need but I can't get pass this error.
Any help will be greatly appreciated.
i have the same problem
STATUS_INSUFFICIENT_BUFFER (0xC0010007)
i try to update with OTA and failed too
anyone can help ?
Samsung recovery
Code:
samsung a12zh/a12
10/QP1A.190711.020/A125FZHU1AYC3
user/release/keys
Install /sdcard/A12/stock/A125FXXU1AUC3_A125FOLM1AUC3_XSA.zip ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: Footer is wrong
Update pkacage verification took 0.1s (result 1).
E: Signature verification failed
E: Error 21
Install from SD card completed with status 2.
Installation aborted. #1
PNG and TGY were also failed like is, but if reflashing stock ROM using Heimdall, which partitions are to be flashed accoring to the PIT on my A12? And which partitions should never be touched?
Even with successful flashes using Heimdall, it still always reports to me SW REV check failed
Now my device is still being boot-looped, and on either YouTube or online text tutorials nothing is about solving the boot loops for my A12
And have also retried to flash my own builds of TWRP instead, https://sourceforge.net/p/twrp-samsung-a12/code/ci/master/tree/out/target/product/a12, however also unfortunately somewhy,
Code:
Heimdall mode (High speed)
Product name: SM-A125F
...
Warranty void: 0x1 (0x500)
RP SWREV: B1 NS1 K1 S1
...
SW REV check fail: [recovery] Fused 1 > Binary 2
SW REV check fail: [boot]Fused 1 > Binary 0
Me again.. Ive obtained the same problem and solved it just reflashing my whole firmware with Odin u_u
I’ve just flashed the full firmware.
The SW REV check failures were fixed, but my device is still being boot looped
What to do next?
My A12 has MTK chipsets (according to my CPU-Z), hence also their ‘‘secure’’ boot locks, now going to unlock it by their SPFlashTool
speedmetal444 said:
Me again.. Ive obtained the same problem and solved it just reflashing my whole firmware with Odin u_u
Click to expand...
Click to collapse
Heimdall flashes are always by PIT partitions; PIT means partitioning informative tables
Odin flashes, on the other hand, are instead more by tar packages, namely BL, AP, CP, and CSC
* BL = BootLoaders; AP = Android PDA’s i.e. systems with also recoveries; CP = Core PDA’s i.e. modems; CSC = Country support codes or Consumer software customizations
I’m still being boot looped due to sth in unknown errors named PDP
Code:
Android recovery
samsung/a12nsxx/a12
11/RP1A.200720.012/A125FXXU1BUE3
...
Supported API: 3
# MANUAL MODE v1.0.0#
No commands specified
-- Wiping data ...
Formatting /data ...
E: [PDP] lstat /c___/pdp_b__: 0 - No PDP scenario
Formatting /cache ...
Formatting /metadata ...
Formatting /keydata ...
Formatting /keyrefuge ...
Data wipe complete.
hd_scania said:
Samsung recovery
Code:
samsung a12zh/a12
10/QP1A.190711.020/A125FZHU1AYC3
user/release/keys
Install /sdcard/A12/stock/A125FXXU1AUC3_A125FOLM1AUC3_XSA.zip ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: Footer is wrong
Update pkacage verification took 0.1s (result 1).
E: Signature verification failed
E: Error 21
Install from SD card completed with status 2.
Installation aborted. #1
PNG and TGY were also failed like is, but if reflashing stock ROM using Heimdall, which partitions are to be flashed accoring to the PIT on my A12? And which partitions should never be touched?
Even with successful flashes using Heimdall, it still always reports to me SW REV check failed
Now my device is still being boot-looped, and on either YouTube or online text tutorials nothing is about solving the boot loops for my A12
And have also retried to flash my own builds of TWRP instead, https://sourceforge.net/p/twrp-samsung-a12/code/ci/master/tree/out/target/product/a12, however also unfortunately somewhy,
Code:
Heimdall mode (High speed)
Product name: SM-A125F
...
Warranty void: 0x1 (0x500)
RP SWREV: B1 NS1 K1 S1
...
SW REV check fail: [recovery] Fused 1 > Binary 2
SW REV check fail: [boot]Fused 1 > Binary 0
Click to expand...
Click to collapse
The error at the last is probably because the firmware you are trying to flash has older bootloader than what it is currently and it looks like you cannot downgrade bootloader.
I
How can I flash my Nokia Lumia 630?
I tried on WPInternals, but it says:
Flash failed! Error 0x1106: Security header validation failed
I also tried THOR2, which also failed. It says:
Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Device mode 6 Uefi mode
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Detecting UEFI responder
Lumia UEFI Application did not respond to version info query
Device is not in Lumia UEFI mode
Device mode get failed, mode is 6
Connection lost, trying to re-connect
Rebooting to the normal mode...
Rebooting from the WP/MMOS failed.
Operation took about 16.00 seconds.
THOR2_ERROR_TO_COMMUNICATE_WITH_DEVICE
THOR2 1.8.2.18 exited with error code 84102 (0x14886)
Can someone help me?
I'm also having issues unbricking my Nokia 630 (RM-979),
It's completely bricked. Nothing shows on the screen. Completely black.
It is detected on Windows Device Manager as QDLoader 9008 (COM7), but I'm not being able to flash it.
I have tried:
- Windows Phone Internals
- Windows Device Recovery Tool
- NaviFirm
- Thor
Result from thor:
> thor2 -mode ffureader -ffufile "C:\rm-914\XXX.ffu" -dump_gpt -filedir C:\dump
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode ffureader -ffufile C:\rm-914\XXX.ffu -dump_gpt -filedir C:\dump
Process started Wed Dec 29 17:13:00 2021
Logging to file C:\Users\Angelo\AppData\Local\Temp\thor2_win_20211229171300_ThreadId-13244.log
Debugging enabled for ffureader
Initiating do FFUReader operations
Version of FfuReader is 2015061501
Parsing FFU... Please wait...
Failed to parse FFU file. Header size: 0x00000000, Payload size: 0x0000000000000000, Chunk size: 0x00000000, Header offset: 0x00000000, Payload offset: 0x0000000000000000
File open failed
THOR2_ERROR_FFUREAD_CORRUPTED_FFU
THOR2 1.8.2.18 exited with error code 84204 (0x148EC)
Any ideas?
Angelo Marzolla said:
I'm also having issues unbricking my Nokia 630 (RM-979),
It's completely bricked. Nothing shows on the screen. Completely black.
It is detected on Windows Device Manager as QDLoader 9008 (COM7), but I'm not being able to flash it.
I have tried:
- Windows Phone Internals...
Click to expand...
Click to collapse
I don't have bricked Nokia, but did you format the whole phone storage when Windows said it's broken? Because it can be the reason why your phone is bricked.