WIFI not turn on. - Touch Diamond, MDA Compact IV General

WIFI not turn on. - Touch Diamond, MDA Compact IV General

Hi!
I can't turn on wifi. When I touch in switch it do not on. I already made several hard resets and this does not result.
How I can resolve this?

I have the same problem, anyone help us ?

1
must install slp-1.40.olinex
2
enter into bootloader
3
connect to usb (disable activesync usb)
3
open eprom.nb with an hex editor and replace 78 with your mac adress in revers mode :
for exaple
real mac is 00 - 18 - 41 - c0 - 68 - f1
be written f1 68 c0 41 18 00
at 50h - 60h
Code:
00 00 01 0D 56 40 00 00 - 00 02 6D 54 [COLOR="Red"]78 78 78 78 [/COLOR]| [email protected][COLOR="red"]xxxx[/COLOR]
[COLOR="Red"]78 78[/COLOR] 00 00 01 15 58 A4 - 00 00 00 01 31 56 01 02 | [COLOR="red"]xx[/COLOR]....X.....1V..
so will become
Code:
00 00 01 0D 56 40 00 00 - 00 02 6D 54 [COLOR="Red"]F1 68 C0 41 [/COLOR]| [email protected][COLOR="red"]ñhÀA[/COLOR]
[COLOR="Red"]18 00[/COLOR] 00 00 01 15 58 A4 - 00 00 00 01 31 56 01 02 | [COLOR="red"]..[/COLOR]....X.....1V..
4
copy eprom.nb into directory of mtty
5
open mtty
command :
task 32
lnb eprom.nb 880fc000 320
lnb eprom.nb 8839d9c0 320
reset
Tell me if solved

hi all
I have done exactly as laid out above but its doesn't seem to work. would it make any difference if the spl is signed or unsigned version?
Also does it matter what version of mtty you use?
any help you could shed on this would be great.
thanks in advance.

mrlard12 said:
hi all
I have done exactly as laid out above but its doesn't seem to work. would it make any difference if the spl is signed or unsigned version?
Also does it matter what version of mtty you use?
any help you could shed on this would be great.
thanks in advance.
Click to expand...
Click to collapse
i use unsigned version

i have the same problem, except that wifi can recive a small part of the signal..
I have a 300n router and i can see its signial only staying next to it...tne phone gives a low level data reception and has difficulties to get the ip....
i 'll change hard spl soon

LucaAL said:
i have the same problem, except that wifi can recive a small part of the signal..
I have a 300n router and i can see its signial only staying next to it...tne phone gives a low level data reception and has difficulties to get the ip....
i 'll change hard spl soon
Click to expand...
Click to collapse
but this solution is only wlan not turn on

not to turn on it is very similar to not to connect....by the way no changes after having installed the radio 1.17... i donnow if i have installed the hard spl 1.93 ..i did it but he is always 1.4...

LucaAL said:
not to turn on it is very similar to not to connect....by the way no changes after having installed the radio 1.17... i donnow if i have installed the hard spl 1.93 ..i did it but he is always 1.4...
Click to expand...
Click to collapse
ita :
allora da quello che ho capito
hai un router sitecom 300n
e il diamond non si connette anche se lo vede come segnale ?
eng :
then from what I understand
you have a router Sitecom 300N
and the diamond does not connect even though it sees as a signal?

I am sorry for my error....i have solved my problem disassembling the device and reassembling the cpu zone; there were a cple not enough plugged in his hole
Ita: inoltre ciao e scusate per il disturbo

gruptnt said:
1
must install slp-1.40.olinex
2
enter into bootloader
3
connect to usb (disable activesync usb)
3
open eprom.nb with an hex editor and replace 78 with your mac adress in revers mode :
for exaple
real mac is 00 - 18 - 41 - c0 - 68 - f1
be written f1 68 c0 41 18 00
at 50h - 60h
Code:
00 00 01 0D 56 40 00 00 - 00 02 6D 54 [COLOR="Red"]78 78 78 78 [/COLOR]| [email protected][COLOR="red"]xxxx[/COLOR]
[COLOR="Red"]78 78[/COLOR] 00 00 01 15 58 A4 - 00 00 00 01 31 56 01 02 | [COLOR="red"]xx[/COLOR]....X.....1V..
so will become
Code:
00 00 01 0D 56 40 00 00 - 00 02 6D 54 [COLOR="Red"]F1 68 C0 41 [/COLOR]| [email protected][COLOR="red"]ñhÀA[/COLOR]
[COLOR="Red"]18 00[/COLOR] 00 00 01 15 58 A4 - 00 00 00 01 31 56 01 02 | [COLOR="red"]..[/COLOR]....X.....1V..
4
copy eprom.nb into directory of mtty
5
open mtty
command :
task 32
lnb eprom.nb 880fc000 320
lnb eprom.nb 8839d9c0 320
reset
Tell me if solved
Click to expand...
Click to collapse
It don't work...
People, pls another solution?

