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
Related
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
Hi guys new member pestering for help here. I've lurked anonymously for a few years getting valuable info re: phone stuff & even managed a ROM upgrade on a crappy old htc following threads here. . this is my goto forum for anything phone related & has been of great help many times. Huge thanks for that!
However, I've come across a problem on my Galaxy S4 that I can't find info about anywhere, so have decided to bite the bullet & register.
Keeping it as brief as possible, my GTi9505 Galaxy phone registered to Virgin Mobile developed what I believe is a fault shortly after an (official) OTA firmware update. Where previously mobile data (not WiFi) was very fast & the 'H' symbol was more or less constant, after the update bandwidth dropped dramatically (as slow as gprs) & only the 'E' symbol lit.
After several very long phone phone calls to Virgin technical department, they eventually fobbed me of by suggesting that the network towers local to my location were being downgraded. . :ahemB$!: They couldn't however explain why my sim in my girlfriends S4 mini was getting 3g from the same location. So, I stopped paying the bill & was cut off.
I decided to try an EE payg 4g sim in the phone & surprisingly, it works fine apart from the same bandwidth limitation. . still locked to 'Edge' regardless of location. WiFi into home router is fast & works normally. ??
I know how to get into service mode & move around so if anyone has any suggestions of settings that I might be able to check/tweak I'd be extremely grateful.
Hope one of you fine people can help
Open your phone dialer, type *#4636#* and check if your phone is locked to edge mode only. Try *#*#4636#*#* if the first command doesn't work.
Hi popthosegaskets thanks for replying. Tried both codes several times to make sure but neither of them work :/
I tried it on a Samsung Note 3 and it works, not sure why it shouldn't work. I'll get back to you about it.
Update: I got so p*ssed off trying to figure out how to fix this issue that I installed CyanogenMod 10 which works fine but still showing 'Edge' icon on mobile data in spite of changing connection settings. I expected something as radical as flashing a new OS would solve the problem but it hasn't.
Kind of weird, maybe it's a hardware issue or some part of the underlying firmware that isn't affected by the OS??
Download "4G LTE Switch" from Play Store and see if it works for you.
OK, installed. 4G LTE Switch & tried every possible option to get LTE mode to stick but it refuses to shift from 'Edge'. Definitely have 3g & 4g coverage but phone setting seems to be welded to Edge for some reason.
{
"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"
}
Edit to add: opened up the phone & checked antenna contacts & plugs. All seem to be good.
Hmm... Let me think.
Have you tried flashing another software? Since the problem started after the OTA update maybe it should be fixed with a ROM flash?
popthosegaskets said:
Hmm... Let me think.
Have you tried flashing another software? Since the problem started after the OTA update maybe it should be fixed with a ROM flash?
Click to expand...
Click to collapse
Well as I said I've flashed it with Cyanogenmod, I've tried different modems via Odin, checked the hardware (physically replaced LTE antenna/charge port this morning) have even resorted to playing with EFS Professional! I guess I could try to replace the co-axial wire that connects the antenna to the mainboard but realistically, that probably isn't going to fix it.
BTW.. IMEI is valid (matches label) so I don't think thats corrupted or missing but the root\efs folder is empty. Is that normal?
To be honest I'm not really into this phone stuff, I just want my phone to work properly when I need it to & make a few tweaks sometimes. I updated the software as instructed & now the phone doesn't work properly. The only thing I've done wrong, if anything, is refuse to pay for a phone that stopped working after a legitimate update from Samsung. I read somewhere that it's possible that the mainboard can be damaged when upgrading the firmware, that seems crazy to me.
I think I'll just give this up as a bad idea & go get an S5. I don't need the hassle.
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.
Has anyone experienced this yet? Twice this weak while on the web, my phone just froze and rebooted. I took the phone to Samsung less than a hour after it happened.. They ran a test, and it passed.. It also did not save any log for the reboots.. I have had this phone about 7 months now.. Since new overheated twice, rebooted twice. Had the mainboard, and charging port changed.. Never had this issue with any Samsung phone in my life.. Well at the end of April, when I purchase the wife her new phone, this one goes as well.. Not sure what i'm getting, Possibly a Note 20 or S22 Ultra.
for the phone to save logs for the reboot it needs to enable 'secret' settings used by the engineers that troubleshoot and test devices.
normally customers don't have such access or know the pass code to get in there, nor the tool to install and run collections.
For the consumers, the best bet is to submit error report to samsung members app > Get help > error report as soon as the issue occurs.
Could you share the device model number and the software version it's running?
also, do you recall any specific commonality between the reboots? such as you were using a camera or some app at the time when reboots occur. Or... more generally, you were running multiple apps at the same time ,etc. etc.
First time, it was on Facebook. Second I believe just waking the device up. Galaxy A52 5G
{
"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"
}
3 is the charm. Just happen while watching a video. Yup time to dump it
It's happening to a lot of people with this phone. What seemed to work for me was rebooting to recovery and wiping the cache and fixing apps
redspeed said:
It's happening to a lot of people with this phone. What seemed to work for me was rebooting to recovery and wiping the cache and fixing apps
Click to expand...
Click to collapse
I have done that on a regular routine, when apps themselves would give me issues.. I'm not sure if it has anything to do with Android 12.. But this is the first Samsung phone I have had this issue being completely stock.
As a last-ditch attempt, you might want to use the nuclear option and factory reset it.
No reboots in a while. Hopefully this new update fixed it.
Got rid of this phone last week.. Purchased right from Samsung the S22 Ultra 512 GB storage factory unlocked version..
doubledragon5 said:
Got rid of this phone last week.. Purchased right from Samsung the S22 Ultra 512 GB storage factory unlocked version..
Click to expand...
Click to collapse
That's one way to fix it!
How's it compare? A worthy upgrade?
koimr said:
That's one way to fix it!
How's it compare? A worthy upgrade?
Click to expand...
Click to collapse
Excellent upgrade imop... Never had issues with Samsung Flagship phones.. So far this phone lives up to its name.. Expensive, but it is what it is.