Hey folks,
its bricked due to FOTA (I think it stands for: firmware over the air) update. This means the phone downloads a firmware update without computer connection or further PC-Software. Alas it didn't work.
Situation:
Phone starts, displays LG Logo and after that an 'updating firmware' screen for about 1 sec before rebooting and doing it all over again.
What I tried to solve this:
set up a new Win 7 32 bit machine to try to unbrick it. (drivers didn't work correctly on 64 bit) at least the MCCI driver update didn't)
connected the phone with the PC in Emergency Mode (holding VOL_UP + VOL_DOWN + PWR while USB is connected)
downloaded B2CApp (LGSupport Tool) and installed the device drivers for Emergency mode.
disabled the Android(Modem) dirver
downloaded V10D_00.kdz from LG home page
using the phones IMEI and this link:
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=IMEI_NUMBER_GOES_HERE
This gave me this link
http://csmgdl.lgmobile.com/swdata/WDLSW/LGE720/ADEUBK/V10d_00/V10D_00.kdz
I'm German so this seems all right, but I'm no expert​
installed msxml
ran KDZ_FW_UPD_EN and tried CDMA in CS_EMERGENCY Mode
A bunch of magic happend until the phone restarts during the process and is right back where we started, if I put it back to Emergency Mode while KDZ_FW_UPD_EN is still running the process finishes, but to no avail.
The log of this try is attached.
Where I am stuck now:
phone:
runs in Emergency Mode
is recognized by KDZ_FW_UPD_EN as well es LG Support Tool
Flashing via KDZ_FW_UPD_EN finishes
Flashing yields no result.
What else did I try
download V10C_00.kdz, as well as V10A_00.kdz from LG site and tried those with same result as with V10D_00.kdz
tried 3GQCT Type instead of CDMA
Wild guesses by me:
I need a different KDZ_FW_UPD_EN version, maybe different dll. I got it from here somewhre in a LG P500 related topic.
I messed up the driver install or need a different driver
LG hates me personally and planted this whole brick specifically to get to me.
The device really is permanently bricked, so I did all I could and there is nothing more to do? That would be sad, I hope I'm wrong here.
Additional Info:
The phone is not rooted and has never before been flashed. It ran with the same stock firmware since it was unwrapped.
The phone was not interrupted by power-loss during FOTA update.
The [read phone information] tool from KDZ_FW_UDP_EN crashes every time, maybe this tells somebody where things go wrong
Any help is appreciated. Ask for more info, if you need it.
Update - What else did I try:
I got the LG Support Tool to flash the Emergency Recovery all by itself runs till 99% --> reboots --> still stuck in same ol' bootloop
reentering Emergency Mode from the bootloop makes the Emergency Recovery finish with 100%, no error, but still bricked.
Regards
gimmeg
I used SP Flash Tool to update the ROM of my Umi Iron (deselected preloader, as advised), it stopped at 18%, gave an error and since then, my phone is in a bootloop. Can only get to stock Recovery (the android on its back). After a while in recovery, the phone reboots automatically, showing the Umi symbol for a few seconds, rebooting again back to recovery...
Fastboot and adb don't seem to find the device in this state. Installed the MT65x3 USB VCOM drivers, anything else I need?
Anyway to enter the bootloader or use adb/fastboot in any way? Sure hope I'm not completely screwed...
Good Day. I was upgrading from LP to MM. Was on Step 3 on de LGUP update process when my computer battery died on me. The phone is now in a bootloop indicating me Boot Verification Fail cause: Mismatch_Sig_Len on the LG Screen, I can access Download Mode but it rolls back to the Lg Bootloop Screen and I can also access fastboot and the computer does recognize the phone... ........ . Is it dead? Tried to get the phone to be recognized with LGUP with no luck. Thanks for any help provided. :crying::crying:
Good evening, I have in my hands a smartphone lg p778g does not pass me the logo to light following a simple copy of the folder whatsapp internal memory to the microsd (it was blocked after you copy and to restart it and did not initiate more ... it stays in the LG logo when turned on and there does not pass.
I tried to hard reset with vol (+ or -) buttons + home + power but rather than get out the menu of recovery I get the doll android slept with a triangle exclamation and there is no way to enter the menu that tightening no buttons.
Then I looking for information online found the utility tool flash, did all the steps as marked, I installed the drivers perfectly, the PC detects me the phone without problems, but always in the middle of the update (put the mobile mode s / w upgrade ) 50% program lg cancel the process by saying that there has been an unknown error and try try again by disconnecting and connecting the mobile, but no way, I give retry to to try again and again it hangs at 50% and I jump the error screen again.
I wonder if there is some other program where you can do the hard reset this phone than by the official LG utility, or by microsd.
The operating system used is Windows 7 64-bit, disable the Windows firewall and antivirus and run as administrator utility tool flash lg 2014, but always the same. I also tried running the utility lg mobile support tool directly to you directly seeking the most updated for lg p778g firmware, but it's the same as using the lg flash tool 2014, the 50% of the upgrade stops and gives me the message error.
A greeting and I hope you can help me, I need the phone !!
We'd need someone with a p778g. The problem may be be caused by the special branding of the phone, or an encrypted bootloader. Or the internal flash got completely cleared, partitions and baseband rom, which means a full brick. Otherwise flashing stock in D/L mode should work, even if anything else fails. But this goes mainly for LGs official tool working online. With the LG Flash Tool 2014 i had also problems.
I think both tools have to ways to perform the unbricking. Either with the phone put in D/L mode by the user (if Fastboot don't work on the PC), or by recognizing the phone (but with a still running system) via ADB, then auto-switching to Fastboot. And you should also be able to attach the phone when it's already in Fastboot mode. The latter methods don't work on both my systems under Win10. When my desktop pc had been upgraded to 8.1, i performed all servicing of the L9 with my netbook, which was still on Seven.
My last unbrick was months ago, and i don' t know what happens at 50%. It's something important, and knowing it may help to understand the nature of the problem(loss of contact between phone and pc before the actual process starts, errors during flashing...).
It could be like this:
-phone seems to get recognized by driver&tool, that is good
-image gets downloaded(only with the official tool)
-image gets temporarily extracted on the pc(both online and offline). I fear that by completing the extraction the 50% mark is reached, and that no actual writes to the phone can be performed.
And LG's stock recovery, which calls itself "service mode" or "s/w mode" can be mistaken for D/L mode. I'm talking about the D/L mode, which is also present with a custom recovery, but theoretically D/L mode, S/W mode and Fastboot could be used for unbricking
lecorbusier said:
We'd need someone with a p778g. The problem may be be caused by the special branding of the phone, or an encrypted bootloader. Or the internal flash got completely cleared, partitions and baseband rom, which means a full brick. Otherwise flashing stock in D/L mode should work, even if anything else fails. But this goes mainly for LGs official tool working online. With the LG Flash Tool 2014 i had also problems.
I think both tools have to ways to perform the unbricking. Either with the phone put in D/L mode by the user (if Fastboot don't work on the PC), or by recognizing the phone (but with a still running system) via ADB, then auto-switching to Fastboot. And you should also be able to attach the phone when it's already in Fastboot mode. The latter methods don't work on both my systems under Win10. When my desktop pc had been upgraded to 8.1, i performed all servicing of the L9 with my netbook, which was still on Seven.
My last unbrick was months ago, and i don' t know what happens at 50%. It's something important, and knowing it may help to understand the nature of the problem(loss of contact between phone and pc before the actual process starts, errors during flashing...).
It could be like this:
-phone seems to get recognized by driver&tool, that is good
-image gets downloaded(only with the official tool)
-image gets temporarily extracted on the pc(both online and offline). I fear that by completing the extraction the 50% mark is reached, and that no actual writes to the phone can be performed.
And LG's stock recovery, which calls itself "service mode" or "s/w mode" can be mistaken for D/L mode. I'm talking about the D/L mode, which is also present with a custom recovery, but theoretically D/L mode, S/W mode and Fastboot could be used for unbricking
Click to expand...
Click to collapse
If i was you:
1) Enter in bootload mode using LELUS Method
2) Flash a TWRP 3.0.2 recovery
3) In TWRP recovery format all partitions
4) Install a custom rom
5) Enjoy
Initially I tried to root the P9000 following this guide (http://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042), and it seems to have bricked my phone. I got this error, (BROM ERROR-1073676724), and now my phone won't boot, or boot into recovery mode. The PC only sees it if I plug it in and press the recovery buttons (Vol+ and power), and then it'll flash up for a short time before vanishing. I've found the only way to keep it visible in the device manager is to use the flashtool to attempt to flash something to it, but I get this error (BROM ERROR -1073414139). I've tried this on a Windows 10 and a Windows 7 PC with no dice on either. Any help would be much appreciated.
holygoatofsteel said:
Initially I tried to root the P9000 following this guide (http://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042), and it seems to have bricked my phone. I got this error, (BROM ERROR-1073676724), and now my phone won't boot, or boot into recovery mode. The PC only sees it if I plug it in and press the recovery buttons (Vol+ and power), and then it'll flash up for a short time before vanishing. I've found the only way to keep it visible in the device manager is to use the flashtool to attempt to flash something to it, but I get this error (BROM ERROR -1073414139). I've tried this on a Windows 10 and a Windows 7 PC with no dice on either. Any help would be much appreciated.
Click to expand...
Click to collapse
Fixed it, but I'll leave this up for anyone thinking they might have the same problem. I fixed this by flashing the stock ROM again, but with one key difference. Ensure you install all appropriate drivers, and then when you hit download, plug the phone in and attempt to put it into recovery mode. This will open the port just long enough for the flash tool to keep it open, and it will flash as usual.