Database Develop

Nexus & laggy after 4.4 update

It was smooth before,now its so laggy...
anyone else have this issue?
I'm going to try a factory restore after I back my stuff up but if this is the way its going to be on 4.4 i'm going to be kind of :crying:

Try a clean flash and ull feel the difference, besides half of the apps u use are not optimized for KK so that might be the issue.
Remember after first boot tablet is laggy and services in the background will stop soon.

xateeq said:
Try a clean flash and ull feel the difference, besides half of the apps u use are not optimized for KK so that might be the issue.
Remember after first boot tablet is laggy and services in the background will stop soon.
Click to expand...
Click to collapse
yea im gonna try that,just gotta back up my pics and stuff.
whats that last phone in your pic(the nokia one). I remember it but cant remember the model #.

I guess I got lucky. Mine has been great since the update.

You need to wipe the device clean and begin from scratch. Mine runs better than 4.3 ever did, overall i think its great.

yep, do fresh stock install then 4.4 rocks
cr0wnest said:
You need to wipe the device clean and begin from scratch. Mine runs better than 4.3 ever did, overall i think its great.
Click to expand...
Click to collapse
+1
My 4.4 is great, I did a stock 4.4 KRT14S fresh wipe install, and then installed my apps and entered settings. It runs a lot better than 4.2.2 and 4.3.

yep, same results here! Laggy as hell, i did a backup using helium (as not rooted) to my pc of various game data then let the ota upgrade start, followed by a hard reset a.k.a. a clean install (me thinks??)
Google Play automatically then re installed my apps and settings (most of them!) Finally a restore of some apps and theme settings again using helium from my PC = slow, and getting various app and system crashes ever since...? #Disappointed
Sent from my Nexus 7 using xda app-developers app

nigelhealy said:
+1
My 4.4 is great, I did a stock 4.4 KRT14S fresh wipe install, and then installed my apps and entered settings. It runs a lot better than 4.2.2 and 4.3.
Click to expand...
Click to collapse
So how do I do "a stock 4.4 KRT14S fresh wipe install" ?

illingd said:
So how do I do "a stock 4.4 KRT14S fresh wipe install" ?
Click to expand...
Click to collapse
Many ways, the way I did was to http://www.wugfresh.com/nrt/ this, get drivers installed (once only and the most fiddly thing of all overall) and do "unlock" (once only), and then as I tried 4.2.2. , 4.3, 4.4, 4.4.1 and back to 4.3..... etc is "stock+unroot" then root. Then I copy supersu.zip to /sdcard to keep root on it if it loses root which it does in a few situations. e.g. 4.4 then root then installed Franco kernel lost root.
There is the adb sideload and other methods but once I got the WUGS NRT working, I stuck with that.
I now don't use any google backup/restore at all now, I just install what I want and configure myself. That way it is as vanilla as possible. A few APKS hard to get, I copy them onto fileserver I can access from anywhere.
I've done this with my N4 and N7 2012.

I want a responsive Note 3 without a new Rom

I don't have the time to constantly be looking for new roms to make my phone run properly. My phone is always freezing up due to the stupid Touchwiz UI and I absolutely hate it. I am sick and tired of my phone freezing up and lagging constantly and having to do factory reset and reinstalling all my apps fresh.
So I was wondering, what can I do to fix this problem in a easier manner? I was thinking about rooting the phone, saving all my app data, unrooting, resetting the phone, rooting again, uninstall bloatware, reinstalling apps with their data, and unrooting.
Here are my concerns though. I want to be able to reset the phone using the orignal factory reset. I don't have time or care to install new roms on my phone as I want to keep my warranty and I want to be able to sell my phone in the future.
So what are my options here? What can I do and what are my steps to start doing them?
I am on AT&T Note 3 with kitkat 4.4.2 with my build number ending in NC2.

Is the Note 3 development this bad? Not one response in a couple days. Anyone have a simple answer?
I just want to know if I can factory reset if I root my device and how I could complete unroot.

