mtk6737 baseband unknown and imei blank..how to repair - General Questions and Answers

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

Related

[Q] how to recover a bricked lg optimus p500 which is 'not' detecting by pc

mine is an rooted lg optimus p500 with stock gingerbread 2.3.3 ,firmware v20c for india.last day i installed rom manager trail,when i tried to back up current rom,the phone gone off,now it is strucked at lg logo.i tried kdz for installing another stock rom.but it says phone is not connected. i checked through adb,when typing command 'adb shell' it also says no devices found.hard reseting is not working,no emergency mode. what to do??? pls help me.
Did u flash recovery first before hitting backup current rom? If you are getting LG logo then u should get emergency mode. Press volume up button+return key + connect the usb cable connected to your PC all at the same time. http://forum.xda-developers.com/showthread.php?t=883314 Read this. it will help u.
reinstall drivers.
let your phone be on (stuck at lg logo), connect to computer, flash custom recovery from lgmdp.
There might errors occur at nv backup or nv restore but it will flash recovery.
sweettaniyaa said:
Did u flash recovery first before hitting backup current rom? If you are getting LG logo then u should get emergency mode. Press volume up button+return key + connect the usb cable connected to your PC all at the same time. http://forum.xda-developers.com/showthread.php?t=883314 Read this. it will help u.
Click to expand...
Click to collapse
thnks. phone recovered. then how to back up current rom using rom manger????.do i want to flash recovery first.??
phone not even starting
hi everyone,
i tried to update the firmware on my op1 p500.it came to emergency mode,but after this some error occured and kdz updater showed 'c drive erased'
and now my phone is not even starting.
it is in warranty,but i dnt knw wat reason i can tell at the service center,that wat happened to the phone.
Plz help.
farzii said:
hi everyone,
i tried to update the firmware on my op1 p500.it came to emergency mode,but after this some error occured and kdz updater showed 'c drive erased'
and now my phone is not even starting.
it is in warranty,but i dnt knw wat reason i can tell at the service center,that wat happened to the phone.
Plz help.
Click to expand...
Click to collapse
If the phone can't boot, then it's alright. Easy. Something like "I switched it off before I went to sleep and the next morning I couldn't turn it on" should do the trick
Sent from my LG-P500 using xda premium
farzii said:
hi everyone,
i tried to update the firmware on my op1 p500.it came to emergency mode,but after this some error occured and kdz updater showed 'c drive erased'
and now my phone is not even starting.
it is in warranty,but i dnt knw wat reason i can tell at the service center,that wat happened to the phone.
Plz help.
Click to expand...
Click to collapse
Just say when you are updating firmware it had an error and your phone would not start up.
Lg bricked
I've got a similar problem;
Rom manager crashed my phone (lg p500) when i was trying to back-up the original rom. The Phone booted in <b> fastboot mode </b>, i've followed the guide your guide to recover, but the phone crashed and even the fastboot mode disappeared. After a long research i've found the kdz 'ultima ratio' system, i've started the phone to <b> emergency mode </b> followed all the procedure (shaking included) trying to flash my phone to V10C.kdz, the result was
[23:14:11:932] : =============================================
[23:14:11:932] : Log is started on 06.03.2012, at 23:14:11:932,
executable: C:\Users\giuseppe\Desktop\KDZ_FW_UPD_EN\KDZ_FW_UPD.exe (ProcID: 0x00000810),
compile time : May 24 2011 11:19:45
[23:14:11:932] : Version :
[23:14:11:932] : Get Usb Port
[23:14:11:979] : rsi.strFriendlyName=Porta di comunicazione (COM1)
[23:14:11:979] : Remove Porta di comunicazione (COM1)
[23:14:11:979] : rsi.strFriendlyName=LGE Bluetooth TransPort (COM4)
[23:14:11:979] : Remove LGE Bluetooth TransPort (COM4)
[23:14:11:979] : rsi.strFriendlyName=LGE Android Platform USB Serial Port (COM11)
[23:14:11:979] : FriendlyNameList[iii].szFriendlyName=LGE Android Platform USB Serial Port
[23:14:11:979] : WM_COPYDATA žÞœÃÁö ºž³¿ 1 - COM11
[23:14:11:979] : Port = COM11
[23:14:11:995] : UNKNOWN : Req(12) -> Rsp(13)
[23:14:12:010] : UNKNOWN : Req(12) -> Rsp(13)
[23:14:12:026] : UNKNOWN : Req(12) -> Rsp(13)
[23:14:12:026] : >> DIAG_STATUS_F FAILED
[23:14:12:041] : >>Get Model Name [DIAG_VERNO_F]
[23:14:12:057] : BAD CONN MODE : Req(0) -> Rsp(3)
[23:14:12:073] : BAD CONN MODE : Req(0) -> Rsp(3)
[23:14:12:088] : BAD CONN MODE : Req(0) -> Rsp(3)
[23:14:12:104] : BAD CONN MODE : Req(0) -> Rsp(3)
[23:14:12:119] : BAD CONN MODE : Req(0) -> Rsp(3)
[23:14:12:135] : BAD CONN MODE : Req(0) -> Rsp(3)
[23:14:12:135] : FAIL (No Phone)
[23:14:12:135] : GetModelName() Operation Failed Check Diag CMD
[23:14:12:135] : EMERGENCY Booting Mode
[23:14:12:135] : >>Get Model Name in Emergency Mode [DLOAD_VERREQ_F]
[23:14:12:151] : BS/P500/7Diuseppe\AppData\Local\Temp\DZ
[23:14:12:151] : WM_COPYDATA žÞœÃÁö ºž³¿ 0 - P500
[23:14:12:166] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[23:14:12:166] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[23:14:12:182] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[23:14:12:182] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[23:14:12:197] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[23:14:12:197] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[23:14:12:197] : NV Write Fail : NV ITEM 9028(9028)
[23:14:12:307] : >> GET DLOAD COMM MODE
[23:14:12:322] : [GetCommMode] Communication mode : 2
[23:14:12:322] : Pre Nand Download
[23:14:12:322] : >>Set Trusted Mode [DLOAD_NAND_SEC_MODE] sec_mode = 1 (1=trusted 0=NonTrusted)
[23:14:12:322] : WM_COPYDATA žÞœÃÁö ºž³¿ 3 - TRUSTED MODE
[23:14:12:338] : [COM11] >>NandFlashInitWithFile(PARTITION TBL)
[23:14:12:338] : WM_COPYDATA žÞœÃÁö ºž³¿ 3 - INIT PARTITION TBL
[23:14:17:267] : žÞœÃÁö ºž³¿ TYPE_WPARAM_WRITE_AMSS 15
[23:14:17:267] : [COM14] žÞœÃÁö ºž³¿ TYPE_WPARAM_WRITE_AMSS 15
[23:14:17:267] : [COM11] >>NandFlashInitWithFile(AMSS MODEM HEADER)
[23:14:17:267] : WM_COPYDATA žÞœÃÁö ºž³¿ 3 - INIT AMSS MODEM HEADER
[23:14:17:283] : [COM14] >>Dl_AsyncWrite()
[23:14:17:283] : >> AMSS FLASHING ...
[23:14:17:283] : žÞœÃÁö ºž³¿ ProgreassiveBar Init wParam TYPE_WPARAM_PROGRESSIVE_POS=5 lParam(pos)=0 nResult=0
[23:14:17:283] : Sending Pkt Seq : 0
[23:14:17:283] : Sending Pkt Seq : 1
[23:14:17:283] : Sending Pkt Seq : 2
[23:14:17:283] : Sending Pkt Seq : 3
[23:14:17:283] : Sending Pkt Seq : 4
[23:14:17:283] : Sending Pkt Seq : 5
[23:14:17:283] : Sending Pkt Seq : 6
[23:14:17:283] : Sending Pkt Seq : 7
[23:14:17:283] : Sending Pkt Seq : 8
[23:14:17:283] : Sending Pkt Seq : 9
[23:14:17:283] : Sending Pkt Seq : 10
[23:14:17:283] : Sending Pkt Seq : 11
[23:14:17:283] : Sending Pkt Seq : 12
[23:14:17:283] : Sending Pkt Seq : 13
[23:14:17:283] : Sending Pkt Seq : 14
[23:14:17:283] : Sending Pkt Seq : 15
[23:14:17:283] : Sending Pkt Seq : 16
[23:14:17:283] : Sending Pkt Seq : 17
[23:14:17:283] : Sending Pkt Seq : 18
[23:14:17:283] : Sending Pkt Seq : 19
[23:14:17:283] : Sending Pkt Seq : 20
[23:14:17:283] : Sending Pkt Seq : 21
[23:14:17:283] : Sending Pkt Seq : 22
[23:14:17:283] : Sending Pkt Seq : 23
[23:14:17:283] : Sending Pkt Seq : 24
[23:14:17:299] : Dl_AsyncWrite - ErrNo(45), Addr(0x0000C600), NandErrNo(0x04)
[23:14:17:299] : [COM14] ERROR Dl_AsyncWrite() TYPE_LPARAM_UPGRADE_ERROR_WRITE_TO_FLASH
[23:14:17:299] : WM_COPYDATA žÞœÃÁö ºž³¿ 3 - Close Port
[23:14:17:299] : Close Port<<
[23:14:17:299] : TYPE_WPARAM_UPGRADE_ERROR
[23:14:17:299] : žÞœÃÁö ºž³¿ - TYPE_WPARAM_UPGRADE_ERROR Error Code = 4008
[23:14:17:361] : Log finished
Click to expand...
Click to collapse
I've tried to reflash, but nothing happened even shaking the pc, then i've disconnected the phone and unplugged the battery pack. From that moment my phone is officially 'dead' no key combination seems to work, no usb connection, no signal.
Now what are your suggestions?
BACK + VOLUMEN UP + POWER... you can get EMERGENCY MODE... Then use KDZ
Stuck at fastboot mode Started udc start()
I was using
ROM : LG Icy Snap (4.0.4)
and wanted to update to 4.4.4 . Started the process normally .(i had previously tried the 4.4 kitkat by mukulsoni. which used the CWM 6..0.4 something like that)So updated my recovery .The recovery was fine but the volume buttons were not working so pressed the power button and i got a message saying that i would loose root access. i pulled out the battery and when i started it with the combo(Power+vol UP+ Home) i got the fastboot msg. i bricked my phone previously similarly but came out of it as my pc detected my mobile. Now it is not and when i try to launch that command to says waiting for device. Dunno what to do . I know LG P500 is a bit old but it is the only mobile i have :crying: .