I did as mention but honestly I don`t know where to find the MAC address of my device. In wireless, because it cannot be turned on, I cannot see the MAC address. Anyway, I try and change it like in your example, using the same MAC as you provided, but nothing happens. Any help appreciated!

Related

HardSpl ends up in "Error [270]: Update Error"

Hi,
I intend to flash a cooked ROM (ITsPapa20748) to my Herald. From reading some sticky posts here I learned that at first I have to install a hacked bootloader - so I downloaded HardSpl_WM6.rar
My procedure was as follows:
1. install canonyang, ASerg_Policies and Disable_Security (in this order)
2. softreset
3. start RUU
My mobile then enters bootloader mode and ends up with error message "Error [270]: Update Error" (progress bar freezes at 3pct)
My config is as follows:
PC: is running WindowsXP (with SP2), ActiveSync v4.5 is in Guest Mode
Mobile: Model-Nr. Hera100
ROM version 4.17.402.102 GER
IPL 4.17.0001
SPL 4.17.0000
I had to UNcheck the start/system/advanced_networking-box in order to establish USB-connection.
After spending some hours going through existing threads I'm pretty sure that this is a common situation. But I didn't find any hint that helped me to flash successfully.
So any comments and suggestions are welcome.
thx!
1aladdin1

it works now
sorry for posting too early - now it worked.
I basically performed the same steps as listed in my previous post. Two differences:
1. softreset between installation of canonyang/aserpolicy/disable_security
2. while performing the RUU I had FILEMON running (a great tool from mark russinovich)
Finally I don't know, which step was the decisive one - bot anyhow it works now.
Hope this helps other guys in a similar situation.

please guys help me
my htc touch p3452 is dead becoz i flash but something is wrong and then it was dead now it will on on bootloder mode(red,green,blue) here is my detail please tell ,me what to do
it show..
IPL 3.07.0002
SPL 3.07.0000
DEVICE ID= ELF010050
CID= DOPOD001
45 4C 46 30 31 30 30 35 30 00 00 00 00 00 00 00 ELF010050.......
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
44 4F 50 4F 44 30 30 31 00 00 00 00 00 00 00 00 DOPOD001........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 ..............
i also tryed to flash "DID-ELF010050_CID-DOPOD001_ROM-2.20.721.2B" but is not flashed it gave "error 270 update error" something please tell me where is the problem and how to solve please guys

Wwwwwweeeellllllll....YOU HAVE AN ELF, NOT A HERALD. Seriously, if you tried to HardSPL your Elf with the Herald HardSPL...I don't even know. These are the Herald forums, NOT the Elf forums, as such, more than likely no one that frequents here will know what to do to help you.

Big Problem - Not Possible to Flash

Hello guys
After i Installed CM10, the Auto Rotating dont Works.
For this reason, I wanted to go back to ICS.
Unfortunately, not everything went well on ICS after the down grade of JB and the IMEI was not recognized. Now I tried again to flash JB, and he always stops at "iParam207". The boot loader also writes Critical Error unable to start kernel boot unrecoverable error
I have always respected all the steps when flashing. But now it no longer works, even in emergency mode. Even with the LG update tool it is not because he supposedly always loses the connection to the phone.
Does anyone have an idea? Thank you and sorry for the Google English
BTW: Offical LG Update Tool means, that the Connection break all 1 min... Not possible to Update with this or make emergeny Flash... :/

Use search before posting.
Search for the thread rollback to ICS and follow the Instructions there.
There you go http://forum.xda-developers.com/showthread.php?t=2179126
It should work with post 1 but you can look at the post 7 as well and don't forget to say thanks to the original authors.
Sent from my LG-P880 using xda premium
Hit the Thanks Button in each and every reply that you get against your queries.

Read First!!!!
sPEADy said:
Use search before posting.
Search for the thread rollback to ICS and follow the Instructions there.
There you go http://forum.xda-developers.com/showthread.php?t=2179126
It should work with post 1 but you can look at the post 7 as well and don't forget to say thanks to the original authors.
Sent from my LG-P880 using xda premium
Hit the Thanks Button in each and every reply that you get against your queries.
Click to expand...
Click to collapse
This Tread i have already USE !!!! But not works by me.. Please Read my Question right before answer!!!!
i CANT!!!! Flash anyway... With Flashtool,or with KDZUpdate it dont works anyway... Perhabs i have lose my
IMEI ... i need a way to programming complete my Bootloader... dnt knw...
PS. Deutsch?

Have you changed the port number to 41?
Take the battery out before you connect your phone with PC and be quick to insert it back as soon you see the LG logo. After that just wait and let windows install drivers.
You need the correct dll file as well which is similar to the version you want to install.
Sent from my LG-P880 using xda premium

Joshy6 said:
This Tread i have already USE !!!! But not works by me.. Please Read my Question right before answer!!!!
i CANT!!!! Flash anyway... With Flashtool,or with KDZUpdate it dont works anyway... Perhabs i have lose my
IMEI ... i need a way to programming complete my Bootloader... dnt knw...
Click to expand...
Click to collapse
did tried reinserting the battery? I khow, this may sound wierd, but when I flasher CM no app was recognising my phone. I even couldn't get into S/W mode. I wanted to flash back to stock. I just reinserted the battery and everything was fine about getting into S/W mode. I don't know about IMEI though.

Subhajitdas298 said:
did tried reinserting the battery? I khow, this may sound wierd, but when I flasher CM no app was recognising my phone. I even couldn't get into S/W mode. I wanted to flash back to stock. I just reinserted the battery and everything was fine about getting into S/W mode. I don't know about IMEI though.
Click to expand...
Click to collapse
I Have Port change yes.
I have tried so much DLL with other .DZ files... NO WAY!!! it breaks everytime by 10%... Fail to Download...
Reinserting Battery i have tested too... Not any Change.
PS. the SW Update Mode starting, but is no way possible to flash ... With LG Mobile Support Tool too...

Joshy6 said:
I Have Port change yes.
I have tried so much DLL with other .DZ files... NO WAY!!! it breaks everytime by 10%... Fail to Download...
Reinserting Battery i have tested too... Not any Change.
PS. the SW Update Mode starting, but is no way possible to flash ... With LG Mobile Support Tool too...
Click to expand...
Click to collapse
Try Kdz updater again. I never had this problem. I am really sorry for you.

try to see log file inside log folder created in the same folder of the dll you used -may be it has more info

Subhajitdas298 said:
Try Kdz updater again. I never had this problem. I am really sorry for you.
Click to expand...
Click to collapse
Sorry. Dont Work.
And the Fastboot menu dont work too...
i come not in the Menu with "-" and Power.... Write only unable to start Kernel....
Is there a way to only flash a new bootloader?
Only way i can anything do is S/W Upgrad, but dont works with normal flashtools...

[17:02:22.616]Selected 7 Binary : c:\users\siciliana\desktop\lg flashtool and accessories\dll and dz file\gp880at-00-v20a-eur-xxx-mar-04-2013+0.dz
[17:02:22.616]DoDownload : Retry(1)
[17:02:22.616]###### Port Opend(41) ######
[17:02:22.616]Opened COM41
[17:02:22.616]=====================================================
[17:02:22.616]= DLL Info : Dec 12 2012 11:01:58
[17:02:22.616]=====================================================
[17:02:22.648] MODEL880
[17:02:22.804] IMEI:
[17:02:22.960] PID:
[17:02:23.116] SWV:
[17:02:23.116][VerReq]
[17:02:23.116]Model Name : Target(P880)
[17:02:23.116][FeatureQuery]
[17:02:23.131]This firmware supports the following features:
[17:02:23.131] - Protocol Version : 3
[17:02:23.131] - CP Download : TRUE
[17:02:23.131] - AP Download : TRUE
[17:02:23.131] - ROM Download : TRUE
[17:02:23.131] - MaxPacketLength : 0x40000
[17:02:23.131] - Battery Level : 87%
[17:02:23.131] - OperatingMode : 4
[17:02:23.131] - AutoUpdateBuffer : 1
[17:02:23.131] - ThreadOn : 1
[17:02:23.131] - Flashless : 0
[17:02:23.131] - UpdateBct : 0
[17:02:23.350] Dz Information
[17:02:23.350] - Model Name : Binary(P880)
[17:02:23.350] - SWV : GP880AT-00-V20a-EUR-XXX-MAR-04-2013+0
[17:02:23.350] - BuildTime : 2013-03-04 05:54:18
[17:02:23.350] - SecureType : 1
[17:02:23.350] - TotalFiles : 10
[17:02:23.350] Loading FLS
[17:02:23.677]IntelFlash::GetDownloadSize
[17:02:23.677] - PSI : 35316
[17:02:23.677] - EBL : 157172
[17:02:23.677] - Hardware : 172
[17:02:23.677] - Security : 2048
[17:02:23.677] - DownloadData : 20572
[17:02:23.677] - Security : 2048
[17:02:23.677] - DownloadData : 167768
[17:02:23.677] - Security : 2048
[17:02:23.677] - DownloadData : 697892
[17:02:23.677] - Security : 2048
[17:02:23.677] - DownloadData : 356380
[17:02:23.677] - Security : 2048
[17:02:23.677] - DownloadData : 7864472
[17:02:23.677] Loading CFG
[17:02:23.708]NvidiaFlash::GetDownloadSize
[17:02:23.708] - BCT : 6128
[17:02:23.708] - EBT : 1132440
[17:02:23.708] - EKS : 684
[17:02:23.708] - SOS : 8232960
[17:02:23.724] - LNX : 7124992
[17:02:23.724] - APP : 941138264
[17:02:23.724]TotalSize : 84628329
[17:02:23.724]CP Download Starting : 0
[17:02:23.724]CP Binary has been loaded(9349520)
[17:02:23.724][Intel] MemoryMap
[17:02:23.724] FlashStartAddr : 0x40000000
[17:02:23.724] CUST : StartAddress(0x63000000), Length(0x00500000) : LINUX
[17:02:23.724] CUST : StartAddress(0x38000000), Length(0x08400000) : CLONE
[17:02:23.724] CUST : StartAddress(0x30000000), Length(0x08400100) : PREFLASH
[17:02:23.724] CUST : StartAddress(0x20000000), Length(0x00500000) : USBRO_ISO
[17:02:23.724] CUST : StartAddress(0x90000000), Length(0x001FE000) : CUSTDATA
[17:02:23.724][CMD_Intel_DownloadMode]
[17:02:24.301] - Device synchronized
[17:02:24.301][Injecting PSI RAM] : 35316
[17:02:24.301] - Sending PSI RAM
[17:02:27.374] - Receiving CRC
[17:02:27.390] - Received CRC OK : 01
[17:02:27.390] - Receiving ACK
[17:02:27.406] - Received ACK : 01 00 AA
[17:02:27.406] - PSI RAM Running
[17:02:27.406][Injecting EBL] : 157172
[17:02:27.406] - Sending EBL Length
[17:02:27.421] - Receiving ACK
[17:02:27.437] - Received ACK : 0xCCCC
[17:02:27.437] - Sending EBL : 157172
[17:02:41.212] - Sending CRC : FA
[17:02:41.227] - Receiving ACK
[17:02:41.274] - Received OK : 51 A5
[17:02:41.274] - Receiving Capabilities : 76
[17:02:41.290] - Boot-loader is active
[17:02:41.290] - EBL version: XMM6260_20.21_M1S1
[17:02:41.290] - Boot mode is: 00BB
[17:02:41.290] - EBL Running
[17:02:41.290][ReqSetProtConf]
[17:02:41.290] == prot_capabilities_t ==
[17:02:41.290] - protocol_version : 11
[17:02:41.290] - package_size : 2 -> 8
[17:02:41.290] - crc_type : 1
[17:02:41.290] - skip_writeblock_tx : 0
[17:02:41.290] - compression : 11 -> 10
[17:02:41.290] - compression : 10
[17:02:41.290] - flags : 1
[17:02:41.290] - erase_sector_verify : 0
[17:02:41.290] - flash_debug : 0
[17:02:41.290] - protocol_crc : 0
[17:02:41.290] - skip_erase : 1 -> 0
[17:02:41.290] - skip_wr_pack_crc : 0
[17:02:41.290] - Sending capabilities
[17:02:41.321] - Receiving ACK
[17:02:41.336] - Received : ACK 0100
[17:02:41.336][CnfBaudChange] : 3250000
[17:02:41.336] - Sending BaudRate
[17:02:41.352] - Receiving ACK
[17:02:41.399] - Received BaudRate : 3250000
[17:02:41.399] - Changing BaudRate
[17:02:41.414] - Changed BaudRate : 3250000
[17:02:41.414][ReqFlashId]
[17:02:41.414] - Platform : 14
[17:02:41.414] - ProjectName : XMM6260
[17:02:41.414] - Sending HardWare Info
[17:02:41.430] - Receiving ACK
[17:02:41.446][ERROR] Type : 0041 <> 0801
[17:02:41.446] - IndErrorMsg
[17:02:41.461]File_id(34), Line_number(291), Error_class(1), Error_code(70)
[17:02:41.461]File_id(16), Line_number(546), Error_class(1), Error_code(7)
[17:02:41.461]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:02:41.461]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:02:41.461]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:02:41.461]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:02:41.461]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:02:41.461]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:02:41.461] - Failure!
[17:02:41.461]ERROR : _Func_02_Ebl_3_ReqFlashId - Line(266)
[17:02:41.461]__Proc_NormalDownload : 0
[17:02:41.461]Error! IntelFlash:__Proc_NormalDownload
[17:02:41.461]_DoDownload : 0
[17:02:41.461]
-----------------------------------------Trace Last 100 Message-------------------------------------------------
[17:02:33.895][T008207] 44 00 00 00 00 20 00 00 10 27 00 00 D4 1D 7E 0E E1 8B E0 24 C0 9D E5 07 C0 CE E5 03 C0 D5 E3 1B D........'.........$............
[17:02:34.613][R000010] 44 00 00 00 00 20 00 00 67 F3 D.......g.
[17:02:34.613][T008207] 44 00 00 00 00 20 00 00 10 27 00 00 D4 1D 7E 4C 12 9F E5 80 00 81 E0 B0 00 D0 E1 01 10 45 E2 01 D........'.....L.............E..
[17:02:35.330][R000010] 44 00 00 00 00 20 00 00 67 F3 D.......g.
[17:02:35.330][T008207] 44 00 00 00 00 20 00 00 10 27 00 00 D4 1D 7E 03 11 83 E0 90 3D 1F E5 01 21 D3 E7 70 1D 1F E5 70 D........'..........=...!..p...p
[17:02:36.048][R000010] 44 00 00 00 00 20 00 00 67 F3 D.......g.
[17:02:36.048][T008207] 44 00 00 00 00 20 00 00 10 27 00 00 D4 1D 7E B0 10 D1 E1 9C C2 9F E5 81 30 8C E0 05 11 85 E0 C8 D........'..............0.......
[17:02:36.766][R000010] 44 00 00 00 00 20 00 00 67 F3 D.......g.
[17:02:36.766][T008207] 44 00 00 00 00 20 00 00 10 27 00 00 D4 1D 7E 00 41 00 00 4F 00 00 00 01 00 00 00 00 11 00 00 01 D........'......A..O............
[17:02:37.483][R000010] 44 00 00 00 00 20 00 00 67 F3 D.......g.
[17:02:37.483][T008207] 44 00 00 00 00 20 00 00 10 27 00 00 D4 1D 7E 01 00 00 1A 00 00 A0 E3 CE FF FF EA 00 00 D2 E5 58 D........'.....................X
[17:02:38.201][R000010] 44 00 00 00 00 20 00 00 67 F3 D.......g.
[17:02:38.201][T008207] 44 00 00 00 00 20 00 00 10 27 00 00 D4 1D 7E 00 F0 20 E3 00 00 A0 E3 30 80 BD E8 00 F0 20 E3 00 D........'.............0........
[17:02:38.918][R000010] 44 00 00 00 00 20 00 00 67 F3 D.......g.
[17:02:38.918][T008207] 44 00 00 00 00 20 00 00 10 27 00 00 D4 1D 7E 06 10 A0 E1 00 00 42 E0 05 00 80 E0 01 50 80 E2 01 D........'...........B......P...
[17:02:39.636][R000010] 44 00 00 00 00 20 00 00 67 F3 D.......g.
[17:02:39.636][T008207] 44 00 00 00 00 20 00 00 10 27 00 00 D4 1D 7E 64 08 1F E5 10 20 90 E5 0C 10 90 E5 07 30 A0 E1 06 D........'.....d............0...
[17:02:40.354][R000010] 44 00 00 00 00 20 00 00 67 F3 D.......g.
[17:02:40.354][T008207] 44 00 00 00 00 20 00 00 10 27 00 00 D4 1D 7E 06 F1 93 E7 38 70 9D E5 00 00 57 E3 02 00 00 1A 01 D........'.........8p....W......
[17:02:41.071][R000010] 44 00 00 00 00 20 00 00 67 F3 D.......g.
[17:02:41.071][T001539] 44 00 00 00 F4 05 00 00 10 27 00 00 B1 DB 7E 10 00 00 00 EC B1 01 01 02 02 00 00 00 08 00 00 20 D........'......................
[17:02:41.212][R000010] 44 00 00 00 F4 05 00 00 26 CC D.......&.
[17:02:41.212] - Sending CRC : FA
[17:02:41.212][T000016] 44 00 00 00 01 00 00 00 E8 03 00 00 41 0D 7E FA D...........A...
[17:02:41.227][R000010] 44 00 00 00 01 00 00 00 E7 EC D.........
[17:02:41.227] - Receiving ACK
[17:02:41.227][T000015] 43 01 00 00 02 00 00 00 E8 03 00 00 98 50 7E C............P.
[17:02:41.274][R000012] 43 00 00 00 02 00 00 00 51 A5 B4 76 C.......Q..v
[17:02:41.274] - Received OK : 51 A5
[17:02:41.274] - Receiving Capabilities : 76
[17:02:41.274][T000015] 43 01 00 00 4C 00 00 00 88 13 00 00 15 19 7E C...L..........
[17:02:41.290][R000086] 43 00 00 00 4C 00 00 00 BB 00 00 00 14 00 00 00 15 00 00 00 58 4D 4D 36 32 36 30 5F 32 30 2E 32 C...L...............XMM6260_20.2
[17:02:41.290] - Boot-loader is active
[17:02:41.290] - EBL version: XMM6260_20.21_M1S1
[17:02:41.290] - Boot mode is: 00BB
[17:02:41.290] - EBL Running
[17:02:41.290][ReqSetProtConf]
[17:02:41.290] == prot_capabilities_t ==
[17:02:41.290] - protocol_version : 11
[17:02:41.290] - package_size : 2 -> 8
[17:02:41.290] - crc_type : 1
[17:02:41.290] - skip_writeblock_tx : 0
[17:02:41.290] - compression : 11 -> 10
[17:02:41.290] - compression : 10
[17:02:41.290] - flags : 1
[17:02:41.290] - erase_sector_verify : 0
[17:02:41.290] - flash_debug : 0
[17:02:41.290] - protocol_crc : 0
[17:02:41.290] - skip_erase : 1 -> 0
[17:02:41.290] - skip_wr_pack_crc : 0
[17:02:41.290] - Sending capabilities
[17:02:41.290][T000101] 44 00 00 00 56 00 00 00 20 4E 00 00 CE 88 7E 02 00 86 00 4C 00 BB 00 00 00 14 00 00 00 15 00 00 D...V....N.........L............
[17:02:41.321][R000010] 44 00 00 00 56 00 00 00 D0 6E D...V....n
[17:02:41.321] - Receiving ACK
[17:02:41.321][T000015] 43 01 00 00 0C 00 00 00 88 13 00 00 E4 7C 7E C............|.
[17:02:41.336][R000022] 43 00 00 00 0C 00 00 00 02 00 86 00 02 00 01 00 89 00 03 00 B5 2C C....................,
[17:02:41.336] - Received : ACK 0100
[17:02:41.336][CnfBaudChange] : 3250000
[17:02:41.336] - Sending BaudRate
[17:02:41.336][T000029] 44 00 00 00 0E 00 00 00 20 4E 00 00 FB 9B 7E 02 00 82 00 04 00 50 97 31 00 9E 01 03 00 D........N...........P.1.....
[17:02:41.352][R000010] 44 00 00 00 0E 00 00 00 1E 5E D........^
[17:02:41.352] - Receiving ACK
[17:02:41.352][T000015] 43 01 00 00 06 00 00 00 10 27 00 00 EF B4 7E C........'.....
[17:02:41.368][R000016] 43 00 00 00 06 00 00 00 02 00 82 00 04 00 C7 FA C...............
[17:02:41.368][T000015] 43 01 00 00 04 00 00 00 88 13 00 00 58 51 7E C...........XQ.
[17:02:41.383][R000014] 43 00 00 00 04 00 00 00 50 97 31 00 9E D9 C.......P.1...
[17:02:41.383][T000015] 43 01 00 00 04 00 00 00 10 27 00 00 80 BF 7E C........'.....
[17:02:41.399][R000014] 43 00 00 00 04 00 00 00 9E 01 03 00 B7 96 C.............
[17:02:41.399] - Received BaudRate : 3250000
[17:02:41.399] - Changing BaudRate
[17:02:41.399][T000011] 45 00 00 00 50 97 31 00 F3 0E 7E E...P.1....
[17:02:41.414][R000010] 45 00 00 00 50 97 31 00 F3 0E E...P.1...
[17:02:41.414] - Changed BaudRate : 3250000
[17:02:41.414][ReqFlashId]
[17:02:41.414] - Platform : 14
[17:02:41.414] - ProjectName : XMM6260
[17:02:41.414] - Sending HardWare Info
[17:02:41.414][T000197] 44 00 00 00 B6 00 00 00 20 4E 00 00 2D 90 7E 02 00 01 08 AC 00 0E 00 00 00 00 00 00 02 00 C2 01 D........N..-...................
[17:02:41.430][R000010] 44 00 00 00 B6 00 00 00 5A DA D.......Z.
[17:02:41.430] - Receiving ACK
[17:02:41.430][T000015] 43 01 00 00 0C 00 00 00 88 13 00 00 E4 7C 7E C............|.
[17:02:41.446][R000022] 43 00 00 00 0C 00 00 00 02 00 41 00 40 00 22 00 23 01 01 00 B1 EB [email protected]".#.....
[17:02:41.446][ERROR] Type : 0041 <> 0801
[17:02:41.446] - IndErrorMsg
[17:02:41.446][T000015] 43 01 00 00 3E 00 00 00 88 13 00 00 03 9A 7E C...>..........
[17:02:41.461][R000072] 43 00 00 00 3E 00 00 00 46 00 10 00 22 02 01 00 07 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C...>...F..."...................
[17:02:41.461]File_id(34), Line_number(291), Error_class(1), Error_code(70)
[17:02:41.461]File_id(16), Line_number(546), Error_class(1), Error_code(7)
[17:02:41.461]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:02:41.461]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:02:41.461]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:02:41.461]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:02:41.461]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:02:41.461]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:02:41.461] - Failure!
[17:02:41.461]ERROR : _Func_02_Ebl_3_ReqFlashId - Line(266)
[17:02:41.461]__Proc_NormalDownload : 0
[17:02:41.461]Error! IntelFlash:__Proc_NormalDownload
[17:02:41.461]_DoDownload : 0
[17:02:41.461]
-----------------------------------------Trace Last 100 Message-------------------------------------------------
[17:02:41.461]
------------------------------------------Trace Last 100 Message-------------------------------------------------
[17:02:41.461] ErrorCode(207)

If I am not mistaking you had flashed CWM Recovery? Or installed cm 10.1? Or can you reboot into Recovery?
Sent from my LG-P880 using xda premium

sPEADy said:
If I am not mistaking you had flashed CWM Recovery? Or installed cm 10.1? Or can you reboot into Recovery?
Sent from my LG-P880 using xda premium
Click to expand...
Click to collapse
After i have installet CM10.1 with CWM, i go back to stock JB and with the Manual u send before, i make a downgrade to ICS: But in the Version of ICS i had the Problem, that i had no IMEI number, and no Mobile Network.. So I tried to turn back to Stock JB with Emergency Flash of official LG Mobile Support tool and since there is nothing more ...
I Cant Reeboot in Recovery, the Recovery Menu dont works...

Can you boot into software update mode with phone turned off by pressing volume down key and inserting the usb in PC?
Sent from my LG-P880 using xda premium app.
If you ask for help and you get a Reply or anything productive in return then please hit the Thanks Button.

yes that work, but everytime while Flashing comes error messages...
Wie ich schon geschrieben habe , ist es mit keiner Software möglich zu flashen.
Weder mit LGFLashtool , noch mit KDZUpdate noch mit LGMobile support tool...
Aktuell bleibt er beim LG tool Immer hier stehen...

I have send you a private message reply me please. I would try to help you out of this.

Joshy6 said:
Sorry. Dont Work.
And the Fastboot menu dont work too...
i come not in the Menu with "-" and Power.... Write only unable to start Kernel....
Is there a way to only flash a new bootloader?
Only way i can anything do is S/W Upgrad, but dont works with normal flashtools...
Click to expand...
Click to collapse
Only way it will be with LGFlash Tool. I saw a "Intel Flash error"...
Try to go in S/W mode without battery, after fail, take out the battery, put it back again, reboot in S/W mode and try it.
Maybe it works...
Don't forget to use the correct .dll for the .dz file.

No Sir, Dont work. Sorry.
Is a connection Problem i think
Because everytime i upload the Flash, it's stop the Upload. Strange...
Thank for any Help...

hey I'm having the same problem here. Have u had any luck in fixing this...?

fix
Likhit6 said:
hey I'm having the same problem here. Have u had any luck in fixing this...?
Click to expand...
Click to collapse
did anyone had this errors and fixed it ???

To fix this problem may flash cp image with prog-box (example-octoplus).
Type 3845#*880# - port settings - cp image download, than connect prog-box,
than use box-software...
Sorry for my english.

[DISSCUSION]Unofficial Bootloader Unlock

Hey guys, Curiosity got the better of me and I did some research into unlocking the bootloader when it says no.
I remember from the Xperia U forums that XperianPro was looking at this and got people to back up there ta partition and view it in notepad++, this is shown in a hexadecimal format which is difficult to edit.
I took a new approach and decided to use the adb command
Code:
dd if=/dev/block/mmcblk0p1 of=/mnt/sdcard/ta.img
to get a .img of the ta partition which is loaded to mmcblk0p1 (on the T anyway)
when I opened this in notepad++ I found a whole lot more of human readable stuff in the ta partition.
I did find
Code:
ROOTING_ALLOWED="0"
As I recall. from XperianPros thread they did see this, and AFAIK some tried changing it to 1 and it caused a hard brick. but from using my method I think I found something else that will lead to the solution.
I found a Signature Value section
Code:
<SignatureValue>Uf7ztzGcQiKz5ivqLEG0Emxhh/9L0C0doeq1HlJIIamuyLiU8kmHxfxytPlzCVYC68jz0WWdRVsL
jaN62bvED6ZmUDETiUQa/mlytNFv2n8Ffv7ihXMay9uebxnme77JzThpWOrSXGP1odiMhvgft3xq
k9tAZKqAzChvy8LYruPXVB8dL1hl0wN3MrPrD4Dd+1WvTeXiTPJMmbftzLYy+HOaJw5oKmamHJRb
U6ejjC4eBgORvdmMddekkSd5JMMZ4ki6CBWU8SPK7eAebxUUXs1vT19gzjEIxiVt3fRnw680D4Fv
5zNB7Wy++y1dcqYyBEPEq9jVGwamcintj/fI9A==</SignatureValue>
I believe this is the signature of the file and changing the value of rooting allowed to 1 would obviously change the signature of the file, and I don't think they recalculated a signature in the other thread. from what I can gather from my ta.img is that it uses a sha1 key verification method (I think)
Sooooo.... Any help or insight would be great
I'm going to keep looking at this for the next few days and see what I find.
I don't think this has been covered regarding looking into an unofficial unlock, If it has then I must have missed it haha, and I'm probably barking mad. I also wanted to keep this separate from the bounty thread as that's about a bounty

If I remember correctly, however I may be wrong, but that signature is an SHA hashed version of the unlock code provided by Sony. Not sure which version of SHA, also may be salted. But do check/find out more, I may be wrong.
Sent from my LT30p using xda app-developers app

Thanks for looking into this for us people not allowed to unlock our bootloaders!
I believe if u crack this the bounty would rightfully be yours? I certainly would gladly give you my donation if you crack it.
Good luck

Very intresting thread. I hope this is the right way to unlock bootloader even for those who can't.

DS-1 said:
Very intresting thread. I hope this is the right way to unlock bootloader even for those who can't.
Click to expand...
Click to collapse
No.
This has been tried before and it results in a hard brick.
Simply changing a value from 0 to 1 is way to simple.

gregbradley said:
No.
This has been tried before and it results in a hard brick.
Simply changing a value from 0 to 1 is way to simple.
Click to expand...
Click to collapse
that's why I think this Signature Value has something to do with it

matt4321 said:
that's why I think this Signature Value has something to do with it
Click to expand...
Click to collapse
Well, best of luck with that

On the one hand, bear in mind that kexec is being developed (on and off development, really). I'd suggest that you get your unlock code from Sony, and the original one for the ta you got unlocked and start finding out what the various hashes of it are, might be you end up with one that matches that section, then hash your code with the same way, then do some magic the ta area
Just a thought.
Sent from my LT30p using xda app-developers app

Maybe simlock.ta, could be helpful.
There were some cases, when rooting allowed changed to yes after update.
It probably flashes only with the right values or what?
Simlock.ta in HEX -
Code:
// [SIMLOCK S1]
02
000007DA 0146 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 02 00 05 0A 02 00 00 00 0A 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 02 00 00 00 0A 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 47 4F 50
5F 49 44 3D 22 31 38 37 22 3B 4F 50 5F 4E 41 4D
45 3D 22 4F 72 61 6E 67 65 20 50 4C 22 3B 43 44
41 5F 4E 52 3D 22 31 32 36 38 2D 33 31 36 34 22
3B 52 4F 4F 54 49 4E 47 5F 41 4C 4C 4F 57 45 44
3D 22 30 22 3B 00 00 00 09 00 07 30 30 31 30 31
2D 2A 00 00 00 00 00 0B 00 07 32 36 30 30 33 2D
2A 00 00 00 00 00 00 00 00 02 00 00 00 0A 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 02 00 00 00 0A 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00
00 0A 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 02 00 00 00 0A 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
Simlock.ta in ASCII -
Code:
// [SIMLOCK S1]
02
(symbol)2010 (+)326(symbols) something...GOP_ID="187";OP_NAME="Orange PL";CDA_NR="1268-3164";ROOTING_ALLOWED="0";00101-* 26003-*...something
Just some idea.

is it reliable?

Looks promising. But [email protected] said this is too risky. Unless someone is willing to make a sacrifice for it. But come to think of it it had sone potential for bootloaders not allowed for unlocking.
Sent from my LT29i using XDA Premium 4 mobile app

I'm down to use my prototype Xperia T LT30a as a guinea pig for this experiment, but obviously only if some advancement is made to the current theory (Signature verification relationship, etc.). If the dev is somewhat confident/comfortable, then so am I. I have my Xperia L as a backup unit if my T gets destroyed.

LaZiODROID said:
I'm down to use my prototype Xperia T LT30a as a guinea pig for this experiment, but obviously only if some advancement is made to the current theory (Signature verification relationship, etc.). If the dev is somewhat confident/comfortable, then so am I. I have my Xperia L as a backup unit if my T gets destroyed.
Click to expand...
Click to collapse
this is good, I'm still looking into the relationship between unlock keys, signature value and other things

Ok. I just tested one thing. The same way, I can relock bootloader, I can also reunlock bootloader, using the unlocking number from Sony in hex format.
Anyone tested to get the number from Sony site and flash it with preset.ta?
This is preset.ta for reunlocking - replace ** with hex symbols of your unlocking number
Code:
// [ReUnlock bootloader]
02
000008B2 0010 ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **
This is simlock.ta, which can be theoretically renamed to preset.ta and flashed, but who knows what happens.
Weird is, that each simlock.ta has different number of symbols.
HEX:
Code:
// [SIMLOCK S1]
02
000007DA 0141 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 02 00 05 0A 02 00 00 00 0A 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 02 00 00 00 0A 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 4D 4F 50
5F 49 44 3D 22 38 32 34 32 22 3B 4F 50 5F 4E 41
4D 45 3D 22 43 75 73 74 6F 6D 69 7A 65 64 20 43
45 31 22 3B 43 44 41 5F 4E 52 3D 22 31 32 36 38
2D 33 31 39 34 22 3B 52 4F 4F 54 49 4E 47 5F 41
4C 4C 4F 57 45 44 3D 22 31 22 3B 00 00 00 09 00
07 30 30 31 30 31 2D 2A 00 00 00 00 00 00 00 00
00 00 00 00 02 00 00 00 0A 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00
00 00 0A 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 02 00 00 00 0A 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 02 00 00 00 0A 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 14 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
ASCII:
Code:
something...OP_ID="8242";OP_NAME="Customized CE1";CDA_NR="1268-3194";ROOTING_ALLOWED="1";...something

I found that they use some of these algorithms: http://www.w3.org/TR/xmlsec-algorithms/ to make the ta secure.
So I'm thinking we try do it in reverse with an unlocked ta and key then we would know what to do in the correct order....? thoughts?
There are some from this signed info bit but there are a few more lurking around
Code:
<SignedInfo>
<CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
</CanonicalizationMethod>
<SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1">
</SignatureMethod>
<Reference URI="#node">
<Transforms>
<Transform Algorithm="http://www.octopus-drm.com/octopus/specs/cbs-1_0"></Transform>
</Transforms>
<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1">
</DigestMethod>
<DigestValue>axQveCiPf9Q7wn958RRi5ohD130=</DigestValue>
</Reference>
</SignedInfo>
@peetr_
Yeah my simunlock.ta looks different, I'm confused between the connection (if any) of these.
I also have a different OP_ID="8242" to you, mine is 24, not sure of the significance of that.....
EDIT: It also seems they are using the W3 digital signature initiative: http://www.w3.org/PICS/DSig/RSA-SHA1_1_0.html

I guess that the signature is unbreakable. These signature things in TA has probably something to do with drm keys, and other similar things. System takes it from here.
I think the only way to get somewhere, is finding some workaround or hole, using sony way of changing things in TA partition. But maybe, some of these parts could be never changed. Who knows?

Well. Changing rooting status with preset.ta is nothing special. It is possible. You only need good nerves. And dump of whole 7DA adress from your TA.
I just changed 1 to 0.
Side effect is no mobile service. I guess you have to choose - unlocked bootloader without mobile service or locked bootloader with mobile service.
Changing 0 to 1 makes service available again.
As you can see, I tested it on already unlocked bootloader (locking it permanently). So I don't know if it works backwards. But I do not see any reason, why not.
You only need another tester. I did all I could.
And it would be good, if someone with unlockable bootloader dumps his 7DA before first unlock and compares it with 7DA after unlocking. Or compare with restored not unlocked TA.
And yes, with rooting allowed 0, fastboot and custom kernels are no longer working for me, even if I flash my unlocking number with preset.ta.

peetr_ said:
Well. Changing rooting status with preset.ta is nothing special. It is possible. You only need good nerves. And dump of whole 7DA adress from your TA.
I just changed 1 to 0.
Side effect is no mobile service. I guess you have to choose - unlocked bootloader without mobile service or locked bootloader with mobile service.
Changing 0 to 1 makes service available again.
As you can see, I tested it on already unlocked bootloader (locking it permanently). So I don't know if it works backwards. But I do not see any reason, why not.
You only need another tester. I did all I could.
And it would be good, if someone with unlockable bootloader dumps his 7DA before first unlock and compares it with 7DA after unlocking. Or compare with restored not unlocked TA.
And yes, with rooting allowed 0, fastboot and custom kernels are no longer working for me, even if I flash my unlocking number with preset.ta.
Click to expand...
Click to collapse
If changing it looses mobile service, would changing it to unlock and then restoring after bring back mobile service. Thoughts?
Sent from my LT30p using Tapatalk

Yes, but you will be locked again.
Btw. if nothing, you can at least root and test things this way. I think this procedure is not for everyone, but once you make your unlock and lock ftf, you can change your device's state very easily.
Comparison between 7DA before and after first unlock would be better, just to be sure.
But if you have your TA backed up, to change it back to previous state, I think there's nothing to break.
And one more thing. It looks to me that flashmode cannot be broken. Am I right? So you can always flash something.

peetr_ said:
And one more thing. It looks to me that flashmode cannot be broken. Am I right? So you can always flash something.
Click to expand...
Click to collapse
I seem to recall in the Xperia U forum that some bricks were made from tampering with the TA, if a bad/corrupt TA is flashed then you can't get into flashmode. That's what was established from the U forums

[Q] How to unbrick? (Stuck at S/W update mode)

A little while ago, I had problems with my phone not reading the SIM. When I tried to flash the stock firmware, the application crashed, resulting in a (hopefully) softbricked phone. I tried these methods trying to get it back to life:
http://forum.xda-developers.com/showthread.php?t=1843830 (post 4)
http://forum.xda-developers.com/showthread.php?t=2069723
And I also tried the LG R&D test tool to fash the kdz (I can't find the corresponding thread right now).
I've tried all of these methods on Win7 x64, Vista x64 and XP 32bit. The all did the same thing: they got stuck at wParam=2010 Iparam=210, so I think the phone is the problem and not the computers.
I was running CM11 with an unlocked bootloader. I can turn the phone on (and not off) but I can't get it out of the update mode. I can still update the phone until wParam=2010 Iparam=210, when it gets stuck. (I also tried waiting about an hour, nothing happened). As far as I know the phone is not a developer edition.
My question is, what do I try next?

Beunhof said:
I was running CM11 with an unlocked bootloader. I can turn the phone on (and not off) but I can't get it out of the update mode. I can still update the phone until wParam=2010 Iparam=210, when it gets stuck. (I also tried waiting about an hour, nothing happened). As far as I know the phone is not a developer edition.
Click to expand...
Click to collapse
Hello, and good day,
I have the same problem as you,
I also tried several guides ranging from installing KDZ files, through adb consoles and with a program (unfortunately I've forgotten the name) that caused the LG software to detect the KDZ files as an update for the phone, like it was from their servers, so it was 'intalled in an original way'.
But whatever, none of them worked.
Also, very important, mine gets also stuck on wParam=2010 Iparam=210,
I took the phone to a service store, where they repair cellphones through "boxes", but without success, they just mentioned that it would get stuck everytime at 15-25% of the installation process.
My Optimus 4X HD status is: can only access the S/W Update screen, or, if I turn the phone On it just shows and gets stuck on the LG logo.
It has no OS or recovery...
:crying:
Edit: I forgot to mention, I tried on Win 7 x64, x32 and on Win XP sp3 x32. So obviously the problem is on the phone.

Sounds like we have the same problem, except my phone doesn't show the boot logo at all, it instantly jumps to S/W mode when I turn it on.
After some searching, I found 3 methods I haven't tried yet:
http://forum.xda-developers.com/showthread.php?t=2475045
http://forum.xda-developers.com/showthread.php?t=2085344
http://forum.xda-developers.com/showthread.php?t=2797190
When I get back from work I'll give these a try, I will report back with results.
Does anyone have more suggestions or ideas? Should I contact LG for a fix?

Beunhof said:
After some searching, I found 3 methods I haven't tried yet:
http://forum.xda-developers.com/showthread.php?t=2475045
http://forum.xda-developers.com/showthread.php?t=2085344
[*]http://forum.xda-developers.com/showthread.php?t=2797190
Does anyone have more suggestions or ideas? Should I contact LG for a fix?
Click to expand...
Click to collapse
Hello again, I checked the three methods listed above,
i didn't like the first two really, but the third one got me so I'm doing it.
This is what I did and the result (on Win XP sp3 x32)
- Downloaded a fresh P880 V20A_00.kdz
- Downloaded and Installed fresh LGUnitedMobileDriver_S50MAN311AP22_ML_WHQL_Ver_3.11.3.exe
- During the drivers Installation, XP asked me to download and install this WMFDist11-WindowsXP-X86-ENU.exe (as suposedly I needed an mtp 11 runtime whatever). All good.
- Downloaded the LG Flash Tool 2014 from the guide, and moved the .kdz into that folder.
- Opened the program following the instructions on the post and started flashing my Optimus 4X with that Tool using CSE Flash.
- The second window named LG Mobile Support Tool that poped up started the process and had 4 modules
On the third module, the program started the Installation of the firmware on my device, on the S/W Update screen, after a while it reached 10%
Well.... it's been on 10% of the Installation progress for 43 minutes now (even while writing this response...).
The phone is perfectly recognized by the PC, I just dont get why it won't progress!....
Thanks tho, that LG Tool 2014 seemed really helpful. But still bricked.

Status:
After several investigation, I've also tried the following:
- Using P880_HK_V20B_00.kdz version, didn't work.
- Flashing thru kdz-update UpTestEX_mod2_marwin.exe, didn't work.
- Once LGMobile Support Tool is open, on the Tab "Additional Characteristics" I clicked on Recovery from Update Error.
The Tool asked for the Model & Serial Number of my device, which I entered and after the program tried to connect to the phone, said that it couldn't connect to the device.
I'm now totally sure that the problem is somewhere between the communication of the Computer and the P880, because:
Either KDZ-Update or LG Mobile Support Tool always gets stuck at what seems the 10% of the process.
Any method of flashing the device gets stuck and asks to remove battery and disconnect the usb, then replace and reconnect (an attempt to re-enable connection IMO)
Changing USB port on the PC always 'reinstall' the drivers, but with no avail.
Another thing I forgot to mention before, even tho every guide on XDA says that on the flashing process we should first "Install the drivers of the LG P880 from the list on the LG Mobile Support Tool", my tool (any version downloaded) never displayed LG P880 on the list, I've always had to use the UnitedDrivers package instead.
Any thoughts?

alessocf said:
Well.... it's been on 10% of the Installation progress for 43 minutes now (even while writing this response...).
Click to expand...
Click to collapse
I got to 10% in 52 seconds and then I got a disconnect error. I gave it a try with windows enabled just to make sure but the same thing happened. Seems like a nice and fast tool, too bad it couldn't do the trick.
This attempt also failed, but I might have some usefull information now:
Code:
[22:56:11.593]Selected 7 Binary : c:\users\beunhof\desktop\fix\lgp880at-00-v20b-eur-xxx-jul-17-2013+0.dz
[22:56:11.594]DoDownload : Retry(1)
[22:56:11.595]###### Port Opend(41) ######
[22:56:11.595]Opened COM41
[22:56:11.595]=====================================================
[22:56:11.596]= DLL Info : Dec 12 2012 11:01:58
[22:56:11.596]=====================================================
[22:56:11.602] MODEL:P880
[22:56:11.605] IMEI:000000000031
[22:56:11.611] PID:0000000003001721
[22:56:11.614] SWV:LGP880AT-00-V20b-EUR-XXX-JUL-17-2013+0
[22:56:11.617][VerReq]
[22:56:11.618]Model Name : Target(P880)
[22:56:11.618][FeatureQuery]
[22:56:11.633]This firmware supports the following features:
[22:56:11.633] - Protocol Version : 3
[22:56:11.633] - CP Download : TRUE
[22:56:11.633] - AP Download : TRUE
[22:56:11.633] - ROM Download : TRUE
[22:56:11.633] - MaxPacketLength : 0x40000
[22:56:11.633] - Battery Level : 37%
[22:56:11.633] - OperatingMode : 4
[22:56:11.633] - AutoUpdateBuffer : 1
[22:56:11.633] - ThreadOn : 1
[22:56:11.633] - Flashless : 0
[22:56:11.633] - UpdateBct : 0
[22:56:11.636] Dz Information
[22:56:11.636] - Model Name : Binary(P880)
[22:56:11.636] - SWV : LGP880AT-00-V20b-262-000-JUL-17-2013+0
[22:56:11.636] - BuildTime : 2013-07-18 01:35:51
[22:56:11.636] - SecureType : 1
[22:56:11.636] - TotalFiles : 10
[22:56:11.636] Loading FLS
[22:56:11.729]IntelFlash::GetDownloadSize
[22:56:11.729] - PSI : 35316
[22:56:11.729] - EBL : 157172
[22:56:11.729] - Hardware : 172
[22:56:11.729] - Security : 2048
[22:56:11.729] - DownloadData : 20572
[22:56:11.729] - Security : 2048
[22:56:11.729] - DownloadData : 167768
[22:56:11.729] - Security : 2048
[22:56:11.729] - DownloadData : 697892
[22:56:11.729] - Security : 2048
[22:56:11.729] - DownloadData : 356380
[22:56:11.729] - Security : 2048
[22:56:11.729] - DownloadData : 7864428
[22:56:11.729] Loading CFG
[22:56:11.733]NvidiaFlash::GetDownloadSize
[22:56:11.733] - BCT : 6128
[22:56:11.733] - EBT : 1132440
[22:56:11.733] - EKS : 684
[22:56:11.733] - SOS : 8228864
[22:56:11.733] - LNX : 7120896
[22:56:11.733] - APP : 925208920
[22:56:11.733]TotalSize : 83624509
[22:56:11.733]CP Download Starting : 0
[22:56:11.733]CP Binary has been loaded(9349476)
[22:56:11.733][Intel] MemoryMap
[22:56:11.733] FlashStartAddr : 0x40000000
[22:56:11.733] CUST : StartAddress(0x63000000), Length(0x00500000) : LINUX
[22:56:11.734] CUST : StartAddress(0x38000000), Length(0x08400000) : CLONE
[22:56:11.734] CUST : StartAddress(0x30000000), Length(0x08400100) : PREFLASH
[22:56:11.734] CUST : StartAddress(0x20000000), Length(0x00500000) : USBRO_ISO
[22:56:11.734] CUST : StartAddress(0x90000000), Length(0x001FE000) : CUSTDATA
[22:56:11.734][CMD_Intel_DownloadMode]
[22:56:12.294] - Device synchronized
[22:56:12.294][Injecting PSI RAM] : 35316
[22:56:12.294] - Sending PSI RAM
[22:56:15.354] - Receiving CRC
[22:56:15.367] - Received CRC OK : 01
[22:56:15.367] - Receiving ACK
[22:56:15.379] - Received ACK : 01 00 AA
[22:56:15.379] - PSI RAM Running
[22:56:15.379][Injecting EBL] : 157172
[22:56:15.379] - Sending EBL Length
[22:56:15.389] - Receiving ACK
[22:56:15.401] - Received ACK : 0xCCCC
[22:56:15.401] - Sending EBL : 157172
[22:56:29.112] - Sending CRC : FA
[22:56:29.121] - Receiving ACK
[22:56:29.169] - Received OK : 51 A5
[22:56:29.169] - Receiving Capabilities : 76
[22:56:29.184] - Boot-loader is active
[22:56:29.184] - EBL version: XMM6260_20.21_M1S1
[22:56:29.184] - Boot mode is: 00BB
[22:56:29.184] - EBL Running
[22:56:29.184][ReqSetProtConf]
[22:56:29.184] == prot_capabilities_t ==
[22:56:29.184] - protocol_version : 11
[22:56:29.184] - package_size : 2 -> 8
[22:56:29.184] - crc_type : 1
[22:56:29.184] - skip_writeblock_tx : 0
[22:56:29.184] - compression : 11 -> 10
[22:56:29.184] - compression : 10
[22:56:29.184] - flags : 1
[22:56:29.184] - erase_sector_verify : 0
[22:56:29.185] - flash_debug : 0
[22:56:29.185] - protocol_crc : 0
[22:56:29.185] - skip_erase : 1 -> 0
[22:56:29.185] - skip_wr_pack_crc : 0
[22:56:29.185] - Sending capabilities
[22:56:29.194] - Receiving ACK
[22:56:29.208] - Received : ACK 0100
[22:56:29.208][CnfBaudChange] : 3250000
[22:56:29.208] - Sending BaudRate
[22:56:29.217] - Receiving ACK
[22:56:29.254] - Received BaudRate : 3250000
[22:56:29.254] - Changing BaudRate
[22:56:29.267] - Changed BaudRate : 3250000
[22:56:29.267][ReqFlashId]
[22:56:29.267] - Platform : 14
[22:56:29.267] - ProjectName : XMM6260
[22:56:29.267] - Sending HardWare Info
[22:56:29.276] - Receiving ACK
[22:56:29.358] - Received ACK : 0000
[22:56:29.358][ReqCfiInfo_1]
[22:56:29.358] - Sending CfiInfo1
[22:56:29.368] - Receiving CfiInfo2
[22:56:29.406] - Received CfiInfo2 : 256
[22:56:29.406][ReqCfiInfo_2]
[22:56:29.406] - Sending CfiInfo2
[22:56:29.415] - Receiving ACK
[22:56:29.429] - Received ACK : FFFF
[22:56:29.429][Downloading BOOT CORE PSI(0)] : psi.fls
[22:56:29.429][ReqSecStart]
[22:56:29.429] - BootCoreVersion : 131072
[22:56:29.429] - Sending Security Start
[22:56:29.444] - Receiving ACK
[22:56:29.529][ERROR] Type : 0041 <> 0204
[22:56:29.529] - IndErrorMsg
[22:56:29.542]File_id(34), Line_number(415), Error_class(1), Error_code(79)
[22:56:29.542]File_id(16), Line_number(617), Error_class(1), Error_code(10)
[22:56:29.542]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[22:56:29.542]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[22:56:29.542]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[22:56:29.542]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[22:56:29.542]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[22:56:29.542]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[22:56:29.542] - Failure!
[22:56:29.542]ERROR : _Func_03_Ebl_0_ReqSecStart - Line(300)
[22:56:29.543]__Proc_NormalDownload : 0
[22:56:29.543]Error! IntelFlash:__Proc_NormalDownload
[22:56:29.544]_DoDownload : 0
[22:56:29.544]
-----------------------------------------Trace Last 100 Message-------------------------------------------------
[22:56:29.169][T000015] 43 01 00 00 4C 00 00 00 88 13 00 00 15 19 7E C...L..........
[22:56:29.184][R000086] 43 00 00 00 4C 00 00 00 BB 00 00 00 14 00 00 00 15 00 00 00 58 4D 4D 36 32 36 30 5F 32 30 2E 32 C...L...............XMM6260_20.2
[22:56:29.184] - Boot-loader is active
[22:56:29.184] - EBL version: XMM6260_20.21_M1S1
[22:56:29.184] - Boot mode is: 00BB
[22:56:29.184] - EBL Running
[22:56:29.184][ReqSetProtConf]
[22:56:29.184] == prot_capabilities_t ==
[22:56:29.184] - protocol_version : 11
[22:56:29.184] - package_size : 2 -> 8
[22:56:29.184] - crc_type : 1
[22:56:29.184] - skip_writeblock_tx : 0
[22:56:29.184] - compression : 11 -> 10
[22:56:29.184] - compression : 10
[22:56:29.184] - flags : 1
[22:56:29.184] - erase_sector_verify : 0
[22:56:29.185] - flash_debug : 0
[22:56:29.185] - protocol_crc : 0
[22:56:29.185] - skip_erase : 1 -> 0
[22:56:29.185] - skip_wr_pack_crc : 0
[22:56:29.185] - Sending capabilities
[22:56:29.185][T000101] 44 00 00 00 56 00 00 00 20 4E 00 00 CE 88 7E 02 00 86 00 4C 00 BB 00 00 00 14 00 00 00 15 00 00 D...V....N.........L............
[22:56:29.194][R000010] 44 00 00 00 56 00 00 00 D0 6E D...V....n
[22:56:29.194] - Receiving ACK
[22:56:29.196][T000015] 43 01 00 00 0C 00 00 00 88 13 00 00 E4 7C 7E C............|.
[22:56:29.208][R000022] 43 00 00 00 0C 00 00 00 02 00 86 00 02 00 01 00 89 00 03 00 B5 2C C....................,
[22:56:29.208] - Received : ACK 0100
[22:56:29.208][CnfBaudChange] : 3250000
[22:56:29.208] - Sending BaudRate
[22:56:29.208][T000029] 44 00 00 00 0E 00 00 00 20 4E 00 00 FB 9B 7E 02 00 82 00 04 00 50 97 31 00 9E 01 03 00 D........N...........P.1.....
[22:56:29.217][R000010] 44 00 00 00 0E 00 00 00 1E 5E D........^
[22:56:29.217] - Receiving ACK
[22:56:29.218][T000015] 43 01 00 00 06 00 00 00 10 27 00 00 EF B4 7E C........'.....
[22:56:29.230][R000016] 43 00 00 00 06 00 00 00 02 00 82 00 04 00 C7 FA C...............
[22:56:29.230][T000015] 43 01 00 00 04 00 00 00 88 13 00 00 58 51 7E C...........XQ.
[22:56:29.242][R000014] 43 00 00 00 04 00 00 00 50 97 31 00 9E D9 C.......P.1...
[22:56:29.242][T000015] 43 01 00 00 04 00 00 00 10 27 00 00 80 BF 7E C........'.....
[22:56:29.254][R000014] 43 00 00 00 04 00 00 00 9E 01 03 00 B7 96 C.............
[22:56:29.254] - Received BaudRate : 3250000
[22:56:29.254] - Changing BaudRate
[22:56:29.254][T000011] 45 00 00 00 50 97 31 00 F3 0E 7E E...P.1....
[22:56:29.267][R000010] 45 00 00 00 50 97 31 00 F3 0E E...P.1...
[22:56:29.267] - Changed BaudRate : 3250000
[22:56:29.267][ReqFlashId]
[22:56:29.267] - Platform : 14
[22:56:29.267] - ProjectName : XMM6260
[22:56:29.267] - Sending HardWare Info
[22:56:29.267][T000197] 44 00 00 00 B6 00 00 00 20 4E 00 00 2D 90 7E 02 00 01 08 AC 00 0E 00 00 00 00 00 00 02 00 C2 01 D........N..-...................
[22:56:29.276][R000010] 44 00 00 00 B6 00 00 00 5A DA D.......Z.
[22:56:29.276] - Receiving ACK
[22:56:29.277][T000015] 43 01 00 00 0C 00 00 00 88 13 00 00 E4 7C 7E C............|.
[22:56:29.358][R000022] 43 00 00 00 0C 00 00 00 02 00 01 08 02 00 00 00 0B 00 03 00 4F 25 C...................O%
[22:56:29.358] - Received ACK : 0000
[22:56:29.358][ReqCfiInfo_1]
[22:56:29.358] - Sending CfiInfo1
[22:56:29.359][T000027] 44 00 00 00 0C 00 00 00 20 4E 00 00 94 90 7E 02 00 84 00 02 00 00 00 86 00 03 00 D........N.................
[22:56:29.368][R000010] 44 00 00 00 0C 00 00 00 68 67 D.......hg
[22:56:29.368] - Receiving CfiInfo2
[22:56:29.369][T000015] 43 01 00 00 06 00 00 00 10 27 00 00 EF B4 7E C........'.....
[22:56:29.381][R000016] 43 00 00 00 06 00 00 00 02 00 84 00 00 01 B4 C7 C...............
[22:56:29.381][T000015] 43 01 00 00 00 01 00 00 88 13 00 00 53 D8 7E C...........S..
[22:56:29.394][R000266] 43 00 00 00 00 01 00 00 00 00 00 00 AD 00 B1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C...............................
[22:56:29.394][T000015] 43 01 00 00 04 00 00 00 10 27 00 00 80 BF 7E C........'.....
[22:56:29.406][R000014] 43 00 00 00 04 00 00 00 E3 01 03 00 7D 47 C...........}G
[22:56:29.406] - Received CfiInfo2 : 256
[22:56:29.406][ReqCfiInfo_2]
[22:56:29.406] - Sending CfiInfo2
[22:56:29.406][T000281] 44 00 00 00 0A 01 00 00 20 4E 00 00 F0 12 7E 02 00 85 00 00 01 00 00 00 00 AD 00 B1 00 00 00 00 D........N......................
[22:56:29.415][R000010] 44 00 00 00 0A 01 00 00 2E 76 D........v
[22:56:29.415] - Receiving ACK
[22:56:29.417][T000015] 43 01 00 00 0C 00 00 00 88 13 00 00 E4 7C 7E C............|.
[22:56:29.429][R000022] 43 00 00 00 0C 00 00 00 02 00 85 00 02 00 FF FF 85 02 03 00 0B 76 C....................v
[22:56:29.429] - Received ACK : FFFF
[22:56:29.429][Downloading BOOT CORE PSI(0)] : psi.fls
[22:56:29.429][ReqSecStart]
[22:56:29.429] - BootCoreVersion : 131072
[22:56:29.429] - Sending Security Start
[22:56:29.429][T002073] 44 00 00 00 0A 08 00 00 20 4E 00 00 C9 53 7E 02 00 04 02 00 08 00 00 00 00 00 00 00 00 00 00 00 D........N...S..................
[22:56:29.444][R000010] 44 00 00 00 0A 08 00 00 30 EA D.......0.
[22:56:29.444] - Receiving ACK
[22:56:29.445][T000015] 43 01 00 00 0C 00 00 00 88 13 00 00 E4 7C 7E C............|.
[22:56:29.529][R000022] 43 00 00 00 0C 00 00 00 02 00 41 00 40 00 22 00 9F 01 01 00 19 1D [email protected]".......
[22:56:29.529][ERROR] Type : 0041 <> 0204
[22:56:29.529] - IndErrorMsg
[22:56:29.529][T000015] 43 01 00 00 3E 00 00 00 88 13 00 00 03 9A 7E C...>..........
[22:56:29.542][R000072] 43 00 00 00 3E 00 00 00 4F 00 10 00 69 02 01 00 0A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C...>...O...i...................
[22:56:29.542]File_id(34), Line_number(415), Error_class(1), Error_code(79)
[22:56:29.542]File_id(16), Line_number(617), Error_class(1), Error_code(10)
[22:56:29.542]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[22:56:29.542]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[22:56:29.542]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[22:56:29.542]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[22:56:29.542]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[22:56:29.542]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[22:56:29.542] - Failure!
[22:56:29.542]ERROR : _Func_03_Ebl_0_ReqSecStart - Line(300)
[22:56:29.543]__Proc_NormalDownload : 0
[22:56:29.543]Error! IntelFlash:__Proc_NormalDownload
[22:56:29.544]_DoDownload : 0
[22:56:29.544]
-----------------------------------------Trace Last 100 Message-------------------------------------------------
[22:56:29.547]
------------------------------------------Trace Last 100 Message-------------------------------------------------
[22:56:29.547] ErrorCode(210)
Anyone an idea on what the strange hex-ish lines are? they show up just after the first error. Maybe something is encrypted? I'll google error code 10, 79 and 210 in a minute.
I lost hope and I can't bother to try the last link I posted, maybe tomorrow
Any thoughts on the log?
EDIT:
Searching the errors in the log led me here:
http://forum.xda-developers.com/showthread.php?t=2287267
http://forum.xda-developers.com/showthread.php?t=2786001
http://forum.xda-developers.com/showthread.php?t=2737915
The last one is identical to my problem, my phone also couldn't read my SIM. Sadly no one ever solved the problem here.
I think these solutions are the last resort:
http://forum.xda-developers.com/showthread.php?t=1448803
http://forum.xda-developers.com/showthread.php?t=1861942
I will give these a try later today when I get home.

Hello again,
I've checked the threads you mentioned above, as well as I've been googling to another forums. Yet no success.
Every thread where P880 gets stuck at param:207, Failure:207 or the infamous 10%; have no final solutions.
I've tried LGFlash Tool, LGFlash Tool 2014, LGSupport Tool, SmartFlash, KDZ-Update, each one w/o success and stopping at the same point.
The last and only solution I haven't yet manage to do, is using the program LGNPST v_2.2.3
I have it installed, it does recognize my P880 only on the "Emergency" tab, and automatically recognize it on COM19.
To make the flash procedure it requires a DLL and a BIN or CAB firmware, which I do not possess (I've only found .kdz and .dz firmwares)
Also, as far as I've read, the .kdz files when decrypted become .dz which when decrypted become .fls & .bin files.
That is my last hope... nobody seem to have an answer. Wish we had an ODIN for LG.

alessocf said:
To make the flash procedure it requires a DLL and a BIN or CAB firmware, which I do not possess (I've only found .kdz and .dz firmwares)
Also, as far as I've read, the .kdz files when decrypted become .dz which when decrypted become .fls & .bin files.
Click to expand...
Click to collapse
I used this method to create a .cab or .dz from a .kdz for this attempt.
Do you have a guide for the LGNPST? I can only find this thread.
A zeroed MEID could also be (part of) the problem:
If you encounter problems during flashing, upgrading or downgrading you may fall victim to your MEID/ESN being zeroed out.
The usual cause is pulling your battery while stuck on the white LG Software Update screen.
Click to expand...
Click to collapse
Thats exacly how I got bricked.

Beunhof said:
I used this method to create a .cab or .dz from a .kdz for this attempt.
Click to expand...
Click to collapse
Gonna try with that method for a.cab to use in the LGNPST, thanks.
Also, I'll try using the P880.dll that is inside the KDZ-Update folder.
Beunhof said:
Do you have a guide for the LGNPST? I can only find this thread.
Click to expand...
Click to collapse
Sorry, I can't remember where I got it, but I uploaded it to my dropbox for you, here is the link:
https://dl.dropboxusercontent.com/u/52565427/LGNPST v2.2.3.rar
It contains a Readme.txt with the instructions, its quite easy, the program looks like a suite.
Gonna report later the status. Good luck to both of us, lol.
EDIT: STATUS:
- Made a .cab file and used the P880.dll contained on the kdz-update folder for the LGNPST, the program instantly said "Finish!" and obviously, did nothing.
I'm probably doing something wrong there... but I've ran out of ideas.

Exact Same Problem!
Hi.
Looking all over the internet, the XDA forum in particular, to find a solution to my issue with my 4xHD.
It seems that I have the exact same problem as you describe; SIM not being recognised (out of the blue), eventually decided to re-flash to fix the issue (last resort after trying everything else I could find). Followed all instructions word for word; drivers installed, etc... etc... but when flashing stopped on 210... (not fully explaining, but essentially the same place it stopped for you). Waited hours, nothing happened, so forced to unplug phone. Therefore stuck on S/W mode after a failed/partial flash.
I have also attempted to complete this via every method I can find on here, but stops at the 210/10% point (depending on software being used), every time!
I love this phone and need it back up and running. If you have any luck sorting yours please update and let me know how the issue was resolved. Similarly, let me know if you have had no further luck and if I make any progress I will update you.
Cheers!

aaron_gavin said:
Hi.
Looking all over the internet, the XDA forum in particular, to find a solution to my issue with my 4xHD.
It seems that I have the exact same problem as you describe; SIM not being recognised (out of the blue), eventually decided to re-flash to fix the issue (last resort after trying everything else I could find). Followed all instructions word for word; drivers installed, etc... etc... but when flashing stopped on 210... (not fully explaining, but essentially the same place it stopped for you). Waited hours, nothing happened, so forced to unplug phone. Therefore stuck on S/W mode after a failed/partial flash.
I have also attempted to complete this via every method I can find on here, but stops at the 210/10% point (depending on software being used), every time!
I love this phone and need it back up and running. If you have any luck sorting yours please update and let me know how the issue was resolved. Similarly, let me know if you have had no further luck and if I make any progress I will update you.
Cheers!
Click to expand...
Click to collapse
Someone managed to solve. Already tried and everything.

Sup
Hello,
there is no software solution (at least known to me) for fixing this issue.
I've searched and scavenged all over the internet for a solution or at least AN EXPLANATION on why it does get stuck no matter what at 10% or Param:207.
My last resort (I'm trying it this weekend, will post later if it worked) is
a method called JTAG, where they kinda force-fix the boot software of the device connecting directly to the cellphone MoBo (for more explanation look on youtube)
Well, thats it... if it works, cheers, otherwise I'm throwing my Optimus 4X on a drawer.
Till' later.

alessocf said:
Hello,
there is no software solution (at least known to me) for fixing this issue.
I've searched and scavenged all over the internet for a solution or at least AN EXPLANATION on why it does get stuck no matter what at 10% or Param:207.
My last resort (I'm trying it this weekend, will post later if it worked) is
a method called JTAG, where they kinda force-fix the boot software of the device connecting directly to the cellphone MoBo (for more explanation look on youtube)
Well, thats it... if it works, cheers, otherwise I'm throwing my Optimus 4X on a drawer.
Till' later.
Click to expand...
Click to collapse
I will research this 'force-fix' and see if i can make any progress when i get some time off work. please update how you get on with this iff/when you try!
im feeling the same way with the phone; getting close to giving up, having tried all the software solutions word for word as described in the forums to fix it.
its strange that on all the guides when people have had similar problems as we are facing the response is usually to remove drivers+software and try again/follow the guide properly (not that im saying that a simple human error is not at fault the majority of the time). but i have not seen any posts were people have accepted that all methods have been attempted correctly and advice given regarding possible hardware faults and/or this 'force-fix' you mention.
if i am not able to fix myself i think i will consider posting a plea for someone more competent with this kind of stuff to have my phone posted to them in order to try and fix it for me. im sure that someone who is really into this kind of thing would like to have a go out of general interest, and the worst case scenario would be that i dont get my phone back (which is no use to me in its current state anyway).
cheers!
---------- Post added at 11:43 AM ---------- Previous post was at 11:22 AM ----------
aaron_gavin said:
I will research this 'force-fix' and see if i can make any progress when i get some time off work. please update how you get on with this iff/when you try!
im feeling the same way with the phone; getting close to giving up, having tried all the software solutions word for word as described in the forums to fix it.
its strange that on all the guides when people have had similar problems as we are facing the response is usually to remove drivers+software and try again/follow the guide properly (not that im saying that a simple human error is not at fault the majority of the time). but i have not seen any posts were people have accepted that all methods have been attempted correctly and advice given regarding possible hardware faults and/or this 'force-fix' you mention.
if i am not able to fix myself i think i will consider posting a plea for someone more competent with this kind of stuff to have my phone posted to them in order to try and fix it for me. im sure that someone who is really into this kind of thing would like to have a go out of general interest, and the worst case scenario would be that i dont get my phone back (which is no use to me in its current state anyway).
cheers!
Click to expand...
Click to collapse
UPDATE:
had a look at this JTAG repair method (also found a youtube video of some company touting for work, showing repair of a 4x hd - http://www.youtube.com/watch?v=5NRXhJxbtYY).
im not sure that i would want to go down that route, as they explain that it delves further into the phones software to fix issues caused by people bricking due to messing about to much after gaining root access. but i dont feel that this is the reason for the issues with my phone; had it set-up how i liked it for ages (without any real messing about after root), the issue with nonrecognition of my SIM came completely out of the blue (i attempted to re-flash to fix this; causing the stuck in s/w mode issue i now have, but the issue could quite easily be due to failing hardware as it could be an issue with the software).
in the case that it is damaged/failing hardware at fault JTAG would not be able to repair the phone, and even if it got my firmware back up and running there is no guarantee that it would recognise my SIM when i got it back.
so im not sure that i would be happy either paying someone to perform this 'fix' on my phone or paying for the hardware to attempt to fix myself, if its possible that the phone may still not work afterwards due to broken hardware. especially when you can buy a working model of our phone from places like ebay for under £100.
any thoughts or advice?

any luck/updates?
i think that i may just call it a day trying to fix this thing.
from what i have read it may be possible to fix the bootloader, thus allow to boot into recovery/fastboot/adb (hence not remaining stuck in an unflashable s/w update mode) in order to fix the phone, by using nvflash/apx mode. but it does not seem that our phones allow us access to do this.
have you had any luck with your mentioned jtag fix or otherwise?
had to get a new phone anyway (as was fed up using my old phone while trying to fix my 4x hd) - got a moto g 4g. am pretty chuffed with it for the price (enjoying screen mirroring through a miracast dongle and kitkat, etc...), but to be honest would go back to using my 4x hd if someone was able to find a fix.
any response/update would be appreciated, and if anyone thinks they can fix this issue please let me know.
cheers!

It's been a while!
Hey!
Long time since we had this issure with our 4X HD's, in fact almost a year since I had touched mine.
Was clearing out a drawer and found the brick. Which made me think, did anyone actually succeed in fixing their phone/solve this issue?
If so, I may have a bash just for the hell of it. If not, I think it's time for the bin.
:silly:

Whats Up
aaron_gavin said:
Hey!
Long time since we had this issure with our 4X HD's, in fact almost a year since I had touched mine.
Was clearing out a drawer and found the brick. Which made me think, did anyone actually succeed in fixing their phone/solve this issue?
If so, I may have a bash just for the hell of it. If not, I think it's time for the bin.
:silly:
Click to expand...
Click to collapse
Same here, didn't tried much since my last update. JTAG didn't work "cause Tegra based devices don't support it" or something like that.
Also tried with a homemade USB Jig Method, nothing happened.
My X4 is in my desktop, I use it mostly as a luxury paper holder.
Bless !.

alessocf said:
Same here, didn't tried much since my last update. JTAG didn't work "cause Tegra based devices don't support it" or something like that.
Also tried with a homemade USB Jig Method, nothing happened.
My X4 is in my desktop, I use it mostly as a luxury paper holder.
Bless !.
Click to expand...
Click to collapse
Guys, we may have a working solution: http://forum.xda-developers.com/optimus-4x-hd/general/maybe-nvflash-method-t3159853
I am currently testing it right now and until now it seems to work.
Update: It worked! My phone is booting again. Now i need to fix the IMEI and I am good.
Code:
C:\LG\\nvflash>nvflash --blob blob.bin --bct flash.bct.encrypt --setbct --configfile flash_encrypt.cfg --create --bl bootloader.bin.encrypt --go
Nvflash v1.7.75664 started
Using blob v1.1.57813ngs\Adm
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x81
chip uid: 0x015d441469040a07
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: flash.bct.encrypt
- 6128/6128 bytes sent
flash.bct.encrypt sent successfully
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: bootloader.bin.encrypt
\ 1142880/1142880 bytes sent
bootloader.bin.encrypt sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: LGE
creating partition: EKS
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: NVA
creating partition: UDA
creating partition: DRM
creating partition: MLT
creating partition: FOT
creating partition: CAL
creating partition: UDB
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 LGE please wait.. done!
Formatting partition 6 EKS please wait.. done!
Formatting partition 7 GP1 please wait.. done!
Formatting partition 8 SOS please wait.. done!
Formatting partition 9 LNX please wait.. done!
Formatting partition 10 APP please wait.. done!
Formatting partition 11 CAC please wait.. done!
Formatting partition 12 MSC please wait.. done!
Formatting partition 13 USP please wait.. done!
Formatting partition 14 NVA please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 DRM please wait.. done!
Formatting partition 17 MLT please wait.. done!
Formatting partition 18 FOT please wait.. done!
Formatting partition 19 CAL please wait.. done!
Formatting partition 20 UDB please wait.. done!
Formatting partition 21 GPT please wait.. done!
done!
sending file: bootloader.bin.encrypt
\ 1142880/1142880 bytes sent
bootloader.bin.encrypt sent successfully
sending file: eks.dat
- 684/684 bytes sent
eks.dat sent successfully
sending file: recovery.img
/ 7577600/7577600 bytes sent
recovery.img sent successfully
sending file: boot.img
/ 6496256/6496256 bytes sent
boot.img sent successfully
sending file: system.img
- 687920496/687920496 bytes sent
system.img sent successfully

GoodSoul said:
Guys, we may have a working solution: http://forum.xda-developers.com/optimus-4x-hd/general/maybe-nvflash-method-t3159853
I am currently testing it right now and until now it seems to work.
Update: It worked! My phone is booting again. Now i need to fix the IMEI and I am good.
[/code]
Click to expand...
Click to collapse
Greetings :fingers-crossed:, love to hear some good news and that it worked out for you.
I'm currently downloading the software and reading on how to use it, i'll be updating on how does it go for me.
Thank you for sharing this info with us.:highfive:
UPDATE: I T - W O R K E D !, after doing the process it automatically restarted and the LG Boot Logo reanimated, and started just as factory reset.
I had some issues installing the NvidiaUsb.inf, because I'm running on Windows 10 AMD x64 bits.
Steps I followed (in case someone needs them):
1) I had to open Command Prompt using the command: shutdown /r /o /f /t 00
THIS WILL RESTART YOUR COMPUTER
2)Then go through the options: Troubleshoot > Advanced Options > and look to "Disable Driver Signature Enforcement" using F7 key.
This allowed my W10 to Install the NVIDIA USB Boot-recovery driver for Mobile devices, which later allowed me to run NvFlash succesfully.
Current Status: LG P880 Boots and Runs!, doesn't have Baseband Version or IMEI, but this is something easier to fix.
Mostly appreciated.

UPDATE: I T - W O R K E D !, after doing the process it automatically restarted and the LG Boot Logo reanimated, and started just as factory reset.
Click to expand...
Click to collapse
Yippie!
Current Status: LG P880 Boots and Runs!, doesn't have Baseband Version or IMEI, but this is something easier to fix.
Click to expand...
Click to collapse
If you know how please let me know. I tried for serveral hours to fix that problem but had no luck yet.
Mostly appreciated.
Click to expand...
Click to collapse
You are welcome.

Need Help LG P880 Stuck in software upgrade screen. Tried most of the things here

My phone got stuck in s/w upgrade screen the one with the blue one. Let me give you some history first.
My phone was working fine. Then i tried to update the software via LG Tool. Then the problem came with no sim card error. After researching a lot i found that there was IMEI number error. Then looked into many threads tried flashin with LG flash tool. I did everything as mentioned in the thread. But LG flash tool did not flash my phone. Only sign came READY in the flash tool, it did nothing.
No i am in need of help. Can anyone help me.
PS: Sent to service center they said that they did some hardware change and they solved the issue but after 2 days they said that again the problem persists.
Waiting for your help guyz....

Which operating system are you running your flash tool from?
Had a similar issue trying to flash my phone on Windows 8.1 64x, while using the exact same method and software on Windows 7 64x worked perfectly.

fugitive666 said:
My phone got stuck in s/w upgrade screen the one with the blue one. Let me give you some history first.
My phone was working fine. Then i tried to update the software via LG Tool. Then the problem came with no sim card error. After researching a lot i found that there was IMEI number error. Then looked into many threads tried flashin with LG flash tool. I did everything as mentioned in the thread. But LG flash tool did not flash my phone. Only sign came READY in the flash tool, it did nothing.
No i am in need of help. Can anyone help me.
PS: Sent to service center they said that they did some hardware change and they solved the issue but after 2 days they said that again the problem persists.
Waiting for your help guyz....
Click to expand...
Click to collapse
Once you get S/w on phone and ready on port-xx and after removing cable your phone will be stuck on s/w dont worry its normal, just pull the battery out and re-insert it again. REMEMBER : Do not close FLASH-TOOL
Now you need to follow this steps for flashing
*After inserting battery again connect usb cable to PC holding Volume down button and after that you will able to see port xx will be in blue colour (mean while your phone will be in s/w mode) Please do not remove cable untill the process is completed.
Still having problem please let us know, I recommend use WIN-7.

Try flash data from APX mode using
this
http://forum.xda-developers.com/optimus-4x-hd/general/maybe-nvflash-method-t3159853
or this
https://mega.nz/#!Udk3VT7R!64nsZEOxSfE2ppSiqz15O-N5Vlf6cHDG7Oh3a6A15GU
second link based on data from first link but contains newer firmware images

[17:43:43.162]Selected 7 Binary : e:\p880\lgp880at-00-v20a-262-000-mar-26-2013 0\lgp880at-00-v20a-262-000-mar-26-2013+0.dz
[17:43:43.163]DoDownload : Retry(1)
[17:43:43.163]###### Port Opend(41) ######
[17:43:43.163]Opened COM41
[17:43:43.163]=====================================================
[17:43:43.163]= DLL Info : Dec 12 2012 11:01:58
[17:43:43.163]=====================================================
[17:43:43.178] MODEL880
[17:43:43.194] IMEI: xxxxx I hide this
[17:43:43.209] PID:
[17:43:43.225] SWV:LGP880AT-00-V20c-EUR-XXX-OCT-07-2014+0
[17:43:43.225][VerReq]
[17:43:43.225]Model Name : Target(P880)
[17:43:43.225][FeatureQuery]
[17:43:43.256]This firmware supports the following features:
[17:43:43.256] - Protocol Version : 3
[17:43:43.256] - CP Download : TRUE
[17:43:43.256] - AP Download : TRUE
[17:43:43.256] - ROM Download : TRUE
[17:43:43.256] - MaxPacketLength : 0x40000
[17:43:43.256] - Battery Level : 21%
[17:43:43.256] - OperatingMode : 4
[17:43:43.256] - AutoUpdateBuffer : 1
[17:43:43.256] - ThreadOn : 1
[17:43:43.256] - Flashless : 0
[17:43:43.256] - UpdateBct : 0
[17:43:43.738] Dz Information
[17:43:43.738] - Model Name : Binary(P880)
[17:43:43.738] - SWV : LGP880AT-00-V20a-262-000-MAR-26-2013+0+0
[17:43:43.738] - BuildTime : 2013-03-26 23:28:12
[17:43:43.738] - SecureType : 1
[17:43:43.738] - TotalFiles : 10
[17:43:43.738] Loading FLS
[17:43:43.871]IntelFlash::GetDownloadSize
[17:43:43.871] - PSI : 35316
[17:43:43.871] - EBL : 157172
[17:43:43.871] - Hardware : 172
[17:43:43.871] - Security : 2048
[17:43:43.871] - DownloadData : 20572
[17:43:43.871] - Security : 2048
[17:43:43.871] - DownloadData : 167768
[17:43:43.871] - Security : 2048
[17:43:43.871] - DownloadData : 697892
[17:43:43.871] - Security : 2048
[17:43:43.871] - DownloadData : 356380
[17:43:43.872] - Security : 2048
[17:43:43.872] - DownloadData : 7864428
[17:43:43.872] Loading CFG
[17:43:43.880]NvidiaFlash::GetDownloadSize
[17:43:43.880] - BCT : 6128
[17:43:43.880] - EBT : 1132440
[17:43:43.880] - EKS : 684
[17:43:43.880] - SOS : 8228864
[17:43:43.880] - LNX : 7120896
[17:43:43.880] - APP : 914424152
[17:43:43.880]TotalSize : 82950461
[17:43:43.880]CP Download Starting : 0
[17:43:43.880]CP Binary has been loaded(9349476)
[17:43:43.880][Intel] MemoryMap
[17:43:43.880] FlashStartAddr : 0x40000000
[17:43:43.881] CUST : StartAddress(0x63000000), Length(0x00500000) : LINUX
[17:43:43.881] CUST : StartAddress(0x38000000), Length(0x08400000) : CLONE
[17:43:43.881] CUST : StartAddress(0x30000000), Length(0x08400100) : PREFLASH
[17:43:43.881] CUST : StartAddress(0x20000000), Length(0x00500000) : USBRO_ISO
[17:43:43.881] CUST : StartAddress(0x90000000), Length(0x001FE000) : CUSTDATA
[17:43:43.881][CMD_Intel_DownloadMode]
[17:43:44.440] - Device synchronized
[17:43:44.441][Injecting PSI RAM] : 35316
[17:43:44.441] - Sending PSI RAM
[17:43:47.510] - Receiving CRC
[17:43:47.526] - Received CRC OK : 01
[17:43:47.526] - Receiving ACK
[17:43:47.541] - Received ACK : 01 00 AA
[17:43:47.541] - PSI RAM Running
[17:43:47.541][Injecting EBL] : 157172
[17:43:47.541] - Sending EBL Length
[17:43:47.557] - Receiving ACK
[17:43:47.573] - Received ACK : 0xCCCC
[17:43:47.573] - Sending EBL : 157172
[17:44:01.368] - Sending CRC : FA
[17:44:01.384] - Receiving ACK
[17:44:01.431] - Received OK : 51 A5
[17:44:01.431] - Receiving Capabilities : 76
[17:44:01.446] - Boot-loader is active
[17:44:01.446] - EBL version: XMM6260_20.21_M1S1
[17:44:01.446] - Boot mode is: 00BB
[17:44:01.446] - EBL Running
[17:44:01.446][ReqSetProtConf]
[17:44:01.446] == prot_capabilities_t ==
[17:44:01.446] - protocol_version : 11
[17:44:01.446] - package_size : 2 -> 8
[17:44:01.446] - crc_type : 1
[17:44:01.446] - skip_writeblock_tx : 0
[17:44:01.446] - compression : 11 -> 10
[17:44:01.446] - compression : 10
[17:44:01.446] - flags : 1
[17:44:01.446] - erase_sector_verify : 0
[17:44:01.446] - flash_debug : 0
[17:44:01.446] - protocol_crc : 0
[17:44:01.446] - skip_erase : 1 -> 0
[17:44:01.446] - skip_wr_pack_crc : 0
[17:44:01.446] - Sending capabilities
[17:44:01.462] - Receiving ACK
[17:44:01.478] - Received : ACK 0100
[17:44:01.478][CnfBaudChange] : 3250000
[17:44:01.478] - Sending BaudRate
[17:44:01.493] - Receiving ACK
[17:44:01.540] - Received BaudRate : 3250000
[17:44:01.540] - Changing BaudRate
[17:44:01.556] - Changed BaudRate : 3250000
[17:44:01.556][ReqFlashId]
[17:44:01.556] - Platform : 14
[17:44:01.556] - ProjectName : XMM6260
[17:44:01.556] - Sending HardWare Info
[17:44:01.571] - Receiving ACK
[17:44:01.650] - Received ACK : 0000
[17:44:01.650][ReqCfiInfo_1]
[17:44:01.650] - Sending CfiInfo1
[17:44:01.665] - Receiving CfiInfo2
[17:44:01.712] - Received CfiInfo2 : 256
[17:44:01.712][ReqCfiInfo_2]
[17:44:01.712] - Sending CfiInfo2
[17:44:01.728] - Receiving ACK
[17:44:01.743] - Received ACK : FFFF
[17:44:01.743][Downloading BOOT CORE PSI(0)] : psi.fls
[17:44:01.743][ReqSecStart]
[17:44:01.743] - BootCoreVersion : 131072
[17:44:01.743] - Sending Security Start
[17:44:01.759] - Receiving ACK
[17:44:01.853][ERROR] Type : 0041 <> 0204
[17:44:01.853] - IndErrorMsg
[17:44:01.868]File_id(34), Line_number(415), Error_class(1), Error_code(79)
[17:44:01.868]File_id(16), Line_number(617), Error_class(1), Error_code(10)
[17:44:01.868]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:44:01.868]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:44:01.868]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:44:01.868]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:44:01.868]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:44:01.868]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:44:01.868] - Failure!
[17:44:01.868]ERROR : _Func_03_Ebl_0_ReqSecStart - Line(300)
[17:44:01.868]__Proc_NormalDownload : 0
[17:44:01.868]Error! IntelFlash:__Proc_NormalDownload
[17:44:01.868]_DoDownload : 0
[17:44:01.868]
-----------------------------------------Trace Last 100 Message-------------------------------------------------
[17:44:01.431][T000015] 43 01 00 00 4C 00 00 00 88 13 00 00 15 19 7E C...L..........
[17:44:01.446][R000086] 43 00 00 00 4C 00 00 00 BB 00 00 00 14 00 00 00 15 00 00 00 58 4D 4D 36 32 36 30 5F 32 30 2E 32 C...L...............XMM6260_20.2
[17:44:01.446] - Boot-loader is active
[17:44:01.446] - EBL version: XMM6260_20.21_M1S1
[17:44:01.446] - Boot mode is: 00BB
[17:44:01.446] - EBL Running
[17:44:01.446][ReqSetProtConf]
[17:44:01.446] == prot_capabilities_t ==
[17:44:01.446] - protocol_version : 11
[17:44:01.446] - package_size : 2 -> 8
[17:44:01.446] - crc_type : 1
[17:44:01.446] - skip_writeblock_tx : 0
[17:44:01.446] - compression : 11 -> 10
[17:44:01.446] - compression : 10
[17:44:01.446] - flags : 1
[17:44:01.446] - erase_sector_verify : 0
[17:44:01.446] - flash_debug : 0
[17:44:01.446] - protocol_crc : 0
[17:44:01.446] - skip_erase : 1 -> 0
[17:44:01.446] - skip_wr_pack_crc : 0
[17:44:01.446] - Sending capabilities
[17:44:01.446][T000101] 44 00 00 00 56 00 00 00 20 4E 00 00 CE 88 7E 02 00 86 00 4C 00 BB 00 00 00 14 00 00 00 15 00 00 D...V....N.........L............
[17:44:01.462][R000010] 44 00 00 00 56 00 00 00 D0 6E D...V....n
[17:44:01.462] - Receiving ACK
[17:44:01.462][T000015] 43 01 00 00 0C 00 00 00 88 13 00 00 E4 7C 7E C............|.
[17:44:01.478][R000022] 43 00 00 00 0C 00 00 00 02 00 86 00 02 00 01 00 89 00 03 00 B5 2C C....................,
[17:44:01.478] - Received : ACK 0100
[17:44:01.478][CnfBaudChange] : 3250000
[17:44:01.478] - Sending BaudRate
[17:44:01.478][T000029] 44 00 00 00 0E 00 00 00 20 4E 00 00 FB 9B 7E 02 00 82 00 04 00 50 97 31 00 9E 01 03 00 D........N...........P.1.....
[17:44:01.493][R000010] 44 00 00 00 0E 00 00 00 1E 5E D........^
[17:44:01.493] - Receiving ACK
[17:44:01.493][T000015] 43 01 00 00 06 00 00 00 10 27 00 00 EF B4 7E C........'.....
[17:44:01.509][R000016] 43 00 00 00 06 00 00 00 02 00 82 00 04 00 C7 FA C...............
[17:44:01.509][T000015] 43 01 00 00 04 00 00 00 88 13 00 00 58 51 7E C...........XQ.
[17:44:01.525][R000014] 43 00 00 00 04 00 00 00 50 97 31 00 9E D9 C.......P.1...
[17:44:01.525][T000015] 43 01 00 00 04 00 00 00 10 27 00 00 80 BF 7E C........'.....
[17:44:01.540][R000014] 43 00 00 00 04 00 00 00 9E 01 03 C0 BB 50 C............P
[17:44:01.540] - Received BaudRate : 3250000
[17:44:01.540] - Changing BaudRate
[17:44:01.540][T000011] 45 00 00 00 50 97 31 00 F3 0E 7E E...P.1....
[17:44:01.556][R000010] 45 00 00 00 50 97 31 00 F3 0E E...P.1...
[17:44:01.556] - Changed BaudRate : 3250000
[17:44:01.556][ReqFlashId]
[17:44:01.556] - Platform : 14
[17:44:01.556] - ProjectName : XMM6260
[17:44:01.556] - Sending HardWare Info
[17:44:01.556][T000197] 44 00 00 00 B6 00 00 00 20 4E 00 00 2D 90 7E 02 00 01 08 AC 00 0E 00 00 00 00 00 00 02 00 C2 01 D........N..-...................
[17:44:01.571][R000010] 44 00 00 00 B6 00 00 00 5A DA D.......Z.
[17:44:01.571] - Receiving ACK
[17:44:01.571][T000015] 43 01 00 00 0C 00 00 00 88 13 00 00 E4 7C 7E C............|.
[17:44:01.650][R000022] 43 00 00 00 0C 00 00 00 02 00 01 08 02 00 00 00 0B 00 03 00 4F 25 C...................O%
[17:44:01.650] - Received ACK : 0000
[17:44:01.650][ReqCfiInfo_1]
[17:44:01.650] - Sending CfiInfo1
[17:44:01.650][T000027] 44 00 00 00 0C 00 00 00 20 4E 00 00 94 90 7E 02 00 84 00 02 00 00 00 86 00 03 00 D........N.................
[17:44:01.665][R000010] 44 00 00 00 0C 00 00 00 68 67 D.......hg
[17:44:01.665] - Receiving CfiInfo2
[17:44:01.665][T000015] 43 01 00 00 06 00 00 00 10 27 00 00 EF B4 7E C........'.....
[17:44:01.681][R000016] 43 00 00 00 06 00 00 00 02 00 84 00 00 01 B4 C7 C...............
[17:44:01.681][T000015] 43 01 00 00 00 01 00 00 88 13 00 00 53 D8 7E C...........S..
[17:44:01.696][R000266] 43 00 00 00 00 01 00 00 00 00 00 00 AD 00 B1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C...............................
[17:44:01.696][T000015] 43 01 00 00 04 00 00 00 10 27 00 00 80 BF 7E C........'.....
[17:44:01.712][R000014] 43 00 00 00 04 00 00 00 E3 01 03 00 7D 47 C...........}G
[17:44:01.712] - Received CfiInfo2 : 256
[17:44:01.712][ReqCfiInfo_2]
[17:44:01.712] - Sending CfiInfo2
[17:44:01.712][T000281] 44 00 00 00 0A 01 00 00 20 4E 00 00 F0 12 7E 02 00 85 00 00 01 00 00 00 00 AD 00 B1 00 00 00 00 D........N......................
[17:44:01.728][R000010] 44 00 00 00 0A 01 00 00 2E 76 D........v
[17:44:01.728] - Receiving ACK
[17:44:01.728][T000015] 43 01 00 00 0C 00 00 00 88 13 00 00 E4 7C 7E C............|.
[17:44:01.743][R000022] 43 00 00 00 0C 00 00 00 02 00 85 00 02 00 FF FF 85 02 03 00 0B 76 C....................v
[17:44:01.743] - Received ACK : FFFF
[17:44:01.743][Downloading BOOT CORE PSI(0)] : psi.fls
[17:44:01.743][ReqSecStart]
[17:44:01.743] - BootCoreVersion : 131072
[17:44:01.743] - Sending Security Start
[17:44:01.743][T002073] 44 00 00 00 0A 08 00 00 20 4E 00 00 C9 53 7E 02 00 04 02 00 08 00 00 00 00 00 00 00 00 00 00 00 D........N...S..................
[17:44:01.759][R000010] 44 00 00 00 0A 08 00 00 30 EA D.......0.
[17:44:01.759] - Receiving ACK
[17:44:01.759][T000015] 43 01 00 00 0C 00 00 00 88 13 00 00 E4 7C 7E C............|.
[17:44:01.853][R000022] 43 00 00 00 0C 00 00 00 02 00 41 00 40 00 22 00 9F 01 01 00 19 1D [email protected]".......
[17:44:01.853][ERROR] Type : 0041 <> 0204
[17:44:01.853] - IndErrorMsg
[17:44:01.853][T000015] 43 01 00 00 3E 00 00 00 88 13 00 00 03 9A 7E C...>..........
[17:44:01.868][R000072] 43 00 00 00 3E 00 00 00 4F 00 10 00 69 02 01 00 0A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C...>...O...i...................
[17:44:01.868]File_id(34), Line_number(415), Error_class(1), Error_code(79)
[17:44:01.868]File_id(16), Line_number(617), Error_class(1), Error_code(10)
[17:44:01.868]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:44:01.868]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:44:01.868]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:44:01.868]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:44:01.868]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:44:01.868]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:44:01.868] - Failure!
[17:44:01.868]ERROR : _Func_03_Ebl_0_ReqSecStart - Line(300)
[17:44:01.868]__Proc_NormalDownload : 0
[17:44:01.868]Error! IntelFlash:__Proc_NormalDownload
[17:44:01.868]_DoDownload : 0
[17:44:01.868]
-----------------------------------------Trace Last 100 Message-------------------------------------------------
[17:44:01.868]
------------------------------------------Trace Last 100 Message-------------------------------------------------
[17:44:01.868] ErrorCode(210)
Can please someone help me with reading this error message I have almost tried every solution except the Nvidia flash and I am using windows 10 64 bit.

fugitive666 said:
My phone got stuck in s/w upgrade screen the one with the blue one. Let me give you some history first.
My phone was working fine. Then i tried to update the software via LG Tool. Then the problem came with no sim card error. After researching a lot i found that there was IMEI number error. Then looked into many threads tried flashin with LG flash tool. I did everything as mentioned in the thread. But LG flash tool did not flash my phone. Only sign came READY in the flash tool, it did nothing.
No i am in need of help. Can anyone help me.
PS: Sent to service center they said that they did some hardware change and they solved the issue but after 2 days they said that again the problem persists.
Waiting for your help guyz....
Click to expand...
Click to collapse
Don't know if will work, please check: https://forum.xda-developers.com/op...to-unbrick-stuck-s-update-mode-t2871951/page2 specially communication #17.
GL.

Database Develop

welcome