joshlete said:
Is the Note 3 development this bad? Not one response in a couple days. Anyone have a simple answer?
I just want to know if I can factory reset if I root my device and how I could complete unroot.
Click to expand...
Click to collapse
Simple answer is root with towelroot, and when you want to do a complete factory reset, flash stock NC2 using the guide in this thread.
I think your original question about what options you have is a little more complicated...rooting your phone technically voids your warranty, but if you're referring to the KNOX warranty flag then towelroot doesn't trip that flag. Reflashing stock NC2 with Odin will unroot your phone automatically so no worries there either. What I'm getting at is flashing roms isn't going to void your warranty any more than rooting with towelroot will, on the other hand uninstalling system apps can cause lots of problems, so you may find it easier to flash a near-stock rom that has the bloatware already removed.
But if you're set on not flashing anything, then I'd suggest using titanium backup to freeze any apps you don't want instead of uninstalling them. If you uninstall the wrong app you could end up having to do a factory reset anyway just to get your phone working again. Freezing system apps can cause problems too but it's generally easier to unfreeze an app than try and find and reinstall a system apk. And as tempting as it is don't uninstall My Magazine you'll get FC all over the place and your email won't work properly

So if I install that stock rom, would I be able to update my phone using the internal updater? I just want to be able to install Android 5.0 when/if it comes out for the Note 3. Seeing how AT&T note 3 has little to no roms to install. Very disappointing.

The Odin files in that thread are for stock NC2 and unless you flashed a rom after your second post you're still on stock...it's the exact same AT&T stock build...flashing it won't really benefit you at all unless you rooted and made changes to your system. I assume by internal updater you mean the OTA updates that get pushed out from AT&T then yes since that is the official AT&T build if you flash it you will still get those updates provided AT&T is your carrier. There may not be a lot of roms but the ones we have are great I'd encourage you to try one or two there are a couple "debloated" stock roms I think would give you what you're looking for in terms of stability but of course it's up to you if you just want to stay stock

joshlete said:
So if I install that stock rom, would I be able to update my phone using the internal updater? I just want to be able to install Android 5.0 when/if it comes out for the Note 3. Seeing how AT&T note 3 has little to no roms to install. Very disappointing.
Click to expand...
Click to collapse
Wow... just... wow.
This POST is disappointing.

I'm on the same boat as you OP. When time comes for a new phone, my next phone will never be another Samsung phone again. I will only consider phones that are close to stock. Most likely Motorola X or Sony Z3 Compact or similar.
TouchWiz is so disappointing. It's slow and creates lags even for just checking what time it is.
Fortunately I have some time so unlike OP, I tried debloating stock rom, tried at least 5 custom roms. Most of the custom roms have either too much theme customization (really not my taste) or something else doesn't work (NFC payment or deep sleep or some other thing). And they all claim super duper fast and rock stable, but those are hyperboles. The only time I experienced one rom being faster than the other was with Galaxy S5 port rom, but that was most likely due to the fact that standby mode is disabled because we have no way to update the firmware. In other words, uses more battery but still lasts a day. Also, I never seen the battery last exceptionally longer than the stock rom, so don't trust the super long lasting battery claims.
The easiest way to get your phone run smoothly is to factory reset it, and then only install select apps that you really need and know that it won't be a resource hog reporting your every move.
Oh, and last year's Moto X (dual core) feels faster than a quad core Note3 for everyday task in my hands. I wish we had a google experience rom for n900a.

brisinger08 said:
The Odin files in that thread are for stock NC2 and unless you flashed a rom after your second post you're still on stock...it's the exact same AT&T stock build...flashing it won't really benefit you at all unless you rooted and made changes to your system. I assume by internal updater you mean the OTA updates that get pushed out from AT&T then yes since that is the official AT&T build if you flash it you will still get those updates provided AT&T is your carrier. There may not be a lot of roms but the ones we have are great I'd encourage you to try one or two there are a couple "debloated" stock roms I think would give you what you're looking for in terms of stability but of course it's up to you if you just want to stay stock
Click to expand...
Click to collapse
Could you link me to some stock roms? I lost my game in rom finding and can't seem to get a good running/looking rom.
RErick said:
Wow... just... wow.
This POST is disappointing.
Click to expand...
Click to collapse
Most useless post of the year goes to......

joshlete said:
Could you link me to some stock roms? I lost my game in rom finding and can't seem to get a good running/looking rom.
Most useless post of the year goes to......
Click to expand...
Click to collapse
UR Droid is probably the closest to stock...Knox removed, sd card write permissions fixed, etc. are the only mods...that said carl's made a ton of flashable zips too so if you did want to start making mods yourself chances are you won't have any problems while running his rom
FireKat is one you've probably run across. That is a stock rom all of the mods/optimizations/etc mega makes are from other stock builds. There's no theming or anything like that it's more like "TouchWiz optimized"...again nothing extraneous added if you want to add tethering, call recording, etc you'll have to do it yourself. FireKat is geared towards speed and battery life but it's rock solid with no known issues. All of the rom updates you see are for performance improvements as opposed to the majority of the aosp-hybrid or heavily themed roms where updates are for bug fixes.
Both devs are really helpful and responsive definitely check out their threads though since I'm not up to date with both roms. I have flashed both of them at some point and both are significant improvements over stock...of course no one can tell you what roms you'll like or should flash but I'd be pretty surprised if you have a better experience on stock than either of these roms.

