Database Info

[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: .

[GT-P6210 WIFI]bootloader output & default settings & Native ubuntu running

I recently installed ubuntu on GT-P6210, it works fine until i tried to port some drivers from Linaro Origen source, as I couldnt see anything from bootloaders and kernel, it's hard to get off the reboot loop,
So I made a serial cable, thanks for Technomancer's post here:http://forum.xda-developers.com/showthread.php?t=1010314
and the following are those outputs from bootloaders, maybe it's helpful to someone:
Welcome to Samsung Primitive Bootloader.
build time: Jan 5 2012 22:13:07
current time: 0/1/3 0:9:30
[set_mmc_ocr] Sector Mode
[hsmmc_init] MMC card is detected
Product Name : MAG4FA
<display_card_info:1009> ext_csd
<display_card_info:1011>card_size: 15028
Total Card Size: 15029 MByte
mmc_init: card initialization completed!
pbl found bootable sbl in #49152.
jump to sbl 0x4d400000.
init_fuel_gauge - Start!!
init_fuel_gauge - CGAIN=0x3cd5
check_battery_type: fuel_temp = 34, adc_temp = 40
set_fuel_gauge_parameter: battery_type = 1
init_fuel_gauge - Already initialized!! (SDI type)
fuel_gauge_test_read - addr(0x00), data(0x0000)
fuel_gauge_test_read - addr(0x01), data(0xff00)
fuel_gauge_test_read - addr(0x02), data(0x7f80)
fuel_gauge_test_read - addr(0x03), data(0xff01)
fuel_gauge_test_read - addr(0x04), data(0x0000)
fuel_gauge_test_read - addr(0x05), data(0x1e4c)
fuel_gauge_test_read - addr(0x06), data(0x5f6c)
fuel_gauge_test_read - addr(0x07), data(0x4d58)
fuel_gauge_test_read - addr(0x08), data(0x224c)
fuel_gauge_test_read - addr(0x09), data(0xca7a)
fuel_gauge_test_read - addr(0x0a), data(0xf5f3)
fuel_gauge_test_read - addr(0x0b), data(0xec06)
fuel_gauge_test_read - addr(0x0d), data(0x48e6)
fuel_gauge_test_read - addr(0x0e), data(0x5f5f)
fuel_gauge_test_read - addr(0x0f), data(0x1e4d)
fuel_gauge_test_read - addr(0x10), data(0x1fc0)
fuel_gauge_test_read - addr(0x11), data(0x0bfb)
fuel_gauge_test_read - addr(0x12), data(0x7d5a)
fuel_gauge_test_read - addr(0x14), data(0x021f)
fuel_gauge_test_read - addr(0x16), data(0x2055)
fuel_gauge_test_read - addr(0x17), data(0x0d70)
fuel_gauge_test_read - addr(0x18), data(0x290a)
fuel_gauge_test_read - addr(0x19), data(0xc859)
fuel_gauge_test_read - addr(0x1a), data(0x2716)
fuel_gauge_test_read - addr(0x1b), data(0xd099)
fuel_gauge_test_read - addr(0x1c), data(0x23e9)
fuel_gauge_test_read - addr(0x1d), data(0x2210)
fuel_gauge_test_read - addr(0x1e), data(0x0520)
fuel_gauge_test_read - addr(0x1f), data(0x1def)
fuel_gauge_test_read - addr(0x21), data(0x0092)
fuel_gauge_test_read - addr(0x23), data(0x2934)
fuel_gauge_test_read - addr(0x24), data(0x1400)
fuel_gauge_test_read - addr(0x25), data(0x2305)
fuel_gauge_test_read - addr(0x27), data(0x6d46)
fuel_gauge_test_read - addr(0x29), data(0x87a4)
fuel_gauge_test_read - addr(0x2a), data(0x506b)
fuel_gauge_test_read - addr(0x2b), data(0x0010)
fuel_gauge_test_read - addr(0x2c), data(0xe3e1)
fuel_gauge_test_read - addr(0x2d), data(0x290e)
fuel_gauge_test_read - addr(0x2e), data(0x3cd5)
fuel_gauge_test_read - addr(0x2f), data(0x0000)
fuel_gauge_test_read - addr(0x32), data(0x0800)
fuel_gauge_test_read - addr(0x33), data(0x0000)
fuel_gauge_test_read - addr(0x36), data(0x0100)
fuel_gauge_test_read - addr(0x37), data(0x05e0)
fuel_gauge_test_read - addr(0x38), data(0x0089)
fuel_gauge_test_read - addr(0x39), data(0x132a)
fuel_gauge_test_read - addr(0x3a), data(0x1458)
fuel_gauge_test_read - addr(0x3b), data(0x057f)
fuel_gauge_test_read - addr(0x3d), data(0x1008)
fuel_gauge_test_read - addr(0x3f), data(0xe000)
fuel_gauge_test_read - addr(0xfb), data(0xcd7e)
fuel_gauge_test_read - addr(0xff), data(0x47ae)
fuel_gauge_read_vfsoc : VFSOC(71), data(0x47ae)
fuel_gauge_read_vcell : VCELL(4052), data(0xca9c)
calculate_sdi_table_soc: Get table SOC in case of not charging!!
calculate_sdi_table_soc: vcell(4052), table_soc(91)
[VFSOC_Patch] differ(3), table_soc(91), vfsoc(71)
fuel_gauge_read_vfsoc : VFSOC(71), data(0x47ae)
fuel_gauge_read_vcell : VCELL(4052), data(0xca9c)
calculate_sdi_table_soc: Get table SOC in case of not charging!!
calculate_sdi_table_soc: vcell(4052), table_soc(91)
[VFSOC_Patch] differ(3), table_soc(91), vfsoc(71)
fuel_gauge_read_vfsoc : VFSOC(71), data(0x47ae)
fuel_gauge_read_vcell : VCELL(4052), data(0xca9c)
fuel_gauge_read_soc : SOC(95), data(0x5f6c)
calculate_sdi_table_soc: Get table SOC in case of not charging!!
calculate_sdi_table_soc: vcell(4052), table_soc(91)
fuel_gauge_read_vfsoc : VFSOC(71), data(0x47ae)
fuel_gauge_read_soc : SOC(95), data(0x5f6c)
fuel_gauge_read_soc : SOC(95), data(0x5f6c)
init_microusb_ic: MUIC: CONTROL1:0x3f
init_microusb_ic: MUIC: CONTROL1:0x3f
init_microusb_ic: MUIC: CONTROL2:0x3a
init_microusb_ic: MUIC: CONTROL2:0x3a
Secondary Bootloader v3.1 version.
Copyright (C) 2011 System S/W Group. Samsung Electronics Co., Ltd.
Board: P4 REV 02 / Jan 5 2012 22:13:13
current time: 0/1/3 0:9:31
booting code=0x0
[set_mmc_ocr] Sector Mode
[hsmmc_init] MMC card is detected
Product Name : MAG4FA
CID:150100 4d414734 4641196e c10e81f
<display_card_info:1043> ext_csd
<display_card_info:1045>card_size: 15028
Total Card Size: 15029 MByte
Total Sector Count: 30777344
MoviNand Initialization Complete!
===== PARTITION INFORMATION =====
ID : GANG (0x0)
DEVICE : MMC
FIRST UNIT : 0
NO. UNITS : 0
=================================
ID : BOOT (0x1)
DEVICE : MMC
FIRST UNIT : 0
NO. UNITS : 0
=================================
ID : EFS (0x4)
DEVICE : MMC
FIRST UNIT : 8192
NO. UNITS : 40960
=================================
ID : SBL1 (0x2)
DEVICE : MMC
FIRST UNIT : 49152
NO. UNITS : 2560
=================================
ID : SBL2 (0x3)
DEVICE : MMC
FIRST UNIT : 53248
NO. UNITS : 2560
=================================
ID : PARAM (0x5)
DEVICE : MMC
FIRST UNIT : 57344
NO. UNITS : 16384
=================================
ID : KERNEL (0x6)
DEVICE : MMC
FIRST UNIT : 73728
NO. UNITS : 16384
=================================
ID : RECOVERY (0x7)
DEVICE : MMC
FIRST UNIT : 90112
NO. UNITS : 16384
=================================
ID : CACHE (0x8)
DEVICE : MMC
FIRST UNIT : 106496
NO. UNITS : 409600
=================================
ID : FACTORYFS (0xa)
DEVICE : MMC
FIRST UNIT : 516096
NO. UNITS : 1572864
=================================
ID : DATAFS (0xb)
DEVICE : MMC
FIRST UNIT : 2088960
NO. UNITS : 27615232
=================================
ID : HIDDEN (0xc)
DEVICE : MMC
FIRST UNIT : 29704192
NO. UNITS : 1048576
=================================
ID : FOTA (0xd)
DEVICE : MMC
FIRST UNIT : 30752768
NO. UNITS : 16384
=================================
loke_init: j4fs_open..fsd_reclaim 1287: MST is not recognized(mst.magic=0x72726624)
fsd_reclaim 1288: MST is not recognized
fsd_reclaim 1603: Error(nErr=0x00000000)
fsd_reclaim 1608: j4fs_rw_start is set to default value(128KB)
j4fs_open 154: Error(nErr=0x40000000)
failed
init_ddi_data: usable ddi data.
j4fs_read_file_bootloader 356: j4fs panic
nps status file does not exist..
nps status is incorrect!! set default status.(completed)
nps status=0x504d4f43
PMIC_IRQSRC = 0x00
PMIC_IRQ1 = 0x00
PMIC_IRQ2 = 0x08
PMIC_IRQ3 = 0x00
PMIC_IRQ4 = 0x11
PMIC_STATUS1 = 0x00
PMIC_STATUS2 = 0x16
PMIC_STATUS3 = 0x03
PMIC_STATUS4 = 0x00
bootloader base address=0x4d400000
LPDDR0 1st. cached=0x40000000, size=0xe400000
LPDDR0 non-cached=0x4e400000, size=0xa00000
LPDDR0 2nd. cached=0x4ee00000, size=0x1200000
RST_STAT = 0x20000000
get_hwrev() = 11
board_process_platform: MAGIC 0 at 40004000!
check_reboot: INFORM3 = 12345670
save param.blk, size: 5268
j4fs_write_file_bootloader 185: j4fs panic
mbcctrl = d4
mbcctrl = 14
mbcctrl = 14
fuel_gauge_read_vcell : VCELL(4051), data(0xca98)
pm_check_low_battery: Now, Start Booting...
check_30pin_cable: ch4. ADC value = 4095
check_30pin_cable: ch4. ADC value = 4088
check_30pin_cable: ch4. ADC value = 4093
microusb_get_attached_device: STATUS1:0x3f, 2:0x00
hw_pm_status: chg_status = 0, INFORM2 = 12345678
AST_POWERON..
......kernel is non signed binary.
div:15, FB_SOURCE_CLOCK:800000000, FB_PIXEL_CLOCK:53988360
mDNIe is enabled
check_lcdtype : adc=1135, lctype=1
Autoboot (0 seconds) in progress, press any key to stop
boot_kernel: debug level low!
checkbit (00000000)
......kernel (id 0) is non signed binary.
ATAG_CORE: 5 54410001 0 0 0
MEMCONFIG: 20e01323 20e01323
ATAG_MEM: 4 54410002 10000000 40000000
ATAG_MEM: 4 54410002 10000000 50000000
ATAG_MEM: 4 54410002 10000000 60000000
ATAG_MEM: 4 54410002 10000000 70000000
ATAG_SERIAL: 4 54410006 c10e81f 4641196e
ATAG_REVISION: 3 54410007 b
ATAG_CMDLINE: 47 54410009 'console=ttySAC2,115200 loglevel=4 sec_debug.enable=0 sec_debug.enable_user=0 c1_watchdog.sec_pet=5 [email protected] s3cfb.bootloaderfb=0x5ec00000 lcdtype=1 consoleblank=0 lpj=3981312 vmalloc=144m an'
ATAG_NONE: 0 0
Starting kernel at 0x40008000...
default env settings:
SBL> printenv
PARAM Rev 1.3
SERIAL_SPEED : 7
LOAD_RAMDISK : 0
BOOT_DELAY : 0
LCD_LEVEL : 97
SWITCH_SEL : 1
PHONE_DEBUG_ON : 0
LCD_DIM_LEVEL : 0
LCD_DIM_TIME : 6
MELODY_MODE : 1
REBOOT_MODE : 0
NATION_SEL : 0
LANGUAGE_SEL : 0
SET_DEFAULT_PARAM : 0
FLASH_LOCK_STATUS : 1
PARAM_INT_14 : 0
VERSION : I9000XXIL
CMDLINE : console=ttySAC2,115200 loglevel=4
DELTA_LOCATION : /mnt/rsv
PARAM_STR_3 :
PARAM_STR_4 :

Can you provide a how-to install ubuntu on the gtab? or provide a link to which instructions you followed to install it? Thanks

bdds13 said:
Can you provide a how-to install ubuntu on the gtab? or provide a link to which instructions you followed to install it? Thanks
Click to expand...
Click to collapse
2 steps:
ubuntu rootfs on tf card;
flash the attached zImage file with:
heimdall flash --kernel zImage

Fyi, if you can build a kernel with sec_log support, you can get this bootloader info as well (on /proc/last_kmsg). I backported sec_log to the hc kernel from the galaxys2 ics source at a couple of points, it is pretty straightforward.

locerra said:
Fyi, if you can build a kernel with sec_log support, you can get this bootloader info as well (on /proc/last_kmsg). I backported sec_log to the hc kernel from the galaxys2 ics source at a couple of points, it is pretty straightforward.
Click to expand...
Click to collapse
thanks, I just had a look, it's on in my kernel, will check the messages in /proc

jackqin said:
I recently installed ubuntu on GT-P6210, it works fine until i tried to port some drivers from Linaro Origen source
Click to expand...
Click to collapse
Can you provide any details as to what was working and what wasn't? Hardware wise?
Thanks

SirFunk said:
Can you provide any details as to what was working and what wasn't? Hardware wise?
Thanks
Click to expand...
Click to collapse
I just needed framebuffer console, so I didn't get to X interface, for now, I can say multi-touch device is working, coz I saw touch events.
most other devices should work, since the kernel is from Gary's working one, and I did some minor modifications to let Linux boot.
I'll work on it and try to put together a rather complete rootfs, and update my progress here.

Stuck on the emergencymode yellow screen

LG Optimus T - blue
My phone is stuck in the emergency mode with the yellow screen.
Ill take you through what happened,
I wanted to update to 2.3.3, so i downloaded kdz updater and followed the tutorial on how to do so, I downloaded the ROM that i was told to download and I initiated XDA updater with the right type (3gqct) and phone mode (diag)--- right off the bat i got an error message on the program and the phone went to the emergency mode screen. I retried a good 5-7 times...nothing.
I looked around and people said to flash back to original ROM (2.2.2) and i tried that with the right stuff selected(3gqct) and emergency instead of the "diag"...but nothing.
I looked around and i have yet to find anything that can help, I cant hard reset it or any type of reset. the kdz program isnt working with any combo of steps...
I'm lost please help! I just got this phone yesterday and thought i would be doing some good updating it. But now im back to my blackberry.
Here's the Log Report:
[15:51:32:927] : =============================================
[15:51:32:927] : Log is started on 01.10.2012, at 15:51:32:927,
executable: C:\Users\Chad Kantlehner\Desktop\Android Crap\KDZ_FW_UPD_EN\KDZ_FW_UPD.exe (ProcID: 0x00000bac),
compile time : Dec 8 2010 09:19:37
[15:51:32:927] : Version :
[15:51:32:937] : Get Usb Port
[15:51:32:937] : rsi.strFriendlyName=LGE Android Platform USB Serial Port (COM3)
[15:51:32:937] : FriendlyNameList[iii].szFriendlyName=LGE Android Platform USB Serial Port
[15:51:32:937] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 1 - COM3
[15:51:32:937] : Port = COM3
[15:51:32:957] : UNKNOWN : Req(12) -> Rsp(13)
[15:51:32:967] : UNKNOWN : Req(12) -> Rsp(13)
[15:51:32:977] : UNKNOWN : Req(12) -> Rsp(13)
[15:51:32:977] : >> DIAG_STATUS_F FAILED
[15:51:32:987] : >>Get Model Name [DIAG_VERNO_F]
[15:51:32:997] : BAD CONN MODE : Req(0) -> Rsp(3)
[15:51:33:007] : BAD CONN MODE : Req(0) -> Rsp(3)
[15:51:33:017] : BAD CONN MODE : Req(0) -> Rsp(3)
[15:51:33:027] : BAD CONN MODE : Req(0) -> Rsp(3)
[15:51:33:037] : BAD CONN MODE : Req(0) -> Rsp(3)
[15:51:33:047] : BAD CONN MODE : Req(0) -> Rsp(3)
[15:51:33:047] : FAIL (No Phone)
[15:51:33:047] : GetModelName() Operation Failed Check Diag CMD
[15:51:33:047] : EMERGENCY Booting Mode
[15:51:33:047] : >>Get Model Name in Emergency Mode [DLOAD_VERREQ_F]
[15:51:33:057] : BS/P504/7DHADKA~1\AppData\Local\Temp\DZ
[15:51:33:057] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 0 - P504
[15:51:33:067] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[15:51:33:067] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[15:51:33:077] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[15:51:33:077] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[15:51:33:087] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[15:51:33:087] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[15:51:33:087] : NV Write Fail : NV ITEM 9028(9028)
[15:51:33:187] : >> GET DLOAD COMM MODE
[15:51:33:197] : [GetCommMode] Communication mode : 2
[15:51:33:197] : Pre Nand Download
[15:51:33:197] : >>Set Trusted Mode [DLOAD_NAND_SEC_MODE] sec_mode = 1 (1=trusted 0=NonTrusted)
[15:51:33:197] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - TRUSTED MODE
[15:51:33:207] : [COM3] >>NandFlashInitWithFile(PARTITION TBL)
[15:51:33:207] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - INIT PARTITION TBL
[15:51:33:227] : ¸Þ½ÃÁö º¸³¿ TYPE_WPARAM_WRITE_TO_SDRAM 3
[15:51:33:227] : [COM14] ¸Þ½ÃÁö º¸³¿ TYPE_WPARAM_WRITE_AMSS 15
[15:51:33:227] : [COM3] >>NandFlashInitWithFile(AMSS MODEM HEADER)
[15:51:33:257] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - INIT AMSS MODEM HEADER
[15:51:33:267] : [COM14] >>Dl_AsyncWrite()
[15:51:33:267] : >> AMSS FLASHING ...
[15:51:33:267] : ¸Þ½ÃÁö º¸³¿ ProgreassiveBar Init wParam TYPE_WPARAM_PROGRESSIVE_POS=5 lParam(pos)=0 nResult=0
[15:51:33:267] : Sending Pkt Seq : 0
[15:51:33:267] : Sending Pkt Seq : 1
[15:51:33:267] : Sending Pkt Seq : 2
[15:51:33:267] : Sending Pkt Seq : 3
[15:51:33:267] : Sending Pkt Seq : 4
[15:51:33:267] : Sending Pkt Seq : 5
[15:51:33:267] : Sending Pkt Seq : 6
[15:51:33:267] : Sending Pkt Seq : 7
[15:51:33:267] : Sending Pkt Seq : 8
[15:51:33:267] : Sending Pkt Seq : 9
[15:51:33:287] : Dl_AsyncWrite - ErrNo(45), Addr(0x00004800), NandErrNo(0x04)
[15:51:33:287] : [COM14] ERROR Dl_AsyncWrite() TYPE_LPARAM_UPGRADE_ERROR_WRITE_TO_FLASH
[15:51:33:287] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - Close Port
[15:51:33:287] : Close Port<<
[15:51:33:287] : TYPE_WPARAM_UPGRADE_ERROR
[15:51:33:287] : ¸Þ½ÃÁö º¸³¿ - TYPE_WPARAM_UPGRADE_ERROR Error Code = 4008
[15:51:33:367] : Log finished

First, it‘s called KDZ Updater and not XDA Updater
Second:
Windows:
Uninstall all drivers, reboot, reinstall them, reboot, deactivate LG USB Moden in Device manager (Systempanel)
Now try again. If it won‘t work either, reboot your phone and take out battery, unplug and plug in it again and repeat until it works
Btw, welcome to XDA
Edit: Now you have the log. It seems like it can not recognise your phone. Don‘t use USB HUB or something else.

DarkCoding said:
First, it‘s called KDZ Updater and not XDA Updater
Second:
Windows:
Uninstall all drivers, reboot, reinstall them, reboot, deactivate LG USB Moden in Device manager (Systempanel)
Now try again. If it won‘t work either, reboot your phone and take out battery, unplug and plug in it again and repeat until it works
Btw, welcome to XDA
Edit: Now you have the log. It seems like it can not recognise your phone. Don‘t use USB HUB or something else.
Click to expand...
Click to collapse
Lol i realized that when i was rereading it a while after iposted it.
but i did what you said and still, no results. I still have the yellow screen with emergency mode typed on it. Its not in a hub, connected directly to my laptop. and i forgot to out in the post that the only way for the pc to recognize the phone is to pull and keep the battery out of the phone while i am attempting to do stuff.
any other ideas... please iwould like to get this thing working with either ROM

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