Hi everyone,
Just got a brand new Nexus 6P yesterday, camera was working fine. Woke up this morning and the camera produces a black screen. Cleared camera data, cache, updated, tried third party apps, then performed a factory reset. All to no avail.
I'm assuming this has something to do with some **** in the kernel that google wrote?
It is still locked I haven't unlocked the bootloader or even rooted the device yet... literally got it yesterday.
I guess there's not much else I can do, is there? Just wondering if anyone's experienced the same problem, and what they did to solve it. I read a post where someone simply flashed the stock boot.img, not even a custom kernel, and it fixed the problem. Any verification?
Cheers
Magnetox said:
Hi everyone,
Just got a brand new Nexus 6P yesterday, camera was working fine. Woke up this morning and the camera produces a black screen. Cleared camera data, cache, updated, tried third party apps, then performed a factory reset. All to no avail.
I'm assuming this has something to do with some **** in the kernel that google wrote?
It is still locked I haven't unlocked the bootloader or even rooted the device yet... literally got it yesterday.
I guess there's not much else I can do, is there? Just wondering if anyone's experienced the same problem, and what they did to solve it. I read a post where someone simply flashed the stock boot.img, not even a custom kernel, and it fixed the problem. Any verification?
Cheers
Click to expand...
Click to collapse
Just send it back for a new one. You just got it. It's most likely a bad unit. It happens.
Related
When I try to start the stock camera app it just hangs won't start. I've rebooted and still no luck. Is this a known issue?
I guess this isn't a popular issue. One I myself have though.
I RMA'd the phone and got a replacement. Except the replacement had a dead pixel, and now the replacement I have has a large dent near the fingerprint reader. Maybe the 4th time is a charm.
Same issue here running stock 6.0.1. It was working fine then suddenly just stopped. I've tried starting in safe mode and factory reset, and nothing. Any clever suggestions to fix this or I guess I'll ring to ask for a replacement tomorrow?
timtime said:
Same issue here running stock 6.0.1. It was working fine then suddenly just stopped. I've tried starting in safe mode and factory reset, and nothing. Any clever suggestions to fix this or I guess I'll ring to ask for a replacement tomorrow?
Click to expand...
Click to collapse
Could try manually Flashing the vendor.img from stock 6.0.1 image. I've read that fixes camera issues for some.
XxMORPHEOUSxX said:
Could try manually Flashing the vendor.img from stock 6.0.1 image. I've read that fixes camera issues for some.
Click to expand...
Click to collapse
Yeah I had the same issue where the camera just wouldn't open. flashing Vendor.img did the trick
Hello there xda.
I have a Samsung Galaxy Note 4 SM910F.
So what is happening to my phone is that whenever I am in any random app lets say reddit or even chrome for example. It will like freeze for a minute or two and then unfreeze.
In more extreme cases it will reboot.
So this happened randomly because I flashed a Stock unbloated 5.1.1 ROM from here back in december and everything was working smoothly and stuff. I had xposed installed and all my apps. Then in February it started with this random freeze/reboot. I had not installed anything else apart from what I had for the last 3 months.
So I restarted the phone, changed the battery and stuff to see whether that will fix it. However it didn't. So I formatted the phone (the soft type) just so I can install another ROM. So I tried another ROM, flashed the correct CP and BL and stuff and then just installed chrome and whatsapp. After an hour or two the same thing happened. So this time I factory reset he phone, like a complete wipe and I installed the unbloated ROM once again with few apps. Same thing happened...
So my last resort was to install Cyonagen Mod. After an hour or two same thing happened...
I don't know what is the problem. I read about some peoples phones emmc failing and thus the freezing, but I am not sure yet.
Please could you guys explain what I should do to fix this?
Thank in advance!
I have the same problem. Starting on mid january. I'm on stock 5.1.1 with root and twrp recovery
Tried backup and factory reset
I went back to stock after I factory reset the phone. And still had the same problems.
People say that its a hardware problem... So I guess I'll have to send it back to Samsung soon.
I think I tripped the knox. I just have to unroot and get it back once again to stock and send it back. I hope that they accept it.
i have the same problem. my model is SM-N910W8 and I bought it from 2nd hand, so no receipt and no prove of purchase.
can I still send it back to samsung to fix it?
same problem as you and now my phone died completely .
my phone was 4 months and he has not supported any longer he died naturally lol.
my operator gave me another free under warranty because the phone had a faulty motherboard and after several back galaxy note 4
This started happening to me a week or so ago and my phone just got stuck in a boot loop after it froze and rebooted. I'm on the latest stock firmware. Tried factory reset, reflashed stock firmware, nothing helps. It still reboots (sometimes it almost gets booted completely, other times it reboots after 2 seconds.
Just disable finger print. Yes that magic feature offered by Samsung is causing more hungry that happiness since S5
EclipseX said:
Just disable finger print. Yes that magic feature offered by Samsung is causing more hungry that happiness since S5
Click to expand...
Click to collapse
Many thanks. This was driving me mad for a few days, I had tried three different ROMS, completely wiping everything. I eventually went back to stock, which I'm still running and it was the same; it would run fine for a few hours and then start to lock up until eventually it would either reboot or stop responding and I'd have to pull the battery to restart it.
Just not selecting fingerprint security doesn't work, you have to force stop "Fingerprints" in Application Manager (All).
just do not setup the finger print lol. I was having those problemes too when I bought the note 4 until someone tell "do not setup the finger print" lol, not I'm a happy user.... I hope that android 6.0.1 solve the probleme
HXOY said:
Many thanks. This was driving me mad for a few days, I had tried three different ROMS, completely wiping everything. I eventually went back to stock, which I'm still running and it was the same; it would run fine for a few hours and then start to lock up until eventually it would either reboot or stop responding and I'd have to pull the battery to restart it.
Just not selecting fingerprint security doesn't work, you have to force stop "Fingerprints" in Application Manager (All).
Click to expand...
Click to collapse
EclipseX said:
just do not setup the finger print lol. I was having those problemes too when I bought the note 4 until someone tell "do not setup the finger print" lol, not I'm a happy user.... I hope that android 6.0.1 solve the probleme
Click to expand...
Click to collapse
Spoke too soon, it's started rebooting itself again.
Same problems here since 2 days. I was on original 5.1.1 software... Very strange all those people with the same problems
did the problem was resolved ? started to have the same problem 3 days ago ! was on 6- flashed stock with full wipe..nothing ! downgraded to 5.1 with full wipe via odin...again nothing !
WTF [email protected]!
Davids said:
did the problem was resolved ? started to have the same problem 3 days ago ! was on 6- flashed stock with full wipe..nothing ! downgraded to 5.1 with full wipe via odin...again nothing !
WTF [email protected]!
Click to expand...
Click to collapse
Still having the same issue around the same time everyone else started experiencing it.
I also was rooted and had xposed installed on 4.4.4 before the issue started happening.
Try the solution provided here & report back..
http://forum.xda-developers.com/note-4/help/note-4-sm-n910f-freeze-restart-issue-t3439111
Hi guys,
So I had been using my Moto X Pure (3 months approx) and it had been perfectly fine. Except just a couple of days ago while I was on snapchat the phone suddenly shut down. While I tried to restart the phone it got stuck on the boot screen and didn't go past that. I initially tried to wipe cache partition & factory reset but nothing happened, it was still getting stuck on the boot screen.
My phone is unrooted and I haven't tried experimenting with the kernel or anything, mind you.
I left it alone for a couple of days and it started to boot up again, it was working perfectly, no issues whatsoever. But just yesterday the same situation occurred yet again :/ not while I was using snapchat but I unlocked the phone but the screen didn't turn on and it restarted by itself and got stuck onto boot screen again.
Is this an issue with the software or the hardware?
I talked to Motorola and they said they will issue a replacement phone, but I live overseas so it could be a hassle. Should I just send it in for replacement or try and reinstall the rom using factory image?
Thanks guys, really appreciate your help
could try reinstalling the factory image but if you havent messed with anything on the phone maybe its a hardware issue... i dont know
If the bootloader is still locked, i would definitely go through the replacement hassle. Should have no issues whatever after only 3 months and 100% stock.
DejektedZ76 said:
Hi guys,
So I had been using my Moto X Pure (3 months approx) and it had been perfectly fine. Except just a couple of days ago while I was on snapchat the phone suddenly shut down. While I tried to restart the phone it got stuck on the boot screen and didn't go past that. I initially tried to wipe cache partition & factory reset but nothing happened, it was still getting stuck on the boot screen.
My phone is unrooted and I haven't tried experimenting with the kernel or anything, mind you.
I left it alone for a couple of days and it started to boot up again, it was working perfectly, no issues whatsoever. But just yesterday the same situation occurred yet again :/ not while I was using snapchat but I unlocked the phone but the screen didn't turn on and it restarted by itself and got stuck onto boot screen again.
Is this an issue with the software or the hardware?
I talked to Motorola and they said they will issue a replacement phone, but I live overseas so it could be a hassle. Should I just send it in for replacement or try and reinstall the rom using factory image?
Thanks guys, really appreciate your help
Click to expand...
Click to collapse
Have you tried a simple factory reset? Basically a data wipe?
Sent from my One using XDA-Developers mobile app
bmeek said:
Have you tried a simple factory reset? Basically a data wipe?
Sent from my One using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, tried a factory wipe and cleared cache but didn't seem to work.
DejektedZ76 said:
Yes, tried a factory wipe and cleared cache but didn't seem to work.
Click to expand...
Click to collapse
Yeah - I haven't heard of stock unrooted phones getting their system image corrupted such that a reset doesn't get back to proper "stock". Maybe a botched OTA, but if you've got that warranty option, probably be wise to take it.
I don't know this phone and Motorola well enough to say that unlocking your bootloader and starting from scratch, as I would be sorely tempted to do in your situation, won't void your warranty option.
Sent from my One using Tapatalk
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. ?
Hi guys. Over the weekend, I was running Android O beta, just to give it a spin and see how it was. Everything was working ok, but then I missed the good features of AOSP, so I decided to come back to it. So on Sunday night, I flashed back the previous rom, including the vendor, bootloader and radio as requested on the OP. But the problem was that the screen rotation wasn't working, no matter what I tried. I even tried other roms, to see if the problem was from the rom, but no, the problem persisted. I flashed stock again, and the problem was also there. I gave Google a call and they sent me some steps to go through and none of them solved my problem as well. So, I decided to flash back the O Beta, and voila, the problem was gone. My question, have I done anything wrong, any step that I may have missed? Or is it the drivers? Any help/suggestion is highly appreciatted
Did you factory reset or wiped data? It's sometimes necessary when downgrading.
I did yes. It was the first thing I did as soon as I got TWRP installed on it,because it was asking for the encryption key, to which it never what it was(tried my password and my lock screen code,but none of them worked,so just ended up wiping the whole data)