A few weeks/months after installing a ROM it starts to get slower over time. The only way I've found to fix it is going back to stock ROM and then back to a custom ROM. It happened with different ROMs.
Any idea of why this could happen or how I can fix it?
I'm thinking it may be related to some partition, because even a clean flash doesn't work. And I have to go back to stock ROM before flashing a new ROM.
My previous ROM was Pixel2ROM. Current Pixel Experience. I had to go back to stock before flashing this.
Could you help me? Any idea why is this happening?
Related
Hi,
I have really googled this but cant really figure it out.
I have been through several excellent custom roms. Good work to you all !
.. but very often they crash hang etc. Sometimes during the day. Often when I charge the phone at night etc.
Is it correct that it is very important to first flash the latest stock rom before you flash the custom rom !?!?
I believed that flashing the custom rom image would replace all prior rom data?
Please help me out !
If I do it is just to flash stock rom with Hard SPL and then hardreset and another custom rom? I read something about someone bricking the phone.
/P
Lombiz said:
Hi,
I have really googled this but cant really figure it out.
I have been through several excellent custom roms. Good work to you all !
.. but very often they crash hang etc. Sometimes during the day. Often when I charge the phone at night etc.
Is it correct that it is very important to first flash the latest stock rom before you flash the custom rom !?!?
I believed that flashing the custom rom image would replace all prior rom data?
Please help me out !
If I do it is just to flash stock rom with Hard SPL and then hardreset and another custom rom? I read something about someone bricking the phone.
/P
Click to expand...
Click to collapse
hi
crashes might happen, right
sometimes it could be the rom, or an app, or rhe sd card, or radio+ril combo,...
its not always easy to trace and single out
some reported that -although indeed everything of the previous rom should be removed during flash- they still fared better when flashing stock before custom
I must say I never did and fortunately also didnt have hlaf of the problems reported by other users
so: find out for yourself, as it cannot be generalised
cheers
Two phones. result very different !
Thanks !
What I really find strange though.
My friend and I have the same X1. Released at about the same time etc.
So hardware should differ mouch.
The rom is flashed so any difference in updates shouldnt matter too much.
After flashing my phone works great and his barely starts.
/peter
from my experience there is a difference
flashing a custom rom only replaces the previous rom
but flashing the latest custom rom replaces (rom+radio+ and 2 other things that i cant remember)
u wont get a problem free mobile after flashing the stock rom
but i'm sure that it decreases them to a very noticeable degree
less freezes better performance etc...
in my opinion: u won't loose anything from doing it, but it might help
so y not to try, it worth the shot
I have tried a couple of custom roms and they have all worked fine at first but then after a while most of them would do something like force close whenever i try to open anything. This is getting really frustrating. I have a build 1009 and im looking at phoenix 3.0 and perception 10.0 both look really nice. Could someone tell me what im doing wrong and how to fix it. Every time i try to enable third party apps recently or something else ( I can't remember specificly what it was but it was rooting it or something) it will do the blah blah something apcore stoped working force close so right now im just going to use my phone on stock firmware and use it like normal and see what happens but could someone help me. I have used gingerclone, Assonance (force close problem), Darky 8.0 with the captivate workaround (force close problem), and maybe a few others but those are the only ones i can remember.
Custom roms are rooted with side loading enabled. So if you are trying to do this after you have the rom loaded, that could be a problem. I also would like to know what you are restoring on these roms. Should only be user apps.
To pin point your problem please provide more detail
I have put apps from custom roms onto the stock rom and other roms. Could that be the problem? And also this is what im going back to.
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
Im only doing the first part im not going to jh7. would that have something to do with it. Any help is greatly appriciated.
yamato2 said:
I have put apps from custom roms onto the stock rom and other roms. Could that be the problem? And also this is what im going back to.
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
Im only doing the first part im not going to jh7. would that have something to do with it. Any help is greatly appriciated.
Click to expand...
Click to collapse
What apps?
I do not think only going back to jh7 would cause your issue. Tell me more about what you are trying to do to enable side loading, and why you are doing it on as custom rom
I had the ones i downloaded and i sideloaded one wireless tether app a long time ago then i backed it all up with titanium backup and i would install a custom rom and it would have roms preinstalled on it. I would want to put on a different custom rom so i backed up again and the flashed back to stock the to the new rom. and i would restore all the apps including the one from previous roms. If you are asking for the specifics it would take a while and about the side loading i followed the guide http://forum.xda-developers.com/showthread.php?t=738376 and did the method 3 it seemed to work fine until i rebooted and then it did the force close thing. And i didn't go to jh7 i went to jh6 or jh2 or something like that but im going to try going to jh7 and see if that helps.
dont restore ALL apps in Titanium Backup. safest option is "restore missing apps+data"
all the custom 2.2 roms have tethering/wifi hotspot built into them...no need for another app for it.
for custom roms, you DO NOT need to root or sideload...they are enabled by default on all custom roms.
Thank both of you for your help. I will probably for now only install roms specificly for captivate and with specific instructions.
I was hoping to flash Paragon tonight, but it said to flash to stock first and I had a few questions.
Why do some ROMs have you flash to stock while others you can just flash through ROM Manager?
Is the Stock backup I made through ROM Manager sufficient as a subsitute for an Odin flash?
If not, are there any Mac alternatives out there?
I'm trying to get a good understanding of what I'm tooling around with so I don't brick my phone.
Thanks for the answers
I wish I could answer all your questions, I'm guessing it's because the recovery uses a zip file and it does not update everything that odin would. Anyways, if you need any help flashing to stock I know that the FAQ page of the cognition rom found here has directions.
cognition.theidiotshideout.net/mw/index.php?title=ODIN#One-Click_JF6
It is not needed but many think it is best. Depending on the rom you are on you have a cocktail of lag fixes and kernels. Flashing stock gives a clear slate.
You can disable lag fix, delete davlik cache, clear cache. You should be fine but you may run into issues. May.
What are you running?
It's some sort of ancient lore past down from priests of captivate forum antiquity.
As for 'cocktails of lag fixes and kernels,' there is no reason your cwm install can't format those partitions, particularly in light of the fact that it has built-in support for ext4. I don't know why people think the stock flash functions are particularly better at dealing with it.
Do yourself a favor, make sure you have a working download mode combo, purge your mind of the flash to stock FUD and obliviously commence to flashing one froyo ROM right over another. You'll be glad you did.
So if I'm hearing you correctly, it's more of a this will make sure you have no issues and are starting from a clean slate. It's not 100% neccessary to flash to stock before flashing a new rom?
Meanwhile, I was furiously trying to get Odin to work on an old laptop I scrounged up to no avail. Sometimes my need to tinker creates so many problems.
Thanks, guys!
wmbenham said:
So if I'm hearing you correctly, it's more of a this will make sure you have no issues and are starting from a clean slate. It's not 100% neccessary to flash to stock before flashing a new rom?
Meanwhile, I was furiously trying to get Odin to work on an old laptop I scrounged up to no avail. Sometimes my need to tinker creates so many problems.
Thanks, guys!
Click to expand...
Click to collapse
It is like a default disclaimer to flash stock. If you flash the rom and have an issue, one if the first things they will ask is did you flash stock. As mentioned almost all lag fixes use some form of ext 4 filing and most clockwork recoveries can now handle ext 4.
So in summation you do not need to, if you flash and get stuck in a boot loop you need to. I would make sure you can get odin up and running, and recognizing your phone in either case just so you know you can use it if needed
Absolutely no need at all to flash to stock
Would you install Vista in order to install Win7?
As long as you format everything in CWM before you flash a new ROM, then everything is a clean slate. It'll wipe your stock install, so why install stock first?
This and the 're-calibrating' your battery are the two biggest FUDs about Android.
Let's say i got a rom that performs amazingly,super fast tab switch,good at multi tasking,25k in benchmark.
Then I want to try a new rom,so I flash the new rom after cleaning my devide,as i should do.
But I don't like it or whatever and I want to return to the old one. But after I flash the old rom the performance is extremely bad,getting random systemui FC ,reboots,etc.
Why is this happening? Right now I'm running out of roms that I can use on my phone,as I cannot go back to the ones that I really liked. Please help
It also happens when a developer posts a new build of a rom. If i got the previous build installed and i flash the new one,the rom is broken again.
darkkfruit said:
Let's say i got a rom that performs amazingly,super fast tab switch,good at multi tasking,25k in benchmark.
Then I want to try a new rom,so I flash the new rom after cleaning my devide,as i should do.
But I don't like it or whatever and I want to return to the old one. But after I flash the old rom the performance is extremely bad,getting random systemui FC ,reboots,etc.
Why is this happening? Right now I'm running out of roms that I can use on my phone,as I cannot go back to the ones that I really liked. Please help
It also happens when a developer posts a new build of a rom. If i got the previous build installed and i flash the new one,the rom is broken again.
Click to expand...
Click to collapse
I use Philz recovery and before flashing a new rom i just simply hit Clean up to install a new rom.
I never faced any of the issue that u mentioned. Try following what i said.
If u are using a lollipop rom then u may face systemui FC ,reboots as there is a bug which is experienced by some users.
I tried every recovery, twrp with full device wipe,cwm with their wipe,and philz with full wipe and the one you mentioned.
The issues happen in every rom,wether it's 3.2,4.4 or 5.x.
darkkfruit said:
I tried every recovery, twrp with full device wipe,cwm with their wipe,and philz with full wipe and the one you mentioned.
The issues happen in every rom,wether it's 3.2,4.4 or 5.x.
Click to expand...
Click to collapse
Return to stock by flashing ftf through flashtool and start from beginning.
What would be the quickest way to update a rom. I think some have them built in from what I'm hearing like cyanogenmod, but i'm looking at others like pure android, is there a way to just drop the new pure android rom on top of the old one without starting from scratch and downloading all the apps over again and such? Is it as easy as just not wiping anything and flashing the new rom?
treysmith7 said:
What would be the quickest way to update a rom. I think some have them built in from what I'm hearing like cyanogenmod, but i'm looking at others like pure android, is there a way to just drop the new pure android rom on top of the old one without starting from scratch and downloading all the apps over again and such? Is it as easy as just not wiping anything and flashing the new rom?
Click to expand...
Click to collapse
quickest way.. download the update onto your phone, boot into twrp recovery, flash the rom, and supersu, then just reboot. if you are updating a rom, you dont have to wipe. if you are flashing a different rom, then you have to wipe.
Not wiping between flashes is known as dirty flashing and is generally only doable within the same rom. Pure nexus rom I know though if you're going from lollipop to marshmallow the dev is instructing a full wipe. It MIGHT work dirty flashing but I highly highly doubt it and honestly in the time it would be to dirty flash then have to restore a backup you might as well backup apps and clean flash it.
Just always look in the update post, if the dev says clean flash do a clean flash, its a shocker to some people but devs generally know what they're talking about when it comes to their rom.
if you are going from 5.1.1 to marshmellow, what you can do is make a backup in recovery, then flash the update. if toj do have issues, you can always restore your backup, then do a clean flash(wipe).