I've been running a stock rooted 4.4.2 for months and it was not laggy at all.
In the application manager settings I turned off all bloatware apps that I did not use. I froze (with titanium backup) all bloatware that could not be turned off in settings and also froze anything that says "knox" in the title. I used xposed installer to install many modules that allowed me to tweak my stock rom... including greenify to auto hibernate apps, smart booster to manage ram, boot manager, and also Wanam xposed for ui customizing...
My phone has run extremely well.
I just made the jump to 4.4.4 and got it rooted (thanks to @muniz_ri and a few others).... exact same setup again... stock rooted... turn off and freeze un-needed apps... xposed modules... and again it is running nice and smooth.
I also use nova launcher prime because it feels more responsive and does more things that I want (like a home screen that will autorotate to landscape mode).

Wow, that's a lot to have for being stock .
The only way to get rid most of your concerns is to root your phone. Then you can delete all other useless apps that you don't need and slow your phone down a bit.
But installing a new Rom is the best way to have a peace in mind I think. Dynamic KitKat is one of the best roms for our phone. I've been using it for months and there is nothing I can say how much I like it. Sometimes I experience lag, but that is to be expected because of Android's ability to do multitasks.
Just my 2 cents.

Randoom Reboots on Lollipop, multiple ROMs with the same issue

Ok, I have been searching for a couple of weeks now but I have not found a soulution. I recently recieved a replacement Note 4. I updated it to Lollipop, then rooted and flashed Rapture.
Ever since, I have been experiencing random reboots and the occasional loss of data. This is not a Rapture problem it appears. I have had the issue with both versions of the Rapture Lollipop builds, DarthStalker, and stock Deodexed COD6. I did not have this problem on my last Note 4 which had the first Rapture build on it.
I have factory reset, I have Odined back to stock and repeated the rooting process, following the guides posted here to the letter and I still have the problem. Any help in resolving this issue is greatly appreciated.

KingBeef said:
Ok, I have been searching for a couple of weeks now but I have not found a soulution. I recently recieved a replacement Note 4. I updated it to Lollipop, then rooted and flashed Rapture.
Ever since, I have been experiencing random reboots and the occasional loss of data. This is not a Rapture problem it appears. I have had the issue with both versions of the Rapture Lollipop builds, DarthStalker, and stock Deodexed COD6. I did not have this problem on my last Note 4 which had the first Rapture build on it.
I have factory reset, I have Odined back to stock and repeated the rooting process, following the guides posted here to the letter and I still have the problem. Any help in resolving this issue is greatly appreciated.
Click to expand...
Click to collapse
Seeing that it's happening on so many different Roms; it's something you're installing on your device.
Does it happen on a fresh stock rooted COD6 with nothing installed 3rd party?

I have not tried a stock run without third party apps installed. I will try a fresh install of stock COD6 with root and see how that fairs. It normally happens the first time within an hour of flashing so it won't take long to see if it happens I believe.

I was getting one or two random reboots a day after updating to LP. I noticed most reboots happened after I finish or during use of Google All Access. I have a lot of tracks stored on my SD cards. Once I refreshed the tacks [in all access settings], I haven't has a reboot since.

Jammol said:
Seeing that it's happening on so many different Roms; it's something you're installing on your device.
Does it happen on a fresh stock rooted COD6 with nothing installed 3rd party?
Click to expand...
Click to collapse
So I tried stock rooted without third party apps installed. Got 2 reboots but no loss of data. Seems like it's something with the device itself or should I try just running without root?

dkb218 said:
I was getting one or two random reboots a day after updating to LP. I noticed most reboots happened after I finish or during use of Google All Access. I have a lot of tracks stored on my SD cards. Once I refreshed the tacks [in all access settings], I haven't has a reboot since.
Click to expand...
Click to collapse
I wish it was something that simple. The only consistency I am getting in terms of reproducing it is trying to multitasking and possibly having too many apps running in the background, but sometimes it happens with just 2 or 3 apps running so I am not sure.
What's really annoying about it all is the first unit I had ran flawlessly, even after the 5.0 update.

