Last night my phone just rebooted for no reason and now i cant get it to get past the LG boot screen. Only once has it gotten to the Verizon screen after it but then it looped back to the LG screen again. It does this until the battery dies or i pull it. Tried going into recovery mode and even tried to FDR but it wont do that either. Has anyone else dealt with this or does anyone have any suggestions, any and all welcome.
If it's boot looping,id take it back and get it exchanged
Related
Hey guys...
Kinda ultimate noob here, so I'll start from the beginning because I don't know what information could be pertinent. I don't really know much lingo at all, but I have a completely stock, unrooted HTC Inspire 4G from AT&T that my cousin gave me a few months ago. On and off since then, I've had a few random restarts and crashes, no big deal, always came back up. The other day,about a week ago, the headphone icon started blinking and my sound stopped working, so I restarted the phone and it got stuck on the ATT boot screen, so I took out the battery, let it sit, and when I put it back together, everything was fine. Last night, I was in a meeting and my phone battery was at 2%, so I turned it off so avoid it dying. I got home and plugged it in, and when I went to turn it on, it would not load past the ATT boot screen. I let it sit overnight, and a couple hours ago I tried a factory reset, and tried to boot up again, and it got stuck in what I believe is called a boot cycle, where it would go from the HTC startup screen to the ATT screen, go black, then repeat over and over. I did some research, and tried to use an RUU to set everything back to complete stock, but both of the ones I tried gave me the "Please get the correct RUU and try again" error. I have the 1.03.2011 RUU up right now, and it says that my image version is 3.20.502.52, and gives me that same error. I don't know if I completely effed it up or what, so any possible help would be greatly appreciated. I've been looking through guides and trying things for over 12 hours, but I can't get anything to work, so it would be best to start from the beginning. I tried to get everything I know about the problem in there, but if more information is needed, just let me know and I'll do my best to get it for you. I've heard great things about XDA and did most of my research here, so I'm hoping you can work some of your magic on my phone
Hello guys.
About an hour ago, I tried to access my WiFi configs, and realized it would take me back to the start screen. So I rebooted my phone. The thing is, it is now stuck in the big red Motorola/Intel logo, and keeps looping.
If I try to turn it off by using the Power button, it doesn't work. If I try to reset using Power + Vol Down, it just restarts the loop. I can't get into recovery mode, because it won't turn off.
I really don't know what to do. My phone is still trying to boot for the past hour, and I really need it, asap.
It is running Android 4.1.2. No root. As stock as it gets.
Any advice, guys? Please
alovose said:
Hello guys.
About an hour ago, I tried to access my WiFi configs, and realized it would take me back to the start screen. So I rebooted my phone. The thing is, it is now stuck in the big red Motorola/Intel logo, and keeps looping.
If I try to turn it off by using the Power button, it doesn't work. If I try to reset using Power + Vol Down, it just restarts the loop. I can't get into recovery mode, because it won't turn off.
I really don't know what to do. My phone is still trying to boot for the past hour, and I really need it, asap.
It is running Android 4.1.2. No root. As stock as it gets.
Any advice, guys? Please
Click to expand...
Click to collapse
I have the exact same problem.
My phone (non rooted, stock Android) has been freezing quite a lot for the past 1 or 2 weeks. Sometimes rebooting on its own, sometimes I had to force it. This afternoon it froze again and I had to force reboot, where it started freezing at the Motorola logo. I cant go any further since rebooting just makes it loop that way.
I waited for the battery to deplete so my phone eventually turned off, charged it back at around 60% and tried to go into recovery mode with power+volume up+volume down. Same results. I don't think I could have failed the recovery mode procedure because I had practiced and knew I would only get 1 chance of succeeding.
Anyone has experience with this ?
I will see if Motorola or my retailer will repair/replace it for free under warranty terms, otherwise I will try opening it up for some cleaning and maybe further attempts with control over the battery.
SuperS06 said:
I have the exact same problem.
My phone (non rooted, stock Android) has been freezing quite a lot for the past 1 or 2 weeks. Sometimes rebooting on its own, sometimes I had to force it. This afternoon it froze again and I had to force reboot, where it started freezing at the Motorola logo. I cant go any further since rebooting just makes it loop that way.
I waited for the battery to deplete so my phone eventually turned off, charged it back at around 60% and tried to go into recovery mode with power+volume up+volume down. Same results. I don't think I could have failed the recovery mode procedure because I had practiced and knew I would only get 1 chance of succeeding.
Anyone has experience with this ?
I will see if Motorola or my retailer will repair/replace it for free under warranty terms, otherwise I will try opening it up for some cleaning and maybe further attempts with control over the battery.
Click to expand...
Click to collapse
Well, Motorola did repair my phone for free, but I live in Brazil. It took them 1 day to repair. They say that part of the circuit board was damaged, but I don't know what could be the cause. Maybe overheat? I don't know about your phone, but mine would get up to 50ºC while using Skype.
Hi i am new here and was hoping that i get a solution to the problem that i have been trying to figure out for a few days now. I searched a lot before posting but wasnt able to find something related to this. My phone is an HTC One M7 and i was trying to update to the latest OS when the phone stopped booting into it after the update as it got stuck at the boot screen. So i waited for an hour until i decided to shut it off and when i tried restarting it, the phone stayed stuck at the HTC logo not even the ONE logo screen.
So i read a few suggestions and went into the bootloader > recovery and cleared cache and then restarted the phone as per the instruction i got afterwards. This time it kept cycling around the boot screen and black screen and so on. So i again went into bootloader and decided to *power down* the device till i was able to learn what to do next but to my surprise, the phone doesnt boot anymore into whatever there is - tried Power + Vol down, Power hold etc.
The phone charges though and is currently at 100%. So i am right now in a dilemma as whether to continue trying to fix this by myself or just send it to the service centre where they will charge around 300$ for this to get repaired while telling me that something got fried on the inside.
Thanks in advance!
I recently plugged my M9 into my computer to run the repair assistant in HTC sync... Well, for some reason the repair failed, and now my phone won't boot. I have tried running the repair numerous times since to see if it would fix itself, but to no avail. I've also cleared the cache in recovery mode, as well as factory reset from recovery mode. Still won't boot past white screen with HTC logo.
Any thoughts? I'd rather not have to send it in for repairs...
For the record, I did the repair initially in the hopes of it fixing what might be draining my battery. I've been searching frantically lately trying to figure out what is draining my battery, again, to no avail. Perhaps it was stupid to think this would help... but I also don't know how it screwed things up.
Any help is GREATLY appreciated.
It's a Verizon branded phone, no root.
I have only had it for about 16 months now. It is a MetroPCS GS7 so it's a T-Mobile variant if that matters. Never been rooted or modified in a similar way. The same thing happened with my previous phone, a GS4 which never got fixed. I was just using a video downloader app when it suddenly restarted. It only shows the first screen for about 5 seconds then restarts. I have some experience using ODIN and flashing ROMs but I don't know what I should try with a GS7.
After a few tries to get it into recovery, this is what happened. The blue recovery message in the top left showed up but I didn't let go of the buttons this time. Then this rotating white circle showed up and said something like "applying system update". After about 20 seconds then I got a screen with the dead android and it said "no command" below it. Then I don't know what happened but then suddenly the recovery menu showed up. So I picked to just power off so it is just turned off now and no longer in a boot loop. I don't know what to do from here. I won't turn it back on until I get advice on what to do next.
If you just want to fix it without worrying about losing data, see if you can get it onto download mode and full a full stock flash with all 4 firmware files in Odin.
If anything is corrupt, Odin should give you an error message which might be enough of a clue as to where to look next.
OK so I flashed it once and it didn't work, it was still stuck. After that I just gave up on keeping anything and wiped all data. I flashed it a second time and it still got stuck, but after about 10 restarts it finally worked. However it is now on the T-Mobile firmware instead of the Metro PCS one and also I am having weird problems now. I would like to go back to the Metro PCS however I cannot find any firmware for a G930T other than T-Mobile. The problems I have experienced so far is the auto brightness does not work anymore, I have to manually set brightness even when it is switched on, the screen turns on for a few seconds when it's done charging now, and also I restarted my phone to fix an app and then it got stuck in a loop again. It took 10 restarts then worked again, but that is still a problem. I don't even know if I should still be wasting my time trying to fix this. I really don't want to buy a new phone right now but I also feel hopeless in fixing this one.