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
Related
Hello everyone. I'm pretty new to rooting and flashing ROMs and everything. I was playing with my buddy's rooted Incredible (CM 6.0.1) and I was amazed. I just recently rooted my Incredible and flashed a couple different versions of CM with the same outcome. My phone freezes and then reboots randomly after a couple minutes of it being on. I've tried wiping and restoring factory settings, wiping the cache and wiping calvik. I also tried clearing the storage and then flashing the ROM with no luck. Is it possible that CM just doesn't work with my Incredible or is there any possible way to fix the constant reboots? I apologize in advance if this has been covered already. Thanks!
Yes, I had the exact same problems. Impressed with the features, but disappointed with stability. I switched for now to VirtuousROM and have been happy. Also, check forum.cyanogenmod.com. Several people facing the same problem.
Is it just by chance that it's so unstable? My buddy has been running CM 6.0.1 for awhile now with no reboots at all. In any case, thanks for the info. I'll give the cyanogenmod forms a try.
If I recall, CM 6.0.1 had a default overclock of 1.15 which some phones can't handle. But CM 6.0.2 restored default setting to 998 (stock), which should solve the problem!
I tried both CM 6.0.1 and CM 6.0.2 and both had the same results. They both of them did the freeze and reboots over and over again.
I've had great luck with CM nightly builds starting from 9/6 which was released after 6.0.2. I'm currently running the 9/8 nightly. If you decide to try a nightly, do a full wipe first.
Don't feel alone I have struggled with cm as well. Im using. 92 hboot 2.15 radio and still get splash freeze and reboot upon install. I have wiped: data,cache& dalvik...still no success. Any help.would be great. I've tried almost all nightlys rc3 6.0 6 6.1 6.2.
Sent from my ADR6300 using XDA App
Do I need the sd-ext partition to run CM? When I go to wipe everything it always returns with the message "sd-ext partition does not exist" but it still wipes everything else. If so, how do I go about creating that partition? Thanks for all the help.
kirkland signature said:
Do I need the sd-ext partition to run CM? When I go to wipe everything it always returns with the message "sd-ext partition does not exist" but it still wipes everything else. If so, how do I go about creating that partition? Thanks for all the help.
Click to expand...
Click to collapse
You don't need the sd-ext partition. I would download set-cpu, you can find it free on xda, and make sure that it is not overclocking for you.
I purchased set cpu....how would I tell if my cpu is over clocked?
mine is set to 998 max 245 min....still cant install cm6
Has any one found the same install issues as myself.....Ive been trying for at least a month to two months to get cm6. Just tried again tonight got the nightly to work once ...i rebooted and gota stupid bootloop. I tried to install again and just a bootloop this time. Please help!
Hey all,
I've been running CyanogenMod 10.1.3 (Stable) since it came out, and used the Nightlies for many months prior to this.
I recently decided to try the CM 10.2 nightlies, and successfully booted into CM 10.2-20131107. I let Google play restore my apps, and then decided to run "Fix Permissions" and reboot for good measure, however my device was stuck in a boot loop (Google screen with lock) for approximately 10 minutes, before I decided it definitely wasn't going to boot.
This is the second time this hapoened, the first time being with an earlier 10.2 nightly. I assumed it was an issue with that build, but ive found no other reports of my particular issue (I apologise if I am wrong about that, its hard to know exactly what to search for!)
Prior to install, I wiped everything (System, Dalvik Cache, Cache, Data and data/media) for good measure.
I use TWRP.
Does anyone have any idea what the problem might be? I've wiped everything, and gone back to 10.1.3 now with no issues, so at least I have a functioning device.
All I wanted was natively supported TRIM..
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.
everything was ok till 22 december build...it started from 27 december build
earlier every lollipop rom worked fine on my n7100.
i dirty flashed 27 december build on 22 december build..it started rebooting randomly.
i wiped everything and flashed again it also showed same error and the rom was rebooting as soon as the screen turns off
after that i have tried every lollipop rom out there even every build of cyanogenmod 12 but it is showing same problem and rom in unusable. I was also using agni kernel on that rom and titanium backup. The phone reboots as soon as the screen turns off and the cyanogenmod logo appears. I have also tried wiping internal storage 3 times but no success.
I seriously want to use 5.0.2. Came from dn4 which worked awesome. using TWRP 2.8.4.0 Earlier i also used multirom twrp when everything was working fine.
Thanks in Advance
ritikbanga said:
everything was ok till 22 december build...it started from 27 december build
earlier every lollipop rom worked fine on my n7100.
i dirty flashed 27 december build on 22 december build..it started rebooting randomly.
i wiped everything and flashed again it also showed same error and the rom was rebooting as soon as the screen turns off
after that i have tried every lollipop rom out there even every build of cyanogenmod 12 but it is showing same problem and rom in unusable. I was also using agni kernel on that rom and titanium backup. The phone reboots as soon as the screen turns off and the cyanogenmod logo appears. I have also tried wiping internal storage 3 times but no success.
I seriously want to use 5.0.2. Came from dn4 which worked awesome. using TWRP 2.8.4.0 Earlier i also used multirom twrp when everything was working fine.
Thanks in Advance
Click to expand...
Click to collapse
This is not true for me.I have tried almost all the Lollipop ROMs since their first release.Now I am with the Resurrection Remix 5.3.2 dated 27.01.2015.I have not experienced any random reboots till this date.Most of the time while flashing new ROMs I was doing full wipe and Factory Reset.Once I installed Agni Kernel.After that when I shifted to another ROM I lost my IEMI. Flashing stock ROM couldn't restore it.Hence I went to Samsung Service Centre.They said that the Mother Board has to be replaced which which will cost Rs.7000.00 (apprxly 75..00 USD).So I went to a private technician and he restored the IMIE at a cost of merely Rs.250.00(apprxly 4.50 USD).Thereafter also I shifted to many Lollipop ROMs without any issues.But I never installed Agni since then.I am sticking with the kernels came with those ROMs.
pnsdhrn said:
This is not true for me.I have tried almost all the Lollipop ROMs since their first release.Now I am with the Resurrection Remix 5.3.2 dated 27.01.2015.I have not experienced any random reboots till this date.Most of the time while flashing new ROMs I was doing full wipe and Factory Reset.Once I installed Agni Kernel.After that when I shifted to another ROM I lost my IEMI. Flashing stock ROM couldn't restore it.Hence I went to Samsung Service Centre.They said that the Mother Board has to be replaced which which will cost Rs.7000.00 (apprxly 75..00 USD).So I went to a private technician and he restored the IMIE at a cost of merely Rs.250.00(apprxly 4.50 USD).Thereafter also I shifted to many Lollipop ROMs without any issues.But I never installed Agni since then.I am sticking with the kernels came with those ROMs.
Click to expand...
Click to collapse
but i am getting these issues
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage. But none of these roms allow the T800 boot to get beyond the initial splash logo screen. I am using latest TWRP, 3.1.1 to wipe and install rom. I am not getting any install errors. Boot loader is confirmed as CPK2.
FYI, I am able to get back to the samsung rom by reflashing it with Odin.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
mach281 said:
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
Click to expand...
Click to collapse
My wife has the US Cellular 10.5 variant (T807R4). It was freezing so frequently it had become almost unusable for anything but watching videos. Rooting and disabling most of the Samsung apps did not fix the problem. I wiped the system with TWRP only to discover that none of the custom ROMs would work on this model. I downloaded and flashed the stock Samsung MM firmware (and it sat on the opening splash screen for at least 15 minutes before it finally booted up) and for the hour I used it after setting it up, I had no problems. I had previously cleared the cache with Titanium Backup and that also seemed to be a temporary fix. My conclusion is that something is happening when the cache fills up that causes the freezes but I'll need more data to say that for sure.
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
mach281 said:
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
Click to expand...
Click to collapse
Please explain the steps to install 7.1.2 (and which ROM you used) and update on the freezing issue. Most of the freezing issues I have read about seem to be on LTE variants (SM-T807x) so I was about to buy a wifi only (T800) tablet, thinking that would be a solution to the problem. If that's not the case, then I shouldn't waste my money.
The instructions for installing a non-stock ROM are on the dev's host page in Tab s forums. I first tried Resurrection Remix and now am on LineageOS. It was only after I wiped the internal storage area that I was able to get past the 7.x.x boot screens.
I found the stock rom 6.0.1 freezing issue persistent. I believe the problems started for me with XAR H4 and really picked up with K2 (roms supplied by sammobile). The tablet would frequently just freeze while working in an app: the screen and hardware buttons would not respond at all. Never had that problem with Android 5. The only thing I was able to do to unfreeze it was to reboot into download mode then restart the OS from there. I sometimes found that if I left it frozen overnight it would unfreeze itself by morning.