Database Users

All ROMs I flash on my device have become unstable

I've had my S4 for a little over a week now. I've been flashing different ROMS to find which one I like but all of them except for CleanROM are very, very unstable on my phone. I've tried CM, SlimBean, Graviton, and PACMan. Some are TW, some are AOSP but I get the same results for each. Device becomes unresponsive, I get FCs, random reboots. Its crazy because I had no issues at all on my Note 2. I wipe and factory reset every time, its becoming very tedious to restore each time. I do not restore system apps, I follow all instructions and still get these results. I'm wondering if I have a faulty device? Maybe a sensor or something is not liking certain things on certain apps? I've noticed that after I installed Graviton and went back to CleanROM, Titanium has stopped working and I get the Samsung lockscreen instead of the SGS4 one. I may just go back to MDL stock in Odin, re-root and see what happens...I'm currently wiping everything and fixing permissions

Sorry to hear, sometimes starting over cures 90% of all issues, and the os gets better each time.. If it were me, I would quit wasting time and odin.
Thanks, and good luck.

Don't Forget -
jedimyndtryx said:
I've had my S4 for a little over a week now. I've been flashing different ROMS to find which one I like but all of them except for CleanROM are very, very unstable on my phone. I've tried CM, SlimBean, Graviton, and PACMan. Some are TW, some are AOSP but I get the same results for each. Device becomes unresponsive, I get FCs, random reboots. Its crazy because I had no issues at all on my Note 2. I wipe and factory reset every time, its becoming very tedious to restore each time. I do not restore system apps, I follow all instructions and still get these results. I'm wondering if I have a faulty device? Maybe a sensor or something is not liking certain things on certain apps? I've noticed that after I installed Graviton and went back to CleanROM, Titanium has stopped working and I get the Samsung lockscreen instead of the SGS4 one. I may just go back to MDL stock in Odin, re-root and see what happens...I'm currently wiping everything and fixing permissions
Click to expand...
Click to collapse
Don't forget to immediately freeze the ATT update apps... Or you will get the MF3 OTA... which, for now, is NOT-ROOTABLE & Custom Recoveries NOT-Installable.

I always factory reset,wipe both cache and format system.even when I use a back up.
Sent from my SAMSUNG-SGH-I337 using xda premium

Well I ODIN'ed and went back to CleanROM. So simple. I'm dying to try one of the VZW AOSP themed TW ROMs though. Decisions, decisions. Oh man....when I first got the phone it was on MF3. I spent 3 days on craigslist and found someone to trade me their non-updated phone. Still new to this Android business. So far I love it. Don't see why I spent so many years hating. Thank you all for the help.

[Q] Build KRT16S?

OTA for KRT16O from JWR66Y failed on my Nexus. It bootlooped, and I had to reflash stock. I haven't yet decided to try updating again, but today I got a notification that an update was ready to install. I checked it out, and the file says (in part) signed-nakasi-KRT16S-from-JWR66Y.
I've searched the Nexus forums for KRT16S and can't find mention of it. Anyone else have it?
What's the difference between that and KRT16O?
Inquiring minds want to know.

Serial_Noob said:
OTA for KRT16O from JWR66Y failed on my Nexus. It bootlooped, and I had to reflash stock. I haven't yet decided to try updating again, but today I got a notification that an update was ready to install. I checked it out, and the file says (in part) signed-nakasi-KRT16S-from-JWR66Y.
I've searched the Nexus forums for KRT16S and can't find mention of it. Anyone else have it?
What's the difference between that and KRT16O?
Inquiring minds want to know.
Click to expand...
Click to collapse
Coming from 4.3.1 myself, was running 16O myself for a week+ and then got the OTA for 16S, it's a minor update, bug fixed and newer apps, etc. and seemed to run smoother, and has the GEL, etc. - running quite smoothly for me to the point where I decided to wipe & deep clean and start fresh.
Then, I saw this & decided to flash it instead, keep my CWM & root, but essentially just like factory fresh rom, with SUv1.75 and busybox, odexed and starting off with plenty of internal storage space. Got lazy instead & opted for it instead of flashing image, running ADB & unlock routine all over.
http://forum.xda-developers.com/showthread.php?t=2533035
As always, backup via TB & custom recovery, and save it offline to portable storage first, just in case. I was fully prepared this past weekend to start from scratch - too many posts about problems downloading, upgrading, bootlooping and freezing, etc.

