KF1: Permanent Restart after Power Off - Galaxy S II General

I've experimented today with the leaked XWKF1 build from samfirmware.com! After a few hours I realized that I've got a (for me serious) bug as well:
Every time I wanted to do a power off (shut down), the phone immediately restarts itself. Tried everything to get rid of this: Reflash with or without repartition, factory reset, rooting, using ZSKF1 kernel, CWM4.0.0.2, ...
Even after pulling the battery out: As soon as I put the battery back in the phone booted up immediately.
At this time I began to fear a hardware fault, luckily after going back to Liteningv1-3 power off works as intended again...
So, why I'm writing this here:
If anybody encounters the same: Just flash back your old rom and you will be fine again.
And: Can somebody explain this?

I do not have this problem with KF1

hg3atintin said:
I do not have this problem with KF1
Click to expand...
Click to collapse
Thx for your feedback!
I'm almost sure most people won't have that problem, otherwise there should be quite a few reports till now...

I've had that issue before, on KE7 and my o2 stock ROM. I never could figure out what caused it, but battery pulling usually fixed it (at least good for a few power downs)

Might be that you have an alarm set in the next days.

just flashed to the kf1 stock and don't have the problem

I think when you are on a custom rom and go to stock, you might encounter weird quirks like this. Since the stock roms are non-wipe, it may leave remnants of your custom rom. Might be better to try a full factory reset and wipe cache/dalvik from recovery before flashing if you are okay with losing all data to see if that stops the reboot issue. Its not always necessary but I have had some weird problems in the past.
Either that or just wait for Litepro to come out with a KF1 version or another version in the near future. I think thats what I'll do

+10 for a wipe .
jje

Related

WIFI not switching on

Hi, about 5 days ago my wifi stopped working. I'd turned it off a few days earlier since I didn't need it. When I try to turn it back on now though, it takes a few seconds and then says error. I'm not sure what's wrong with it.
Since then I've reflashed my phone rom (leedroid), factoryreset it, and updated the radio. nothing so far has fixed it. Mobile data still works so I wouldn't think it was hardware, but a software error shouldn't have survived the wipe and the radio update.
Does anyone have any suggestions?
blackied said:
Hi, about 5 days ago my wifi stopped working. I'd turned it off a few days earlier since I didn't need it. When I try to turn it back on now though, it takes a few seconds and then says error. I'm not sure what's wrong with it.
Since then I've reflashed my phone rom (leedroid), factoryreset it, and updated the radio. nothing so far has fixed it. Mobile data still works so I wouldn't think it was hardware, but a software error shouldn't have survived the wipe and the radio update.
Does anyone have any suggestions?
Click to expand...
Click to collapse
I had similar issue when flashing another kernel on my stock ROM. Maybe your kernel isn't compatible with the radio or the kernel modules haven't been applied correctly. Hardware error should be presumed after flashing original RUU.
The thing is that I hadn't played with my phone since last year. the wifi just randomly stopped working. It was still on 1.22ghz kernel 1.0.2. It got reset to stock kernel when I factory wiped it.
I've gotta go travelling again for work tomorrow so I'll try flashing the original ruu back next weekend. Would it just be a case of restoring the original nandroid backup I did before I first h-booted/rommed it?
blackied said:
The thing is that I hadn't played with my phone since last year. the wifi just randomly stopped working. It was still on 1.22ghz kernel 1.0.2. It got reset to stock kernel when I factory wiped it.
I've gotta go travelling again for work tomorrow so I'll try flashing the original ruu back next weekend. Would it just be a case of restoring the original nandroid backup I did before I first h-booted/rommed it?
Click to expand...
Click to collapse
As far as I know, factory wipe deletes just the user data. I might be wrong though, because this is my first android, so I'm still learning the basics on rooting, kernels, etc. But from your first post it seemed that you updated your radio in that period, so this might be the clue to what happened. I don't know if the nandroid backup would restore everything to stock, but I'm pretty sure that the original RUU would. Still, you should follow a procedure that would allow you to keep your root (I think if you have radio S-OFF, you'd be able to flash 1.32 RUU and just root it). Anyway, you can't return the phone for warranty services with a custom ROM, so you still need to flash a stock RUU.
Sorry, I should clarify: I did the radio update yesterday to see if it could fix it. It wasn't the cause.

[Q] Galaxy S4 restarts every 10 minutes

