I woke up, turned on my phone, it asked me if I was running a custom OS or not, I can't remember I was still waking up, I hit a button and then it started doing this, wondering if I can just turn it off?
I'm rooted and I've been havin those annoying 4.4.2 updates keep popping up, but I haven't updated cause I dint wanna lose root. HELP
brainpuke said:
I woke up, turned on my phone, it asked me if I was running a custom OS or not, I can't remember I was still waking up, I hit a button and then it started doing this, wondering if I can just turn it off?
I'm rooted and I've been havin those annoying 4.4.2 updates keep popping up, but I haven't updated cause I dint wanna lose root. HELP
Click to expand...
Click to collapse
please give full info about your phone
and what is your problem in detail
Never EVER stop an update in the middle of it. That's one of the surest ways to brick your phone, on ANY phone, even iPhones. What you were describing was Samsung's Download Mode, it sounds like. You should have disabled the updates. Sounds like it was set to auto update, and since you were half-asleep, you confirmed it. Hopefully lesson learned about touching things you don't understand...
Related
Hello!
Well... I have this phone since yesterday... I plugged to the computer with Kies, and well, a update was available... now the phone have Froyo and the aesthetics changed completely, it looks awesome.
But, the phone have this ANNOYING problem that, after using it... like 5~10 minutes of no activity, when I try to use the phone again it doesnt work... doesn't respond to any button, I have to take off the battery in order to restart it and that over and over again...
I've realized also that this happens when I'm using wifi, if I left the phone with wifi on this happens, without wifi seems to work fine.
Somebody have any clue what could be? there's little information about this issue in the internet...
I think I'm going to return it but I want to try everything I can do (without voiding the warranty) since the phone was perfect for what I wanted.
Thanks in advance!
Hey. I got the same problem here. It only happened a few times when I just had froyo that came stock on my galaxy 5 but I recently installed cyanogenmod 7 and now its happening everytime I put my phone down.
So I'm guessing it may be directly related to what rom is installed? I've heard about it happening a bit to people who have 2.1 installed to.
I dont know too much but it seems the only fix is to take out battery and turn on.
Sorry I can't help more. I hope somebody knows a bit more than me on this.
Think this is called something like the 'wifi sleep of death', something to do with the rom. i'd try change the rom and see if it still occurs
Thanks for the hints tho!, but I returned the phone... it seems that is a bug related to the update of the phone, since I know that with the out of the box 2.1 version it doesn't have that issue...
You know, the mobile carriers also do weird stuff to the roms... -__-
Lately my tab has been turning off by itself and it takes me a long time to turn it back on by holding the power button. Has a fix been found for this problem yet? I'm a little worried that one day the thing won't turn on again. Sometimes the tab is charged when it turns off, and I'm never using the thing when it does, so battery isn't really the issue. Any suggestions?
Gja88 said:
Lately my tab has been turning off by itself and it takes me a long time to turn it back on by holding the power button. Has a fix been found for this problem yet? I'm a little worried that one day the thing won't turn on again. Sometimes the tab is charged when it turns off, and I'm never using the thing when it does, so battery isn't really the issue. Any suggestions?
Click to expand...
Click to collapse
Are you rooted? Running a custom ROM? Running any extra mods at all?
No, I'm fully stock,never been rooted. Willing to root if the problem can be fixed though through a rom or something
i've made good strides in combating this.
But, you must have CWM installed in order to flash.
When you are ready to do this, then head over to the dev section, kernel thread.
In the meantime, set wifi to never sleep, and see if that cures some of it.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
To be honest if you have a completely stock machine I would call samsung and get them to check it, it sounds faulty. I work for a large computer retailler and haven't seen a single one behaving like yours out of hundreds.
Brian
Brian-UK said:
To be honest if you have a completely stock machine I would call samsung and get them to check it, it sounds faulty. I work for a large computer retailler and haven't seen a single one behaving like yours out of hundreds.
Brian
Click to expand...
Click to collapse
Mine also does and I have seen posts in other forums of others complaining of smae thing.
Ian
For the past week or so the wifi radio on my phone has been acting up. Once or twice a day it will start to constantly cycle on and off. If I manually turn it off while it's in the "on" phase, it usually stays off. But when I go to turn it back on it just goes back into the loop, even if I wait an hour. The only way to fix it is to reset the phone, sometimes more than once (hard reset holding power and volume up). I rooted my phone over a month ago and haven't done anything else root-related since (no ROMs, mods, not even deodex). I did install AdAway, but that was at the time I rooted it and this just started happening. Not sure what could be causing this or if I just need to contact Verizon for a replacement.
Wifi cycling
Spaded21 said:
For the past week or so the wifi radio on my phone has been acting up. Once or twice a day it will start to constantly cycle on and off. If I manually turn it off while it's in the "on" phase, it usually stays off. But when I go to turn it back on it just goes back into the loop, even if I wait an hour. The only way to fix it is to reset the phone, sometimes more than once (hard reset holding power and volume up). I rooted my phone over a month ago and haven't done anything else root-related since (no ROMs, mods, not even deodex). I did install AdAway, but that was at the time I rooted it and this just started happening. Not sure what could be causing this or if I just need to contact Verizon for a replacement.
Click to expand...
Click to collapse
I got a DNA last week and lose wifi when I'm on my patio, which never happened with my Galaxy Nexus LTE. In the house, the wifi cycles a couple of times a day. I would appreciate any input.
This happens to me no matter what network I try to connect to or where I am at.
Anyone else have this happen? I am ready to do a factory reset and I really don't want to since this phone doesn't have an SD card.
any one with same prob?
sandeep.mjs said:
any one with same prob?
Click to expand...
Click to collapse
Did you install a custom ROM and/or kernel?
If custom, a kernel change may help.
If you did any tweaks like overclock, undo those changes.
But to answer your question, this hasn't happened to me.
yearn2burn said:
Did you install a custom ROM and/or kernel?
If custom, a kernel change may help.
If you did any tweaks like overclock, undo those changes.
But to answer your question, this hasn't happened to me.
Click to expand...
Click to collapse
I rooted my phone but have not done anything else besides install AdAway. I planned on installing a few tweaks like the battery percent indicator and location icon remover but honestly the whole odex/deodex thing really confused me so I haven't done anything else.
I am going to get a new SIM card today because my phone keeps saying it doesn't have one and I have to reboot once or twice to get it to come back up, but I doubt that could be the cause of my wifi issues.
I have the Verizon S4 i545, obviously. Rooted right after getting it in June. Still on Android 4.2.2, kernel 3.4.0-562219, build number i545VRUAMDK. I have never updated anything. Tried, tbh, but OTA fails. But whatever. I have never had an issue with anything, until a few days ago. Now, whenever my phone turns on, regardless of whether it was restarted or powered down then on, It hangs at the Verizon animation, then finally goes to my lockscreen with no notification bar. Phone is essentially useless at this point because when I unlock my phone, I get a black screen that does nothing. Only way to fix it, is to pull the battery, then power on. Works every time. I have no idea what happened to cause this. I have not removed anything system related recently. Any ideas?
I would like to fix the problem and leave it. But if I can't, I might be flashing a new rom.
Kasper DG said:
I have the Verizon S4 i545, obviously. Rooted right after getting it in June. Still on Android 4.2.2, kernel 3.4.0-562219, build number i545VRUAMDK. I have never updated anything. Tried, tbh, but OTA fails. But whatever. I have never had an issue with anything, until a few days ago. Now, whenever my phone turns on, regardless of whether it was restarted or powered down then on, It hangs at the Verizon animation, then finally goes to my lockscreen with no notification bar. Phone is essentially useless at this point because when I unlock my phone, I get a black screen that does nothing. Only way to fix it, is to pull the battery, then power on. Works every time. I have no idea what happened to cause this. I have not removed anything system related recently. Any ideas?
I would like to fix the problem and leave it. But if I can't, I might be flashing a new rom.
Click to expand...
Click to collapse
Are you running a custom rom.
No I'm not. Everything is untouched except for the root process. That's it.
Kasper DG said:
No I'm not. Everything is untouched except for the root process. That's it.
Click to expand...
Click to collapse
I would guess to flash VRUAMDK no wipe factory image.
http://forum.xda-developers.com/showthread.php?t=2301259
Any idea why I'm randomly having this problem?
Kasper DG said:
Any idea why I'm randomly having this problem?
Click to expand...
Click to collapse
I don't really know, I've never encountered a problem like that yet.
Ok. Might try flashing the factory image.
hi all, as the title says my hox + is repeatedly crashing n rebooting. this has been happening since yesterday. the hox was fine in the morning and then randomly started playing up in the afternoon. the phone is completely stock n locked. its not the power button as when I enter fastboot the phone stays on n doesn't even freeze. it went flat after a while so I left it to completely flatten over night. its been on charge for a while now n its still rebooting even without me turning it on, it turns on by itself.....freezes.....then reboots.
any ideas guys?
really don't want to pay for insurance again n I now know it takes takes 2 weeks to replace a lost phone so god knows how long it will take them to look at a phone
"pay for insurances AGAIN"?
Does this happen randomly? Or it happens all the time? If you will be enough desperate, you can always try a factory reset as this looks like a software bug.
/\/\ said:
"pay for insurances AGAIN"?
Does this happen randomly? Or it happens all the time? If you will be enough desperate, you can always try a factory reset as this looks like a software bug.
Click to expand...
Click to collapse
yeh ive tried factory reset in fastboot and also erased cache command. im going to try a rom now ive got it to stay off n charge. it will only stay off selecting power down quickly, if I select power off in bootloader it restarts. it does seem like software though as it doesn't auto reboot in recovery or bootloader
well a new rom ddnt work.....n of course I cant find an ruu anywhere
bassyboy said:
well a new rom ddnt work.....n of course I cant find an ruu anywhere
Click to expand...
Click to collapse
you can try increasing the voltage for the CPU...
does it show something on its screen when it reboots?
cant do anything. it would boot up fully...then freeze after 5 secs or so then reboot and do the same again. Ive claimed for a new phone now tho. I couldn't find an ruu after trying a new rom so insurance repair wasn't going to happen. the phones gone now n hopefully a replacement will come soon. guessing I had a bad refurb last time iclaimed