Nexus 10 Random Reboots

'My Nexus 10 started to randomly reboot several times a day after the Kitkat update and because it is outside the warranty period I cannot get it replaced.'
It reboots no matter what is running and sometimes it reboots immediately after a power up but never enters a reboot loop.
I've tried a factory reset and running it in safe mode but that didn't stop it.
I've not been able to replicate the reboot fault until yesterday when I ran the BBC iplayer and downloaded a 1-hour Horozon video of about 650Mb and when I tried to play it I got a reboot and that happened consistantly.
I tried a complete power down and reboot then tried to play the downloaded video but it always rebooted.
I tried deleting and re-saving the video incase it was corrupt but it still rebooted.
I tried deleting the video and streaming it and I could watch it that way without any reboot.
I've tried downloading three 1-hour Horizon videos of about the same size and only one plays without rebooting.
A check of running apps shows just the keyboard and a couple of system apps but I still get the reboot when I try to play the saved video.
I thought about removing apps one at a time to see if that would solve it but I've basically got the same apps I had before the Kitkat update.
I wondered if I could undo the Kitkat update and flash the previous rom to see if that would solve it for Kitkat was not a big improvement.
I've never used a custom rom and not run anyting other than stock software.
I would be most grateful for any suggestions on how to fix this rebooting problem and whether going to an earlier version of Android is feasable and how would I do it.
PS. There is a BBC iplayer option to download videos using less resolution and when I choose that option the Horizon file size falls to 344Mb which is about half the size of the original and it solves the reboot problem when playing the saved video.
So it would seem that the BBC iplayer reboot problem is related to file size.

It's fairly easy to downgrade, just Google "nexus factory images" and you should find all the old versions of android straight from Google. There should be guides online for how to flash a factory image. Just make sure to back up all your files to your computer as it will wipe everything.
Sent from my SGH-I747M using xda app-developers app

gc84245 said:
It's fairly easy to downgrade, just Google "nexus factory images" and you should find all the old versions of android straight from Google. There should be guides online for how to flash a factory image. Just make sure to back up all your files to your computer as it will wipe everything.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Thanks for your help.
I've found the factory images and I'm now looking for a simple detailed guide how to do the downgrade.
My Nexus 10 is on 4.4.2 (KOT49H) and I think I'll try downgrading one level to 4.4 (KRT16S) to see if that solves the reboots problem and if not then I'll try downgrading further to 4.3 (JWR66Y).