Well for starters, high everyone!
I have an issue with my S4 and I've searched all over but none of what has been recommended helps.
The issue I have is that my phone will restart about every 10 minutes (give or take). I used Reboot Logger to determine this. The phone only restarts when it is idle. It WILL NOT restart if I am using it (screen is on). The weird part is that it doesn't even go through the whole reboot sequence. The screen will stay black the entire time. The notification button pulses and the home buttons will light up like it was restarting though.
I had a bad battery and had it replaced with a stock Samsung battery. I've tried pulling the SD card, pulling the battery for 10 minutes, pulling the battery while the phone is on, and I've performed two factory resets.
The one thing I have noticed is that, after performing the factory reset, I get an "error" under the little android dude. This also happens if I do a cache wipe.
My model is the SPH-L720 running on android v4.3. The phone has never been rooted and there are no software or firmware updates that are found.
I was beginning to think that this was a hardware issue but the consistency in reboot intervals makes me believe otherwise. At this point I'm at a loss. I rooted my old phone but my experience in that area is very limited. I have read that the cache partition is bad from the factory on some of these (hence the error message) so I was thinking about rooting the phone and trying to use a good cache partition, but that's the only other option I could think of.
sounds like a voltage prob....or mem prob... id redownload a new rom..wipe wipe wipe..reinstall and that should fix it
Sent from my SPH-L720 using xda app-developers app
Insufficient voltage at idle was my first thought too, but if you haven't undervolted (since you aren't even rooted), that seems less likely. If I were you, I'd root the phone so I could do more to figure things out. Maybe try bumping up the voltage a little on the lower clock speeds.
Ok, first of all, do not root your phone. As you admitted yourself, you have limited experience in this area, and there is nothing that rooting will do for you. Not to mention, if you think you have a bad cache partition, you don't need root to fix it. Your phone is stock, running the stock kernel, there is no reason to suspect voltage issues that are not hardware related. If you root the phone, you will likely trip KNOX, and void your warranty.
My personal opinion is that your phone has a hardware problem. If you want to truly start over, either recover your phone through KIES, or better yet, download and flash via ODIN a stock MK2 ROM from this forum. Since this is a stock, signed ROM, you will not trip KNOX, and it will rewrite every partition properly on it's own. This is all assuming you don't have a hardware problem. But do not go ahead and try to fix anything yourself besides what I mentioned. You will not succeed, and likely lose your warranty in the process.
Edit: did you buy this phone new or used? If you bought it used, more than likely somebody ruined it for you. And more than likely, you can fix it. If this was a new device, more than likely it will be a warranty issue. That's why you shouldn't do anything to void the warranty.
If you're going to use odin for anything, just make sure you follow someone's directions step by step. Otherwise very bad things can happen.
im also having a slightly similar problem
Problem : The screen after a sleight amount of time of being on, or sometimes instantly when opening the lockscreen it freezes for 10-15 sec then shoots black lines across it, then reboots.
Things ive tried :
1. Installing a new rom ( from AOKP 4.4 and Triforce 4.3)
2. Changing modem (from MJA, MK2, NAE)
3. Changing the type
of Gapps i was using. (4.3 gapps for triforce, aokp 4.4 gapps, and pa gapps)
Current Phone Info:
Rom: aokp_jfltespr_kitkat_nightly_2014-02-08
Modem/Firmware: NAE
Gapps: Pa.gapps 4.4.x
Let me know if you need anything more! plz!
I'll look into Odin before I root. The phone was also purchased new. I spent most of today monkeying around with different settings to see if I could trigger the issue as well. As it turns out, the phone will only restart at idle if it's plugged into the charger, or the wifi is on. If wifi is off and it's not plugged in it's fine. I am also using the stock Samsung charger that came with the phone. Again though, if I'm actively using the phone it doesn't happen (charging or connected to wifi). I did turn the phone off earlier to charge it but would keep freezing at the sprint logo upon boot up. I thought it was bricked for a second... I wiped the cache (didn't do a factory reset) and that fixed it, but now I have that stupid issue where videos won't play on wifi, only on 4G or 3G. It's an issue I thought I had solved.
Le sigh. This is frustrating. The Odin option is looking to be my best bet it seems.
Tizamarou said:
im also having a slightly similar problem
Problem : The screen after a sleight amount of time of being on, or sometimes instantly when opening the lockscreen it freezes for 10-15 sec then shoots black lines across it, then reboots.
Things ive tried :
1. Installing a new rom ( from AOKP 4.4 and Triforce 4.3)
2. Changing modem (from MJA, MK2, NAE)
3. Changing the type
of Gapps i was using. (4.3 gapps for triforce, aokp 4.4 gapps, and pa gapps)
Current Phone Info:
Rom: aokp_jfltespr_kitkat_nightly_2014-02-08
Modem/Firmware: NAE
Gapps: Pa.gapps 4.4.x
Let me know if you need anything more! plz!
Click to expand...
Click to collapse
Since you are running a custom source-built ROM, first thing to do would be to ODIN a stock ROM. If the problems go away, you have your answer. If not, this would likely be a warranty issue. Of course you tripped KNOX most likely already.
sputnik767 said:
Ok, first of all, do not root your phone. As you admitted yourself, you have limited experience in this area, and there is nothing that rooting will do for you. Not to mention, if you think you have a bad cache partition, you don't need root to fix it. Your phone is stock, running the stock kernel, there is no reason to suspect voltage issues that are not hardware related. If you root the phone, you will likely trip KNOX, and void your warranty.
My personal opinion is that your phone has a hardware problem. If you want to truly start over, either recover your phone through KIES, or better yet, download and flash via ODIN a stock MK2 ROM from this forum. Since this is a stock, signed ROM, you will not trip KNOX, and it will rewrite every partition properly on it's own. This is all assuming you don't have a hardware problem. But do not go ahead and try to fix anything yourself besides what I mentioned. You will not succeed, and likely lose your warranty in the process.
Click to expand...
Click to collapse
Alright I'm a little confused as to what exactly I should be using. I found this:
http://forum.xda-developers.com/showthread.php?t=2575470
which is a stock ROM. Although I also found this:
http://forum.xda-developers.com/showthread.php?t=2259513&highlight=odin
which is the stock firmware.
Which one do I use, or do I use both of them?
Dfeeds said:
Alright I'm a little confused as to what exactly I should be using. I found this:
http://forum.xda-developers.com/showthread.php?t=2575470
which is a stock ROM. Although I also found this:
http://forum.xda-developers.com/showthread.php?t=2259513&highlight=odin
which is the stock firmware.
Which one do I use, or do I use both of them?
Click to expand...
Click to collapse
Neither. Use this one : http://forum.xda-developers.com/showthread.php?t=2601443
Follow instructions in the thread. This is a completely stock rom with no root or mods and will not trip the Knox bootloader. If you flash anything other than this, including custom recovery, cf autoroot, etc, you will void your warranty.
rebooting
i had this problem once and it was related to a corrupt file on my sdcard believe it or not. there are Defraggers out there for your android file system and internal SD card but your Ext sc you would have to do on your PC. it worked for me. the one i used is called CLEAN i got it off amazon app store.
cyberweasal
Dfeeds said:
Well for starters, high everyone!
I have an issue with my S4 and I've searched all over but none of what has been recommended helps.
The issue I have is that my phone will restart about every 10 minutes (give or take). I used Reboot Logger to determine this. The phone only restarts when it is idle. It WILL NOT restart if I am using it (screen is on). The weird part is that it doesn't even go through the whole reboot sequence. The screen will stay black the entire time. The notification button pulses and the home buttons will light up like it was restarting though.
I had a bad battery and had it replaced with a stock Samsung battery. I've tried pulling the SD card, pulling the battery for 10 minutes, pulling the battery while the phone is on, and I've performed two factory resets.
The one thing I have noticed is that, after performing the factory reset, I get an "error" under the little android dude. This also happens if I do a cache wipe.
My model is the SPH-L720 running on android v4.3. The phone has never been rooted and there are no software or firmware updates that are found.
I was beginning to think that this was a hardware issue but the consistency in reboot intervals makes me believe otherwise. At this point I'm at a loss. I rooted my old phone but my experience in that area is very limited. I have read that the cache partition is bad from the factory on some of these (hence the error message) so I was thinking about rooting the phone and trying to use a good cache partition, but that's the only other option I could think of.
Click to expand...
Click to collapse
sputnik767 said:
Neither. Use this one : http://forum.xda-developers.com/showthread.php?t=2601443
Follow instructions in the thread. This is a completely stock rom with no root or mods and will not trip the Knox bootloader. If you flash anything other than this, including custom recovery, cf autoroot, etc, you will void your warranty.
Click to expand...
Click to collapse
That solved my problem, thank you! I spent the last couple days testing it just to be sure I wouldn't be crying wolf. The phone has yet to restart on me even while charging or using wifi. The error message I would receive after a cache wipe or factory reset went away as well. It makes me wonder if the bad partition was what caused my old battery to fail.
Dfeeds said:
That solved my problem, thank you! I spent the last couple days testing it just to be sure I wouldn't be crying wolf. The phone has yet to restart on me even while charging or using wifi. The error message I would receive after a cache wipe or factory reset went away as well. It makes me wonder if the bad partition was what caused my old battery to fail.
Click to expand...
Click to collapse
Great, I am glad it worked out, and hopefully your problem is resolved. I doubt that your old battery failed due to a bad partition, and I have to wonder how your partition got messed up in the first place, but that's just a curiosity and is irrelevant in the grand scheme of things. Just remember that if you decide to root, cf_autoroot works but will trip the KNOX bootloader and potentially void your warranty.

lag, freeze, restart after 6.0.1

hey guys, today i bought a used NOTE 4 for my mother, and when i checked the version it was 6.0.1...so i wiped everything and restarted the phone to get the best performance....but the phone lags and freezes a lot, especially in the camera, and it keep restarting all the time....what should i do? should i try to flash another FW through ODIN?
You mean you used the Factory reset option? That's not a full wipe, just resetting stuffs. And yes, you know the answer, wipe everything from a custom recovery, then flash stock MM ROM (always latest) via Odin. Earlier versions did have a reboot problem though, and lags here and there, but that's expected, but the last release, PE1, has got rid of all those problems, its a very good release already, and I am sure upcoming releases will only make it better. There are no major bugs at all, I don't even find any minor bugs except the need for a separate app to clear default apps selection.
Best of luck.
ithehappy said:
You mean you used the Factory reset option? That's not a full wipe, just resetting stuffs. And yes, you know the answer, wipe everything from a custom recovery, then flash stock MM ROM (always latest) via Odin. Earlier versions did have a reboot problem though, and lags here and there, but that's expected, but the last release, PE1, has got rid of all those problems, its a very good release already, and I am sure upcoming releases will only make it better. There are no major bugs at all, I don't even find any minor bugs except the need for a separate app to clear default apps selection.
Best of luck.
Click to expand...
Click to collapse
the phone is stock, it has the stock recovery, and i have the PE1 version, the exact name is "MMB29M.N910FXXU1DPE1"...and still got a lot of lag, freeze and rebooting.....is there another version?
EDIT: ok, so i flashed another MM through odin ( first time it gave me a fail) and then done a factory reset, now it's so much better, maybe not as smooth as my S6 but really fast and smooth enough...thanks for the help
EDIT: today the phone started to shutdown completly....not reboot....and you need to press the power button 10 seconds to reboot it or turn it on...is there any advice?
Guys . Ib tead the whole thread over last few day had wake lovk runnimg last couple weeks. Lastnight used kies for reset and it crashed half way.
I then used odin 307 and went back to stock 501
It booted strarted to restore from google apps ect .
I allowed the 1st 601 update
All apps running aok no crashing freezing no wakelock .. its asking for another 601 update. Im gonna hold back
Hope this helps .. will post agian in gew days with any updates
Good luck !!
Just download and install Wake Lock from Google Play Store. I had the same problem and more. Once I installed Wake Lock (on a fresh install from Android 5 up to all the 6.0..1 builds) phone doesn't shut off or freeze. Most importantly no more Boot Loops..

Phone crashing and shutting down randomly when not On charge

. For the past few days my phone has been crashing and turning off randomly, when the phone is off the charger. The screen just goes black and Shuts down. When I try to reboot the phone it will get upto the boot animation and then freeze and shutdown again. I have to connect my phone to a charger and then reboot, only then does it fully boot up. My battery is 100% btw.
What I have done so far is:
1) flashed the latest build of exodus
2) cleared dalvik and cache
3) flashed an earlier build (25/07) without flashing XPOSED and SUPERSU. However problem still present.
Can someone help please and tell me what other steps I can take. My phones important to me at the moment as I'm away in Turkey for an internship. It's a really strange problem I can't figure out what to do. Thanks alot
Did you try to go bacm for stock oneplus OS? Try to do a full recovery via the tool it will wipe root twrp back to stock. It may help.
Does it happens with other roms?
hi, i solved the problem by flashing stock oxygen. i tried flashing oxyslim and cyanogen however both of them still had the same problem. Anybody have a idea of why this might have happened? it was completely random, and if it was the kernel then it would have been solved when i flashed the other roms...strange
Zeeshansafdar1 said:
hi, i solved the problem by flashing stock oxygen. i tried flashing oxyslim and cyanogen however both of them still had the same problem. Anybody have a idea of why this might have happened? it was completely random, and if it was the kernel then it would have been solved when i flashed the other roms...strange
Click to expand...
Click to collapse
It could be that te ROMs u DL were corrupted. This happens, thats why is always good yo verify HASH from your dl ROM and HASH from the developers topic
So you haven't read up on the official CM13 thread about the latest unstable builds?

Freezing and rebooting

Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
raz_il_dio said:
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
Click to expand...
Click to collapse
This advice doesn't work with my phone even with holding the buttons for 30 secs and more. For rebooting I can only wait until the battery is completely drained. With little hope for another way shortening time to the next reboot any help is appreciated.
Same here...experiencing the same prob...
Same problem.
Sent from my Redmi Note 4 using Tapatalk
smallcapsicum said:
Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Click to expand...
Click to collapse
Sounds like you need your motherboard replaced i had the same issues on marshmallow thought the nougat update would fix it but realized it was a hardware fault not software..left it in store to get fixed and on repair sheet it said faulty motherboard..
Sent from my SM-G935F using XDA-Developers Legacy app
As i know some S7 have motherboard hardware problem, mine has too, what help? warranty and they replaced motherboard. But if you root, you can say good bye to warranty, they look at knox first with this problem.

Categories

Resources