Database Develop

Samsung Galaxy Mini GT-S5570 Bootloop

Hello.
Today I tried rooting and flashing a custom rom to my smartphone. The rooting process was completed normally, superuser was up etc. Installed Rom Manager but didn't flash CWM from there because I couldn't find my device name so I found it independently from here. Afterwards I tried flashing a CM 10.1 rom (Android 4.2.1), so I booted into recovery. Had a problem with backing up my rom so I proceeded (although I have a backup of my files from Titanium). Wiped data/cache and flashed the rom but then I forgot to REwipe data/cache and rebooted, resulting into a bootloop, with the samsung logo coming up, then the samsung galaxy animation, then repeat. Also, I could not enter recovery mode to wipe, because even after pressing the button combo the phone would skip to the samsung boot screen.
After that I tried multiple things:
1.Flashed CWM through Odin 4.38 independently. (File obtained from http://forum.xda-developers.com/showthread.php?t=1342190)
2.Flashed Stock Froyo rom. (File obtained from http://samsunggalaxyreview2.blogspot.gr/2011/05/samsung-galaxy-mini-s5570-original.html)
3.Flashed Stock Gingerbread rom (File obtained from http://yagyagaire.blogspot.gr/2011/08/upgrade-samsung-galaxy-popmini-gts5570.html#.UYmCjqJA3RM)
After Googling my problem and searching the forums I saw that most people got their issue fixed by either entering recovery (something I can't do), or flashing a different rom (which I did but to no avail).
So now I'm stuck with a device unable to fully boot successfully but with a working Download mode (the phone is accepted by Odin).
I don't know if this is what "bricking" is called but I definitely need help, either by a tutorial, link, instructions, etc. Anything you provide will be helping.
Also: it may sound stupid but is there a difference between s5570 and GT-s5570? If yes then probably the mistake is on my part and I'm sorry for making this thread.
Thank you very much.
Alexziab
EDIT: My initial stock version was Froyo 2.2.1

The first mistake you do is, you flashed Froyo over Gingerbread. Which NOT recommended.
Second, you flashed CM10.1 in stock recovery, another NOT recommended.
Third, GT-S5570 is S5570.
Fourth, that's not bootloop, that's Softbrick. Bootloop is looping in bootscreen, NOT bootsplash.

Reply
I see. Thank you for replying. Do you know any way to fix this problem?
EDIT: CM 10.1 was flashed after flashing the CWM recovery for Froyo 2.2.1, not stock recovery.

AlexZiab said:
I see. Thank you for replying. Do you know any way to fix this problem?
EDIT: CM 10.1 was flashed after flashing the CWM recovery for Froyo 2.2.1, not stock recovery.
Click to expand...
Click to collapse
You should have flashed cwm recovery over gingerbread, not on froyo.:what:
Sent Via XDA™ Premium

Reply
Galaxy_Rohit said:
You should have flashed cwm recovery over gingerbread, not on froyo.:what:
Sent Via XDA™ Premium
Click to expand...
Click to collapse
You see, I originally had Froyo. Flashed CWM on it through a thread here on xda (link above) then flashed 10.1.
Gingerbread was flashed later, in an attempt to recover the phone.

AlexZiab said:
You see, I originally had Froyo. Flashed CWM on it through a thread here on xda (link above) then flashed 10.1.
Gingerbread was flashed later, in an attempt to recover the phone.
Click to expand...
Click to collapse
Send it to SSC, they'll know what to do.

recovery problem with mini 2
I have a problem with GALAXY MINI 2, stock rom, stock kernel, rooted, TWRP recovery
I only tried CWM and TWRP, when I reboot into recovery from RomManager or QuickBoot I cannot reboot system, allways reboots into recovery, only other things that let's me do is power off and bootloader, is this a bug from something in stock kernel or something else ? for the moment I do not wish to flash something else in it
only thing that I could do to resolve this problem is to reflash recovery and autoboot from odin, all works ok now beside booting into recovery other way than power off and using hard keys, and it is damn hard to keep pressed that combination, and 90% from tryes I get power off, it shows TWRP screen and powers off
any ideas ?

grigtm said:
I have a problem with GALAXY MINI 2, stock rom, stock kernel, rooted, TWRP recovery
I only tried CWM and TWRP, when I reboot into recovery from RomManager or QuickBoot I cannot reboot system, allways reboots into recovery, only other things that let's me do is power off and bootloader, is this a bug from something in stock kernel or something else ? for the moment I do not wish to flash something else in it
only thing that I could do to resolve this problem is to reflash recovery and autoboot from odin, all works ok now beside booting into recovery other way than power off and using hard keys, and it is damn hard to keep pressed that combination, and 90% from tryes I get power off, it shows TWRP screen and powers off
any ideas ?
Click to expand...
Click to collapse
Go make a separate thread ! This isn't a ASKING THREAD !

Reply
F4uzan said:
Send it to SSC, they'll know what to do.
Click to expand...
Click to collapse
Can't I fix it by myself? My warranty has expired since 2012 so they will probably charge to fix it.

AlexZiab said:
Can't I fix it by myself? My warranty has expired since 2012 so they will probably charge to fix it.
Click to expand...
Click to collapse
No, you can't.

Fixed!
Followed this tutorial here on youtube: /watch?v=dU80AYnzf6g
After following the instructions, the phone finally booted! Language was set to (probably) russian but switched it to english and now I have a normally working (for now) phone! I don't see any problems with it! I guess the problem is solved. Thank you all for your support in any way!
Sorry for dodging the "link posting" rule that says that I should make 10 posts before posting a link. I have no intention to spam or anything, hope you understand.

AlexZiab if you don't now what you are doing just don't do it , buy a new phone and be careful next time
Sent from my GT-S5570 using xda app-developers app

SamsungGalaxyMiniPro said:
AlexZiab if you don't now what you are doing just don't do it , buy a new phone and be careful next time
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
You know what. I have flashed about 30 phones or more but It never happened to me that phone was stuck at bootloop until this phone. AlexZiab made a mistake but we all do mistakes sometimes so I do and you will aswell. He just asked for help. If you dont have any answer you should just be quiet and let somebody else to help. Your post looks like AlexZiab is some stupid guy or whatever. Nobody is so smart as you are probably :laugh: . If he dont made that mistake he will not know next time. We are all learning every day. If we dont do mistakes we will be stupid, You know.

Boot-Loop resurrection - I am stucked
Hi All,
I've a S5570, and seems soft bricked after some
- probably - mistyped dd.
Now it is in boot-loop. . .
I can enter DM but stock ROM-s won't help.
I've managed to get into this baby using openocd
but stucked at identifying the OneNAND flash on-board.
Code:
> arm9 mww 0xa0a000e0 0x00000000
> arm9 mww 0xa0a0000c 0x00000004
> arm9 mww 0xa0a00000 0x0000000b
> arm9 mww 0xa0a00010 0x00000001
> arm9 mdw 0xa0a00014
0xa0a00014 00000020
> arm9 mdw 0xa0a00040
0xa0a00040 00d100d1
>
The Id returned is öxööd1ööd1 but sould be 0x5500bcec or something.
The dump of the controller region seems OK:
Code:
> arm9 mdb 0xa0a00000 0x0x100
0xa0a00000 0b 00 00 00 01 f1 00 00 00 f2 01 f1 04 00 00 00 ................
0xa0a00010 00 00 00 00 20 00 00 00 00 00 00 00 20 00 00 00 .... ....... ...
0xa0a00020 1a 00 d4 aa bd 01 21 00 00 00 00 00 00 00 00 00 ......!.........
0xa0a00030 1a 00 d4 aa bd 01 21 00 06 00 00 10 00 00 00 00 ......!.........
0xa0a00040 d1 00 d1 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a00050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a00060 00 00 00 00 00 09 00 00 00 00 00 00 00 00 00 00 ................
0xa0a00070 80 47 80 47 a0 03 a0 03 b9 11 b9 11 a0 85 a0 85 .G.G............
0xa0a00080 20 c0 20 c0 20 c0 20 c0 20 c0 20 c0 00 00 00 00 . . . . . .....
0xa0a00090 00 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 ................
0xa0a000a0 00 00 00 00 00 00 00 00 00 00 00 00 0d 00 00 00 ................
0xa0a000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a000c0 41 f2 20 f2 00 00 00 00 00 00 00 00 00 00 00 00 A. .............
0xa0a000d0 90 70 ff f0 00 00 80 00 94 00 f3 00 e0 40 00 00 [email protected]
0xa0a000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a000f0 ff 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Now what?
Is it a hard-brick?
Regards
M5

Separate thread
meres5 said:
Hi All,
I've a S5570, and seems soft bricked after some
- probably - mistyped dd.
Now it is in boot-loop. . .
I can enter DM but stock ROM-s won't help.
I've managed to get into this baby using openocd
but stucked at identifying the OneNAND flash on-board.
Code:
> arm9 mww 0xa0a000e0 0x00000000
> arm9 mww 0xa0a0000c 0x00000004
> arm9 mww 0xa0a00000 0x0000000b
> arm9 mww 0xa0a00010 0x00000001
> arm9 mdw 0xa0a00014
0xa0a00014 00000020
> arm9 mdw 0xa0a00040
0xa0a00040 00d100d1
>
The Id returned is öxööd1ööd1 but sould be 0x5500bcec or something.
The dump of the controller region seems OK:
Code:
> arm9 mdb 0xa0a00000 0x0x100
0xa0a00000 0b 00 00 00 01 f1 00 00 00 f2 01 f1 04 00 00 00 ................
0xa0a00010 00 00 00 00 20 00 00 00 00 00 00 00 20 00 00 00 .... ....... ...
0xa0a00020 1a 00 d4 aa bd 01 21 00 00 00 00 00 00 00 00 00 ......!.........
0xa0a00030 1a 00 d4 aa bd 01 21 00 06 00 00 10 00 00 00 00 ......!.........
0xa0a00040 d1 00 d1 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a00050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a00060 00 00 00 00 00 09 00 00 00 00 00 00 00 00 00 00 ................
0xa0a00070 80 47 80 47 a0 03 a0 03 b9 11 b9 11 a0 85 a0 85 .G.G............
0xa0a00080 20 c0 20 c0 20 c0 20 c0 20 c0 20 c0 00 00 00 00 . . . . . .....
0xa0a00090 00 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 ................
0xa0a000a0 00 00 00 00 00 00 00 00 00 00 00 00 0d 00 00 00 ................
0xa0a000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a000c0 41 f2 20 f2 00 00 00 00 00 00 00 00 00 00 00 00 A. .............
0xa0a000d0 90 70 ff f0 00 00 80 00 94 00 f3 00 e0 40 00 00 [email protected]
0xa0a000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a000f0 ff 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Now what?
Is it a hard-brick?
Regards
M5
Click to expand...
Click to collapse
Someone said it before on this same thread, and I'm going to say it again. This is NOT a Q&A thread. If you have a question regarding a problem, make a separate thread. If you don't follow the rules, we are not obliged to help. Simple as that
Cheers

NP
Probably I misunderstood the titles:
> Legacy & Low Activity Devices > Samsung Galaxy Mini > Galaxy Mini Q&A, Help & Troubleshooting >
Sorry for that. . .
Seems I had better to buy a riffbox and do not disturb the "developers"...
(in the URL above)
Lynuxen said:
Someone said it before on this same thread, and I'm going to say it again. This is NOT a Q&A thread. If you have a question regarding a problem, make a separate thread. If you don't follow the rules, we are not obliged to help. Simple as that
Cheers
Click to expand...
Click to collapse

meres5 said:
Hi All,
I've a S5570, and seems soft bricked after some
- probably - mistyped dd.
Now it is in boot-loop. . .
I can enter DM but stock ROM-s won't help.
I've managed to get into this baby using openocd
but stucked at identifying the OneNAND flash on-board.
Code:
> arm9 mww 0xa0a000e0 0x00000000
> arm9 mww 0xa0a0000c 0x00000004
> arm9 mww 0xa0a00000 0x0000000b
> arm9 mww 0xa0a00010 0x00000001
> arm9 mdw 0xa0a00014
0xa0a00014 00000020
> arm9 mdw 0xa0a00040
0xa0a00040 00d100d1
>
The Id returned is öxööd1ööd1 but sould be 0x5500bcec or something.
The dump of the controller region seems OK:
Code:
> arm9 mdb 0xa0a00000 0x0x100
0xa0a00000 0b 00 00 00 01 f1 00 00 00 f2 01 f1 04 00 00 00 ................
0xa0a00010 00 00 00 00 20 00 00 00 00 00 00 00 20 00 00 00 .... ....... ...
0xa0a00020 1a 00 d4 aa bd 01 21 00 00 00 00 00 00 00 00 00 ......!.........
0xa0a00030 1a 00 d4 aa bd 01 21 00 06 00 00 10 00 00 00 00 ......!.........
0xa0a00040 d1 00 d1 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a00050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a00060 00 00 00 00 00 09 00 00 00 00 00 00 00 00 00 00 ................
0xa0a00070 80 47 80 47 a0 03 a0 03 b9 11 b9 11 a0 85 a0 85 .G.G............
0xa0a00080 20 c0 20 c0 20 c0 20 c0 20 c0 20 c0 00 00 00 00 . . . . . .....
0xa0a00090 00 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 ................
0xa0a000a0 00 00 00 00 00 00 00 00 00 00 00 00 0d 00 00 00 ................
0xa0a000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a000c0 41 f2 20 f2 00 00 00 00 00 00 00 00 00 00 00 00 A. .............
0xa0a000d0 90 70 ff f0 00 00 80 00 94 00 f3 00 e0 40 00 00 [email protected]
0xa0a000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a000f0 ff 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Now what?
Is it a hard-brick?
Regards
M5
Click to expand...
Click to collapse
We all make mistakes reading and remembering. I believe that this thread was in dev section and it was moved but he remembered it veing at the wrong place. We are all tires at the end of the year. Me too. My PC is about to die and I'm rarely in good mood nowdays.
Sent from my GT-S5570 using xda premium

An apology for my behavior
meres5 said:
Probably I misunderstood the titles:
> Legacy & Low Activity Devices > Samsung Galaxy Mini > Galaxy Mini Q&A, Help & Troubleshooting >
Sorry for that. . .
Seems I had better to buy a riffbox and do not disturb the "developers"...
(in the URL above)
Click to expand...
Click to collapse
I am deeply sorry for my behavior, and even more sorry that you misunderstood me.
You are in the right section. When I said this isn't a Q&A thread I meant it wasn't from the likes of this, meaning you post a question and you get an answer. But here you posted your question on another person's thread. This thread was created to by him to help him solve his problem by anyone who knows what that specific problem is. And you just walk right in here and start asking what's wrong with your device. Having a separate thread for your problem is mandatory in a case like this.
Second, I am not a developer. Am trying though. So you don't have to take my word for it, since obviously I have no right of telling what's wrong or what's right since I've never developed anything, right? Here is the same meaning in a different sentence by a person who is experienced here.
F4uzan said:
Go make a separate thread ! This isn't a ASKING THREAD !
Click to expand...
Click to collapse

[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

[HELP] P880 lock in download/SWUpgrade mode

hi ,
i've installed CM 10.1 on my p880 but I made the error to try upgrade to CM 10.3 ... all work fine but after a reboot i lost my imei number and so I can't use the phone .
I've tried to restore the previous ROM but it still don't work ...
So i tried to install the original rom and i put the phone in download mode ( vol down + usb cable ). Now i can't exit from this mode
( if i start my phon i can see lg logo and then "S/W Upgrade Please wait while upgrading....").
I tried with LG Flash Tool and with KDZ_UPDATE ... but always it stop at 10% ....
this is the LG Flash Tool log :
[17:53:42.612]DoDownload
[17:53:42.612]=====================================================
[17:53:42.612]= DLL Info : May 8 2012 13:09:31
[17:53:42.612]=====================================================
[17:53:42.613]###### Port Opend(41) ######
[17:53:42.613]Opened COM41
[17:53:42.618] MODEL880
[17:53:42.621] IMEI:352967057613485
[17:53:42.628] PID:YE05S130528000075
[17:53:42.631] SWV:LGP880AT-00-V20a-EUR-XXX-MAR-26-2013+0
[17:53:42.631][VerReq]
[17:53:42.631]Model Name : Target(P880)
[17:53:42.631][FeatureQuery]
[17:53:42.644]This firmware supports the following features:
[17:53:42.644] - Protocol Version : 3
[17:53:42.644] - CP Download : TRUE
[17:53:42.644] - AP Download : TRUE
[17:53:42.644] - ROM Download : TRUE
[17:53:42.644] - MaxPacketLength : 0x40000
[17:53:42.644] - Battery Level : 86%
[17:53:42.644] - OperatingMode : 4
[17:53:42.644] - AutoUpdateBuffer : 1
[17:53:42.644] - ThreadOn : 1
[17:53:42.646] Dz Information
[17:53:42.646] - Model Name : Binary(P880)
[17:53:42.646] - SWV : LGP880AT-00-V10a-EUR-XXX-MAY-23-2012+0
[17:53:42.646] - BuildTime : 2012-05-23 03:22:15
[17:53:42.646] - SecureType : 1
[17:53:42.646] - TotalFiles : 10
[17:53:42.646] Loading FLS
[17:53:42.793]IntelFlash::GetDownloadSize
[17:53:42.793] - PSI : 35316
[17:53:42.793] - EBL : 157172
[17:53:42.793] - Hardware : 172
[17:53:42.793] - Security : 2048
[17:53:42.793] - DownloadData : 20572
[17:53:42.793] - Security : 2048
[17:53:42.793] - DownloadData : 167768
[17:53:42.793] - Security : 2048
[17:53:42.793] - DownloadData : 697904
[17:53:42.793] - Security : 2048
[17:53:42.794] - DownloadData : 358028
[17:53:42.794] - Security : 2048
[17:53:42.794] - DownloadData : 7978564
[17:53:42.794] Loading CFG
[17:53:42.807]NvidiaFlash::GetDownloadSize
[17:53:42.807] - BCT : 6128
[17:53:42.807] - EBT : 1142868
[17:53:42.807] - EKS : 684
[17:53:42.807] - SOS : 7577600
[17:53:42.807] - LNX : 6496256
[17:53:42.807] - APP : 679695740
[17:53:42.807]TotalSize : 67130255
[17:53:42.807]CP Download Starting : 0
[17:53:42.807]CP Binary has been loaded(9465272)
[17:53:42.807][Intel] MemoryMap
[17:53:42.807] FlashStartAddr : 0x40000000
[17:53:42.807] CUST : StartAddress(0x63000000), Length(0x00500000) : LINUX
[17:53:42.808] CUST : StartAddress(0x38000000), Length(0x08400000) : CLONE
[17:53:42.808] CUST : StartAddress(0x30000000), Length(0x08400100) : PREFLASH
[17:53:42.808] CUST : StartAddress(0x20000000), Length(0x00500000) : USBRO_ISO
[17:53:42.808] CUST : StartAddress(0x90000000), Length(0x001FE000) : CUSTDATA
[17:53:42.808][CMD_Intel_DownloadMode]
[17:53:43.367] - Device synchronized
[17:53:43.367][Injecting PSI RAM] : 35316
[17:53:43.367] - Sending PSI RAM
[17:53:46.427] - Receiving CRC
[17:53:46.440] - Received CRC OK : 01
[17:53:46.440] - Receiving ACK
[17:53:46.453] - Received ACK : 01 00 AA
[17:53:46.453] - PSI RAM Running
[17:53:46.454][Injecting EBL] : 157172
[17:53:46.454] - Sending EBL Length
[17:53:46.461] - Receiving ACK
[17:53:46.474] - Received ACK : 0xCCCC
[17:53:46.474] - Sending EBL : 157172
[17:54:00.181] - Sending CRC : FA
[17:54:00.192] - Receiving ACK
[17:54:00.241] - Received OK : 51 A5
[17:54:00.241] - Receiving Capabilities : 76
[17:54:00.254] - Boot-loader is active
[17:54:00.254] - EBL version: XMM6260_20.21_M1S1
[17:54:00.254] - Boot mode is: 00BB
[17:54:00.254] - EBL Running
[17:54:00.254][ReqSetProtConf]
[17:54:00.255] == prot_capabilities_t ==
[17:54:00.255] - protocol_version : 11
[17:54:00.255] - package_size : 2 -> 8
[17:54:00.255] - crc_type : 1
[17:54:00.255] - skip_writeblock_tx : 0
[17:54:00.256] - compression : 11 -> 10
[17:54:00.256] - compression : 10
[17:54:00.256] - flags : 1
[17:54:00.256] - erase_sector_verify : 0
[17:54:00.256] - flash_debug : 0
[17:54:00.256] - protocol_crc : 0
[17:54:00.256] - skip_erase : 1 -> 0
[17:54:00.257] - skip_wr_pack_crc : 0
[17:54:00.257] - Sending capabilities
[17:54:00.267] - Receiving ACK
[17:54:00.280] - Received : ACK 0100
[17:54:00.280][CnfBaudChange] : 3250000
[17:54:00.280] - Sending BaudRate
[17:54:00.291] - Receiving ACK
[17:54:00.327] - Received BaudRate : 3250000
[17:54:00.327] - Changing BaudRate
[17:54:00.337] - Changed BaudRate : 3250000
[17:54:00.337][ReqFlashId]
[17:54:00.337] - Platform : 14
[17:54:00.337] - ProjectName : XMM6260
[17:54:00.338] - Sending HardWare Info
[17:54:00.348] - Receiving ACK
[17:54:00.431] - Received ACK : 0000
[17:54:00.431][ReqCfiInfo_1]
[17:54:00.431] - Sending CfiInfo1
[17:54:00.442] - Receiving CfiInfo2
[17:54:00.480] - Received CfiInfo2 : 256
[17:54:00.480][ReqCfiInfo_2]
[17:54:00.480] - Sending CfiInfo2
[17:54:00.490] - Receiving ACK
[17:54:00.502] - Received ACK : FFFF
[17:54:00.502][Downloading BOOT CORE PSI(0)] : psi.fls
[17:54:00.502][ReqSecStart]
[17:54:00.502] - BootCoreVersion : 131072
[17:54:00.502] - Sending Security Start
[17:54:00.518] - Receiving ACK
[17:54:00.605][ERROR] Type : 0041 <> 0204
[17:54:00.605] - IndErrorMsg
[17:54:00.615]File_id(34), Line_number(415), Error_class(1), Error_code(79)
[17:54:00.615]File_id(16), Line_number(617), Error_class(1), Error_code(10)
[17:54:00.615]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.615]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616] - Failure!
[17:54:00.616]ERROR : _Func_03_Ebl_0_ReqSecStart - Line(326)
[17:54:00.619]__Proc_NormalDownload : 0
[17:54:00.619]Error! IntelFlash:__Proc_NormalDownload
[17:54:00.619]_DoDownload : 0, ErrorCode(210)
[17:54:00.620]
-----------------------------------------Trace Last 100 Message-------------------------------------------------
[17:54:00.242][T000015] 43 01 00 00 4C 00 00 00 88 13 00 00 15 19 7E C...L..........
[17:54:00.254][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:54:00.254] - Boot-loader is active
[17:54:00.254] - EBL version: XMM6260_20.21_M1S1
[17:54:00.254] - Boot mode is: 00BB
[17:54:00.254] - EBL Running
[17:54:00.254][ReqSetProtConf]
[17:54:00.255] == prot_capabilities_t ==
[17:54:00.255] - protocol_version : 11
[17:54:00.255] - package_size : 2 -> 8
[17:54:00.255] - crc_type : 1
[17:54:00.255] - skip_writeblock_tx : 0
[17:54:00.256] - compression : 11 -> 10
[17:54:00.256] - compression : 10
[17:54:00.256] - flags : 1
[17:54:00.256] - erase_sector_verify : 0
[17:54:00.256] - flash_debug : 0
[17:54:00.256] - protocol_crc : 0
[17:54:00.256] - skip_erase : 1 -> 0
[17:54:00.257] - skip_wr_pack_crc : 0
[17:54:00.257] - Sending capabilities
[17:54:00.257][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:54:00.267][R000010] 44 00 00 00 56 00 00 00 D0 6E D...V....n
[17:54:00.267] - Receiving ACK
[17:54:00.268][T000015] 43 01 00 00 0C 00 00 00 88 13 00 00 E4 7C 7E C............|.
[17:54:00.280][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:54:00.280] - Received : ACK 0100
[17:54:00.280][CnfBaudChange] : 3250000
[17:54:00.280] - Sending BaudRate
[17:54:00.281][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:54:00.291][R000010] 44 00 00 00 0E 00 00 00 1E 5E D........^
[17:54:00.291] - Receiving ACK
[17:54:00.291][T000015] 43 01 00 00 06 00 00 00 10 27 00 00 EF B4 7E C........'.....
[17:54:00.301][R000016] 43 00 00 00 06 00 00 00 02 00 82 00 04 00 C7 FA C...............
[17:54:00.303][T000015] 43 01 00 00 04 00 00 00 88 13 00 00 58 51 7E C...........XQ.
[17:54:00.315][R000014] 43 00 00 00 04 00 00 00 50 97 31 00 9E D9 C.......P.1...
[17:54:00.315][T000015] 43 01 00 00 04 00 00 00 10 27 00 00 80 BF 7E C........'.....
[17:54:00.327][R000014] 43 00 00 00 04 00 00 00 9E 01 03 00 B7 96 C.............
[17:54:00.327] - Received BaudRate : 3250000
[17:54:00.327] - Changing BaudRate
[17:54:00.328][T000011] 45 00 00 00 50 97 31 00 F3 0E 7E E...P.1....
[17:54:00.337][R000010] 45 00 00 00 50 97 31 00 F3 0E E...P.1...
[17:54:00.337] - Changed BaudRate : 3250000
[17:54:00.337][ReqFlashId]
[17:54:00.337] - Platform : 14
[17:54:00.337] - ProjectName : XMM6260
[17:54:00.338] - Sending HardWare Info
[17:54:00.339][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:54:00.348][R000010] 44 00 00 00 B6 00 00 00 5A DA D.......Z.
[17:54:00.348] - Receiving ACK
[17:54:00.349][T000015] 43 01 00 00 0C 00 00 00 88 13 00 00 E4 7C 7E C............|.
[17:54:00.431][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:54:00.431] - Received ACK : 0000
[17:54:00.431][ReqCfiInfo_1]
[17:54:00.431] - Sending CfiInfo1
[17:54:00.433][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:54:00.442][R000010] 44 00 00 00 0C 00 00 00 68 67 D.......hg
[17:54:00.442] - Receiving CfiInfo2
[17:54:00.443][T000015] 43 01 00 00 06 00 00 00 10 27 00 00 EF B4 7E C........'.....
[17:54:00.455][R000016] 43 00 00 00 06 00 00 00 02 00 84 00 00 01 B4 C7 C...............
[17:54:00.455][T000015] 43 01 00 00 00 01 00 00 88 13 00 00 53 D8 7E C...........S..
[17:54:00.467][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:54:00.468][T000015] 43 01 00 00 04 00 00 00 10 27 00 00 80 BF 7E C........'.....
[17:54:00.480][R000014] 43 00 00 00 04 00 00 00 E3 01 03 00 7D 47 C...........}G
[17:54:00.480] - Received CfiInfo2 : 256
[17:54:00.480][ReqCfiInfo_2]
[17:54:00.480] - Sending CfiInfo2
[17:54:00.481][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:54:00.490][R000010] 44 00 00 00 0A 01 00 00 2E 76 D........v
[17:54:00.490] - Receiving ACK
[17:54:00.490][T000015] 43 01 00 00 0C 00 00 00 88 13 00 00 E4 7C 7E C............|.
[17:54:00.502][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:54:00.502] - Received ACK : FFFF
[17:54:00.502][Downloading BOOT CORE PSI(0)] : psi.fls
[17:54:00.502][ReqSecStart]
[17:54:00.502] - BootCoreVersion : 131072
[17:54:00.502] - Sending Security Start
[17:54:00.503][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:54:00.518][R000010] 44 00 00 00 0A 08 00 00 30 EA D.......0.
[17:54:00.518] - Receiving ACK
[17:54:00.518][T000015] 43 01 00 00 0C 00 00 00 88 13 00 00 E4 7C 7E C............|.
[17:54:00.605][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:54:00.605][ERROR] Type : 0041 <> 0204
[17:54:00.605] - IndErrorMsg
[17:54:00.606][T000015] 43 01 00 00 3E 00 00 00 88 13 00 00 03 9A 7E C...>..........
[17:54:00.615][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:54:00.615]File_id(34), Line_number(415), Error_class(1), Error_code(79)
[17:54:00.615]File_id(16), Line_number(617), Error_class(1), Error_code(10)
[17:54:00.615]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.615]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616] - Failure!
[17:54:00.616]ERROR : _Func_03_Ebl_0_ReqSecStart - Line(326)
[17:54:00.619]__Proc_NormalDownload : 0
[17:54:00.619]Error! IntelFlash:__Proc_NormalDownload
[17:54:00.619]_DoDownload : 0, ErrorCode(210)
[17:54:00.620]
-----------------------------------------Trace Last 100 Message-------------------------------------------------
[17:54:00.632]
------------------------------------------Trace Last 100 Message-------------------------------------------------
can someone help me :crying::crying:.... please
there's a way to exit from this mode ??

