This is finally starting to get some attention.
Just wanted to let others know who have this problem to check these links out for more info and to share your bug reports, findings.
If we're lucky maybe Google will finally admit there's a problem and do something about it.
https://code.google.com/p/android/issues/detail?id=227849
http://www.androidpolice.com/2016/1...toff-problem-and-its-becoming-a-safety-issue/
https://www.reddit.com/r/Nexus6P/comments/5j6qyc/report_your_early_battery_shutdown_issue_directly/
Well.. my 6P is DEAD after the update.. it worked for a day, rebooted and then bootloop. I sent it to two repair services with no result. At this point I can only enter bootloader. Is anyone kind enough to point me to what I can do to bring it back? Burying it seems the only option right now *sadface*
Try the NRT,...Nexus Root Toolkit. Go on YouTube to see how to set up and use it.
Sent from my Pixel XL using XDA-Developers mobile app
Anyone with this issue yet a clean install? I'm not in the mood to do so, so if others have tried without success of be appreciative of the knowledge.
rbrenart said:
Anyone with this issue yet a clean install? I'm not in the mood to do so, so if others have tried without success of be appreciative of the knowledge.
Click to expand...
Click to collapse
Yeah, I've tried a clean install and still have the same problem.
I'm convinced it's a hardware issue.
Thanks for letting me know, just finished a support chat. They seem to think it's a faulty battery and are sending a new (refurbished) device. We'll see what happens.
I had this issue almost daily once I went to 7.0. Even with clean installs if I remember right. I got a refurbished phone over a month ago and it hasn't happened since. Plus my battery life is better or at least as good as when I got my original phone a year ago.
Sent from my Nexus 6P using Tapatalk
maybe Google purposely did this so people with Nexus 6P will upgrade to Pixel :silly:
whoisrikk said:
Well.. my 6P is DEAD after the update.. it worked for a day, rebooted and then bootloop. I sent it to two repair services with no result. At this point I can only enter bootloader. Is anyone kind enough to point me to what I can do to bring it back? Burying it seems the only option right now *sadface*
Click to expand...
Click to collapse
I was having same issue. Until someone referred me to a guide burried deep in the forum. Basically, the procedure involved flashing the stock MM image then booting into the bootloader and flashing custom recovery (TWRP) through bootloader. Then the OP provided link to a TWRP backup that I manually transferred to the twrp backup folder on my phone. Entered recovery and restored my phone through that backup. Only then did it work. Took me about 6 hours after much trial and error. But God bless that person. If I find that guide I will post a link here to exit bootloop!
P.s. Just remembered I had it bookmarked. It worked for me. Give it a try!
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938
hashim71 said:
I was having same issue. Until someone referred me to a guide burried deep in the forum. Basically, the procedure involved flashing the stock MM image then booting into the bootloader and flashing custom recovery (TWRP) through bootloader. Then the OP provided link to a TWRP backup that I manually transferred to the twrp backup folder on my phone. Entered recovery and restored my phone through that backup. Only then did it work. Took me about 6 hours after much trial and error. But God bless that person. If I find that guide I will post a link here to exit bootloop!
P.s. Just remembered I had it bookmarked. It worked for me. Give it a try!
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938
Click to expand...
Click to collapse
My friend..if this works, I'll find you and the op of that post and give you a huge beer.
hashim71 said:
I was having same issue. Until someone referred me to a guide burried deep in the forum. Basically, the procedure involved flashing the stock MM image then booting into the bootloader and flashing custom recovery (TWRP) through bootloader. Then the OP provided link to a TWRP backup that I manually transferred to the twrp backup folder on my phone. Entered recovery and restored my phone through that backup. Only then did it work. Took me about 6 hours after much trial and error. But God bless that person. If I find that guide I will post a link here to exit bootloop!
P.s. Just remembered I had it bookmarked. It worked for me. Give it a try!
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938
Click to expand...
Click to collapse
That's for recovering from a bootloop? This thread is for the battery shutting down below a certain %.
whoisrikk said:
Well.. my 6P is DEAD after the update.. it worked for a day, rebooted and then bootloop. I sent it to two repair services with no result. At this point I can only enter bootloader. Is anyone kind enough to point me to what I can do to bring it back? Burying it seems the only option right now *sadface*
Click to expand...
Click to collapse
B3501 said:
That's for recovering from a bootloop? This thread is for the battery shutting down below a certain %.
Click to expand...
Click to collapse
That was just an answer to the first comment I saw on the post.. Thought I'd help. But with the battery issue.. My phone seems to die around 5-10℅ battery depending on the day
Sometimes mine dies between 5-15%. Never seen it happening with more juice in it then 15% though. I'm thinking about going back to the online shop where I bought it from.
my does it at 15% automatically.. but sometimes at 35% it shuts off.. then i reboot and its at 30%.. like wth..... I moved on to the V20 (t-mobile had a crazy black friday deal) but I kept the nexus 6p. I really like the phone... does it on both stock rom and custom..
For whatever it's worth I don't have that issue purchase my Nexus 6p 3 months ago at Best Buy
Sent from my Pixel XL using XDA-Developers mobile app
I don't have that issue. And I have the phone since Dec 2015. It only appeared to restart twice while on DP2 (in all realness, it sat at the "enter screen unlock pin").
I highly doubt it's a hardware issue since it started with Nougat. Did anyone of you roll back to MM and see if the problem persists?
wow the google issue site has skyrocket.. it was at 75 replies. two days ago to 455 as of now.. all same issue...
Lets keep this updated with any & all info.
Gotta get Huawei or Google to take responsibility for this.
They have to know that we all can do a Samsung to their bottom lines.
I'm getting my RMA new one tomorrow but today was a mess again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 06:30 PM ---------- Previous post was at 06:01 PM ----------
Puck24 said:
I don't have that issue. And I have the phone since Dec 2015. It only appeared to restart twice while on DP2 (in all realness, it sat at the "enter screen unlock pin").
I highly doubt it's a hardware issue since it started with Nougat. Did anyone of you roll back to MM and see if the problem persists?
Click to expand...
Click to collapse
Yes, it happened on MM too although Im on Nougat now.
I've read about this issue for months and always thought I was one of the lucky ones since I'd never experienced it, until one day a few weeks ago I turned the phone on and launched the camera, with about 15% battery left and was met with the "shutting down..." screen.
Since then it's happened sporadically, with the battery anywhere between 10-25%. And other times I've been able to use the phone right down to the single digits.
But yesterday took the cake. I thought I was in the clear, as I was around 50%, so I went on a trip through the junkyard to look for parts for my car. I hadn't been to a junkyard in many years, so it was a bit of an event, and I looked forward to snapping a few pics of the interesting cars I might see.
Pulled the phone out once and snapped a pic and a snapchat video, and right after I hit the send button in snapchat, the phone powered down. Now it was cold and windy, which may have had something to do with it, but even after putting the phone back in my pocket and warming it up with my hand, I powered it back up and the battery meter read 1%.
Now I'm not usually one to complain, but how can a battery drop from 50% to zero in one second? This has to be a hardware issue, and I don't know whether to wait until I'm near the end of my warranty period to replace it, or do it now and risk the replacement device not showing signs of the same issue until after the warranty expires.
It sucks, but I'm finally a part of this crew.
Related
After flashing, the phone sometimes had came up color distortion. After reset..It will back to normal. But today the phone stuck on color distortion and reset with no luck. Please help how to bring it back to normal..
Thnx!!!
can you post some pictures so we get an idea of what you're dealing with?
I have the same problem every now & then. I even had it in for repairs but they only re-flashed it When this problem occurs, try "tapping" on the screen with your fingers or on the back of the phone. Works for me everytime.
A couple of times I've had green/yellow horizontal streaks on the screen. The icons etc under the streaks are still visible but discoloured.
This cannot be captured in a screen shot taken on the phone, I've tried and the capture looks Ok once the streaking has gone
Is this similar to your problem?
ericjennings said:
A couple of times I've had green/yellow horizontal streaks on the screen. The icons etc under the streaks are still visible but discoloured.
This cannot be captured in a screen shot taken on the phone, I've tried and the capture looks Ok once the streaking has gone
Is this similar to your problem?
Click to expand...
Click to collapse
Yes, same problem.
I don't know what causes it but I haven't flashed my phone.
The first time it happened I could only clear it by taking out the battery.
Then I cleared it a couple of times by soft reset and a couple of times just by unlocking the phone.
I emailed HTC and they suggested a hard reset.
i have the same problem
i tried task 29 which fixed the problem
after 5 days the same came back ( problem ) , when i tried task 29 it didnt fix the problem
not a good sign...i have the same problem, mine gives me blue strips across icons n stuff...tried reflashing n task29, doesnt help....i was thinking to change the radio, now its 2.08.50...just a try..pls post if u find something....
what happened after flashing the new radio
mshabandar said:
what happened after flashing the new radio
Click to expand...
Click to collapse
no change...i saw this discoloring from the progress bar while flashing the rom...which suggests its not the rom's fault... there must be some other issue with it....
this is some fotos showing my device's color issue
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
yeap...looks exactly same as mine...expect that my one has only blue distortions, seems like some of us r stuck with very bad deal.... if its a hardware issue then we have a big problem, at least i have a big problem...dont have the warranty...
Tahmaseeb said:
yeap...looks exactly same as mine...expect that my one has only blue distortions, seems like some of us r stuck with very bad deal.... if its a hardware issue then we have a big problem, at least i have a big problem...dont have the warranty...
Click to expand...
Click to collapse
my warantee still valid - but i flashed many ROM's and hard SPL the device and i have to returned the device to the original status before send it to the dealer which i dont know how to do that ?
do u know how?
mshabandar said:
my warantee still valid - but i flashed many ROM's and hard SPL the device and i have to returned the device to the original status before send it to the dealer which i dont know how to do that ?
do u know how?
Click to expand...
Click to collapse
yea, search for "original shipped rom"...look around u will get all the info...i was planning on going back to the original thinking maybe it will get fixed if i do so....but i saw someone who bricked his phone trying to go back, n he is kinda stuck...that scared me...by the way did u have this problem after flashing the new roms or before..???
Tahmaseeb said:
yea, search for "original shipped rom"...look around u will get all the info...i was planning on going back to the original thinking maybe it will get fixed if i do so....but i saw someone who bricked his phone trying to go back, n he is kinda stuck...that scared me...by the way did u have this problem after flashing the new roms or before..???
Click to expand...
Click to collapse
i think before the first try to fix this problem was by using task 29 - this fixed the problem for 5 days then this issue came back and when i tried to use the task 29 again it wasnt work and the problem not fixed
then the distortion was very minor then it found growing day by day till it reach the full screen
regarding how to return the device to the original factory setting - yes i have the original rom but it is no the rom only - i have to return the device to the same SPL and also to find any other things might be exists in the original setting
if the dealer catch me that i flashed other roms he might refuse to fix the issue in order to save the fixing money
moreover
i got another worst and serious issue
my phone since 3 days is not able to receive the signal -
that doesnt sound good...anyways ...check this out...http://forum.xda-developers.com/showthread.php?t=779088&highlight=flashing+original+spl
Help please
Hey Guys...
I am also facing a similar issue.
http://forum.xda-developers.com/showthread.php?p=8036565#post8036565
What can I do now?
Can someone explain what is task 29?
I tried a hard reset today but nothing happened. Its still not working. Now I am facing an additional problem.
The phone keeps throwing me back to the home page. Whatever I open, whatever I do, the phone just throws me back to the home page within 2-3 seconds.
Can this be attributed to some virus?
Thanks,
Mohit Goyal
task 29 is a software to delet the rom and will make the phone withought any rom
about this issue, i submitted the same question in other forum and the experts told me that it is a motherboard issue
i am going to take my phone to the dealer and will update you about the reason soon
Me too....I think HD2 is under Virus Attack.
http://forum.xda-developers.com/showthread.php?t=776796
pack21 said:
I think is a virus or something else, because has happened to many people lately.
I also had the issue as pictured above.....and exactly as described in the first post.
It began to occur about three weeks....and gradually was getting worse.
Click to expand...
Click to collapse
Hello,
So, I have had a custom flash for some time. I don't use this phone too often and it sat off with a dead battery for about 2 weeks.
I plugged it in and turned it on. It booted into the custom rom for windows just fine. I went to reboot into Android like I normally would and it got stuck at the main boot screen but never displayed the rom / radio red text in the bottom left of the screen.
I've set it sit like that over night with no dice.
I have tried task29, reflashing HSPL, removing HSPL. I can't get anything to complete. It seems like as soon as anything tries to write into the phone's internal RAM is dies. I've tried flashing different radios but nothing takes once the 7 vibes hit.
Any ideas on what this is and any other ways to get around it. I've tried hard-resetting. When it says to press Vol-Up to boot it just gives me 7 vibes and a blank screen.
Where do I go from here?
Cheers,
Ech0
Here is what my boot loader says:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Really, no one?
Im having the same problem guys... i have a tmo us hd2 1024... it is stuck at the stick together screen and the r,d,g red letter that appear, are not doing so... oddly enough it can flash roms...
sorry for my bad english...
you must install the latest stock-rom from sd-card.
copy the *.nbh from stockrom to the sd-card and renamed to leoimg.nbh.
just restart your hd2 and follow the text on the screen.
So what exactly is the significance of the 7 vibrations?
I got the same problem. I managed to reflash the phone after MTTY and flashed HSPL, bootloader, radio and ROM. Made hard reset. No luck, it freezes again and again.
I wonder what these 7 vibrations mean? Anybody know?
sorry to re dig up this thread but i have been having the same issues 7 vibrations and it just gets stuck on the boot up splash screen. Does anyone have a solution to this?
I have the same problem with my hd2 original rom... It first went a little warm on the back after heavy using with movie mp3 internet and youtube, it reboots and hang, had to remove the battery and wait to let it cool down....
I think it was a bug, so i downloaded the newest rom software from HTC and updated it... Now when i using it on the same way, movie internet mp3 and youtube it still reboots and hang, But it gives me 7 vibrations and stay in the boot screen,.. or it reboot again and again....
Remove the battery, cool it off and it works ok until.... it gets warm....
Called HTC and they sait that it could be a problem with the motherboard...!!! For now i am waiting for my device.... I send it to HTC for repair.... expect him any day now.... hope they fixed it.....
Just an update on my 2x HD2's.
Both went into repair and came back with "No Fault Found!'
So afterwards i sent it to a different repair centre who agreed with my diagnosis that the motherboard was faulty on both devices.
Subsequently they replaced the motherboard and now the HD2's are working as they should.
It used to lock up at around 33c. now with the replacement motherboard it runs fine even up to 45c! ( i used battclock to monitor device temp!)
Very interesting! I think I should send my HD2 for repair too. Did you use warranty service or paid money for the repair?
Always sent in for warranty!
My phone was bought in Frys. I asked my friend to bring it directly to T-Mobile office, they said "Go to Frys and let they repair it". He came to Frys, they said "It's T-Mobile thing, we can't help, give it to T-Mobile".
Please advise, how to get it repaired?
Call HTC or Tmobile and ask for the closest authorised repair centre. drop your device in directly with the proof if purchase and get it repaired.
T-Mobile declined to get it for repair once again. Friend of mine visited 2 T-Mobile offices and Radioshack shop and was sent to HTC everywhere. Maybe it's local Texas habit...
Will try to send it to HTC service.
Hi guys,
I've been faced exactly the same problem, but also have found (a bit of... strange, let's say... and temporary, somehow) solution. Read below...
I found out that the seven vibration signal indicates motherboard issues. AND - as in most of cases mentioned right here, in this topic - the error wasn't occuring immidiately, but after a few minutes since turning the device on. So what I thought is that the phone was simply overheating, or even if it was not - the temperature indicator wasn't working OK and as a result we were getting this error.
As I found this out after long hours of trying to get things work, here a quick guide how to fix what you probably messed up during your efforts:
1. If you tried to reinstall ROM or any other software using USB cable and things didn't go well - don't worry, it was the same for me. Firstly, we need to clean up. Run the installer on your PC again, then try again, the error will occur, and after it does follow the instructions on the screen UNTIL THE INSTALLER ASKS YOU TO CONTINUE AND INSTALL ANYTHING AGAIN. Don't do it, just pull the cable off the phone.
2. What you need to do now, is to download a new ROM, then copy it onto the microSD card, then rename to "LEOIMG.nbh". Turn the phone on with VOL- pressed down, and then confirm installation with the Power button.
Okay, we have got it all installed and... not working. Probably the white HTC splashscreen and nothing more. And after the reset, 7 vibrations again. Now, the magical trick.
Put your phone into the fridge. Seriously. Take out battery, put it into some plastic bag (so it won't get wet) and put it to the fridge. Wait 20 minutes or so, then turn it on and enjoy temporarily working phone. It was fine for me until I started to use Opera.
Further solution? Well, working on it.
P.S. Sorry for refreshing old topic, but the problem doesn't seem to be solved and I'm trying to push things forward.
I have gone from Gingerblur, to Alien, to all the CM7 betas without a single problem.
After installing Faux's 2.0 enhanced kernal on my CM7, I now have a dead region of my touchscreen which is a little above the middle of the screen, 1/4 inch all the way across (horizontally). I verified this by using the touch test app from the market.
It is also very obvious as scrolling is extremely laggy.
I have already tried wiping my phone with fastboot, performing the PDS fix, and then wiping again in recovery and reinstalling CM7.
On top of that, the entire touch screen will become unresponsive at times. For example, I will receive a phone call and when I try to perform the unlock swipe to answer the call, nothing will register. I have to turn the screen off, then turn it back on and try again.
I had been running the CM7 beta for weeks with no hiccups what so ever but even though I am back on 100% 2.4 Motoblur, no fix.
To try to get as close to stock as possible, wipe with fastboot, install 1.83, then download the OTA update to Gingerbread, gets rid of Unlocked logo on bootscreen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here are other people with the same issue:
https://supportforums.motorola.com/thread/59412
https://supportforums.motorola.com/thread/59342
http://forum.xda-developers.com/showthread.php?t=1297626
fsturbo15 said:
I have gone from Gingerblur, to Alien, to all the CM7 betas without a single problem.
After installing Faux's 2.0 enhanced kernal on my CM7, I now have a dead region of my touchscreen which is a little above the middle of the screen, 1/4 inch all the way across (horizontally). I verified this by using the touch test app from the market.
It is also very obvious as scrolling is extremely laggy.
I have already tried wiping my phone with fastboot, performing the PDS fix, and then wiping again in recovery and reinstalling CM7.
On top of that, the entire touch screen will become unresponsive at times. For example, I will receive a phone call and when I try to perform the unlock swipe to answer the call, nothing will register. I have to turn the screen off, then turn it back on and try again.
Please guys, any ideas? The only thing I can link to this problem is faux's kernal. I had been running the CM7 beta for weeks with no hiccups what so ever but even though I am back on 100% stock CM7 fresh install, I still have this problem.
-Thank you
Click to expand...
Click to collapse
try to go back to stock with a fruitcake. If that doesn't work, flash the gingerbread sbf with rsd lite. Id that didn't work then you probably need a new digitizer
Sent from my MB860 using xda premium
Well, I have done some research and others are having the same problem.
Looks like our phones digitizers have a short lifespan and eventually simply fail.
Will be calling for a replacement asap.
OP updated with links to others with the same problem.
Also, I've noticed more and more people seem to be getting an issue where there is a ghost finger over the letter q in portrait keyboard.
Seems like a software issue to me. Problems only arise once any flashing has taken place, especially kernels.
I have the exact same problem. Is it confirmed to be a hardware problem?
Sent from my MB860 using XDA Premium App
I have seen the same issue as mine occur on phones that have never been flashed by an end user before.
I should add:
Flashing a new ROM doesn't help.
Flashing PDS doesn't help.
Flashing with RSD doesn't help.
The only thing I've found to help is the Samsung Galaxy S touchscreen booster app. Generally, if I do this a few times: apply any random setting in the app, restart phone, apply a new setting again
The problem goes away for a while.
The problem also goes away and comes back again by itself, but the SGS booster app seems to help.
I have no idea if the issue is software or not. The randomness makes me think it is a hardware issue, but the fact I can make it go away for a while with the SGS booster app doesn't.
I have the same problem. Sometimes I knock the screen and it is getting better for a while. According to forums, AT&T replaces phones with that problems. But Orange has a ROM with a fix. http://www.motorola.com/staticfiles...4.4.20_Orange_GB_Upgrade_Release_Notes_GB.htm
So, is it hardware or software problem?
Same problem for me. Took it apart, put in a new digitizer. Problem solved without touching software (Cm7). Not sure if this is true for everyone but for me it was definitely hardware.
Sent from my MB860 using XDA App
Your digitizer connector is cracked.
It happens from over heating your phone.
Ok. Thanx. I will buy it through ebay.
Sent from my MB860 using XDA App
Milenko2121 said:
Your digitizer connector is cracked.
It happens from over heating your phone.
Click to expand...
Click to collapse
Evidence please.
gekster said:
Ok. Thanx. I will buy it through ebay.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hmmm... Why don't you ask moto to fix it? My screen died in the same spot and moto fixed it.
gekster said:
Ok. Thanx. I will buy it through ebay.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
matthew5025 said:
Evidence please.
Hmmm... Why don't you ask moto to fix it? My screen died in the same spot and moto fixed it.
Click to expand...
Click to collapse
If it was a software related issue, simply erasing system,boot,preinstall,userdata and flashing a new rom or that touchscreen fix for those who messed up their partition would fix it.
Howevever since it's that area (roughly 10% of the screen horizontally) that's the first effected area.
If you're curious as to proof, use the touch screen tester app, and apply pressure to the top left of your screen in multiple areas to cause the digitizer connector to move and it will change according to the touch test app.
matthew5025 said:
Hmmm... Why don't you ask moto to fix it? My screen died in the same spot and moto fixed it.
Click to expand...
Click to collapse
Because I do not live in USA. I bought my phone through E-bay. To fix my phone through official warranty service I should spent much more money than to buy new digitizer.
Try CNN.cn I believe they have a display assembly.
*edit* found it
cnn.cn/shop/mobile-info.php?products_id=11673
Sent from my Xoom using xda premium
ATT will replace your phone if it has this issue meaning you don't have to go through the process with Motorola.
fsturbo15 said:
ATT will replace your phone if it has this issue meaning you don't have to go through the process with Motorola.
Click to expand...
Click to collapse
Anyway I have no any AT&T in my country too.
---------- Post added at 10:08 AM ---------- Previous post was at 10:04 AM ----------
d3athsd00r said:
Try CNN.cn I believe they have a display assembly.
cnn.cn/shop/mobile-info.php?products_id=11673
Click to expand...
Click to collapse
Tnanx for advise but this one too expensive.
This one much more cheaper:
http://www.ebay.com/itm/Original-NE...aultDomain_0&hash=item19cb8661c6#ht_756wt_906
Milenko2121 said:
If it was a software related issue, simply erasing system,boot,preinstall,userdata and flashing a new rom or that touchscreen fix for those who messed up their partition would fix it.
Howevever since it's that area (roughly 10% of the screen horizontally) that's the first effected area.
If you're curious as to proof, use the touch screen tester app, and apply pressure to the top left of your screen in multiple areas to cause the digitizer connector to move and it will change according to the touch test app.
Click to expand...
Click to collapse
As in the connector is cracked and overheating caused it. I had the same problem before and I checked the connectors and digitizer. No damage at all and no cracked connectors at all. It is true that applying pressure to the top of the screen causes the screen to register random inputs but after I got the phone back from moto, I found they put some plastic parts to make the top of the phone more sturdy.
fsturbo15 said:
To try to get as close to stock as possible, wipe with fastboot, install 1.83, then download the OTA update to Gingerbread, gets rid of Unlocked logo on bootscreen.
Click to expand...
Click to collapse
I'm about to wipe with fastboot, where do I install 1.83 after I wipe? Also how do I install 1.83 once I've wiped the phone? It's been a while since I've done anything really with my phone I forgot basic steps.
Bump, got some free time before I go back to school and figured I'd do this soon but still don't know how
Is anyone else experiencing these. I've only had the phone a few days but started to notice it once I put infected rom eternity on it not sure if it is a rom issue or a hardware issue
Sent from my PG86100 using XDA App
I'm having random reboots and I haven't even rooted/modded in any way. I got a system update earlier today, but it was doing it before that. It might be one of my apps, but it only happens when the screen is off and I'm trying to turn it back on to use the phone. I've tried factory resets and battery pulls so I figure its an app, or having the social lock screen.
Sent from my PG86100 using Tapatalk
It must be a hardware issue then. I've been looking into it more and it seems to be happening to slit if people on slit of roms. Most of what I found said it was kernel related but if your having it happen and your not rooted I'm not so sure its kernel related then.
Sent from my PG86100 using XDA App
mteezey said:
It must be a hardware issue then. I've been looking into it more and it seems to be happening to slit if people on slit of roms. Most of what I found said it was kernel related but if your having it happen and your not rooted I'm not so sure its kernel related then.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
It's definitely hardware. It's the proximity sensor, I believe. I picked up a phone call, and when I put the phone up to my face (I didn't touch my face to the phone, just my ear), the screen didn't shut off, and then rebooted. After it started back up, I called the person back, and when I brought the phone up to my face, the screen shut off as it should, and stayed in the call until I hit end, and it's still on. I received a second call and it had the same behavior. Reboot upon bringing it up to my face the first time, fine the second time. When I try to bring the phone out of standby I thought it was the live unlock screen I had (weather), but it seems to bee the light sensor or proximity sensor... boo..
[EDIT] Just did a factory reset. Market is installing my apps. We'll see how this time around goes.
So far so good. all my apps are re-installed. I have yet to check my games for my data, but I took a phone call and the screen turned off quickly when I brought it up to my face.
That's the same way it happened to me during a phone call but I was on hold for twwenty minutes with it on speaker and once they picked up I put it to my face and ....reboot. like you said boo
Well I got rid of eternity and with new rom(Olympus Trinity XE) and kernel mild anthrax I have not had a reboot yet. Its only been 12 hours but it was happening every few hours before.
Sent from my PG86100 using XDA App
heat
I usually have my E3D in it's Otterbox clipped on my belt, and no problems arise. Last week I went out to a bar and it was very warm in the bar, and the phone was in my pocket. It rebooted once out of the blue. I'll keep it on the belt clip.
Rooted, Stock rom.
I'm planning on getting am otterbox very soon.
As for rebooting, it's still doing it, once when a Words with Friends game wouldn't load and another time while trying to load Paradise Island. I'm now thinking it's the video driver.
I rooted my Intercept and changed the driver. I would rather not root this device if I can't unroot it...
Sent from my PG86100 using Tapatalk
Mines not rooted either and mine just rebooted like literally 3 times in a matter of 30 minutes
Sent from my PG86100 using XDA App
There is a rom to unroot. Its a stock rom once you flash turns your securities back on(s-on). Which is good in case you ever have to take it back to sprint.
Sent from my PG86100 using XDA App
I've only had one reboot with my new kernel. It seems now like its only when its on the charger I set a charging profile now to Max CPU speed of 648mhz with interactive governer gonna see if that helps. If not I'm gonna try a temperature profile.
Sent from my PG86100 using XDA App
From what I can do on an unmodified device, I found this in the "Tell HTC" log.
local_clk_disable_reg: clock 72 status stuck at 'on'
This happens a few times in the log. I've been taking screenshots of the log to post, but I haven't had the time to go through the whole log. The next time I get a chance, the phone has already rebooted 3 times. It's definitely not my app because it's no longer on my system.
Also, I don't know if this goes with it, but I sometimes have to do a PRL update to get out of roaming. I'm in my local, high-signal area... I'm eventually just going to call and get a replacement.
[EDIT]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
here we go. Here's the error message, then it dumps the memory locations. In a minute I'm going to post a link to an album I have with the log, error to end.
Another oops 17 prempt smp.
Sent from my PG86100 using Tapatalk
you got those errors running on the stock kernel ? Or a custom one?
Shot from my Shoot3Rvo
mteezey said:
you got those errors running on the stock kernel ? Or a custom one?
Shot from my Shoot3Rvo
Click to expand...
Click to collapse
This is all untouched stock from Sprint.
But wait! It gets better! I wasn't using the phone last night, and it kept rebooting every 20 minutes +/-, then it gets stuck in a boot loop (which it's still stuck in). As mentioned before, I have to update the PRL every time I reboot the phone, so could it automatically be routing itself to a bad radio? Not that it matters, I have to factory reset anyway...
I went into recovery to do a factory reset (boo... going to try to adb pull my data, first) and I noticed that during the image check, two of the images are the "wrong" image (PG86DIAG and PG86IMG... something like that). Is this bad? I went from a Samsung Intercept to the Evo 3D so there's some major differences between stock recovery and CM01 heh.
Shooter XC Ship S-On RL
HBOOT version 1.50.0000 (used to be 1.4 and I only did the OTA update and install some apps/games)
eMMC-boot
Sorry for somewhat hijacking this thread, by the way. I just think it's strange to have all these problems on a stock device (though stock isn't great... ever). When I initially came on to search about it I noticed your post and jumped right in lol.
I'm glad I didn't root this thing right off the bat because of the watermark, and because of this stupid page fault.
I think wrong image thing is just your phone searchiibg for update IMG when you open the bootloader I would have to see exactly but its normal for it to check for pcwhateverimg. Whenever the bootkaoder opens. Since you have s on and don't have to worry about losing root access it night not be a had idea to update to the latest radios . Then if you still have the problem try to tIe it back. I haven't been having the problem anymore with a new kernel and new usb cord. Since it seemed to be when I plugged in. But as ling as I don't overclock above 1.6ghz I've has no problems Anymore
Shot from my Shoot3Rvo
I'm going with the acct holder (my bro-in-law) tomorrow to get a replacement. Seems we're not the only ones. There's another thread on here about this very topic...
As for rooting it, I need to read more, but doesn't it leave a mark saying it's been modded if it's 1.5 or greater, thus not returnable? I remember the Intercept doesn't have that so it was no problem switching back and forth, but it was a b***h to get a solid root...
Sent from my PG86100 using Tapatalk
I didn't read everything on hboot 1.5 but I know there is some different steps. I know there is a ROM to flash to get back to s on which is all you need for warranty to not be void I'm sure it says whether or not it works with that hboot.
Shot from my Shoot3Rvo
Awesome to hear there's a work around for the S-On. Looks like I got some reading to do when I get home from work!
Sent from my PG86100 using Tapatalk
Oh, this is so good it has to be fattening!
So I did a factory reboot and it lasted like 8 hours, whoopee...
I bring it in to Sprint and they have the tech look at it, estimating 45 minutes to an hour. Good, I had gift shopping to do. I come back and the girl gives me the (same) phone and asks me to log in. I do, and it updated my contacts, etc. She then said "He reset and updated the software so it should be okay now."
"... so why does it still say I'm roaming?"
"It does? Let me see."
She brings it to the tech, who performs the "magical" PRL update, which I TOLD them I HAD to do after every reset I did. Fine. It's working now, and I have no roaming charges, so not worried about the bill. I go home and enjoy the rest of my time before work. I get into my work parking lot, and the phone resets. Mother ****ers. I'm back in roaming, too!
Looks like I have somewhere to be first thing in the morning and to directly talk to the tech and ask, "Did you really think that a severe page fault that's embedded into the ROM would be cleared by a factory reset? The device needs to be flashed or replaced."
I told the girl straight up that I can fix it in 20 minutes, and that I rooted and modded my Intercept on Virgin Mobile (which they sign contracts at that location for heh) and it cleared up all my problems. Then, that I can't do that with this phone because I can't return it if it screws up again.
Ugh! Why do they release crap like this?! There are thousands of people that have this phone with this rebooting problem... Shouldn't there be a recall? Even on the Sprint customer forums there's posts about it, so Sprint KNOWS of this issue, especially if a manager replaced 8 devices in one day for the same problem.
So anyway, I'm on my way home from work, and I click the phone on to pull Pandora up, and it resets, but it doesn't go back to the home screen. It's stuck in a boot loop again! YES! I removed and replaced the battery and it did it again. I took the battery out and just set it on my desk, waiting for the tech to turn it on. Hooray that it got stuck, so I can rub this in his face. I should be working there, not him. (Sorry for my ranting, I'm just tired of Android problems because of carriers changing the software and locking it up. Google WANTS people to make the software their own!)
Pull your SD card and run without it. If it stops rebooting, format the SD on a pc.
rigmort said:
Pull your SD card and run without it. If it stops rebooting, format the SD on a pc.
Click to expand...
Click to collapse
I've seen that on another forum. Thank you for the SD card insight. Just as a precaution, I'm just going to pull all the crap off my card and format it with the SD Formatter. I don't remember what the "brand" is but I know it's the right one. Should I back it up and format through the phone, or use the adapter and format the computer way? I'm thinking phone...
I talked directly to the tech today and told her what the log said and that it needs to be reflashed. After the estimated time she gave it back saying that she ran it through every test their system can run and the software has no errors (which my logs say as well), but she reflashed anyway to make sure (I'm still not sure how she logged into my gmail if she reset it...) I have to call corporate for the roaming issue because I'm connecting to the wrong tower, which she doesn't have permission/clearance to change. If, after fixing the roaming, it still does reboot, it will be replaced. I'm still under warranty, so I'm curious as to why they're trying to keep me on, what I believe to be, a defective device... Because they can't detect anything wrong with it...
I have yet to install any apps (minus Tapatalk) and the phone has yet to reboot, and its been in my pocket all day so I would have felt it reboot. Shame because it's one of my paid apps (one out of 6), Paradise Island, Angry Birds (which wasn't opened at all during this, but it was installed), or Words with Friends. I also had ScummVM but the reboots started way before I installed it and the engines. Those are the only apps I installed the last couple times because I'm sick of reinatalling all my apps. Bigger shame because I can't install apps until I'm sure of what the problem is. Why have an amazing phone I can't use a paid app on? I'm just frustrated at this point... I have a lot of back traces to read through and no list of what is what because the phone has been cleared since then... Does the memory map stay the same no matter if it gets reset? I haven't done any Linux kernel programming so I'm learning as I Google which is what it's meant for.
I really want to Update the PRL to see if it will help with my battery life, which it should, but I don't want to change anything, in case it messes up again. It will be proof its defective. Ugh... What to do...
Merry Christmas, to those who celebrate the holiday! Happy holidays to everyone!
Sent from my PG86100 using Tapatalk
...I have a lot of problems typing with a touch screen so I edit a lot to correct things... That and my screen feels my fingertip before it touches the screen...
[EDIT] My SD card has been unmounted for who knows how long! I just remounted it as is to see if it starts rebooting.
I was in class today and my phone vibrated a few times notifying me of text messages. I checked the phone when I got outside and was greeted by this screen
http://i.imgur.com/WFQ33Rf.jpg
Not my phone, but the same problem!
I've been running the same CM 10 rom for months now. I can't remember if it was a stable or RC but it was good enough that I didn't feel the need to mess with my phone for perhaps the last 5 or 6 months. It's been a while.
Details:
The phone still vibrates and receives messages. I know this because I'm confirming with google voice online that messages are coming in when its vibrating. I can turn the screen on and off, but I'm just greeted by this screen. I can force the phone to reboot by holding the power button, but even the starting animations won't show. It turns on immediately to this. During the start-up animation, it usually has a point where the screen brightens and then dims and even this occurs. The buttons and everything are all doing what they need to do. I can unlock the screen and everything as I can feel the feedback. The volume rocker works and reacts properly. Everything is working except the screen.
Any ideas?
I'd like to apologize if this is a common problem and the solution is posted somewhere as I have not frequented these boards recently and am currently at work so I can't spend much time searching.
Yeah, see my post about the confetti. It went confetti very soon after it went contrast. I run stock CPU speed with stock voltage.
Ironic that yours happens just as mine did. I'm using the phone now. I have the screen turned on to never go to sleep now so that I don't have to try and wake it up. Then I may get that screen and to prevent that? Turn it off, turn it on, turn off, turned on and eventually I'll get the lock screen.
I run meanbean rom with the 1.19 hboot, s-on. I'm going to return it to stock then take it back to sprint. Provided I can keep the phone functional long enough to do this.
This will be my second phone to do this. First 1 did it last September.
Sent from my EVO using xda app-developers app
It's a shame. I've had this since launch and haven't had a single problem with it. Unfortunately, no matter how many times I turn the screen on and off, I can't get it to the lock screen.
Edit: I have a feeling this isn't going to be an easy fix. I'm gonna switch to my brothers old Evo 3D as soon as I get home
http://forum.xda-developers.com/showthread.php?p=38160970 is my original post (first)
I would like to add the screen freezes when the battery gets to a full charge. Unplug it and it recovers almost instantly. Interesting I'd say.
Sent from my EVO using 2 kidneys and a rock.
Yeah, I went through your post. I can see that no one really had any idea for you either which was kinda disheartening. I'll have to play around with it when I get home tonight, but I'll be forced to switch to an older phone as I won't have enough time to fix this on my own right now
Sprint exchanged the first one because the grfx chip went bad according to them. My concern is that it was not that long ago and now I have the same issue. How old is your phone?
Sent from my EVO using xda app-developers app
My concern is that they won't exchange it unless I can get it back to stock, but I'm assuming there's no way for them to know considering they can't access anything on the screen?
I've had the phone since June. Never had a problem with it
I think the screen might show via the hdmi feature but I'm not going to force the issue. You should be able to answer incoming call via bluetooth adaptor. I can also listen to Pandora via bluetooth through my head unit in my truck. Also make phone calls through my head unit to but I'm not going go to the car in the phone calls unless I'm in it.
If your proficient with voice commands via bluetooth or Google Voice you maybe able to get some functionality of the phone for a little bit more time. I would like to see if other folks have this issue also.
Sent from my EVO using xda app-developers app
http://code.google.com/p/androidscreencast/
I found a link to this program which allows you to access your phones screen that I think may be helpful! I'm going to use this to get what I need off the phone, get it back to stock, and return it to the store tomorrow. I'll update this post later tonight when I get home
The only time this happened to me is when my voltages were too low. I would boot into recovery and reflash your ROM or the voltage increase script in thick lizards dev host folder.
If you can get to recovery which shouldn't be a problemyou can fix this easily.
Sent from my EVO 4G LTE using xda premium
So I'm back to stock using racun's soff procedure. I still has pixy dust issues. Will look into the thicklizzard angle tomorrow.
Zori said:
I was in class today and my phone vibrated a few times notifying me of text messages. I checked the phone when I got outside and was greeted by this screen
http://i.imgur.com/WFQ33Rf.jpg
Not my phone, but the same problem!
I've been running the same CM 10 rom for months now. I can't remember if it was a stable or RC but it was good enough that I didn't feel the need to mess with my phone for perhaps the last 5 or 6 months. It's been a while.
Details:
The phone still vibrates and receives messages. I know this because I'm confirming with google voice online that messages are coming in when its vibrating. I can turn the screen on and off, but I'm just greeted by this screen. I can force the phone to reboot by holding the power button, but even the starting animations won't show. It turns on immediately to this. During the start-up animation, it usually has a point where the screen brightens and then dims and even this occurs. The buttons and everything are all doing what they need to do. I can unlock the screen and everything as I can feel the feedback. The volume rocker works and reacts properly. Everything is working except the screen.
Any ideas?
I'd like to apologize if this is a common problem and the solution is posted somewhere as I have not frequented these boards recently and am currently at work so I can't spend much time searching.
Click to expand...
Click to collapse
Have you tried getting into the bootloader?
Sent from my EVO using xda premium
I tried using android screencast, but I don't think it's possible to get it running without interacting with the phone. I can't even connect the phone to my computer and use it as a storage device because I don't remember exactly where the buttons are. At this point, I'm considering flashing cm10 onto another device so that I can see where everything is and replicate the location of the screen presses on my LTE to try the voltage trick or reflashing the rom.
I'm very likely going to take it in as is and hope they don't have any way to see if its rooted or not and just give me a replacement.
aFoodStampBaby said:
Have you tried getting into the bootloader?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Yeah, but it still gives me the same screen.
Edit: I can't even switch to my Evo 3D because it says I need to switch my plan. This is just another sprint headache considering my plan is fine for the LTE it should be fine for the 3D. I'm gonna wake up at 4am to talk to chat since they're not currently open
Zori, is your evo S Off? Then you can flash individual kernels I think. If it is, then take a CLOSE look at unlimited.io/jewel.htm because most of that procedure is remote terminal. If you do it via ubantu, I'm thinking you can push the proper package onto the phone and update it that way.
The hardest part will be getting to recovery from the hboot screen and BAM!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The bootloader screen:
At the very least it can get you to the point of getting to stock I think. My phone seams to have recovered a bit at stock. I briefly see the confetti when I wake it. I can imagine that it would be an under volt condition while powering on. You can do it mate the force is strong.
---------- Post added at 06:23 AM ---------- Previous post was at 06:08 AM ----------
vipermod looks relevant to our issue. I will need to do some reading while the bosses are not looking.
Zori said:
I tried using android screencast, but I don't think it's possible to get it running without interacting with the phone. I can't even connect the phone to my computer and use it as a storage device because I don't remember exactly where the buttons are. At this point, I'm considering flashing cm10 onto another device so that I can see where everything is and replicate the location of the screen presses on my LTE to try the voltage trick or reflashing the rom.
I'm very likely going to take it in as is and hope they don't have any way to see if its rooted or not and just give me a replacement.
Yeah, but it still gives me the same screen.
Edit: I can't even switch to my Evo 3D because it says I need to switch my plan. This is just another sprint headache considering my plan is fine for the LTE it should be fine for the 3D. I'm gonna wake up at 4am to talk to chat since they're not currently open
Click to expand...
Click to collapse
The online esn swap always prompts you to change plans for some reason now..have to call or chat.
Sent from my EVO using Tapatalk 2
Well my phone went all confetti, all the time. Got a new one today.
Zori said:
I tried using android screencast, but I don't think it's possible to get it running without interacting with the phone. I can't even connect the phone to my computer and use it as a storage device because I don't remember exactly where the buttons are. At this point, I'm considering flashing cm10 onto another device so that I can see where everything is and replicate the location of the screen presses on my LTE to try the voltage trick or reflashing the rom.
I'm very likely going to take it in as is and hope they don't have any way to see if its rooted or not and just give me a replacement.
Yeah, but it still gives me the same screen.
Edit: I can't even switch to my Evo 3D because it says I need to switch my plan. This is just another sprint headache considering my plan is fine for the LTE it should be fine for the 3D. I'm gonna wake up at 4am to talk to chat since they're not currently open
Click to expand...
Click to collapse
How did you make out with this issue? The same thing happened to me today. Running 10.1. Cant even see revovery.
Answer to confetti screen issue
My phone did this exact thing on Saturday. I took it in to the Sprint store, and the tech there (the only one I've ever run in to who really knows his stuff, Phil in Westminster), explained that there is a cable between the battery and screen that is "kinked" and loses contact. If you squeeze the phone really hard just above the back button the screen will come back on for a bit. They did agree to send me a new phone (I am rooted, and running a custom ROM, they did not care). I've been able to get enough functionality out of it to get by for about two days, but as of last night the screen only stays on the "confetti", and won't come back at all.
Anyway, hope that helps a bit!
crapid said:
My phone did this exact thing on Saturday. I took it in to the Sprint store, and the tech there (the only one I've ever run in to who really knows his stuff, Phil in Westminster), explained that there is a cable between the battery and screen that is "kinked" and loses contact. If you squeeze the phone really hard just above the back button the screen will come back on for a bit. They did agree to send me a new phone (I am rooted, and running a custom ROM, they did not care). I've been able to get enough functionality out of it to get by for about two days, but as of last night the screen only stays on the "confetti", and won't come back at all.
Anyway, hope that helps a bit!
Click to expand...
Click to collapse
Yup.. mine started doing the same thing couple of days back..
I instinctively started pressing the screen and it came back on.. must be the same prob like ur sprint guy said..
I'm thinking of going to sprint store but I don't have their insurance or total equipment protection plan.. so, any clue on if they will replace? Do u guys have the TEP?
Edit: Let me add that I have noticed that the screen fuzziness happens whenever i put the phone in my pocket... have started carrying it around in my hand now!!
Sent from my EVO using xda premium
[email protected] said:
Yup.. mine started doing the same thing couple of days back..
I instinctively started pressing the screen and it came back on.. must be the same prob like ur sprint guy said..
I'm thinking of going to sprint store but I don't have their insurance or total equipment protection plan.. so, any clue on if they will replace? Do u guys have the TEP?
Edit: Let me add that I have noticed that the screen fuzziness happens whenever i put the phone in my pocket... have started carrying it around in my hand now!!
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I didn't think I had insurance, and they were going to charge me $50 for a replacement. After they looked at my account it turned out I did have insurance on this line, so no charge.
Unfortunately, I got the replacement last night, and sound doesn't work on this one! Getting yet another replacement on Friday.