hi.
In the last week, I have been experiencing random reboots. It usually happens when the phone is in sleep mode, it just restarts by itself.
When this first happened, I was using Vanir ROM with the AK kernel. (there I got green screen instead of a reboot). So I installed the purified kernel, thinking it might be kernel-related. It did not help.
Then I tried Purity ROM (after a full wipe) with purified kernel. Still the same reboots.
Tried Semaphore kernel, the same.
I did a dirty flash of the ROM before switching between kernels.
So I am completely lost here. I go on a vacation tomorrow, and I really hope to fix the problem before I go. So I would really appreciate your help.
Thanks.
romitkin said:
hi.
In the last week, I have been experiencing random reboots. It usually happens when the phone is in sleep mode, it just restarts by itself.
When this first happened, I was using Vanir ROM with the AK kernel. (there I got green screen instead of a reboot). So I installed the purified kernel, thinking it might be kernel-related. It did not help.
Then I tried Purity ROM (after a full wipe) with purified kernel. Still the same reboots.
Tried Semaphore kernel, the same.
I did a dirty flash of the ROM before switching between kernels.
So I am completely lost here. I go on a vacation tomorrow, and I really hope to fix the problem before I go. So I would really appreciate your help.
Thanks.
Click to expand...
Click to collapse
Try flashing a official image via any Nexus toolkits and then install the rom you want.. bakcup your data and also make a nandroid backup..:good:
Hi
I did that, flashed stock ROM and did a full wipe including the user storage.
Then I flashed Purity ROM and Semaphore kernel.
I still experience the reboots, a few times a day usually...
Should I try a different ROM or kernel?
Sent from my Nexus 4 using xda premium
I'm using Purity ROM for some time now and it's just awesome.
Kernel is purified kernel and as i read many people writing about semaphore having better battery live with purity, i tried it.
just for half a day, because it randomly rebooted twice in this time.
first time while talking with someone, second one while browsing the internet.
any idea why? for now i'm back to purified, but i just get normal battery life. maybe 2hrs screen on.
Related
My phone is getting a bootlóop without me flashing anything. This has happened multiple of times. Im using my phone normally and then after i reböot it decides to bóotlóop with a broken recovery??!! How is it possible to bóotlóop that much without flashing anything or of that sorts???
I was using aokp b35 and devil kernel 2 big memory
surely im not the only 1?
that bug happens on every huge mem config kernels*.no one still found fix.
*since Devil2 0.70 Semaphore 2.9.7.devil 1.1.6 kernel not bootlooping
Did a search but have not seen any thread on this, so apologies if I have missed something.
I've just encountered this today and not sure what to make of it. i9000 been on CM9 nightly without issues until I woke up this morning, backlight was on (nothing unusual, just emails overnight), but it will not wake up no matter what I pressed (home button, power button etc.). So ended popping the battery out and start it up again.
This is when the strangest thing happen, loaded the usual Galaxy logo screen, then into the CyanogenMod screen, seconds later, it restarted. This boot loop went on forever. Doing VOL UP + HOME + POWER does not get me back into recovery. At this stage, I am on CM9 nightly 20120707, with CWM 6.0.0.3 (I think).
I ended up having to Odin flash back to GB 2.3.6 (XXJVU) and start over again. And I thought that was the end of it. Picked up the latest nightly 20120728 and RC2, and I ended up with the same symptom. I.e. post WIPE (Data / System / Cache) and loaded CM9 of both version (plus Gapps loaded), all ended in the aforementioned bootloop. Have also tried fixed permission as well in between tries to load CM9.
Spent a bit more time on this and I am now on the unofficial CM10 (not that I am complaining ), but this is very strange to me. Has anyone ever experienced this? It seems that I have no way of getting back in CM9.
I was running cm9 nightlies until I flashed cm10 (which is amazing ) and had no issues with it what so ever :S
I don't think I've heard of any cases of what happened to you, happening elsewhere
I'd just stick with cm10
Happened to me, too. I solved the problem flashing a previous build of CM9 and a previous build of Gapps - it seems like Gapps was the problem.
After popping out battery, insert batt., start download mode, Odin flash Semaphore ICS kernel as PDA, re-partition unticked.
Enjoy
The Semaphore dev has a thread about this. A number of people have experienced what you say with a combination of different ROMs and kernels. Check it out on development thread
Sent from my GT-I9000 using xda premium
Cheers for the reply fellas. Will check out Semaphore. Interesting though as I've always thought "stock" CM9 was just easy as.
Hey guys, I've had my transformer for just under a year and love it to death, but for the last couple of days it has been giving me hell! I was running ARHD 3.4.1 with Guevor's ICS kernel (can't remember version, either 19.4, 20 or 21). Anyway, all was well until I changed to ARHD 3.5.1 and switched to raymanfx's harmony kernel to try it out. I couldn't get my videos to play on mxplayer, FC's on apps, random freezes and tablet kept randomly rebooting. So I reflashed ARHD 3.5.1 again, same, reflashed guevor kernel, same, updated CWM to Rogue XM Touch Recovery v1.5.0-R1, same. Finally used this method: http://www.theandroidsoul.com/update-and-restore-eee-pad-transformer-to-stock-ice-cream-sandwich/ to flash back to stock, no root, no nothing annnnnd... same! Same issues no matter what I try. So my question is, with a few weeks of ASUS global warranty left (bought it in HK so I can't take it back to 'shop') can/should I send it back now that it's flashed back to stock without them finding out I rooted it? Or is there something I'm missing that you guys can think of. Please let me know asap in case I do need to send it back. Thanks in advance. Oh and let me know if you need more info
Maybe a stupid question...
Did you do a factory reset in between flashing the different roms and kernels? Full factory reset, wipe cache and dalvik?
Not a stupid question at all, but yes, I tried all three
Sent from my R800i using Tapatalk 2
I can't think of anything else causing that behaviour. Restoring apps, data and system data with Titanium has been a source of trouble for me in he past. Restoring setCPU with profiles that don't work well with the new kernel for example. But I guess that's not the case here. At least stock ROM should be working.
Sorry, maybe someone else has another idea.
I am experiencing sudden shutdowns (or atleast non-responsive screen) quite often while on 4.2.2. For example, last night, the phone was at 89%. I went to sleep. When I woke up, the phone did not respond to the power button. I am not sure how long I pressed the power button (so I am not sure if I did a reboot or a boot) but the phone did not go to the lock screen, a (re)boot was required. I've had this since the day I had it (came on 4.2.1, currently running 4.2.2 stock).
When I did boot my phone back up, my battery was as indictaed in the screenshot. It was suddenly at 34%! I have no idea what causes this, but would much like to resolve this issue. I'd love to try a different kernel, but on the franco kernel (r82) I was unable to receive notifications (and thus missed alot of Whatsapp messages) unless I would actively turn on my phone with the power button.
I did google this problem but found no solution for me.
If you're using custom kernel, then post this kind of issues on kernel thread. If not then clean phone and stock reflash it.
Some mods (like the awesomeBEATS) breaks 4.2.2 so keep that in mind.
Adam
AdamLange said:
If you're using custom kernel, then post this kind of issues on kernel thread. If not then clean phone and stock reflash it.
Some mods (like the awesomeBEATS) breaks 4.2.2 so keep that in mind.
Adam
Click to expand...
Click to collapse
I have reflashed the custom ROM and kernel. So that can't be the issue.
I just posted this thread:
http://forum.xda-developers.com/showthread.php?t=2153860
Did you get a flashing white led?
As I was very sleepy when I woke up, I'm not sure, but there could have been one, yes!
Anyone ever experienced this? Is this RMA-worthy?
Edit: Just happened again, while I was whatsapping. I turn it on standby, want to turn it on 5 minutes later and I have to reboot it...
I have this problem since 4.2.2 on the nexus 5
Hi,
i'm using purity rom with purified kernel right now. as i read that many people using purity have better battery life with semaphore, i tried to switch my kernel. worked fine and my battery lasted longer, but i would get 5-10 random soft reboots during the day.
so i don't see the google logo on reboot and don't have to enter my sim pin.
this was and is no problem with purified kernel, but because of the battery life i would like to change to semaphore.
can i somehow fix this?