Related
Hello everyone,
Pretty new here, 1st post
I recently updated my N4 to 4.3 (flashed the stock image from google). I'm rooted with CF's autoroot (and have an unlocked bootloader), but the rest is stock....
I seem to have an issue: when I unlock the screen, the screen turns black and then turns on again (in less-than-a-second maybe...), so there's a screen flicker, just one time when I unlock the screen... I thought the problem was N4 Display Contol app, but the issue remains after I removed it...
4.2.2. didn't do this as far as I remember....
Anyone else have this problem? (I'm set to auto-brightness btw..)
I am having the exact same issue after I updated last night.
HowlinMadMurdoc said:
I am having the exact same issue after I updated last night.
Click to expand...
Click to collapse
Well.... I went into (stock) recovery and wiped cache. Then I manually deleted my dalvik cache with Tcmd...
..aaand (after reboot) the issue seems to be gone. It unlocks without flickering :good:
Please try this (if you are rooted) and write back if it helped.
dSERiES said:
Well.... I went into (stock) recovery and wiped cache. Then I manually deleted my dalvik cache with Tcmd...
..aaand (after reboot) the issue seems to be gone. It unlocks without flickering :good:
Please try this (if you are rooted) and write back if it helped.
Click to expand...
Click to collapse
you are lucky you can get into recovery! i cant even get there, just says "no command" when i do so.
---------- Post added at 11:29 AM ---------- Previous post was at 11:15 AM ----------
Ok was able to fix the recovery error by using the Nexus 4 Toolkit to install one of the custom recovery tools. now wiping cache and dalvik to see if that fixes it.
---------- Post added at 11:46 AM ---------- Previous post was at 11:29 AM ----------
that didnt work, flashing back to stock recovery brings that error back as well. might have to just wipe everything and start from scratch :/
dSERiES said:
Well.... I went into (stock) recovery and wiped cache. Then I manually deleted my dalvik cache with Tcmd...
..aaand (after reboot) the issue seems to be gone. It unlocks without flickering :good:
Please try this (if you are rooted) and write back if it helped.
Click to expand...
Click to collapse
Unfortunately this works for a little while (even just rebooting when you get flickering), but the problem keeps coming back after a few days of use (without restart)
patsmike said:
Unfortunately this works for a little while (even just rebooting when you get flickering), but the problem keeps coming back after a few days of use (without restart)
Click to expand...
Click to collapse
Reboot didn't help me at all. The issue did come back however. I updated SuperSU and it updated some binaries for me, after it was complete and phone rebooted, the flickering came back. I deleted dalvik-cache again and wiped cache partition through stock recovery and it's gone again....
You aren't talking about the CRT on off animation like TV set old school are you??? Lol if not its common for many flickers on these devices. I get them off and on. Usually in the ROM hw overlays. Sometimes in settings you can revert by clicking or get to stop. Just hoping its CRT as those unfamiliar have asked bfore
Sent from my Nexus 4 using xda premium
Droid2drummer said:
You aren't talking about the CRT on off animation like TV set old school are you??? Lol if not its common for many flickers on these devices. I get them off and on. Usually in the ROM hw overlays. Sometimes in settings you can revert by clicking or get to stop. Just hoping its CRT as those unfamiliar have asked bfore
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
"screen UNLOCK flicker"
CRT off animation? :laugh::laugh::laugh::laugh:
seriously no, we are talking about the flickering when you Un-lock your device
Same problem here. But mine does not go to the black screen. Just straight cut off the animation. From lockscreen to homesreen without any animation. Restart is a temporary fix. Any suggestions?
I have a tab pro 10.1 WiFi. It is only six months old and is rooted with stock 4.4.2 it began to reboot randomly so I reset to factory and it still does it. I tried wiping cache and dalvik with no luck. Anyone else have this issue? thanks in advance
p.s. I do have a 64GB Samsung SD card in it that I noticed every so often I get a message about formatting and have done so.
kamelda said:
I have a tab pro 10.1 WiFi. It is only six months old and is rooted with stock 4.4.2 it began to reboot randomly so I reset to factory and it still does it. I tried wiping cache and dalvik with no luck. Anyone else have this issue? thanks in advance
p.s. I do have a 64GB Samsung SD card in it that I noticed every so often I get a message about formatting and have done so.
Click to expand...
Click to collapse
Hmm. Do you have anything loaded on the card? What brand is it? Have you tried just using the tablet without the card in it?
---------- Post added at 07:25 PM ---------- Previous post was at 07:20 PM ----------
kamelda said:
I have a tab pro 10.1 WiFi. It is only six months old and is rooted with stock 4.4.2 it began to reboot randomly so I reset to factory and it still does it. I tried wiping cache and dalvik with no luck. Anyone else have this issue? thanks in advance
p.s. I do have a 64GB Samsung SD card in it that I noticed every so often I get a message about formatting and have done so.
Click to expand...
Click to collapse
Also look at what processes are running too and list them here.
Korgy said:
Hmm. Do you have anything loaded on the card? What brand is it? Have you tried just using the tablet without the card in it?
---------- Post added at 07:25 PM ---------- Previous post was at 07:20 PM ----------
Also look at what processes are running too and list them here.
Click to expand...
Click to collapse
I believe I found what I did wrong, flashed wrong ROM.Just realized that mine ended in XAR and I had used the Canada(XAC) one when I originally flashed it after rooting. Trying the XAR(Cellular South)
BTW the card is Samsung and is the same one used in my S4.
Awesome.
Well, the XAR 4.4.2 Flash didn't work. So now I am trying unfreezing the few apps that I froze in Titanium. The Samsung(entertaiment) apps and Knox.:crying:
Have you done these things? It looks like some people's problem is caused by a combination of freezing certain apps (Knox) and allowing SU to disable Knox notifications. http://forum.xda-developers.com/showthread.php?p=55004876
Hello all! This is the second time this has happened to me, I've rooted my phone for about a week, and then for some reason when I decide to restart my phone -- it no longer boots up. It is stuck at the t-mobile screen and vibrates for a bit then stops, I have booted in to recovery mode and tried wiping that cache, but to no avail.
Any help would be appreciated -- or even how I can backup my data would be great too.
Wah gwan! My T-Mobile S7 Edge running TekHD v2. To have your phone running very nicely, you need to download the APD8 fireware. Make sure everything on your phone running APD8. download the files from max on highonandroid, flash the tar file twice using modified Odin from max. Once boot up screen say custom, next step download and extract TekHD.rar file .there's a part in the file that operates like cmd, right click and let it do its thing. Make sure your phone is on and a low USB debugging.
---------- Post added at 10:09 PM ---------- Previous post was at 09:43 PM ----------
Also this TekHD Rom is best for unlimited hotspot for Windows, Android and Mac. I have download about 20 more GB of files to make sure its good. The tutorial from max is good, the easiest way I see so far is to click on the root.dat in max files to add superSU. For TekHD click tekhd.bat. That was the easiest way after flashing the tar file. The hold process take 2 minutes once done right. I'm not a developer but a big Samsung Android fan. I have a Note 3,4,5 S6 Edge+ and S7Edge, I tried and tested many Roms at my own risk. Never had any problems. Make sure you always have the stock rom tar file for your device before any flashing any roms, is case something goes wrong you can start over.
first of all this is an eng boot root, so expect some hiccups and proble.. before u root make sure u back up everything then odin back to stock then root or else u will run into problems
You're going to have to ODIN back to stock. This seems to be happening to a lot of people (myself included) and a stock flash is the only way anyone has been able to recover. Flash all 4 files in ODIN simultaneously, but if you don't have a backup, try flashing the Home_CSC and see if it'll boot. I've heard reports that the Home-CSC file doesn't wipe your phone. If that doesn't work, then unfortunately you're going to have to re-flash, but this time use the standard CSC file, which will wipe your phone. Good luck.
I just had this happen for my second time and was stuck phoneless out of the house :/ I wish we could figure out the cause... Not sure if related, but my recovery has red text on the bottom "dm-verity verification failed"
ph00ky said:
Not sure if related, but my recovery has red text on the bottom "dm-verity verification failed"
Click to expand...
Click to collapse
No, that is not related, dm-verity verification fails because recovery still checks dm-verity even though the kernel does not.
Damn same thing just happened to me at work. Had to do factory reset...
When at that tmobile screen, hold down volume down + home button + power. It will reboot,and as soon as it does, switch volume down to vol up until it loads recovery to reset
This happened to me also. Go to lockscreen and security options and disable automatic security updates.
I think it could be new firmware update from Google. I tried to install TekHD Rom after update to the newest APG1. And it hapened to me also. Stuck on Samsung screen with random weird vibrations.
I can almost certainly say that the vibrate crash has something to do with the phone installing something behind the scenes. After getting the Amazon/Google/Samsung services multiple crash followed by the reset to the vibrating T-mobile screen I did a non-wipe ODIN, which works and works perfectly. What seems to not work though is re-installing root, it just leads back to the same screen, so I think Samsung is pushing something sneaky onto our phones probably through the security thing as mentioned.
---------- Post added at 01:41 PM ---------- Previous post was at 01:40 PM ----------
pawel30w said:
I think it could be new firmware update from Google. I tried to install TekHD Rom after update to the newest APG1. And it hapened to me also. Stuck on Samsung screen with random weird vibrations.
Click to expand...
Click to collapse
TekHD Only works on PD8, it's mentioned in the thread.
pawel30w said:
I think it could be new firmware update from Google. I tried to install TekHD Rom after update to the newest APG1. And it hapened to me also. Stuck on Samsung screen with random weird vibrations.
Click to expand...
Click to collapse
Can't run that ROM on APG1. If you want to try it, you will have to ODIN PD8. There is a post in a thread in this section that shows how.
I just had this same thing happen on PG1. Using ODIN with all of the various parts and Home_CSC got me back in without having to wipe and everything survived. Going to try and re-root with the engineering boot image now that I made a decent backup. Would be great if someone smarter than me figures out what is updating/changing and causing this problem.
I said it on page 1: In settings, go to lockscreen, then security options and disable automatic security updates.
rp3 said:
I said it on page 1: In settings, go to lockscreen, then security options and disable automatic security updates.
Click to expand...
Click to collapse
That might work to prevent this problem -- but what needs to be reverted once this problem starts? I can flash stock PG1 and if I use the (home_csc) it will fix the problem and not wipe my data.... but if I reflash the engineering bootloader it goes back to hanging at the tmobile screen.
im stuck on tmobile screen, and it keeps vibrating, idk what to do
swaggyyd said:
im stuck on tmobile screen, and it keeps vibrating, idk what to do
Click to expand...
Click to collapse
I haven't rooted but if your stuck just Odin back to stock.
I came to post that I'm having these issues as well, this is the second time it's happened to me.
The first time I had TEKHD on my Phone, and so with it constantly nagging to do a system update.
I figured when it did this the first time, it was because the update ran over my TEKHD side load "ROM" and corrupted. Ok , whatever, reloaded.
But now I'm just rooted, and stock ROM otherwise. Just happened to me again
Each time it's happened, I start getting "playstore has crashed" errors - dismiss and it comes right back. So I reboot, and then it boot loops and gets CRAZY hot. Man I've never been able to fry an egg on a phone quite like my S7 Edge...
Is there any light shed on what could be doing this? I may have to remain stock which makes me want to :crying: but I can't keep bothering my Work Admin's to unlock my Token account so I can re-register my same phone -
I shall try that home_CSC Flash when I get home though, hopefully I can recover it at least in a way to transfer token to my tablet or something.
posted that at work, I'm at home now. I tried to flash just the home CSC and that did not work, just booted into recovery with an error and wouldn't resurrect at all.
I shall try that disable auto updates thing though and see if it helps in the long run...
wotan2525 said:
I just had this same thing happen on PG1. Using ODIN with all of the various parts and Home_CSC got me back in without having to wipe and everything survived. Going to try and re-root with the engineering boot image now that I made a decent backup. Would be great if someone smarter than me figures out what is updating/changing and causing this problem.
Click to expand...
Click to collapse
you got a link for the home csc file you can send me I was good for about a month and a half and it finally happened to me as well and can confirm I was getting the play store/ google services errors right before the reboot and tmobile screen
Was having this issue as well, forgot that I needed to turn off Security policy updates.
can i install the new up date over rooted phone if not is there a way were i can turn the message of. doing my head in .cheers
@rael75, no, generally not. But you can install the update if you satisfy following conditions.
1. You have not modified system partition. That is, you didn't make any changes to the system partition, so, haven't installed or deleted any apps on system partition.
2. You haven't loaded system in TWRP recovery, when it asks when booted first time.
3. You have stock recovery installed.
---------- Post added at 03:42 PM ---------- Previous post was at 03:41 PM ----------
@rael75 BTW, what is the software version you see? Can you share a screenshot of the update message?
sorry am a novice dont understand when i installed it it went staight to recovery did know what to do so just used old back up. do you know how to stop update popping up all the time.thanks alot
Just to hook in, i got the same headache as OP. Im on vacation with a limited data plan and rooted XT1622.. have to hit so many times a day to delay it. At one point it popped up while i was looking for something on my phone and it wanted to start. Lucky me, it wont download without Wifi. Yet it stil keeps very agressively reminding me to do it.
No way of disabling the reminders, no way to update now. Gg Moto for annyoing me more then apple ever did me with their updates. If anything, it remains my choice to update and not moto's..
Anyways what would be needed to update??
Restore recovery to original? Go completely stock?
Coldstream said:
Just to hook in, i got the same headache as OP. Im on vacation with a limited data plan and rooted XT1622.. have to hit so many times a day to delay it. At one point it popped up while i was looking for something on my phone and it wanted to start. Lucky me, it wont download without Wifi. Yet it stil keeps very agressively reminding me to do it.
No way of disabling the reminders, no way to update now. Gg Moto for annyoing me more then apple ever did me with their updates. If anything, it remains my choice to update and not moto's..
Anyways what would be needed to update??
Restore recovery to original? Go completely stock?
Click to expand...
Click to collapse
done my head in. waiting for N before i unroot
Same as op. Not rooted but twrp installed. Cannot update by receiving notification for so many times. Actually I'd like to update if I can keep my current status, I mean apps and data. It seems impossible without revert to stock recovery.
I'm running a Galaxy S5 with CM14.1. All was good for many weeks until today, when suddenly the phone started freezing irrecoverably. It occurs about 1 minute after the phone boots. Before that, between starting up and freezing, the phone is a little laggy but works fine.
I've tried a factory reset and also tried reinstalling CM14 but it still occurs.
Nothing was changed on the phone between when it was working fine and when it started freezing consistently.
Anyone have this experience?
[Update] Downgrading to CM13 (or even restoring a backup of a CM13 install) solves the problem. But no amount of reinstalling CM14, or even reverting to a backup of a CM14 install that was entirely functional (no freezing) solves the problem - all installs of CM14 now freeze.
Similar experience from another user....
Literally could have written your post word for word (S5, 14.1, same symptoms) and created an account to tell you so, but it won't let me. Still a n00b in many respects but I've backed my way out of enough soft bricks to not feel totally out of my depth when I say "This is weird, but probably not unique." So, thanks.
Additional info, in case it helps in any way:
- T-Mobile network
- was working fine until about 8:45pm when it died while I was making a call. Plugged it in, turned it on, freeze.
- Recently installed a new SD card because my old one was unreadable, discovered by "too little storage, delete some apps." 128GB Samsung brand (just because I was bitter about it). Promptly made a full backup Jan 20. Tried to restore it but it was giving me a LOT of **** about making the SD internal, and I got so frustrated that I gave in. Result: "Cannot restore modem -- mounted read only." Restoring everything but the modem now.
Moved to Galaxy s5 Q&A
same same
same problem here, all in a sudden 14.1 started freezing. i can factory reset, wipe, dalvik, cache, etc. even went so far to format system and everything, and reinstalled, it boots, and as soon as i should be select language etc. it freezes. no way to do anything. i will go back to a 13/6.0.1 based rom, and see if this works.
Update: i formated everything, system, cache, data, you name it after going back to a 6.0.1 based rom, in my case Resurrection Remix, it worked like a charm, as expected. it offered me an update to 7.1.1 or so, i downloaded it, factory resettet it, installed it, as soon as it booted, it froze, again. so there is, indeed, something with the 7.1.1 roms, which my phone does not like. i feel at a loss, since i never before experienced such a problem, since i started putting custom roms on my first galaxy S, and my S3.
any pointers would be helpful. not sure if i can provide any logs, since it freezes anyway, as soon as the setup-wizard comes up, before i can enter anything.
at least 6.0.1 works, which means, unless i feel like wasting an afternoon again, or some pointers on what goes wrong will come up, i will stay on it, for a month or so at least.
novae_lithic said:
I'm running a Galaxy S5 with CM14.1. All was good for many weeks until today, when suddenly the phone started freezing irrecoverably. It occurs about 1 minute after the phone boots. Before that, between starting up and freezing, the phone is a little laggy but works fine.
I've tried a factory reset and also tried reinstalling CM14 but it still occurs.
Nothing was changed on the phone between when it was working fine and when it started freezing consistently.
Anyone have this experience?
[Update] Downgrading to CM13 (or even restoring a backup of a CM13 install) solves the problem. But no amount of reinstalling CM14, or even reverting to a backup of a CM14 install that was entirely functional (no freezing) solves the problem - all installs of CM14 now freeze.
Click to expand...
Click to collapse
Was there ever a resolution to this. I am having freezing issues with all versions of Nougat on my Verizon S5.
---------- Post added at 09:49 PM ---------- Previous post was at 09:46 PM ----------
novae_lithic said:
I'm running a Galaxy S5 with CM14.1. All was good for many weeks until today, when suddenly the phone started freezing irrecoverably. It occurs about 1 minute after the phone boots. Before that, between starting up and freezing, the phone is a little laggy but works fine.
I've tried a factory reset and also tried reinstalling CM14 but it still occurs.
Nothing was changed on the phone between when it was working fine and when it started freezing consistently.
Anyone have this experience?
[Update] Downgrading to CM13 (or even restoring a backup of a CM13 install) solves the problem. But no amount of reinstalling CM14, or even reverting to a backup of a CM14 install that was entirely functional (no freezing) solves the problem - all installs of CM14 now freeze.
Click to expand...
Click to collapse
tron65 said:
same problem here, all in a sudden 14.1 started freezing. i can factory reset, wipe, dalvik, cache, etc. even went so far to format system and everything, and reinstalled, it boots, and as soon as i should be select language etc. it freezes. no way to do anything. i will go back to a 13/6.0.1 based rom, and see if this works.
Update: i formated everything, system, cache, data, you name it after going back to a 6.0.1 based rom, in my case Resurrection Remix, it worked like a charm, as expected. it offered me an update to 7.1.1 or so, i downloaded it, factory resettet it, installed it, as soon as it booted, it froze, again. so there is, indeed, something with the 7.1.1 roms, which my phone does not like. i feel at a loss, since i never before experienced such a problem, since i started putting custom roms on my first galaxy S, and my S3.
any pointers would be helpful. not sure if i can provide any logs, since it freezes anyway, as soon as the setup-wizard comes up, before i can enter anything.
at least 6.0.1 works, which means, unless i feel like wasting an afternoon again, or some pointers on what goes wrong will come up, i will stay on it, for a month or so at least.
Click to expand...
Click to collapse
Were you "tron65" ever able to use Nougat on your S5 without freezing? Thanks.
martytoo said:
Was there ever a resolution to this. I am having freezing issues with all versions of Nougat on my Verizon S5.
---------- Post added at 09:49 PM ---------- Previous post was at 09:46 PM ----------
Were you "tron65" ever able to use Nougat on your S5 without freezing? Thanks.
Click to expand...
Click to collapse
i am now again using nougat, the latest nightly fixed all problems, i suppose it was a bug in the specific version, then. now i am at 7.1.2
cheers
martytoo said:
Was there ever a resolution to this. I am having freezing issues with all versions of Nougat on my Verizon S5.
---------- Post added at 09:49 PM ---------- Previous post was at 09:46 PM ----------
Were you "tron65" ever able to use Nougat on your S5 without freezing? Thanks.
Click to expand...
Click to collapse
I only found a solution doing a full install and going back to 6.0.1. The latest (last) CyanogenMod build didn't work for me, and now they're defunct anyhow.