Related
My wife and I both have non-rooted TBs which started experiencing random reboots after the OTA. We went to the store and they ordered us two new ones. They'll be here Tuesday.
Yesterday my wife's TB rebooted, and got stuck at the HTC logo. She was unable to turn it off. I did a battery pull, and again, stuck at the HTC logo. I swapped my battery since hers was low, nothing. It's dead, Jim.
We called the store and they wouldn't swap it since one is already on order. My wife is a doctor, and being without a phone until Tuesday is not an option. So I loaned her mine. (Sigh).
I tried reflashing the latest signed ruu I got from another thread. I downloaded it onto my SD card, swapped cards, and I was able to hboot and the install seemed to go fine. However, it had no effect. It still gets stuck in the same spot.
Tried factory reset, recovery, nothing. Every time I reboot I get stuck at the logo and I need to pull the battery.
Out of curiosity more than anything else, any other things I can try?
Thanks.
ZBoater said:
I tried reflashing the latest signed ruu I got from another thread. I downloaded it onto my SD card, swapped cards, and I was able to hboot and the install seemed to go fine. However, it had no effect. It still gets stuck in the same spot.
Tried factory reset, recovery, nothing. Every time I reboot I get stuck at the logo and I need to pull the battery.
Out of curiosity more than anything else, any other things I can try?
Thanks.
Click to expand...
Click to collapse
Unfortunately, the only thing I would've suggested would be flashing the signed ruu.
You could try reverting to the pre-OTA firmware, but I'm not sure you'll be able to use ADB if you're stuck bootlooping. Check out the "NOT FOR ROOT USERS" section.
ZBoater said:
My wife and I both have non-rooted TBs which started experiencing random reboots after the OTA. We went to the store and they ordered us two new ones. They'll be here Tuesday.
Yesterday my wife's TB rebooted, and got stuck at the HTC logo. She was unable to turn it off. I did a battery pull, and again, stuck at the HTC logo. I swapped my battery since hers was low, nothing. It's dead, Jim.
We called the store and they wouldn't swap it since one is already on order. My wife is a doctor, and being without a phone until Tuesday is not an option. So I loaned her mine. (Sigh).
I tried reflashing the latest signed ruu I got from another thread. I downloaded it onto my SD card, swapped cards, and I was able to hboot and the install seemed to go fine. However, it had no effect. It still gets stuck in the same spot.
Tried factory reset, recovery, nothing. Every time I reboot I get stuck at the logo and I need to pull the battery.
Out of curiosity more than anything else, any other things I can try?
Thanks.
Click to expand...
Click to collapse
RIP poor TB
How long did you wait for the screen to clear?
Just curious because I know usually when I do any type of update or rom change, etc, since you normally wipe the data and cache, the boot up can take quite a long time on the initial boot up.
I know some people report as long as 10 minutes or so to get past the screen. I don't think mine ever took that long, but there have been times I think it's stuck and then a minute or so later, it gets past it.
Just my two cents.
This has happened to a few people already after the update. I don't know what is in this update but HTC screwed up majorly.
Sounds a lot like what happend to mine, but mine was rooted.
See here...http://forum.xda-developers.com/showthread.php?t=1090531
LOL, I welcome the breaks when I can't find my phone for the day.
you should just leave it on the htc logo until the battery dies or until it get wayy to hot.. just to see
will9512 said:
you should just leave it on the htc logo until the battery dies or until it get wayy to hot.. just to see
Click to expand...
Click to collapse
What would that accomplish?
Yeah your lucky you got a guy to order your phone because I wouldn't have because even the new ones are rebooting, when you get it I would suggest postponing the update if it comes without the Mr1 update, as far as your wives phone yeah I would check out the forum uptop on going back to old software other than I have had a few people come into the store with same problem and couldn't do anything( mainly because I have no access to anything), but ship a replacement, oh and one suggestion is if you don't want your wife to borrow your phone your local store does have emergency stock Android loaners that you use until you get your replacement in, and then you just send your phone and the loaner back in the FedEx box so if you really need a phone you can do that.
Sent from my ADR6400L using Tapatalk
I believe your random reboots are due to the new radio which is tied into the OTA. If you apply the OTA again your still going to have random reboots. I ever used the newer radios and have never had a random reboot.
I was slow around flashing to the latest baseband but finally took the dive today and the program locked up at 5% for like 2 hours before I yanked it. Now it just gets to the "S/W Updater" screen regardless of what I do (NVFlash recoveries, roms, kernels, format, hard reset, etc). When I try to update it again, it just immediately says it's already the latest version. Why won't it just flash over it like most flashing programs.
Tmobile is pinging me $20 for a replacement but I have a really good G2x. Is there anything I can do to revive mine or is it toast? ADB commands or something? I have clockworkmod on there now, but I'm not really getting anywhere.
[Update]
Use this NVFlash method to completely format your phone, re-setup your partition tables, and flash the stock GB rom:
http://forum.xda-developers.com/showthread.php?p=17258229
Dead
It's dead. Same thing happened to me and to many many others. Turn it back to TMo and take the hit--it's not worth the time playing around with it any more.
Call TMo and ask to be forgiven the $20. If you've been a long and loyal customer they might even do it.
Your new phone should come with 2.3.3 installed. Mine did and I've had no trouble with it--it's finally settled down into a very usable and fast phone. Stock ROM. But I won't buy another LG phone again for a very long time--not until they hire a few software engineers who know what they're doing.
No my friend. I got revived!
http://forum.xda-developers.com/showthread.php?p=17258229
It totally erased everything, formatted everything, reset all the partitions, and flashed the GB Stock rom.
Booted up, NVFlashed CWM, Restored my Nandroid backup, viola!
Thought it would be a good thing to make more available. It was in the Android development thread but the title is tricky as its listed as a rom (which I guess it kinda is).
Sent from my LG-P999 using xda premium
i dont understand why people get stuck on this. ok
when i did it. the LG Tool stop responding on half the period % and my phone had the S/W updater screen so what i did i click on closed unpluged my device then open the LG Tool again plug my device and the LG TOOL said that there was a problem if i wish to continue with my update i click yes and it kept doing till it was done and my phone was fine with 2.3.3
The mistake you made was just stopping the update. Mine did the same thing. Instead of listening to the stupid message about removing the battery, etc. I just removed the usb cable, waited for the beep, put the cable back in, waited for the beep and then pressed "restart" on the update. It completed perfectly after that.
Well I've gone through all of those scenerios and it would attempt to reflash it, but the last time it got stuck on 5% for about 2 hours... no error message or anything. After 2 hours at 5% I pulled the plug. When it is in the middle of "flashing" and gets locked up, there is no Cancel button or Restart button like when it errors out.
I had no errors, just a locked up program. Regardless the posted link really fixed me up and got it working again.
I changed the title and updated the OP with the solution.
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!
So I've been v customizing friends and families S3's today even an old LG Revolution, And I finally got around to doing my dad's and was using going to use odin to just flash the stock image of JB 4.1.2 and then boom lol
Anyways, it said Successful and all that good stuff, unplugged it, and then restarted it but instead it just shut off. And it wont turn back on, But it still makes the notification sound on my laptop for when a device is plugged/unplugged from the USB, and it started installing the Android device drivers as well, so something in that phone still has to be alive.
Please tell me I can fix thi. When I show up at his his house later with a broken S3, he's gonna be so pissed, and I just got a new Note 3 and I really dont wanna have to give it to him as a replacement.
Just read this in a thread if ound on here while doing a search - And if it doesn't work you can force it into downoad mode by holding down the power. volume down and power key without the battery and then putting in a micro usb cord plugged into the computer. Then put in the battery. -
when i did that, the notification LED lit up RED, but I think i did something wrong after that. So I am thinikin this is fixable if I can just get into stock recovery and format/reset system and cache.
and apparently this guy had the same problem and fixed his - Update:
Josh over at MTVideos is the bomb. He was very professional and accommodating. They are typically a mail order operation but I was desperate and only a couple hours away, so he let me stop by. As soon as I showed up, he put down what he was working on and jumped into my phone. This was the first 32 Gb version he'd seen, so we were learning as we went. He explained everything he was doing as he went. First, try the dongle to get into download mode. No go. Next, hook up his JTAG equipment and dump a full backup, Justin Case .
Next, carefully write, address block by address block a known good 16 Gb bootloader and test. All the way up to 18 ( which, if you read the linked threads, was where I dd'd the recovery). Bingo. Once a known good recovery was put back in, it booted right up.
Factory data reset and we were off to the races.
Moral of the story: the recovery is very important. MD5 that ish before pushing.
I do still have one issue. When it boots, it tries to put me in Factory Mode, then FC's "factory mode" twice before letting me use my phone...
Again, a big thanks to Josh for helping me out. Those guys at Mobile Tech Videos really know their stuff and are good at what they do.
BackSeatSuicide said:
and apparently this guy had the same problem and fixed his - Update:
Josh over at MTVideos is the bomb. He was very professional and accommodating. They are typically a mail order operation but I was desperate and only a couple hours away, so he let me stop by. As soon as I showed up, he put down what he was working on and jumped into my phone. This was the first 32 Gb version he'd seen, so we were learning as we went. He explained everything he was doing as he went. First, try the dongle to get into download mode. No go. Next, hook up his JTAG equipment and dump a full backup, Justin Case .
Next, carefully write, address block by address block a known good 16 Gb bootloader and test. All the way up to 18 ( which, if you read the linked threads, was where I dd'd the recovery). Bingo. Once a known good recovery was put back in, it booted right up.
Factory data reset and we were off to the races.
Moral of the story: the recovery is very important. MD5 that ish before pushing.
I do still have one issue. When it boots, it tries to put me in Factory Mode, then FC's "factory mode" twice before letting me use my phone...
Again, a big thanks to Josh for helping me out. Those guys at Mobile Tech Videos really know their stuff and are good at what they do.
Click to expand...
Click to collapse
So yea. dont have Jtag equipment, but apparently this type of Hardbrick has been fixed without JTAG before. Tnere are a few threads/Guides on here. So I just gotta go find a bigger SD Card cause apparently you need a 16GB SD and I only have an 8 right now cause my 64GB got stolen. Other then that I got everything I need including a dual-boot installation of Linux. So as soon one of the Electronic stores around here opens I am going to get that card and hopefully make this thign work.....
I dont get what Happened. I flashed like 4 or 5 S3's yesterday, all of them were on 4.1.1 so I used to odin to flash them to 4.1.2, that file worked fine for all of them, including thw two of them that were Verizon, just like this one is. The phone has never been rooted or anytiing custom at all done to it. And it was not even 3months old. And my stepdad barely uses the thing. Just gonna be one of those days I can tell already.
BackSeatSuicide said:
So yea. dont have Jtag equipment, but apparently this type of Hardbrick has been fixed without JTAG before. Tnere are a few threads/Guides on here. So I just gotta go find a bigger SD Card cause apparently you need a 16GB SD and I only have an 8 right now cause my 64GB got stolen. Other then that I got everything I need including a dual-boot installation of Linux. So as soon one of the Electronic stores around here opens I am going to get that card and hopefully make this thign work.....
I dont get what Happened. I flashed like 4 or 5 S3's yesterday, all of them were on 4.1.1 so I used to odin to flash them to 4.1.2, that file worked fine for all of them, including thw two of them that were Verizon, just like this one is. The phone has never been rooted or anytiing custom at all done to it. And it was not even 3months old. And my stepdad barely uses the thing. Just gonna be one of those days I can tell already.
Click to expand...
Click to collapse
Have seen that happen when battery too low and messing with SD Card and recovery. Remove battery and sd card a few minutes. Replace battery only and plug into charger for at least 30 minutes. Unplug and Try to boot. If it boots. Power off and replace sim card. Reboot. Worth a shot.
I will try that
Sent Using My Galaxy Note 3
Yea that didn't work.
Sent Using My Galaxy Note 3
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/