Database Info

Applied Todays Update Sep 22nd... BRICKED!

Went to Setting->Software-Update and it started to update. Accicently hit cancel. The phone rebooted once and said failed and shutdown.
Now the power won't even come back on. Changed batteries, tried to boot into recovery, etc... nothing. no power, nada! Bricked
Went to ATT store, they said go back to Kiosk. Kiosk doesn't have anymore phones. WTH Kiost Says goto ATT.

Same thing happened to me. Phone is completely dead...

Guess I'm not the only one.
I didn't even hit cancel. It was almost at 50% and it just blacked out and never came back. Tried everything I could think of. Had to call AT&T and they are sending out replacement under warranty. Then they tried to tell me it would take 5 to 8 days (i think that was how long) unless I wanted to pay for priority shipping for 2 day. Short story even shorter. No, this is my second warranty phone and again I am without a phone or service I pay for. You will send it priority and I will not pay for it. I didn't pay for shipping on first replacement either. Don't let them tell you different. On another note, when calling AT&T tell them you need help with an Android phone. They don't know anything about them. Even the regular techs can't help you. They have specially trained (have special answer book) techs for our special phones.

Completely bricked
It's all messed up. It won't even turn on.. Please tell me there's a fix for this.

loganfynne said:
It's all messed up. It won't even turn on.. Please tell me there's a fix for this.
Click to expand...
Click to collapse
Odin3 didn't work for me. I exchanged my phone...

THANK YOU so much for this post!
I was about 50% into it when I started reading all the bricks that were occurring!

I guess I should consider myself lucky. I went to settings > Check for updates. It found and downloaded the update, and rebooted.
The update got to 50%, sat there for about one minute. Then it got to 88% and said "Update is failed. Phone will reboot now."
The phone still works, but with no update, and I can't try again for 24 hours.

