This tutorial is for people who have bricked their phone due to messing about with important files/partitions on their Nitro HD and found that it won't boot up afterward. Prior to attempting this, see if you can access your phone while booting with adb in order to fix your problem. The method used in this tutorial should only be used as a last resort. Don't hold me responsible if this method somehow makes your problem worse (although, really, how much worse can it get than a phone that won't boot?).
Now that's out of the way, let's move on...
Things you'll need:
1) ADB: You can get this in the Android Developer SDK <-Once installed, install platform-tools and add the directory containing ADB to your PATH. Alternately, you can just grab the ADB folder from your SuperOneClick folder, copy it to C:/, and then add that directory to your PATH. Hell, you could even run all the commands from wherever you have the ADB folder, just make sure you have it.
2) LG P930 drivers: http://s3.amazonaws.com/lgforum.com/...nal/LGP930.zip
3) LG Mobile Software Update Tool: http://csmg.lgmobile.com:9002/client...2CAppSetup.exe
4) UpTestEX_mod2_marwin/KDZ_FW_UPD_EN: http://www.filesonic.com/file/225575..._FW_UPD_EN.zip
5) LG SU-640 firmware V10F_00.kdz: http://www.megaupload.com/?d=31XABWWJ
6) A method of rooting your phone. My preferred method is the latest SuperOneClick due to its simplicity. I won't really cover how to root your phone in this tutorial as it's covered elsewhere.
The following should only need to be downloaded if you were stupid like me and bricked your device before you made backups of the necessary partitions (This will be explained elsewhere, but needless to say it's as simple as switching the "if=" argument and "of=" argument in the dd commands toward the bottom):
7) boot.img: http://fileape.com/dl/OCowIxMnbDUMiPW6
8) recovery.img: http://fileape.com/dl/jFMlB8I3kkSMOYWN
9) firmware.img: http://fileape.com/dl/4gHHDDUhODLiJGHM
10) baseband.img: http://fileape.com/dl/TMsvdaKOa7VG4mVT
11) system.img: http://depositfiles.com/files/f0ke241ew
Alright, now that you have everything you need, let's move on to fixing your phone. I'm going to assume you are competent enough to install ADB (Android SDK or folder included to with SuperOneClick) to your system PATH. Go ahead and install the LG Mobile Software Tool and then install the drivers for LG P930 if you haven't already. Extract the KDZ_FW_EN.zip file. Note, in my case, I didn't have to do anything with the mfc42.dll or run WindowsEnabler as mentioned in similar tutorials elsewhere, but your mileage may vary.
Flashing the SU-640 rom:
1) Put your phone in download mode: power off the phone if it's not already, unplug the usb charging cable, and simultaneously hold the volume up button and plug the usb charging cable back in.
2) Open up UpTestEX_mod2_marwin. (If you know what you're doing, I've been told you can use KDZ_FW_UPD_EN as well, but since I didn't use it, I'm not going to discuss it)
3) Hit the folder icon next to the "Select kdz file" line and browse to the SU-640 v10f_00.kdz
4) Select "CSE web upgrade test", a new window with some options including an "Upgrade Start" button should appear.
5) Take a deep breath...there's no going back :) Press "Upgrade Start".
6) At this point in time another dialog box will appear asking what country and language the LG Mobile Upgrade tool should use. Since this guide is written in English, I assume you'll want to change it from Republic of Korea to All other countries and Korean to English. This affects the language that output messages are displayed in in the LG Update tool only, it doesn't affect anything with the rom (that'll be all Korean on initial startup lol).
7) The update tool will proceed to flash your phone, but it should never complete "normally" (mine never made it past 4% according to the tool and other users have reported similar behavior). However, your phone should reboot once or a couple of times and then just be sitting idle waiting for you to go through the setup wizard. At this point, just kill the LG update tool process in task manager, don't wait for it to complete because it won't.
Rooting your phone:
1) Now, on your phone you should see the standard Android startup wizard...in Korean. Hit the left button confirming you want to go through it, and on the next screen should be an option to switch the language to English. Ah, much better.
2) Go through the rest of the setup wizard if you want, but it's not necessary and you won't be able to set up accounts anyway unless you somehow have wifi.
3) Put the phone in USB debug mode and allow 3rd party sources. Don't freak out if the phone spontaneously reboots when you do this. It rebooted on me every single time I put it into debug mode for the first time (I flashed it several times lol).
4) Once it's rebooted itself, you should be able to connect in debug mode and connect via PC mode. Go ahead and root it using your preferred method. We're almost there!
Restoring Nitro HD partition images:
1) Open up a command prompt and navigate to the folder you saved your recovery images to (hopefully you put them in the same folder, it'll make your job easier)
2) Push all the image files to the phone's sdcard using the command:
adb push filename.img /sdcard
3) Now the real fun begins! Use the following commands:
adb shell su dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8 dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13 dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1 dd if=/sdcard/system.img of=/dev/block/mmcblk0p27 dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
5) Hit power twice and your phone should go through its reset process and (hopefully!) come back up in a working (and rooted) AT&T "stock" rom
If you have any issues, it's possible I've forgotten some steps, so I'll address them in this thread. At this point, I'd like to thank specific people who helped me immensely getting a working phone again: bytecode64, gordec, schwin97, belth219, sukudos, and ziiljuks. (If I've missed you, I'm sorry, I'm thankful to this entire forum!)
So I was messing with fonts (actually trying to get the "look of disapproval" from Reddit to display) and substituted DroidSansFallback with a kannada font using Font Installer *Root*. Well, long story short, it was causing issues with other non-english characters so I tried to restore *all* my fonts using the "stock" option that comes with Font Installer.
When I rebooted, my phone only got to the LG Screen and that's as far as it has gotten since. I can't do anything with it, but I can get to Factory Data Reset mode and Download mode. I tried plugging the phone into my computer, but it doesn't appear to get far enough to mount the disk. Odin recognizes it's attached when I put it in download mode, but obviously Odin doesn't work with our phones.
Does anyone know if there will ever be hope for my phone or should I pursue getting a replacement? I'm actually completely shocked that simply replacing fonts has bricked my phone to the point where it doesn't even boot. This has seriously made me reconsider tinkering with Android at all until recovery methods are possible. I'm more than willing to be a guinea pig at this point until I try to send it in for a replacement (within the next few days probably).