Database Info

mtk6737 baseband unknown and imei blank..how to repair

my phone model- CENTRIC CM2221
android -6.0
problem- no service
i check imei blank and baseband unknown .
how to solve ?
please provide me stock rom or good solution ..
Phone Info Log .........
1. Power Off Phone , Remove battery , Insert back
2. Insert USB cable. In some cases require hold BootKey
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!

You cm2 to Repaire baseband
Sent from my iPhone using Tapatalk Pro

abuk91 said:
You cm2 to Repaire baseband
Sent from my iPhone using Tapatalk Pro
Click to expand...
Click to collapse
bro allready try but not done .....need flash file

no solution????????????????????????????????????????????????????????????

I have the same problem
phone accent neon no service imei not found
I'm looking for rom file for this model

need MTK6737 cpu .....nv data

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

Help A8 2018 A530F emmc file repair

Hello i have A8 2018 sm-a530f which has the emmc files corrupted , i need to revive and when i connect to the Easy Jtag Plus i get the error Partition info not found ,guide repair procedures and below is the log data
Setting interface to EasyJtag2/ISP
Setting bus width to 1 Bit
Setting frequence to 36 MHz
CMD Pullup Level: 445 mV
CMD Active Level: 1192 mV
EMMC Device Information :
EMMC CID: 150100424A5444345200523F424BB5A7
EMMC CSD: D02701320F5903FFF6DBFFEF8E40400D
EMMC Manufacture : SAMSUNG , EMMC NAME: BJTD4R , HEX: 424A544434xx , S/N: 523F42xx , rev. 0x00
EMMC Manufacture ID: 0x15 , OEM ID: 0x00 , Device Type: BGA (Discrete embedded) , Date: 11/2018
EMMC ROM 1 (Main User Data) Capacity: 29820 MB (000747C00000)
EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
EMMC RPMB (Replay Protected Memory Block) Capacity: 16384 KB (000001000000) Counter: 0 , Response: Maybe not clean
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
Extended CSD Information :
Extended CSD rev: 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG]: 0x48 , Boot from: ROM2 (Boot partition 1)
Boot Bus Config: 0x01 , width 4bit
H/W Reset Function [RST_N_FUNCTION]: 0x01, RST_n signal is permanently enabled
Supported partition features [PARTITIONING_SUPPORT]: 0x07
Device supports partitioning features
Device can have enhanced technological features in partitions and user data area
Device can have extended partitions attribute
Partition Settings [PARTITION_SETTING_COMPLETED]: 0x00
Backup saved: BJTD4R_523F424B_20210404_201644.extcsd
EMMC Init completed.
Scanning soft partitions
Partition table not found
Get firmware version
Firmware info not found
NOTE: I HAVE THE BACK UP FILE BUT I DO NOT KNOW WHICH FILES TO LOAD , MAY SOMEONE CHECK THE ATTACHMENT AND TELL ME WHICH FILES TO LOAD LIKE (Select eMMC Image file *.bin) from THIS BACK UP.MAY SOMEONE TELL ME FROM THE BACK UP WHICH ONE IS ( eMMC ROM1 Image file, eMMC ROM2 Image file, eMMC ROM3 Image file, eMMC GP1 Image file, eMMC ExtCSD file. IN THEIR ORDER.

gruka said:
Hello i have A8 2018 sm-a530f which has the emmc files corrupted , i need to revive and when i connect to the Easy Jtag Plus i get the error Partition info not found ,guide repair procedures and below is the log data
Setting interface to EasyJtag2/ISP
Setting bus width to 1 Bit
Setting frequence to 36 MHz
CMD Pullup Level: 445 mV
CMD Active Level: 1192 mV
EMMC Device Information :
EMMC CID: 150100424A5444345200523F424BB5A7
EMMC CSD: D02701320F5903FFF6DBFFEF8E40400D
EMMC Manufacture : SAMSUNG , EMMC NAME: BJTD4R , HEX: 424A544434xx , S/N: 523F42xx , rev. 0x00
EMMC Manufacture ID: 0x15 , OEM ID: 0x00 , Device Type: BGA (Discrete embedded) , Date: 11/2018
EMMC ROM 1 (Main User Data) Capacity: 29820 MB (000747C00000)
EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
EMMC RPMB (Replay Protected Memory Block) Capacity: 16384 KB (000001000000) Counter: 0 , Response: Maybe not clean
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
Extended CSD Information :
Extended CSD rev: 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG]: 0x48 , Boot from: ROM2 (Boot partition 1)
Boot Bus Config: 0x01 , width 4bit
H/W Reset Function [RST_N_FUNCTION]: 0x01, RST_n signal is permanently enabled
Supported partition features [PARTITIONING_SUPPORT]: 0x07
Device supports partitioning features
Device can have enhanced technological features in partitions and user data area
Device can have extended partitions attribute
Partition Settings [PARTITION_SETTING_COMPLETED]: 0x00
Backup saved: BJTD4R_523F424B_20210404_201644.extcsd
EMMC Init completed.
Scanning soft partitions
Partition table not found
Get firmware version
Firmware info not found
NOTE: I HAVE THE BACK UP FILE BUT I DO NOT KNOW WHICH FILES TO LOAD , MAY SOMEONE CHECK THE ATTACHMENT AND TELL ME WHICH FILES TO LOAD LIKE (Select eMMC Image file *.bin) from THIS BACK UP.MAY SOMEONE TELL ME FROM THE BACK UP WHICH ONE IS ( eMMC ROM1 Image file, eMMC ROM2 Image file, eMMC ROM3 Image file, eMMC GP1 Image file, eMMC ExtCSD file. IN THEIR ORDER.
Click to expand...
Click to collapse
I think there are not many users who are able to help in your case.
I only found this thread about emmc repair for your device:
Samsung A520f ,A530f Dead boot repair direct emmc file download
gsm flash,gsm flash file,gsm crack,combine file,easy firmware,frp file,gsm firmware,gsm file,samsung firmware,samsung dump,all android flashing tool,
www.awaismobile.com

Yes i downloaded the file ,how do i know this file is rom 1 ,Rom2,Rom 3, and ex PLEASE I DENTIFY FOR ME

Problem with Nokia Lumia 630 flashing

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.

Question How to change Product I.D of device in Brom?

So long story short, I bricked my A226b and after a week of trying different things I noticed the product code was different when I was using Android Utilities. This could be why (my other post) I'm getting errors.
Looking around, the closest I can find to my problem is "build.prop" where the device I.D has changed after flash
I'm stuck in BROM and I can't get to DM or ADB, I'm searching for the answer but I still don't understand how to achieve changing the device I.D / Product I.D back so SP flash tool sees it as a correct model or deactivated this check etc.
I'm hoping I'm close to finding solution, any ideas?
Thank you

Decmanager said:
So long story short, I bricked my A226b and after a week of trying different things I noticed the product code was different when I was using Android Utilities. This could be why (my other post) I'm getting errors.
Looking around, the closest I can find to my problem is "build.prop" where the device I.D has changed after flash
I'm stuck in BROM and I can't get to DM or ADB, I'm searching for the answer but I still don't understand how to achieve changing the device I.D / Product I.D back so SP flash tool sees it as a correct model or deactivated this check etc.
I'm hoping I'm close to finding solution, any ideas?
Thank you
Click to expand...
Click to collapse
If your device is in BROM mode, and you have the right firmware files, SPFT, don´t check the device model to flash it, only it is based on the scatter file. Maybe you can upload some screenshots from the message you are receiving. Note that to really be sure your device is entering to BROM mode, you have to check in device manager, that it is in preloader mode, and using other tool, device will stay in BROM mode. Can you describe what you have with?

I'm bricked in brom, I use auth bypass, then Android Utilities / A226b dead boot repair and when it reads it, it shows product code of A12 and hangs back to brom. I feel like I've flashed it to be a12 some how and when I try flash the correct files it's giving me an error.
*(in my other post are the details of why I'm doing it and some logs / I'm not sure how I bricked it)

Waiting for mtk usb device... ok
BootMode : BootRom[COM21]
DriverDesc : MediaTek USB Port
DriverPath : usb\vid_0e8d&pid_0003\6&39447387&0&2
DriverSRV : wdm_usb
DriverVersion : 3.0.1504.0
DriverDate : 1-22-2015
DriverCFG : oem25.inf
DriverOEM : MediaTek Inc.
● BBChip ID MT6833
● BBChip Inf 989:8A00:CA00:0
● Chip PID Dimensity 700
● Chip UID Palmer
● Chip Ver CHIP_VER_E1
BRom::SEC:{0xe5}[SBC:ON:SLA:OFFAA:ON]
BRom stage Re-configuration
● BR_MEID:0x76206C45E7FF29381C34C136A484886F
Disabling watchdog timer0...
BRom::WinUSB:evHnd{0xefaf700}
BRom::WinUSB:evHnd{0xefb0218}
BRom::WinUSB:evHnd{0xefb07e0}
===== Bypass Authentication =====
Dumping Dram data(0xa47a0500)...
Re-connecting to BootROM...
Sending Download Agent(A037F)...
Booting Download Agent at(0x200000)...
Successfully received DA sync cahr
Start setup da environment...
Setup da device enviroment...
Successfully received 1st DA sync signal
Initialize Dram(0x1000)...
Dram initialized
Boot and enter 2nd DA...
Boot 2nd Da done! Getting Ram Info
● Sram 448.00KB
● Dram 4.00GB
Boot and enter 2nd SEC DA...
===== Power On HACC =====
Boot 2nd SEC DA done! Getting HW Info
● Storage eMMC
● BOOT1 4.00MB
● BOOT2 4.00MB
● RPMB 16.00MB
● GP1 00000000
● GP2 00000000
● GP3 00000000
● GP4 00000000
● USR 58.24GB
● MLC 00000001
● SLC 00000001
● EOL 00000001
● LCYCLE 00000000
● CID 13014E47314A395238101B685D0A29D1
● MFRID 0x13
● Vendor Micron
● Card BGA BGA (Discrete embedded)
● OEMID 0x4e
● Product G1J9R8
● Revision 1.0
● Card SN 0x1b685d0a
● MFDate 2/2022
● EMCP MT29VZZZAD8GQFSL_046W_9R8
● Capacity 0xe91000000:58.27GB
● RNID 07C80DE18DA944D652A025AC302451BA
Switching to usb high-speed...
===== wait for DA high speed port =====
Waiting for mtk da device... ok
BootMode : MTK DA VCOM[COM22]
DriverDesc : MediaTek DA USB VCOM (Android)
DriverPath : usb\vid_0e8d&pid_2001\6&39447387&0&2
DriverSRV : wdm_usb
DriverVersion : 3.0.1504.0
DriverDate : 1-22-2015
DriverCFG : oem25.inf
DriverOEM : MediaTek Inc.
● USBSpeed high-speed
Gathering partitions info...
===== wait for DA S/W detection report =====
===== Download boot_section to device =====
BOOT-A/B region(s) successfully updated!
===== Download user_section to device =====
(P/S)-GPT header(s) and entries(s) successfully updated!
Rebooting device... Done
Waiting for samsung-dm usb device...
**AND THEN HANGS**
It's showing up as : ● Product - G1J9R8

Decmanager said:
Waiting for mtk usb device... ok
BootMode : BootRom[COM21]
DriverDesc : MediaTek USB Port
DriverPath : usb\vid_0e8d&pid_0003\6&39447387&0&2
DriverSRV : wdm_usb
DriverVersion : 3.0.1504.0
DriverDate : 1-22-2015
DriverCFG : oem25.inf
DriverOEM : MediaTek Inc.
● BBChip ID MT6833
● BBChip Inf 989:8A00:CA00:0
● Chip PID Dimensity 700
● Chip UID Palmer
● Chip Ver CHIP_VER_E1
BRom::SEC:{0xe5}[SBC:ON:SLA:OFFAA:ON]
BRom stage Re-configuration
● BR_MEID:0x76206C45E7FF29381C34C136A484886F
Disabling watchdog timer0...
BRom::WinUSB:evHnd{0xefaf700}
BRom::WinUSB:evHnd{0xefb0218}
BRom::WinUSB:evHnd{0xefb07e0}
===== Bypass Authentication =====
Dumping Dram data(0xa47a0500)...
Re-connecting to BootROM...
Sending Download Agent(A037F)...
Booting Download Agent at(0x200000)...
Successfully received DA sync cahr
Start setup da environment...
Setup da device enviroment...
Successfully received 1st DA sync signal
Initialize Dram(0x1000)...
Dram initialized
Boot and enter 2nd DA...
Boot 2nd Da done! Getting Ram Info
● Sram 448.00KB
● Dram 4.00GB
Boot and enter 2nd SEC DA...
===== Power On HACC =====
Boot 2nd SEC DA done! Getting HW Info
● Storage eMMC
● BOOT1 4.00MB
● BOOT2 4.00MB
● RPMB 16.00MB
● GP1 00000000
● GP2 00000000
● GP3 00000000
● GP4 00000000
● USR 58.24GB
● MLC 00000001
● SLC 00000001
● EOL 00000001
● LCYCLE 00000000
● CID 13014E47314A395238101B685D0A29D1
● MFRID 0x13
● Vendor Micron
● Card BGA BGA (Discrete embedded)
● OEMID 0x4e
● Product G1J9R8
● Revision 1.0
● Card SN 0x1b685d0a
● MFDate 2/2022
● EMCP MT29VZZZAD8GQFSL_046W_9R8
● Capacity 0xe91000000:58.27GB
● RNID 07C80DE18DA944D652A025AC302451BA
Switching to usb high-speed...
===== wait for DA high speed port =====
Waiting for mtk da device... ok
BootMode : MTK DA VCOM[COM22]
DriverDesc : MediaTek DA USB VCOM (Android)
DriverPath : usb\vid_0e8d&pid_2001\6&39447387&0&2
DriverSRV : wdm_usb
DriverVersion : 3.0.1504.0
DriverDate : 1-22-2015
DriverCFG : oem25.inf
DriverOEM : MediaTek Inc.
● USBSpeed high-speed
Gathering partitions info...
===== wait for DA S/W detection report =====
===== Download boot_section to device =====
BOOT-A/B region(s) successfully updated!
===== Download user_section to device =====
(P/S)-GPT header(s) and entries(s) successfully updated!
Rebooting device... Done
Waiting for samsung-dm usb device...
**AND THEN HANGS**
It's showing up as : ● Product - G1J9R8
Click to expand...
Click to collapse
I saw you had "verified boot enabled" error, in the other post. You can try this https://www.hovatek.com/forum/thread-39260.html, but, excluding some files for the flash round, you can bypass that error, I have to see the files in SPFT, to can remember which (I also had the same issue with other device).
G1J9R8 it´s just the eMMc RAM product, not your device, the error may happen with UFI boxes.
You won´t have issues flashing any partition, through mtk-client.

SubwayChamp said:
I saw you had "verified boot enabled" error, in the other post. You can try this https://www.hovatek.com/forum/thread-39260.html, but, excluding some files for the flash round, you can bypass that error, I have to see the files in SPFT, to can remember which (I also had the same issue with other device).
G1J9R8 it´s just the eMMc RAM product, not your device, the error may happen with UFI boxes.
You won´t have issues flashing any partition, through mtk-client.
Click to expand...
Click to collapse
OK I setup and ready to flash with MTK client, can you point me to the simplest method to flash my MT6833 or what ever it is I need. I am also actively searching for info but if you have something please post. Thank you lots.

Decmanager said:
OK I setup and ready to flash with MTK client, can you point me to the simplest method to flash my MT6833 or what ever it is I need. I am also actively searching for info but if you have something please post. Thank you lots.
Click to expand...
Click to collapse
Simple, unlock bootloader through mtk-client (don´t erase metadata), then flash all the partitions available in the firmware.

SubwayChamp said:
Simple, unlock bootloader through mtk-client (don´t erase metadata), then flash all the partitions available in the firmware.
Click to expand...
Click to collapse
Couldn't find good solution to unlock bootloader, the phone stuck in Brom.