KingBeef said:
I wish it was something that simple. The only consistency I am getting in terms of reproducing it is trying to multitasking and possibly having too many apps running in the background, but sometimes it happens with just 2 or 3 apps running so I am not sure.
What's really annoying about it all is the first unit I had ran flawlessly, even after the 5.0 update.
Click to expand...
Click to collapse
Does your device get really hot right before it does the random reboots? Could be thermal function of the Note 4. 805SOC is a very hot chip albeit not as bad as the 810 but pretty dang close if you ask me!!! If no heat issues then see below
Give this a try:
This will require you to Odin to COD6 Stock NO ROOT!!!
Shut down and take out your External SDCard.
Boot into TWRP or Flash TWRP if you don't have it on there right now
Do a FULL WIPE: Factory Reset 3x, Advanced Wipe(Everything there) 3x, and finally Format Data(where you have to type yes) 3x
Power off your device and start it up into Download mode and Odin COD6 Stock Firmware(the full one not the partial)
Let it do it's thing and then simply use the device for a few hours on just pure stock.
DO NOT INSERT YOUR SD CARD!!! Why? We want to make sure it isn't something on your card causing Indexing to hang and force reboot.
If you get no reboots then go ahead and shutdown and insert your SDCard and use your device. Still no reboots? Then go ahead and Root. Still no reboots? It's resolved.
This process of elimination is lengthy but it is effective.

Jammol said:
Does your device get really hot right before it does the random reboots? Could be thermal function of the Note 4. 805SOC is a very hot chip albeit not as bad as the 810 but pretty dang close if you ask me!!! If no heat issues then see below
Give this a try:
This will require you to Odin to COD6 Stock NO ROOT!!!
Shut down and take out your External SDCard.
Boot into TWRP or Flash TWRP if you don't have it on there right now
Do a FULL WIPE: Factory Reset 3x, Advanced Wipe(Everything there) 3x, and finally Format Data(where you have to type yes) 3x
Power off your device and start it up into Download mode and Odin COD6 Stock Firmware(the full one not the partial)
Let it do it's thing and then simply use the device for a few hours on just pure stock.
DO NOT INSERT YOUR SD CARD!!! Why? We want to make sure it isn't something on your card causing Indexing to hang and force reboot.
If you get no reboots then go ahead and shutdown and insert your SDCard and use your device. Still no reboots? Then go ahead and Root. Still no reboots? It's resolved.
This process of elimination is lengthy but it is effective.
Click to expand...
Click to collapse
I can't say that I have noticed it in the past, however, it froze up shortly after I read the email notification of your response and was quite warm towards the top half. I pulled the battery expecting it to reboot anyway. Is there anyway to mitigate the thermal affect if it is indeed the culprit?
I will try the second method this evening and see if there's any change in behavior and report back sometime tomorrow. Thank you for your assistance with this.

KingBeef said:
I can't say that I have noticed it in the past, however, it froze up shortly after I read the email notification of your response and was quite warm towards the top half. I pulled the battery expecting it to reboot anyway. Is there anyway to mitigate the thermal affect if it is indeed the culprit?
I will try the second method this evening and see if there's any change in behavior and report back sometime tomorrow. Thank you for your assistance with this.
Click to expand...
Click to collapse
Yes but it is not recommended. Using Synapse from the playstore will do such a thing but it requires a custom Kernel. If it is a thermal issue your device may be defective seeing that it's spiking so much so quickly and just crashing.
Definitely give the process of elimination a try that I suggest in my previous post. If it fails at the first step of being pure stock no SDCard then I'm afraid you need a new device.

Hi KingBeef,
Unfortunately, I have the exact same issues you do. Except I've tried literally everything. Even Odin back to stock KitKat. Seems to reboot or randomly shut off if more than 3-4 apps are running at completely random times. No SD card as well to confirm it's not that. The only difference I see with your situation is my phone will degrade after 3rd day of use. First 2 days are flawless, then almost like a failing hard drive, things start to domino progressively worse. My last attempt was to run it only in wifi mode, no SIM card.
The only thing left is to consider unfortunately is swapping again under warranty. I myself am waiting until I go back to the US (Cad user here) to swap with TMo for another handset.
Good luck!
Sent from my D6503 using Tapatalk

How to replace stock rom and reclaim all that space?

I never want to touch the stock rom again, how do I make the most of my xt894?
Sent from my XT894 using Tapatalk

