[Android Q&A, Help & Troubleshooting] toxinburn:
Okay so this is actually fairly simple for once, I will cut out all the useless info and only post the stuff relative to the optimus fuel..if you have softbricked your device or maybe your not sure yet, first things first you need to plug it up to the pc in windows it will mount the phone like it would a thumbdrive, instead of showing the phone name under my computer it will now show it as a drive open that up and you will see two folders image and verinfo, if that is the case then you are ready to attempt to un-softbrick it.

The second thing you are going to have to have is a copy of linux installed, I use a dual boot of mint and win 8.1, I tried this on a virtual machine as well and it did not list things properly..so I cannot say whether a vm will work for sure.

So boot into your linux os on pc and plug the phone to usb to pc.

Now open up console

type in ls /dev/sd* -----press enter

This will show you a big list of partitions, whichever partition you see with the highest number for instance sdf32 then take note of it as it is where your device is being detected.

now with the result of the last command you typed from console enter gdisk -l /dev/sdf <----i am using sdf because that is what mine listed, i assume it will be the same, let me know if for some reason it is not, but would probably work anyway press enter and you will get a big list of the partitions, with numbers associated with them it will look something like this below

Number Start (sector) End (sector) Size Code Name

6 229376 231423 1024.0 KiB FFFF aboot

but with many more numbers listed pay attention to those numbers, especiallly to the ones associated with the .img you may have altered to brick your phone in the first place, because you will be wanting to replace those .img with the originals.

So....if you have messed up any of those partition images listed for instance the aboot is listed under sdf6 in the above example then you first need to be root in the console by typing sudo -i and enter your admin pw press enter to run console as root.

now lets fix out aboot with none other than dd commands in the console you enter

dd if=/path/toyour/aboot.img of=/dev/sdf6 and then press enter and it should push the image back.

Once you have pushed all the images back that you need/want then simply hold power button down til the phone reboots and hopefully you see the logo again, i have recovered my own from messing with aboot twice, as far as the other partitions I cannot say as I have not messed with them much, i can say that abootb modifying it does not softbrick or do anything that i can tell, unless i type adb reboot recovery after changing it i get a security error instead of the regular booting right into the os.

so just make sure to use sdf6 instead of most of the time you would use of=/dev/block/platform/msm_sdcc.1/aboot but since it is in bulk mode it changes to /dev/sdf6 and the gdisk -l /dev/sdf will give you the list of them all so you will know which # the img should be associated with hope that helps someone out there, I used the following post to figure all this out on my own for this device, i used all that info just simply modified it to fit my own needs, so if any thanks is given give it there.

Once y

http://xdaforums.com/showthread.php?t=2582142

---------- Post added at 03:34 PM ---------- Previous post was at 03:26 PM ----------

Also i found a post that tells you how to get into stock recovery if that helps or not i dunno, but it does work.

the first is a way to run it in a script i had probs with it.

#!/system/bin/sh

cd /cache/recovery

echo "--show_text" >> command

chmod 644 command

reboot recovery

Now This is what I used thru adb and it works, however it doesnt stick for next time i have to enter this again just to get into stock recovery.

adb shell
su
cd /cache/recovery
echo "--show_text" >> command
chmod 644 command
reboot recovery

this info came from androidarea51.com/lg-ortimus-fuel-lgl-l-35c/all-things-fuel/58/