Hi:
I have a HTC sensation 4G. I really like the phone. However, about 3-4 months ago, my phone suddenly switched off. When I restarted my phone, it got stuck on the HTC logo and wouldn't go further and switch off. It would start again, show the white screen with the HTC logo and switch on again. It wouldn't go any further and kept doing so in a loop. I thought there could be 2 possible reasons for the same: 1.) software issue or 2.) Hardware issue. I was pretty sure it was not a software issue as I had not made any changes in the software. I took it to a HTC repair center. The repair charges they were asking were freakingly high (300$!!). I didn't get it repaired from them. However, they gave me the exact reason of the problem. They said that it was a hardware issue and often happens with the phones when battery of the phone is removed while the phone is running. If this is done multiple times, such an issue can arise. I had done it multiple times before the phone had stopped working. I then got the phone repaired from another shop paying a third of the price. He didn't give any guarantee if the phone works. But the phone started working after the repair.
Very recently though, I was using my camera and as soon as the flash came on, the flash light got stuck. The phone was, however, working. But I couldn't get the flash to switch off. So I thought of restarting my phone. The phone switched off and when it turned on, it had the same problem. It is stuck in a loop on the HTC logo screen. I think this could be a software problem. What can i do to repair it?
Another thing I want to mention is that I am unable to go even in the recovery. When I try to go in to the recovery, it switches off and shows the HTC screen again. On one occasion when I tried to go into recovery from the boot screen, it showed a message that the battery voltage is low, please change the battery immediately. So i thought it is a battery problem and I looked up on the internet to find a solution. Somewhere I read that sometimes the gold plated contact points on the battery get scratched and corrosion happens. One solution was to clean the corrosion and try again. I did but didn't work. Also, when I try to charge the phone (because the battery voltage is low), even if the phone is switched off, its starts up again automatically without pressing the power button. Then it keeps going in the loop.
I don't know what the problem exactly is. Do i need to change the battery? I am running official HTC ICS ROM. Please help me with a solution.
It will be of great help. Thank you!!
Android lover
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
Okay, so, I know I am not the only one with this issue. At the same time I know not ALOT of people have this issue. Lets get right down to it, I bought a Note I717 from someone who claimed that it was stuck in a bootloop. Well, I turned it one when I got home after doing a factory restore and it came on and stayed on. I thought I had fixed it until the battery died.
Symptoms:
Boots up fine
Stays on for around 2 minutes
Freeze then Reboot
Happens every time. I have tried to restore stock firmware, have tried custom roms. Have rooted it, unrooted it. Battery holds a charge and is perfectly fine. Power button is NOT stuck.
There have been 2 times I have got it to come on and stay on for like 12 hrs then it will freeze and cut off, then start the rebooting sequence all over again. Anybody think they can help me out?
Lemon Kush said:
Okay, so, I know I am not the only one with this issue. At the same time I know not ALOT of people have this issue. Lets get right down to it, I bought a Note I717 from someone who claimed that it was stuck in a bootloop. Well, I turned it one when I got home after doing a factory restore and it came on and stayed on. I thought I had fixed it until the battery died.
Symptoms:
Boots up fine
Stays on for around 2 minutes
Freeze then Reboot
Happens every time. I have tried to restore stock firmware, have tried custom roms. Have rooted it, unrooted it. Battery holds a charge and is perfectly fine. Power button is NOT stuck.
There have been 2 times I have got it to come on and stay on for like 12 hrs then it will freeze and cut off, then start the rebooting sequence all over again. Anybody think they can help me out?
Click to expand...
Click to collapse
whn i had a similar issue, the answer turned out to be that i was overclocking. if you are overclocking/undervolting it can cause random reboots.
Out of nowhere my phone started to restart randomly to the point when it looks like a boot loop. Also I have noticed that those boot loops occurs when my battery is below 50% and when I'm charged to 100% I can boot but after 3-4 minutes it goes to restart anyway. Also when I have turned off WiFi, GPS and BT there are no more reboots so far but I'm not able to turn on back WiFi, GPS or BT unless I will pull battery out and put back and turn on them back quickly but then I'm getting back those random restarts.
I'm on a stock but rooted Lollipop with TWRP.
I saw some threads with similar issues and were related to a battery but in those cases phones stay up when were charged or a battery pack and mine has still if is connected to the wall or a battery pack.
Any clue what is going on?
Thanks
OK now I'm not able to get to the Factory Reset screen (Power + Vol Down). Any clue on that?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
So now I have issues to get started that phone. Mostly goes into boot loop mode (LG logo, LED flashes few times and reboots). Sometimes it goes beyond LG logo - to AT&T logo and reboots there. When I pass that I have a luck and I can get phone to work but I need to disable WiFi, BT and NFC.
Also I have got into MiniOS and run that ATT testing tool which came all passed except one - OTG or something like that failed.
Any help?
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
Click to expand...
Click to collapse
try a new battery @TheNetwork @Scyzor
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Click to expand...
Click to collapse
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
harffmut said:
try a new battery @TheNetwork @Scyzor
Click to expand...
Click to collapse
Zahr said:
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have got two batteries week ago. One original replacement (3000 mAh) and some OEM (3500 mAh) - both were failing into boot loop until I will get to be lucky enough after full charge over the night and boot to the system and leave it as is but last Tuesday my screen started to fade away instead of turning off and after that it went again into boot loop.
But I don't have any problems booting into recovery (TWRP) or DL mode. Strange...
Scyzor said:
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
Click to expand...
Click to collapse
This happens with all phones as devs are like anyone else. They upgrade their devices and focus on the new device. Some sell their old device to offset the cost of the new one. Development takes time and many of these individuals have lives outside of development. They have jobs and/or families. What they do is for the fun of it and so they can get more of what they want out of Android. If they share it, then that is up to them and does not mean they owe support to those who choose to use their ROM(s). The fact that a development site lets non developers use ROMs that are uploaded is a privilege and I'm thankful for it. I'm not a developer but have been able to use info from here to get more of whst I want from my phones.
Strange problem. Battery full, no problems there. After getting mad about sdcard not being recognized, even with cm 12.1 , I decided to install cm 6.01 rom(marshmallow) nightly. Installed, changed launcher to nova prime, right gapps, and installed kernel auditor. Downloaded xposed for marshmallow, rebooted, everything was fine(or so I thought). Two days later, coming back from store, looked at my phone and hit power, to get it out of sleep. That's when everything went wrong. It didn't come back, and no pressing of the power button did anything, I had to battery pull. I rebooted to twrp, and over the next week tried to get it right. Uninstalled cm 6.01 nightly, and put xneon rom on it. Same problem persisted, no boot to the os, or partial boot to the lockscreen. I knew the phone wasn't hard bricked, since twrp was still working, and phone wasn't shutting down to no response. Whenever I tried to boot into the os' , it would still get stuck on startup, though. I read all of the advice to return to stock, using flashtool, or lgup, going into download mode, everthing that I could read up on, and implement. I ran to best buy, and ordered a huawei 5x, and said to myself, I can't fix it. Well, today, I said why don't I short the battery pins, and repeatedly press the power buttons, at the same time( because when i put the battery in, even after 10~15 seconds, it would boot to the lg logo, then fade to non-responsive again). Viola! it booted into the os' , and didn't shut down to unresponsive condition(no power button action, and ultimately, battery pull). It seems everthing was fine, until I used the browser, then condition came back. Battery pull again, and it's working now, haven't shut it down since, so I adjusted the display off time to 30 min. , and turned off power saving modes. I don't know if it's truly fixed, but I thought my phone was going to my archives history drawer(all my other phones still work, but they're underpowered, old os' phones). It may still go there, once I pick up my huawei, but I'm glad to see it still living. Is there some type of time out I'm not aware of? or a shutdown by internal fuse, or reset that's built into the firmware? I've heard of bad screens with this, but didn't think that was the problem, since, when in twrp, it never shut down to being unresponsive, and when twrp shut off screen, it would come back, even after hrs of it on. I want to know if the bootloader has anything to do with this, and by shorting it, cleared the emmc.
I have made a video how it looks on my LG G3:
PS.
Is there flashable CWM for D850? I have heard that TWRP is creating those issues from the video.
Well, based on some articles it looks like a hardware issue mostly related to the overheating and "cold soldering joints". Based on that article most of LG phones may experience that issue:
http://www.androidauthority.com/lg-v10-bootloop-problem-711334/
I have had nothing but problems with the two G3s I have had. One had a broken screen (not its fault) so was retired. One the screen started doing this weird backlight problem. So I swapped out the internals from one into the other. to make one good one. Both the same exact ATT LG G3 D850s.
Worked fine for a year. Then today the phone just turns itself off. So I tried to turn it back on, no response. Remove the battery, turn back on. Looks like it is going to boot, gets to the ATT screen, then loops back to boot again and again.
So I said screw it, everything on it gets backed up daily, so lets factory reset it. No go, it starts to do the factory reset then reboots over and over.
So I said fine, and started to follow this guide:
lgg3root com/lg-g3-root/how-to-unrootunbrick-lg-g3/
I downloaded the proper TOT and DLL files, but when it goes to do the update, it says Model Information CHECKFAIL
Any thoughts? I do not care if I have to put a custom ROM on or whatever, I just need it to work for a few more months.
Thanks!
Update today.
Not sure if this is a battery problem or hardware problem. I do not think it is a software issue. I suspected a battery issue, which is why I tried swapping them before. I have two genuine original LG G3 batteries. One used for a year and one for two years.
I decided to say screw it and see if maybe sitting overnight with the battery out did anything.
I have two batteries, both were at around 70% originally. I think through testing yesterday one had gotten up to 80%. I had tried swapping them at various times yesterday while troubleshooting. I put one in again. It came up and started optimizing apps like it was doing the reset. I said ok great! But then it crapped out after like 5 or 6 apps. So I put in the other battery, and it made it through the entire process and has been staying on without issue.
The thing is, it would stay on the DOWNLOAD MODE without issue before, so I am not sure it is a battery problem. But I am wondering if there is a problem now with both batteries where if it gets below say 70% it doesn't work.