Gaugerer said:
Thanks for your help.
I've found the factory images and I'm now looking for a simple detailed guide how to do the downgrade.
My Nexus 10 is on 4.4.2 (KOT49H) and I think I'll try downgrading one level to 4.4 (KRT16S) to see if that solves the reboots problem and if not then I'll try downgrading further to 4.3 (JWR66Y).
Click to expand...
Click to collapse
Here is a good guide (sorry, I would have posted it earlier but I didn't have my computer with me at the time and was posting from my phone):
http://forum.xda-developers.com/showthread.php?t=1907796

gc84245 said:
Here is a good guide (sorry, I would have posted it earlier but I didn't have my computer with me at the time and was posting from my phone):
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
Thanks for the guide link.
Unfortunately, my laptop is running Windows 8.1 and it is difficult to install the USB driver and Android Development Kit needed to flash previous Android versions, so I've given up until I can find the way to do it.
PS. I've found a way of installing the ADB and Fastboot drivers on my Windows 8.1 laptop and here is a link:
http://forum.xda-developers.com/showthread.php?t=2588979
So I'm back on track to solve my random reboots using an earlier version of Android.

I noticed the iPlayer hard crash thing too. I can play downloads, but as soon as I pause it and attempt to restart, or just slide the progress bar to move to a different part of the video, the tablet hangs then reboots. It's completely reproducible, and doesn't happen on any of my other devices.
Apart from that, my n10 has now gone 20 days since the last random reboot, so it's a lot more stable in general than it used to be!

I've found a easy way to downgrade to 4.3 and would be grateful for any opinion on how safe it is and if anyone has tried it.
http://forum.cyanogenmod.com/topic/83985-nexus-factory-images-to-revert-to-stock/

AleT said:
Apart from that, my n10 has now gone 20 days since the last random reboot, so it's a lot more stable in general than it used to be!
Click to expand...
Click to collapse
Arghh...this thing is a POS. I haven't used it in 2 months. Today I fired up chrome for some browsing. It hard locked within 5 minutes. I left it for an hour plus with the screen on and still locked up. Just frustrated. Worst Android device I've owned.
Sent from my XT1053 using Tapatalk

Either you have a faulty app or your tablets have a hardware defect. The random reboot issue, where the GPU driver would leak memory and force a kernel panic, has been fixed since Android 4.3 in July. This includes the Chrome reboot issue. I've had 2 reboots over 13 months, and both were cause by a ROM issue. I assure you, there is nothing wrong with the Nexus 10. Try a 4.4.2 factory image and see if that solves anything.

Koopa777 said:
Either you have a faulty app or your tablets have a hardware defect. The random reboot issue, where the GPU driver would leak memory and force a kernel panic, has been fixed since Android 4.3 in July. This includes the Chrome reboot issue. I've had 2 reboots over 13 months, and both were cause by a ROM issue. I assure you, there is nothing wrong with the Nexus 10. Try a 4.4.2 factory image and see if that solves anything.
Click to expand...
Click to collapse
I still get random re-boots in `safe mode` which is supposed to only allow apps installed with the system to run which leaves a bad 4.4.2 which could be checked by a re-flash of the factory image or faulty hardware.
I was planning to downgrade to 4.3 to see if that solved the re-boots but I might try a re-flash of 4.4.2 first to see if that works..
I'm not very confident about flashing and I've had the additional problem of working on windows 8.1 on my laptop.

I am running the factory image, 2nd one with same issues. I'm not necessarily disputing what you are saying but there were plenty of people telling me they had a perfect tablet when the memory leak wasn't fixed.
Sent from my XT1053 using Tapatalk

rxnelson said:
I am running the factory image, 2nd one with same issues. I'm not necessarily disputing what you are saying but there were plenty of people telling me they had a perfect tablet when the memory leak wasn't fixed.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
The memory leak was fixed but apparently, it's reappeared for me with the latest kitkat update. Quite frustrating, you'd think Google would be on top of these things. What's the point of fast updates if you're waiting months on end for a fix. If I don't powerdown my tablet when I'm finished using it I can guarantee a reboot during use. In the last 24hrs, it has rebooted on me twice while using Chrome. Quite irritating to be honest

It seems from previous posts that re-flashing 4.4.2 does not solve the reboots and I've not found a way to downgrade to 4.3 on Windows 8.1 to see if that works.
So I've tried another factory reset, but this time I've not allowed any non-Google apps to be installed other than the Photon browser which I need for flash Websites and the Re-boot logger app to record any reboots.
I'm using my Note 3 for the rest of my apps as that is still on 4.3 and doesn't have the reboot problem, but that might change after the KitKat upgrade.
I was getting at least 2 or 3 reboots a day so I should soon know if running 4.4.2 after a factory reset with just two 3rd party apps solves the problem and if so then that will suggest a rougue app. which I can reveal by re-installing the apps piecemeal.

I've just had another random reboot so I've done another factory reset but not signed in to Google so there have been no downloads and the only program I've run is Settings to increase the screen timeout to 30 - minutes.
If I still get random reboots then it is nothing to do with 3rd party apps or updates for I've not downloaded any.
That just leaves the hardware or the original 4.4.2 assuming the factory reset returns to that.

I didn't experience any reboots when not signed into google after a factory reset so I signed in and restored my tablet using Google backup.
I soon started to get reboots again, but I noticed that since the KitKat upgrade a website I use very often was sometimes automatically loading the Play store to try and get me to use their much inferier app. It doesn't happen on my Note 3 which is still on 4.3.
If I tried to close the Play store app to get back to the browser by swiping it away then it crashes and keeps trying to load over and over. If I hit the home button the Play store automatically re-appears still loading over and over, but after swiping it away several times it goes away or stops with an error message asking me to report the crash which I did and the browser is closed.
In order to fix this I disabled the Play store app so that it did not appear in my list of apps.and the website instead of loading the Play store app re-directed the browser to the Play store website which was better for I was still in the browser.
Since I stopped this particular website loading the Play store by removing it, I've just had one re-boot instead of several and my tablet is no longer overheating. I am a heavy user and have my tablet on many hours a day, so one re-boot is acceptable to me.
I've downloaded a Play store apk which I can install if needed but always remove it before using the website which tries to automatically load it.
It is a nuisance and I wish I'd stayed with 4.3, but I can live with the occaisional re-boot that might not be noticed if I only used my tablet lightly.
I'm annoyed that a website can automatically load the Playstore without me requesting it and that KitKat allows it.
I hope my experience helps others who are getting several re-boots a day.
PS
I did a factory reset then removed the Play store app before using the problem website so that it never loaded it in case that was needed.

Flashing the 4.3 factory image downgrades everything. For what it's worth, I noticed that the userdata partition is constructed differently than in 4.2.2(my last factory flash). That could have something to do with it. But also, I've been on custom ROMs since I got the tablet, yet I've never rebooted on 4.4.X. I guess try a vanillish ROM(like RastaKat) to see if that reboots.

Koopa777 said:
Flashing the 4.3 factory image downgrades everything. For what it's worth, I noticed that the userdata partition is constructed differently than in 4.2.2(my last factory flash). That could have something to do with it. But also, I've been on custom ROMs since I got the tablet, yet I've never rebooted on 4.4.X. I guess try a vanillish ROM(like RastaKat) to see if that reboots.
Click to expand...
Click to collapse
Now that I'm just getting one reboot a day and my tablet is running cooler I can live with that and I don't mind re-installing the Play store when needed for continuous updates can be a nuisance.

I finally managed to downgrade to 4.3 and I'm hoping that will solve all the problems I had with 4.4.2
But all seems well at the moment.
I'm not being booted from websites to the Play store, I can use the BBC iPlayer to download and run 1-hour videos and flash player works better.
Google has downloaded 4.4.2 (KitKat) but I'm not going to install it.

[Q] Systemui keeps crashing on custom roms

Need some expert assistance. The problem is my phone keeps crashing with systemui errors when using custom roms. It always happens after a reboot and usually within 1-3 days, depends on WHEN I reboot the phone. Let me give you a little backstory.
A little over a month ago, I was running AICP on my phone, but decided to try SimpleAOSP and Hells doctor.. So I created a backup in TWRP, then flashed SimpleAOSP and HD. The next day day I started getting the errors. At the time, I thought it was the kernel or a Titanium Backup glitch.
So I wiped and reflashed SimpleAOSP without HD and without restoring from TB. But the next day, systemui failed to start. I thought it might be a rom issue so I restored AICP from my TWRP backup. And I couldn't believe it when the same systemui errors happened. So I restored the backup again. Again it was okay for a few days, then error.
After that I copied everything from my phone to the PC and wiped internal storage. Then installed the same rom version from AICP that I had been using for weeks prior to all this. Same error after a few days.
So next I tried wiping internal storage again and flashing stock 4.4.4. I used that for over a week with no system errors. So I did a TWRP backup of Google stock rom, Then installed AICP again but this time without modifying any systemui type settings, I left the rom as stock as it could come. Didn't even restore apps or anything. I then the rebooted the phone a couple of times to test and the error came back. This was the same day I installed it.
So I restored the stock backup and have been running fine all week. I want to get back on a custom rom though. Any suggestions?

Am I getting no replies because I'm missing something really obvious?
Or can no one think of anything that I haven't already tried?
By the way, right after posting the OP I installed the L preview and it's been working fine so far. I figured if I had to run stock android it may as well be the latest thing.
Sent from my Nexus 4 using Tapatalk

I don't have any answer to your question but I was wondering if this happens without installing a custom kernel on CM11 and AOSP custom ROMs.

Thanks for replying.
When I tried SimpleAOSP, it was with and then without an additional kernel. I saw no difference as far as the error is concerned. I have not tried a CM11 based ROM since this all started.
Maybe I should try a custom rom that doesn't have heavy modifications like AICP has.
Sent from my Nexus 4 using Tapatalk

Are you flashing a Gapps package? A couple weeks ago when I was trying different ROMs I was getting system crashes after flashing PA Gapps and they updated. I never narrowed it down, but after uninstalling a bunch of them (News/Weather, Talkback, Keep, Newsstand, some others) so they wouldn't update, I stopped getting system crashes.

Idk why I have the feeling your theme/icon pack has something to do with it. I run pa and whenever I try to use click ui icon pack it happens to me but if I just run veu I don't have a problem. Try not using themes for a bit to see what happens

Sorry, I missed your responses, I had kinda given up on the whole thing. Android L is running good for an unfinished product.
Getting back to the original issue, no theme or icon pack was installed.
Yes, I was using PA gapps mini from 9-23. Maybe that was it.
But that would be weird because I don't remember my first ROM running PA gapps, not 100% sure... that was a month ago.
I'll try to install without any gapps package and report back. Thanks.
Sent from my Nexus 4 using Tapatalk

from my past history, I'm facing issues when I did 3 things :
1. if I just dirty flash or factory reset only before flashing new rom.
2. Did restore backup from TB (which from your explanation above, you don't have any problem TB)
Nowdays I always use wipe dalvik, system, data, cache. Because someone once told me if you changing roms, if not it's possible that the system setting from old rom will crash with the new ones. and for the wipe system part (some roms included that command in their roms zip file and some didn't).

[Q] Unbelievable lag on lollipop

I flashed the android 5.0 image from google website using NRT and then rooted the device. I have TWRP 2.8.1.0.
The problem is that my nexus 7 2012 12GB is giving me unbelievable lag. I have cleared cache and all but it is of no help.
I have no idea about F2FS but I read that changing to F2FS might help. So can any of you tell me what to do.

Falcon_Eyes said:
I flashed the android 5.0 image from google website using NRT and then rooted the device. I have TWRP 2.8.1.0.
The problem is that my nexus 7 2012 12GB is giving me unbelievable lag. I have cleared cache and all but it is of no help.
I have no idea about F2FS but I read that changing to F2FS might help. So can any of you tell me what to do.
Click to expand...
Click to collapse
I had that problem when I first flashed the factory 5.0 Image, without wiping data. It was horrid. The situation didn't improve after wiping data.
Later I flashed the ROM in my sig, and it is working very good. Occasional lag, but nothing worse than kit-kat. Overall the performance is much better than kit-kat.
I made sure to wipe, format, and repair data, cache, and system. In fact, that ROM wouldn't even boot until I did.
I wiped, formatted, and repaired, then loaded the ROM and GAPPS manually via ADB and flashed both normally using the TWRP interface.
Bootloader: 4.23
TWRP: 2810

Falcon_Eyes said:
I flashed the android 5.0 image from google website using NRT and then rooted the device. I have TWRP 2.8.1.0.
The problem is that my nexus 7 2012 12GB is giving me unbelievable lag. I have cleared cache and all but it is of no help.
I have no idea about F2FS but I read that changing to F2FS might help. So can any of you tell me what to do.
Click to expand...
Click to collapse
Factory reset does wonders. Lollipop works great after

I was having the same issue, then uninstalled Facebook and it has been fine since.

I had lag issue with google launcher. I am using launch came with Rom and nexus is much better. I am using f2fs Rom w/o google launcher. It's very usable.

I turned on Develop Options then scrolled to the bottom and checked off "Kill all activities when you leave them" and I really don't have the lag anymore.

FSRBIKER said:
I turned on Develop Options then scrolled to the bottom and checked off "Kill all activities when you leave them" and I really don't have the lag anymore.
Click to expand...
Click to collapse
Thank you for this tip. I did this and now its like having a whole different tablet. It is usable again. The only thing is in my developer options it is called "Don't Keep Activities."

I was writing the post from memory but your correct on the name. Glad it helped.
Sent from my Z3 Compact

piratesscareme said:
Thank you for this tip. I did this and now its like having a whole different tablet. It is usable again. The only thing is in my developer options it is called "Don't Keep Activities."
Click to expand...
Click to collapse
Also, scale all the animation speeds down to 0.5x in Developer Options and you'll love the snappiness It works great on my Nexus 7.

wiped cache, 'Don't Keep Activities' and whatever i could find still laggy as sh*t. Will wait for 5.0.1 OTA if that doesn't work back to 4.4.4. Any other suggestions without resetting/wiping ?

Try to run fstrim on /cache and /data

try this fix
I was able to fix my nexus 7 2012 lagging problem after the lollipop update and now it is as fast as before. I posted a video on how I did it and there is no downgrade or rooting required. Here is the link youtube.com/watch?v=OH2iYdr91DE

jamesmat said:
I was able to fix my nexus 7 2012 lagging problem after the lollipop update and now it is as fast as before. I posted a video on how I did it and there is no downgrade or rooting required. Here is the link youtube.com/watch?v=OH2iYdr91DE
Click to expand...
Click to collapse
u captured and uploaded a whole video just to tell us that the lag was fixed after turning location service off?!

I just received my nexus 7 2012, bought it from someone and it had 5.0.2 already installed on it.
This thing is sooo slow that i was wondering if i made a bad buy by getting this model.
Everything is super laggy, for example,.. 9gag or facebook, when it finally loads i cant scroll through it, its so slow it crashes the application before scrolling down.
I tried the wipe cache, enabled "dont keep activities" and set all animations to .5 in dev mode. i tried disabling location.
It all made it a bit more usable,.. but i read people having a smooth and fast device... which i dont have still.
what else could i try? as far as i know its not rooted and has the stock rom.
I really want to like this device but its not happening so far.
Any help is really appreciated

Most of the custom roms fix this issue. very fast now!

I am waiting for 5.0.3 and hoping it helps!

rbeavers said:
I am waiting for 5.0.3 and hoping it helps!
Click to expand...
Click to collapse
I am not going to hold my breath. After I did a full wipe & installed 5.02 that did seem to help.

I had really bad lag after flashing 5.0.2. I discovered (while trying to install Busybox) that the system partition was full. I deleted a few system apps (stuff I could get from Google Play if I ever needed it down the road), freed up a few megs, and things got instantly better.

Lost 1/2 my storage space
After factory resetting & flashing LRX22G on my 16Gb nakasi/grouper Nexus 7, it has turned into an 8Gb device... I've just spent the past 7 hours setting it all up again, so I am less than keen on factory resetting it all yet again to try & get it working as well as it did under Kitkat before I was stupid enough to upgrade to Lollipop. On the plus side, the horrible lag has finally gone (I think that it is the factory resets & cache wipes that fixes it, but I could be wrong). Now all I need to do is to find out how to convince it that it is a 16Gb version without having to factory reset it. Does anyone have any good advice on that please?

JustinSB said:
...On the plus side, the horrible lag has finally gone...
Click to expand...
Click to collapse
No, I take it all back! The horrible lag & frequent crashes are still here on 5.0.2 & exactly the same as they were on 5.0, & after an afternoon trying to use my tablet I am having no luck. Now my problem is that because I have lost half of my storage space, I don't have enough space to copy back my nandroid backup of my lovely, fast, & fully functional Kitkat installation.