Switched phone on after work, phone powers up, boots up and then freezes after around 20 secs then switches off and re-boots, the process then starts again over and over again.
I've tried deleting cache, master reset, safe mode, simulated battery reset which does not work. I let the battery run flat by putting the phone into download mode and then recharged the battery but still nothing. The phone seems stable only in download mode.
I managed to re-install stock 7.0 firmware via Odin. Firmware installs fine, phone boots up and then freezes on welcome screen and then boots up again. I then tried 6.0.1, again installs fine, I get the welcome set up screen but after a 20 odd secs freezes up again.
The phone is less than two years old. Samsung service centre warranty job? Thanks.
Yes. Mine had also freezing and reboot issues, Sammy changed the Mainboard
The phone is less than two years old. Samsung service centre warranty job?
Click to expand...
Click to collapse
Same problem after 5 months.
Yes get it back to service centre
guys this sounds like the same issues the lgg4 was having with the ilapo bootloop also a snapdragon
had bad solder points on the big cores and they would come loose over time and basicly the phone was stuck in a infinite loop
Related
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.
This is my story that happened with my LG G2
I recently purchased a LG G2 F320L, a refurbished one, from aliexpress(I think this was the biggest mistake of all)
I got the phone, I started using it, used it for 20 minutes and just installed antutu benchmark and ran the app and started the benchmark.
Firstly, I'd like to mention that the phone just got warm, just like other phones, during the test. While the multicore performance test was going on, the phone turned off, all of a sudden (Battery was as low as 9% when I started antutu benchmark). I thought that, it was because the battery was too low to run a benchmark app and turned on the phone back and waited, it just showed me the LG logo for 5 seconds, powered off, ended up with a bootloop. :crying:
I thought that the OS or the bootloader got corrupted and stuck and also thought that I could easily fix it by flashing boot.img or the original .kdz using LG flashtool.
I connected the phone to the PC, it was charging from 9% (That means, low battery isn't the reason for this problem). I waited until it charged till 25% and tried turning the phone on again, but, the same bootloop happened again. I downloaded the .kdz file for my exact model and prepared to flash it using LG flash tool. Unfortunately, the phone came out of download mode (Whilst the flashing was going on) and started with the bootloop again. I really got scared cause the flashing was interrupted indefinitely. I didn't know what to do and I just googled how to enter factory reset mode and I finally entered factory reset mode and chose to reset the phone completely. But, it has happened for a while and continued with the same kind of beat-up (But I was able to enter the factory reset mode later on, though) I was pretty much scared at this time and I gave the phone to one of my friends. I showed him the factory reset mode that was still working, but not useful, and I tried resetting 3 to 4 times but couldn't come out of the bootloop. But, suddenly I couldn't enter factory reset mode and the bootloop became pretty much faster that before (Just showed me the LG logo for 3 seconds and rebooted with the same bootloop). Now, no factory reset mode, download mode, and no charging either.
I got to know that it was a really serious hard brick that has ever happened to one's phone!
I handed over the phone to another one of my friends and he dismantled the phone and tried something, then connected to the computer and the computer detected the phone and QHUSB mode was saying 'Searching Windows update' with a loading symbol. He just stopped it there and told me to take it to a good service center (An expert, of course), and he also told me that I was supposed to ask him, to make the QHUSB mode work.
But, after he gave me the phone back, the bootloop was still happening, just like before, but, instead of LG logo, it was showing some bluish white lines on the 2/4 on the screen.
I haven't got time to go to a service center till date, as they might cost me more than I invested on my phone.
This is really serious problem and I need to enter the QHUSB mode and I need to flash the stock firmware cleanly. Please anyone give some time to read this thread and help me out in this situation. AGAIN, I have used the phone for like, just 20 minutes when it was in a working condition.
So, I request any experts to help me out, suggest me the solutions.
Sorry for my bad English, though.
Thanks in advance.
SumanthBv said:
This is my story that happened with my LG G2
I recently purchased a LG G2 F320L, a refurbished one, from aliexpress(I think this was the biggest mistake of all)
I got the phone, I started using it, used it for 20 minutes and just installed antutu benchmark and ran the app and started the benchmark.
Firstly, I'd like to mention that the phone just got warm, just like other phones, during the test. While the multicore performance test was going on, the phone turned off, all of a sudden (Battery was as low as 9% when I started antutu benchmark). I thought that, it was because the battery was too low to run a benchmark app and turned on the phone back and waited, it just showed me the LG logo for 5 seconds, powered off, ended up with a bootloop. :crying:
I thought that the OS or the bootloader got corrupted and stuck and also thought that I could easily fix it by flashing boot.img or the original .kdz using LG flashtool.
I connected the phone to the PC, it was charging from 9% (That means, low battery isn't the reason for this problem). I waited until it charged till 25% and tried turning the phone on again, but, the same bootloop happened again. I downloaded the .kdz file for my exact model and prepared to flash it using LG flash tool. Unfortunately, the phone came out of download mode (Whilst the flashing was going on) and started with the bootloop again. I really got scared cause the flashing was interrupted indefinitely. I didn't know what to do and I just googled how to enter factory reset mode and I finally entered factory reset mode and chose to reset the phone completely. But, it has happened for a while and continued with the same kind of beat-up (But I was able to enter the factory reset mode later on, though) I was pretty much scared at this time and I gave the phone to one of my friends. I showed him the factory reset mode that was still working, but not useful, and I tried resetting 3 to 4 times but couldn't come out of the bootloop. But, suddenly I couldn't enter factory reset mode and the bootloop became pretty much faster that before (Just showed me the LG logo for 3 seconds and rebooted with the same bootloop). Now, no factory reset mode, download mode, and no charging either.
I got to know that it was a really serious hard brick that has ever happened to one's phone!
I handed over the phone to another one of my friends and he dismantled the phone and tried something, then connected to the computer and the computer detected the phone and QHUSB mode was saying 'Searching Windows update' with a loading symbol. He just stopped it there and told me to take it to a good service center (An expert, of course), and he also told me that I was supposed to ask him, to make the QHUSB mode work.
But, after he gave me the phone back, the bootloop was still happening, just like before, but, instead of LG logo, it was showing some bluish white lines on the 2/4 on the screen.
I haven't got time to go to a service center till date, as they might cost me more than I invested on my phone.
This is really serious problem and I need to enter the QHUSB mode and I need to flash the stock firmware cleanly. Please anyone give some time to read this thread and help me out in this situation. AGAIN, I have used the phone for like, just 20 minutes when it was in a working condition.
So, I request any experts to help me out, suggest me the solutions.
Sorry for my bad English, though.
Thanks in advance.
Click to expand...
Click to collapse
Hi,
Try looking here:
http://forum.xda-developers.com/showthread.php?t=2475045
and maybe posting your question in there
Good luck!
Hello, everyone.
I'm using an OPO since october 2014 and I had no intention of buying a new phone in the near future. But now I'm worried about it.
Abouth three weeks ago, my phone started to freeze and reboot. At the time I was using sultan's latest ROM. I thought the problem was the latest updates and, as I wanted to test Nougat, I decided to download Lineage.
To my surprise, I kept having random freezes and reboots.
While reflashing ROMs and changing kernels, I had some reboots. Yes, self rebooting while on recovery.
So I decided to get it totally back to stock and re-start fresh.
Phone froze and restarted on COS initial config. And, after that, rebooted again when updating Gmail apps.
During these three weeks, it kept on with no reboots for, at max, around 40 hours.
Is there any way I can test my phone to determine if it's a hardware issue? It all makes me think it is. :/
Any clue is welcome.
Thanx.
Cappelletti said:
Hello, everyone.
I'm using an OPO since october 2014 and I had no intention of buying a new phone in the near future. But now I'm worried about it.
Abouth three weeks ago, my phone started to freeze and reboot. At the time I was using sultan's latest ROM. I thought the problem was the latest updates and, as I wanted to test Nougat, I decided to download Lineage.
To my surprise, I kept having random freezes and reboots.
While reflashing ROMs and changing kernels, I had some reboots. Yes, self rebooting while on recovery.
So I decided to get it totally back to stock and re-start fresh.
Phone froze and restarted on COS initial config. And, after that, rebooted again when updating Gmail apps.
During these three weeks, it kept on with no reboots for, at max, around 40 hours.
Is there any way I can test my phone to determine if it's a hardware issue? It all makes me think it is. :/
Any clue is welcome.
Thanx.
Click to expand...
Click to collapse
Get your device checked at a local shop. Looks to me like a battery or logic board issue.If it's battery then you can get a replacement but if its logic board then yes,you should consider buying new device.
Mr.Ak said:
Get your device checked at a local shop. Looks to me like a battery or logic board issue.If it's battery then you can get a replacement but if its logic board then yes,you should consider buying new device.
Click to expand...
Click to collapse
I'm fairly sure that there is no local shop that could check it.
Right now, before checking this thread, I let the battery completely drain and now it's on the wall recharging. I'll enter recovery when it's 100% charged and do a factory reset. Then install everything back and use it for a few hours.
Let's see it that helps.
Thanx for the reply.
- phone battery completely drained
- phone battery completely charged
- booted to recovery and factory reseted
- initial COS configuration done without any freeze and/or reboot
- updating Google Apps
So far, so good.
And it rebooted twice, during apps update.
Although it updated main Google apps, it was not supposed to reboot.
:/
Hmmm...if random reboot but able to boot normally afterwards then you need to tweak the kernel a little bit but if is random reboot and then stuck at 1+ logo or bootanimation then your battery is dying....
to check whether the battery is dying just wait until next reboot...if it stuck on 1+ logo or bootanimation, turn off the phone completely then plug in the charger...it it charge for 5 minutes in offline mode then turn it on while the charger still connected...if its boot normal then it is confirmed that the battery is dying...replace a new battery as quick as possible...
I've been living with random freeze+ automatic reboot since COS13 it's a PITA but doesn't cost me anything to wait 1min until full reboot, only problem are lucky patch on boot which take longer but nothing that bad. I was never able to troubleshot the issue, usually happens to me when I receive some notification I see the LED and try to unlock but the phone stays blacked out (even though it's clearly on since notifications are shown on the LED) until I force reboot.
Over the years I tried insane amount of ROMs and kernels, nothing changed, adding to that the fact that 10% of the times when i put it in charge (original charger+cable) says 7h or 6h until full charge (and I actually have to wait all that time), I just have to unplug and try again until it fixes. It's not the charger because I tried it with other phones, so I started to assume my problems are the small board with the charging board + battery. But I never had the willing to change it. I'm "fine" with how it works.
iPusak Gaoq™ said:
Hmmm...if random reboot but able to boot normally afterwards then you need to tweak the kernel a little bit but if is random reboot and then stuck at 1+ logo or bootanimation then your battery is dying....
to check whether the battery is dying just wait until next reboot...if it stuck on 1+ logo or bootanimation, turn off the phone completely then plug in the charger...it it charge for 5 minutes in offline mode then turn it on while the charger still connected...if its boot normal then it is confirmed that the battery is dying...replace a new battery as quick as possible...
Click to expand...
Click to collapse
It does not get stuck. At times, it reboots during boot. Some times (rarely) it does that for two or three times and then turns off. But most of the time it freezes, reboots and I can use it normally for hours and hours.
seanwlk said:
I've been living with random freeze+ automatic reboot since COS13 it's a PITA but doesn't cost me anything to wait 1min until full reboot, only problem are lucky patch on boot which take longer but nothing that bad. I was never able to troubleshot the issue, usually happens to me when I receive some notification I see the LED and try to unlock but the phone stays blacked out (even though it's clearly on since notifications are shown on the LED) until I force reboot.
Over the years I tried insane amount of ROMs and kernels, nothing changed, adding to that the fact that 10% of the times when i put it in charge (original charger+cable) says 7h or 6h until full charge (and I actually have to wait all that time), I just have to unplug and try again until it fixes. It's not the charger because I tried it with other phones, so I started to assume my problems are the small board with the charging board + battery. But I never had the willing to change it. I'm "fine" with how it works.
Click to expand...
Click to collapse
I'm "almost" fine with the way it works for me. As most of the time it's fully operational.
I found a OPO with damage screen for sale here. He guy didn't want too much $ for it. I bought it and will receive next week. Will try to swap logic boards.
Let's see what happens.
Was able to have logcat running when the device froze (during game) and rebooted.
Is anyone able to see any error on the log that could make the device freeze and reboot?
Got the broken screen OPO two days ago. Yesterday my phone was impossible to be used. Rebooting like hell.
I swapped logic boards and all is fine. No freezes and reboots (of course, it's pratically another phone). I kept only my screen, housing and battery.
My logic board had a 2.5 sticker on it. The one I got now has a 2.1 sticker. Does anyone know what's that about?
Hello,
I am quite familar with samsung devices and flashing etc. but my friends phone died today I suppose. At some point it got stuck and got into a bootloop. After some reboots it tried to find a ota update.zip, but there was none. After some tries I got into download mode, but flashing a stock image (was stock before as well, never seen root or something) did help at first (it booted, we backupped some stuff) but at some point it got stuck into bootloop again.
This time, when going into recovery, it tried flashing a firmware again, however this ended badly (freeze while flashing). Now it's not even charging anymore. Not a single button combination is working (force reboot, recovery, download mode, ...) and when plugging into a power bank, it doesn't even charge anymore (power bank shows if a device is charging). So it's completely back and unnoticed by odin, adb or fastboot. Does anyone know this problem or have an idea, what we could try? My last idea would be to test a wireless charger, which i sadly do not have at hand.
Thanks!
Cloud2F said:
Hello,
I am quite familar with samsung devices and flashing etc. but my friends phone died today I suppose. At some point it got stuck and got into a bootloop. After some reboots it tried to find a ota update.zip, but there was none. After some tries I got into download mode, but flashing a stock image (was stock before as well, never seen root or something) did help at first (it booted, we backupped some stuff) but at some point it got stuck into bootloop again.
This time, when going into recovery, it tried flashing a firmware again, however this ended badly (freeze while flashing). Now it's not even charging anymore. Not a single button combination is working (force reboot, recovery, download mode, ...) and when plugging into a power bank, it doesn't even charge anymore (power bank shows if a device is charging). So it's completely back and unnoticed by odin, adb or fastboot. Does anyone know this problem or have an idea, what we could try? My last idea would be to test a wireless charger, which i sadly do not have at hand.
Thanks!
Click to expand...
Click to collapse
If it's not showing any signs of life and will not charge then it's a hardware problem, you should start with the obvious like the usb connector. You are going to have to open the phone and check usb connection, battery connection etc. but it may be easier to take to repair shop.
cooltt said:
If it's not showing any signs of life and will not charge then it's a hardware problem, you should start with the obvious like the usb connector. You are going to have to open the phone and check usb connection, battery connection etc. but it may be easier to take to repair shop.
Click to expand...
Click to collapse
but when it died the first time, i was able to flash the stock image; after it rebooted, it was charging perfectly fine until it died again. from that point on, i was not able to get any sign of life anymore... maybe something crashed that badly and it's still running and i have to wait for the battery to completely drain, so it can do something again? or is the charging process completely hardware dependent, so a crash shouldnt do anything?
Cloud2F said:
but when it died the first time, i was able to flash the stock image; after it rebooted, it was charging perfectly fine until it died again. from that point on, i was not able to get any sign of life anymore... maybe something crashed that badly and it's still running and i have to wait for the battery to completely drain, so it can do something again? or is the charging process completely hardware dependent, so a crash shouldnt do anything?
Click to expand...
Click to collapse
the way to test if it has power but blank screen is to hold power+volume down+home. If it has power it will turn off and boot into download mode
After the Forst Crash all such combinations didnt Seen to work either. Once odin recognized is while having a black screen. At that point I flashed stock :/ but still, not even the led was showing something
A friend of mine owns an s7 and he's told me he has been experiencing random restarts. He gave the phone to me with his phone in android 8 with the stupid bootloader that doesnt allow you to downgrade to android 7. I tried downloading various stock software from sammobile and apparently it would only allow odin to flash firmwares with a label LU2. After flashing every firmware, I'd have a hard time with the setup because the phone would randomly reboot most of the time and would even make the phone unusable as the frequency of the reboots worsen. I didn't wanna give up and told myself I should try to root the phone, install some custom roms, and try to calibrate the battery (root method). Tried it and the phone would not randomly reboot the same as before. In about 11 hrs with screen usage of about 4 hrs to 5 hrs and 30 mins, the phone would reboot a maximum of three times only. With the thought that the phone was fixed, I installed the original firmware again. Low and behold, even before finishing setting up the phone, it would randomly restart again and again. Rooted the phone again and installed havoc os (android 9) and since yesterday to today, the phone only randomly restarted once when i was using the gcam port. It seems to me samsung placed something in the bootloader that would make the phone randomly restart. Or is this just bad luck? It could be a faulty battery or a faulty board but it seems weird that the phone would be fine in odin mode and recovery mode (Stock or twrp). Any thoughts?
Probably a faulty battery or mother board. You would need to get in there to fix it