A few days ago, I flashed a 4.4.2 rom and kernel. I noticed that it was randomly rebooting so I went ahead and flashed another rom, this time without a new kernel. Everytime I flashed I did a wipe of the device. When I did this the Galaxy Note 2 splash screen would come up then the rom boot logo. But then it would go back to the splash screen and the boot loop would continue. I ultimately discovered that the phone would get past the boot loop sequence if either plugged in via USB or AC. I set up my phone thinking it was cool but once I unplug it, and start using the phone, it reboots itself and starts up the boot loop cycle again. I've gotten fed up to the point that I unrooted the phone back to a stock 4.3 rom thinking that might solve the problem but even with the stock rom the boot issue persisted. I've since then used Odin to put new recoveries in hopes that this could be the issue but still the same problem persists. I've had to start carrying around my laptop with me to and from work just to have the phone plugged in because otherwise it will eventually shutoff and start the bootloop. I'm usually pretty good at solving these issues but right now I'm without any answers. I haven't checked to see if possibly it could be a battery issue but I haven't had an opportunity to find someone with a Note 2 to try out this theory...has anyone had somewhat remotely close to a similar issue and if you have, did you solve it? Someone help...lol otherwise my Note 2 may have seen it's final days although I'm not in the market of finding another phone right now.
bkjay78 said:
A few days ago, I flashed a 4.4.2 rom and kernel. I noticed that it was randomly rebooting so I went ahead and flashed another rom, this time without a new kernel. Everytime I flashed I did a wipe of the device. When I did this the Galaxy Note 2 splash screen would come up then the rom boot logo. But then it would go back to the splash screen and the boot loop would continue. I ultimately discovered that the phone would get past the boot loop sequence if either plugged in via USB or AC. I set up my phone thinking it was cool but once I unplug it, and start using the phone, it reboots itself and starts up the boot loop cycle again. I've gotten fed up to the point that I unrooted the phone back to a stock 4.3 rom thinking that might solve the problem but even with the stock rom the boot issue persisted. I've since then used Odin to put new recoveries in hopes that this could be the issue but still the same problem persists. I've had to start carrying around my laptop with me to and from work just to have the phone plugged in because otherwise it will eventually shutoff and start the bootloop. I'm usually pretty good at solving these issues but right now I'm without any answers. I haven't checked to see if possibly it could be a battery issue but I haven't had an opportunity to find someone with a Note 2 to try out this theory...has anyone had somewhat remotely close to a similar issue and if you have, did you solve it? Someone help...lol otherwise my Note 2 may have seen it's final days although I'm not in the market of finding another phone right now.
Click to expand...
Click to collapse
I would suggest that you try another battery. Kinda sounds like an issue with the device not getting proper power supply. If I were you I would try finding a friend or coworker who has the same device and try using theirs. If it boots and runs then a replacement battery is all you need. I have had this issue with a previous phone (HTC 3d) but not this device.
jlmancuso said:
I would suggest that you try another battery. Kinda sounds like an issue with the device not getting proper power supply. If I were you I would try finding a friend or coworker who has the same device and try using theirs. If it boots and runs then a replacement battery is all you need. I have had this issue with a previous phone (HTC 3d) but not this device.
Click to expand...
Click to collapse
Thank you for the reply..I will check to see whom may have a Note 2 at work. The ones who did have other phones now I believe. I know of one co-worker who has a Note 3 but not sure if that would be something that I could try..I'll report back tomorrow with my findings...
Yeah I doubt the N3 has the same battery but hopefully you can find someone.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Good morning guys,
Last night, i was just using my phone like normal when it froze, crashed, and began to bootloop.
I've tried battery pulls, I've tried to factory reset using the volume down + power combo, I've tried to wipe cache and enter safe mode but none of this worked
I was on 10b firmware but since none of the above worked, I tried to KDZ to a stock 11a which still keeps my phone at a bootloop. All I see if the LG logo at startup and a crash.
do you have any suggestions on how I can try to fix this? according to reddit this random bootloop has been happening to multiple people
thanks in advance for your help
It started happening to me, as well, over the weekend. My phone crashed and started bootlooping, stuck at the LG startup screen where it stalls for a few seconds and then goes black. Every now and then it will boot up properly, but the phone crashes after about two minutes and starts bootlooping again. I cannot manage to wipe the phone because it so seldom boots properly. I noticed that the phone gets very hot. I suppose that I will need to return it to Verizon for warranty replacement, but I hate having so much data on the phone when I return it. I was doing nothing unusual with the phone when this started happening.
Katmeat said:
It started happening to me, as well, over the weekend. My phone crashed and started bootlooping, stuck at the LG startup screen where it stalls for a few seconds and then goes black. Every now and then it will boot up properly, but the phone crashes after about two minutes and starts bootlooping again. I cannot manage to wipe the phone because it so seldom boots properly. I noticed that the phone gets very hot. I suppose that I will need to return it to Verizon for warranty replacement, but I hate having so much data on the phone when I return it. I was doing nothing unusual with the phone when this started happening.
Click to expand...
Click to collapse
yeah it's definitely weird. I was rooted on 10b holding out for a bootloader exploit down the line.
I called up verizon and theyre shipping me a new g4 since it was still under the 1 year warranty. I hope it's still rootable with the firmware it'll ship with
Same here
Hey guys! I thought I'd reply instead of making a new post because I think I'm in the same boat. My dads phone has just started doing this, but the weird thing is he wasn't rooted! I was able to get it to the recovery and tried the wipe cache and safe mode options, it didn't do anything.. I then tried flashing the kdz but no luck..
Hope some of the smart folks here can help us!
-Travis
I was fortunate to get it into download mode so I kdz it back to 11a stock so as to wipe all data, thankfully. The stock reset made no difference, as it still would rarely boot, and even when it did boot it would crash fairy quickly. My warranty replacement should arrive tomorrow.
Katmeat said:
I was fortunate to get it into download mode so I kdz it back to 11a stock so as to wipe all data, thankfully. The stock reset made no difference, as it still would rarely boot, and even when it did boot it would crash fairy quickly. My warranty replacement should arrive tomorrow.
Click to expand...
Click to collapse
yup, i kdzed up to 11a and it went from modified status to official so hopefully that wiped everything on my phone too. My new one will be coming in tomorrow
I just received my warranty replacement, and it is an 11a factory refurb device that looks like new. No noticeable screen lag thus far, but it is running awfully warm as it restores all my apps and some data from the Verizon Cloud.
Katmeat said:
I just received my warranty replacement, and it is an 11a factory refurb device that looks like new. No noticeable screen lag thus far, but it is running awfully warm as it restores all my apps and some data from the Verizon Cloud.
Click to expand...
Click to collapse
Is there any downside to refurbished devices?
pfizzle said:
Is there any downside to refurbished devices?
Click to expand...
Click to collapse
I think not, and I actually prefer buying factory refurbs in most cases when possible because you are assured of the product being carefully inspected. In this case, my phone looks brand new and is performing just fine. The initial heat concern has gone away as the phone has settled in.
Please Help!!!!!
I'm trying to help my sister out who is in Ecuador right now. Her phone was a little slow today and kept going to the red verizon sign - so she turned it off and took the battery out.... when she turned it on it said the SD card is blank. She has 800 pics on it from her trip and is wondering if there is anything to get them back???? Please help!!!! Any suggestions would be helpful!
weird i had the same thing happen a few days ago also...using new phone now.
This issue happened to me out of no where last week and had a replaement sent. Wasn't rooted
Sent from my VS986 using Tapatalk
same problem here ...
rooted device. nothing special today .. and then: bootloops.
When i remove the battery for a longer time, sometimes the g4 boots properly. But after a few minutes it'll bootloop again.
Any ideas?
FootballFan141 said:
Hey guys! I thought I'd reply instead of making a new post because I think I'm in the same boat. My dads phone has just started doing this, but the weird thing is he wasn't rooted! I was able to get it to the recovery and tried the wipe cache and safe mode options, it didn't do anything.. I then tried flashing the kdz but no luck..
Hope some of the smart folks here can help us!
-Travis
Click to expand...
Click to collapse
What's the manufacturing date of the phone that failed? I'm trying to figure out if it's just a matter of time (the May ones failed first, then June), or if it's only May boards with the issue.
Hi you clever people, I wonder if anyone had any ideas or pointers please. I've been on an older Eragon for some time and decided to update the other day, went to Eragon 9.9 and afterward touch screen was inoperative. Power button seems to respond with a delay also. It's complaining about anti-theft too (I had set that up a long time ago and can't get rid). Anyway I can get into recovery no problem (Philz) done every reset you can imagine and no improvement. Used the flashtool and original rom and the fault is still apparent so I'm stuck now. Is this destined for the bin?
Thanks for reading.
Regards
J
So my mom's G3 started acting weird a couple weeks ago, it would randomly shut down but could be started without big problems. However yesterday it shut down and when we tried to restart it it became stuck in a bootloop. I've thought about hard reset but my mom has some pretty important stuff on it and prefers not to lose it. I've also thought about kdz flash but since I'm not sure about her phone's current firmware (i'm sure that it's lollipop, but I don't know which exact version) I can't do anything.
How can I solve this, or, at least, know which exact firmware is the phone running ?
By the way it's a 100% stock phone, no root no recovery, nothing.
Thanks in advance.
metamoq said:
So my mom's G3 started acting weird a couple weeks ago, it would randomly shut down but could be started without big problems. However yesterday it shut down and when we tried to restart it it became stuck in a bootloop. I've thought about hard reset but my mom has some pretty important stuff on it and prefers not to lose it. I've also thought about kdz flash but since I'm not sure about her phone's current firmware (i'm sure that it's lollipop, but I don't know which exact version) I can't do anything.
How can I solve this, or, at least, know which exact firmware is the phone running ?
By the way it's a 100% stock phone, no root no recovery, nothing.
Thanks in advance.
Click to expand...
Click to collapse
Many people has such problem mine one able to make it boot again by plugging in to a charger, still it will still reboot frequently, my friend fixed his by replacing motherboard while some others said it is related to battery
I've tried plugging in the charger but never thought of the battery.
I'll try switching batteries, thanks for advice.
UPDATE: I could get the phone on again by switching batteries, thanks a lot !
If I flash a new firmware can the old battery work again ?
metamoq said:
I've tried plugging in the charger but never thought of the battery.
I'll try switching batteries, thanks for advice.
UPDATE: I could get the phone on again by switching batteries, thanks a lot !
If I flash a new firmware can the old battery work again ?
Click to expand...
Click to collapse
I.don't think it is related to Rom as I am using stock MM
We're going to buy a new battery, hope this fixes it for good.
Thanks for your help.
Heya folks,
So my HTC 10 just randomly crapped out on me a few weeks ago. Been trying a few things to try to flash a new ROM on there, but I'm not having much luck and need advice. I was using my phone like I would any other time and all of a sudden the phone froze and restarted, but when it restarted it was taking forever to load back up (was just stuck at the HTC logo). I tried turning it off and on again and realized the thing was bootlooping on me. It wouldn't boot into system, download, recovery, nothing.
Now, here's the issue. My phone's S-ON and the bootloader is Locked. I've never done anything to the software on it before (but for some reason the software status is "Modified", which is weird. I did buy this phone used, so that could mean something, but I've never seen a modified software status on a bootloader that was not unlocked). The symptoms are pretty weird. I tried flashing the ROM using an official HTC RUU EXE, but the thing keeps saying that my phone is below 30%, and when I charge the phone it always starts charging at 22% (all the more reason I think the software is just completely kaputs). I found this thread where people were talking about the SD Card solution, but I'm quite sure the only way this would work is if my bootloader is unlocked.
So what do you guys think? Am I in a catch 22? Am I missing something? Any and all replies or questions would definitely help.