"Bootloader download failed"
I had hoped I wouldn't need to ask for help on this one. I've been trying to repair my Made in Korea P990 now for a couple of days, but none of the information I found is working.
The situation:
- About one week ago, I flashed the V28G_00 leak from LG to my P990. I unpacked the kdz and installed
the AP bin and CP fls files using Smartflash and allowed it to repartition my phone. The ROM worked well
for about one week, then started running extremely hot and I experienced a lot of battery consumption.
- So I did a "factory reset." Oops.
- Following a factory reset, I got stuck in the LG boot logo that several people have mentioned in this forum.
I also couldn't enter the "S/W Upgrade" screen, as the phone didn't react at all to the volume-down and USB
cable song and dance.
- No worries, I figured; I'll just nvflash a new bootloader. So I came to this thread (and found other threads
and followed those as well)
- I have been utterly unable to flash a new bootloader. Every NVflash download out there reports the same thing:
NvError 0x30012 when trying to downlad the new bootloader.
Except once. One one single occasion, using this repair tool from ProgMaq, the entire process seemingly worked. The flash batch script ran from start to end, I got a "S/W Upgrade" screen on the phone while still connected to the computer (in Korean, but I figured I could live with that), and allowed the phone to disconnect itself from the computer (waited for USB disconnect sound) before unplugging it. However, the phone is now stuck in a white LG logo boot loop instead of the pink logo that came with the ICS upgrade.
To sum up: can't get past the LG boot logo. I can enter APX mode just fine. I can't enter ADB mode, for obvious reasons. Every flavor of NVflash fails to install a bootloader. Output from ProgMaq repairer:
ProgMaq LG Optimus 2X (P990) repairer
========================================
* Remove the battery.
* Simultaneously press Vol+ and Vol- and connect the microUSB cable to device.
* Wait 5 seconds and stop pressing Vol+ and Vol-.
Press any key to continue . . .
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x02884182411fe3d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: 0-bct-settings.bct
- 4080/4080 bytes sent
0-bct-settings.bct sent successfully
failed executing command 6 NvError 0x30012
odm data failure NvError 0x0
command failure: bootloader download failed
Flashing completed!
Unplug the USB cable, insert the battery and turn on the device.
Enjoy!
Output from Russ' NVFlash Recovery Flasher:
-------------------------------
Russ' NVFlash Recovery Flasher
1. CWM 4.0.1.5 Internal
2. CWM 4.0.1.5 External
X. Exit
-------------------------------
Please pick a recovery, or exit [1,2,X]?1
Attempting to flash internal recovery...
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x02884182411fe3d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
data send failed NvError 0x30012
command failure: bootloader download failed
-------------------------------
Program will now exit
I also tried initializing the partition layouts and restoring the ICS partitions using the nvflash toolkit for ICS. Every option failed with the same result: failed executing command 6 NvError 0x30012, odm data failure NvError 0x0, command failure: bootloader download failed. Same thing with nvflash-cleaner v0.2.
I'm at a loss here and hoping somebody will try to assist me.
EDIT: Forgot to mention that I've tried different USB ports and also uninstalled the APX driver completely (removed files from computer option) several times, to no avail. I am running Windows 7 x64, which of course *could* have something to do with it...
EDIT 2: This turned out to be a hardware issue. Phone has now been serviced and replaced with a refurbished one.
Svein