Database Info

no keyboard on nexus s

I recently bought a nexus s and once rooted the keyboard dissapered. It was fine until i flashed a rom unsuccessfuly, then turned the phone off. Once turned back on the keyboard was no more. If anyone could help me find a zip. to flash or a way to put a new keyboard on the phone I would appreciate it. the phone is basicly useless without the keyboard now, ive tried recoving to factory condition, flashing from an earlier point, and so forth. Please help!!!

You probably didn't flash gapps, you can find them on www.goo.im
Sent from my Nexus S using Tapatalk 2

jojoost said:
You probably didn't flash gapps, you can find them on www.goo.im
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
i never knew keyboard was in Gapps, i thought it's included in all ROMS since its absolutely necessary as the OP stated.
here is a dump
UPDATE: uploading
---------- Post added at 11:36 AM ---------- Previous post was at 11:33 AM ----------
Billchen0014 said:
i never knew keyboard was in Gapps, i thought it's included in all ROMS since its absolutely necessary as the OP stated.
here is a dump
UPDATE: uploading
Click to expand...
Click to collapse
Dictionary http://db.tt/3echUtSP and IME: http://db.tt/EUAXXcsR

re: i flashed gapps
Sent from my Nexus S using Tapatalk 2[/QUOTE]
I flashed a gapps zip from the site you linked me to and now when the phone turns on it says setup wizard is not responding and give me the option to force close. Nothing happens from that point its just stuck in a force close loop. I hope to god i didnt brick this thing. Is there a way to fix this problem? I didnt backup before flashing gapps and ive tried to restore the phone and wipe it clean but no luck. Any help would be greatly appriciated because i just got the phone, mainly to use it as a fun project seeing as smartphone customization has become my new hobby, and Im usually very good at it but now I am just afraid ive bricked the phone and I bought it unlocked so i paid a fair amount of money for i. Please help if there is a solution. Thank You,

Do you still have access to CWM? Can you make a clean install of any ROM? Wipe dalvik, cache, factory reset, format boot, system, data, cache and install ROM.
Download another ROM (and follow instructions from OP) which is not the one you initially had problems with (or download again - might be a corrupt zip file).

Thank you
Oogway13 said:
Do you still have access to CWM? Can you make a clean install of any ROM? Wipe dalvik, cache, factory reset, format boot, system, data, cache and install ROM.
Download another ROM (and follow instructions from OP) which is not the one you initially had problems with (or download again - might be a corrupt zip file).
Click to expand...
Click to collapse
Thank you very much, I followed and executed your instructions and now im running ice cream sandwich 4.0.4. not bad from going from almost a bricked phone to running one of the best versions of android. I downloaded offical roms this time instead of custom ones, first a version 2.3.4 and a 4.0.3, flashed the ics rom first and worked like a charm. Thank you very much, even got an update 5 min after i flashed the rom. You saved me 200$ and the embaracement of having a worthless phone. Im sure ill have more questions in the future, so glad there are ppl out there with the same passion for smartphone customization that i have. Much obliged. Omar

Re: [BeanStalk][1.179] Phone freezes after call

Re: [BeanStalk][1.179] Phone freezes after call
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app

bretcb said:
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over

qkster said:
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over
Click to expand...
Click to collapse
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.

bretcb said:
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.
Click to expand...
Click to collapse
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.

qkster said:
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.
Click to expand...
Click to collapse
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.

bretcb said:
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.
Click to expand...
Click to collapse
yeah...for the most part, while in cwm, factory reset, wipe system, data, cache, dalvik and then flashing a new rom work very well.
occasionally, for what ever reason that i'm not sure, going back to stock..changing file system back to rfs and then changing back to ext4 may be needed to fix certain problems...not common and not routine practice, but is needed...at least imo

OK, fair enough. I will read up more on going back to stock so I'm not unfamiliar with it. Which tool do you prefer?
For completeness of troubleshooting info for anyone else who may be reading, I received a phone call yesterday while the lock screen was disabled, and the phone still froze after the caller hung up. I received another call today, and made sure I hung up first, and no freeze, my phone was fine.
Sent from my SGH-I997 using xda app-developers app