narkos said:
hi ,
i've installed CM 10.1 on my p880 but I made the error to try upgrade to CM 10.3 ... all work fine but after a reboot i lost my imei number and so I can't use the phone .
I've tried to restore the previous ROM but it still don't work ...
So i tried to install the original rom and i put the phone in download mode ( vol down + usb cable ). Now i can't exit from this mode
( if i start my phon i can see lg logo and then "S/W Upgrade Please wait while upgrading....").
I tried with LG Flash Tool and with KDZ_UPDATE ... but always it stop at 10% ....
this is the LG Flash Tool log :
[17:53:42.612]DoDownload
[17:53:42.612]=====================================================
[17:53:42.612]= DLL Info : May 8 2012 13:09:31
[17:53:42.612]=====================================================
[17:53:42.613]###### Port Opend(41) ######
[17:53:42.613]Opened COM41
[17:53:42.618] MODEL880
[17:53:42.621] IMEI:352967057613485
[17:53:42.628] PID:YE05S130528000075
[17:53:42.631] SWV:LGP880AT-00-V20a-EUR-XXX-MAR-26-2013+0
[17:53:42.631][VerReq]
[17:53:42.631]Model Name : Target(P880)
[17:53:42.631][FeatureQuery]
[17:53:42.644]This firmware supports the following features:
[17:53:42.644] - Protocol Version : 3
[17:53:42.644] - CP Download : TRUE
[17:53:42.644] - AP Download : TRUE
[17:53:42.644] - ROM Download : TRUE
[17:53:42.644] - MaxPacketLength : 0x40000
[17:53:42.644] - Battery Level : 86%
[17:53:42.644] - OperatingMode : 4
[17:53:42.644] - AutoUpdateBuffer : 1
[17:53:42.644] - ThreadOn : 1
[17:53:42.646] Dz Information
[17:53:42.646] - Model Name : Binary(P880)
[17:53:42.646] - SWV : LGP880AT-00-V10a-EUR-XXX-MAY-23-2012+0
[17:53:42.646] - BuildTime : 2012-05-23 03:22:15
[17:53:42.646] - SecureType : 1
[17:53:42.646] - TotalFiles : 10
[17:53:42.646] Loading FLS
[17:53:42.793]IntelFlash::GetDownloadSize
[17:53:42.793] - PSI : 35316
[17:53:42.793] - EBL : 157172
[17:53:42.793] - Hardware : 172
[17:53:42.793] - Security : 2048
[17:53:42.793] - DownloadData : 20572
[17:53:42.793] - Security : 2048
[17:53:42.793] - DownloadData : 167768
[17:53:42.793] - Security : 2048
[17:53:42.793] - DownloadData : 697904
[17:53:42.793] - Security : 2048
[17:53:42.794] - DownloadData : 358028
[17:53:42.794] - Security : 2048
[17:53:42.794] - DownloadData : 7978564
[17:53:42.794] Loading CFG
[17:53:42.807]NvidiaFlash::GetDownloadSize
[17:53:42.807] - BCT : 6128
[17:53:42.807] - EBT : 1142868
[17:53:42.807] - EKS : 684
[17:53:42.807] - SOS : 7577600
[17:53:42.807] - LNX : 6496256
[17:53:42.807] - APP : 679695740
[17:53:42.807]TotalSize : 67130255
[17:53:42.807]CP Download Starting : 0
[17:53:42.807]CP Binary has been loaded(9465272)
[17:53:42.807][Intel] MemoryMap
[17:53:42.807] FlashStartAddr : 0x40000000
[17:53:42.807] CUST : StartAddress(0x63000000), Length(0x00500000) : LINUX
[17:53:42.808] CUST : StartAddress(0x38000000), Length(0x08400000) : CLONE
[17:53:42.808] CUST : StartAddress(0x30000000), Length(0x08400100) : PREFLASH
[17:53:42.808] CUST : StartAddress(0x20000000), Length(0x00500000) : USBRO_ISO
[17:53:42.808] CUST : StartAddress(0x90000000), Length(0x001FE000) : CUSTDATA
[17:53:42.808][CMD_Intel_DownloadMode]
[17:53:43.367] - Device synchronized
[17:53:43.367][Injecting PSI RAM] : 35316
[17:53:43.367] - Sending PSI RAM
[17:53:46.427] - Receiving CRC
[17:53:46.440] - Received CRC OK : 01
[17:53:46.440] - Receiving ACK
[17:53:46.453] - Received ACK : 01 00 AA
[17:53:46.453] - PSI RAM Running
[17:53:46.454][Injecting EBL] : 157172
[17:53:46.454] - Sending EBL Length
[17:53:46.461] - Receiving ACK
[17:53:46.474] - Received ACK : 0xCCCC
[17:53:46.474] - Sending EBL : 157172
[17:54:00.181] - Sending CRC : FA
[17:54:00.192] - Receiving ACK
[17:54:00.241] - Received OK : 51 A5
[17:54:00.241] - Receiving Capabilities : 76
[17:54:00.254] - Boot-loader is active
[17:54:00.254] - EBL version: XMM6260_20.21_M1S1
[17:54:00.254] - Boot mode is: 00BB
[17:54:00.254] - EBL Running
[17:54:00.254][ReqSetProtConf]
[17:54:00.255] == prot_capabilities_t ==
[17:54:00.255] - protocol_version : 11
[17:54:00.255] - package_size : 2 -> 8
[17:54:00.255] - crc_type : 1
[17:54:00.255] - skip_writeblock_tx : 0
[17:54:00.256] - compression : 11 -> 10
[17:54:00.256] - compression : 10
[17:54:00.256] - flags : 1
[17:54:00.256] - erase_sector_verify : 0
[17:54:00.256] - flash_debug : 0
[17:54:00.256] - protocol_crc : 0
[17:54:00.256] - skip_erase : 1 -> 0
[17:54:00.257] - skip_wr_pack_crc : 0
[17:54:00.257] - Sending capabilities
[17:54:00.267] - Receiving ACK
[17:54:00.280] - Received : ACK 0100
[17:54:00.280][CnfBaudChange] : 3250000
[17:54:00.280] - Sending BaudRate
[17:54:00.291] - Receiving ACK
[17:54:00.327] - Received BaudRate : 3250000
[17:54:00.327] - Changing BaudRate
[17:54:00.337] - Changed BaudRate : 3250000
[17:54:00.337][ReqFlashId]
[17:54:00.337] - Platform : 14
[17:54:00.337] - ProjectName : XMM6260
[17:54:00.338] - Sending HardWare Info
[17:54:00.348] - Receiving ACK
[17:54:00.431] - Received ACK : 0000
[17:54:00.431][ReqCfiInfo_1]
[17:54:00.431] - Sending CfiInfo1
[17:54:00.442] - Receiving CfiInfo2
[17:54:00.480] - Received CfiInfo2 : 256
[17:54:00.480][ReqCfiInfo_2]
[17:54:00.480] - Sending CfiInfo2
[17:54:00.490] - Receiving ACK
[17:54:00.502] - Received ACK : FFFF
[17:54:00.502][Downloading BOOT CORE PSI(0)] : psi.fls
[17:54:00.502][ReqSecStart]
[17:54:00.502] - BootCoreVersion : 131072
[17:54:00.502] - Sending Security Start
[17:54:00.518] - Receiving ACK
[17:54:00.605][ERROR] Type : 0041 <> 0204
[17:54:00.605] - IndErrorMsg
[17:54:00.615]File_id(34), Line_number(415), Error_class(1), Error_code(79)
[17:54:00.615]File_id(16), Line_number(617), Error_class(1), Error_code(10)
[17:54:00.615]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.615]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616] - Failure!
[17:54:00.616]ERROR : _Func_03_Ebl_0_ReqSecStart - Line(326)
[17:54:00.619]__Proc_NormalDownload : 0
[17:54:00.619]Error! IntelFlash:__Proc_NormalDownload
[17:54:00.619]_DoDownload : 0, ErrorCode(210)
[17:54:00.620]
-----------------------------------------Trace Last 100 Message-------------------------------------------------
[17:54:00.242][T000015] 43 01 00 00 4C 00 00 00 88 13 00 00 15 19 7E C...L..........
[17:54:00.254][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:54:00.254] - Boot-loader is active
[17:54:00.254] - EBL version: XMM6260_20.21_M1S1
[17:54:00.254] - Boot mode is: 00BB
[17:54:00.254] - EBL Running
[17:54:00.254][ReqSetProtConf]
[17:54:00.255] == prot_capabilities_t ==
[17:54:00.255] - protocol_version : 11
[17:54:00.255] - package_size : 2 -> 8
[17:54:00.255] - crc_type : 1
[17:54:00.255] - skip_writeblock_tx : 0
[17:54:00.256] - compression : 11 -> 10
[17:54:00.256] - compression : 10
[17:54:00.256] - flags : 1
[17:54:00.256] - erase_sector_verify : 0
[17:54:00.256] - flash_debug : 0
[17:54:00.256] - protocol_crc : 0
[17:54:00.256] - skip_erase : 1 -> 0
[17:54:00.257] - skip_wr_pack_crc : 0
[17:54:00.257] - Sending capabilities
[17:54:00.257][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:54:00.267][R000010] 44 00 00 00 56 00 00 00 D0 6E D...V....n
[17:54:00.267] - Receiving ACK
[17:54:00.268][T000015] 43 01 00 00 0C 00 00 00 88 13 00 00 E4 7C 7E C............|.
[17:54:00.280][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:54:00.280] - Received : ACK 0100
[17:54:00.280][CnfBaudChange] : 3250000
[17:54:00.280] - Sending BaudRate
[17:54:00.281][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:54:00.291][R000010] 44 00 00 00 0E 00 00 00 1E 5E D........^
[17:54:00.291] - Receiving ACK
[17:54:00.291][T000015] 43 01 00 00 06 00 00 00 10 27 00 00 EF B4 7E C........'.....
[17:54:00.301][R000016] 43 00 00 00 06 00 00 00 02 00 82 00 04 00 C7 FA C...............
[17:54:00.303][T000015] 43 01 00 00 04 00 00 00 88 13 00 00 58 51 7E C...........XQ.
[17:54:00.315][R000014] 43 00 00 00 04 00 00 00 50 97 31 00 9E D9 C.......P.1...
[17:54:00.315][T000015] 43 01 00 00 04 00 00 00 10 27 00 00 80 BF 7E C........'.....
[17:54:00.327][R000014] 43 00 00 00 04 00 00 00 9E 01 03 00 B7 96 C.............
[17:54:00.327] - Received BaudRate : 3250000
[17:54:00.327] - Changing BaudRate
[17:54:00.328][T000011] 45 00 00 00 50 97 31 00 F3 0E 7E E...P.1....
[17:54:00.337][R000010] 45 00 00 00 50 97 31 00 F3 0E E...P.1...
[17:54:00.337] - Changed BaudRate : 3250000
[17:54:00.337][ReqFlashId]
[17:54:00.337] - Platform : 14
[17:54:00.337] - ProjectName : XMM6260
[17:54:00.338] - Sending HardWare Info
[17:54:00.339][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:54:00.348][R000010] 44 00 00 00 B6 00 00 00 5A DA D.......Z.
[17:54:00.348] - Receiving ACK
[17:54:00.349][T000015] 43 01 00 00 0C 00 00 00 88 13 00 00 E4 7C 7E C............|.
[17:54:00.431][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:54:00.431] - Received ACK : 0000
[17:54:00.431][ReqCfiInfo_1]
[17:54:00.431] - Sending CfiInfo1
[17:54:00.433][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:54:00.442][R000010] 44 00 00 00 0C 00 00 00 68 67 D.......hg
[17:54:00.442] - Receiving CfiInfo2
[17:54:00.443][T000015] 43 01 00 00 06 00 00 00 10 27 00 00 EF B4 7E C........'.....
[17:54:00.455][R000016] 43 00 00 00 06 00 00 00 02 00 84 00 00 01 B4 C7 C...............
[17:54:00.455][T000015] 43 01 00 00 00 01 00 00 88 13 00 00 53 D8 7E C...........S..
[17:54:00.467][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:54:00.468][T000015] 43 01 00 00 04 00 00 00 10 27 00 00 80 BF 7E C........'.....
[17:54:00.480][R000014] 43 00 00 00 04 00 00 00 E3 01 03 00 7D 47 C...........}G
[17:54:00.480] - Received CfiInfo2 : 256
[17:54:00.480][ReqCfiInfo_2]
[17:54:00.480] - Sending CfiInfo2
[17:54:00.481][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:54:00.490][R000010] 44 00 00 00 0A 01 00 00 2E 76 D........v
[17:54:00.490] - Receiving ACK
[17:54:00.490][T000015] 43 01 00 00 0C 00 00 00 88 13 00 00 E4 7C 7E C............|.
[17:54:00.502][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:54:00.502] - Received ACK : FFFF
[17:54:00.502][Downloading BOOT CORE PSI(0)] : psi.fls
[17:54:00.502][ReqSecStart]
[17:54:00.502] - BootCoreVersion : 131072
[17:54:00.502] - Sending Security Start
[17:54:00.503][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:54:00.518][R000010] 44 00 00 00 0A 08 00 00 30 EA D.......0.
[17:54:00.518] - Receiving ACK
[17:54:00.518][T000015] 43 01 00 00 0C 00 00 00 88 13 00 00 E4 7C 7E C............|.
[17:54:00.605][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:54:00.605][ERROR] Type : 0041 <> 0204
[17:54:00.605] - IndErrorMsg
[17:54:00.606][T000015] 43 01 00 00 3E 00 00 00 88 13 00 00 03 9A 7E C...>..........
[17:54:00.615][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:54:00.615]File_id(34), Line_number(415), Error_class(1), Error_code(79)
[17:54:00.615]File_id(16), Line_number(617), Error_class(1), Error_code(10)
[17:54:00.615]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.615]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616]File_id(0), Line_number(0), Error_class(0), Error_code(0)
[17:54:00.616] - Failure!
[17:54:00.616]ERROR : _Func_03_Ebl_0_ReqSecStart - Line(326)
[17:54:00.619]__Proc_NormalDownload : 0
[17:54:00.619]Error! IntelFlash:__Proc_NormalDownload
[17:54:00.619]_DoDownload : 0, ErrorCode(210)
[17:54:00.620]
-----------------------------------------Trace Last 100 Message-------------------------------------------------
[17:54:00.632]
------------------------------------------Trace Last 100 Message-------------------------------------------------
can someone help me :crying::crying:.... please
there's a way to exit from this mode ??
Click to expand...
Click to collapse
Mate, you're trying install KDZ V10A? Right?
You must install KDZ V20A, V20B, V20C or V20D because V10A will not work (It's possible)
Try remove the battery for a few minutes, do a factory reset, then after flash KDZ ​​V20xx.
If you want to downgrade again to V10A follow this.
Hope this helps you. :fingers-crossed:

thank's for the answer.
i tried to install both 10A_00, 10H_00, 20A_00, 20B_00, with the same result....
to do a factory reset i must press vol down + power button ?
i tried but at boot i see just for a moment the LG logo and then the written : SW Upgrade ....
Now i'll try 20C_00 or 20_D ... i hope it will work
I want try with nvflash to rewrite all... do you agree ?

Well, try to follow this tutorial or try to downgrade, if you try to burn some V10xx KDZ in the normal method will not work.
to do a factory reset i must press vol down + power button ?
Click to expand...
Click to collapse
See this
i tried but at boot i see just for a moment the LG logo and then the written : SW Upgrade ....
Click to expand...
Click to collapse
The usb cable was connected? If so, unplug.
About nvflash, I've never tried, so do not know what to say.
I believe it is better you attempt downgrade, then try installing again some V20xx.
Good luck mate.

Buuzzaa said:
Well, try to follow this tutorial or try to downgrade, if you try to burn some V10xx KDZ in the normal method will not work.
See this
The usb cable was connected? If so, unplug.
About nvflash, I've never tried, so do not know what to say.
I believe it is better you attempt downgrade, then try installing again some V20xx.
Good luck mate.
Click to expand...
Click to collapse
I've re-tried the guide that you link me without success :crying::crying::crying::crying::crying:
the hard reset don't work for me ..... the phone always start in s/W update mode.
I supposed that my phone was void in this moment....
When I try to install KDZ by LG Mobile Support Tool i've this error :
...
Step : TYPE_WPARAM_UPGRADE_ERROR
CleanModelDll() : Free Model.dll
_DetachDLL Call
_DetachDLL Call End
Page_Error ºÎºÐÀÔ´Ï´Ù
¿©±â´Â Retry ºÎºÐÀÔ´Ï´Ù
both with 10_A, 10_H, 20_A, 20_B, 20_D .
what other can I try ?

narkos said:
I've re-tried the guide that you link me without success :crying::crying::crying::crying::crying:
the hard reset don't work for me ..... the phone always start in s/W update mode.
I supposed that my phone was void in this moment....
When I try to install KDZ by LG Mobile Support Tool i've this error :
...
Step : TYPE_WPARAM_UPGRADE_ERROR
CleanModelDll() : Free Model.dll
_DetachDLL Call
_DetachDLL Call End
Page_Error ºÎºÐÀÔ´Ï´Ù
¿©±â´Â Retry ºÎºÐÀÔ´Ï´Ù
both with 10_A, 10_H, 20_A, 20_B, 20_D .
what other can I try ?
Click to expand...
Click to collapse
Well, there is one other option to install KDZ... Try this.
Remember, try install only V20xx with this method.
Good luck mate... Hope is the last one to die. :fingers-crossed:

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