[Q] AT&T LG G2 Bricked? - AT&T LG G2

So I was doing the usual and installing a new ROM: CloudyG2 3.0. After it installed it said "failed" and I was like "okay" so I rebooted my device and I got stuck in fastboot mode. I got this phone a week ago for my birthday and I really hesitated and I still am hesitating. I was looking all over XDA and found this http://forum.xda-developers.com/showthread.php?t=2477595 so I followed the instructions and got all the way to the download mode part. What was supposed to happen was when you entered download mode it went to the Firmware Update thing with the 0% bar right? Wrong, mine got stuck at Download Mode with the 5 blue dots getting bigger and bigger. I have tried so many things and I just cant get Firmware Update to pop up. If I could have some help that would be great. Thanks.

Related

[Q] S3 stuck at FIrmware upgrade encountered an issue

So I have had my S3 rooted for a long while. But the past few weeks it's been running a bit slower. This week it started randomly turning off. I thought it was my battery at first. But then when I tried to turn it back on it got stuck at the Galaxy s3 screen and would not get into the OS.
I tried to get into recovery, it froze on the splash screen. I made sure both were actually frozen by leaving it sitting there for 30 min to an hour.
Tried to flash using this thread: http://forum.xda-developers.com/showthread.php?t=1974114
It kept just sitting at writing NAND.
Now my phone says "Firmare Upgrade encountered an issue, please select recovery mode in kies and try again"
Kies will not connect my device. It sees it but will not complete the connection. I tried using the model and IMEI number to upgrade firmware but it still would not connect to do that.
More searching lead me to this: http://forum.xda-developers.com/showthread.php?t=2581166&page=11
But I can't get into OS or recovery so I don't think this would work.
Any suggestions on what I can do from here? I only really need the phone to work for a few more months. My old Droid incredible just doesn't cut it at this point.
Sorry to bump, but nobody has anything for this? I haven't really found any other options.
Your bootloader is fine so that thread won't help you. What was the last version of touch wiz that was on your phone before you ran into problems?

[Q] Stuck! Phone does't turn on and does not charge

Hello guys I have been struggling for the past week, my LG G2 phone has been rooted, I flash a custom recovery TWRP then I lunched to my stock rom I then tried to update my firmware to 4.4.2 kitkat the update was downloaded successfully, then it told me to reboot, so I did phone switched off then I was stuck on a boot loop but this time it was a boot loop with a error message on the left top corner. and then it would take be to a dim back screen. I searched the entire week to find a method to get me through the start screen and I found this -> NO Recovery mode, No download mode, after OTA on rooted LG G2 http://forum.xda-developers.com/showthread.php?t=2582142 I done exactly what it was showing, then my phone switched off and now it won't power up. Then I tried turning it on NOTHING phone does't show the LED charging lights, does't respond to the usb being plugged in can't do ANYTHING I am guessing the battery has died so now I don't know what to do, either contact LG or should I try getting a battery that is fully charged or even use a factory cable any ideas guys ?
Call LG support.
Sent from my g2 using Tapatalk

Strange Rom Manager/Clockwork Mod problems

I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
somesortofthing said:
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
Click to expand...
Click to collapse
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
ShapesBlue said:
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
Well, can I somehow get my phone into working order? Because it's as good as bricked right now.

[Q] Bricked Phone stuck at boot - wrong version flashed (f350l on d838)

Hi everyone, I need a help on my LG G PRO 2. Basically what I did is being one of the biggest dickhead on the earth. I was so excited about gettin lollipop on this phone that I didn't noticed it was NOT for my phone.
So, before it happened i had d838v10f on it, rooted and recovery installed (it was an apk with a pharaoh...)
Then I get into recovery and flash this zip:
http://forum.xda-developers.com/lg-g-pro-2/development/b-futurev3-0-lolipop-walkman-f350l-s-k-t3001632
While flashing in recovery it says something went wrong, I reboot and it keeps staying in the boot screen. I noticed that the "powered by android" text in the bottom has changed, android L style, but it does not go forward.
So, I tried to go in download mode: Before it was in english, now it's in KOREAN. I tried to flash d838v10f kdz, and it goes on until 49%. It just stops and won't go on. So I also tried to push some .tot files, but this thime it doesn't even start. Part of the log says:
IMEI:NULL
Error: CrossDL [F350L] to [D838].
So, it's actually a F350L now, a NOT WORKING F350L.
If you have any question, or suggestion about it, don't hesistate!
THANKS!!!
Hi, eagle93. The same happened to me yesterday. Go here:
http://forum.xda-developers.com/showthread.php?t=3004653
And read from post #5 on... Good luck!

Nexus 5 stuck on colored balls/dots..!!!

I got a small 10 mb update for my Marshmallow. I downloaded that and after it was done, while installing an error came. i switched off my phone thinking it would start properly. Then it got stuck on the colored balls/dots that come before the welcome screen. I tried switching on and off but no success.
Then I did a factory reset and after everything was done and i thought the phone would get switched on, but it again got stuck on those colored balls. Now the phone is not getting switched on..
Plesae help..!!!
parthkaura said:
I got a small 10 mb update for my Marshmallow. I downloaded that and after it was done, while installing an error came. i switched off my phone thinking it would start properly. Then it got stuck on the colored balls/dots that come before the welcome screen. I tried switching on and off but no success.
Then I did a factory reset and after everything was done and i thought the phone would get switched on, but it again got stuck on those colored balls. Now the phone is not getting switched on..
Plesae help..!!!
Click to expand...
Click to collapse
Is it rooted or non rooted? Stock recovery? Probably you can flash the latest image files (except userdata) and check if it is working.
You can go through the guides on how to flash image files from the sticky posts.

Categories

Resources