my phone boots up, but after i get the 3g screen, it just hangs at a black screen =-(

Archpope said:
I guess I should consider myself lucky. I went to settings > Check for updates. It found and downloaded the update, and rebooted.
The update got to 50%, sat there for about one minute. Then it got to 88% and said "Update is failed. Phone will reboot now."
The phone still works, but with no update, and I can't try again for 24 hours.
Click to expand...
Click to collapse
Mine got to 100% and says that the update failed, but my phone is updated just fine @[email protected] weird huh.

I didn't even think to look at my About screen; I just took the phone's word for it that it didn't update. Now that I look there. I see:
Firmware Version: 2.1-update1
Baseband version: I897UCJH7
Kernel version: 2.6.29 [email protected] #2
Of course, I didn't bother to note what it was before, but that looks like upgrade info, and I took a walk with Roxanne tonight at the park, and the GPS worked like a champ. So in all likelihood, the upgrade did succeed.

btw
my phone was stuck on galaxy s logo (w/ active animation) for a while. If i didn't notice the animation, i probably would have rebooted

The JH7 update installed without a hitch though at times there seemed to be a delay - 50%, 88% and Galaxy S logo. I wonder if this update will fix any of the GPS bugs.

[Q] Screen not responding to touch

Hi everyone, just got the tablet today and set it up at work, played with it for bit and everthing was working fine.
Got home about 2 hours ago and now when I wake it from Sleep, the touch screen is not responding at all. Have tried everything, power is 98%, plugged into a PC, did the hard reboot, even wiping the data to start setup again. But all to no avail.
The screen isn't responding at all. Its very frustrating as I want to play with it some more!!!
Hope someone has experienced this and can help.

had the same issue once...i turned it off and left it for about 5min...turned it on and the screen works again...
this hasn't occured since then..probably just a system glitch..

Happened to me once, reset the device and it worked. Now it happened again and its been unusable for a day. If it doesn't work tonight, the $hit is going to hit the fan...

Are you stuck at the lock screen immediately after booting because the unlock function doesn't respond to touch? If so, I'm having the same situation. I really hope that waiting a few minutes does the trick...
Edit: even did a full wipe and the thing is still unresponsive. I assume this is a very bad sign. FML.

Have you guys contacted ASUS support? They will probably have you RMA it. How long did you guys have it before this happened? Now I'm worried that mine will do the same thing.

ASUS support did want to RMA my TF that was having this problem. However, after leaving it off for a couple hours, I went to turn it on to wipe out all my account settings and the touchscreen started working again.
I have no explanation for why it started working though. The last thing I did before it was magically fixed was go through the normal shutdown procedure by answering the 'do you want to shut down' using the dock's mouse instead of just holding down the power button. Maybe that made a difference?

Blue_Man said:
Are you stuck at the lock screen immediately after booting because the unlock function doesn't respond to touch? If so, I'm having the same situation. I really hope that waiting a few minutes does the trick...
Edit: even did a full wipe and the thing is still unresponsive. I assume this is a very bad sign. FML.
Click to expand...
Click to collapse
This is what happened to me. Stuck at the lock screen, no touch at all. After 4 days of waiting for Asus to reply to my email and several disconnected phone calls, I have returned it to newegg. Since this item is still out of stock I expect to receive a full refund. Which is fine by me. June 8th, here I come.

Same thing happened to me, just returned it to fry's and was able to avoid the restocking fee. Going to get the galaxy tab come june 8th now instead.
Sent from my Xoom using XDA Premium App

I have weird little quirky things like this happen from time to time with my TF, such as having to hit the power button or lock button twice before it works. I think it might be more of a software issue than anything to be honest. Hoping that future updates will correct all of these issues.

I hope its a software issue....

Found a solution that worked for me. I booted into recovery mode by holding vol down and power. then I selected vol up to enter recovery. Then the exclamation point came up with the android robot. I left it like that for a few minutes then held down the power until it resarted.
It booted up like normal, no data lost. I then restarted for good measure. Came right back up like normal, touch screen and all.

Thanks jdmnash. I followed your instructions and it worked like a breeze. Should make this part of a sticky help thread.

Found a solution
Update: Tried every fix I could identify on the forums as I was also draining the battery as suggested on several forums. After 4 days waiting for the battery to drain, I was able to restart the TF and get active responses to the touchscreen. Unfortunately I had performed a reset and wipe earlier so I am having to reload everything. I am happy to have a functioning TF again, but have serious concerns about this failure and this awkward repair method. Additionally, I have still not had a response from ASUS support from 5 days ago.

Mine is constantly doing this. Randomly.
Its as if the daemon for screen touch detection crashes. The rest of the unit is fine but that stops and the only fix is a power button off, then on.
Something is not right here. Its vanilla out of the box, no extra software just the 13 FW update.
Will 3.1 fix this? Hopefully, as it stands, this will have to be returned. It is not fit for purpose, constantly failing.

same problem
Just picked up mine. Out of the box at a cafe it worked just fine. Brought it home and same problem as everyone else in this thread. Have tried all of the suggestions in this thread (except waiting for the battery to die). Even installed the 3.1 update via SD. Still no joy. Guess I'll try a few more things before returning it. My guess is a problem in the supply chain with the capacitors that detect screen touch. Doubt that it can be solved solely through a software update (or if it can it definitely didn't make it into 3.1)

my touch screen stopped working a week ago while i was at school. and i got really pissed and just kept on rebooting it and after like 5 or 6 reboots it started working. Havent had same problem since.

Hmm... thanks for suggestion. Tried booting it about 5 times but still borked. Draining the battery now as my last attempt before taking it back.

Update: I ran the battery down to zero. Charged it up for 30 mins and now it works again. Hope I don't have to repeat that very often.
BTW, the fastest way I could find to run down the battery was to power on while holding down the volume down button. Then just leave it sitting in that state until it reboots itself and then repeat.

