Related
*no need to comment problem resolved thank you*
kinda pissed im on my third d3. 1st one random reboot problems sent it back got a refurbished one. 2nd one headphone jack stoped working. 3rd one refurbished once again. this 3rd one that i got came with a dead pixle yes annoying but i lived with it also sliding mechinism scratched the gloss yes annoying i lived with it random reboots ok problem. i know i can fix it but i dont feel like spending the time to do it. ive been at it since the original droid custom roms kernels all that fun stuff and i would like to start developing not there yet but im not an idiot. my plan is to call verizon and get a droid 4 but i havent decided if i want to yet the only problems i see with the d4 are no removable battery/locked bootloader/motoblur. locked bootloader could possibly eventually be unlocked who knows. so i can cross out bootloader i can deal. motoblur i can just run the .sh or something to remove the bloat an get a better rom. so cross off motoblur. no removable battery thoughts?
im not asking for help fixing it because i know i can and no its not as easy as an .sbf at this point.
i know my information isnt perfect but i had my original droid for what 3 years? one not 2 of them one, and that thing runs beautifully. unlocked bootloader/removable battery/sturdy heavy. why don't they make em like they used to? moto blur free
so excuse my grammar and such im kinda ranting cause of the time ive spent working on it and im kinda angry but now i need to decide if i should get the droid 4.
minus how to fix my droid 3 cause im going to but im ya LOL scatter brain
thoughts on non removable battery?
your opinions and thoughts are valued.
*no need to comment problem resolved thank you*
If you're getting random reboots you may wanna try rooting and putting a custom bootstrap on there and wiping cache and delvik. Also there are some ROMs w\o Blur and you can choose between it or not. But the Blur isn't too bad at all once you get past the Verizon crap. I run Liberty and it's just Blur and Android, no Verizon crap except for My Verizon.
For the reboots, see if it still does it with no sd card in. I had read that there was a directory that could be causing it.
For the battery, do you carry a backup battery with you now? If not, who cares if you can take it out? My D1 I had multiple backup batteries, and I used them. My D3 I haven't had to use my backup yet, it is big enough to get me through the day, and the D4 has an even bigger one (course there's always the 4G to suck up all that power)
Sent from my XT862 using Tapatalk
My Droid 3 only reboots itself, if I leave it in Airplanemode for 8 hours or so. Then it reboots automatically. When not in Airplanemode it never reboots itself.
Maybe this helps?
thanks all its decided. im now getting my 4th refurbished droid 3. hopefully its not a pos again.
Im having the same issue lately. Ill try the suggestions here tonight when I get off work and let you know how it goes.
I'm upgrading from the Droid3, but this is the best built, most reliable phone I've ever owned. You guys must either be extremely hard on yours or extremely unlucky.
Sent from my DROID3 using xda premium
UNLUCKY lol received my 4th refurbished one its perfect btw. i take care of my tech.
jellman said:
UNLUCKY lol received my 4th refurbished one its perfect btw. i take care of my tech.
Click to expand...
Click to collapse
I got my Droid 3 about 5 or 6 months ago (if I'm remembering correctly) and I have yet to get a scratch anywhere besides the back of the screen (where the clips slide.) Now thats taking care of your technology, considering I use it all day, every day.
ChaoticWeaponry said:
I got my Droid 3 about 5 or 6 months ago (if I'm remembering correctly) and I have yet to get a scratch anywhere besides the back of the screen (where the clips slide.) Now thats taking care of your technology, considering I use it all day, every day.
Click to expand...
Click to collapse
i take care of my tech but, im sure you do the best job in the whole world with yours better than everyone congratulations. i am not hard on my phones.
I used to have random reboots while on Liberty and Mav, none Steel or any CM9A5+, since then I have recovered to both without any reboots, not sure, but assume complete wipes/resets between GB and ICS resolved issue.
CM9A7
Sent from my XT862 using XDA App
The story is I was having a lot of general problems with my Sprint HTC One. I was using it with CyanogenMod 10.1 and I noticed it was getting VERY warm. I then noticed that the battery was at 21%, I had hardly used it all day. It would normally have been around 94% percent. So I was shocked. Then I noticed that is would make weird clicking and "eek" noises when I would browse the Operating system. It would make an especially annoying noise when I would turn on the LED Camera light. I also noticed that the battery would drop about 1 percent ever 30 seconds.
I immediately shut it off and plugged it into my charger (AC). I opened up ClockworkMod and wiped my cache and dalvik cache and then did a factory reset from ClockworkMod. The problems still occured. I then tried flashing an Earlier version of CyanogenMod 10.1. The problem still occured. So I let my battery charge up to 50% (it took a especially long to charge, it would actually lose a charge while charging at times) and then used RUU tool to flash it to Complete Stock. That got rid of the weird noises caused during the operating system use. But the battery continued to run hot and take especially long to charge (somtimes the battery level actually was dropping). I then installed an app to control the frequency of the CPU. It was set to always run at 1.7GHz. So I fixed that and made the minimum Frequency the lowest option and the Max Frequency 1.7GHz. That solved the charging problem.
I left it to charge over night and by the morning it was at 100%, so I unplugged it and turned it off. I thought I had solved everything. I left the phone alone for about 4 hours and when I checked on it, it would not boot whatsoever. I could not not even get into the Bootloader! Then I plugged it back into the charger to find out that the Orange charging indicator LED would NOT light up! So for now, it is just sitting in the charger without the charging indicator light lit up.
I would also like to mention that I am not the original owner. I bought this phone used. It does not have the normal Sticker on the back of the phone to indicate the Serial Number etc. And since I am not the original owner, I do not believe I qualify for a replacement warranty. Any help at all would be greatly appreciated. Thank you for your time.
this has been happening to alot of people
which of the nightlies did you flash?
flex360 said:
this has been happening to alot of people
which of the nightlies did you flash?
Click to expand...
Click to collapse
It was either the cm-10.1-20130731-NIGHTLY-m7spr (2013-07-31) build or the cm-10.1-20130730-NIGHTLY-m7spr (2013-07-30) build
Might need to go to sprint for a replacement
Sent from my HTCONE using Tapatalk 4 Beta
krazyflipj said:
Might need to go to sprint for a replacement
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
Am I able to get a replacement even though I'm not the original owner?
ammuica said:
Am I able to get a replacement even though I'm not the original owner?
Click to expand...
Click to collapse
If you are under service they should. Phone is still under manufacturer warranty. If you don't have insurance, worst case scenario you pay $50 for a refurb/new phone. Of course that's if they can't repair
Sent from my HTCONE using Tapatalk 4 Beta
krazyflipj said:
If you are under service they should. Phone is still under manufacturer warranty. If you don't have insurance, worst case scenario you pay $50 for a refurb/new phone. Of course that's if they can't repair
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
It is not under service. I Bought it with the plan of not using it on a contract because I cannot afford a data plan, but I would still like to use an android smartphone.
Yeah just got and get a replacement for 50$ I was not the orginal owner and they got the serial number off they're system I got a refurbished one I think but it was in like brand new condition but now it seems the brick problem is still around
Sent from my HTCONE using Tapatalk 4 Beta
Alex1123 said:
Yeah just got and get a replacement for 50$ I was not the orginal owner and they got the serial number off they're system I got a refurbished one I think but it was in like brand new condition but now it seems the brick problem is still around
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
But will they still replace it if I'm not using it with a plan? I bought it from someone else and I never re-activated it.
I've called sprint and since I don't have the phone under my account and since it is not activated, they will not repair it. So a replacement/repair is out of the question. So is there anyway I can fix this myself? I'm familiar with flashing and all that stuff, so any of that stuff is just fine.
There is no way you can repair this yourself.
And eek! This problem's back? What? You were using the latest nightly too?
And since you have no warranty (pretty sure its non transferable), you should look up JTAG services. $60. It may not be as clean as you'd like, though. Besides, HTC repair service wouldn't fix your device for free because, even though the device is bricked, they can see your tampered boot loader. They charged me $200. I probably won't root again.
This has happened to at least a dozen people, but all if them were before July 3rd. This is kind of disturbing.
sauprankul said:
There is no way you can repair this yourself.
And eek! This problem's back? What? You were using the latest nightly too?
And since you have no warranty (pretty sure its non transferable), you should look up JTAG services. $60. It may not be as clean as you'd like, though. Besides, HTC repair service wouldn't fix your device for free because, even though the device is bricked, they can see your tampered boot loader. They charged me $200. I probably won't root again.
This has happened to at least a dozen people, but all if them were before July 3rd. This is kind of disturbing.
Click to expand...
Click to collapse
Hey, it's always worth a try. I always used the latest nightly. I updated whenever they pushed a new update. I had it running CyanogenMod 10.1 Nightly for over a month without a single problem. I've been using it on my Galaxy Nexus for over a year. This is the first time it's ever given me a problem.
I'll look into the JTAG, but if anyone else has any ideas I'm up to try anything. The bright light while holding Volume Down + Power didn't work for me.
OP.... wow. Just wow.
So you have the device's processor spinning at 1.7 GHz constantly, and you are wondering why it is warm? You are also running a custom OS with a myriad of bugs and issues, and you are wondering why now your device isn't working properly.
Unbelievable. You shouldn't be playing around with its powerful hardware if you have absolutely no clue what you are doing, don't you think?
Sent from my SM-N900T
Admiral Sir Manley Power said:
OP.... wow. Just wow.
So you have the device's processor spinning at 1.7 GHz constantly, and you are wondering why it is warm? You are also running a custom OS with a myriad of bugs and issues, and you are wondering why now your device isn't working properly.
Unbelievable. You shouldn't be playing around with its powerful hardware if you have absolutely no clue what you are doing, don't you think?
Sent from my SM-N900T
Click to expand...
Click to collapse
I did know what I was doing. I was running a stock build flashed by RUU. So I assumed that it would have a decent frequency management (that should be a safe assumption). I know what I'm doing when it comes to android's. I'm not stupid enough to have the CPU running at the full 1.7 GHz. Immediately after it started getting warm again that was the first thing I checked. Normally I underclock my devices. I usually have my Galaxy Nexus run at 700 MHz. I've also been using Nightly builds for my Nexus for over a year and I've found it to be stable enough to decide to flash it on my HTC One. And until 2 nights ago, It was perfectly stable.
I've done no fault on my own. I personally blaim HTC for pumping out a ROM that let it run at 1.7GHz 24/7, even unrooted.
Also to include, while I was running CM 10.1 I had my CPU set to a minimum of ~300MHz (forget exact frequency) and a maximum of 1.7GHz. I'm not stupid enough to set it to run at 1.7GHz 24/7 for any reason whatsoever. I was shocked when I saw that it had been running at 1.7GHz 24/7 (had only been running for an hour in sleep mode at that point before I fixed it).
Admiral Sir Manley Power said:
OP.... wow. Just wow.
So you have the device's processor spinning at 1.7 GHz constantly, and you are wondering why it is warm? You are also running a custom OS with a myriad of bugs and issues, and you are wondering why now your device isn't working properly.
Unbelievable. You shouldn't be playing around with its powerful hardware if you have absolutely no clue what you are doing, don't you think?
Sent from my SM-N900T
Click to expand...
Click to collapse
?
10.1 is very close to stable...
Except, you know, the bricking issue.
Where does it say the device was maxed out on purpose? Stock CM is supposed be pretty good at CPU management.
So now we know what is causing the bricks. The CPU is literally self destructing. We should have deck look into it.
I'm considering selling it to technollo.com . With a promo code, they will pay $70. I only payed $230, so I might as well just cut my losses.
ammuica said:
I'm considering selling it to technollo.com . With a promo code, they will pay $70. I only payed $230, so I might as well just cut my losses.
Click to expand...
Click to collapse
Really sucks man.
Again, just goes to show. If you can't afford to lose/fix your device, then you shouldn't be rooting it and stuff. HTC makes no guarantees that the phone will be able to run AOSP ROMs. The devs just do their best. Phones are getting more and more complicated, and it gonna get harder and harder to make stable ROMs for them.
Looks like this is your only option... maybe you can go and get yourslef an N5 when it comes out as a replacement?
sauprankul said:
Really sucks man.
Again, just goes to show. If you can't afford to lose/fix your device, then you shouldn't be rooting it and stuff. HTC makes no guarantees that the phone will be able to run AOSP ROMs. The devs just do their best. Phones are getting more and more complicated, and it gonna get harder and harder to make stable ROMs for them.
Looks like this is your only option... maybe you can go and get yourslef an N5 when it comes out as a replacement?
Click to expand...
Click to collapse
Well I think it's worth the risk. Usually I can fix nearly any software issue possible. However, this is a hardware issue. I love modifying my devices and I won't stop anytime soon. My Personal computer currently has full liquid loop (GPU + CPU) that I setup and maintain that I am proud of. Sometimes things just go wrong. That's no reason to give up. For now I'll just continue to use my Galaxy Nexus until I find it necessary to upgrade.
However if anyone would be interested in purchasing this HTC One from me, just message me and we could try to work something out.
ammuica said:
Well I think it's worth the risk. Usually I can fix nearly any software issue possible. However, this is a hardware issue. I love modifying my devices and I won't stop anytime soon. My Personal computer currently has full liquid loop (GPU + CPU) that I setup and maintain that I am proud of. Sometimes things just go wrong. That's no reason to give up. For now I'll just continue to use my Galaxy Nexus until I find it necessary to upgrade.
However if anyone would be interested in purchasing this HTC One from me, just message me and we could try to work something out.
Click to expand...
Click to collapse
I never asked you to stop rooting. It was just a PSA saying one should only root if one can afford to lose or fix one's device.
English is stupid.
I don't know if this will catch on or not, but I'd like to hear people's stories on how they screwed up or thought they screwed up their phone and fixed it? I think this could be an interesting thread with plenty of good stories and such
absoluterebirth said:
I don't know if this will catch on or not, but I'd like to hear people's stories on how they screwed up or thought they screwed up their phone and fixed it? I think this could be an interesting thread with plenty of good stories and such
Click to expand...
Click to collapse
I haven't screwed this phone up but I remember when I first started rooting phones I bricked my Vibrant (Galaxy S). I think I bricked it because I flashed the wrong radio or something. After that I have never bricked another phone. **Knock on wood**
Now I take extra caution and read extensively before rooting, flashing Roms, kernels etc.
sent from my neXus 5
Heres how i screwed my Nexus 5 on stock, I forgot to charge it and its now dead..
How i fixed it? I charged it :good:
I didn't because I actually read the stickies on the top of the general forum.
/Thread
Sent from my Nexus 5 using Tapatalk
Just took apart my Nexus 5 after it was unresponsive after a week of putting into rice/silica gels. No idea of what I am doing. I have never opened anything up in my life. Soaked motherboard into isopropyl and cleaned it with toothbrush, dropped it like 10 times, ripped a couple of cables. Should be all good though. Will post if it worked.
eastpac said:
Just took apart my Nexus 5 after it was unresponsive after a week of putting into rice/silica gels. No idea of what I am doing. I have never opened anything up in my life. Soaked motherboard into isopropyl and cleaned it with toothbrush, dropped it like 10 times, ripped a couple of cables. Should be all good though. Will post if it worked.
Click to expand...
Click to collapse
Yeah, ripping cables is probably not going to turn out "all good". Just my opinion
markdapimp said:
Heres how i screwed my Nexus 5 on stock, I forgot to charge it and its now dead..
How i fixed it? I charged it :good:
Click to expand...
Click to collapse
Please accept this Thanks as your post is very accurate and straight to the point.:good: Many of us have had that experience before whether it's forgetting to charge it over night by not plugging it into a charging source or it running out of battery power from heavy/extented usuage and not being able to charge it immediately after.:highfive:
DON`T USE TOOLKITS, these are related to most screwups Oh and get your rooting/flashing/adb skills up to par
FuMMoD said:
I didn't because I actually read the stickies on the top of the general forum.
/Thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Same!
Sent from my Nexus 5 using Tapatalk
I've only totally bricked one device, that was a sprint HTC evo (og evo). I got a replacement device via insurance and due to new firmware, I bricked it trying to root it/set s-off. No fix possible, only a new phone.
As far as nexi, nexus 5 specifically, I've soft bricked it a ton of times. But, one of the reasons I love the nexus brand, its never taken any more than a nandroid restore or only once a revert to stock. Unless you Dev test (and knowingly flash untested fw) or just start randomly picking zips and flash a modem or boot loader from a different device I've found it damn near impossible to make a nexus device unrecoverable.
I did initially flash the multi-boot mod w an incompatible ROM (beanstalk) and a kernel that really didn't like the multi-boot idea either (don't remember which ver of which kernel ATM). I was stuck on the "Google" boot loader screen for hours til I tried flashing a different ROM (which also changed the kernel) and trying again. Frustrated the hell out of me, kept phone unusable for almost a whole day, and wasted a ton of my time due to my laziness to read the whole thread.
Best advice ever given on XDA, whether you are a novice/learning/a noob or a android pro many years of experience or even a skilled developer.....
ALWAYS, ALWAYS, ALWAYS... did I say ALWAYS read the whole op or even better whole op and hopefully 90%+ of the thread before you try something you are unsure of.
Sent from my Nexus 5 using Xparent Skyblue Tapatalk 2
helioXverse said:
As far as nexi
Click to expand...
Click to collapse
Nexuses
Had the device perfectly set-up, with a few twrp backups as well and then for no reason...moved those backups from the device to the pc (probably in order to free some space). Then in a sequence of screw-ups, downloaded Flashify and wiped the cache and and dalvik cache from within the app (thinking it would be cool)...AND...bootloop! No backups...nothing! Booted to recovery...wiped cache/Dalvik the usual way, still nothing! Wiped data...nothing! Couldn't get ADB to work in the recovery. Finally -> Bootloader -> Fastboot Flash Stock ROM!
Did not stop though. in the next 5 minutes I was back with custom recovery, root and Titanium backup...ready to get back the device in shape (done and dusted as I type )
Reading the undervolting thread I decided to go -75 across the board. I succeeded but then tried to push it lower. Bootloops occurred. Backup copied back to SD card from PC failed to restore (said data failed. This was my first time restoring a ROM on the Nexus 5. If someone has insight as to why this happened it would be appreciated). Decided to go aosp and flash Rasta + trinity kernel but for some reason my mobile data wouldn't activate nor could I update PRL or profile by clicking on the usual option even after reboot and continuously clicking. Now I'm just getting my phone back to the original state it was in before I screwed up my UV values. Cataclysm + ElementalX #Life of a Phone Nerd
Sent from my Nexus 5 using XDA Premium 4 mobile app
gee2012 said:
DON`T USE TOOLKITS, these are related to most screwups Oh and get your rooting/flashing/adb skills up to par
Click to expand...
Click to collapse
I actually used a toolkit to return mine back to stock after i shipped it out to LG for repair after my son dropped. It was much easier for me than to write out the commands. took me about 10 minutes and that was because I locked the bootloader before flashing a zip. and i had to go back yada yada but worked out fine.
Screwed up 2 Galaxy S2's, first one because I didn't pay close enough attention to the brickbug, second one because it just died... Due to the brickbug. Other than those I've never killed a phone. I thought I had broken my friends Nexus 5 though, I unlocked it and went to root it for him but TWRP/CWM couldn't mount any partitions because it's "encrypted". Got it fixed though.
I've killed xbox's, PSP's, everything. It's all part of the learning process.
...When I first got my Nexus 5 in MTP on my Windows PC I had my phone hooked up to, on Internal Memory I saw a folder called sdcard that was not there before that was supposedly empty according to MTP. Deleted it. Turns out it was a symlink screwup in MTP, and it deleted my entire SD card including photos, luckily the important ones were already uploaded to Facebook and such. Now I backup my phone almost daily just in case.
I bricked my Archos Home Connect 35 once. Kinda my fault. I had set the bootloader to boot SDE firmware for it defaultly on boot. (Dev edition firmware from Google that was rootable). I updated from .82 firmware to .83 firmware, forgot to change that. It took the SDE firmware out, normally youd have to reinstall it, and since it was set to boot from that in Archos. mess of a firmware and bootloader, it would just bootloop because the SDE firmware wasnt there. No way to get out of it. RMA'd it and got a new one from Archos though. Never again, will always just manually select the SDE Dev Edition firmware when/if i ever reboot it. (Its just a Alarm clock mostly that plays Pandora occasionally. it last went 300 days without a reboot until it hard locked and I had to reboot. )
Never had a unrecoverable problem with my Galaxy S4, or my Nexus 5.Worst case with the S4 I Odin'd back to stock firmware. Nexus 5 got a corrupt data or cache partition once, i could have ran fsck but I flashed stock images instead.
I was having an issue having my phone seen on my PC. This is after I've rooted... Transferred music and pics from PC to phone, so I knew my drivers were installed. So I tried going back to stock. I downloaded the stock image and tried fastboot flashing. My download was corrupted. It got froze sending the radio. Froze for 30 min... Just kept saying sending. So I finally unplugged and rebooted to bootloader as everything else has been wiped. Tried again and it froze again at sending the boot loader. Froze for 30 min. I unplugged and tried rebooting. It never turned back on. No charging indication or anything. Officially bricked. I had tmo send me a new one and I'm returning the old one today. Wish me luck
First brick of my life and I've been rooting and modding since the OG Nex1
Sent from my Nexus 5 using Tapatalk
My GPS was working intermittently so I applied the cardboard fix and now its great. But in the process I damaged my back cover and now NFC and wireless charging don't work.
Really wishing I just RMA'd it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
My phones original lcd panel and digitizer got busted 2 weeks ago. I bought spare parts from internet and its now working. But weird thing happened. On my previous screen I have never experienced a single white screen issue but now I am one of the few to have it. Its gotta be an issue about several panels. And my screen quality dropped heavily... Gonna lend this phone to my dad soon anyways. I just wanted to warn you guys.
What ROM are you using? If you're using CM 10.1 try to install the 07/07/2013 build (why don't you try the 07/07/2013 build by bleached? It works very very well! :good: )
I know but I am not gonna bother. stock seems fine right now.
Excuse me, explain right..
You have a whitescreen issue with Stock ROM?
Sent from my GT-S6500 using XDA Free mobile app
rhisendark said:
My phones original lcd panel and digitizer got busted 2 weeks ago. I bought spare parts from internet and its now working. But weird thing happened. On my previous screen I have never experienced a single white screen issue but now I am one of the few to have it. Its gotta be an issue about several panels. And my screen quality dropped heavily... Gonna lend this phone to my dad soon anyways. I just wanted to warn you guys.
Click to expand...
Click to collapse
About this, I think that you keep the screen on direct sun light! Or under a desk lamp.
I recommend, to keep the phone on cold places.
I had same problem when I had the phone on my bag at school.....It was automaticaly turned off, and when I try to power on it says battery low.
(Even I charged it before).
Antox97 said:
Excuse me, explain right..
You have a whitescreen issue with Stock ROM?
Sent from my GT-S6500 using XDA Free mobile app
Click to expand...
Click to collapse
no not on stock. stock works fine. having whitescreen issues with cm and omni rom after I changed my lcd panel and digitizer.
Sent from my GT-S6500D using XDA Free mobile app
So I was using my vs980 today and I unlocked it and noticed columns of dead pixels along the right hand side. This phone was bought in may and has always been in a case and has never been dropped. Is this a known issue with the phone? Do I bring it to Verizon or contact LG?
Haswell4200 said:
So I was using my vs980 today and I unlocked it and noticed columns of dead pixels along the right hand side. This phone was bought in may and has always been in a case and has never been dropped. Is this a known issue with the phone? Do I bring it to Verizon or contact LG?
Click to expand...
Click to collapse
Known issue. Usually occurs after flashing, but has been reported not always the case.
If you're rooted, return to stock and warranty that bad boy.
Sent from my VS980 4G using XDA Premium 4 mobile app
Okay I flashed a lot in the past few days. Is there anything I need to do besides returning to stock?
Haswell4200 said:
Okay I flashed a lot in the past few days. Is there anything I need to do besides returning to stock?
Click to expand...
Click to collapse
Nope. Just make sure it says unrooted in settings and in download mode. I also went in and registered the my Verizon app and played a bit, just to make sure. But that's probably not necessary.
Sent from my VS980 4G using XDA Premium 4 mobile app
I've been reading online about it and it seems to happen to certain panels. Do I need to flash a different kernel to fix it? I noticed that when using the phone that some of the lines will disappear then reappear. I also have the jdi panel if that helps.
Haswell4200 said:
I've been reading online about it and it seems to happen to certain panels. Do I need to flash a different kernel to fix it? I noticed that when using the phone that some of the lines will disappear then reappear. I also have the jdi panel if that helps.
Click to expand...
Click to collapse
Once the pixels are dead, you need a new panel.
Mine went on me yesterday when I was restoring a rom, just flashed it back to stock last night so I can take it in the store and get it replaced.
When did you buy yours? I would rather bring it into the store than warranty it.
Well Ive gone from six black lines to four. They keep disappearing.
Haswell4200 said:
When did you buy yours? I would rather bring it into the store than warranty it.
Click to expand...
Click to collapse
February, even if you take it to the store, they are just going to ship you another one. Mine's coming Tuesday, hoping it's not a messed up refurb.
OK thank you
mjones73 said:
February, even if you take it to the store, they are just going to ship you another one. Mine's coming Tuesday, hoping it's not a messed up refurb.
Click to expand...
Click to collapse
I got my replacement yesterday, I think it's a new phone, it had the LG protectors on it vs the generic wrap I've seen on refurbs.
mjones73 said:
I got my replacement yesterday, I think it's a new phone, it had the LG protectors on it vs the generic wrap I've seen on refurbs.
Click to expand...
Click to collapse
I got mine today. It had some stickers an it and said "certified like new replacement" I think it's a refurb. How do I prevent black lines if I want to flash again?
Haswell4200 said:
I got mine today. It had some stickers an it and said "certified like new replacement" I think it's a refurb. How do I prevent black lines if I want to flash again?
Click to expand...
Click to collapse
It's a risk with flashing roms, there's no one answer on how to stop it.
Mine done this after flashing and I sent mine in and got new one and they never said a thing
Sent from my VS980 4G using XDA Free mobile app