Hi all,
after updating my unrooted Nexus 4 to Android 4.4.4 OTA, I have quite an annoying issue: I can only turn wi-fi on once per reboot. If I turn it off to save battery when i'm out of range of wi-fi hotspots, i have to reboot the phone to be able to turn wi-fi on again.
Anybody else having this issue? Any ideas on how to fix it, other than doing a factory reset?
I haven't found a way to wipe Dalvik cache yet, maybe I should try that first...
Any help will be much appreciated.
EDIT: Formatting the cache partition actually seems to have fixed the issue. Yay! :good:
EDIT 2: Nope, the problem persists, both on the Nexus 4 and on the Nexus 7. Should I wait for Android L, or...?
Further Instruction?
Re-flash your radio? Is it named radio-mako-m9615a-cefwmazm-2.0.1701.03
Do you need help with wiping your Dalvik?
Nope, the problem seems to be solved but thanks for asking. I did the same (wiped the cache partition) on my wifes Nexus 7 since she also had a wi-fi issue, hopefully it solves it for her as well.
Related
I recently rooted and installed OmniROM on my Xoom, but am having problems getting the tablet to boot. It makes it past the moto screen, but gets stuck on the blinking omni logo.
I followed the instructions in this thread, but I can't seem to get it to work. I have tried the entire process twice, and tried omitting gapps and even the update. Anyone have an idea what I am doing wrong?
If it means anything, TWRP is unable to wipe Dalvik, data or Internal Storage.
Thanks in advance!
Okay Scratch that. I did a reformat/reinstall and it finally booted. Now I just need to figure out that Text To Speech engine error.:good:
I have the same problem but with the Everest version
I have gone back to Gingerbread then back to EOS4
What did you do to reformat?
Did you successfully manage to wipe the dalvik cache and data etc?
OK in case anyone else had the problems I had then this repartitioning guide helped me. It was slightly different than the guide here, ie not just a wipe everything and expect it all to be ok kinda thing.
I was running my Xoom with the last EOS build and had an earlier version of TWRP. I started by upgrading in recovery to the NonBigPart TWRP and then followed the instructions from this link to repartition format etc and it worked for me.
http://forum.xda-developers.com/showthread.php?t=2506997
Same Problem - can you explain more?
Zaxxon8 said:
Okay Scratch that. I did a reformat/reinstall and it finally booted. Now I just need to figure out that Text To Speech engine error.:good:
Click to expand...
Click to collapse
I have the same problem. Can you explain what you mean by "a reformat/reinstall and it finally booted"? My Xoom is stuck on the Omni Android screen with the android blinking, but will not finish loading. My advanced wipe did not wipe all and I received a failed message. I'm guessing that is my issue, but I'm not sure what to do about it. Any help would be appreciated.
cagerbrandt said:
I have the same problem. Can you explain what you mean by "a reformat/reinstall and it finally booted"? My Xoom is stuck on the Omni Android screen with the android blinking, but will not finish loading. My advanced wipe did not wipe all and I received a failed message. I'm guessing that is my issue, but I'm not sure what to do about it. Any help would be appreciated.
Click to expand...
Click to collapse
Okay. I found out what to do. Thanks though. Persistence works.
Seriously? Can't anyone explain what they did to fix the problem? You guys are pretty quick to ask for help, but don't even take the time to explain what you did to people who have the same problem.
If there's anyone with the same problem, the solution is to go to the wipe option and instead of using advanced wipe, just use format to delete all internal storage, then reboot and clear dalvik cache, etc. then flash omni, gapps and superSU (in that order), then reboot and wait a few minutes on the omni loading screen and its done.
I am struggling to get past the blinking omni logo, tried all ways to get this to boot, am i missing some thing
Folks,
Strange one. Just upgraded to Lollipop 5.0 and now when I move out of range from a WIFI access point, my phone DOES NOT automatically switch to mobile data. Previously on KitKat 4.4.2, where this would occur automatically.
Strange thing is that when I manually switch off the WIFI transmitter on my phone, it then switches to mobile data.
Don't want to have to do this all the time when I'm out of range!
Any advice would be great.
Thanks in advance.
Mine did that once, clearing cache from recovery and rebooting the phone fixed it
Turn off smart network switch too from wifi settings
Cheers.
Will give this a try.
Also remember that after upgrading from KK to LP, leaves a load of rubbish files behind from KK that cause all sorts of problems, it is highly advised to factory reset after upgrading, you'll find most people here have done that and it solves a majority of problems
Ok cool.
Looks like I might have to do this.
Have tried clearing cache from recovery and have also disabled autoswitching - still getting the same issue.
Will try a factory reset.
Hi everyone,
i am having a SM-G900F (it is t-mobile). It is on stock lollipop LRX21T.G900FXXU1BNL9 with modem and bootloader BOB7 (which i flashed a week ago).
I have problems since the last 2-3 days, my phone is connected to a working WiFi or mobile data and everything seems alright, but it isn't, i don't have any internet access. I have to turn of WiFi or mobile data and turn it on and eventually it starts working again :S
Does anyone has an idea what the problem may cause and how should i fix it? Thanks in advance
EDIT: Also if i take out the battery of my phone and turn it on afterwards, it turns off but with a black screen, and i get a "System fc", and i have to try to turn it on a few times to get it work like it should, but if i turn off the phone without taking out the battery it turns on just fine everytime
First thing Id try is clearing CACHE from Recovery
Did you factory reset after updating to Lollipop from KK? It is needed to get rid of left over bugs / files from KK
*Detection* said:
First thing Id try is clearing CACHE from Recovery
Did you factory reset after updating to Lollipop from KK? It is needed to get rid of left over bugs / files from KK
Click to expand...
Click to collapse
When i bought the phone (used) it already had lollipop on it. I tried clearing cache+dalvik cache but still the same, but didn't tried a factory reset, right now i am downloading a custom rom, will wipe everything and see what happens after that.
Some strange thing that i noticed is, that the internet now won't work for any app escept for viber, on viber it works without problems
Right now i have flashed another ROM with wipe-ing everything before and i have still problems with the internet :S
i don't know what do to now :/
EDIT: Data is working, but wifi connects but no internet :/
EDIT2: I've found out what the problem is, it wasn't my phone, it was some weird virus which changed my routers DNS settings
Last night, my wifi just stopped working, it won't enable. When I go to advanced I am sometimes able to turn on the wifi, but it just continuously says turning on but won't enable, and sometimes it's just totally greyed out. I also had some problems today connecting to mobile data services as well, and I don't know if that's related.
I've tried a hard reboot (but it just comes up saying no command...), I've tried restarting it a million times... The only thing I haven't tried is a factory reset, because I am abroad using google fi and I am worried that I will have to set up my project fi again and I can't connect to a tower in the USA. (I am not sure if that will even happen, but I won't be back in the USA for a good few months so I don't want to risk it)
My phone says it updated yesterday, which I assume has caused this wifi problem (or a really big coincidence), but I can't find any information online about it.
I run the stock rom, it's not rooted, I have had no problems with any other things besides this.
Is anyone else experiencing this, or has experienced this before? Do you have any suggestions on how to resolve it?
It sounds like you are experiencing the same problem as everyone who forgot to update their vendor image after flashing the OTA. Had you been rooted, the simple fix would have been to flash the the MTC19X vendor image. With unrooted phone, I got nothing. The only possible solution would be a factory reset and to download and install the OTA again.
kyzn said:
It sounds like you are experiencing the same problem as everyone who forgot to update their vendor image after flashing the OTA. Had you been rooted, the simple fix would have been to flash the the MTC19X vendor image. With unrooted phone, I got nothing. The only possible solution would be a factory reset and to download and install the OTA again.
Click to expand...
Click to collapse
I don't touch anything or mod anything on my phones. The phone updates itself and as long as I am not running any custom roms I don't see why they wouldn't have a complete update that basically just spoon feeds my phone. Do you know if factory reset would reset my project fi?
RoseBunny87 said:
I don't touch anything or mod anything on my phones. The phone updates itself and as long as I am not running any custom roms I don't see why they wouldn't have a complete update that basically just spoon feeds my phone. Do you know if factory reset would reset my project fi?
Click to expand...
Click to collapse
I believe factory resets wipe the /data and /cache partitions of the device. All apps installed in /data are deleted, while apps in /system like project fi will have all its setting reset.
It's easy to resolve the iasue if your rooted, but since you aren't the next to last step you may try would be doing a network settings reset. Go to Settings>Backup and Reset>Network Settings reset. Just make sure that you are aware of your cellular data settings so you can set thing back up after the reset.
Hello guys, I've a nexus 6p that doesn't starts. I was wondering that was caused by the well known problem, but my particular phone is stuck on "balls" bootanimantion... So I think it isn't related to the snap810 problem.
I should say that the smartphone was completely out of memory, no MB of storage left. Maybe this is the problem?
I should apply the known methods to solve bootloop?( I mean... Flashing modified kernel...)
I tried also wiping cache with no result.
I didn't already made a factory reset because the owner asked me if I can save photos.
Thanks.