officer623
Well-Known Member
if i can get you the firmware from this phone can you extract what you need?
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
if i can get you the firmware from this phone can you extract what you need?
I have the firmware, but LG decided to make it in tot format instead of bin format....
they did the same with the lg connect maybe you can use the method they did with the connect.
post what you need me to do and i'll test
http://forum.xda-developers.com/showthread.php?t=1512203
Follow the instructions from this thread above, BUT make sure you use the CWM image shabby made for THIS phone. Also, you do not need UDK nor the recovery from that phone.
Where it says this:
1. Run KDZ Updater from UPK with Windows Enabler on.
Select your KDZ file.
Just replace that with following my unbrick guide, but stop at step 14.
Then follow the directions from the xda thread.
In step 8 from the xda thread, make sure you copy the address correctly!!! If you don't then you WILL be hard bricked.
Because of the differences between the Optimus Black and the LG Motion, I really do think mrpnut should try this since he has an extra phone...

can a hard brick be fixed with the unbrick guide?
cant the phone be emulated on a pc.
To emulate a ROM yes, to emulate the actual phone to go through this process, no.
what are the chances of this working do you think?
i have the replacement plan $10.70 for a refurb from metro if i tell them it jut happened haha

what are the chances of this working do you think?
There are 5 things that could happen:
1) You do everything successfully and it boots correctly and CWM actually works (I feel like this would be a miracle...)
2) You don't copy and paste the number correctly causing a perma-brick (hard-brick)
3) You do everything correctly and it boots correctly, but trying to load recovery gets you fastboot (that wouldn't be bad at all)
4) You do everything correctly, bootloader finds the replaced recovery right away and gives you a soft-brick.
5) You do everything correctly and it perma-bricks. (I wouldn't know if this was a problem with Shabby's recovery or if it would always perma-brick.)
I'll go with number 4
There are 5 things that could happen:
1) You do everything successfully and it boots correctly and CWM actually works (I feel like this would be a miracle...)
2) You don't copy and paste the number correctly causing a perma-brick (hard-brick)
3) You do everything correctly and it boots correctly, but trying to load recovery gets you fastboot (that wouldn't be bad at all)
4) You do everything correctly, bootloader finds the replaced recovery right away and gives you a soft-brick.
5) You do everything correctly and it perma-bricks. (I wouldn't know if this was a problem with Shabby's recovery or if it would always perma-brick.)