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/
Related
Hello all, I have an HTC Arrive running LEAD's 7.8 8858 ROM. I've been running this rom since January with very little issues. However, within the last couple of weeks I have been noticing strange things going on with my phone. Some mornings I have woken up and left for work and notice my phone is almost dead, even though I remember plugging it in the night before. Also, as of this week, after a reboot of my phone, the Call button shows Home Service instead of Sprint, but eventually changes over to Sprint. At times I will go to use my phone and see it has put itself in Airplane mode or has a locked sim card logo displayed instead of signal bars. In this case I have to reconnect to the network to regain functionality.
Now as of last night my phone is constantly rebooting while charging. I plugged it in last night and kept hearing a buzz (I keep it on vibrate), looked at the phone and it would be booting up. It fully boots to the Start screen and I can go ahead and begin doing something, but no matter what I'm doing it just shuts completely off without even saying Goodbye (literally). It continues to do this until I unplug it, and it ONLY reboots when plugged in. I've tried a battery pull a couple of times but to no avail. Its getting very annoying because it takes much longer to actually charge, and I also don't imagine this is very good for the phone itself.
I was planning on flashing LEAD's latest release to see if it fixes it, but I'm not sure if the phone will react this way plugged into the PC as well. I haven't plugged in to the computer yet to find out, hopefully it won't do this, else I won't be able to flash it.
Any ideas or suggestions? Has anyone else had this issue?
well i plugged into the pc and it still reboots however, when in the tricolor bootloader it does not reboot! so with this discovery i now know that its a bug in the OS causing the reboots. also, because its not rebooting in the bootloader, i should be able to reflash without issues, correct?
as a side note, the phone got VERY hot last night while left in to charge, so i will just charge my wifes phone and swap the batteries so that i wont damage my phone.
no one else has reported this issue with this ROM as far as i can see, only random reboots.
Sorry to hear about all those problems. Have you tried the latest ROM after the 8858 release? I suspect there could be some sort of corruption in the OS. If you haven't, I recommend biting the bullet and just restoring the phone. I also recommend flashing the latest ROM, since it has the latest OS version. If the phone isn't having problem when in boot-loader mode (tri-color screen), you should be OK to flash it.
leadpoizon said:
Sorry to hear about all those problems. Have you tried the latest ROM after the 8858 release? I suspect there could be some sort of corruption in the OS. If you haven't, I recommend biting the bullet and just restoring the phone. I also recommend flashing the latest ROM, since it has the latest OS version. If the phone isn't having problem when in boot-loader mode (tri-color screen), you should be OK to flash it.
Click to expand...
Click to collapse
thanks for the reply lead! i am going to flash you latest release now. i am going to look for an alternative way to backup pictures outside of Zune and the PC, but i dont think any exist.
i will post back when its up and running.
i flashed the 8862 ROM and its been plugged in for about an hour with no reboots
plus, this ROM feels snappier than the 8858. an issue i used to have with IE, that is gone in this build is it would open Google every time i click the IE tile.
thanks for the help leadpoizon
x_orange90_x said:
i flashed the 8862 ROM and its been plugged in for about an hour with no reboots
plus, this ROM feels snappier than the 8858. an issue i used to have with IE, that is gone in this build is it would open Google every time i click the IE tile.
thanks for the help leadpoizon
Click to expand...
Click to collapse
No problem. Glad your issue is fixed now.
Ok so I am no longer having the charging or battery issues anymore, but now my Marketplace is basically broken. When I can manage to begin a download it immediately goes to Attention Required, and upon clicking i get error code 8000ffff. So no apps will install/download from Marketplace. Also, on almost every game and app, it says this app is not available for your device, even ones i used to use on 8858. Some i have even manually installed and they work fine. Also when trying to even view many of the games in the Marketplace, I get error 805a0194. So far I haven't managed to install anything from the Marketplace aside from the Bank of America app.
I have tried resyncing with Live, rebooting the phone, tried changing Marketplaces and settings with the Marketplace Config app. Nothing fixes it
Any suggestions?
No one?
I'm beginning to think 8862 is to blame. I keep getting service unavailable errors from MP, or everything is not available for my device. I don't want to hard reset, but it looks like this isn't going away on its own. :/
x_orange90_x said:
No one?
I'm beginning to think 8862 is to blame. I keep getting service unavailable errors from MP, or everything is not available for my device. I don't want to hard reset, but it looks like this isn't going away on its own. :/
Click to expand...
Click to collapse
Sorry, I've moved on from this device, so I can't test anything now. I never had any issues like this on my device and I used it extensively for a long time after flashing that ROM.
I'm having a weird issue that literally just started yesterday. First of all, I didn't do any changes yesterday before this occurred. Anyway, my G3 just started freezing, then rebooting randomly, BUT that's not all! When it tries to reboot, it flashes the LG screen, and SOMETIMES makes it to the AT&T screen....and even, sometimes makes it all the way booted up. But, at any point, it can/will reboot and start the process all over. I read on another site that it could be a battery going bad, but I only trust XDA. So, could someone chime in with some help or info pointing me in the right direction?
Thanks in advance,
Ontabok
same issue i am having ..i thought about the battery thing so i pulled it out and put in a fully charged one and no bootloop..but now 3 hours later and 85 percent left on battery and bootloops have started again..btw other battery was a 20 percent when changed it out for fully charged batt..so im just as lost trying to figure it out
Ontabok said:
I'm having a weird issue that literally just started yesterday. First of all, I didn't do any changes yesterday before this occurred. Anyway, my G3 just started freezing, then rebooting randomly, BUT that's not all! When it tries to reboot, it flashes the LG screen, and SOMETIMES makes it to the AT&T screen....and even, sometimes makes it all the way booted up. But, at any point, it can/will reboot and start the process all over. I read on another site that it could be a battery going bad, but I only trust XDA. So, could someone chime in with some help or info pointing me in the right direction?
Thanks in advance,
Ontabok
Click to expand...
Click to collapse
Sadly that sounds like a hardware issue
hyelton said:
Sadly that sounds like a hardware issue
Click to expand...
Click to collapse
How can I figure out what part of the hardware could be causing this? Is there a diagnostics or something I can use? I've tried factory reset (multiple times), LG Flash Tools to flash previous version, and the strange thing is it may not even make it through the process without restarting again. It's been rooted, but I've never had a problem until this. I never deleted anything.
Ontabok said:
How can I figure out what part of the hardware could be causing this? Is there a diagnostics or something I can use? I've tried factory reset (multiple times), LG Flash Tools to flash previous version, and the strange thing is it may not even make it through the process without restarting again. It's been rooted, but I've never had a problem until this. I never deleted anything.
Click to expand...
Click to collapse
Not really other than swapping out parts. If using flash tool won't work and it won't go back to stock then it's definitely a hardware issue.
What percent does it get too before rebooting? If 80% that's normal. If before it's definitely a hardware problem.
hyelton said:
Not really other than swapping out parts. If using flash tool won't work and it won't go back to stock then it's definitely a hardware issue.
What percent does it get too before rebooting? If 80% that's normal. If before it's definitely a hardware problem.
Click to expand...
Click to collapse
I can try Flash Tools again. Maybe it just didn't take. I just noticed another thing. When it's trying to boot, if the notification light flash when the LG screen is on, it will load. But, if it doesn't flash, then it will just go black, then flash the LG screen again.
Kameirus said:
same issue i am having ..i thought about the battery thing so i pulled it out and put in a fully charged one and no bootloop..but now 3 hours later and 85 percent left on battery and bootloops have started again..btw other battery was a 20 percent when changed it out for fully charged batt..so im just as lost trying to figure it out
Click to expand...
Click to collapse
Yeah. It's really weird. It seems to do it less when the battery is charged, but if I get down to 40-50%, it could go into a loop that runs the battery into the red. Also, it seems to heat up around the power button when it's stuck in the loop. And, to top it off, my software update popped up yesterday. I've been anxiously awaiting Marshmallow for a while, but I'm afraid to update because of boot-looping right in the middle and bricking the whole thing. I already have a bricked G2 due to something weird that happened while trying to update to Lollipop. I'm going to the AT&T store today, I think. I'll let you know what I find out. Maybe, it can help you.
Thanks,
Ontabok
hyelton said:
Not really other than swapping out parts. If using flash tool won't work and it won't go back to stock then it's definitely a hardware issue.
What percent does it get too before rebooting? If 80% that's normal. If before it's definitely a hardware problem.
Click to expand...
Click to collapse
Ok. So, first of all, sorry for the long wait on a reply.
I did manage to get through a factory reset, but it still is doing the boot loop. I'm going to take it in to AT&T today. You can see my reply above to see more info. I unrooted everything and factory reset, but it still loops. I think it's a problem with the phone. I may have to go to LG, depending on what AT&T says.
Thanks for the help!
Ontabok
So, final update. I had to go into the AT&T tech store. I was having the random boot loop for about a week, then, on Saturday, I got the Demigod green screen. I had went in the day before and ordered a new battery, but I couldn't find any information on the green screen error. I took it in and they immediately (after checking for rooting) replaced it (warranty). They said they had never seen/heard of this screen. They had to actually Google it to see if it's attached to rooting. (It's not) Anyway, so I'm back in the saddle with a brand new phone. ?
Sent from my LG-D850 using Tapatalk
Also, thanks for the replies!
Sent from my LG-D850 using Tapatalk
ok so my g/fs g3 just started doing this. updated to mm about 3 or 4 days ago. was doing fine. haven't changed anything software wise. completely stock. no root.
what is really odd is that it doesn't loop when plugged into a power source. take it off the charger= insta loop ...
hoping a rom might solve the issue but from the sounds of the replies maybe that isn't the case.
any help greatly appreciated. i've not owned this phone myself or i would already have it rooted and custom recovery..
is there even a root method for MM? recovery?
i'd love to see if its a software issue. the phone worked swell before the update...
im trying to get to the bottom of this tonight if i can my g/f has a final tmr early in the morning and i'd like to make sure she has a phone to go with her. prob send her with mine if i can't get this working. but thats less than ideal PM if you've got anything i can try or links to get me started... i'll be reading in the mean time...
ok so im working on a nexus 5. i was already all too aware of the potential power button issue so that was the 1st thing i checked out, ive cleaned it twice now and made dbl damn sure i can feel it both click in and click out when being pressed.
on top of that i can boot into twrp both temp boot and flashing recovery for it. it does not cut off when in twrp (as i imagine it would if it were the power button being stuck)
previously i could not boot into twrp or flash anything at all so i ordered and installed a breand new battery.. now i can flash twrp via fastboot (progress right?)
however when it is powered off, on teh charger it shows the battery full with lightening bolt, then that fades and is replaced with a hollow battery being filled, then goes black and starts over... leading me to believe its not taking any charge in..
ive tried stock 7.1.1, stock 7.0.1, stock 6.0.1, cyanogenmod 14 and even ran the NRT by Wugs... i have wiped everything, i formatted data and made sure the partition was correct pre-flashing by running NRT to return stock values n such, i have also tried different approachs to flashing. fastboot flash system, adb sideload, twrp install zip and NRT...
with my small (yet excessive) experience so far with android im led to believe this is being caused by some sort of conflict inside the system memory, it almost has a rythym to when it cuts off, like when it hits block such n such it goes "OUCH DAMMIT" and retreats for safety (powering off)
you'll have to forgive me for starting a new thread, the only info i can find pertains to the power button which i am fairly confident it is NOT, and after hours of searching tonight alone im really not for diffing thru every thread, i did however do a quick search prior to posting....
Where did you get the battery? Tried different USB cables and chargers? The phone boots and runs properly on stock?
I had a similar problem. I talked to LG customer support and they were aware of this issue and suggested that the whole logic board needs to be replaced. Apparently this is common with LG devices.
A workaround that worked for me is to turn off the phone for 1 day (let it cool down), clean flash whatever rom you like, then flash ElementalX kernel with the CPU under-clocked to minimum.
I have tried various ports and cords, battery from a top seller on ebay (checked reviews prior) and I cannot boot into stock Android either... During my extensive tweaking of the device last night I relocked the bootloader while returning to complete stock... After doing such I later tried some thing I saw suggested on the forums, removal of the power button.. so I desoldered it.. didn't change anything so it's def not the button... However now I cannot click the screen to confirm unlocking the BL again so I'm close to boned as far as flashing options ATM... Lol fail...
If it is a motherboard problem, and it sounds like it is, the cheapest solution may be to buy a used Nexus 5 with smashed screen and working motherboard. Swapping the motherboards is quite simple.
That's probably gonna happen, I don't see many other viable options .... It's not my phone so imma be putting money into someone else's to save face. U don't get a broke device back from me
Thanks guys
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 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.