Related
Hi there. I currently am running the Legend 2 ICS Edition ROM for Infuse 4G. I just noticed there is a new update Legend 3 ICS. If I want to keep all my files and apps, do I just flash the Update file (instead of the Full Wipe file)? And do I need to go through the same process, clear cache, dalvik cache, etc.? Probably no need to wipe data and factory reset.
Any help is much appreciated! Thanks.
Yakusoya said:
Hi there. I currently am running the Legend 2 ICS Edition ROM for Infuse 4G. I just noticed there is a new update Legend 3 ICS. If I want to keep all my files and apps, do I just flash the Update file (instead of the Full Wipe file)? And do I need to go through the same process, clear cache, dalvik cache, etc.? Probably no need to wipe data and factory reset. Any help is much appreciated! Thanks.
Click to expand...
Click to collapse
I suggest do a full wipe, if you want to keep your app, "tibu" titanium backup is great and well worth app, buy it...I did and worth every dime. IMHO Tibu will and can backup your apps and restore them.
So I suggest get tibu, backup your apps, do a full wipe install Leg3 go back to Gplay download/install tibu back on, then use the program to restore your apps only in this case.
Plus tibu can do a full backup of your data & apps, say you find your DD but want to test other ROMs, use tibu to backup data & apps, go test the another ROM, and want to come back to your DD ROM, you can then do a full data & app restore...plus there are lots of YouTube vid on Titanium Backup app.
Yakusoya said:
Hi there. I currently am running the Legend 2 ICS Edition ROM for Infuse 4G. I just noticed there is a new update Legend 3 ICS. If I want to keep all my files and apps, do I just flash the Update file (instead of the Full Wipe file)? And do I need to go through the same process, clear cache, dalvik cache, etc.? Probably no need to wipe data and factory reset.
Any help is much appreciated! Thanks.
Click to expand...
Click to collapse
You can do the update and keep your files, which is the reason for the update. Though, like Bigjoe says, a full wipe is always prefered, but not necessary.
Yakusoya said:
Hi there. I currently am running the Legend 2 ICS Edition ROM for Infuse 4G. I just noticed there is a new update Legend 3 ICS. If I want to keep all my files and apps, do I just flash the Update file (instead of the Full Wipe file)? And do I need to go through the same process, clear cache, dalvik cache, etc.? Probably no need to wipe data and factory reset.
Any help is much appreciated! Thanks.
Click to expand...
Click to collapse
The reason why everyone suggests a full wipe is so that you dont potentially run into any problems after the flash. ie flash not working, or camera wont load... little things like that that make it hard to narrow down problems. One of the main things people are going to ask is did you wipe before you installed? It helps to eliminate and remnants of left over roms so that you dont have any issues with the new rom. Its called a Bad flash.
I hope i answered your question!
Thanks for all the replies! So whether it is the full wipe ROM or the update ROM, both go through the same procedure of booting into CWM first? I will try Tibu for app backup! :good:
Stuck at blue loading loop
Hey, I am new so bare with me, I just flashed this rom onto my Infuse 4g and it seems to be restarting itself and looping to the Blue Android/Dust loading screen. It seems to fix with a fresh install of the rom, but shortly starts after everything seems fine. Please help!
araidis said:
Hey, I am new so bare with me, I just flashed this rom onto my Infuse 4g and it seems to be restarting itself and looping to the Blue Android/Dust loading screen. It seems to fix with a fresh install of the rom, but shortly starts after everything seems fine. Please help!
Click to expand...
Click to collapse
Try doing an odin or hemdall back to stock with partitioning, then flash the full wipe rom.
http://forum.xda-developers.com/showthread.php?t=1524081
http://forum.xda-developers.com/showthread.php?t=1705260
So I've been using your latest release (full wipe Legend v3) and I did factory reset, clear cache and dalvik cache, fixed permissions, etc. The phone is occasionally laggy now, usually when I open web browser it would stay on the white screen a several seconds. Sometimes, when I open my phone, it would stay on the black screen even though I never turned it off and it still has battery. So I had to long-press the button to restart. I've already rebooted and shut down numerous times but these problems still persist.
Also, bluetooth doesn't work for me. When I enable it from settings, the "Turn bluetooth on" checkbox stays unchecked and does nothing.
Should I reflash again? I did to a Titanium Backup to restore apps and settings... Any help is appreciated! Thanks.
turkish ?
i wonder if turkish is included or not ?
turnazurna said:
i wonder if turkish is included or not ?
Click to expand...
Click to collapse
With any rom, you should be able to install More Locale 2 from the Play Store to get support for Turkish (and many other languages).
Yakusoya said:
So I've been using your latest release (full wipe Legend v3) and I did factory reset, clear cache and dalvik cache, fixed permissions, etc. The phone is occasionally laggy now, usually when I open web browser it would stay on the white screen a several seconds. Sometimes, when I open my phone, it would stay on the black screen even though I never turned it off and it still has battery. So I had to long-press the button to restart. I've already rebooted and shut down numerous times but these problems still persist.
Also, bluetooth doesn't work for me. When I enable it from settings, the "Turn bluetooth on" checkbox stays unchecked and does nothing.
Should I reflash again? I did to a Titanium Backup to restore apps and settings... Any help is appreciated! Thanks.
Click to expand...
Click to collapse
My bet is the tibu restore of your settings is what is causing the issues, I've had problems and have known others that had problems when restoring system settings with tibu, especially if the tibu backups were done on another rom.
crt60 said:
My bet is the tibu restore of your settings is what is causing the issues, I've had problems and have known others that had problems when restoring system settings with tibu, especially if the tibu backups were done on another rom.
Click to expand...
Click to collapse
I only started using tibu when I had Legend ICS v2 and then I immediately upgraded to v3 using the full wipe ROM. And then I restored all apps and settings. I'll try wipe and re-flash without restoring any settings in tibu. But honestly, I only wanted to backup my widget and screen settings (such as app shortcuts on home screens) but tibu didn't back that up.
Yakusoya said:
I only started using tibu when I had Legend ICS v2 and then I immediately upgraded to v3 using the full wipe ROM. And then I restored all apps and settings. I'll try wipe and re-flash without restoring any settings in tibu. But honestly, I only wanted to backup my widget and screen settings (such as app shortcuts on home screens) but tibu didn't back that up.
Click to expand...
Click to collapse
I would try reflashing to stock, then reflashing the rom again, are you converting to ext4 at all or just using rfs?
crt60 said:
I would try reflashing to stock, then reflashing the rom again, are you converting to ext4 at all or just using rfs?
Click to expand...
Click to collapse
I'm a noob so I don't know what those are. :laugh: But I've only flashed ZEUS final and then Legend ICS v2 and v3. Full wiped and cleared cache on all those flashes.
I've reflashed to stock and then back to Legend 3 without restoring anything. It is all better now, very snappy. The bluetooth can be turned on now but for some reason, it doesn't detect my Jabra headset no matter how many times I scan. But it detects my Macbook Pro...
My girlfriend's Skyrocket starting tonight has been freezing while the screen is locked. It won't wake by pressing the button immediately, but opens briefly after maybe 30 seconds. I pull the battery and restart and it worked fine for about two hours and did it again.
Any ideas? I have her fix permissions but it keeps coming back.
I feel bad because she was fine with stock but I convinced her to let me root it!
Unlocked, rooted, stock rom.
wipe cache and dalvik cache? Any new apps or changes that have been done recently?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
this happens to mine maybe once every two weeks, so it is so few and far between that i dont mind. using nexusmod gb.
whenever it freezes, i hold down the home button to see which apps are running and attempt to close them, but it takes too long and i just yank the battery. the only common app that is always running during every freeze is 'phone'.
jphilippon said:
My girlfriend's Skyrocket starting tonight has been freezing while the screen is locked. It won't wake by pressing the button immediately, but opens briefly after maybe 30 seconds. I pull the battery and restart and it worked fine for about two hours and did it again.
Any ideas? I have her fix permissions but it keeps coming back.
I feel bad because she was fine with stock but I convinced her to let me root it!
Unlocked, rooted, stock rom.
Click to expand...
Click to collapse
Rooting wont freeze your phone, that's something to do with the ROM. Did you make a CMW backup before rooting? If yes, then you can boot into recovery, perform a factory reset 3 times, then wipe cache 3 times, then wipe davlik cache 3 times, then restore from the backup, reboot back to recovery and flash the radio (the ICS radio's ) work with GB so you can chose one from them.
If you haven't made a backup, you can download the stock 2.3.5 rom from sammobile, install it, and then do the update to 2.3.6.
Also dont restore apps, using Titanium backup, it causes issues. You can use superbackup to restore, call logs, sms and contacts, that's what I use.
If you would like to try a ICS rom, you can install Sky ICS 4.2E, there is an update 4.2F but it kept crashing so I am on 4.2E runs butter smooth as the stock GB.
All custom ROMS you can find in the Android Development Section
Unless she is going to run themes on AOSP, she probably won't get much other benefit from root. Sounds like she just wants stable, stock. I learned that lesson the hard way with my wife...every time she ran into a glitch! Otherwise, SkyICS is going to be your best bet for the least problems. My wife has been using it with no complaints... yet.
Sent from my SGH-I727 using xda app-developers app
aviseqdas said:
Rooting wont freeze your phone, that's something to do with the ROM. Did you make a CMW backup before rooting? If yes, then you can boot into recovery, perform a factory reset 3 times, then wipe cache 3 times, then wipe davlik cache 3 times, then restore from the backup, reboot back to recovery and flash the radio (the ICS radio's ) work with GB so you can chose one from them.
If you haven't made a backup, you can download the stock 2.3.5 rom from sammobile, install it, and then do the update to 2.3.6.
Also dont restore apps, using Titanium backup, it causes issues. You can use superbackup to restore, call logs, sms and contacts, that's what I use.
If you would like to try a ICS rom, you can install Sky ICS 4.2E, there is an update 4.2F but it kept crashing so I am on 4.2E runs butter smooth as the stock GB.
All custom ROMS you can find in the Android Development Section
Click to expand...
Click to collapse
SkyICS 4.2F is running far more flawlessly than all other sky roms. The vast majority of users have no issues. It's based on an official release, not a leaked release. Those users with issues are normally at fault, not the rom; and these issues are usually easily fixed.
Don't be afraid of 4.2F.
Using SeanZ's SkyICS 4.2F r2 v6B ROM / XDA Premium
Beginning 4 or 5 days ago, the CM nightlies have become absolutely unusable on my phone. Even after a full clean flash (wipe system/data/cache/dalvik), the first boot will yield multiple force closes, usually including SystemUI and com.android.phone. After a couple reboots these will stop for the most part, but flashing gapps prompts a whole slew of new FCs (pretty much every gapp crashes, along with the accounts manager).
TouchWiz roms, older CM nightlies, and AOKP build 2 all run fine. But I simply cannot get CM to work.
Any ideas?
demonguard said:
Beginning 4 or 5 days ago, the CM nightlies have become absolutely unusable on my phone. Even after a full clean flash (wipe system/data/cache/dalvik), the first boot will yield multiple force closes, usually including SystemUI and com.android.phone. After a couple reboots these will stop for the most part, but flashing gapps prompts a whole slew of new FCs (pretty much every gapp crashes, along with the accounts manager).
TouchWiz roms, older CM nightlies, and AOKP build 2 all run fine. But I simply cannot get CM to work.
Any ideas?
Click to expand...
Click to collapse
I've tried all of the CM10 bases roms and the one that seems to run rock solid for me with zero issues so far is paranoid android, plus I like the things that he cherry picked, I'd give that rom a try as it works super smooth and fast with imo's lean kernel.
natethegreat86 said:
I've tried all of the CM10 bases roms and the one that seems to run rock solid for me with zero issues so far is paranoid android, plus I like the things that he cherry picked, I'd give that rom a try as it works super smooth and fast with imo's lean kernel.
Click to expand...
Click to collapse
That rom actually runs fine for me too, along with anything else based on a CM before ~9/17, but I'd love to know why my phone wont run the newer nightlies.
I have had no issues at all running the CM10 nightlies, works like a champ for me. If you find out what is going on please let us know!
Still having this problem on a clean flash of the 10-04 nightly. Email, gapps, setup wizard, talk, and Play store all chain force close on the first boot.
Your forgetting to format your system in cwm mounts/storage. That's a true clean install. Double check your md5 and try again doing all you did+format system.
Sent from my YP-G70 using xda premium
Hey so I have been having the exact same issue! I flashed back to the M1 snapshot and I'm staying there until this get sorted out. Weird how it's only happening to a couple of us...
Sent from my SCH-I535 using xda premium
Have you guys tried fixing permissions after flashing?
yosterwp said:
Have you guys tried fixing permissions after flashing?
Click to expand...
Click to collapse
So do you think that we should do a full wipe then install, boot, go back into recovery then fix permissions or can we do it without a full wipe?
yosterwp said:
Have you guys tried fixing permissions after flashing?
Click to expand...
Click to collapse
I wiped system, data, cache, and dakvik. Then I installed CM. Then I wiped cache and dalvik, and fixed permissions. Same issues ocurred.
Still having this problem with M2 and the new gapps after formatting and wiping and fixing literally everything.
demonguard said:
Still having this problem with M2 and the new gapps after formatting and wiping and fixing literally everything.
Click to expand...
Click to collapse
What I would do if I were you....
Odin all the way back to stock
Re-root
Re-unlock bootloader
flash cwm
Wipe data/factory reset
wipe cache
wipe dalvik
FORMAT /system <- under mounts
rewipe
install newest cm10
install newest gapps
boot
Odin'ing back and formatting will help wipe out any remnants you may have derp'd along the line somewhere
You should have no issue with these steps. It put me rock solid every single time (along with many many others). Report back and let us know.
Hi all. I've had an issue for a few weeks now. I have apps that are constanly locking up and force closing on my phone. I'm currently running Jelly Beans 11 with a rooted and unlocked GS3.
All different apps force close: gmail, play store, kik messenger, system processes. It seems it's not centralized to gapps for instance.
I've installed Beans 5, 6, 8, 9 once. 10 about 2 times, and version 11 i think 3 times. Each time I do a delvik cache wipe, a cache wipe, and a factory reset via CWM. Some times even the initial setup wizard will lock up after first boot.
I've tried flashing different modems as well, and i'm currently on the newest verizon one, the K3.
If anyone has any information on how to fix this it would be much appreciated. Even a full phone wipe or something... I'm going to try clean rom and CM 4.2 tonight.
In a seperate issue, that may or may not be related:
I'm currently in iraq and i'm using the world phone exploit to get cell service and data here in Baghdad. It used to work great, but now the data connection will be connected, but no data will upload or download for long periods of time. For example i could send a kik message while connected to EDGE network, but it might take an hour for it to actually send. It didn't used to do this...
All things considered i'm wondering if I actually physically damaged the phone somehow...
If I haven't provided enough information, please let me know and i'll be happy to reply.
Ok, i tried CM 4.2 and there weren't any lockups. But i couldn't keep the rom, doesn't seem to be any way to get cell service. it won't let me change the band to global.
Going to try clean rom now.
Clean rom works fine as well...
So why would Jelly Beans ROM, that's worked fine for quite a while for me, through various versions of ICS and JB, to suddenly cause apps to force close and general instability?
I've checked MD5's and they're correct...
I think i still need a few more posts before i can post in the dev section as well.
Any help is appreciated, thanks
Have you tried fixing permissions?
Here's how I flash a rom:
Wipe data/ factory reset
Wipe cache
Wipe dalvic
Format system
Flash rom
Boot the phone, wait 5 min and then wipe cache and dalvic again. I then fix permissions and then boot the phone and profit.
Sent from my SCH-I535 using xda app-developers app
bobAbooE said:
Have you tried fixing permissions?
Here's how I flash a rom:
Wipe data/ factory reset
Wipe cache
Wipe dalvic
Format system
Flash rom
Boot the phone, wait 5 min and then wipe cache and dalvic again. I then fix permissions and then boot the phone and profit.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
+1
fixing permissions is a must after a flash/restore.
ok i'll try installing beans again and using fix permissions afterwards.
Thanks
still not working
Ok, i've tried fixing permissions and i'm still having problems. Gapps has stopped working... System UI has stopped working... I followed the above posts exactly.
Any other suggestions?
Are you flashing gapps or just using that term to describe the apps from Google?
Sent from my SCH-I535 using xda app-developers app
bobAbooE said:
Are you flashing gapps or just using that term to describe the apps from Google?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
gapps was the term that the phone said when it crashed. But no i'm not flashing the gapps, they're included on most of the roms like Jelly Beans 11. I've had a few different gapps force close, like the store and gmail. but i've also had the system ui and kik force close.
Sorry man, it's beyond my knowledge. Never had a bunch of apps stop working that fixing permissions or a clean install didn't fix.
Sent from my SCH-I535 using xda app-developers app
How did Beans build 10 work for you, was that running fine? There are only two things I could suggest since you've tested normal suggestions already:
1) Beans removed a few files from System/Bin on Build 11, these are all included in Build 10. Maybe your phone needs those in order to work properly:
gsiff_daemon
mpdecision
qosmgr
smdexe
This is why I ask was Build 10 working fine for you? If so, maybe pulling these files from the Build 10 zip then putting them into System/Bin, setting permissions as rw r- r-, and rebooting could help. Or it could not.
2) Try flashing with TWRP recovery and see if the FC issue pops up.
SlimSnoopOS said:
How did Beans build 10 work for you, was that running fine? There are only two things I could suggest since you've tested normal suggestions already:
1) Beans removed a few files from System/Bin on Build 11, these are all included in Build 10. Maybe your phone needs those in order to work properly:
gsiff_daemon
mpdecision
qosmgr
smdexe
This is why I ask was Build 10 working fine for you? If so, maybe pulling these files from the Build 10 zip then putting them into System/Bin, setting permissions as rw r- r-, and rebooting could help. Or it could not.
2) Try flashing with TWRP recovery and see if the FC issue pops up.
Click to expand...
Click to collapse
Well I think 10 was when the issue started but i'm not sure anymore. I've flashed so many versions in the past week, from 5 to 11 that i've forgotten. I'll see if I can't do that though and see what happens.
should I do a factory reset? i mean is there an equivelant to formating a hard drive and reinstalling windows that i can do on an android?
Icewolf69 said:
Well I think 10 was when the issue started but i'm not sure anymore. I've flashed so many versions in the past week, from 5 to 11 that i've forgotten. I'll see if I can't do that though and see what happens.
should I do a factory reset? i mean is there an equivelant to formating a hard drive and reinstalling windows that i can do on an android?
Click to expand...
Click to collapse
To be consistent, its best to clean flash (factory reset/dalvik/cache) build 10 just to see if it works fine.
The equivalent to a Windows reinstall would be using Odin to flash a stock image. Using Odin, you would reset your phone back to fresh out of the box, bloated Verizon OTA. I feel that's unnecessary though cuz you flashed CleanRom and had no issues. If you flash another TW JB rom and have no issues, then it's more telling. As of now, something specific in Beans Build 11 (we'll verify b10 soon) is causing issues for you. Are you restoring any apps with Titanium Backup or restoring text messages using another app?
Edit: to detail a little more about the Odin route. After flashing the stock image, then you would need to root, unlock, install a custom recovery all over again and THEN flash Beans build 11. Idk if you want to do all that, esp if you haven't confirmed if this is something that's been happening with prior builds or with other roms.
SlimSnoopOS said:
To be consistent, its best to clean flash (factory reset/dalvik/cache) build 10 just to see if it works fine.
The equivalent to a Windows reinstall would be using Odin to flash a stock image. Using Odin, you would reset your phone back to fresh out of the box, bloated Verizon OTA. I feel that's unnecessary though cuz you flashed CleanRom and had no issues. If you flash another TW JB rom and have no issues, then it's more telling. As of now, something specific in Beans Build 11 (we'll verify b10 soon) is causing issues for you. Are you restoring any apps with Titanium Backup or restoring text messages using another app?
Edit: to detail a little more about the Odin route. After flashing the stock image, then you would need to root, unlock, install a custom recovery all over again and THEN flash Beans build 11. Idk if you want to do all that, esp if you haven't confirmed if this is something that's been happening with prior builds or with other roms.
Click to expand...
Click to collapse
I just did a fresh install of 10, including cache, delvik, factory reset, system partition, and after first boot i went back and fixed permissions. I'm still getting force closes. media service, google play, etc. I don't have many apps on it yet to see what else will force close since i'm not using titanium backup to restore anything. Everything is fresh and coming from the play store...
I should be hitting 10 posts soon so i'll be able to try and post in the beans thread, or the dev section. But any other ideas would be appreciated. Thanks.
I also seem to be getting a lot of "invalid file" and "file couldn't be downloaded" when i try to install apps from the store. Not sure what this means
Beans 12 came out today and I tried installing that and i'm getting the same issue.
Tomorrow i'm going to do a full wipe to stock verizon image. and go through the unlock and root motions unless someone has any more ideas.
Thank you for the help so far, i appreciate it.
I did a complete stock OTA flash last night to verizon's jelly bean, and went through the root and unlock process again. flashed beans 12, and i'm still getting the same error.
I'm on beans 6 right now and it's working great. Going to try changing a few settings in 12 to see if it works and then maybe see if 10 works.
I don't know if I missed a step or not, but every app and settings screen now takes about 20-30 seconds to open, booting takes 3-5 minutes. The phone is set up with the same ROM, kernel, apps, etc. as a few weeks ago when it was running super-fast.
I reflashed this version of CM 11 which had worked perfectly for me for about a month (this is a Samsung Galaxy Blaze S 4G):
cm-11-20150119-NIGHTLY-t769.zip
I was downgrading back to that after trying a nightly that made staticky lines all over my phone and made it lock up constantly...
When I reflashed, here's what I did (after backing up with TiBu):
In recovery I wiped to factory
Cleared the cache and Dalvik cache
Formatted /system and /data
Flashed the zip of CM 11 from my external SD
Flashed the zip of GaPPs from the external SD
Rebooted
Rebooted fine, I installed TiBu and Link2SD and started restoring apps/moving to 2nd SD card partition.
The phone is much much slower than stock. I don't know what the difference is... can someone please give me a checklist to try or tell me what I might have done wrong in the re-flashing process?
kanjigirl said:
I don't know if I missed a step or not, but every app and settings screen now takes about 20-30 seconds to open, booting takes 3-5 minutes. The phone is set up with the same ROM, kernel, apps, etc. as a few weeks ago when it was running super-fast.
I reflashed this version of CM 11 which had worked perfectly for me for about a month (this is a Samsung Galaxy Blaze S 4G):
cm-11-20150119-NIGHTLY-t769.zip
I was downgrading back to that after trying a nightly that made staticky lines all over my phone and made it lock up constantly...
When I reflashed, here's what I did (after backing up with TiBu):
In recovery I wiped to factory
Cleared the cache and Dalvik cache
Formatted /system and /data
Flashed the zip of CM 11 from my external SD
Flashed the zip of GaPPs from the external SD
Rebooted
Rebooted fine, I installed TiBu and Link2SD and started restoring apps/moving to 2nd SD card partition.
The phone is much much slower than stock. I don't know what the difference is... can someone please give me a checklist to try or tell me what I might have done wrong in the re-flashing process?
Click to expand...
Click to collapse
Hi
There are newer versions of CM11 t769 up already.
You should wipe cache and dalvik after restoring your apps. If it doesn't help, make a clean installation of cm and try if the speed is better. Restoring apps via Titanium Backup while using Link2SD can easily cause errors. May be you have reinstall apps without restore. Also new partitioning of your sd card could help.
LS.xD said:
Hi
There are newer versions of CM11 t769 up already.
You should wipe cache and dalvik after restoring your apps. If it doesn't help, make a clean installation of cm and try if the speed is better. Restoring apps via Titanium Backup while using Link2SD can easily cause errors. May be you have reinstall apps without restore. Also new partitioning of your sd card could help.
Click to expand...
Click to collapse
How do I choose a version of CM to use?? This is new to me, just rooted for the first time last month. I don't know how to choose... I was using that one I mentioned above for a month with zero issues, then upgraded to a new nightly, but had to downgrade back due to problems and that was where my issue here started...
I did wipe cache and Dalvik after restoring my apps, and I did repartition my SD card as Link2SD wasn't working for me after reflashing (I got a new beta version of Link2SD from the developer that worked perfectly).
kanjigirl said:
How do I choose a version of CM to use?? This is new to me, just rooted for the first time last month. I don't know how to choose... I was using that one I mentioned above for a month with zero issues, then upgraded to a new nightly, but had to downgrade back due to problems and that was where my issue here started...
I did wipe cache and Dalvik after restoring my apps, and I did repartition my SD card as Link2SD wasn't working for me after reflashing (I got a new beta version of Link2SD from the developer that worked perfectly).
Click to expand...
Click to collapse
The CM11 builds are sorted by date. Newest build CLICK HERE are always on the top. Latest is 02/23. Keep in mind that CM is still under develpoment and may not run stable.
LS.xD said:
The CM11 builds are sorted by date. Newest build CLICK HERE are always on the top. Latest is 02/23. Keep in mind that CM is still under develpoment and may not run stable.
Click to expand...
Click to collapse
Should I pick the newest build then, and reflash with that? I see there's a stable one for CM 10 for my phone, but it's from 2012...
Should I go with something other than CM? I'm just confused at this point. I like Kitkat and would like to stay with that if feasible (my stock phone was ICS).
kanjigirl said:
Should I pick the newest build then, and reflash with that? I see there's a stable one for CM 10 for my phone, but it's from 2012...
Should I go with something other than CM? I'm just confused at this point. I like Kitkat and would like to stay with that if feasible (my stock phone was ICS).
Click to expand...
Click to collapse
I haven't tested the builds as i don't have the phone, its usefull to read the CM11 thread for your phone to check out bugs. You can try newer builds, but theres no guarantee that everything works. All in all you should go for newer versions from time to time
LS.xD said:
I haven't tested the builds as i don't have the phone, its usefull to read the CM11 thread for your phone to check out bugs. You can try newer builds, but theres no guarantee that everything works. All in all you should go for newer versions from time to time
Click to expand...
Click to collapse
Hmm. My build was stable, I upgraded to a new one, and my phone stopped working. Going back isn't working either.
CM 10.0 is listed as a stable release, I'm wondering if that would be better (i.e. less time spent wiping and reflashing repeatedly) than a new nightly for CM 11?
kanjigirl said:
Hmm. My build was stable, I upgraded to a new one, and my phone stopped working. Going back isn't working either.
CM 10.0 is listed as a stable release, I'm wondering if that would be better (i.e. less time spent wiping and reflashing repeatedly) than a new nightly for CM 11?
Click to expand...
Click to collapse
CM10 = Android 4.1.2
CM10.1 = Android 4.2.2
CM10.2 = Android 4.3.1
CM11 = Android 4.4.4
CM12 = Android 5.0.2
CM10 means you have NO bugs, everything runs stable at the cost that you have a really old rom. If you don't like maintain your phone continuisly its a good choice. I really like trying new stuff, so i flash nearly every new build of used roms / kernels for my phones. So I would stay at CM11. But thats just my personal opinion. By the way you don't need to create backups with Titanium Backup all the time. Just make a backup with your recovery. After installing a new rom, use Titanium Backup with the option "Extract from nandroid backup" to restore your apps. On previous phones I also used tools like Link2SD or Int2Ext, but after some time it always caused problems and never ran 100% stable and fast, so think about if you really need it.
LS.xD said:
CM10 = Android 4.1.2
CM10.1 = Android 4.2.2
CM10.2 = Android 4.3.1
CM11 = Android 4.4.4
CM12 = Android 5.0.2
CM10 means you have NO bugs, everything runs stable at the cost that you have a really old rom. If you don't like maintain your phone continuisly its a good choice. I really like trying new stuff, so i flash nearly every new build of used roms / kernels for my phones. So I would stay at CM11. But thats just my personal opinion. By the way you don't need to create backups with Titanium Backup all the time. Just make a backup with your recovery. After installing a new rom, use Titanium Backup with the option "Extract from nandroid backup" to restore your apps. On previous phones I also used tools like Link2SD or Int2Ext, but after some time it always caused problems and never ran 100% stable and fast, so think about if you really need it.
Click to expand...
Click to collapse
Ack. Well... I like Kitkat a lot. I might get the latest CM11 nightly and new GAPPS and try that first.
I have so little memory, kept running out of space and that's why I use Link2SD. But thanks for the advice on TiBu, I did make a Nandroid backup last night from CWM.
kanjigirl said:
Ack. Well... I like Kitkat a lot. I might get the latest CM11 nightly and new GAPPS and try that first.
I have so little memory, kept running out of space and that's why I use Link2SD. But thanks for the advice on TiBu, I did make a Nandroid backup last night from CWM.
Click to expand...
Click to collapse
PA GApps are quite good and still up-to-date. Use "PICO" to save some space.
LS.xD said:
PA GApps are quite good and still up-to-date. Use "PICO" to save some space.
Click to expand...
Click to collapse
That looks great, thanks very much!
I'll post back here once I get my phone straightened out in the next couple of days to say what happened, in case it helps someone later.
Possibly stupid question - do I need to do anything with the kernel or pit if I'm just installing a new ROM? That was only for rooting, right?
kanjigirl said:
Possibly stupid question - do I need to do anything with the kernel or pit if I'm just installing a new ROM? That was only for rooting, right?
Click to expand...
Click to collapse
Kernel is always included in the new "rom". So everytime you flash a rom, you automatically flash the kernel with it. PIT is the partition table of the phones partition. As long its not clearly necessary, DON'T ever change it!
Got it, thank you for your help!
So last night I wiped the phone and flashed the latest CM 11 (from yesterday) and the Pico package from PA-GApps. The phone is now super-fast again. I restored a few key apps to try out for the next day or so before restoring the rest, but so far so good, everything is back to normal. Thank you so much for the help.
kanjigirl said:
So last night I wiped the phone and flashed the latest CM 11 (from yesterday) and the Pico package from PA-GApps. The phone is now super-fast again. I restored a few key apps to try out for the next day or so before restoring the rest, but so far so good, everything is back to normal. Thank you so much for the help.
Click to expand...
Click to collapse
Sounds great
Quick question - if this thread is still open. The phone's been fine since I flashed CM 11 and Pico GApps, until this morning, when it now does 'Android is Upgrading' every time I boot and every user app crashes as soon as it's opened. I have all auto-syncs and auto-updates disabled, and haven't added any user apps to the phone since Wednesday.
Do I need to flash again, and then have to go through the restore process all over? Or could it be an app causing this? I'm not sure where to look for a source of the problem.