Unstable touchscreen
obi-nine said:
Update: I ran the battery down to zero. Charged it up for 30 mins and now it works again. Hope I don't have to repeat that very often.
BTW, the fastest way I could find to run down the battery was to power on while holding down the volume down button. Then just leave it sitting in that state until it reboots itself and then repeat.
Click to expand...
Click to collapse
Hi , After the battery is zero and then 30 minutes charging, in order to make it work , did you discharge it right after 30 minutes or still you keep it charging ?
I got same problem with my TF which is really a disappointment.. I tried to factory reset, reboot ... but still can't make it work. I have to try this trick by draining the battery to zero. Hopefully, I get advise from all of you for this problem ?
Thanks a lot

Can you guys try using ADW launcher and see if things improve?
I think it did for me.

My Galaxy S3 just died without explanation (resolved)

Welp,
There's no doubt in my mind that my Galaxy S3 just hard bricked
Looking for some advice on what to do.
I've had the phone for 20 days, I've been running Beans Custom Stock ROM Build 10 for over a week I think?
And this is how it happened:
I started sending a few texts to one of my brothers, with "Go SMS" , and my phone around the time I hit send decided to switch to 4G (which it hardly does because it's only 1-2 bars where I am) , I then went into the basement and my phone then went to show 0 bars of 4G, then looked like it was going to switch to 3G but then the SMS application hung. I tried closing it, but it wouldn't, so I held down the power button and as the boot menu was coming up, that hung, so I pulled down the notifications bar and tried shutting off data, but then that hung. So, I had no choice but to pull the battery.
I left the battery out for a little while and then put it back in. Held the power button, and the device hung on the "Samsung Galaxy S III" first boot screen. I pulled the battery again and waited for a really long while and took my Micro SDXC out.
Tried to boot but power button does nothing. There's no signs off life!
Plugging it into a wall charger does nothing and I'm sure there's still charge in the battery because when it died it was around 20-30%.
Only sign of life I can get is when I plug it into my PC and then put the battery in. THE RED LIGHT TURNS ON.
:crying:
I have no idea what caused this, and I have no idea what to do!
Will Verizon cover this since it bricked without question and it's been under 30 days?
Or maybe Samsung will cover it?
Or because I rooted, I pretty much screwed myself?
I've never had anything like this happen before so I'm stumped...................HELP!!!!!!!!!!! I used to love my S III but now it's just a really nice paperweight.............. :crying:

I guess this is an option also: http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/

mcappleman said:
Welp,
There's no doubt in my mind that my Galaxy S3 just hard bricked
Looking for some advice on what to do.
I've had the phone for 20 days, I've been running Beans Custom Stock ROM Build 10 for over a week I think?
And this is how it happened:
I started sending a few texts to one of my brothers, with "Go SMS" , and my phone around the time I hit send decided to switch to 4G (which it hardly does because it's only 1-2 bars where I am) , I then went into the basement and my phone then went to show 0 bars of 4G, then looked like it was going to switch to 3G but then the SMS application hung. I tried closing it, but it wouldn't, so I held down the power button and as the boot menu was coming up, that hung, so I pulled down the notifications bar and tried shutting off data, but then that hung. So, I had no choice but to pull the battery.
I left the battery out for a little while and then put it back in. Held the power button, and the device hung on the "Samsung Galaxy S III" first boot screen. I pulled the battery again and waited for a really long while and took my Micro SDXC out.
Tried to boot but power button does nothing. There's no signs off life!
Plugging it into a wall charger does nothing and I'm sure there's still charge in the battery because when it died it was around 20-30%.
Only sign of life I can get is when I plug it into my PC and then put the battery in. THE RED LIGHT TURNS ON.
:crying:
I have no idea what caused this, and I have no idea what to do!
Will Verizon cover this since it bricked without question and it's been under 30 days?
Or maybe Samsung will cover it?
Or because I rooted, I pretty much screwed myself?
I've never had anything like this happen before so I'm stumped...................HELP!!!!!!!!!!! I used to love my S III but now it's just a really nice paperweight.............. :crying:
Click to expand...
Click to collapse
Call verizon and they will send you an replacement. If its thats far gone theres no way they can check to see if its been modded.

Me too!!!!
Message removed

This happened to me after having mine for 3 days, i got mine replaced without a problem and i was rooted, cm10 custom kernel everything

fr8cture said:
This happened to me after having mine for 3 days, i got mine replaced without a problem and i was rooted, cm10 custom kernel everything
Click to expand...
Click to collapse
But I've had it for 20 days now and their website says they don't allow returns or replacements after 14 days. Or is this different because it randomly died?
Also. I don't get insurance on my phones because they always would charge me $10 or more a month and then when the phone died they would charge half the cost of the phone just to get it replaced!
Honestly I think I may just send it to MobileTechVideos.........
Unless I still have a chance with Verizon. Hard decision............

I'm pretty sure the 14 day timeframe is for refunds on the purchase. Most electronics have some sort of manufacturer's warranty.

Have you tried to get it into download mode? volume down, then home, then power, Hold them all together until it boots into download mode? Do this while plugged in maybe?

samsung s 3
Take it to att ive done it a few times call cuctomer service tell them your on warranty hopefullt you bought this new from them they then will send you to repair center no one will no difference tell them it just crashed this doesnt seem like a rom problem its manufacture
email or text me [email protected] or 5105086739

cmars said:
Take it to att ive done it a few times call cuctomer service tell them your on warranty hopefullt you bought this new from them they then will send you to repair center no one will no difference tell them it just crashed this doesnt seem like a rom problem its manufacture
email or text me [email protected] or 5105086739
Click to expand...
Click to collapse
You really give your phone number out to strangers like that?
Sent from my SCH-I535 using Tapatalk 2

cmars said:
Take it to att ive done it a few times call cuctomer service tell them your on warranty hopefullt you bought this new from them they then will send you to repair center no one will no difference tell them it just crashed this doesnt seem like a rom problem its manufacture
email or text me [email protected] or 5105086739
Click to expand...
Click to collapse
Haha. Thanks!
Well, I ended up making a Google Voice account since my phone is dead and I called Verizon customer service. The first lady started having me go through the usual checklist like most companies do, I very nicely let her know that I've tried it all and I indeed know it's dead without explanation. She then sent me to someone higher up, we talked very briefly and she said it's covered under the manufacturer warranty, they're sending me a replacement for free. Only thing I paid for was a $12 upgrade to 1-day shipping!
I seriously was freaked out that I wasn't going to be able to get this replaced. Thankfully I can!
So, I guess, some advice to people that have hard bricked Galaxy S IIIs, CALL VERIZON BEFORE ANYTHING ELSE!
Thanks for the suggestions and help guys!
It's crazy how deep the brick went, the phone wouldn't even charge! Maybe I got a lemon? I hadn't even dropped or scratched it and I had 0 problems with unlocking/rooting it. I swear it was it hanging on trying to switch from 4G to 3G that killed it. Either way, stress is gone! phew! :fingers-crossed:

mcappleman said:
Haha. Thanks!
Well, I ended up making a Google Voice account since my phone is dead and I called Verizon customer service. The first lady started having me go through the usual checklist like most companies do, I very nicely let her know that I've tried it all and I indeed know it's dead without explanation. She then sent me to someone higher up, we talked very briefly and she said it's covered under the manufacturer warranty, they're sending me a replacement for free. Only thing I paid for was a $12 upgrade to 1-day shipping!
I seriously was freaked out that I wasn't going to be able to get this replaced. Thankfully I can!
So, I guess, some advice to people that have hard bricked Galaxy S IIIs, CALL VERIZON BEFORE ANYTHING ELSE!
Thanks for the suggestions and help guys!
It's crazy how deep the brick went, the phone wouldn't even charge! Maybe I got a lemon? I hadn't even dropped or scratched it and I had 0 problems with unlocking/rooting it. I swear it was it hanging on trying to switch from 4G to 3G that killed it. Either way, stress is gone! phew! :fingers-crossed:
Click to expand...
Click to collapse
So i didn't see it, but did you even try to get it into download mode?
Sent from my Synergized vzw S3!

silver04v said:
So i didn't see it, but did you even try to get it into download mode?
Sent from my Synergized vzw S3!
Click to expand...
Click to collapse
It's hard bricked. Will not charge, no booting, and download or recovery mode won't work. Will not show any indication of life except for plugging it into a power source without the battery and then putting the battery in. If the red light comes on when you do that, it means it's hard bricked? Correct me if I'm wrong?

mcappleman said:
It's hard bricked. Will not charge, no booting, and download or recovery mode won't work. Will not show any indication of life except for plugging it into a power source without the battery and then putting the battery in. If the red light comes on when you do that, it means it's hard bricked? Correct me if I'm wrong?
Click to expand...
Click to collapse
If you can't get into download mode then yea, most likely I guess or the battery died. I just didn't see that you said you tried to get into download mode.
Sent from my Synergized vzw S3!

Glad you got this fixed! Also i think its a 30 day replacement or swap for another phone if you don't like it. Thats what i was told when i got mine.

[Q] Some really weird problem over here.

Once, i was halfway using whatsapp then phone turned off automatically, when I turn it back on i was able to boot up past the bootscreen until i got this: Refer to Picture 003.jpg
Then I did a complete reset via CWM. I even installed CNA 3.6.6 (I was using 3.5.0 before this)
Still no avail, do I've decided to flash back to 4.0.4 to see whether things are working out or not.
I did it via fastboot.
Same thing.
What could be the problem?
Do take note that even though in the picture I'm booting it up in safe mode but still no avail for normal mode.
And, when I'm charging my phone with the power switched off I'm getting this: Refer to Picture 004.jpg
Supposedly it's a battery icon that indicates charging activity but I'm getting a battery icon with (blinking) exclamation mark.
What's wrong?

Try a new battery
Sent from my Nexus S using xda premium

jayjay3333 said:
Try a new battery
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Gonna try it soon as soon as my friend is with me. Anyways, the picture I've attached shows the shutting down popup.
When it first occured(and for the next few times)it's without the popup and i can't even pull down my notifications window. BUT the 4 buttons worked. they responded by vibrating.

zennasyndroxx said:
Gonna try it soon as soon as my friend is with me. Anyways, the picture I've attached shows the shutting down popup.
When it first occured(and for the next few times)it's without the popup and i can't even pull down my notifications window. BUT the 4 buttons worked. they responded by vibrating.
Click to expand...
Click to collapse
its a battery issue for sure
or maybe your usb is broken, but i dont think so

Cascabreu said:
its a battery issue for sure
or maybe your usb is broken, but i dont think so
Click to expand...
Click to collapse
warning! TL; DR post about what happened to my phone.
I've left my phone (accidentally) under heavy rain for almost an hour.
By the time I got my phone back it's still working, but with a (kinda) faulty loudspeaker.
Others went a-okay.
I turned off and let it stay put for everything inside to dry up then charge. Realized that I can't charge at all. I can't even connect to computer or whatnot. So I brought it to a service center. They told me it's mobo issue and I've decided not to fix it (cause my warranty's over)
That day when I brought it back from service center, miraculously I can charge my phone! was happy at first then I kept on charging. Then story continues as first post.

same thing here!
zennasyndroxx said:
warning! TL; DR post about what happened to my phone.
I've left my phone (accidentally) under heavy rain for almost an hour.
By the time I got my phone back it's still working, but with a (kinda) faulty loudspeaker.
Others went a-okay.
I turned off and let it stay put for everything inside to dry up then charge. Realized that I can't charge at all. I can't even connect to computer or whatnot. So I brought it to a service center. They told me it's mobo issue and I've decided not to fix it (cause my warranty's over)
That day when I brought it back from service center, miraculously I can charge my phone! was happy at first then I kept on charging. Then story continues as first post.
Click to expand...
Click to collapse
i bought my nexus from a man for 25$ because it wasnt able to charge and when u turned it on it just went stuck on the motion starting picture.
so i went to a technician and he told me to buy the usb port , i found the original port for nexus s on ebay, so he fixed it...
since then i am able to charge it (with a exclamation sign if its off) and i have even intalled every rom i have found here, via odin/fastboot/CWM, etc. but nothing... so it keeps on stucked on the starting picture, sometimes just SOMETIMES it went up like yours, *going up and saying/showing Android System icon, batterymetter on the upper part of the screen, middle screen; saying power off, shutting down, after some secs, vibrates and goes OFF.
only with slimbeam i got that behavior always turn it on.
p.s. the USB port was unable because phone have been wet (from the other owner hands)...

one thing, make sure the battery contact points are clean i know its dumb but it could help

Still the same.
qaz2453 said:
one thing, make sure the battery contact points are clean i know its dumb but it could help
Click to expand...
Click to collapse
Still the same thing. Then I left my phone unattended for a day.
It's back up and running after I turned it back on.
Then the same thing happened again. But I just left my phone idle.
Man what's wrong

dude, tell me something...
zennasyndroxx said:
Still the same thing. Then I left my phone unattended for a day.
It's back up and running after I turned it back on.
Then the same thing happened again. But I just left my phone idle.
Man what's wrong
Click to expand...
Click to collapse
man, anything new?
i would like to know how to install EVERYSINGLE THING on the nexus s, i mean like a stock boot or fastboot, or a new BIOS..
help me over here ! please. i would be pleased,

Nexus S i9023 Android 4.1.2 Update
Yesterday i got OTA update 4.1.2 in my Nexus S i9023 in India. But after restarting the system for installation for some reason the update was not done. After hard booting the device when it logs on, it was showing 4.1.1. But when i am checking whether any system update is there, it is showing no update. How to get it again ????

Boot Loop, sort of...

I'm having a weird issue that literally just started yesterday. First of all, I didn't do any changes yesterday before this occurred. Anyway, my G3 just started freezing, then rebooting randomly, BUT that's not all! When it tries to reboot, it flashes the LG screen, and SOMETIMES makes it to the AT&T screen....and even, sometimes makes it all the way booted up. But, at any point, it can/will reboot and start the process all over. I read on another site that it could be a battery going bad, but I only trust XDA. So, could someone chime in with some help or info pointing me in the right direction?
Thanks in advance,
Ontabok

same issue i am having ..i thought about the battery thing so i pulled it out and put in a fully charged one and no bootloop..but now 3 hours later and 85 percent left on battery and bootloops have started again..btw other battery was a 20 percent when changed it out for fully charged batt..so im just as lost trying to figure it out

Ontabok said:
I'm having a weird issue that literally just started yesterday. First of all, I didn't do any changes yesterday before this occurred. Anyway, my G3 just started freezing, then rebooting randomly, BUT that's not all! When it tries to reboot, it flashes the LG screen, and SOMETIMES makes it to the AT&T screen....and even, sometimes makes it all the way booted up. But, at any point, it can/will reboot and start the process all over. I read on another site that it could be a battery going bad, but I only trust XDA. So, could someone chime in with some help or info pointing me in the right direction?
Thanks in advance,
Ontabok
Click to expand...
Click to collapse
Sadly that sounds like a hardware issue

hyelton said:
Sadly that sounds like a hardware issue
Click to expand...
Click to collapse
How can I figure out what part of the hardware could be causing this? Is there a diagnostics or something I can use? I've tried factory reset (multiple times), LG Flash Tools to flash previous version, and the strange thing is it may not even make it through the process without restarting again. It's been rooted, but I've never had a problem until this. I never deleted anything.

Ontabok said:
How can I figure out what part of the hardware could be causing this? Is there a diagnostics or something I can use? I've tried factory reset (multiple times), LG Flash Tools to flash previous version, and the strange thing is it may not even make it through the process without restarting again. It's been rooted, but I've never had a problem until this. I never deleted anything.
Click to expand...
Click to collapse
Not really other than swapping out parts. If using flash tool won't work and it won't go back to stock then it's definitely a hardware issue.
What percent does it get too before rebooting? If 80% that's normal. If before it's definitely a hardware problem.

hyelton said:
Not really other than swapping out parts. If using flash tool won't work and it won't go back to stock then it's definitely a hardware issue.
What percent does it get too before rebooting? If 80% that's normal. If before it's definitely a hardware problem.
Click to expand...
Click to collapse
I can try Flash Tools again. Maybe it just didn't take. I just noticed another thing. When it's trying to boot, if the notification light flash when the LG screen is on, it will load. But, if it doesn't flash, then it will just go black, then flash the LG screen again.

Kameirus said:
same issue i am having ..i thought about the battery thing so i pulled it out and put in a fully charged one and no bootloop..but now 3 hours later and 85 percent left on battery and bootloops have started again..btw other battery was a 20 percent when changed it out for fully charged batt..so im just as lost trying to figure it out
Click to expand...
Click to collapse
Yeah. It's really weird. It seems to do it less when the battery is charged, but if I get down to 40-50%, it could go into a loop that runs the battery into the red. Also, it seems to heat up around the power button when it's stuck in the loop. And, to top it off, my software update popped up yesterday. I've been anxiously awaiting Marshmallow for a while, but I'm afraid to update because of boot-looping right in the middle and bricking the whole thing. I already have a bricked G2 due to something weird that happened while trying to update to Lollipop. I'm going to the AT&T store today, I think. I'll let you know what I find out. Maybe, it can help you.
Thanks,
Ontabok

hyelton said:
Not really other than swapping out parts. If using flash tool won't work and it won't go back to stock then it's definitely a hardware issue.
What percent does it get too before rebooting? If 80% that's normal. If before it's definitely a hardware problem.
Click to expand...
Click to collapse
Ok. So, first of all, sorry for the long wait on a reply.
I did manage to get through a factory reset, but it still is doing the boot loop. I'm going to take it in to AT&T today. You can see my reply above to see more info. I unrooted everything and factory reset, but it still loops. I think it's a problem with the phone. I may have to go to LG, depending on what AT&T says.
Thanks for the help!
Ontabok

So, final update. I had to go into the AT&T tech store. I was having the random boot loop for about a week, then, on Saturday, I got the Demigod green screen. I had went in the day before and ordered a new battery, but I couldn't find any information on the green screen error. I took it in and they immediately (after checking for rooting) replaced it (warranty). They said they had never seen/heard of this screen. They had to actually Google it to see if it's attached to rooting. (It's not) Anyway, so I'm back in the saddle with a brand new phone. ?
Sent from my LG-D850 using Tapatalk

Also, thanks for the replies!
Sent from my LG-D850 using Tapatalk

ok so my g/fs g3 just started doing this. updated to mm about 3 or 4 days ago. was doing fine. haven't changed anything software wise. completely stock. no root.
what is really odd is that it doesn't loop when plugged into a power source. take it off the charger= insta loop ...
hoping a rom might solve the issue but from the sounds of the replies maybe that isn't the case.
any help greatly appreciated. i've not owned this phone myself or i would already have it rooted and custom recovery..
is there even a root method for MM? recovery?
i'd love to see if its a software issue. the phone worked swell before the update...
im trying to get to the bottom of this tonight if i can my g/f has a final tmr early in the morning and i'd like to make sure she has a phone to go with her. prob send her with mine if i can't get this working. but thats less than ideal PM if you've got anything i can try or links to get me started... i'll be reading in the mean time...