bretcb said:
I will read up more on going back to stock..
Which tool do you prefer?
Click to expand...
Click to collapse
Everyone has their own prefs...I prefer heimdall. It doesn't matter. Whatever it takes to get the job done. You prolly should buy a usb jig too.
http://forum.xda-developers.com/showthread.php?t=1437548

Flash Kernel

So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.

Cobinator said:
So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.
Click to expand...
Click to collapse
I see that I have the Cyanogenmod Kernel installed currently which I suppose either is installed with Slimbean or it may have been installed because I tried the CM10 rom first, but it wouldn't boot.

what are you doing before flash the new rom?

juancaperez2000 said:
what are you doing before flash the new rom?
Click to expand...
Click to collapse
Wiping the device. Always best in the long run.
Sent from my Nokia RinGo far far away...

Well when I originally rooted and flashed the device it was brand new out of the box. Even then the only custom rom that I could get to work was Slimbean.
Pretty sure I tried all the other custom roms listed here:
http://forum.xda-developers.com/showthread.php?t=1850506
I have installed Slimbean a few time because I started getting errors, and keyboard kept crashing and things like that. I always wipe cache, and dalvik cache.

Cobinator said:
So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.
Click to expand...
Click to collapse
Restore your stock rom format internal memory and flash clean rom ASAP brother you will be straight !!!
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 05:45 PM ---------- Previous post was at 05:44 PM ----------
And all the necessary wipes of course
Sent from my SCH-I535 using xda app-developers app

Cobinator said:
Well when I originally rooted and flashed the device it was brand new out of the box. Even then the only custom rom that I could get to work was Slimbean.
Pretty sure I tried all the other custom roms listed here:
http://forum.xda-developers.com/showthread.php?t=1850506
I have installed Slimbean a few time because I started getting errors, and keyboard kept crashing and things like that. I always wipe cache, and dalvik cache.
Click to expand...
Click to collapse
Sorry to hear this, there is no reason why my sg3 would work and yours doesnt though
a ODIN reflash back to stock I assume will fix things.
if you'd like to try a clean stock TouchWiz ROM, please give mine a try and let me know how you like it.
http://forum.xda-developers.com/showthread.php?t=2275376
but from the sound of it, it sounds as though either
you are not waiting long enough for it to boot (first boot can take up to 10-20 mins..)
or not wiping fully in recovery before the flash

andybones said:
Sorry to hear this, there is no reason why my sg3 would work and yours doesnt though
a ODIN reflash back to stock I assume will fix things.
if you'd like to try a clean stock TouchWiz ROM, please give mine a try and let me know how you like it.
http://forum.xda-developers.com/showthread.php?t=2275376
but from the sound of it, it sounds as though either
you are not waiting long enough for it to boot (first boot can take up to 10-20 mins..)
or not wiping fully in recovery before the flash
Click to expand...
Click to collapse
Oh wow can it really take that long for first boot? I know I waited probably somewhere close to 10 minutes, but def no where close to 20.

Cobinator said:
Oh wow can it really take that long for first boot? I know I waited probably somewhere close to 10 minutes, but def no where close to 20.
Click to expand...
Click to collapse
in theory AOSP ROMs should load faster than a Touch Wiz ROM as TW ROMs are around 1 gig for the ROM.zip and AOSP ROMs are about half that, but still I've had ROMs take over 15 mins to load, I know one time I thought it was the phone, but then I wiped fully again, and waited 20 mins and it loaded. I would say anything after 20 mins though, then it's definitely something wrong.

Ok backing stuff up then going to flash back to stock then try LiquidSmooth and see if it will let me boot up. Will let ya know how it goes.