My p500 got hard brick

Some 1 plz help me
while flashing with WP7 mango tango my phone got bricked firs it loss its signals ,so i flashed it wit iosdroid then also it shows the same problem....after this i seek some helps from my friends they tell me to flash the kernel so i done so... nw it have no menu no signal and nothing plz help me soon i dnt have any oter phone plz hel me to unbrick it.I tried so many ways but nthng is effective plsssss help me sooooooon
Doesn't the phone turn on?
Just flash a new baseband
my :tank: has blown your house up
Boot to recovery, flash the rom and then flash the old bb fix. Seems you are on old bb and the rom is for the new bb. Were you on froyo 2.2 when you flashed the mango tango rom?
Sent from my LG-P500
Flash oldbb fix after complete wipe
Sent from my LG-P690 using xda premium
rijukrishnan said:
Some 1 plz help me
while flashing with WP7 mango tango my phone got bricked firs it loss its signals ,so i flashed it wit iosdroid then also it shows the same problem....after this i seek some helps from my friends they tell me to flash the kernel so i done so... nw it have no menu no signal and nothing plz help me soon i dnt have any oter phone plz hel me to unbrick it.I tried so many ways but nthng is effective plsssss help me sooooooon
Click to expand...
Click to collapse
Can you see LG logo on your phone or can you connect it to computer in emergency mode. If either of this is true than your phone is not hard bricked. Its just a soft brick and can be resolved easily.
So can you tell us the exact status of your device. So that others can help you.
Yes I can connect it in emergency mode it shows startup screen an unlock screen but no signal and menu can I fix it via kdz updater
This is not a hard brick. A hard brick is when the device no longer turns on
I'M BATMAN
Wat to do next.
Sent from my SHW-M250S using xda app-developers app
rijukrishnan said:
Yes I can connect it in emergency mode it shows startup screen an unlock screen but no signal and menu can I fix it via kdz updater
Click to expand...
Click to collapse
Sent from my SHW-M250S using xda app-developers app
how can i fix dis prblm ........ plz discribe in detail .. am a nube in this field
Sent from my SHW-M250S using xda app-developers app
Which custom recovery are you using?
Sent from my LG-P500
Amonra
Sent from my SHW-M250S using xda app-developers app
Can you boot into recovery? If you can, flash a rom (clean flash with all wipes ). Try hephappy's 9.2.1 or cyberics 3.0. Boot into the rom and check your bb. If it says v10 its old bb. Flash the old bb fix. If it is 20, you are on new bb and no need to flash the fix. You should get network back.
Sent from my LG-P500
Yes try kdz updater or lgmdp to flash official firmware. Then root again, flash custom recovery and then any custom rom you like.
But don't remove your battery during flashing or interrupt the process as it can hard brick your phone.
Sent from my LG-P500
Hey can u help me via FB
Sent from my SHW-M250S using xda app-developers app
This is the exact situation of my phon
Sent from my SHW-M250S using xda app-developers app
Sent from my SHW-M250S using xda app-developers app
Have you tried reboot into recovery,clean all cache, dalvik, data, system and then re-flash the rom? Try an ics rom as its newer and almost nil bugs.
Sent from my LG-P500
p500 stuck at booting
[16:44:00:378] : =============================================
[16:44:00:378] : Log is started on 28.04.2013, at 16:44:00:378,
executable: C:\Users\user\Desktop\riju files\kdz-udpate\KDZ_FW_UPD.exe (ProcID: 0x00000c64),
compile time : Dec 8 2010 09:19:37
[16:44:00:379] : Version :
[16:44:00:398] : Get Usb Port
[16:44:00:404] : rsi.strFriendlyName=Communications Port (COM1)
[16:44:00:404] : Remove Communications Port (COM1)
[16:44:00:404] : rsi.strFriendlyName=LGE Android Platform USB Serial Port (COM5)
[16:44:00:404] : FriendlyNameList[iii].szFriendlyName=LGE Android Platform USB Serial Port
[16:44:00:404] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 1 - COM5
[16:44:00:404] : Port = COM5
[16:44:00:416] : UNKNOWN : Req(12) -> Rsp(13)
[16:44:00:417] : UNKNOWN : Req(12) -> Rsp(13)
[16:44:00:418] : UNKNOWN : Req(12) -> Rsp(13)
[16:44:00:418] : >> DIAG_STATUS_F FAILED
[16:44:00:423] : >>Get Model Name [DIAG_VERNO_F]
[16:44:00:424] : BAD CONN MODE : Req(0) -> Rsp(3)
[16:44:00:425] : BAD CONN MODE : Req(0) -> Rsp(3)
[16:44:00:426] : BAD CONN MODE : Req(0) -> Rsp(3)
[16:44:00:427] : BAD CONN MODE : Req(0) -> Rsp(3)
[16:44:00:428] : BAD CONN MODE : Req(0) -> Rsp(3)
[16:44:00:429] : BAD CONN MODE : Req(0) -> Rsp(3)
[16:44:00:429] : FAIL (No Phone)
[16:44:00:429] : GetModelName() Operation Failed Check Diag CMD
[16:44:00:429] : EMERGENCY Booting Mode
[16:44:00:429] : >>Get Model Name in Emergency Mode [DLOAD_VERREQ_F]
[16:44:00:430] : BS/P500/7D
[16:44:00:430] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 0 - P500
[16:44:00:441] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[16:44:00:441] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[16:44:00:442] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[16:44:00:442] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[16:44:00:443] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[16:44:00:443] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[16:44:00:443] : NV Write Fail : NV ITEM 9028(9028)
[16:44:00:543] : >> GET DLOAD COMM MODE
[16:44:00:544] : [GetCommMode] Communication mode : 2
[16:44:00:544] : Pre Nand Download
[16:44:00:544] : >>Set Trusted Mode [DLOAD_NAND_SEC_MODE] sec_mode = 1 (1=trusted 0=NonTrusted)
[16:44:00:544] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - TRUSTED MODE
[16:44:00:545] : [COM5] >>NandFlashInitWithFile(PARTITION TBL)
[16:44:00:545] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - INIT PARTITION TBL
[16:44:00:647] : ¸Þ½ÃÁö º¸³¿ TYPE_WPARAM_WRITE_TO_SDRAM 3
[16:44:00:647] : [COM14] ¸Þ½ÃÁö º¸³¿ TYPE_WPARAM_WRITE_AMSS 15
[16:44:00:647] : [COM5] >>NandFlashInitWithFile(AMSS MODEM HEADER)
[16:44:00:662] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - INIT AMSS MODEM HEADER
[16:44:00:673] : [COM14] >>Dl_AsyncWrite()
[16:44:00:673] : >> AMSS FLASHING ...
[16:44:00:675] : ¸Þ½ÃÁö º¸³¿ ProgreassiveBar Init wParam TYPE_WPARAM_PROGRESSIVE_POS=5 lParam(pos)=0 nResult=0
16:44:15:377] : RX Timeout : 3.0 seconds
[16:44:15:377] : RX TIMEOUT
[16:44:18:387] : RX Timeout : 3.0 seconds
[16:44:18:387] : RX TIMEOUT
[16:44:21:398] : RX Timeout : 3.0 seconds
[16:44:21:398] : RX TIMEOUT
[16:44:21:398] : [COM14] ERROR Dl_AsyncWrite() TYPE_LPARAM_UPGRADE_ERROR_WRITE_TO_FLASH
[16:44:21:398] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - Close Port
[16:44:21:398] : Close Port<<
[16:44:21:398] : TYPE_WPARAM_UPGRADE_ERROR
[16:44:21:398] : ¸Þ½ÃÁö º¸³¿ - TYPE_WPARAM_UPGRADE_ERROR Error Code = 5
[16:44:21:431] : Log finished
after this show only a black screen only and a cmnd Fast boot started
Thanx for all helps my fon got life back
Sent from my GT-S5360 using xda app-developers app

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

