As the title says, my G2 had a yellow tint on the screen yesterday after tinkering with it. I flashed from stock 4.4.2 to CM12, found out about the GPS issue (not locking in location) so I did the old trick. I flashed back to stock, turned on GPS till it found my location, then booted into recovery and flashed the CM12 backup I had made (dirty flash) Once booted back in CM12, I made sure GPS was working properly, but when i went to the Google Maps app, immediately the whole screen switched to a yellow tone. I freaked out and Googled it, thinking I had messed up with the hardware somehow (never did that before) I rebooted and the screen was back to normal, then I realized it only turns yellow when I go to the Maps app. Otherwise it does not happen. Anyone else has the same problem?
Related
TL;DR: I have flashed the stock 4.2.1 image through fastboot, and yet my n7 wifi still reboots continuously at the google screen with the little unlocked lock.
Background: I have had the device for about 3 months, no real problems with it before this. I was reading yesterday night and i fell asleep, and thus instead of being on my desk all night the device was under a blanket. When i woke up, I opened the cover and found it on the google screen with the lock. It was warm, but not incredibly so. I thought it was weird that it had rebooted and apparently frozen, but i held down the power to turn it off. when i turned it back on, it started the google screen, then went black, then started the google screen again. Seems like there may be some sort of a kernel issue that is keeping it from booting. The next thing i did was to go into recovery (had CWM at this point, and it was rooted as well but that's a moot point if i can't get into the system.) and i did a backup, then wiped data and did a restore from the backup that i had just made. after rebooting, it made it all the way into the system, and seemed ok. I set it down, and a few moments later it turned off and started doing the loopy google screen thing again. Next, I went into recovery and wiped data/factory reset, and tried to boot up. no luck, still looping. Next, i grabbed the 4.0 toolkit from the dev section and tried to flash the stock recovery from that, but it was proving troublesome so i just downloaded the image myself and fastbooted then replaced cwm with the stock recovery, wiped everything, and flashed the 4.2.1 image. that should have worked, from what i understand, but no, still being loopy. I re-wiped and flashed, tried 4.1.2 instead, that didn't work, and i re-did 4.2.1. after flashing 4.2.1 and then leaving it boot looping for a little while, i noticed that it sometimes made it into the boot animation and then the animation froze and it rebooted and looped more. after a few more tries, powering it off, leaving it for a few min, and powering it on again, it booted all the way to the welcome screen to pick a language and then froze. some number of loops later, it made it all the way to picking a wifi network and froze. I have yet to make it past that point. Thinking it may help, i fastbooted CWM onto the device, so i have a more capable recovery now. I am now going to look into pushing a non stock rom to the device to see if that will help at all.
Any ideas on what on earth could have caused this? Was it just that the device was a little warmer than usual for a while?
Any ideas on how i can fix this? Much appreciated!
Lastly, should i consider looking at sending it back to google? I didn't think there was anything wrong with the hardware, but i'm not sure.
Thanks!
Update: After leaving the system repeating it's loopy boot thing for about 45 min, it seems to have finally booted into the system, and has yet to reboot again. I have no idea why this happened in the first case, nor why this finally worked in the end, but so far it seems ok.
More: Ok, so it still seems to be looping a lot. I have no idea why still. I'm having trouble getting it to boot back into the system, so hopefully something helps fix this.
Ok, so a day later it seems to have settled down such that there's very little looping on the google logo screen any more; now it just tends to randomly reboot when in use. this is quite frustrating, but seems more similar to what others have reported to be the case with 4.2.1. oddly, i never had these reboot issues before it decided to fail the first time, so i'm not sure if this is just because ii'm on 4.2.1. I may look at flashing back to 4.1.2 and staying there, i suppose it can't hurt. does anyone else have any ideas as to what could be going on?
I was having trouble getting a rom to flash. Finally after some struggle I got PA KK to work after flashing in this order.
G2Pannel Swap (for white lines i was getting earlier)
KK radio
PA
Gapps.
Everything was working great. I had to reboot, and the white lines came back. I reflashed everything in the same order as before, but I am still getting the same white lines, and it is not booting. It is just sitting at the LG logo.
Hi.
There are lots of issues about the note 4 not charging properly while switched on. I seem to have the opposite problem. I recently updated to Cpc1 firmware, and twrp 3. It works really well. Boots to download, recovery etc fine.
But if I plug the power lead in while it's off. The battery symbol appears but does not animate. The phone locks. And the only way to get it back to life is pull the battery.
This is hardly a big problem, and I'll live with it if nobody has a fix. But has anyone come across this before?
Thanks
Broomfundel said:
Hi.
There are lots of issues about the note 4 not charging properly while switched on. I seem to have the opposite problem. I recently updated to Cpc1 firmware, and twrp 3. It works really well. Boots to download, recovery etc fine.
But if I plug the power lead in while it's off. The battery symbol appears but does not animate. The phone locks. And the only way to get it back to life is pull the battery.
This is hardly a big problem, and I'll live with it if nobody has a fix. But has anyone come across this before?
Thanks
Click to expand...
Click to collapse
It seems to have started after COL3, it was occurring to users who were using my stock de-bloated ROM. I initially thought it had something to do with SuperSU.
If you could try to flash the stock firmware and not install a custom recovery or SuperSU and see if the issue still occurs?
OK. Phones originally a BTU so I pulled down N910FXXS1CPC1_N910FBTU1COI1_N910FXXS1COK1_HOME.tar.md5 as the latest BTU available. Charges normally while off. Manually rooted with auto root, re flash TWRP 3 and xposed. All is fine
So went back and looked at the version I had downloaded before. It was your partially de-bloated Stock-CPC1-signed.zip. Not sure what in the debloat causes it. Maybe Ill debloat by hand and see if I can work it out. If I get the problem back Ill let you know.
Hey All,
Having an odd issues with Nougat and my proximity sensor. Was curious is anyone else has experienced this.
So, it seems like when I run Nougat ROMs my proximity sensor doesn't work. When I get a call and place the phone up to my ear, the screen turns off. However, when I pull the phone away from my head the screen doesn't turn back on. Even when I hit the power button the screen still stays blank and does so until after the call is ended (by the other person).
So I did some flashing of different things and this is what I found...
I flashed a couple Nougat ROMs (DigitalHigh and WETA, I think) and had the same blank screen issue. I then tried flashing the stock Nougat image (NBD90X) from Google and that also had the same issue. From there, I flashed back to Google's stock Marshmallow image (MTC20L) and the issue went away. I then upgraded to Nougat from stock MTC20L and I didn't have the issue. Everything worked fine after that upgrade.
Anyone have any ideas as to why the upgrade worked fine but the stock Nougat images and other Nougat ROMs don't?
Also, for the record, I don't have a screen protector on the phone.
TheRectified said:
Hey All,
Having an odd issues with Nougat and my proximity sensor. Was curious is anyone else has experienced this.
So, it seems like when I run Nougat ROMs my proximity sensor doesn't work. When I get a call and place the phone up to my ear, the screen turns off. However, when I pull the phone away from my head the screen doesn't turn back on. Even when I hit the power button the screen still stays blank and does so until after the call is ended (by the other person).
So I did some flashing of different things and this is what I found...
I flashed a couple Nougat ROMs (DigitalHigh and WETA, I think) and had the same blank screen issue. I then tried flashing the stock Nougat image (NBD90X) from Google and that also had the same issue. From there, I flashed back to Google's stock Marshmallow image (MTC20L) and the issue went away. I then upgraded to Nougat from stock MTC20L and I didn't have the issue. Everything worked fine after that upgrade.
Anyone have any ideas as to why the upgrade worked fine but the stock Nougat images and other Nougat ROMs don't?
Also, for the record, I don't have a screen protector on the phone.
Click to expand...
Click to collapse
It is peculiar. I have flashed about every factory image clean when they come out and my proximity has always worked. There was an issue where certain devices had locked up sensors about a year ago but that was on MM and I think it was just a hardware problem. Maybe it's early symptoms of that specific problem.
TheRectified said:
Hey All,
Having an odd issues with Nougat and my proximity sensor. Was curious is anyone else has experienced this.
So, it seems like when I run Nougat ROMs my proximity sensor doesn't work. When I get a call and place the phone up to my ear, the screen turns off. However, when I pull the phone away from my head the screen doesn't turn back on. Even when I hit the power button the screen still stays blank and does so until after the call is ended (by the other person).
So I did some flashing of different things and this is what I found...
I flashed a couple Nougat ROMs (DigitalHigh and WETA, I think) and had the same blank screen issue. I then tried flashing the stock Nougat image (NBD90X) from Google and that also had the same issue. From there, I flashed back to Google's stock Marshmallow image (MTC20L) and the issue went away. I then upgraded to Nougat from stock MTC20L and I didn't have the issue. Everything worked fine after that upgrade.
Anyone have any ideas as to why the upgrade worked fine but the stock Nougat images and other Nougat ROMs don't?
Also, for the record, I don't have a screen protector on the phone.
Click to expand...
Click to collapse
I am having this same exact issue ever since I got Nougat. I am not rooted and am running the OTA upgrade. I've been hesitant to reset to factory settings but I may try that later tonight.
abenco said:
I am having this same exact issue ever since I got Nougat. I am not rooted and am running the OTA upgrade. I've been hesitant to reset to factory settings but I may try that later tonight.
Click to expand...
Click to collapse
Oddly enough, the OTA update is the only thing that worked on mine.
Gizmoe said:
It is peculiar. I have flashed about every factory image clean when they come out and my proximity has always worked. There was an issue where certain devices had locked up sensors about a year ago but that was on MM and I think it was just a hardware problem. Maybe it's early symptoms of that specific problem.
Click to expand...
Click to collapse
It really is weird. I'm back on MM now and its working fine. I guess I stay here until the next build comes up and then I'll see what happens.
Same issue here. stock rom, received OTA and now I have the excess battery use, and thanks to the post boss above, the same proximity sensor issue. Phone goes black in middle of call with no way to get back to the screen to hang up, change to speakerphone, etc. It stays black sometimes, even after the other party hangs up, requiring me to reboot. PITA.
Resetting the phone did nothing to fix the problem. The only way to revert back to MM is to root the phone first, correct?
abenco said:
Resetting the phone did nothing to fix the problem. The only way to revert back to MM is to root the phone first, correct?
Click to expand...
Click to collapse
You have to unlock the bootloader but thats pretty much it. After you flash you can relock it if you want.
I could fix that problem by removing the screen protector.
abenco said:
Resetting the phone did nothing to fix the problem. The only way to revert back to MM is to root the phone first, correct?
Click to expand...
Click to collapse
No not rooting. You have to unlock the bootloader and then fastboot flash a factory image. It's best to leave the bootloader unlocked too, unless you are going to leave it stock and never tinker with it again. But if you ever need to flash an image again or use twrp or anything fastboot related you will need an unlocked bootloader.
I have the same problem with my phone. Android 7.1 seems to fix this.
Enviado de meu Nexus 6P usando Tapatalk
I had the same problem, but fixed it by installing a sensor reset app from Play Store, then uninstalled the app.
Just talked to Huawei tech support. My 6P wasn't rotating the screen and whenever I was in a call, wouldn't dim the screen. Such a small feature but we all take it for granted. Anyway, she told me to enter recovery (Power+Volume Up) and "Wipe Cache Partition" rebooted and running like a champ. ?
I originally posted what's written below over in reddit but then the next day it rebooted randomly one time. It was then that I realised that the camera had begun causing reboots.
It started bootlooping before I tried to boot into recovery. It then got stuck on "installing new software" and got pretty hot before going blank with the blue light on.
S7 Edge Nougat Exynos unrooted
Not sure if relevant or not but I recently installed the Bixby apk that was on here and it screwed up the standard launcher. I set it Nova and it seemed to be working. I'd also recently removed greenify.
Edit - Fixed.... I let the battery run flat, rebooted into recovery and did factory reset. All good now.
Exynos unrooted Nougat
If anyone has ideas, I'd be very appreciative.