Hello guys!
I'm a new guy here, but found no answers to the following issues.
So i've got the 6.0.1 update to Note 4, and now im stuck with issues like the Phone just freezes, crashes and hangs for like 1 minute after i can use it again, so i had to download the WakeLock application from the google play store.
I'm just curious, is this a phone issue, or its releated to the stock rom? I should flash a new ROM based on guides here, or is there any fixes to this issue?
Thanks.
You may have to try a factory reset. I haven't heard of this issue
Mine went into the same issues since a day or 3. Factory reset, cache wipe, no dice until now.
clawlancer said:
Hello guys!
I'm a new guy here, but found no answers to the following issues.
So i've got the 6.0.1 update to Note 4, and now im stuck with issues like the Phone just freezes, crashes and hangs for like 1 minute after i can use it again, so i had to download the WakeLock application from the google play store.
I'm just curious, is this a phone issue, or its releated to the stock rom? I should flash a new ROM based on guides here, or is there any fixes to this issue?
Thanks.
Click to expand...
Click to collapse
i had this problem with my n910C but it was after flashing custom kernel ,
factory reset and it was working like a charm then
Related
Hello Guys,
I'm with a problem in my #nexus4 .. If i update my device to #android 4.3 or newer my phone gets #bootloop and don't start anymore. I read a lot of tips to solve that but nothing worked. I tried to reflash with stock firmware from google (developers images to nexus devices) but didnt work (flash-all.bat), i tried use #NexusRootToolkit but happened the same situation. I tried to install the versions 4.3, 4.4, 4.4.2, 4.4.4, 5.0 and happened the same problem at all.
Someone could help me? Because i didnt find how to solve since a last year. I'm using android 4.2.2 because its the only one that works.
I tried all methods like flash stock rom, but, wont works. ....
Could someone help me with that please??
I have the same problem, can someone help ?
Any updates?
I have the same problem. I used to get the bootloop when I updated from 4.4.3 to 4.4.4 and from 4.4.4 to 5.0 and from 5.0 to 5.01 and in all those times, from what I can recall, a wiping of the cache/delvik + fix-permissions + install the modified boot image from NRT - solved the problem.
However - a couple of days ago, after getting the Google Cardboard and playing around with it, installing all the VR stuff and playing with magnets around my phone to get it to work with the VR - I think I must've damaged something because it suddenly died and refused to get back up and out of a bootloop. I tried the above procedures and it didn't work. I went back to version 5.0, then 4.4.4 and further back till only 4.2.2 worked, as with the first post here. It's the only version that doesn't give me the bootloop. If I try then to upgrade I again get the bootloop, whether it's a full flashing or an OTA update (to 4.3).
One thing I noticed with 4.2.2 - it's not acting all that well: when I download apps through Google Play some of them seem to get stuck at 85-95% on the download and won't install. Maybe I have a faulty storage issue...?
Any insight on how to fix that?? Any news from those who experienced the same issue?
Thanks!
tiagomoraisc said:
Hello Guys,
I'm with a problem in my #nexus4 .. If i update my device to #android 4.3 or newer my phone gets #bootloop and don't start anymore. I read a lot of tips to solve that but nothing worked. I tried to reflash with stock firmware from google (developers images to nexus devices) but didnt work (flash-all.bat), i tried use #NexusRootToolkit but happened the same situation. I tried to install the versions 4.3, 4.4, 4.4.2, 4.4.4, 5.0 and happened the same problem at all.
Someone could help me? Because i didnt find how to solve since a last year. I'm using android 4.2.2 because its the only one that works.
I tried all methods like flash stock rom, but, wont works. ....
Could someone help me with that please??
Click to expand...
Click to collapse
no good news ...
hummus said:
I have the same problem. I used to get the bootloop when I updated from 4.4.3 to 4.4.4 and from 4.4.4 to 5.0 and from 5.0 to 5.01 and in all those times, from what I can recall, a wiping of the cache/delvik + fix-permissions + install the modified boot image from NRT - solved the problem.
However - a couple of days ago, after getting the Google Cardboard and playing around with it, installing all the VR stuff and playing with magnets around my phone to get it to work with the VR - I think I must've damaged something because it suddenly died and refused to get back up and out of a bootloop. I tried the above procedures and it didn't work. I went back to version 5.0, then 4.4.4 and further back till only 4.2.2 worked, as with the first post here. It's the only version that doesn't give me the bootloop. If I try then to upgrade I again get the bootloop, whether it's a full flashing or an OTA update (to 4.3).
One thing I noticed with 4.2.2 - it's not acting all that well: when I download apps through Google Play some of them seem to get stuck at 85-95% on the download and won't install. Maybe I have a faulty storage issue...?
Any insight on how to fix that?? Any news from those who experienced the same issue?
Thanks!
Click to expand...
Click to collapse
I think it's a defective device. You have to repair or change it. Sorry
No Sensors
Looks like none of my sensors are working, judging from 3 sensor testing apps I've downloaded. Seems as if the motherboard is defective.
tiagomoraisc said:
no good news ...
Click to expand...
Click to collapse
hummus said:
Looks like none of my sensors are working, judging from 3 sensor testing apps I've downloaded. Seems as if the motherboard is defective.
Click to expand...
Click to collapse
The same situation I have
Fix
tiagomoraisc said:
Hello Guys,
I'm with a problem in my #nexus4 .. If i update my device to #android 4.3 or newer my phone gets #bootloop and don't start anymore. I read a lot of tips to solve that but nothing worked. I tried to reflash with stock firmware from google (developers images to nexus devices) but didnt work (flash-all.bat), i tried use #NexusRootToolkit but happened the same situation. I tried to install the versions 4.3, 4.4, 4.4.2, 4.4.4, 5.0 and happened the same problem at all.
Someone could help me? Because i didnt find how to solve since a last year. I'm using android 4.2.2 because its the only one that works.
I tried all methods like flash stock rom, but, wont works. ....
Could someone help me with that please??
Click to expand...
Click to collapse
I made a similar thread, and found a fix.
Here http://forum.xda-developers.com/nexus-4/help/nexus-4-jellybean-4-2-2-t3472292#post68941174
Hey everybody,
I've been having an issue lately. Since I upgraded to Android Lollipop, I have not been able to get a GPS lock anymore. This issue only applies when I'm on a Lollipop ROM. As soon as I flash back to a kitkat TW ROM, everything works again. When I go back to a Lollipop ROM, the issue returns again.. No GPS lock. This is not ROM specific, but just related to Lollipop in my experience.
I have not seen anyone else yet with this issue, so I find this very strange. I'm currently on the latest version of GPE5 by @Danvdh if this helps. But like I mentioned before, the issue exists on every Lollipop ROM.
If someone could please help me, this would be very much appreciated! Thanks!
Anyone? ?
Me Gusta!
It seems to be a Lollipop thing.
I have the same issue with my Find 7 since installing Lollipop.
See this discussion:
https://code.google.com/p/android/issues/detail?id=81140
Me Gusta said:
Anyone?
Me Gusta!
Click to expand...
Click to collapse
mate, flash official firmaware and reset /set up your original csc with samsung phone info+ app from google play , worked on 3 phones until now this solution , be carefully csc reset gonna wipe your internal storage
thanks, i will try it
Hello friends, i have samsung galaxy s5, when i bought it , it was running kit kat 4.4.2, i updated it to lollipop 5.0 OTA, it was okay and running smooth for a few days, now it is generating heat at the back , because of which the battery percentage drops by 1-2 % after one minute, which is very annoying, i hard rest my s5, the problem was gone for few hours, but then come back , i again hard reset it, and also formatted my MMC, but now after few hours it still showing that problem, please can some one help me here, i love my s5, i dnt want to lose it any one here please provide a possible solution, thanks in advance.
Hard reset?
Factory reset fixes most issues caused by leftover KK files
toohurt said:
Hello friends, i have samsung galaxy s5, when i bought it , it was running kit kat 4.4.2, i updated it to lollipop 5.0 OTA, it was okay and running smooth for a few days, now it is generating heat at the back , because of which the battery percentage drops by 1-2 % after one minute, which is very annoying, i hard rest my s5, the problem was gone for few hours, but then come back , i again hard reset it, and also formatted my MMC, but now after few hours it still showing that problem, please can some one help me here, i love my s5, i dnt want to lose it any one here please provide a possible solution, thanks in advance.
Click to expand...
Click to collapse
Hi toohurt,
I have been having this issue as well, it sounds like its a bug with the lollipop update for s5. If you are with verizon, supposedly their latest update fixes the issue, so I would try that first.
I saw some advice on another forum that if the hard reset didnt work, that rebooting the phone about 5 minutes after you take it off the charger can at least help stabilize the battery drain a little. I've also seen that uninstalling Google Fit and then disabling the "S Health" app can help.
As a last resort you can always go back to kit kat.
Hopefully that helps!
*Detection* said:
Hard reset?
Factory reset fixes most issues caused by leftover KK files
Click to expand...
Click to collapse
Yes by hard reset i mean factory reset, still the problem remains
Goldmeyer said:
Hi toohurt,
I have been having this issue as well, it sounds like its a bug with the lollipop update for s5. If you are with verizon, supposedly their latest update fixes the issue, so I would try that first.
I saw some advice on another forum that if the hard reset didnt work, that rebooting the phone about 5 minutes after you take it off the charger can at least help stabilize the battery drain a little. I've also seen that uninstalling Google Fit and then disabling the "S Health" app can help.
As a last resort you can always go back to kit kat.
Hopefully that helps!
Click to expand...
Click to collapse
Yes dear i do the same, reboot my cell phone for 5 minutes, so the problem goes away for some time, i dnt want to go back to kit kat, waiting for 5.0.1 or 5.1 , may be that will solve the problem, and no mine is not on verizon, and can u tell me how to disabale s health please
Hi,
Got a strange issue on my i9505. Evrything working fine at boot until i lock the screen (or until it lock by himself).
Then touch screen become irresponsive.
other roms , factory reset nothing works ...strange because seems to be driver related.
I was about to odin flash a samsung rom ...
Has anybody ever experienced such behaviour ?
Z
Problem solved by reflashing samsung firmware than soin all he road again .
Suppose bl related.
zapatt said:
Problem solved by reflashing samsung firmware than soin all he road again .
Suppose bl related.
Click to expand...
Click to collapse
Hello!
I know that reviving dead threads is not very popular but would you please tell me what you wanted to say in your post? I presume that some auto complete function garbled your text. Which revision of Samsung firmware did you flash to solve the problem?
I have exactly the same problem. Moreover, it prevents me from installing Optimized CM13 since I don't have touch in AROMA installer.
eTaurus said:
Hello!
I know that reviving dead threads is not very popular but would you please tell me what you wanted to say in your post? I presume that some auto complete function garbled your text. Which revision of Samsung firmware did you flash to solve the problem?
I have exactly the same problem. Moreover, it prevents me from installing Optimized CM13 since I don't have touch in AROMA installer.
Click to expand...
Click to collapse
Hi Taurus,
I m not sure we got the same issue. My touchscreen become irresponsive After being Locked, either in twrp or in Android. As far as I Can remember, it Was related to custom kernel, i have to reflash à Samsung kernel. I think i Was underground jdc lollipop rom.
We have exactly the same problem, actually. It prevents me from installing a custom ROM which sucks!
Hi everyone,
My brother has a samsung galaxy s5 SMG900F which was working just fine on lolipop. After seeing that he got updates to install I installed them all for him. After the update was done the phone behaves strange. It has signal but i can not make any calls, when i try it it just hangs on the calling screen with nothing happening.
We did also a factory reset but still the same issues.
The phone is now on: XXU1BOJ1, XXS1PPC8.
I do not know which version it was earlier but right now I am downloading G900FXXU1CPEM, G900FBHT1CPE3 from sammobile (latest for Bosniua BHMOBILE) and I hope that after flashing it the issues will be gone.
In the meantime, did anyone else experience similar issues? Why could this be happening and what is my best bet on solving it?
EDIT: I need also to mention that the wifi is going crazy, it can not connect, or it connects but disconnects again etc.
EDIT2: After flashing official stock 6.0.1 the problem still exist Please help
EDIT3: Just did a factory reset through the service menu, after that flashed again the 6.0.1 and now everything is working again