I was on 10, September update, no issues.
Just updated to November update, flashed over, and then reflashed patched boot image.
Magisk canary, latest, only a handful of modules for v4a and edgesense.
Kirisakura and Elemental kernels.
After I let screen time out, have to hard reset to get back into phone.
Any ideas?
Sent from my Pixel 3 XL using Tapatalk
MeetFace said:
I was on 10, September update, no issues.
Just updated to November update, flashed over, and then reflashed patched boot image.
Magisk canary, latest, only a handful of modules for v4a and edgesense.
Kirisakura and Elemental kernels.
After I let screen time out, have to hard reset to get back into phone.
Any ideas?
Click to expand...
Click to collapse
Platform-tools v29.0.5?
https://forum.xda-developers.com/pixel-3-xl/themes/magisk-modules-disabler-t3966867
Then
fastboot flash boot -- slot all magisk_patched.img
You have two kernels installed? That may be the problem.
I thought I had used the latest platforms tools (updated before I flashed), but it looks like it had a stepped update.
I'll try flashing again after updating, rom and boot IMG.
Also, my brightness is like 70% of normal
Sent from my Pixel 3 XL using Tapatalk
No dice, black screen again
Sent from my Pixel 3 XL using Tapatalk
MeetFace said:
No dice, black screen again
Click to expand...
Click to collapse
I've been getting this as well. Same setup.
Does it happen when the phone is coming out of sleep?
Sent from my Pixel 3 XL using Tapatalk
MArtyChubbs said:
Does it happen when the phone is coming out of sleep?
Click to expand...
Click to collapse
Yes, I think that's it for me. Most the time that is. Like this morning, after a charge unplugged phone and couldn't wake it.
If you are using dark mode, turn it off. It was suggested as a fix in another thread.
Yep, here you go
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
Sent from my Pixel 3 XL using Tapatalk
darkstar73 said:
If you are using dark mode, turn it off. It was suggested as a fix in another thread.
Click to expand...
Click to collapse
Oh, that is odd. You got a link to that thread?
HamsterHam said:
Oh, that is odd. You got a link to that thread?
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-3-xl/help/issue-updating-to-android-10-t3990949/page2
HamsterHam said:
Oh, that is odd. You got a link to that thread?
Click to expand...
Click to collapse
https://forum.xda-developers.com/pi...ing-to-android-10-t3990949/page2#post80830367
I use dark mode and I was having the same problem which I thought was kernal related but it might not have been.
Sent from my Pixel 3 XL using Tapatalk
Bad news, just froze on me. Really odd though, 12 hes with BSOD and it was happening to me like every 15-20 minutes yesterday.
I wonder if the script missed disabling dark mode. I'm going to run full disabled for a day or two and see what happens.
Sent from my Pixel 3 XL using Tapatalk
Dark mode disabled, was using my phone as a flash light, light still on, screen times out, and I LOST responsiveness immediately (should rules out sleep having anything to do with this... BSOD.
Super irritating. I'll probably downgrade at this point.
Sent from my Pixel 3 XL using Tapatalk
@MeetFace what kernel you on?
Related
for alot of people getting blue screen during first boot and have to battery pull and roll back to 22nd, just warning
my phone still getting blue screen on 26th nightly too
KronicSkillz said:
my phone still getting blue screen on 26th nightly too
Click to expand...
Click to collapse
Are you trying to flash this on Windows or something? Android doesn't have blue screens. Lol.
In all seriousness though, try different kernels. Not all phones are created equal.
rani9990 said:
Are you trying to flash this on Windows or something? Android doesn't have blue screens. Lol.
In all seriousness though, try different kernels. Not all phones are created equal.
Click to expand...
Click to collapse
You didn't try it yourself did you? Well it doesn't even work with the built-in CM Kernel. Even tried a full wipe - to no avail. We'll have to wait for more stable ones. :fingers-crossed:
rani9990 said:
Are you trying to flash this on Windows or something? Android doesn't have blue screens. Lol.
In all seriousness though, try different kernels. Not all phones are created equal.
Click to expand...
Click to collapse
what is with the assumptions, all i did was update run the updater with 26th update and it blue screened after lg logo, so YES IT DOES HAVE BLUE SCREENS... take the idiotic attitude somewhere else when ur the one whos wrong
this is a widespread problem if u knew everything like you act like you do you would have already known that
Geezus, I was kidding. I forgot how unfriendly you guys were....
Sent from my Nexus 7 using Tapatalk 2
rani9990 said:
Geezus, I was kidding. I forgot how unfriendly you guys were....
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
You people..? What do you mean, You people..?
Sent from my LG-P930 using Tapatalk 2
has anyone tried the daily from today yet?
edit -
since no one else is talking i tried flashing 27th nightly and still BSOD upon first boot, confirmed the CM mods are finally aware of the issue, itll probably be fixed for tomorow.
Same problem for 27/05
Sent from my LG-P930 using xda app-developers app
ultimate_neet said:
Same problem for 27/05
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
yes I Still get the same problem
the 28th nightly is currently downloading it should be fixed today but ill post after i have it installed to verify.
the nightlies from today have fixed the BSOD on firstboot. confirmed.
YUP, it's fixed. But i have some problem installing the WIND Kernel, does someone knows something about it?
same here i reflashed to nightly from today to go back to stock kernel until its fixed
So yesterday, I was clumsy and I let my phone drop on my floor in the room. I have the Laza and case and the battery. I quickly picked it up and put my battery inside and put the case inside. I turned it on. I'm running stock. It turned on and displayed the T-Mobile, SGH-T989 and loading bar. It loaded all the way, but didn't go past that screen. So I proceeded to turn off the phone and restart. It worked and booted successfully. then for some reason I wasn't convinced. So I restarted again. After that it hasn't booted past the SGH-T989 screen. I went to TWRP and it was asking me for a password when I never added a password. I think my phone is messed up. My phone is working fine with AOSP, but on stock it messes up. I put back on stock yesterday and it was working fine. However, today on the bus, it restarted by itself and it didn't boot past that dreaded screen. What can I do?
Sent from my epic brain transplant using Tapatalk 4
On stock, I am rooted by the way.
Sent from my epic brain transplant using Tapatalk 4
DJ Scooby Doo said:
On stock, I am rooted by the way.
Sent from my epic brain transplant using Tapatalk 4
Click to expand...
Click to collapse
send it to me to keep
What ROM did you flash after flashing AOSP?
JesusWazBlack said:
send it to me to keep
Click to expand...
Click to collapse
You what mate?
Sent from my epic brain transplant using Tapatalk 4
Koragg618 said:
What ROM did you flash after flashing AOSP?
Click to expand...
Click to collapse
I bop between Stock 4.1.2 and CM 10.1 (Stable 4.2.2). I thoroughly wipe with super wipe before I flash Stock or any ROM regardless.
Sent from my epic brain transplant using Tapatalk 4
Has the 4.4 update fixed random reboots for anyone? I am have not gotten the 4.4 OTA yet, but was hoping it may fix the reboots.
Right now I get a reboot even two days or so, mostly (not always) when the screen is off. I am pretty sure it's a software issue, at least for me.
Sent from my Nexus 7 using Tapatalk 4
cowisland said:
Has the 4.4 update fixed random reboots for anyone? I am have not gotten the 4.4 OTA yet, but was hoping it may fix the reboots.
Right now I get a reboot even two days or so, mostly (not always) when the screen is off. I am pretty sure it's a software issue, at least for me.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I still get them with 4.4.
Thanks, there goes my hope...
Sent from my HTC6435LVW using Tapatalk
cowisland said:
Thanks, there goes my hope...
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
I had this issue... maybe 2 or 3 time / week
after upgrading to 4.4.... it happened, but only once in the last 2 weeks...
So i'm not sure if there is an improvement or not
Just got the OTA. Will report back in a couple of days.
After the second JB OTA I had no reboots, so I know it's possible! Overvolt baby overvolt...
Sent from my HTC6435LVW using Tapatalk
Reboots
I've had no reboots for a couple of weeks, when I don't install any unknown apps. As soon as I install a few unknown apps, I start getting 1-4 reboots per day. I've already tried flashing a fresh factory image and a ton of other things. I'm fairly certain that anyone with reboot problems should create bug reports and flood google with every single bug report until they fix it. In another six months, they'll probably say that they no longer officially support the device or something equally messed up.
support dot google dot com /nexus/contact/bugreport
I have my n7 for about a week and had no single reboot yet.
Running on 4.4 (ART).
Sent from my Nexus 7 using Tapatalk 4
My 16GB flo was working fine from the beginning. Always kept it up to date with android releases. Never had an issue. Just today while swyping noticed some weird behavior.So, I tested with a multi touch tester. There were some fake touches recorded. It didn't even allow me to reboot. Later with some effort I managed though. After reboot, it works fine. I'm scared cause I bought that in US and I doubt the so called international warranty will be honored in India.Has this occurred to anyone else? What shall I do if it happens again? Is there some fix for this?
littleromeo said:
My 16GB flo was working fine from the beginning. Always kept it up to date with android releases. Never had an issue. Just today while swyping noticed some weird behavior.So, I tested with a multi touch tester. There were some fake touches recorded. It didn't even allow me to reboot. Later with some effort I managed though. After reboot, it works fine. I'm scared cause I bought that in US and I doubt the so called international warranty will be honored in India.Has this occurred to anyone else? What shall I do if it happens again? Is there some fix for this?
Click to expand...
Click to collapse
I had the same experience the other day. Currently running
Latest version of Clean Rom with ElementalX kernel. After I was finally able to reboot, all was well.
Sent from my Nexus 7 using Tapatalk
dantegl36 said:
I had the same experience the other day. Currently running
Latest version of Clean Rom with ElementalX kernel. After I was finally able to reboot, all was well.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm running stock+xposed.
Testing with multi touch app seemed to have made it worse for me, even prevented me shutting it down. Hope it doesn't come back.
littleromeo said:
My 16GB flo was working fine from the beginning. Always kept it up to date with android releases. Never had an issue. Just today while swyping noticed some weird behavior.So, I tested with a multi touch tester. There were some fake touches recorded. It didn't even allow me to reboot. Later with some effort I managed though. After reboot, it works fine. I'm scared cause I bought that in US and I doubt the so called international warranty will be honored in India.Has this occurred to anyone else? What shall I do if it happens again? Is there some fix for this?
Click to expand...
Click to collapse
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app
Abel669 said:
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If an RMA is not an option, try Abel's solution. It boils down to bad hardware and no quality control. I had to RMA my first one for the exact same reason. Second one is fine.
If you do some googling, you will see that thousands of people have had this problem. Any definitive word from Google or Asus? You wish. They will never admit they made a mistake.
littleromeo said:
I'm running stock+xposed.
Testing with multi touch app seemed to have made it worse for me, even prevented me shutting it down. Hope it doesn't come back.
Click to expand...
Click to collapse
Abel669 said:
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, will do if it starts again.
Abel669 said:
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Aerowinder said:
If an RMA is not an option, try Abel's solution. It boils down to bad hardware and no quality control. I had to RMA my first one for the exact same reason. Second one is fine.
If you do some googling, you will see that thousands of people have had this problem. Any definitive word from Google or Asus? You wish. They will never admit they made a mistake.
Click to expand...
Click to collapse
Yes I read about them but this is weird cause a reboot solved the problem.
Had this issue start yesterday. Running Sinless 3.2.2 on stock kernel. I've noticed it only start since installing Xposed but that could be coincidence. Reboot fixed it but woke up to it again today...
Sent from my Nexus 7 using xda app-developers app
mister2quick said:
Had this issue start yesterday. Running Sinless 3.2.2 on stock kernel. I've noticed it only start since installing Xposed but that could be coincidence. Reboot fixed it but woke up to it again today...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The one I had (before I sent it back to Google), would only do it after it had been started for a while. Reboot would make it go away for a while, but it always came back.
Not related to Xposed.
I just got an update from AT&T but I do not see anything posted on the support page. Any idea what it included.
Security patch = November 1, 2016
Build number = MMB29K.N920AUCS4CPK1
Possibly getting ready for Nugat 7.1.1.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
poa2k8 said:
Possibly getting ready for Nugat 7.1.1.
Click to expand...
Click to collapse
Doubtful. Looks like another monthly security update.
I didn't notice any changes to mine..
Updated mine and now it's having issues charging. Plug it in and charging keeps cycling on the phone. Keeps popping up stating it's charging over and over again. Tried three different chargers, one fast, one at 2.1a and the other 1.5a. Haven't tried wirelessly but this is a great concern.
Can't see anything different at all.
@Zeab I've had that problem as well. Turned out to be a dirty charging port from a dirty plug. Try a little iso and a microfiber rag to clean it out before you panic.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Jspex said:
Can't see anything different at all.
@Zeab I've had that problem as well. Turned out to be a dirty charging port from a dirty plug. Try a little iso and a microfiber rag to clean it out before you panic.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the suggestion. I was able to resolve the issue. Turns out I had a bad cable AND a bad charger. Just happened that the combinations I was trying always provided bad results. Always charge wirelessly except for upgrades and it bit me this time. Lesson learned.
mudbeast66 said:
I just got an update from AT&T but I do not see anything posted on the support page. Any idea what it included.
Security patch = November 1, 2016
Build number = MMB29K.N920AUCS4CPK1
Click to expand...
Click to collapse
What are the changes?
Kundinga said:
What are the changes?
Click to expand...
Click to collapse
AT&T updated there support page. It says it was only the Android November security update. Nothing more.
Sent from my SAMSUNG-SM-N920A using Tapatalk
SS-N920AUCS3CPJ1-to-S4CPK1
Just uploaded the latest OTA from AT&T, sharing for those of us outside the states to update SS-N920AUCS3CPJ1-to-S4CPK1
UPDATE
:good:
D.O.C said:
Just uploaded the latest OTA from AT&T, sharing for those of us outside the states to update SS-N920AUCS3CPJ1-to-S4CPK1
UPDATE
:good:
Click to expand...
Click to collapse
how do you actually use the files?
adb sideload through recovery, its pretty straight forward
D.O.C said:
adb sideload through recovery, its pretty straight forward
Click to expand...
Click to collapse
Will it erase all data ?
Sent from my SAMSUNG-SM-N920A using Tapatalk
anyone know where I can get N920AUCS3CPJ1 ?
SteveLV702 said:
anyone know where I can get N920AUCS3CPJ1 ?
Click to expand...
Click to collapse
Why do you need old firmware ? you can get newer one here : https://forum.xda-developers.com/att-galaxy-note5/general/n920a-odin-firmware-n920aucs4cqb2-t3581129