I was tinkering with my TF101 and sort of accidentally (lol) overwrote my installation of Timduru's KatKiss-4.3.1_029.zip with his KatKiss-4.4.2_016.zip without wiping anything before doing so. (Actually didn't have any data to speak of - as I formatted and wiped in proper fashion on the install of KatKiss-4.3.1_029), and it hadn't been run for more than a couple of days.
I've developed a severe addition to ROM experimentation, and so may install and backup every few days it seems. Don't have a nickname for that habit yet, but I sense that they are many similar addicts around this site.
What I would like to know, since all seems, at least to this n00b, to be just fine - what "might" happen w/ my TF101 since the overwrite of a newer ROM?
Staying put, until I hear from a forum guru, or at least anyone with more experience than me (and that will include most all members).
Thanks,
Cal
If you overwrite a ROM with a different one (different android version, or by a different developer) you may run into issues where it will not boot, or it may run poorly, random reboots, sleep o death.
When changing ROMs it is HIGHLY recommended to wipe the system, caches and the data partition (wiping data is not the same as FORMAT DATA in TWRP). There are some system settings stored in the /data/ partition that may conflict with different ROMs.
Most of TimDuru's KatKiss ROMs you can forward flash (even to new versions of Android) but you CANNOT go backwards. I flashed from 4.2.2 to 4.3 without wiping data and had no issues. However, if you tried to flash from 4.3 to 4.2.2 without wiping data, it will not boot until you wipe the data partition.
I have not tried this with the 4.4 version of his ROM (I am still on 4.3 for now.)
Oh, and yes, the addiction is called CrackFlashing.
Always ALWAYS make a backup in TWRP before flashing a new ROM or even an upgrade to the current ROM. If you want to go back to 4.3, make a backup and then use Titanium Backup Pro version to extract any apps and data from the 4.4 version and restore to 4.3. Do not restore any system settings or apps.
frederuco said:
<snipped a bit>
When changing ROMs it is HIGHLY recommended to wipe the system, caches and the data partition (wiping data is not the same as FORMAT DATA in TWRP). There are some system settings stored in the /data/ partition that may conflict with different ROMs.
Most of TimDuru's KatKiss ROMs you can forward flash (even to new versions of Android) but you CANNOT go backwards. I flashed from 4.2.2 to 4.3 without wiping data and had no issues. However, if you tried to flash from 4.3 to 4.2.2 without wiping data, it will not boot until you wipe the data partition.
Oh, and yes, the addiction is called CrackFlashing.
Always ALWAYS make a backup in TWRP before flashing a new ROM or even an upgrade to the current ROM. <some stuff snipped>
Click to expand...
Click to collapse
Ahh...then the addiction is obviously not curable unless one destroys the tablet, BUT the new ROM may be just fine as is, I take it. That was what I was hoping to hear.
Thanks, and any idea when a new experimental ROM will come from Tim? Just felt a slight twitch. I've tried the other team's creations and seem to only feel really satisfied with Kits - (guess 'CrackFlashing' addiction picks a really hard one to withdraw from).
Many thanks!
Cal
Cal-123 said:
Ahh...then the addiction is obviously not curable unless one destroys the tablet, BUT the new ROM may be just fine as is, I take it. That was what I was hoping to hear.
Thanks, and any idea when a new experimental ROM will come from Tim? Just felt a slight twitch. I've tried the other team's creations and seem to only feel really satisfied with Kits - (guess 'CrackFlashing' addiction picks a really hard one to withdraw from).
Many thanks!
Cal
Click to expand...
Click to collapse
I think it will be a while until timduru starts to work in a experimental rom , since there is no Android 5 yet.
But Tim has marked katkiss as stable and for my daily use it is. But you could try 4.4.2.
schwigi said:
I think it will be a while until timduru starts to work in a experimental rom , since there is no Android 5 yet.
But Tim has marked katkiss as stable and for my daily use it is. But you could try 4.4.2.
Click to expand...
Click to collapse
Read the original post again -- I've been on the 4.4.2_16 forever now it seems!! The urge to try something new is over-bearing! :silly: :victory:
Ah-Ha! I see that Tim's put up a new 'stable' one. KK 4.4.2_17! Yeah!! This should be a super easy fix for the 'crack-itis' I have developed...as I will overwrite this one also.
Related
I had my tablet set up a certain way, etc..
I went ahead and installed prime and the OC kernel.
I go ahead and boot it up and it came up looking the same as before. I do have the Prime kernel in the settings section and I was able to OC it.
So I assume that I dont have to worry anymore about the whole rom being replaced now?
your question is a bit vague.
are you asking if you will lose your data if you install new roms? no you will not lose you data.
unless the rom installation instructs you to do a factory reset, you'll typically end up with your data intact. (this includes your user data, user apps, and desktops,etc)
Well, what I mean is I expected to lose all of the data, apps, desktop etc.
And it looked exactly the same as before.
I guess I just wanted to make sure that I did it correctly and the result is correct..
if you didn't wipe anything you don't lose anything so it would look the same yes
if you want it to 'look' different then you have to theme it.
custom ROMs mostly change how the rom works with custom modified files and different versions of system files.
ROM modder usually don't change the UI components unless it is something useful
I would have thought that Flashing a custom ROM would wipe whatever you had installed before completely.
When I flash my phone there is nothing left from the previous install.
magicdave26 said:
I would have thought that Flashing a custom ROM would wipe whatever you had installed before completely.
When I flash my phone there is nothing left from the previous install.
Click to expand...
Click to collapse
If you don't wipe data you don't loose anything. its important to wipe just in case a setting is not compatible with something on the new rom. With that said since all these rom still all base on the stock rom you might get away with flashing and no wipe, not recommended.
Now on a phone where its truly custom and stuffs get ported, full wipe is a must going from one rom to another.
magicdave26 said:
I would have thought that Flashing a custom ROM would wipe whatever you had installed before completely.
When I flash my phone there is nothing left from the previous install.
Click to expand...
Click to collapse
Everything a ROM does on installation is up to the dev. They choose whether the script will format system and data partitions or not. Phone devs add the formatting in the scripts because phones constantly have new bases and ports, and people are typically too dumb to understand the concept of "always wipe". With these tablets, there are no ports and very few ROM bases, so wipes are not really required since most people are flashing different ROMs that are based off the same version stock ROM.
I've seen older threads saying that, if you're updating a custom ROM with a new version, usually you will need to clear the caches and re-flash or possibly do a clean wipe.
I have RaymanFX 0.5.0 (which will be updated soon), so I'm wondering if, for an update, I need to do a data wipe or if just clearing the caches and re-flashing is sufficient.
Thanks.
The rule of thumb for upgrading is this:
If you're upgrading within a rom (say RaymanFX 0.5.0 to RaymanFX 0.6.0) then wiping cache/dalvik cache is generally enough. I'd also suggest wiping/formatting the /system folder too, but that's up to you.
If you're upgrading to another rom (say RaymanFX to EOS4) then you should fully wipe/factory reset your device.
The exception to the rule would be upgrading within a rom that changes from android 4.1.x to 4.2.x. In that case you should also fully wipe/factory reset.
Your mileage may vary but this is what's always worked for me. A full wipe each time for every upgrade is the best thing you can do, but it's not needed and means you spend a lot more time re-installing stuff (which I'm guessing is why you are asking).
Thanks, grgmre. That's what I expected. And, yes, I was asking precisely because of reinstalling apps. After I flashed 0.5.0 and played with it for a few hours, I reinstalled most of my apps. I'll install them a bit more slowly after I flash the upgrade or a different ROM.
As easy as it is, it's actually tempting to flash and try out more ROMs.
i have CM10 and android 4.1.2 on my one x (att), i want to upgrade to 4.2.2.
if i install the new rom and gapps do i need to flash a new boot.img or will the one i have still work?
also what is the best way to restore my settings to the new version? i spent lots of time setting this phone up with and and i'd prefer to migrate as much as possible. I would appreciate if if you treated me as a newbie with the migration and are descriptive in your response as i have never done this before.
TIA
You can probably find out more about upgrading from CM10 to 10.1 by looking through the 10.1 thread. I'm almost entirely a Sense person, so I can't speak specifically to this situation (moving from CM10 to 10.1). But seeing as you are moving from one Android build to another, I'd assume you need to treat it as moving to a "new" ROM. I would also bet that you need to flash boot.img again. It only takes a minute to do, so why bother even trying to skip that step?
In general, if moving from one ROM to another, you should wipe user data, and not migrate system data, and migrate as few settings as possible. Migrating system data is almost sure to cause serious bugs, and migrating settings can be problematic also.
Recommend using Titanium Backup to migrate apps and data (but not system data), and if you get the paid version, its well worth the couple dollars to get the batch function (can backup and restore all your user apps with just a couple taps).
Do any other backing up you want to do (I like to backup my text messages by using the app SMS Backup+). And if you like, use TWRP to make a nandroid backup, in case you want to revert to your current ROM.
Then before flashing CM10.1 factory reset only within TWRP (factory reset in hboot will corrupt your SD card). Factory reset will wipe any user data (but should leave the internal SD untouched). So be sure to backup anything you want to keep, beforehand. Then wipe Dalvik and cache, also within TWRP. Then flash the ROM, boot.img and gapps. Then startup the ROM, restore your apps with Titanium. Then setup your homescreen and settings to your liking. Some people also like to migrate WiFi and Bluetooth pairings (I think Titanium will do it). Especially handy if you have a lot of pairings. But I don't have many pairings, and migrating them never seemed to work right for me, so I just do it manually.
Really, setting up from scratch is not that hard. With the help of Titanium, I can be back up and running in about 20 minutes.
You shouldn't have to flash a new boot just flash the new Rom over the old one. As long ast there there both cm something your good. But make a backup in recovery just on case
Sent from my HTC One X using xda premium
Arrow44 said:
As long ast there there both cm something your good. But make a backup in recovery just on case
Click to expand...
Click to collapse
I don't think you mean that literally. If you were to go from CM9 to CM10, and not flash the kernel, I don't think that would work.
Even going from CM10 to CM10.1, it would require the kernels being the same, or at least similar enough to not cause any problems. Have you tried this yourself, or read others tried it on the CM thread?
Are you sure you aren't thinking of just going from one nightly to another?
Also assume the OP is hboot 1.14 or higher, and S-on. Otherwise flashing boot.img separately is not an issue at all.
redpoint73 said:
I don't think you mean that literally. If you were to go from CM9 to CM10, and not flash the kernel, I don't think that would work.
Even going from CM10 to CM10.1, it would require the kernels being the same, or at least similar enough to not cause any problems. Have you tried this yourself, or read others tried it on the CM thread?
Are you sure you aren't thinking of just going from one nightly to another?
Also assume the OP is boot 1.14 or higher, and S-on. Otherwise flashing boot.img separately is not an issue at all.
Click to expand...
Click to collapse
thanks for the relies, i backed it all up this morning and tried to flash the latest nightly and the htc screen just hung, so im guessing i need to flash the boot.img, i need to do that home where i have the android sdk tools installed.
as far as migrating the data, im guessing that's not practical with what appears to be two separate builds... sigh, the 10.1 night came out a week after installed cm 10. oh well at least im not still waiting for slow ass ATT to get me the update.
mike_311 said:
thanks for the relies, i backed it all up this morning and tried to flash the latest nightly and the htc screen just hung, so im guessing i need to flash the boot.img, i need to do that home where i have the android sdk tools installed.
as far as migrating the data, im guessing that's not practical with what appears to be two separate builds... sigh, the 10.1 night came out a week after installed cm 10. oh well at least im not still waiting for slow ass ATT to get me the update.
Click to expand...
Click to collapse
Sorry I come from sense based roms but I have a feeling you haven't heard of flash gui. http://forum.xda-developers.com/showthread.php?t=1453617
Sent from my HTC One X using xda premium
Hi there. I'm new to tweaking Android, but have gotten quite busy the last few days. I'm sorry if these questions have been asked before. I have Googled and searched around; there are answers to be found, but they contradict one another and some . appear to be outdated. I'm having trouble getting an up-to-date and accurate understanding of these things. So I hope some of you are willing to help this newbie out.
I've unlocked the bootloader and rooted my Nexus 5. I kept using Stock Android 4.2.2. for some time and had a fair amount of apps and settings installed. Then I felt curious and started experimenting with some of the roms. I bought Titanium Backup to streamline the setup.
I installed TWRP and wiped everything (including Dalvik cache), then flashed the latest Paranoid Android beta. Afterwards I used Titanium Backup to restore my apps, and it's all working fine, as far as I know.
1. I was wondering about the following. Is there any harm in restoring apps with TB to a different rom (PA) to the one you came from and made the original backup on (Stock)? Google results were remarkably ambivalent, some saying it should be avoided because it slows things down eventually, others saying it doesn't matter at all.
2. Another question: I've been reading up on kernels. The Franco kernel seems like a good option and apparently it goes together quite well with Paranoid Android (which, if I'm not mistaken, leaves stock kernel intact?). Is it necessary to Dalvik- or even system-wipe before flashing it? Online opinion seems to be divided on this.
3. And on that matter: why is doing a Dalvik cache wipe before flashing anything so important? Some websites even advise to do it multiple times, even though TWRP ensures once it quite enough? If the Dalvik cache rebuilds itself post-wipe on the first next boot anyway, is there any significant difference between doing it before or some time after? What am I missing?
I hope someone might shed some light on this. Thanks!
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.