So I install stock un-rooted rom. Then installed a stock rooted rom, then installed liquidsmooth and all I get is the Samsung symbol flashes then it goes black. Then it vibrates and the Samsung symbol flashes then blackness. Just repeats this over and over =(

I noticed you said that you're wiping cache and dalvik, but make sure you're also wiping data and system too.
Sent from my SCH-I535 using xda premium

Please read forum rules before posting
Questions and help issues go in Q&A and help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

My apologies moderator.
Anyways. I wiped everything on the phone before every rom installation. System restore, dalvik, and cache. The custom rom still won't boot.

4.4.3 introduced previously nonexistant bugs for me...

Hello, am I the only one experiencing bugs that I didn't have before since upgrading to 4.4.3?
To be specific: I never had the mm-camera-daemeon bug before updating, now I see it in the battery statistics! I thought 4.4.3 was supposed to fix this, not introduce it for people who previously didn't have it.
Also, this might just be me, but the speaker and headphone volume seem quieter than before, which again, I thought this bug was supposed to be fixed.
I installed the factory image from google with fastboot, but didn't wipe the data.
Any thoughts?

the camera deamon itself is not a bug, itll show up if you use the camera. what was a bug is that it continued to drain battery after the camera was used.

simms22 said:
the camera deamon itself is not a bug, itll show up if you use the camera. what was a bug is that it continued to drain battery after the camera was used.
Click to expand...
Click to collapse
But this is showing up after rebooting, and I haven't used the camera for a few days. I also don't have any apps like skype that may be accesing it. Maybe I'm just being paranoid though.

I always recommend wiping when updating Android versions. The Same principles as custom ROMs actually apply to stock too. Of you have bugs, rule out your data and legacy settings first by wiping data
Sent from my Nexus 5 using Tapatalk

rootSU said:
I always recommend wiping when updating Android versions. The Same principles as custom ROMs actually apply to stock too. Of you have bugs, rule out your data and legacy settings first by wiping data
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, I know it's a good idea, but I'm always hesitant to do so since my internet speed is around .25 mbps. Redownloading apps takes a looong time. I suppose there's always backup solutions though.

iJimaniac said:
Yeah, I know it's a good idea, but I'm always hesitant to do so since my internet speed is around .25 mbps. Redownloading apps takes a looong time. I suppose there's always backup solutions though.
Click to expand...
Click to collapse
Yeah you can use helium.
Sent from my Nexus 5 using Tapatalk

No issues here
iJimaniac said:
Hello, am I the only one experiencing bugs that I didn't have before since upgrading to 4.4.3?
To be specific: I never had the mm-camera-daemeon bug before updating, now I see it in the battery statistics! I thought 4.4.3 was supposed to fix this, not introduce it for people who previously didn't have it.
Also, this might just be me, but the speaker and headphone volume seem quieter than before, which again, I thought this bug was supposed to be fixed.
I installed the factory image from google with fastboot, but didn't wipe the data.
Any thoughts?
Click to expand...
Click to collapse
I have no issues, but I waited for the OTA and sideloaded it because I didn't want to wipe my data.
Dirty flashing is almost always a bad idea, if you have problems your just going to have to reset your device.
Yet everyone insists on doing it because they can't wait a day for the OTA to drop
Happens every time there's a new Google version put out, tons of people with issues because they dirty flashed the factory image.
Lesson
Wait for the OTA to sideload or install the factory image and let it reset your device as it's designed to do.

movielover76 said:
I have no issues, but I waited for the OTA and sideloaded it because I didn't want to wipe my data.
Dirty flashing is almost always a bad idea, if you have problems your just going to have to reset your device.
Yet everyone insists on doing it because they can't wait a day for the OTA to drop
Happens every time there's a new Google version put out, tons of people with issues because they dirty flashed the factory image.
Lesson
Wait for the OTA to sideload or install the factory image and let it reset your device as it's designed to do.
Click to expand...
Click to collapse
Actually, I flashed it because I had modified the /system partition and my limited understanding of how Nexus devices update told me the ota wouldn't work with a modified system. Is this correct, or does the modified system only keep your device from receiving the ota, not sideloading it? This is the first device I've had that actually receives official updates, so I'm new to this.

Modified system
iJimaniac said:
Actually, I flashed it because I had modified the /system partition and my limited understanding of how Nexus devices update told me the ota wouldn't work with a modified system. Is this correct, or does the modified system only keep your device from receiving the ota, not sideloading it? This is the first device I've had that actually receives official updates, so I'm new to this.
Click to expand...
Click to collapse
If your not stock your right, the OTA will likely fail. You can get away with being rooted, you'll just lose root.
Unfortunately everyone wants to get away without clearing and reseting their device and it leads to problems when people dirty flash the factory image.
If your not stock and want the latest update, your best bet is to bite the bullet and install the full factory image the way it was intended.
Clearing the device at the same time with the factory image, or installing one of the pre-rooted roms that comes out shortly after the new version drops. (Again clearing user data)
It's part of the price that comes with tinkering with your device.

movielover76 said:
If your not stock your right, the OTA will likely fail.
Unfortunately everyone wants to get away without clearing and reseting their device and it leads to problems when people dirty flash the factory image.
If your not stock and want the latest update, your best bet is to bite the bullet and install the full factory image the way it was intended.
Clearing the device at the same time with the factory image, or installing one of the pre-rooted roms that comes out shortly after the new version drops. (Again clearing user data)
Click to expand...
Click to collapse
Alright, good deal! Now I know for next time, thanks

Nexus 5 major software issues

Hey guys, i'm posting here because I have a huge issue with my phone.
I think I have an idea of what caused my phone to go haywire, but i'm gonna post my phone specs:
Red Nexus 5 32gb
Rooted
Franco Kernel
4.4.2 (however, I think it may have somehow updated to 4.4.3 OTA somehow, which may be the root of the problems)
TWRP
Nandroid backup but done once i've been experiencing these problems
-The phone boots up normally and then abrubtly freezes.
-The dialogue "Unfortunately, the process com.android.systemui has stopped."
-I press ok, the screen turns black
-"Unfortunately, Update Device has stopped"
-I press ok, shortly after, both prompts pop up again repeatedly.
I literally have no way to get to the home menu, even using Safe Mode.
My main priority is to at least recover my SMS files. And obviously fix my phone..

NotReallyKnown said:
Hey guys, i'm posting here because I have a huge issue with my phone.
I think I have an idea of what caused my phone to go haywire, but i'm gonna post my phone specs:
Red Nexus 5 32gb
Rooted
Franco Kernel
4.4.2 (however, I think it may have somehow updated to 4.4.3 OTA somehow, which may be the root of the problems)
TWRP
Nandroid backup but done once i've been experiencing these problems
-The phone boots up normally and then abrubtly freezes.
-The dialogue "Unfortunately, the process com.android.systemui has stopped."
-I press ok, the screen turns black
-"Unfortunately, Update Device has stopped"
-I press ok, shortly after, both prompts pop up again repeatedly.
I literally have no way to get to the home menu, even using Safe Mode.
My main priority is to at least recover my SMS files. And obviously fix my phone..
Click to expand...
Click to collapse
reflash your rom, or flash another rom. if using stock, you can reflash the factory img or find a rooted stock rom. anyways, you DO want to update to 444, as many bugs have been fixed from 442 to 444. if yoy dont want to lose any data, grab a stock rooted rom and flash it dirty, as in dont wipe a single thing. and your phone can not update itself, only you can let it update. and with you using franco kernel, it can not flash an ota, you would have to do it manually.

simms22 said:
reflash your rom, or flash another rom. if using stock, you can reflash the factory img or find a rooted stock rom. anyways, you DO want to update to 444, as many bugs have been fixed from 442 to 444. if yoy dont want to lose any data, grab a stock rooted rom and flash it dirty, as in dont wipe a single thing. and your phone can not update itself, only you can let it update. and with you using franco kernel, it can not flash an ota, you would have to do it manually.
Click to expand...
Click to collapse
Do you mind linking me a good thread on how to dirty flash a rom? I've been looking all over and i'm getting a lot of results that simply don't work.
Edit:
Nevermind, found out how to use adb. Can you at least tell me where the SMS files are stored? I used Textra.

NotReallyKnown said:
Do you mind linking me a good thread on how to dirty flash a rom? I've been looking all over and i'm getting a lot of results that simply don't work.
Edit:
Nevermind, found out how to use adb. Can you at least tell me where the SMS files are stored? I used Textra.
Click to expand...
Click to collapse
well, theres no such thing. as most everyone will tell you the proper way is to clean flash, you wont find a dirty flashing thread. regardless, im known for my dirty flashing of everything. generally, what you do to dirty flash is make a backup in recovery first, then just flash what you need to flash, without wiping anything. the thing about dirty flashing is that you dont lose any data(while clean flashing you do).
where the sms files are stored, i have no idea. have you checked if your sms app created a file?

simms22 said:
well, theres no such thing. as most everyone will tell you the proper way is to clean flash, you wont find a dirty flashing thread. regardless, im known for my dirty flashing of everything. generally, what you do to dirty flash is make a backup in recovery first, then just flash what you need to flash, without wiping anything. the thing about dirty flashing is that you dont lose any data(while clean flashing you do).
where the sms files are stored, i have no idea. have you checked if your sms app created a file?
Click to expand...
Click to collapse
So what I should do is push the rooted stock rom somewhere into my phone and use TWRP to install it straight?

NotReallyKnown said:
So what I should do is push the rooted stock rom somewhere into my phone and use TWRP to install it straight?
Click to expand...
Click to collapse
right. adb push it to your phone, then flash it in twrp. if the dirty flash doesnt work out(chances are that it will) then you would have to wipe data(factory reset) and reflash.

simms22 said:
right. adb push it to your phone, then flash it in twrp. if the dirty flash doesnt work out(chances are that it will) then you would have to wipe data(factory reset) and reflash.
Click to expand...
Click to collapse
You are a f**king god. It worked perfectly! Thank you so much!
Why isn't Dirty Flashing suggested by most?

NotReallyKnown said:
You are a f**king god. It worked perfectly! Thank you so much!
Why isn't Dirty Flashing suggested by most?
Click to expand...
Click to collapse
because most follow older "proper" ways to flash software. and the proper way to flash, and to make sure all is working as should, is to clean flash. dirty flashing can cause issues, but its issues that are usually fixable. the problem is that most dont know that, or how to fix. 99.99% of issues caused by dirty flashing are caused by corrupt or incompatible data. where a data clearing for that particular app will usually fix. anyways, roms based on the same sourcw, and not far from what you are running, you can dirty flash. roms that have a different base than what you are running, you should factory reset first.

Dirty flashing has the potential of causing conflicts and issues. Of course it is not so bad if you back up your data. One problem though, is you might use your phone for a few weeks before the issues show up, then suddenly you are unable to backup data. So you lost a week or two of stuff.
By the way, I often dirty flash when I run into issues. After that though, it is a good idea to back everything up, wipe, and reflash everything. Limits potential issues arising and also causes of said issues.

wangdaning said:
Dirty flashing has the potential of causing conflicts and issues. Of course it is not so bad if you back up your data. One problem though, is you might use your phone for a few weeks before the issues show up, then suddenly you are unable to backup data. So you lost a week or two of stuff.
By the way, I often dirty flash when I run into issues. After that though, it is a good idea to back everything up, wipe, and reflash everything. Limits potential issues arising and also causes of said issues.
Click to expand...
Click to collapse
issues from dirty flashing do not appear weeks later, dirty flashing issues show up right away. all dirty flashing issues are caused by data, whether corrupt or incompatible. other issues are blamed on dirty flashes, but arent the real cause. issues like app fc's are the most common, and very fixable. the only issues that arent fixable are when you dirtt flash two completely different roms that are based on different sources, or different android versions. i have dirty flashed every single thing ive flashed onto my n5, since december, no issues. the only issue i had dirty flashing my n5 was dirty flashing L over rastakat. and the issue was minor. everything worked great except the status bar didnt go down all the way. why did it mess uo? because of incompatible data from rastakat with the new status bar code in L.

You are correct Simms, but it must be noted that you dirty flash the same version, for dirty flash to work. If just updating a rom it is usually fine, but if they have made a major change then it is not.
Have no tales to tell of my N5, but my Samcrap S3 (cracked the screen and she died, then I bought this bad boy ) had issues that would appear later. Maybe due to the dirty flash. Who knows, that is why I mentioned a clean flash rules that out.
Anyway, backing up everything leads to a carefree life!