F1s bricked need help

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 ?

MBW vodacom kicka 4 plus won't boot , what could be the problem

What could be the problem ..
Operation : Identify [ v2.18 ]
Mode : FLASH
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
2. Insert USB cable in phone
Waiting for device connection ...
PTFN : MediaTek USB Port (COM7)
MODE : BOOTROM
PORT : 7
Waiting BOOT ack ...
BROM : Skip ACK verify
BROM : Init BROM
BROM init passed!
CHIP : MT6580 , SBID : 0x8A00 , HWVR : 0xCA00 , SWVR : 0x0000
TYPE : LEGACY MTK
BROM : MEID : 84E1311723E5F72DDF767B7B831BD757
BROM : SecLevel : 0x00000000
BROM : SecMode : PLAIN [+PRL]
BROM : BROM|BL : 0x05|0xFE
BROM : BOOTROM
MODE : 0_base : BASE_v2044 | Manual : Enabled
AGENT : Look for suitable BootChain in DA ...
AGENT : MTK_AllInOne_DA_SP.bin
AGENT : Found MT6580
AGENT : MTK_DOWNLOAD_AGENT
BROM : Sending 1st DA ...
BROM : DA sent
BROM :Transfer control to DA ...
DA : AGENT started!
NAND : DEVICE NOT FOUND
NAND : 000000000000000000000000
eMMC : OK
eMMC : 45000170414934456E0101344F2524D7
DAInf: 4 : 2 : 156
DA : EXT_RAM NOT initialized!
eMMC : OK
eMMC : 70010045453449413401016ED724254F
NAND : DEVICE NOT FOUND
NAND : 000000000000000000000000
DRAM : 0x0178
EMI : DEV : MT6752
EMI : SRC : preloader_k80hd_bsp_fwv_512m.bin
EMI : CNT : 0003
EMI : [00] : ID : 700100454534454134 : VEN : KINGSTON | DEV : EE4EA4 : RAM : [ 512.00 MB ]
EMI : [01] : ID : C80111344D45594D41 : VEN : UNKNOWN | DEV : 4MEYMA : RAM : [ 512.00 MB ]
EMI : [02] : ID : 700100454534494134 : VEN : KINGSTON | DEV : EE4IA4 : RAM : [ 512.00 MB ]
EMI : Init EMI from PRELOADER
INIT : 0xBC : DRAM [ 0x00000000 : [ 0 B ] ]
DRAM : DRAM: 0x20000000 [ 512.00 MB ]
DA : DRAM ready!
DA : BOOT to 2nd DA ...
DA : Receiving HW info
EMMC: 70010045453449413401016ED724254F
EMMC: VEN : KINGSTON | OEM : 01 | DEV : EE4IA4
EMMC:
BOOT1 : 0x00200000 [ 2.00 MB ]
BOOT2 : 0x00200000 [ 2.00 MB ]
RPMB : 0x00080000 [ 512.00 KB ]
USER : 0xE2000000 [ 3.53 GB ]
SRAM: 0x00020000 [ 128.00 KB ]
DRAM: 0x20000000 [ 512.00 MB ]
CHIP : MT6580 , SBID : 0x8A00 , HWVR : 0xCA00 , SWVR : 0x0000 , EVOL : 0x0000
RNID : C936D9FF3A84D90E7B2010FA5212EA26
STATUS : BLANK FLASH
BSTYLE : EMMC FLASH BOOT
DA : USB : FULL-SPEED
DA : USB : Change Port Speed
PTFN : MediaTek DA USB VCOM (Android) (COM9)
MODE : PRELOADER PORT
PORT : 9
Boot done!
Patch Level : O11019
Display ID : O11019 release-keys
Ver. CodeName : REL
Ver. Release : 8.1.0
Sec. Patch : 2019-09-05
Build Time : 23.08.2019
Product Model : Kicka_4_Plus
Product Brand : MobiWire
Product Name : Kicka_4_Plus
Product Device : Kicka_4_Plus
Product Manfct : MobiWire
Product Info : k80hd_bsp_fwv_512m
Board Platform : mt6580
Product Board : VP402_Mobiwire_Kicka4Plus
USERDATA : FILESYSTEM : F2FS with FDE ( Full Disk Encryption ***)
Done!
Elapsed: 00:00:30
Operation : HW Test [ v1.58 ]
1. Power Off Phone , Remove battery , Insert back
2. Insert USB cable. In some cases require hold BootKey
Wait for phone...
Phone found! [ 1 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6580
BB_CPU_NME : [MediaTek] MT6580_S00
BB_CPU_EXT : 0xCA00 , 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_v3.3001.2018-04-25.11:26_437806
Sending and initialize DA ...
Running DA ver.4.2 on BBID : 0x9C
NAND Flash : NOT INSTALLED
eMMC Flash : 70010045453449413401016ED724254F
Initialize Memory ...
DRAM already initialized by Preloader
DAgent sent , init HW now
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0x70 , OEM : 0100
[eMMC] : FLASH_INF : [KINGSTON] , 4AI4E
[eMMC] : FLASH_CID : 70010045453449413401016ED724254F
[eMMC] : FLASH_BRT : 0x00200000 , 0x00200000 , 0x00080000
[eMMC] : FLASH_LEN : 0x00000000E2000000
[eMMC] : FLASH_UCP : 3616 MiB [eMMC 4 GiB]
DEV RID : 0x4EA014B2FFD936C90ED9843AFA10207B
INT RAM : 0x00020000
EXT RAM : 0x20000000 [512 MiB]
BOOT TYPE : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!
Processing Miscellaneous test
MSC : BatteryLevel : 3009 mV
[Processing] FlashMemory Read-Write test
[eMMC] : [KINGSTON] , 4AI4E , 0xE2000000 , 3616 MiB
[eMMC] : CID : 70010045453449413401016ED724254F
[eMMC] : MODE : SQ-WR
[PASSED] : eMMC RW Check #1 Ok!
[eMMC] : MODE : RA-WR
[PASSED] : eMMC RW Check #2 Ok!
[eMMC RO CHECK] : eMMC Ok! READ-WRITE Passed!
[Processing] RAM Read-Write test
[DRAM] : 0x20000000 , 512 MiB
[DRAM] : ADDRESS BUS test
[PASSED] : Bus Count : 0x1C
[DRAM] : DATA BUS test
[PASSED] : Bus Count : 0x1F
[DRAM] : PATTERN test
[PASSED] : PATTERN Ok
[DRAM] : INCDEC test
[PASSED] : INCDEC Ok
All Done!
Done!
Elapsed: 00:01:40
Reconnect Power/Cable!

Categories

Resources