Related
Hello,
I have a type1brick.
I corrupt the radio after failed rom flash, now If i do a classic rom update, the process stuck at 0,1%.
I modify the hpruu.ini to reinstall the ceos and can reboot.
My device is a Ipaq 6515, but all i read here look very close and bootloader command are the same and a lot work for my device...and my questions general & not specific to this device.
Now I have a working os but no Gsm and the asset info blank (stack, imei ,etc..) just Radio present = Yes (The Gps & Bluetooth is ok.
With all i read on this forum i think or i have or :
1/ a CID problem
The command i try in bootloader :
Info 0 = Beetles
Info 1 = Bootloader
info 2 = NOTHING !!!
Just USB>
2/ A Corrupted OS of the radio that i have to manually erase (cf pof solution) and rewrite.
We have the password 0000000000000000 and erase and wdata work.
Rtask test :
Rtask 1 & 2 = radio on/off = ok
Rtask 3 = Radio image loaded
Rtask 4 = radio bootloader loaded
ernal bootloader & Stuck
Rtask 0 = Reset radio ok
Rtask a = stuck
rtask b : go to external bootloader & stuck
I successfully launch the radio booloader and the Radio Rom ??
So it's the Radio OS ??
We have do a dump rom of a working device on SD card,
of this adress : 60000000 with a length of 800000.
But the sd dump to our device fail to flash (via sd card)
If in the bricked device we do :
USB>Checksum
number is ok
but with the specified adress range d2s & checksum fail.
The device show "Cal.Checksum" and nothing happen.
I was very happy to have conclusions,
and if i can believe and spend time to investigate to solve my problem,
or if it's dead. My warranty is over and HP ask for 350$ motherboard replement.
So i really ready to try everything.
Thanks in advance for your analyse and suggestions.
Dimitri
Info log when trying to update the radio rom :
LOG of a Beetle P10504_BT_HP_Radio_Patch.EXE.
It hangs at 0% when trying to upgrade and the log looks like that:
09:20:18:137 [msg] : Client_Logging() !
09:20:18:137 [msg] : =============================================
09:20:18:137 [msg] : START Client_Initialize() !
09:20:18:137 [msg] : Call CheckActiveSyncVersion() !
09:20:18:137 [msg] : Call CheckCEMode() !
09:20:21:923 [msg] : Currecnt Not in CE Mode or in CE Mode but ActiveSync Not Connected.
09:20:21:923 [msg] : Call DisconnectActiveSync() !
09:20:26:149 [msg] : Start Get Connect Port !
09:20:26:379 [msg] : Currecnt in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
09:20:26:409 [msg] : Device CE Start Address : [80000000].
09:20:26:419 [msg] : Device Radio Start Address : [0].
09:20:26:419 [msg] : END Client_Initialize() !
09:20:26:419 [msg] : =============================================
09:20:26:419 [msg] : START Client_FlashRadioOS() ! FileName : [RADIOOS.nbf] ; HeaderLen : [1260].
09:20:26:439 [msg] : END Client_FlashRadioOS() !
09:20:26:439 [msg] : =============================================
09:20:46:508 [err] : Check Radio Status Error.
Attached you find a usbmonitor of a classic Hp rom update failed :
Thank for your help ! and sorry for the long post
dim920 said:
Hello,
I have a type1brick.
I corrupt the radio after failed rom flash, now If i do a classic rom update, the process stuck at 0,1%.
I modify the hpruu.ini to reinstall the ceos and can reboot.
My device is a Ipaq 6515, but all i read here look very close and bootloader command are the same and a lot work for my device...and my questions general & not specific to this device.
Now I have a working os but no Gsm and the asset info blank (stack, imei ,etc..) just Radio present = Yes (The Gps & Bluetooth is ok.
With all i read on this forum i think or i have or :
1/ a CID problem
The command i try in bootloader :
Info 0 = Beetles
Info 1 = Bootloader
info 2 = NOTHING !!!
Just USB>
2/ A Corrupted OS of the radio that i have to manually erase (cf pof solution) and rewrite.
We have the password 0000000000000000 and erase and wdata work.
Rtask test :
Rtask 1 & 2 = radio on/off = ok
Rtask 3 = Radio image loaded
Rtask 4 = radio bootloader loaded
ernal bootloader & Stuck
Rtask 0 = Reset radio ok
Rtask a = stuck
rtask b : go to external bootloader & stuck
I successfully launch the radio booloader and the Radio Rom ??
So it's the Radio OS ??
We have do a dump rom of a working device on SD card,
of this adress : 60000000 with a length of 800000.
But the sd dump to our device fail to flash (via sd card)
If in the bricked device we do :
USB>Checksum
number is ok
but with the specified adress range d2s & checksum fail.
The device show "Cal.Checksum" and nothing happen.
I was very happy to have conclusions,
and if i can believe and spend time to investigate to solve my problem,
or if it's dead. My warranty is over and HP ask for 350$ motherboard replement.
So i really ready to try everything.
Thanks in advance for your analyse and suggestions.
Dimitri
Info log when trying to update the radio rom :
LOG of a Beetle P10504_BT_HP_Radio_Patch.EXE.
It hangs at 0% when trying to upgrade and the log looks like that:
09:20:18:137 [msg] : Client_Logging() !
09:20:18:137 [msg] : =============================================
09:20:18:137 [msg] : START Client_Initialize() !
09:20:18:137 [msg] : Call CheckActiveSyncVersion() !
09:20:18:137 [msg] : Call CheckCEMode() !
09:20:21:923 [msg] : Currecnt Not in CE Mode or in CE Mode but ActiveSync Not Connected.
09:20:21:923 [msg] : Call DisconnectActiveSync() !
09:20:26:149 [msg] : Start Get Connect Port !
09:20:26:379 [msg] : Currecnt in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
09:20:26:409 [msg] : Device CE Start Address : [80000000].
09:20:26:419 [msg] : Device Radio Start Address : [0].
09:20:26:419 [msg] : END Client_Initialize() !
09:20:26:419 [msg] : =============================================
09:20:26:419 [msg] : START Client_FlashRadioOS() ! FileName : [RADIOOS.nbf] ; HeaderLen : [1260].
09:20:26:439 [msg] : END Client_FlashRadioOS() !
09:20:26:439 [msg] : =============================================
09:20:46:508 [err] : Check Radio Status Error.
Attached you find a usbmonitor of a classic Hp rom update failed :
Thank for your help ! and sorry for the long post
Click to expand...
Click to collapse
Humm... that is quite a mouthful. Have you got the correct version of Radio_.nbf ? Not really sure how things work in ipaq. If you have not tried this already, please remove all the .nbf files (in a full rom upgrade package there are 3) except the radio_.nbf and execute the upgrade with the original cable while in the bootloader mode. The original cable is particularly recomended for radio roms. Out of the three .nbf files radio_.nbf takes the maximum time so be patient. Hope this works....and yes please do search an ipaq fora as you will get more specific help.
Thank you very much to try to help me !
The Beetles device work very close to yours.
Excuse me to come in this forum, but i look around the world forums,
but i think helpfull persons are on device like yours.
The Rom upgrade beetles from Hp come with Hpruu.exe and 4 files :
RadioOS.nbf
RadioFS.nbf
CEOS.nbf
Extrom.nbf
If i do only a selected upgrade as you say, i can reinstall the Os,
but never the Radio, always stuck at 1%.
(after os reinstall, gps & bluetooth ok, but gsm asset blank)
It's very similar problem to a lot of bricked Universal device who was
successfully unbricked here.
I spend a lot of time in the Bootloader,
I Know now that my CID is ok, but my Radio Os dead.
All success story i see here manually erase some adress range,
and manually rewrite the radio part.
I can do that in the bootloader with commande "erase" and "wdata".
But i don't know how in the other device you have successfully
find the good adress range to erase and rewrite.
How i can investigate this ?
I have all install of rom from Hp, unofficial, dump rom of a working device of a selected adress range who normally include the radio part, etc..
Thank you
Dim
Hello,
I have a type1brick.
I corrupt the radio after failed rom flash, now If i do a classic rom update, the process stuck at 0,1%.
I modify the hpruu.ini to reinstall the ceos and can reboot.
My device is a Ipaq 6515, but all i read here look very close and bootloader command are the same and a lot work for my device...and my questions general & not specific to this device.
Now I have a working os but no Gsm and the asset info blank (stack, imei ,etc..) just Radio present = Yes (The Gps & Bluetooth is ok.
With all i read on this forum i think or i have or :
1/ a CID problem
The command i try in bootloader :
Info 0 = Beetles
Info 1 = Bootloader
info 2 = NOTHING !!!
Just USB>
2/ A Corrupted OS of the radio that i have to manually erase (cf pof solution) and rewrite.
We have the password 0000000000000000 and erase and wdata work.
Rtask test :
Rtask 1 & 2 = radio on/off = ok
Rtask 3 = Radio image loaded
Rtask 4 = radio bootloader loaded
ernal bootloader & Stuck
Rtask 0 = Reset radio ok
Rtask a = stuck
rtask b : go to external bootloader & stuck
I successfully launch the radio booloader and the Radio Rom ??
So it's the Radio OS ??
We have do a dump rom of a working device on SD card,
of this adress : 60000000 with a length of 800000.
But the sd dump to our device fail to flash (via sd card)
If in the bricked device we do :
USB>Checksum
number is ok
but with the specified adress range d2s & checksum fail.
The device show "Cal.Checksum" and nothing happen.
I was very happy to have conclusions,
and if i can believe and spend time to investigate to solve my problem,
or if it's dead. My warranty is over and HP ask for 350$ motherboard replement.
So i really ready to try everything.
Thanks in advance for your analyse and suggestions.
Dimitri
Info log when trying to update the radio rom :
LOG of a Beetle P10504_BT_HP_Radio_Patch.EXE.
It hangs at 0% when trying to upgrade and the log looks like that:
09:20:18:137 [msg] : Client_Logging() !
09:20:18:137 [msg] : =============================================
09:20:18:137 [msg] : START Client_Initialize() !
09:20:18:137 [msg] : Call CheckActiveSyncVersion() !
09:20:18:137 [msg] : Call CheckCEMode() !
09:20:21:923 [msg] : Currecnt Not in CE Mode or in CE Mode but ActiveSync Not Connected.
09:20:21:923 [msg] : Call DisconnectActiveSync() !
09:20:26:149 [msg] : Start Get Connect Port !
09:20:26:379 [msg] : Currecnt in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
09:20:26:409 [msg] : Device CE Start Address : [80000000].
09:20:26:419 [msg] : Device Radio Start Address : [0].
09:20:26:419 [msg] : END Client_Initialize() !
09:20:26:419 [msg] : =============================================
09:20:26:419 [msg] : START Client_FlashRadioOS() ! FileName : [RADIOOS.nbf] ; HeaderLen : [1260].
09:20:26:439 [msg] : END Client_FlashRadioOS() !
09:20:26:439 [msg] : =============================================
09:20:46:508 [err] : Check Radio Status Error.
Attached you find a usbmonitor of a classic Hp rom update failed :
Thank for your help ! and sorry for the long post
Hi All,
I was updating my LG 540GT toswift droid 2.3 from 2.1.While using kdz_fw_upd.exe ,some error occured in between and the process was some what like stuck and not responding.So i exit the program,(meanwhile phone was showing downloading mode).So i unplugged the usb cable and removed the battery to restart it.But after that it is not even switching ON.i tried to go to recovery mode by pressing volume down+camera+power keys,button nothing happened.i tried home+volume up key,the same result.
i tried using Kdz_fw_upd.exe again,its showing "PHONE WAS NOT FOUND" error.I tried all the ways i could.Please help me if i can do anything with it?
Its bricked.
Sent from my GT540 using xda premium
So i cant do anything???
anoopmohamed said:
So i cant do anything???
Click to expand...
Click to collapse
if the phone doesnt turn on at all then u can't
do anything about it..
can the service center rectify it??my warranty expired lst month.i am ready to pay charge. they wiil not replace as the warranty expired.or the phone is unusable permenantly?
anoopmohamed said:
can the service center rectify it??my warranty expired lst month.i am ready to pay charge. they wiil not replace as the warranty expired.or the phone is unusable permenantly?
Click to expand...
Click to collapse
actually u do have little hope!
Follow this, this might unbrick ur phone if u
are lucky!
[HOW-TO] Repair your device if it feels like dead | When you click power button nothing happens (Note that this may or may not work)
Make sure you use USB ports that are in back of youre PC, dont use front ones.
Disable LGE Virtual Modem. In your Windows operating system, go to Control Panel > System > Hardware > Device Manager > Modems > Right click on LGE Virtual Modem and click Disable.
Try to boot your phone into Emergency/Download mode (VOL DOWN + POWER).
If the phone booted into Emergency/Download mode, launch KDZ Updater.
In TYPE dropdown menu, choose EMERGENCY.
Load KDZ(ROM) and flash your phone.
If the phone failed to boot into Emergency/Download mode (VOL DOWN + POWER), launch KDZ Updater.
In TYPE dropdown menu, choose CS_EMERGENCY.
Load KDZ(ROM) and flash your phone.
Thanks to fishears!
Thanks,
i had tried it all earlier :'( bt in vain...
cursing the moment where i thought of upgrading
anoopmohamed said:
Thanks,
i had tried it all earlier :'( bt in vain...
cursing the moment where i thought of upgrading
Click to expand...
Click to collapse
trust me i know how it feels...
the first week i got my phone i stuffed it up by trying
fastboot... then i managed to fix it myself. from then on
i stuffed my phone nearly every single time i tried something...
But i always managed to fix it!
But i guess bad luck 4 u..
Thanks dude..
i think my bootloader is gone if it is switching ON i had hope.bt
I heared something about Riff box jtag which can repair from brick..but i am not sure.
Can the service center fix this issue???
anoopmohamed said:
Thanks dude..
i think my bootloader is gone if it is switching ON i had hope.bt
I heared something about Riff box jtag which can repair from brick..but i am not sure.
Can the service center fix this issue???
Click to expand...
Click to collapse
yeah they can be changing the motherboard!
But i think that will cost more than the phone itself..
If u have warranty just say ur phone doesn't turn on and
they will give u a new one!
Actually the 1 warranty expired by last month(oct). When i purchased it,it came with 1.6,later i upgraded to 2.1 successfully.With this confidence only i planned to upgraded to swift droid 2.3.Do u know what had went wrong??
anoopmohamed said:
Actually the 1 warranty expired by last month(oct). When i purchased it,it came with 1.6,later i upgraded to 2.1 successfully.With this confidence only i planned to upgraded to swift droid 2.3.Do u know what had went wrong??
Click to expand...
Click to collapse
Yeah u took out the USB cable while flashing!
Sent from my GT540 using xda premium
but the program was non responsive and return with some error
[00:15:55:880] : TYPE_WPARAM_UPGRADE_ERROR
[00:15:55:880] : ¸Þ½ÃÁö º¸³¿ - TYPE_WPARAM_UPGRADE_ERROR Error Code = 1002...
so i had exit the program,then only i removed the cable unfortunate..
anoopmohamed said:
but the program was non responsive and return with some error
[00:15:55:880] : TYPE_WPARAM_UPGRADE_ERROR
[00:15:55:880] : ¸Þ½ÃÁö º¸³¿ - TYPE_WPARAM_UPGRADE_ERROR Error Code = 1002...
so i had exit the program,then only i removed the cable unfortunate..
Click to expand...
Click to collapse
I dont know about that ....
Sent from my GT540 using xda premium
the program showed up a windows-message that it does not work anymore ?
or was it just doing nothing ?
1st the program showed windows error(im using vista) asking the close down the program.So i closed and restarted the program and loaded the kdz file and it again started to do the work.but after few seconds it displayed some upgrade error like "WPARAM_UPGRADE_ERROR Error Code = 1002"
the log file is shown below
[00:15:21:945] : =============================================
[00:15:21:945] : Log is started on 26.11.2011, at 00:15:21:945,
executable: C:\Users\anoopmohamed\Desktop\swift droid\KDZ_FW_UPD.exe (ProcID: 0x00001120),
compile time : Sep 8 2010 17:19:53
[00:15:21:945] : Version :
[00:15:21:947] : strFilename1 = eur
[00:15:21:948] : m_DlMode = 4, m_strBinaryPath = C:\ProgramData\LGMOBILEAX\Phone\europen+fastboot.dz, m_nSelectedImages= 70787108
[00:15:46:357] : Start Web Downloading
[00:15:46:357] : Get Usb Port
[00:15:46:436] : rsi.strFriendlyName=Standard Serial over Bluetooth link (COM6)
[00:15:46:436] : Remove Standard Serial over Bluetooth link (COM6)
[00:15:46:436] : rsi.strFriendlyName=Standard Serial over Bluetooth link (COM8)
[00:15:46:436] : Remove Standard Serial over Bluetooth link (COM8)
[00:15:46:436] : rsi.strFriendlyName=Standard Serial over Bluetooth link (COM5)
[00:15:46:436] : Remove Standard Serial over Bluetooth link (COM5)
[00:15:46:436] : rsi.strFriendlyName=Standard Serial over Bluetooth link (COM7)
[00:15:46:436] : Remove Standard Serial over Bluetooth link (COM7)
[00:15:46:436] : rsi.strFriendlyName=Standard Modem over Bluetooth link #2
[00:15:46:436] : Remove Standard Modem over Bluetooth link #2
[00:15:46:436] : rsi.strFriendlyName=Nokia 6300 Bluetooth Modem
[00:15:46:436] : Remove Nokia 6300 Bluetooth Modem
[00:15:46:436] : rsi.strFriendlyName=Agere Systems HDA Modem
[00:15:46:436] : Remove Agere Systems HDA Modem
[00:15:46:436] : rsi.strFriendlyName=RIM Virtual Serial Port v2 (COM29)
[00:15:46:436] : Remove RIM Virtual Serial Port v2 (COM29)
[00:15:46:436] : rsi.strFriendlyName=RIM Virtual Serial Port v2 (COM30)
[00:15:46:436] : Remove RIM Virtual Serial Port v2 (COM30)
[00:15:46:436] : rsi.strFriendlyName=LGE Android Platform USB Serial Port (COM13)
[00:15:46:436] : FriendlyNameList[iii].szFriendlyName=LGE Android Platform USB Serial Port
[00:15:46:436] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 1 - COM13
[00:15:46:436] : Port = COM13
[00:15:46:436] : Clear
[00:15:46:437] : Clear
[00:15:46:438] : UNKNOWN : Req(12) -> Rsp(13)
[00:15:46:438] : Clear
[00:15:46:439] : UNKNOWN : Req(12) -> Rsp(13)
[00:15:46:439] : Clear
[00:15:46:440] : UNKNOWN : Req(12) -> Rsp(13)
[00:15:46:440] : >> DIAG_STATUS_F FAILED
[00:15:46:445] : >>Get Model Name [DIAG_VERNO_F]
[00:15:46:445] : Clear
[00:15:46:446] : BAD CONN MODE : Req(0) -> Rsp(3)
[00:15:46:446] : Clear
[00:15:46:447] : BAD CONN MODE : Req(0) -> Rsp(3)
[00:15:46:447] : Clear
[00:15:46:448] : BAD CONN MODE : Req(0) -> Rsp(3)
[00:15:46:448] : Clear
[00:15:46:449] : BAD CONN MODE : Req(0) -> Rsp(3)
[00:15:46:449] : Clear
[00:15:46:450] : BAD CONN MODE : Req(0) -> Rsp(3)
[00:15:46:450] : Clear
[00:15:46:451] : BAD CONN MODE : Req(0) -> Rsp(3)
[00:15:46:451] : FAIL (No Phone)
[00:15:46:451] : GetModelName() Operation Failed Check Diag CMD
[00:15:46:451] : EMERGENCY Booting Mode
[00:15:46:451] : >>Get Model Name in Emergency Mode [DLOAD_VERREQ_F]
[00:15:46:451] : Clear
[00:15:46:451] : Clear
[00:15:46:452] : BS/GT540/7D
[00:15:46:452] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 0 - GT540
[00:15:46:452] : >>Get Mobile SW [DIAG_EXT_BUILD_ID_F]
[00:15:46:452] : Clear
[00:15:46:452] : Clear
[00:15:46:453] : DLOAD_NAK_F reason_msb = 6, reason_lsb = 6
[00:15:46:453] : [ DLOAD ERROR ] : NAK_INVALID_CMD
[00:15:46:453] : Clear
[00:15:46:454] : DLOAD_NAK_F reason_msb = 6, reason_lsb = 6
[00:15:46:454] : [ DLOAD ERROR ] : NAK_INVALID_CMD
[00:15:46:454] : Clear
[00:15:46:455] : DLOAD_NAK_F reason_msb = 6, reason_lsb = 6
[00:15:46:455] : [ DLOAD ERROR ] : NAK_INVALID_CMD
[00:15:46:455] : FAIL
[00:15:46:455] : Phone_Diag_Status = FALSE
[00:15:46:455] : Clear
[00:15:46:455] : Clear
[00:15:46:456] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[00:15:46:456] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[00:15:46:456] : Clear
[00:15:46:457] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[00:15:46:457] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[00:15:46:457] : Clear
[00:15:46:458] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[00:15:46:458] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[00:15:46:458] : NV Write Fail : NV ITEM 9028(9028)
[00:15:46:558] : m_pPhoneCtrl->m_pDload->Dl_GetCommMode(&m_pPhoneCtrl->m_pDload->m_nCommMode)
[00:15:46:558] : >> GET DLOAD COMM MODE
[00:15:46:558] : Clear
[00:15:46:558] : Clear
[00:15:46:559] : [GetCommMode] Communication mode : 2
[00:15:46:559] : Pre Nand Download
[00:15:46:559] : >>Set Trusted Mode [DLOAD_NAND_SEC_MODE] sec_mode = 1 (1=trusted 0=NonTrusted)
[00:15:46:559] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - TRUSTED MODE
[00:15:46:559] : Clear
[00:15:46:559] : Clear
[00:15:46:560] : [COM13] >>NandFlashInitWithFile(PARTITION TBL), BinType =8
[00:15:46:560] : NandFlashInitWithFile :: LG3GBinaryList[BinType].szBinaryTypeName = PARTITION TBL, BinType = 8
[00:15:46:560] : NandFlashInitWithFile ::
[00:15:46:560] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - INIT PARTITION TBL
[00:15:46:560] : Clear
[00:15:46:560] : Clear
[00:15:49:672] : DLOAD_NAK_F reason_msb = 55, reason_lsb = 55
[00:15:49:672] : [ JNAND ERROR ] : ERR_RESERVED_x37
[00:15:49:672] : Clear
[00:15:52:777] : DLOAD_NAK_F reason_msb = 55, reason_lsb = 55
[00:15:52:777] : [ JNAND ERROR ] : ERR_RESERVED_x37
[00:15:52:777] : Clear
[00:15:55:880] : DLOAD_NAK_F reason_msb = 55, reason_lsb = 55
[00:15:55:880] : [ JNAND ERROR ] : ERR_RESERVED_x37
[00:15:55:880] : [COM13] FAIL
[00:15:55:880] : Clear
[00:15:55:880] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - Close Port
[00:15:55:880] : Close Port<<
[00:15:55:880] : TYPE_WPARAM_UPGRADE_ERROR
[00:15:55:880] : ¸Þ½ÃÁö º¸³¿ - TYPE_WPARAM_UPGRADE_ERROR Error Code = 1002
[00:15:55:904] : Log finished
So no process was showing later.I tried a couple of times,same.So i thought of doing it later.Exit the program.But the phone was still in DOWNLOAD MODE,then i pulled out the battery and the usb cable from it.
Hello everyone,
I'm trying to update my LG GT 540 to Gingerbread following this great tutorial. As my machine runs Debian Testing, I am using a virtual machine (in VirtualBox) with Windows XP (32 bits) for KDZ in order to install a fastboot ROM. USB forwarding is enabled in VirtualBox, all devices should be forwarded, and when I connect the phone to the computer, adb and KDZ recognize it. So far, so good.
When I try to update the ROM with KDZ, it switches the phone to download mode, does nothing for ~5 mins, and crashes with the error "wParam 100, lParam 6". The phone stays in download mode, but removing and reattaching the battery makes it boot as usual.
The LG modem is disabled in the Windows device manager. No application that might try to access the phone is running at any time. Drivers are installed as described in the instructions. I have tried all USB ports. I have also tried to remove the battery, connect the phone to the computer using USB, and then using KDZ in CS_EMERGENCY mode. Same result. Later, I manually entered download mode (removed battery, pressed volume down button and plugged the USB cable in) and tried to run KDZ, but in that case it didn't find the phone at all.
So apparently KDZ (or the virtual machine in general) are unable to find and access the phone as soon as it is in download mode. Does anybody have an idea how I could fix this?
Thank you so much for any advice. In case it's helpful, I have added the log file of KDZ:
[16:16:24:251] : =============================================
[16:16:24:251] : Log is started on 14.11.2012, at 16:16:24:251,
executable: C:\LG_KDZ-Flasher.exe (ProcID: 0x000007ac),
compile time : Sep 8 2010 17:19:53
[16:16:24:251] : Version :
[16:16:24:467] : strFilename1 = fas
[16:16:24:467] : m_DlMode = 4, m_strBinaryPath = C:\Dokumente und Einstellungen\All Users\Anwendungsdaten\LGMOBILEAX\Phone\fast.dz, m_nSelectedImages= 70787108
[16:16:50:106] : Start Web Downloading
[16:16:50:106] : Get Usb Port
[16:16:50:106] : rsi.strFriendlyName=LGE Android Platform USB Serial Port (COM4)
[16:16:50:106] : FriendlyNameList[iii].szFriendlyName=LGE Android Platform USB Serial Port
[16:16:50:106] : rsi.strFriendlyName=LGE Android Platform USB GPS NMEA Port (COM5)
[16:16:50:106] : Remove LGE Android Platform USB GPS NMEA Port (COM5)
[16:16:50:106] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 1 - COM4
[16:16:50:106] : Port = COM4
[16:16:50:116] : Clear
[16:16:50:116] : Clear
[16:16:50:136] : >> DIAG_STATUS_F FAILED
[16:16:50:146] : >>Get Model Name [DIAG_VERNO_F]
[16:16:50:146] : Clear
[16:16:50:156] : strModel = GT540
[16:16:50:156] : Read NV item: 71 NV ITEM 71 [71]
[16:16:50:156] : Clear
[16:16:50:166] : CSW
[16:16:50:166] : Banner : CSW
[16:16:50:166] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 0 - GT540
[16:16:50:166] : >>Get Mobile SW [DIAG_EXT_BUILD_ID_F]
[16:16:50:166] : Clear
[16:16:50:176] : GT540-M76XX-V20c-MAR-14-2011-XX
[16:16:50:176] : strFilename = GT540-M76XX-V20c-MAR-14-2011-XX
[16:16:50:176] : strFilename = V20
[16:16:50:176] : Flag_Phone_BIN_Eclair = TRUE
[16:16:50:176] : Clear
[16:16:50:186] : Write NV item:9028 NV ITEM 9028
[16:16:50:186] : 9028 - NV_DONE_S Item
[16:16:50:286] : _DloadMode()
[16:16:50:286] : ¸Þ½ÃÁö º¸³¿ TYPE_WPARAM_CHANGE_DLOAD 4
[16:16:50:286] : >>Change Offline Mode [DIAG_CONTROL_F/Mode = 1]
[16:16:50:286] : Clear
[16:16:50:306] : >>Change Dload Mode [DIAG_DLOAD_F]
[16:16:50:306] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - DLOAD
[16:16:50:306] : Clear
[16:16:50:306] : 2_DIAG_DLOAD_F DLOAD_RESET_F do not wait for response
[16:16:50:306] : #ifdef FEATURE_L4
[16:16:50:306] : Clear
[16:16:50:306] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - Close Port
[16:16:50:306] : Close Port<<
[16:23:30:476] : OPEN_PORT_FAIL
[16:23:30:476] : TYPE_WPARAM_UPGRADE_ERROR
[16:23:30:506] : Log finished
Click to expand...
Click to collapse
Just flashed my D802 with CM11 (todays nightly), gapps-kk-20140105-signed gapps, furnace kernel and Jishnus camera through TWRP 2.6.3.3.
After flashing my phone it stuck at the LG logo, and didn't boot into CM11. It had lines all over the screen so I held down the power button and it rebooted into CM11. But then I saw that I had these lines all over the right side of my screen, kind of like the attatched picture.
I panicked and flashed 10F using LGMobile Support Tool and now my phone is in a boot loop at the LG logo and I don't know how to get it working again. Any help please?
I've tried to boot into download mode by holding down the power button until it reboots and then quickly holding down volume up but it just goes to the boot loop again.
Hold down power button and volume button till lg logo appears. Release both buttons and immediately press them again till you arrive at the white screen for factory reset. Try it.. In case there's a custom recovery on the phone it will load it. In case it's stock recovery you're doing a factory reset which might help. If this isn't working try to get into download mode (don't forget to use the USB cable to get into it as far as I remember..) and flash again or flash custom recovery plus cm11 again but without custom kernel!
Lazy79 said:
Hold down power button and volume button till lg logo appears. Release both buttons and immediately press them again till you arrive at the white screen for factory reset. Try it.. In case there's a custom recovery on the phone it will load it. In case it's stock recovery you're doing a factory reset which might help. If this isn't working try to get into download mode (don't forget to use the USB cable to get into it as far as I remember..) and flash again or flash custom recovery plus cm11 again but without custom kernel!
Click to expand...
Click to collapse
I just got into download mode and tried to flash stock rom, but just getting errors from LGMobile Support Tool...
This is the error log from LGMobile Support Tool.
17:14:23 : Restart.....
17:14:23 : Start Date : 2014-01-17 17:14:23
17:14:23 : ---------- QM Testmode ---------
17:14:23 : ***** Check Tool Version *****
17:14:23 : Tool version : 1.6.9.0
17:14:23 : UpgradeDLL version : 2.1.5.0
17:14:23 : Current Dir : C:\ProgramData\LGMOBILEAX\B2C_Client
17:14:23 : LGE USB Driver Version :
17:14:23 : Android PDLV Version :
17:14:23 : Android NDLV Version :
17:14:23 : ******************************************
17:14:23 : [C:\ProgramData\LGMOBILEAX\Phone] Try to delete folder
17:14:23 : SetEmerModeAT()
17:14:23 : _IsConnectedPhone Call
17:14:24 : _IsConnectedPhone(0)
17:14:24 : 0 - NotConnected.
17:14:24 : 1 - Normal connect success
17:14:24 : 2 - Emergency connect success
17:14:24 : *****CheckOS Start********
17:14:24 : Microsoft_Windows7_Professional_
17:14:24 : *****CheckPCSyncPrograms Start*****
17:14:25 : PCSyncPrograms Not Found - OK and ready to upgrade
17:14:25 : Verifying phone connection...
17:14:25 : dwWaitResetTime(40000 ms)
17:14:26 : _IsConnectedPhone Call for 3GQCT
17:14:27 : Phone Mode(0)
17:14:27 : 0 - NotConnected.
17:14:27 : 1 - Normal connect success
17:14:27 : 2 - Emergency connect success
17:14:27 : _IsConnectedPhone Call
17:14:34 : _IsConnectedPhone(2)
17:14:34 : 0 - NotConnected.
17:14:34 : 1 - Normal connect success
17:14:34 : 2 - Emergency connect success
17:14:34 : Phone Mode(2)
17:14:34 : *****GetPhoneType Start*****
17:14:34 : Phone Type : CDMA_2CHIP
17:14:34 : *****GetPhoneBinaryVersion Start*****
17:14:34 : Phone Bin Version : D80210F_00
17:14:34 : *****Get ESN / IMEI / MEID Start*****
17:14:34 : ESN/IMEI/MEID : 357246058069368
17:14:36 : Check Backup and Restore model
17:14:36 : Skip Backup and Restore - Emergency mode
17:14:36 : Phone type Compare start
17:14:36 : *****CheckPCSyncPrograms Start*****
17:14:36 : PCSyncPrograms Not Found - OK and ready to upgrade
17:14:37 : ****************CheckAndDownload********************
17:14:37 : Version :
17:14:37 : ******Extract Start C:\Users\Oliver\Documents\LG\D80210A_00.kdz*****
17:14:37 : Model Dll Dir(C:\ProgramData\LGMOBILEAX\Phone\)
17:14:37 : Check 2G-4G big size kdz file..
17:14:37 : Extract 2G-4G big size kdz file..
17:14:37 : NNNNN WDB FullPath(C:\Users\Oliver\Documents\LG\D80210A_00.kdz)
17:14:37 : NNNNN Model dll FullPath(C:\ProgramData\LGMOBILEAX\Phone\LGUP_8974.dll)
17:14:37 : Extract End C:\Users\Oliver\Documents\LG\D80210A_00.kdz
17:14:38 : 01 Skip delete kdz 1.1 file...
17:14:38 : ------------------Model.dll Information-------------------
17:14:38 : Filename : LGUP_8974.dll
17:14:38 : Version : 0.2.10.0
17:14:38 : File size : 1461248
17:14:38 : File date : 2014/01/17-17:14:37
17:14:38 : PC Created date: 2014/01/17-17:14:37
17:14:38 : ----------------------------------------------------------
17:14:38 : *****Check LGCM Programs Start*****
17:14:38 : LGCM Programs Not Found - OK and ready to upgrade
17:14:38 : m_pLGCyonUpdate status change.
17:14:39 : *****WorkModelDLL Start*****
17:14:39 : strPhoneBinaryPath(C:\Users\Oliver\Documents\LG\D80210A_00.kdz)
17:14:39 : strModuleDir(C:\ProgramData\LGMOBILEAX\Phone\)
17:14:39 : strModelDLLPath(C:\ProgramData\LGMOBILEAX\Phone\LGUP_8974.dll)
17:14:39 : _DetachDLL Call
17:14:44 : _DetachDLL Call End
17:14:44 : Call fn_StartUpgrade
17:14:44 : ********* 2Chip Model.dll input Parameter*************
17:14:44 : MODEL_EVENT : 32769
17:14:44 : PhoneBinaryPath : C:\Users\Oliver\Documents\LG\D80210A_00.kdz
17:14:44 : ModuleDir : C:\ProgramData\LGMOBILEAX\Phone\
17:14:44 : BootWaitTime : 49500
17:14:44 : UsbHighSpeed : FALSE
17:14:44 : PhoneMode : 2
17:14:44 : NewPhoneBinVersion : D80210A_00
17:14:44 : ClearSI : FALSE
17:14:44 : AuthMark : 0
17:14:44 : ********* 2Chip Model.dll input Parameter End*************
17:14:47 : wParam : 20, lParam = 540
17:14:47 : MODEL DLL Event : (20, 540)
17:14:48 : Model File Count = 540
17:14:48 : wParam : 100, lParam = 51
17:14:48 : MODEL DLL Event : (100, 51)
17:14:48 : Step : TYPE_WPARAM_UPGRADE_ERROR
17:14:48 : CleanModelDll() : Free Model.dll
17:14:48 : _DetachDLL Call
17:14:53 : _DetachDLL Call End
17:14:53 : Page_Error ºÎºÐÀÔ´Ï´Ù
17:14:53 : ¿©±â´Â Retry ºÎºÐÀÔ´Ï´Ù
Okay, so using power + vol down I could make a factory reset and now it boots to 10F. But since the latest update here in Sweden is 10A I want to get it to 10A, but still getting those errors while flashing.
That's not my biggest problem. I still have the lines on my screen..... Any idea? I'm 100% sure that there has been so physical damage to the device.
On a typical monitor, those artifacts can happen if there's problem with the GPU (loose dvi cable, GPU not inserted to the motherboard correctly, static electricity, overheat, etc,etc)
now, when i saw your pic on other thread, your device is a laptop right?, windows xp on the other hand (might be an older generation laptop? they're hot!)
my guess is......Overheating. let it powered off for longer time in a cool place, 12 hour or so.
if it doesn't solve anything, you can take it to repair shops. maybe the GPU-to-monitor cable is problematic
Author of thread wanted to show us an example . He has patterned screen on LG G2, and he wanted to show us that it looks like in the pictrue .
I have very simillar problem on my Asus Transformer TF300T. I have patterned screen, after installing kernel over 1,4GHz on the CPU.
In attachment is my tablet. There is any difrence between my tablet & your phone?
pipops said:
On a typical monitor, those artifacts can happen if there's problem with the GPU (loose dvi cable, GPU not inserted to the motherboard correctly, static electricity, overheat, etc,etc)
now, when i saw your pic on other thread, your device is a laptop right?, windows xp on the other hand (might be an older generation laptop? they're hot!)
my guess is......Overheating. let it powered off for longer time in a cool place, 12 hour or so.
if it doesn't solve anything, you can take it to repair shops. maybe the GPU-to-monitor cable is problematic
Click to expand...
Click to collapse
Hazard17 said:
Author of thread wanted to show us an example . He has patterned screen on LG G2, and he wanted to show us that it looks like in the pictrue .
I have very simillar problem on my Asus Transformer TF300T. I have patterned screen, after installing kernel over 1,4GHz on the CPU.
In attachment is my tablet. There is any difrence between my tablet & your phone?
Click to expand...
Click to collapse
Correct. That's just an example, I have an LG G2.
Mine's not patterned, I just have these lines crossing my screen.
delete
Okay. Turns out that the reason that I couldn't flash 10a was that my kdz was corrupt. Downloaded it again and worked like a charm.
Still have the lines on my screen though...
MaXmeOliver said:
Correct. That's just an example, I have an LG G2.
Mine's not patterned, I just have these lines crossing my screen.
Click to expand...
Click to collapse
I hope it's not the same lines these guys experienced?
android404 said:
I hope it's not the same lines these guys experienced?
Click to expand...
Click to collapse
It's those lines for sure... ****. Guess I'll have to return it and hope that the warranty covers it.
MaXmeOliver said:
It's those lines for sure... ****. Guess I'll have to return it and hope that the warranty covers it.
Click to expand...
Click to collapse
Jævla dritt! As we say in Norwegian. Good luck.
Just a quick update - got the phone back from repair today. The warranty covered it, told them that my problem occured after a factory reset. They changed the screen and the battery(?). Be aware that this was only the lines problem, not the boot loop one.