Well i have been looking all over for help with my phone. I have figured out that i tried to flash a rom without unlocking my bootloader. Well im running windows 8.1 and for some reason i couldnt get my computer to recognize the phone at all. After using 3 or 4 different guides i gave up for a few days so not to get too aggrivated. I mean its my own fault but my back up phone sucks lol. So i borrowed my wifes laptop running win 7. I Followed this guide androidforums.com/optimus-l9-all-things-root/807569-guide-security-error-fix.html. For the first time since i started trying to solve my issue everything seemed to work got the s/w screen to appear in reverse and using the cmd prompt that says wiating for device then starting the .bat file from the download it says on the bat cmd prompt that everything worked. well at the bottom its says done then comes up with C:\fastboot\yours. i have been browsing google but i havent been able to find what i am supossed to do with the yours file. i tried putting a kdz file into the file location and running it from that but no luck. after a few min the phone auto reboots and comes back with the security error screen and not the backwards one. i have tried doing the hard reset at the point but no luck. if someone could please help with what i need to do with the fastboot/yours area that would be awesome. Or at least point me in the right direction cuz google isnt wanting to be my friend with the searches.
Android noob in training:
Sobih
help
Well i have tried several times now with using my wifes windows 7 laptop. i can get everything to work with the screen coming up backwards and in the command prompts it says that the fastboot is done then loads the command fastboot/yours which with the file i downloaded that file was empty. really unsure on what i need to do at this point. from the guides i have read it seems that im at like a step or 2 from getting the phone to work but after 30 seconds while still plugged in it reboots and loads the secruity error screen. from what i have read i should be able to do a factory reset by holding the volume and home button and then pressing the power for 3 seconds but it just reboots into the error. any help would be much appreciated i really dont want to have to buy a new phone.
Seems like that guide is more for when flashing a recovery on the locked bootloader and things go wrong. It was suggested a few posts down on the first page of that guide that if your problem happened when you were trying to flash a rom you might want to follow this : http://androidforums.com/optimus-l9-all-things-root/792689-guide-unbrick-manual-update-updated.html or http://forum.xda-developers.com/showthread.php?t=2085344 (the xda one seems more complete) .
sigh
Well im still stuck on the security error screen. i got the phone to boot into the backwards fastboot screen 1 time and cant remember how to do it again. i can boot into the s/w upgrade mode. if i go to use the lg support tool being that im in the united stats my options is upgrade recovery or help. well if i go to upgrade recovery im told that my phone has the latest upgrade already. if i try and use the moduptest that come in a lot of the unbricking guides it makes me turn the internet back on even with having hte shttps and everything else that is listed in the various folders. i only have the omap44 on my device manager 1 time but there is also 2 lg mobile modems. im thinking my issue lies with the fact thta i dont have the adb file for the device manager. i have donwloaded and uninstalled various times but still no luck. i dont remeber how i got the phone to the backwards fastboot but i remember i was following a guide and the op had to open one file and while that one was stuck on "waiting for device" he opened another one becasue that was the only way he could get it to connect. Any help would be awesome. not trying to rely on everyone else but after several weeks trial and error im at my wits end with it.
thanks
sobih
Related
Evening all,
I have been advised to post here on XDA from Android Forums. This is a copy of my initial post on there to explain the background to my issue.....
Hi there,
I have HTC Desire from O2 and after 12 hours of online searching and tweaking I'm hoping someone may be able to help.
I received the OTA upgrade yesterday which I accepted because I thought O2 might have it sorted by now. Obviously not. Anyway update ran with no interruption but then rebooted to a frozen O2 screen.
I searched the net and eventually found the guide to update the phone using the RUU Rom. I followed this to the letter and the installer for the RUU wouldnt't open. I then realised that Google Chrome hadn't fully downloaded the file (113mb not 171mb). I then used a download manager to ensure I had the full file. It then ran and seemed to be working... until 80% in when I get ERROR 110 File Open.... please use a complete RUU. I downloaded it several more times in various ways but still same result. By this point my phone was pretty much bricked.
I had black screen with silver HTC logo in the middle and 4 exclamation marks in the corners.... this remained whilst the phone was plugged in and the buttons in any combination did nothing. When i removed the USB cable i got a white boot screen with RUU highlighted in orange and again.... buttons do nothing. Every time I ran the RUU file it brought up a green bar as if it was making progress but then errors at the same point every time. (Error 110 use complete RUU... file seems to be complete now at 171mb)
I tried it on two computers, one win7 and the other vista. The vista machine doesn't even see the phone, it gives a USB error before the update begins.
At 2am I used the SDK download and typed the following at command prompt.... "fastboot oem boot".... phone instantly boots into O2 Froyo and works fine. If i then unplug the phone, turn it off and on again.... i get the black HTC screen again, back to square one.
At the moment I have fastbooted it so its working and have used the goldcard tool to obtain the CID and created the .img file.
I don't know what to do from here!!.... the update obviously hasn't FULLY worked but it must have completed enough for the thing to fastboot and seems to have full functionality (calls, wireless, network etc)
I don't really want to void the warranty but O2's only option is to send it off for 14 days to have an engineer tell me its buggered and send a replacement.
Any advice is appreciated.
Rich.
A couple of helpful guys on there have tried to advise me but without success. They suggested rooting etc but here is my problem.....
At the moment the phone seems to be working fine with Froyo... but the only way I can get my phone to start up is by plugging in and running "fastboot oem boot" from command prompt. If my phone is powered off and I turn it on in the normal way, I get the black screen with silver 'HTC' and triangles in 4 corners and all buttons do nothing!
I have tried fastboot command whilst holding down the volume keys etc and it just boots normally. Obviously something isn't right and I can't let my battery run down otherwise its useless until I can fastboot it again.
So this is preventing me from accessing any of the menu's required in the flash/root tutorials.
Can anyone help or do I just need to ensure I don't run the battery down?!?
Thanks in advance
Rich
if you have a goldcard already, have you tried flashing a diffrent ruu from fastboot? maybe just a generic htc one rather than the o2 one?
Hi,
Thanks for your reply.
Could you advise me which RUU would be the best to use?
I have looked through the list on shipped-roms website but apart from the obvious O2 ones, I don't understand which ones are which!
Thanks
Rich
Hi Rich,
I have exactly the same problem. Have you got any feedback about whether you have solved this issue?
Thanks!
Kelk
Edit:
I think I may have got it sorted. Downgrade to 2.1 as per:
hxxp://forum.xda-developers.com/showthread.php?t=768256
(replace xx to tt in link above)
Hi there,
I haven't solved my issue yet. At the moment I am using my phone on 2.2 but trying not let the battery run flat (I have to use fastboot from command prompt to get my phone to boot up)
Did the tutorial above work for you?
My issue is getting a working goldcard. I'm not sure whether mine has worked succesfully because when i've tried running the RUU of either the unbranded froyo update or even the O2 original, i get and error message and it doesn't work.
I followed the goldcard creation tutorial but I still get the CID error when trying to run the various RUU files.
I hope I can sort this soon because i've been close to throwing my phone out of the window several times!!
Cheers
Rich
Hi Rich,
Yes, the above tutorial worked for me. I think this is because it downgrades to a former version of HBOOT.
rich0684 said:
Hi there,
I haven't solved my issue yet. At the moment I am using my phone on 2.2 but trying not let the battery run flat (I have to use fastboot from command prompt to get my phone to boot up)
Did the tutorial above work for you?
My issue is getting a working goldcard. I'm not sure whether mine has worked succesfully because when i've tried running the RUU of either the unbranded froyo update or even the O2 original, i get and error message and it doesn't work.
I followed the goldcard creation tutorial but I still get the CID error when trying to run the various RUU files.
I hope I can sort this soon because i've been close to throwing my phone out of the window several times!!
Cheers
Rich
Click to expand...
Click to collapse
Use Goldcard + your shipped o2 ROM (ROM that came originally with ur phone 1st time). you can get the rom from HTC official website. enter your Serial Number t download (i recommend using Mozilla built in download manager, coz Google Chrome always give me Corrupted Download when downloading Large files)
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.
Hi everyone! As stated in the title my phone(p769) wont boot completely, I was in the middle of doing the bootloader unlock when I accidecntly replaced the bin during the root process of it with the wrong bin. Instead of replacing it with the v6 tmobile usa one I used the v5 canadian one. Now when I boot my phone up the lg screen is there and then eventually it just hits an android with a red exclamation point. I've tried Re-flashing while its in s/w upgrade mode with the flasher set to emergency, and Ive tried pressing the home button + vol down + power to no avail(it goes through the process but the same thing happens)
Any help at all would be greatly appreciated and many thanks in advance!
Edit: Also when I try to reflash, it just says it cant communicate with my phone. Ive uninstalled and reinstalled the drivers several times but seeing as how I cant acutally get into the phone Im not sure what else to do.
Edit 2: So ive been trying do something witht his for the past three hours and I cant get anywhere with it. I cant get the phone to show up as an adb device while its in s/w upgrade mode, and at the red exclamation point screenit shows up but as recovery and the lg tools fail to communicate with it. I would really appreciate if anyone knew how to deal with this.
Just in case anyone stumbles upon this and has the same issue I would like to say that i finally got mine fixed.
It has been a long day of frustrations but I finally got it there with the help of some awesome tutorials.
In order to fix it I had to fastboot my phone and flash the default loader and boot then my device would show up in my adb devices and I could sucessfully flash and root it.
hufger said:
Just in case anyone stumbles upon this and has the same issue I would like to say that i finally got mine fixed.
It has been a long day of frustrations but I finally got it there with the help of some awesome tutorials.
In order to fix it I had to fastboot my phone and flash the default loader and boot then my device would show up in my adb devices and I could sucessfully flash and root it.
Click to expand...
Click to collapse
how you resolve it?
saman_z1384 said:
how you resolve it?
Click to expand...
Click to collapse
I followed the fastboot tutorial and searched around in the help forum for people with similar issues and found a post where lelus posted both of the files I needed to flash with fastboot, from there I just put my phone in s/w upgrade mode and followed Lelus guide for root/flash
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
anticlotto_ said:
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
Click to expand...
Click to collapse
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
CROSSFREEZE said:
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
Click to expand...
Click to collapse
Thank you for your reply! I have tried hard resetting multiple times, but I had removed some bloatware apps (I will quarantine them next time instead because I don't wanna go through this ever again) and I have tried the kdz method to only be stuck at 15% every time when I followed instructions to the pixel. I have tried to do it on windows 7 and windows 8. I have also tried the fastboot method by lelus, and that manages to "work" but I am still stuck at the tmobile boot screen afterwards. I have gotten the hang of the process of getting into the fastboot, but what do I do from there? I chose to flash ics xloader and uboot, but the process goes by so fast, I'm not even sure it is doing anything. The LG Tool has really gotten me nowhere, it just gives me a lovely error and then cannot continue the upgrade recovery process.
It said somewhere that after I flash through the fastboot I then have to try the kdz method, so I am going to do that now and see if it works. I don't know if there would be a difference between flashing a jb kdz or an ics kdz, but I will just do ics to be on the safe side.
I am quite happy to say that flashing the ics kdz was successful, and my phone is now up and running.
My p769BK is stuck on the LG screen. /: months
Sent from my LG-MS770 using xda app-developers app
im terrible with fastboot, i used the unlock the bootloader for noobs with an offline flash.
heres what i did to get out of bootloops....
alright, this is all from memory but the offline flash didnt work as well for me when stuck in weird bootloops.
Step one-going back to online flash---->
A---
the easiest way i found was to go to C:/windows/system32/drivers/ect/hosts
right click>open with notepad
there should be two lines at the bottom
"127.0.0.1 csmg.lgmobile.com
127.0.0.1 csmgdl.lgmobile.com"
i would cut them out and paste them in a text doc in the same folder for reference later...
but either way you should remove them from the hosts file and save
B----
Make sure your small server is closed! once you minimize it it should go down to your status bar (shttps)
Step two-LGMS---->
make sure you have LG mobile support installed or install it.
open lg mobile support
install needed drivers for your phone
power your phone off/remove the battery
put battery back in
connect it to your computer holding down the volume up button
S/W UPDATE mode should pop up, if it doesn't preform and hardreset and try again til it works (it will)
then in the top right corner there should be a button or two click them both until you see
"restore update" or Update restore or something to that effect
select that
and let it ride man
i got my phone ****ed many times and just had to keep redoing this until it worked. if your bootloader is truely unlocked you can probably go through all that again and get CM10 working, i did but im still working through kinks.....
GOOD LUCK feel free to ask any more Q's about this process if you run into any problems
I only want my Wogiz WX40 to work properly again. It somehow got into a booting loop and I spent many hours figuring out how to flash it due to drivers acting unexpectedly, incorrect instructions for my device and so on.
I finally got it to flash with stock software I got from needrom using SP Flash Tool. However 1) none of the bottom keys work now and 2) it looks as if the resolution is set too high for the device and I think there is also some slowness when using the phone. I have tried clicking upgrade firmware and formatting the entire flash and using different versions of the software and the result is always the same - the bottom keys not working in particular makes it unusable. I tried downloading the stock rom from another location but after downloading it said I needed a password.
So what is the next thing I can try? I'm at my wit's end here and just want it to work again. Thanks for all help.
Anyone know what I should try? For example what custom RAM + firmware might I want to try? At this point I don't care what it is as long as it works. It's a MT6580 device if that helps.
God, I FINALLY got it working.
In case there's anyone else that runs into this: My mistake was getting the stockrom from needrom, every one of those roms for this phone is bad. Get the rom from shareas.us and use SP Flash Tool to flash it, and even then you have to try to get the one that isn't password protected with no password. Leave the battery in, turn the phone off, use option "format + download" in the software and click download BEFORE you connect the phone, NOW connect the phone and after a little while it will start downloading. Disconnect the phone when it's done and switch it on, it will take a REALLY long time to boot up the first time but it should then work.
That's what came from hours of trying to get it to work. The tutorials etc. online are so confusing, even some incorrect instructions like saying I should take out the battery that are completely false and I would never have gotten it to work if I paid more attention to them. I don't ever want to go through something like that again. I finally have my phone back.