Hello, here is my problem. I posted it here as well, but maybe it's not the only place because it might be more than a CyanogenMod problem? (http://forum.xda-developers.com/showthread.php?p=57411392#post57411392)
The other day, my phone shut off. I thought maybe my battery (zerolemon standard size) was dead, so I tried charging it, but I realized that nothing was happening. In fact, my phone didn't even start up. I would see the Samsung Screen, then Cyd (sp?) the Android showed up, but it wouldn't boot. I could still get into my Recovery, so I tried reflashing CM11, but it still was broken. I had put in my OEM stock battery at this point. I even factory reset, but nohting.
I found that by flashing Bonestock, that my phone worked, however. So I grabbed whatever photos and files that I deemed important, and tried formatting data, then reflashing the newest cm11 nightly (12/6 i believe. ) STILL nothing. Wouldn't boot.
Finally, I used ODIN to go back to stock (4.1 or something), then rerooted my phone, and put the 12/6 nightly on.
It worked, for the time being. A few random restarts, but nothing weird.
However, Today, i noticed that the random restart happened again. I press the home button, cuz i think it's on, but it isn't. It vibrates, then starts to reset. I see the Samsung screen, then nothing! This is with my zero lemon. I can't get it to go to recovery or anything w/o shutting off.
I put in my stock battery, and it starts right up! However, after a few hours, it starts turning off and doesn't boot up.
I managed to get it into recovery long enough to reflash hyperdrive, because it seems like touchwiz roms work?
questions:
1. is this a CyanogenMod problem?
2. Is this a hardware problem?
3. Is this a battery problem?
4. What should I do? If I stay on this touchwiz rom, I can't use my Moto 360. You need 4.3 or 4.4 to use Android Wear.
5. I am thinking of unrooting and sending my phone back through warranty. (cuz it might be hardware problem). However, if they send me a refurb, would it be unlockable? Cuz it's like 4.2 or something? and then I'm stuck w/o my Moto 360. (what's the latest verizon update?) (also, is there a chance i'd get the phone like 4.1 and then i could still root and unlock bootloader?)
6. the other day, before this happened, it was raining and i used my phone. i don't think water got in... but could this be the result of that? I don't see how water would hate CM but like TW though.
Thanks, any ideas would be super helpful.
chances of getting a phone that is rootable and bootloader unlockable is very low, if there's any chance at all. if you wann try and replace the phone why not try swappa and look for one that is either bootloader unlocked or look for one that is capable of being unlocked. other then that, i dont see any way of getting another one that you can root and rom.
Thanks. I would get a replacement through my Verizon insurance. I guess it might be the end of an era for cm my galaxy s3. Sigh. Just looking forward to nexus 6 hopefully for Christmas.
Related
Let me try to explain as comprehensively as possible what happened before I couldn't start my Nexus S again.
Until yesterday, I was running an older CM9 Nightly, together with the Matrix CFS kernel (18.0) and an older reloadedICS mod. Everything was running fine. Well, except for the fact that every time I rebooted, it took 2 or 3 times before it actually started. So 2 or 3 times, while rebooting, my Nexus S rebooted again, or just crashed so that I'd have to pull out the battery. But when my Nexus S finally started, it worked fine. I still had the occasional crash, but everything worked.
Yesterday, I decided it was time for a new nightly. So I downloaded the CM9 nightly from 7 april, the latest gapps, the newest matrix CFS kernel (18.5), and the Reloaded ICS 1.9b2 mod. Before I flashed everything, I wiped cache/dalvik cache, as always. I did flash everything at the same time though.
I didn't like the new icons in the statusbar from the latest Reloaded ICS mod, so I downloaded a different version of the Reloaded ICS 1.9b2 mod that someone had uploaded, with the different icons. That also worked fine. Every icon changed, except for the battery icon.
I used my Nexus S for the day. I listened music, browsed the web, whatsapped with some people... It worked fine. Then I went and watched some TV. After that I went to bed, and I noticed the battery of my Nexus S was empty. Since I wanted to check my mail/facebook before I went to sleep, I put my Nexus S in the charger. I started it, that worked fine. It said the battery had 0% on the statusbar, and because of the new battery icon from the Reloaded ICS mod, you can't see anymore if your Nexus S is charging. But it started, so I guess that's what counts.
So I started facebook (in the browser). Halfway loading, my Nexus S crashed. I experienced crashes before, certainly with CM9 nightlies, so I wasn't really surprised. I pulled out the battery, because the power button wasn't working (again, wasn't surprised, that's normal with that kind of crash).
And that's when things went wrong. My Nexus S wouldn't start again. I tried starting it in fastboot mode. Didn't work.... I put it in the charger for the night, but the charge icon (the white battery icon) didn't show up on the screen. And the next day (today), it still didn't start. I know someone who also has a Nexus S, so I tried his battery. Didn't work. I tried his charger. Didn't work. But when he tried MY battery and charger in HIS Nexus S, it DID work! Well, except for the fact that his Nexus S is still trying to boot up, after half an hour...
So that's two Nexus S's dead. One that won't even charge anymore. The other at least shows signs of life. I have no idea how this is possible. Clearly it has something to do with pulling out batteries, since his Nexus S wouldn't start anymore after he pulled out the battery when it was still turned on, and my Nexus S wouldn't start anymore after I pulled out the battery when it crashed.
By the way, my friend's Nexus S is not rooted. He is using stock ICS.
Thanks a lot in advance!
Edit; i also noticed that my battery was going down exceptionally quick after the 7 april nightly. I don't know if this is relevant.
Try this to see if you can get it up to fastboot. After this you'll want to have fresh ROMs (preferably stock for now) ready to flash. Data/factory reset, format /system and format /boot, then flash the new ROM in recovery.
Hopefully this works for you and possibly your friend. Does his phone enter bootloader (Vol. Up + Power)?
Harbb said:
Try this to see if you can get it up to fastboot. After this you'll want to have fresh ROMs (preferably stock for now) ready to flash. Data/factory reset, format /system and format /boot, then flash the new ROM in recovery.
Hopefully this works for you and possibly your friend. Does his phone enter bootloader (Vol. Up + Power)?
Click to expand...
Click to collapse
Thanks for your help! I'm going to try that.
Yes, his phone can enter bootloader.
I've found some other people on the internet with the same problem as me. First there were problems with rebooting (it would only start after the second or third try). Then the battery drained exceptionally quick. And then, no signs of life at all... http://groups.google.com/a/googlepr...gory-topic/mobile/android-devices/06zm2LENFpc
Try to go into recovery and download the Stock 4.0.3 (hopefully he's still on 4.0.3) FULL ROM and flash that (needs to be named update.zip, can flash through stock recovery). If this doesn't work it might need the bootloader unlocked at least and data will most likely be lost at this stage.
There have been some people who have had battery drain issues while the phone is off. I've not heard of anything to suggest anything besides a hardware fault which requires the mainboard to be replaced, unsure if this is related at all.
Harbb said:
Try to go into recovery and download the Stock 4.0.3 (hopefully he's still on 4.0.3) FULL ROM and flash that (needs to be named update.zip, can flash through stock recovery). If this doesn't work it might need the bootloader unlocked at least and data will most likely be lost at this stage.
There have been some people who have had battery drain issues while the phone is off. I've not heard of anything to suggest anything besides a hardware fault which requires the mainboard to be replaced, unsure if this is related at all.
Click to expand...
Click to collapse
My friend can't get into recovery anymore... It shows the green android icon for a flash of a second, and then it shuts down... But at least he can get into bootloader mode... I guess that's something.
I guess it has something to do with my battery, since that is what killed my friends Nexus S. I don't think my problem will ever be fixed though. That ubuntu app is worth a shot, but for that I need a computer that can run ubuntu and windows, and I don't think I have that.
I've also found this: http://mobiletechvideos.mybigcommerce.com/nexus-s-jtag-brick-repair/. Is that worth a shot? I'm willing to pay that kind of money for it. I do a lot of things myself without having too much knowledge, but this goes a little too far...
I personally wouldn't go for a jig, i can't vouch for them at all. I hear it it isn't too difficult to make your own though (3x100kOhm resisters in series or something). Wouldn't be worth $40, closer to $2 if you already have a soldering iron.
Your mate can get into recovery, he just can't see anything because he's on the ICS recovery (it doesn't turn on the SC-LCD's backlight, common problem). Shine a bright lamp on it at an angle and you should be able to make out what's there. Power + Vol. Up to get past the exclamation and android, then shine up the top. If he's happy losing his data (and slightly possibly his warranty) to unlock the bootloader i'd be going for that instead.
Just about any computer can run ubuntu. You might even be able to run it straight off the livecd. This is the first thing i would try.
Harbb said:
I personally wouldn't go for a jig, i can't vouch for them at all. I hear it it isn't too difficult to make your own though (3x100kOhm resisters in series or something). Wouldn't be worth $40, closer to $2 if you already have a soldering iron.
Your mate can get into recovery, he just can't see anything because he's on the ICS recovery (it doesn't turn on the SC-LCD's backlight, common problem). Shine a bright lamp on it at an angle and you should be able to make out what's there. Power + Vol. Up to get past the exclamation and android, then shine up the top. If he's happy losing his data (and slightly possibly his warranty) to unlock the bootloader i'd be going for that instead.
Just about any computer can run ubuntu. You might even be able to run it straight off the livecd. This is the first thing i would try.
Click to expand...
Click to collapse
That tip with the bright lamp really worked! Thanks for that! But the first time he didn't do the factory reset yet, and now he can't even see the recovery menu (not even with a bright lamp), just the exclamation mark...
He needs to press Power + Vol. Up while he can see the exclamation mark. This will exit the splash screen and enter the actual recovery menu.
Thanks! But the factory reset didn't work, unfortunately... He is still stuck in boot...
As a matter of fact, oldblue has written up good instructions to get the phone to factory-stock state and fastboot flashable images. These should overwrite everything that should be overwrited on the phone and throw stock google stuff on there. Definitely something to try out, i would be doing this beyond anything else.
Note that it requires unlocking (and relocking later) the bootloader, and this will also erase all data on the phone and internal sdcard.
My friends phone works again. The factory reset did work after all! Hurray for him, lol
I'm going to try that ubuntu app later today. After that, oldblue's guide might come in handy!
Thanks a lot for all of your help, Harbb!
Happy to help and best of luck. Definitely use AdamOutler's app to the best of it's ability, it can do damn near anything. There is one more thing to try on top of this too if nothing goes to plan but it could be a potential sacrifice (minor hardware mod). Let's just hope this works.
The fastboot images would be, theoretically, a more perfect way to return to stock, so if this is possible to fix by software alone you'd be hard at work trying to find a better alternative. Maybe your phone is recoverable after all.
Androyed said:
My friends phone works again. The factory reset did work after all! Hurray for him, lol
I'm going to try that ubuntu app later today. After that, oldblue's guide might come in handy!
Thanks a lot for all of your help, Harbb!
Click to expand...
Click to collapse
No dont try the ubuntu tool unless it doesnt turn on, you cant boot into bootloader or you cant turn it on, and you see nothing on the screen.
---
die tool is voor echte gebrickte nexussen.. gebruik die aleen als je dus niks meer ermee kan, zoals dat hij nieteens in de bootloader kan booten. (dat was met demijne gebeurd).
succes , als je vragen hebt PM me maar.
Same Problem?
Hey guys, i have a Nexus S (never rooted or anything). I received the update notice for ICS so i duly updated. Right after, my phone was bricked. Doesn't turn on / respond to anything.
I ran the UnbrickableRessurector by Adam and I can get Fastboot Mode to show up this way. I was really hoping that i don't have to unlock it or anything as i don't want to void warranty.
Any thoughts? I tried selecting 'recovery' after which the screen goes dark. Shining a bright light on the display doesn't help - really can't make out anything. Do i have a different problem?
Thanks!
I've been having this problem starting the last couple of days. I'll be using my phone, and all of a sudden the screen turns off and nothing short of a battery pull will turn it back on again. Sometimes it happens when I'm not using it at all too. I'll pull it out of my pocket and get nothing. Do a battery pull, and everything's fine again until the next time it happens. Never had this problem before, but in the last two days it has happened 7 times. It even happens when it's plugged in. The LED indicator that is normally lit up when it's charging will go out. Unplugging it and plugging it in seem to have no effect. No sounds, nothing.
I'm running Jellybeans 4.1.2 Rom, with TWRP. Today I ran a backup, cleared and wiped data, fresh install, recovered backup and still having the problem. Should I try a clean install without recovering the backup? Could that have anything to do with it? Any other ideas on what to try or what the problem could be?
If you've been running the same ROM this whole time and it just started out of the blue, I don't really think it would be ROM related. It might be hardware related.
I suppose the only real way to test if it is ROM related is to ODIN back to stock and see if it still happens. If it does keep happening once returning to stock you could probably get it swapped out by Verizon.
BattsNotIncld said:
If you've been running the same ROM this whole time and it just started out of the blue, I don't really think it would be ROM related. It might be hardware related.
I suppose the only real way to test if it is ROM related is to ODIN back to stock and see if it still happens. If it does keep happening once returning to stock you could probably get it swapped out by Verizon.
Click to expand...
Click to collapse
I've been running the ROM a lot longer than I've been having the problems, so I suspect you're right. I've had the phone for over 2 years now, so there's no warranties anymore. If it really is a hardware problem I'm probably looking at a new phone.
I'll try going back to stock though and seeing if it changes. Thanks!
Update: I just flashed did factory reset and flashed back to stock, but can't even get through initial setup before it goes black...guess it is hardware.
Hello,
My phone was running a stock ROM, it was not rooted.
On Tuesday morning i received notification on my phone that I had an update for 4.2.2. I applied the update and it appeared that everything went fine. Unfortunately, the phone immediately began re-booting every two to three minutes.
I have re-set the phone to factory defaults - no change.
I have used different batteries - no change.
I have put the phone into safe mode - no change.
If I put the phone in download mode - it does not re-boot.
I have tried to revert back to an older ROM but ODIN errors out.
Does AT&T have the ability to re-push the update OTA or even roll back to an older version?
Of course my contract is 5 months away from being fulfilled so I believe that I would be forced to pay full price for a new phone should I not be able to resolve this.
Any suggestions?
Thanks.
ShrinkWrap561 said:
Hello,
My phone was running a stock ROM, it was not rooted.
On Tuesday morning i received notification on my phone that I had an update for 4.2.2. I applied the update and it appeared that everything went fine. Unfortunately, the phone immediately began re-booting every two to three minutes.
I have re-set the phone to factory defaults - no change.
I have used different batteries - no change.
I have put the phone into safe mode - no change.
If I put the phone in download mode - it does not re-boot.
I have tried to revert back to an older ROM but ODIN errors out.
Does AT&T have the ability to re-push the update OTA or even roll back to an older version?
Of course my contract is 5 months away from being fulfilled so I believe that I would be forced to pay full price for a new phone should I not be able to resolve this.
Any suggestions?
Thanks.
Click to expand...
Click to collapse
your phone likely is not broken physically, it just needs to be re-flashed. the problem with that is, the flash files dont always get released or leaked right when the ota comes out.
unless someone has a better idea, your best option is probably to keep an eye on your phone specific forum for someone to post the flash file for this new update.
it really doesnt matter if they could push the update again, it would fail on verifying the current install.
if the device was unlocked, it could be rolled back to an older version. i wouldnt hold my breath waiting for them to do that for you.
you could check the forums and see if there is a way to unlock it yourself. some can be unlocked, a lot cant.
bweN diorD said:
your phone likely is not broken physically, it just needs to be re-flashed. the problem with that is, the flash files dont always get released or leaked right when the ota comes out.
unless someone has a better idea, your best option is probably to keep an eye on your phone specific forum for someone to post the flash file for this new update.
it really doesnt matter if they could push the update again, it would fail on verifying the current install.
if the device was unlocked, it could be rolled back to an older version. i wouldnt hold my breath waiting for them to do that for you.
you could check the forums and see if there is a way to unlock it yourself. some can be unlocked, a lot cant.
Click to expand...
Click to collapse
Update...I went to a SAMSUNG experience (or whatever they are called) in a Best Buy and I re-flashed the phone with 4.4.2...no improvement.
I have tried to root the phone with Towel Root and CyanogenMod but neither worked.
In additional attempts to figure this out, My son noticed that if the phone was connected to a computer, it did not re-boot. He though that it was related to it being connected to a power source so he plugged it into a charger, the phone would still re-boot.
So what we have determined is the phone needs to think that it is connected media device. The phone then works as it should.
Any ideas on how to resolve this? If the phone's battery dies and we are not near a useable computer, the phone is then again a paper weight.
ShrinkWrap561 said:
Update...I went to a SAMSUNG experience (or whatever they are called) in a Best Buy and I re-flashed the phone with 4.4.2...no improvement.
I have tried to root the phone with Towel Root and CyanogenMod but neither worked.
In additional attempts to figure this out, My son noticed that if the phone was connected to a computer, it did not re-boot. He though that it was related to it being connected to a power source so he plugged it into a charger, the phone would still re-boot.
So what we have determined is the phone needs to think that it is connected media device. The phone then works as it should.
Any ideas on how to resolve this? If the phone's battery dies and we are not near a useable computer, the phone is then again a paper weight.
Click to expand...
Click to collapse
you have got me on this one. it acts like a classic software issue. now that that has been eliminated.
you performed a factory reset after the flash im assuming?
i don't know what else to tell you, if the software is clean, it has to be hardware damage.
sorry
My tablet is unrooted, untouched, unmolested, etc. Running 5.0.1 from the ota update.
My tablet's battery died while I was using it a few hours ago. I put it on the charger and wait a bit before turning it on. It boots up normally but I'm immediately greeted with the "power off" message box as soon as android loads. I've done fastboot and did the recovery boot (whatever that means in this case) and nothing I have tried has helped.
I'm afraid of tampering with it to install custom roms, because if that doesn't work the warranty would be void.
Anyone experience this problem before?
Sounds unusual but my only recommendation is to leave it on the charger overnight to get it fully powered up.
If not, you might have to boot into the stock recovery and perform a factory reset. At that point if it still doesn't work, if your tablet is completely unrooted with a locked bootloader, just send it to Nvidia.
Yeah it sounds like it's gonna get rma'd. It was charging the whole time, in the 4 or so seconds it was on the lockscreen before turning off it would show the battery percentage at something like 60%+, so it was definitely charging.
After enough tries it just wouldn't even give me the nvidia start up splash screen. I managed to do a factory reset (which seemed to take a really long time). The factory reset let it get back to the lockscreen but it immediately turned off again.
Other things for people who might have this problem as well:
It started after I put in a 32gb micro SD card I bought for it. I think the SD card is fine because it works in my phone.
Also this tablet was only about 4 days old when it broke.
The tablet is completely stock. I'm lucky it broke so soon as I was about to root it.
http://forum.xda-developers.com/shield-tablet/help/tablet-shutdown-boot-t3035492
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/