mirddes said:
I never want to touch the stock rom again, how do I make the most of my xt894?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
install the Rom you want on stock slot
Sent from my KFFOWI using Tapatalk

Its that easy?
Because I installed safestrap on the stock rom, does it not get deleted when I wipe the stock rom?
Sent from my XT894 using Tapatalk

mirddes said:
Its that easy?
Because I installed safestrap on the stock rom, does it not get deleted when I wipe the stock rom?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
safestrap will replace needed files as long as Rom on stock slot is compatible.
Sent from my KFFOWI using Tapatalk

What sort of rom would not be compatible? I would like to use a overclocking 12.1 rom. Unless there would be a significant advantage to using 4.4.4 (overclocking of course). A link to list of differences in features between 4.4.4 and 5.1.1 would be great, then I can make my own mind up without trying both (kinda leaning towards 4.4.4 as I've not tried it, 4.1.3 stock had minimal lag in safe mode and the process limit doesn't seem to stick to a limit of 2, reverts back to no limit as often as I change it. Adblock plus also seems to be less than flawless, much less than flawless. Perhaps there is add injection occuring somewhere however they [adverts] are rather offensive.
Sometime I get huge lag spikes that should never happen on hardware of this caliber unless significant lack of optimization exists.
Sent from my XT894 using Tapatalk

mirddes said:
What sort of rom would not be compatible? I would like to use a overclocking 12.1 rom. Unless there would be a significant advantage to using 4.4.4 (overclocking of course). A link to list of differences in features between 4.4.4 and 5.1.1 would be great, then I can make my own mind up without trying both (kinda leaning towards 4.4.4 as I've not tried it, 4.1.3 stock had minimal lag in safe mode and the process limit doesn't seem to stick to a limit of 2, reverts back to no limit as often as I change it. Adblock plus also seems to be less than flawless, much less than flawless. Perhaps there is add injection occuring somewhere however they [adverts] are rather offensive.
Sometime I get huge lag spikes that should never happen on hardware of this caliber unless significant lack of optimization exists.
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
every Rom that was built in the last 2 years should be compatible with safestrap, and can be installed on stock slot. just be sure not to reboot if you get errors when installing.
http://forum.xda-developers.com/showthread.php?t=3181430
Installing and using Safestrap 3.75 (2015)
Sent from my KFFOWI using Tapatalk

7jkKok terrible stuff happened.
I wiped the stock slot and booted back into slot1. worked fine
went in with the latest nightly and it failed so I did an advanced wipe of ./system and fell asleep flashing 0907 (the sam rom that's running on slot 1) woke up to an un happy android symbol on my phone. safestrap seems to be gone and I can access the recover options as per the guide at
droidforums.net/threads/how-to-restore-your-motorola-droid-4-xt894-to-stock-windows-only.206972/
the "Decompress And Start Flashing" option is greyed out.
please advise, my phone is a partial brick until remedied

mirddes said:
7jkKok terrible stuff happened.
I wiped the stock slot and booted back into slot1. worked fine
went in with the latest nightly and it failed so I did an advanced wipe of ./system and fell asleep flashing 0907 (the sam rom that's running on slot 1) woke up to an un happy android symbol on my phone. safestrap seems to be gone and I can access the recover options as per the guide at
droidforums.net/threads/how-to-restore-your-motorola-droid-4-xt894-to-stock-windows-only.206972/
the "Decompress And Start Flashing" option is greyed out.
please advise, my phone is a partial brick until remedied
Click to expand...
Click to collapse
wiped stock have how?
RSD Lite version?
use decompress only
Droid 4: Flashing XML/Firmware with RSD Lite http://youtu.be/CM3XjZT80m0
Sent from my KFFOWI using Tapatalk

Vs most KitKat ROMs, CM12.1:
Is subject to random slowdowns, due to memory management issues and outright lack of memory (can be remedied to a point via Joojoobee's kernel and aggressive minfree settings), limited overclocking (KK-based ROMs have access to the JBX kernel and its exotic voltage controls, enabling higher overclocking limits), and just because (the cause hasn't quite been pinned down yet)
Is easier on the battery at idle due to less Play Services wakelocking (note: Play Services can be toned down in KK as well, but you lose some functionality like automated mail pushes and such)
Is more modern, some apps need Lollipop APIs
Has some features that rely on Lollipop APIs (as far as I know, anyway), such as Motodoze for pocket/wave detection
If you don't specifically want Lollipop stuff like Motodoze, the better Play Services, etc, go with a KK ROM. I've always been fond of SlimKat, myself, but whatever ROM you choose it will run well more consistently than CM12 does.
If you're still set on CM12, once you get the phone back to factory condition, try flashing CM11 first, then CM12 on top of that. CM12 wasn't intended for use in the stock slot, so going straight from stock JB to it causes...oddities. Used to, anyway, CM12 might contain the same stock-slot housekeeping stuff as CM11 these days.

[Q] Android Process FCs and General Device Instability After Flashing MMB29V

Hello all. Generally I've been able to troubleshoot all my Android issues on my own. Most of the time someone has had the same problem (amirite?!). However, I'm stumped and could use a little help from the community.
I've been going along on Marshmallow with FK as my kernel. Generally, waiting a bit to take an update til SuperSU was confirmed all working correctly and that there wasn't any surprises. I had been putting off the MMB29V update for a bit just because everything was running fine and I had no real reason to upgrade. Well, one day I started getting a few FCs and things seemed a bit off performance wise so I decided that I'd go and move on to the next release.
Now, since I've had my N6 I really haven't had the need to run a custom ROM which is completely unlike my old habits on the S3. I decided that it's been a while since I've checked out AOSP so I flashed MMB29V using the batch file with no issues and then DU and their recommended GApps. Here's the first hint of an issue. When I loaded up the OS for the first time I got acore and phone FC's constantly. I instantly thought that I didn't wipe something or that I had a bad zip. I re-downloaded everything and checked MD5s. Everything looked good and after the flash I was able to get through the setup wizard without any issues. As I was sitting there checking out the tweaks and options available I started getting FCs again. It seemed related to Google apps. I did the whole process a second time and still had the same issues. Basically it seemed like at some random point in time the FCs would come and then shortly after the device would be highly unstable. I'd get random reboots, etc. Looking at the stack traces the errors seemed like odd NPEs and native errors.
I decided that AOSP wasn't going to cut it right now if I was going to have a relatively unstable phone and went to flash completely back to stock. Much to my surprise I still got the same errors! Apps like Feedly would never even be able to open. They would just FC on launch. The device hot reboots. The phone process seems to crash during most calls. I triple checked my MD5 on the download from Google. Made sure I wasn't doing something super stupid. I even tried doing the factory flash, booting to the welcome screen, then powering down, going to stock recovery, and factory resetting before continuing. All the same errors.
I've flashed back to complete stock a few times before without any issues. I've been able to flash system.img without any issues. Now it seems like the phone is completely unstable no matter what I do. I get the "Your device is corrupt. It can't be trusted and may not work properly." (red) message when doing a cold boot.
So... What gives? Am I completely blanking on a step here? Is it possible that I have a hardware issue that is corrupting stuff (I've suffered a bad DIMM before in a desktop and it was mind numbingly frustrating)?
I've burned through two backup cards of Google 2-Step backup codes! I'd really like to figure this one out!

mikejr83 said:
.
So... What gives? Am I completely blanking on a step here? Is it possible that I have a hardware issue that is corrupting stuff (I've suffered a bad DIMM before in a desktop and it was mind numbingly frustrating)?!
Click to expand...
Click to collapse
You could read the OP of the following thread and flash a debloated and prerooted ROM.
http://forum.xda-developers.com/showthread.php?t=3059493

I guess I'll try that. I'm still scratching my head why a flash from the factory image is still suffering from FC's and general instability. It also concerns me that I get the corrupted message at boot. It would be one thing if I flashed factory, then put a recovery, kernel, and rooted, but I haven't done that.
Hopefully I'll get a chance to try that this evening. Thanks for the link to that image. It's pretty much what I run when I take an update.

N, n, ne, necromancy!
I brought this thread back to life because I've never been able to solve the instability issues since my last post back in March.
Having some free time lately I decided to nuke my device and start again. I first grabbed the latest stock image and flashed stock. Then I downloaded the latest TWRP and Dirty Unicorns and decided that I'd give it a whirl again. I had FC issues right after the first go at it. I decided to try another GAPPs and do it again. I was able to get through setup. It took a few hours but the FCs started again.
I decided that I would try factory resetting the device and then starting a setup. I remembered that on my previous devices that I sometimes would have to do an immediate factory reset after flashing.
Well that did crap. FCs are random. The device is stuck booting now after a hot reboot.
How can I debug this? What do I need to grab from a logcat? Is there a way to run something like memtest to see if there is a bad section of RAM and something against storage to see if there is a bad sector?
This is frustrating as hell!