Hello,
I recently changed the LCD of a S6 edge. I installed it and turned it on and it booted up fine. I went to make sure everything was working. While I was playing music it would restart. I thought it was odd, so i was waited til it came back on and started using other apps. Same thing..restart. So, i booted to safe mode. Same thing...restart.
So, I tried factory resetting. After that, it would just get stuck in a endless restart loop cycle.
I have also tried reinstalling the OS using Odin. I ran Odin and it said everything passed. The phone restarts and goes to installing updates.
It gets to 32% every time then it says "erasing". After a few seconds of displaying "erasing" it just starts its endless reboot cycle again.
**EDIT: I should add that it never restarts when it's in the download manger.** So, that makes me think its a OS issue.
*EDIT#2: This is a good video. I did all of this. Got to the 9 minute mark and where his comes on, mine restarts again.
Any help?
Thank you!
back in the latter days of flashing S4 custom roms there would be the occasional user who couldn't boot and it turned out that there was some detail in the roms that didn't work with some 3rd party LCD screens.
check the reviews for what you bought and see if you are alone or not.
the issue with those screens was fixed by the devs so if nothing else you might be able to go custom with it.
3mel said:
back in the latter days of flashing S4 custom roms there would be the occasional user who couldn't boot and it turned out that there was some detail in the roms that didn't work with some 3rd party LCD screens.
check the reviews for what you bought and see if you are alone or not.
the issue with those screens was fixed by the devs so if nothing else you might be able to go custom with it.
Click to expand...
Click to collapse
Hi,
thank you for your reply. I learned about all of this last night lol. so, i'm not exactly sure what you mean. I bought the LCD+frame from Ebay. It stated it was pulled from a working unit.
Could a bad battery cause all these issues? I notice when i power down (only way I can power down is if I Hold POWER+VOL DOWN and select power down) that the LED light stays on.
Hello, could someone delete this thread. I have posted a more detailed thread on this issue.
if it says it's an LCD screen it's not an original part. my point was that some people have had issues booting up roms because of screens.
that was something that was fixed in custom roms though so if you can't another solution a custom rom that works with 3rd party LCD displays might be an option to consider.
Related
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.
So I just picked up this s3, it will turn on but shuts off halfway through galaxy splash screen. Boots into recovery and Odin mode just fine, prior to purchasing we plugged it in, got it to boot and did a factory reset, to clear privious owners data, and it went fine, did it reboot and took me to setup. Satisfied with its performance I went ahead and made the purchase, upon unplugging it shut off, as I expected if battery was indeed shot. What gets me is I let it charge, unplugged, booted, shut off at splash screen, plug back in and says its still fully charged. Boot into recovery and indeed, 100% battery. I haven't gotten around to flashing twrp or rooting, was wondering if anyone has experienced this?
Sent from my HTC Desire HD using XDA Free mobile app
Anyone got any ideas? Just got home, am able to boot past the splash screens as long as its plugged in but once I try to start using it (going through setup/tutorial) it ends up rebooting, computer can read phone in odin/recovery modes but don't see a point reflashing stock firmware if this phone was never touched, completely stock unrooted, just a factory reset upon purchasing. I've read somewhere about a stuck power button, is that common among the Verizon s3? If so ill pop it open and check it out.
Phone was already on 4.4 when I got it, I downloaded and flashed stock firmware (ne1) via odin, I got the whole way to the end of setup and as soon as it started loading the homescreen it cut off and went to the green battery charge icon when phones off. Everytime I try and boot it, she'll go through all the splash screens and ill catch a very short glimpse of the homescreen and it shuts off. Also it HAS to be plugged in still, or else it just shuts off halfway through initial "galaxy s3" splash.. I don't understand...
Have you tried a new battery? Even if it's plugged in it won't run if the battery is completely shot.
Also if you indeed have a Verizon S3 on NE1 firmware you will not be able to install TWRP as the bootloader is locked. You will be able to root, however.
Muhff said:
Anyone got any ideas? Just got home, am able to boot past the splash screens as long as its plugged in but once I try to start using it (going through setup/tutorial) it ends up rebooting, computer can read phone in odin/recovery modes but don't see a point reflashing stock firmware if this phone was never touched, completely stock unrooted, just a factory reset upon purchasing. I've read somewhere about a stuck power button, is that common among the Verizon s3? If so ill pop it open and check it out.
Click to expand...
Click to collapse
The stuck power button seems to affect users IN recovery mode too, it seems like phone randomly reboots in recovery.
You can pick up a new battery from amazon for like $7 I think, its been a while, but might be worth it.
It could also maybe be some issue in transferring charge from the battery to the main board, meaning maybe bad connections/contacts.
Is it plugged in when it reboots, because that may indicate poor contacts, since the charger alone isn't able to power the device (ex I used to be able to take out my LG Ally battery when plugged in and it functioned fine).
Good luck!
Sent from my SCH-I535 using XDA Free mobile app
XdrummerXboy said:
The stuck power button seems to affect users IN recovery mode too, it seems like phone randomly reboots in recovery.
You can pick up a new battery from amazon for like $7 I think, its been a while, but might be worth it.
It could also maybe be some issue in transferring charge from the battery to the main board, meaning maybe bad connections/contacts.
Is it plugged in when it reboots, because that may indicate poor contacts, since the charger alone isn't able to power the device (ex I used to be able to take out my LG Ally battery when plugged in and it functioned fine).
Good luck!
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
Turns out it was the battery all along, found a battery that the contacts matched on (even though it was only 1650 mAh) wedged it in with paper and it booted just fine. Found a battery on craigslist that night and has worked great ever since, unfortunately PO had already updated to 4.4.2 so im stuck with that Thanks for the response, I just found it odd that the battery held a charge just didn't work.. maybe I should check the contacts on that and clean them.
Muhff said:
Turns out it was the battery all along, found a battery that the contacts matched on (even though it was only 1650 mAh) wedged it in with paper and it booted just fine. Found a battery on craigslist that night and has worked great ever since, unfortunately PO had already updated to 4.4.2 so im stuck with that Thanks for the response, I just found it odd that the battery held a charge just didn't work.. maybe I should check the contacts on that and clean them.
Click to expand...
Click to collapse
I'm glad you fixed the problem!
Sent from my SCH-I535 using XDA Free mobile app
Before I start I will say I am rooted and have tried multiple different ROMs to make sure that's no the problem. Starting last Saturday, my phone would randomly turn off. I never saw it turning off until today though. I just thought that somehow it had turned itself off in my pocket. However, today I caught it turning off. Right before it shut down, a logo of a gray battery with a USB cable going into it with an exclamation point in a triangle off to the side appeared. Then, when I tried to turn it on, the same symbol showed up and I couldn't even get to the LG logo. An hour later when I tried again, it booted up, no problem. At the time, I was running illusion rom with Rin kernel. After several other times of the phone turning off with the logo and not being able to turn it back on for a half of an hour, I decided to go back to my old backup of illusion to see if that was the problem. The random turn offs persisted. Worried, I flashed the latest cm12 nightly. Things were going great until just 20 minutes ago where the phone turned off accompanied by the symbol. Whaf does it mean? What should I do? Hopefully my phone's not broken cuz I don't think at&t of lg will accept a phone that's rooted and has seen multiple Roms.
update
Today the problem has persisted and the shut downs have occurred at exactly the same times as they did yesterday. I think I might have to use the "return to stock" stuff and send it to LG. I'm pretty sure this is an internal hardware issue since I have tried multiple different Roms without installing any apps and the problem persists. I am going to call LG now and see if they'll replace it. I've also tried a spare battery so that certainly isn't the problem. I'm confused. If anyone knows what to do, please share.
I would flash tool back to stock and start over. That really does fix a lot of weird problems. It has for me anyway.
Just tried reflashing stock. No success.... sending it in to LG next Tuesday since Monday is a Holiday and its still semi-functional so i'll use it during the weekend. Hopefully they wont charge me for it.
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 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.