running CM for n7105 on my ATT Note II. have been for several months. it's been pretty tight.
keep yesterday's update (the 12th). it tried flashing today's nightly, 13th, several times and it boot looped every time. had to go back to yesterday's. i wonder if i have a corrupt download or if it's a bug they already know about?
-peter
Looks like a bug, im having same problem and there is one guy on developer topic saying that he has boot loop also.
Related
I just flashed the latest version of CM 10.1 about an hour ago. It had randomly rebooted probably 10 times. Please help!!!
What rom did you come from, how did you flash this one and what gave you tried to do to fix it so far?
Hi there! I´ve got some issues with my gnex lately: I clean installed PA 3.99. Every went well for a couple of Days, including turning on and turning off the phone.The one strange thing happend. I installed an app, baammm, first reboot. Hm. Phone came up quickly, then baamm, second reboot. From then things went downhill... Stuck at Google-Logo. Had to pull Battery. Factory reset.
Now, everytime I boot the phone it is stuck at the Google-Logo. I have to install the ROM again and then it boots up. One time. I flashed the latest bootloader, which did not help.
Any ideas?
ive got this problem as well. probably worse.
ive got the latest nightly of carbon installed.
however once i reboot it is stuck at the google logo!!!!
im not sure if i need the latest bootloader or if im missing soemthing!
i came from a 4.2.2 rom .
astarman said:
ive got this problem as well. probably worse.
ive got the latest nightly of carbon installed.
however once i reboot it is stuck at the google logo!!!!
im not sure if i need the latest bootloader or if im missing soemthing!
i came from a 4.2.2 rom .
Click to expand...
Click to collapse
Yeah, pretty bad. At the weekend maybe I'll try to flash stock factory image. Hope that helps. But I've seen some things here at the forum. I'm slightly scared...
Sent from my Galaxy Nexus using xda app-developers app
Is there anybody out there that can help?
I've had a SGN for over two years and it seems like I have always had problems with it. I've been through mulitple SIMS, devices, ROMS, and various apps. Most recently, I had to get a new device. It took several steps of troubleshooting, but I finally rooted the phone. Got Rootchecker Pro and was able to confirm with no errors. For a while now, when I wipe, CWM skips over Android_Secure because it can't be found. About a month, after rooting the phone, I flashed the CRDroid (based on Cyanogenmod) ROM. It was then that I would get bootloops after checking on the Mobile Networks setting. It didn't always do it right away. When it didn't restart immediately, I wouldn't be able to make phone calls. Shortly after, I went through the Developer Options and updated to CM 10.2. The Mobile Network Bootloops stopped and I thought everything was great. But, there has been about three times that the phone will randomly restart and go into a bootloop at the CM splash screen. It's happened a couple times randomly and yesterday after taking about 45 pictures over a 45-minute span.
Luckily, I've been much better about making Nandroid backups and it hasn't been a big deal to restore. You can imagine, though that it is incredibly annoying and critical sometimes. I've been trying to rack my brain about what is consistent about the bootloops and can't figure it out.
It's a Toro with CM 10.2 on 4.3 Android. I flashed Golden Kernel and PA 4.0 GAPPS.
I would love to see what everybody thinks the problem could be. Thanks again.
Hello guys,
I have some issues while using the latest 4.4.2 DN3 ROMs. Before installing DN3 4.2 I flashed MJ5 bootloader, and it was running for a couple of weeks fine, then the phone started to freeze and reboot several times a day. I thought DN3 v5+ would fix these freezes and reboots but it was no good. I was really disappointed, as I really liked the look and feel of DN3. Now I'm using Revolution HD 31, it's stable (more or less, a couple of freezes and reboots for two weeks) and fast, but I really liked the looks of the latest DN3...
So the question is - what can I do to avoid these freezes and reboots and will upgrading the bootloader to a newer one will help me?
I don't think bootloader has anything to do with it. I was on MJ5 with 4.3 creikelo and NEVER had a reboot or force close. DN3 just freezes after 1-3 days. I had the same experience. It started getting laggy, or better said, the CPU was doing something, hence the lag, and then it just restarted by itself. And I did clean install. It is enough to reat the DN3 topic and see how many people have problems with it - and most still consider it the best ROM... I just went away to another ROM, and will post results in a week hope it doesn't behave the same as DN3
Thanks for the reply!
What ROM did you install? Is it stable?
I had a problem with mj5, my phone froze on the boot and i had to reinstall the ROM.
I think mj5 is for 4.4.2 ROMs, is a older bootloader.
brainstormer911 said:
Thanks for the reply!
What ROM did you install? Is it stable?
Click to expand...
Click to collapse
I tried JellyKat 6.7, but seems I have same issue... at first it was getting high CPU usage after a day or two, then phone became so overloaded it reacted to nothing and I had to pull battery out. Then all of a sudden I started getting SOFT reboots (that means only from the point of boot animation, no samsung screen) and I installed Xposed module Samsung Crash Fix and will see if it helps... I dunno, I am begining to believe there's something wrong with all 4.4.2 ROMs Because I never ever had FC, crash or reboot with 4.3 Criskelo....
The last few nightlies have caused bootlooping, and I have reverted to my last backup of 10-15. Yesterday I worked out that after installing the 10-21 nightly (and bootlooping) I could restore just the /boot partition from 10-15 and it booted normally. Today I installed the 10-22 nightly and it bootlooped again (and worked after restoring /boot). So the nightlies appear to be modifying /boot as well as /system, and not in a good way for my Note 8 N5110. I'm using TWRP 2.7.1.0.
Any ideas how to fix this?
Greg
bump
I am having the same issue. I had the 20141008 rom to go back to so not a huge deal.
More detail
I went back to my last backup and then flashed the nightlies until I found the change. 10-17 works well and 10-18 boot loops. The changelog shows half a dozen changes to the Exynos 4412 kernel on that day, so one of them borked the Note 8.0.
I have tried everything I can think of to get these to work. I went back to TWRP 2.6.3.0, unplugged the battery, wiped cache and various partitions, all to no avail. I can't say definitively that it isn't something on this end but it is looking increasingly unlikely.
My brother also has a Note 8 and he has not had these problems. But he is using Ryukiri's custom draco kernel, not the one included in the nightlies, so that seems to confirm the source of the problem is the kernel, and specifically the changes made in the 10-18 nightlies..
Originally I thought this might be a general Omnirom issue but clearly at this point it is Note 8.0 specific. So this thread should probably be relocated to the Note 8.0 forum...
Fixed and will be available shortly
Thanks to Ryukiri for fixing the kernel problem.:highfive:
The patch has been merged and should show up in the 11-4 nightly. Watching intently...
Greg
I can confirm now that 11-04 nightly is booting properly.
Thanks again Ryukiri.
Greg