Hey, so I've looked through these forums, as well as google search, with every combination of words i could think of to address my issue, and so far nothing has worked. So im posting here, hoping y'all can help me.
My phone is the Lg optimus L9 p769 running FW v20h. I had it rooted, bootstrapped cwm recovery is installed and still accessible. Unfortunately for me, i had disabled usb debugging off. Cant remember why, but I did.
I was browsing around for build.prop tweaks, found a good list, and implemented a few. After reboot, everything was going smoothly, hell, faster and smoother than before, which i assume came from tweaking the build.prop. At that point, i chose to implement 1 more and be done. So i added the line and rebooted my phone. SOFT BRICK!!!!!
Now, as i said, ive done quite a bit of searching for a fix, including the offline fix and basic LG Support Tool restoration, but nothing is working. Offline fix says my phone is not connected. Online recovery says im already at the most recent FW available. Ive tried fastboot, but installing the u boot and x loader wont work. CMD doesnt recognize my phone when i try anything adb related (obviously, because usb debugging isnt enabled), nor does it recognize my phone as a fastboot device even with the phone displaying the mirrored logo and says fastboot v0.5 in the top right corner. Also, the bootstrap CWM wont mount my external SD, which has my build.prop backup on it.
So, basically, that what I've read into. A wall, so to speak. As a side note, my wife has the same phone with an unmodified build.prop. in fact, the only thing that i have done to hers is root it with the LGpwn app.
Now, is there anything i can do with this, other than throwing it against the pavement outside? While i think I'd get a sick satisfaction from that, it hardly solves my problem. Also, i called LG directly, but they won't help me at all without payment. Even with their CS rep saying it was their fault (because, of course, I'm not dumb enough to tell them I broke it by messing with the build.prop). However, the slight bit they did do remotely through the laptop had them going through the LG Service Tool.
Anyway, that's about it. It really is a great phone and i really would like to repair, rather than replace, it, but im stuck. Anyone got any ideas?
Hello,
I had a similar problem, offline method didnt worked for me saying that my device is not connected. Then I faund this tool on forum http://forum.xda-developers.com/showthread.php?t=2797190
Use it with described tutorial (use 3GQCT and DIAG) and you are going to unbrick your phone.
Ok, I'll give it a try when i have access to the neighbors laptop again. I'll post the results here. Fingers crossed, my phone is up and running again soon and I'll be able to post my results from my unbricked phone.
IT WORKED!!!!!
Holy hell, it worked! A week of searching and trying with no success, now my phone is up and running again! Thank you sooooooooooooo much! Can i get a solved tag?
You're welcome. I'm glad I could help
Related
So I rooted my sister's optimus v about a month ago. Today she installed a battery mod app from applanet and as soon as she chose which battery mod she wanted she had to restart her phone for the changes to be applied, but when rebooting the phone it would only get stuck in reboot. So I tried to start it up in recovery and got the blue screen that says fastboot mode started. I looked that up online and found a fix to it but I need it to go into emergency mode to fix it that way and it will not go into emergency mode, any combination of keys only takes it to either the blue screen with the fastboot mode message or it just reboots and gets stuck. So now what do I do? I really need to find a way to fix her phone. Thanks in advance to anyone who tries to help.
try to turn on the phone & use LGMobile update tool. That should recognise the phone & install original lg fw
tabs648 said:
So I rooted my sister's optimus v about a month ago. Today she installed a battery mod app from applanet and as soon as she chose which battery mod she wanted she had to restart her phone for the changes to be applied, but when rebooting the phone it would only get stuck in reboot. So I tried to start it up in recovery and got the blue screen that says fastboot mode started. I looked that up online and found a fix to it but I need it to go into emergency mode to fix it that way and it will not go into emergency mode, any combination of keys only takes it to either the blue screen with the fastboot mode message or it just reboots and gets stuck. So now what do I do? I really need to find a way to fix her phone. Thanks in advance to anyone who tries to help.
Click to expand...
Click to collapse
give a try to error guides over here http://forum.xda-developers.com/showthread.php?t=883314 it has done wonders for many flash in cs emergency mode from the flasher menu. Read detail guide in the link provided.
I am not sure if it works for optimus v but it does works for optimus 1. give it at try
I managed to finally get the phone into emergency mode. I had installed the LG mobile support tool and installed all the drivers and tried to go that route but it kept telling me I only had one of four drivers installed, even though I have installed several drivers. After all of that I had finally got it into emergency mode so I went back to trying KDZ. I'm supposed to select the rom where it asks for the KDZ file right? But when I go to browse for the rom file it doesn't show up in the folder I put it in. I've rooted 4 phones and have done so many other things with them and never bricked one, was always able to figure out everything I did and never had to ask any questions but I can't figure this out to save my life and it is driving me crazy. I do really appreciate you guys for the suggestions and thanks to your suggestions I have gotten this far.
Hey, I have the same problem. I rooted my phone then I installed that battery mod app on applanet. I installed it then when I had to restart my phone for it to apply it just got stuck and kept looping the reboot screen where it says "ANDROID". Did you get ur fixed yet?
tabs648 said:
I managed to finally get the phone into emergency mode. I had installed the LG mobile support tool and installed all the drivers and tried to go that route but it kept telling me I only had one of four drivers installed, even though I have installed several drivers. After all of that I had finally got it into emergency mode so I went back to trying KDZ. I'm supposed to select the rom where it asks for the KDZ file right? But when I go to browse for the rom file it doesn't show up in the folder I put it in. I've rooted 4 phones and have done so many other things with them and never bricked one, was always able to figure out everything I did and never had to ask any questions but I can't figure this out to save my life and it is driving me crazy. I do really appreciate you guys for the suggestions and thanks to your suggestions I have gotten this far.
Click to expand...
Click to collapse
I'm having the same issue right now, although at least you have managed to get it into emergency mode. How did you do it?
The other issue I'm seeing is that there is no .kdz for the Optimus V LGVM670. I found a .cab file that is supposed to be the newest update, but not even sure that will work with the the kdz manager.
It was my sister's phone and I had the same problem with kdz. Had the cab file so couldn't use it with kdz. My sister left her phone with me for a few days to try to fix it and when I couldn't she took it home and managed to fully brick it to where it would do nothing at all so she had to get a new phone. I got it into emergency mode by holding down the volume and it was either the back button or the home button I pushed at the same time, can't remember which. As I held those down I plugged in the USB cord that was connected to my laptop and it went right into emergency mode. Just make sure you disable that LG modem in the device manager on the computer before doing anything because my sister forgot to do that and that is how she fully bricked her phone. Good luck to you guys and if anyone figures out how to fix it I would be interested in knowing how you did it.
tabs648 said:
It was my sister's phone and I had the same problem with kdz. Had the cab file so couldn't use it with kdz. My sister left her phone with me for a few days to try to fix it and when I couldn't she took it home and managed to fully brick it to where it would do nothing at all so she had to get a new phone. I got it into emergency mode by holding down the volume and it was either the back button or the home button I pushed at the same time, can't remember which. As I held those down I plugged in the USB cord that was connected to my laptop and it went right into emergency mode. Just make sure you disable that LG modem in the device manager on the computer before doing anything because my sister forgot to do that and that is how she fully bricked her phone. Good luck to you guys and if anyone figures out how to fix it I would be interested in knowing how you did it.
Click to expand...
Click to collapse
hmmmmm, I don't remember completely how I did it, but there was a very helpful guide floating around XDA. I bricked my Mom's Optimus one as well . I actually had to go to the LG support site, type in my Phone serial number and find a list of all the firmware available. From there I right clicked the page and got the page source. From there I got my firmware and I entered it in the KAZ or LG B2I Agent ? - Dont quite remember. Anyways, it ended up working out for me, but I accidentally flashed the German firmware, but in the end, everything was all good LOOL.
I have yet to find an answer to this while searching for the past day, so I'm going to ask about it here.
My LG Optimus V's (just got it a few days ago as a birthday present) screen seems to be permanently blank... In case someone asks... yes, it is activated.
What Happened:
I rooted the phone using Gingerbreak 1.2, installed rom manager/clockwork recovery mod, then attempted to backup my phone in case something went wrong. However, when I started the backup, I noticed that the screen was completely blank. I was kinda freaking out, so I just took a shower while it did it's thing. When I came back, it was done creating the backup and it showed up in Rom Manager. After toying with some of the things I can do with it rooted (I only rooted it to see how much of a difference it would make without changing the kernel), I decided to recover that backup. When my phone restarted to recover the backup, the screen was blank once again. After waiting for over an hour, I concluded that it must have finished (since my HTC Hero would finish restoring and never reboot until I tell it to) and took out the battery. Afterwards, it would show the LG splash screen... then the blank screen.
What I Did:
I was thinking about the android screencast java application a few hours after my problem first developed. I plugged my phone into my computer, got adb working, and android screencast showed me that my phone was actually getting stuck at the clockwork recovery mod screen. I tried many things... I installed a CM7 rom, flashed 3 different recoveries, flashed an overclocked stock rom, etc. Eventually, I flashed the stock rom (no changes whatsoever) and stock recovery. Now I can hear my phone, but cannot see it. However, I should note that while using CM7 the same thing happened. The only difference being that I could use android screencast to see the screen (the phone was actually working) with CM7. Now with the stock rom, adb is disabled and I cannot see the screen or do... anything.
What I Think I Should Do:
I'm thinking about calling Virgin Mobile and telling them that my screen is defected. If they see the issue they'll probably think that it's a hardware issue (for all I know, it could be) and they'll probably give me a replacement. However, if anyone as had the same problem and fixed it, I would love to know.
I would love you hear your opinion on this and, if possible, a fix. Thanks in advance!
(JIC, if I posed in the wrong section, I'm sorry...)
you poor souls reporting the symptoms of getting the newer screen hardware from the optimus s in your v's don't number in the double digits yet, but it's getting closer.
I posted a fix on AndroidCentral, see it:
here
good luck! the fix has worked for everyone I pointed to it so far.
btw, the screencast idea is excellent!
crud. stock recovery, you may be SOL.
you'll probably have to boot into custom recovery to use screencast or adb now.
use the unplug phone -> pull&replace battery -> hold home+volume down -> keep holding, press and hold power until lg screen goes blank to enter recovery. maybe adb will work in stock recovery, I dunno.
Thank you very much for the reply!
Yeah, you're right, I'm probably SOL... I still have one option though! Theoretically, I should be able to turn on ADB without being able to see my screen. I know how to access the settings without seeing it, but navigating myself to the "Applications", "Development", "USB Debugging" may be a little hard. I will attempt to do so. I will report my progress in a bit.
However, if you (or somebody else) could provide screenshots of a step-by-step process to turn on USB Debugging in the stock rom (since it's kinda hard to do remember where everything is and screenshots of different phones is kinda different) then I would appreciate it VERY much!
I shall update this in an hour or so.
UPDATE (9/2/11 - 9 PM):
I'm going to take a break for now. Good thing I give everyone my Google Voice number, I doubt anyone will notice a change. I'm going to flash a stock rom onto my HTC Hero so I can figure out where things are on the LG Optimus V (Same screen size) in an hour or so. I'll update my progress in like 2 hours.
UPDATE (9/3/11 - 8:10 AM):
I have been unable to turn on USB Debugging and it seems to be because I don't know where the confirmation after turning it on is located. However, I should note that when I boot into (I think) recovery, "adb devices" states that the device is attached but offline. If there is a way to make it "online" from stock recovery then I would love to know. For now, I will try everything I can.
UPDATE (9/3/11 - 8:22 AM):
Ok. I plugged my phone into the back of my computer and now when I do "adb devices" it detects the device in recovery mode. However, when I try "adb shell" it says "- exec '/system/bin/sh' failed: No such file or directory <2> -". I'll try some more stuff, but does anyone have any idea of what I can do? Android Screencast doesn't work either, so that's not an option.
UPDATE (9/3/11 - 9:42 AM):
Crap... now it's indefinatly booting into recovery... I had something like this happen before, I'll report my status in an hour or so...
UPDATE (9/3/11 - 12:36 PM):
My friend finally got my phone booting out of recovery again! Now all I have to do is get "USB Debugging" on and it SHOULD work!
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
glad you got back into recovery again, not too sure how to help at this stage though, since I can't find a way to get into the bootloader with a power-on key combo. just emergency mode (useless to the V since the firmware from LG is missing a file) and safe mode. boo.
there is a youtube video for enabling usb debugging on the v, maybe it'll help you find the right spots to press.
http://www.youtube.com/watch?v=nHal0hPNS6s
edit: you can also try to reboot into the bootloader with adb, even though it's missing the shell... it's worth a try, and if it works you can flash xionia recovery with fastboot and things would be a lot easier from that point.
Code:
adb reboot bootloader
if that works but you need more help, a battery pull is the only way to power off with the bootloader except "fastboot reboot" will try to boot your rom.
Awesome, thanks for the replies! I'm going to try your suggestions now. I'll let you know how things work out in a few hours. I would have replied earlier, but to my satisfaction there was a surprise party planned for me, lol. I will defiantly try these out now.
Once again, thank you very much. I honestly did not expect a reply for something that happens to such few people.
bigsupersquid said:
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
Click to expand...
Click to collapse
I'm honestly not sure what my friend did, lol. She was just messing with it while it was, apparently, in recovery and it ended up rebooting and loading the rom. I, honestly, don't want to risk getting stuck in recovery anymore since taking out the battery for an hour didn't do anything... If I'm unable to get adb on using what I know from that video then I'll try booting into the bootloader. Like I said before, I'll report my status in a few hours. I really appreciate your help up to now!
EXTREMELY HAPPY UPDATE!!! (9/4/11 - 1:22 AM)
I was able to turn on ADB! I used what I learned from that video and how turning on ADB works on my HTC Hero to get it working and it's FINALLY ON! Now I can attempt to flash the recovery, kernel, and everything else in order to get it working! Thank you VERY much! I will let you know how everything turn out
Another Wonderful Update! (9/4/11 - 2:03 AM)
I have flashed the recovery.img (the Xionia CWMA one) and can see my screen in recovery! I haven't seen anything on my screen besides the LG splash screen so I'm overwhelmed with joy! I'm flashing a new ROM and the other stuff now!
Final Update! (9/4/11 - 2:09 AM)
2:05 AM - I see the rom's boot screen!
2:06 AM - I see the CM7 Mod boot screen!
2:08 AM - I see the UI on my screen and everything seems to be working! Thank you VERY much!
Quick question though... If I want to install a new ROM, do I need to flash the xionia anykernel one directly afterwards?
ah, excellent! glad it's working now.
you're the most persistent (and maybe technically apt) person I've helped with this so far.
I still think that using screencast was the best new idea I've seen yet.
yes, you'll need to flash the xionia kernel after flashing any rom or rom update.
roms come with their own kernel in the boot.img, and none of them currently out for the v have the video drivers from the newer sprint kernels.
right now, xionia kernel is the only thing that works.
and, you'll need to flash the key swap after changing roms, as well, but at least forgetting to do that won't take out your display.
now that you've got xionia recovery on your phone, it should be a lot easier next time.
Thank you for both the help and the compliment!
I don't like giving up when it's something I know I can do. I figured that if I was able to mount my SD card without being able to see the screen, I should be able to turn on USB Debugging as well. About the Android Screencast... I didn't actually think about it until it until I plugged in my phone while the screen was blank, ran "adb devices", and saw that my device was detected within recovery. I figured that I might as well give it a shot... and it worked.
Alright, that's what I figured. Hopefully someone realizes what's happening with refurbished Optimus V smartphones and ports the newer sprint kernels to the Optimus V. I feel like I got ripped-off though... I bought my phone "new" and got a refurbished one. I can't really do anything though, we're not technically supposed to be rooting our Virgin Mobile phones anyways, lol. I'll be sure to do that everytime now though. For now, I think I'm good with the Bumblebee rom.
Once again, thank you VERY much for your help! I know I would not have been able to fix my phone without your help.
EDIT:
Oh yeah, btw, if the Optimus V ever gets stuck in stock recovery, press the "back" button then "home" button to boot into the rom. Not sure why it works (I was never able to see the screen), but it worked.
There is a key combo!
First time caller long time listener... I bricked my own Optmus V with a bogus ROM. To boot into recovery without adb press (Home)+(Volume Down)+(Power) Now rocking CM7!
was using zedomax's root method and got a bunch of errors "too many devices, more than 1 emulator" and now it won't finish booting. Gets just to the point where the unlock ring should come up and then nothing...
I can pull down the status bar and thats about it ...please help. I have the insurance, but will they be able to see that i started rooting it...
I would try to install the RUU to get it back.
It's probably not Bricked.
You can also check out the more full unlocking procedure http://forum.xda-developers.com/showthread.php?t=1690919
I believe one or both these procedures could be started while in the bootloader.
I'd try the RUU first though.
Look in the Sticky thread in Dev for the RUU (an EXE you run on the PC).
greek goddess said:
was using zedomax's root method and got a bunch of errors "too many devices, more than 1 emulator" and now it won't finish booting. Gets just to the point where the unlock ring should come up and then nothing...
I can pull down the status bar and thats about it ...please help. I have the insurance, but will they be able to see that i started rooting it...
Click to expand...
Click to collapse
This happened to me as well. Then i realized i have both my old Epic4g AND my new EVOLTE plugged into my computer. I unplugged my epic and voila. it worked just fine. If it still doesnt work, try restarting your PC and redo the process.
Thanks guys for your answers. problem is resolved, but I will what happened in case anyone else has this problem.
I couldn't get the drivers to install on my laptop so I went to the desktop and ran the root. The error messages I got were like this: after the second reboot (supposed to reboot 3 times) it would say "device offline" and it filled the whole screen with that line. Then it said "error too many emulators" and then it would say it was done and that is as far as it would go. It did not boot a third time. I could reboot it, but it would only get as far as the screen JUST before the unlok ring comes up, and that's it.
After posting this thread I read another thread where someone suggested holding the volume down and power to bring up stock recovery and doing a factory reset from there (rookie mistake, I have had the Epic Touch for a while and forgot about the Evo's stock recovery). That got me back. THANK GOD! But still no root.
I didn't want to give up trying to I went back to my laptop and still without necessarily "installing" the drivers, went ahead and tried running the root and VIOLA! It worked flawlessly!
So I don't understand what was going on with the desktop though with the "device offline" and "too many emulators" thing, so if anyone could shed some light on that, I would appreciate it.
glad to hear you got it fixed but if you would have had to filed a claim then you can always say you lost it or something like that.
can you please help me with a soft unbricking of my lg g vista (vs880 [11b]) from verizon usa? i found the 880-11b firmware file, at least i think its the right one. if you know of/ come across this and are sure of its validity i would trust that more. i found and downloaded via a google search. i initially think i may have accidentally deleted the splash pic for the carrier when it boots. this caused it to just black screen after the lg logo n the backlight would flash like it was stuck in a boot loop just the image file was missing. after a little more research i figured out how to put it in the download mode so that i can use a pc to try repair or reinstall whatever it needs. i am unsure if i need the sdk or adk toolkits for a repair in the download mode to work. while on that screen it says its plugged in and waiting to download firmware via usb under the progress bar it tells me not to unplug until download is completed. its not showing up in "my computer" however. and i've never had to do s software/firmware download or setup when the phone wasn't in full normal working order. i simply want to put back the out of the box software back in place. firmware 88011b and 4.4.2 os. just want to be sure i get the proper files/and or programs/ directions to use those resources properly the last thing i want is to guess at something that i could ask someone more experienced for help with and end up bricking it beyond repair. any and all help is very appreciated and i must ask you to please explain each step as clearly and "dumbed down" as possible as you can. if i need to use a program i've never used before {i.e. i hear things like odin mentioned in the forums but i don't understand or have any experience with any pc to phone applications so the more detailed any instructions can be made the better. anything that most ppl who have started tinkering with their devices usually know as common sense or steps that seem implied if not specifically mentioned i'll miss. i have been reading n lurking for months n managed to root the device. but had another issue i accidentally caused soon after which resulted in a factory wipe and some time to remember what i did that rooted it after spending a day on it the first time n trying many things it took me a while to refind what i had done that worked. then this happened. i'm sure with the proper files/tools it'll be fine but i need help to know what those are and to be sure i do it right the first time. i know if i don't there may not be a second chance. thank you again in advance for your patience and help.
Well, I just got this phone this week. It was actually a gift in fact since I broke my last phone a week before this.
As soon as I got used to the new phone. I started playing with it's guts. I rooted it with Kingroot, since it has never failed me before. Installed Xposed Framework, and flashed the 5.1.1 stuff for it to run. I had to flash TWRP to flash the Xposed Framework stuff (for some reason I couldn't get the sideload to work). Got a few modules for it. Got all my usual apps such as Facebook, ES FM, Instagram, etc. Got a few games. Spent some hours playing the games. You know, all the stuff you do when you get a new phone.
Then, I decided it was time to switch from Kingroot to SuperSU, as I do with every phone I root with Kingroot (and there were a few). I did it the same way as I have before, using w0lfdroid's method (I can't post links yet). The Kingroot app didn't automatically uninstall, but SuperSU was working. So, I uninstalled Kingroot manually with ES FM. That caused a lot of "unfortunately, com.kingroot.kinguser has stopped" dialogs that never stopped coming, and I decided a reboot might fix it.
I was wrong, the reboot did NOT fix it. It turns on, goes to the LG logo screen, goes to the Metro PCS screen, dims the background, [all of that within a minute and then] vibrates once, and then no sign of anything else. However, the phone does seem to be alive. When I plug it into USB the MTP starts working. It's also listed in adb's devices list. I can even use adb. I used adb to boot it into bootloader/fastboot, and it's even listed in fastboot's devices. It does still charge.
That damned Kingroot, I'll never use it again to shortcut through rooting. It has always worked, and I've been able to swap it with SuperSU everytime before this one. I just don't want to risk this happening again.
I'm lost on what I should do about this. What would you fella's do?
_____________________
I do have a warranty on it, but I've obviously voided that above. I could lock the bootloader back with fastboot (using "fastboot oem lock") so they don't see anything significant right away, but they could always dig in to see that I've done a lot of changing. Hell, all they would have to do is boot into recovery and see TWRP... xD
Well, I just locked it back ("fastboot oem lock" ) and I think my phone is actually coming back on, it's currently on the "Android is starting" screen optimizing app 12 of 151.
I'm just hoping the lock command doesn't reset my device like the unlock command obviously does... I guess I'll edit this with my results in like an hour when this is done (not literally an hour)!
EDIT 1: 10 minutes later, it seems to be stuck on "Starting apps." after it finished optimizing.
EDIT 2: 10 more minutes later, I'm pretty sure it was indeed frozen on "Starting apps.", so I took the battery out. I turned it back on only to see it still freezing on the Metro PCS screen... Well damn.
EDIT 3: Yet another 10 minutes later, still stuck on the Metro PCS screen...
EDIT 4: I no longer have USB debugging access, since I re locked the bootloader (which seems to have reset it, again). So now I also do not have access to fastboot. I think I screwed myself...
unbricking
@ goatitalone can help you unbrick your device. I still have the files if he is OK with it I can help you too or if he can write a tutorial on here that would be great. @ goatitalone?
I have same exact problem howisit fixed?
Magik1 said:
I have same exact problem howisit fixed?
Click to expand...
Click to collapse
do you still have adb? if you do i can send a twrp backup
its been listed kingroot will brick you, currently the oneclick is compatible with our devices. you should have done some searchign before tinkering with your device in my opinion, if youre smart enough to unlock your bootloader .. you should be smarter in researching root methods.
youll have to reflash your device, contact goitalone - as noone that he's helped will help you with getting those files.
as for it being an ms3302 device.. i havent seen that device under our series.
Use this to unbrick http://forum.xda-developers.com/android/development/stock-firmware-rom-unbrick-lg-k7-k330-t-t3432878