Database Info

Asus transformer tf101 going crazy

I have transformer tf101 (Honeycomb 3.2.1 + 16GB + Dock) that I purchased in August 2011. For first 6 months I was on stock ROM and everything was working fine. After that I flashed Android Revolution HD 2.2.0 on my tablet and then it started behaving crazily . Whenever I open browser it will automatically start zooming in/out, scrolling. It will totally go haywire and will start clicking left/right.
I searched on net and found that some of other unlucky guys are facing the same issue . I have attached a .txt file that contains the link to you tube video depicting the problem.
I have tried many ways such as using superwipe script and then reinstalling the ROM's. Even, I have tried with new ROMS(ICS one's) that are there but still the problem does not seem to go away. I have searched a lot but could not find the solution to this issue. Can somebody please guide me how to get rid of this problem. I believe this is the best android forum where I am hoping that someone will help me with this problem.

This is really basic but have you tried cleaning the screen?
Other then that, have you tried going back to a HC rom and see if you don't have any issues. I understand you want the latest and greatest version rom but to determine a fix and narrow down the problem maybe you should try all the alternatives.

Thanks for replying. I had cleaned up my screen and there was not a single app/widget on my homescreens. I flashed back to HC ROM but still the problem persist . I have tried all ways of flashing th ROM's but still the problem doesn't seem to go away. I have not tried the stock ROM for HC that came with my tablet (i didn't take the backup when I flashed new ROM).
Looking at the issue it seems to me as if this problem is software related rather than the hardware.If this would have been hardware related then I should have got this on day1 of my purchase.

stryke504 said:
This is really basic but have you tried cleaning the screen?
Click to expand...
Click to collapse
I think he meant literally "clean the screen." Like with a towel and some cleaner.

typci said:
I think he meant literally "clean the screen." Like with a towel and some cleaner.
Click to expand...
Click to collapse
And dont forget to wash your hands (Im serious, that actually affects the responsiveness of the screen)

I cleaned my screen (Literally ). The problem is still there . Can it be because of the browser. I am currently using Dolphin HD browser for my browsing. I will probably install stock browser and will check with it.

Your text file is rubbish too...no link, it's actually the HTML code for an error 404..which is funny.......not only is it not a working link, or even a link at all, it's a 404 in HTML..LMAO

Sorry for the bad attachment. I have the link.doc containing the link.

Yesterday, I tried with the stock ROM and everything was working fine till the point I connected my tablet to Wifi and upgraded my Google Market to Play store. As soon as the app was updated the same problem started recurring. Now I have uninstalled the updates for google play store but the problem is still there. But the good part is that the frequency of the random zooming/clicking has decreased and it happens in browser only. Earlier it was happening in all the apps. Can somebody please direct me to the link to US stock ROM (for HC 3.2.1). As of now I am running WW_ stock rom. I just want to try out the same with US_ stock ROM as well.

First of all, don't use super wipe script. Just wipe normally with CWM.
Do these options in CWM
1. factory reset/wipe data
2. clear cache partition
3. wipe dalvik cache
4. mounts and storage -> format /system
5. mounts and storage -> format /data (this is done by factory reset but just to be sure)
Get the official ICS rom from Asus' website. US or WW doesn't matter.
Flash it with CWM after doing the wipe procedure above.
Don't let google sync or anything restore any kind of back up.
If the same problem happens again, you got a problem that requires RMA.
Honestly it already sounds like you need to RMA but you should make sure before wasting money and time on RMA.

I will try these steps today. I never did these 2 steps while flashing ROM's
1. clear cache partition
2. wipe dalvik cache
I am just curious to know as to how this problem started when it was not there till the point I flashed a custom ROM.
I have a big problem with RMA. I purchased my tablet in US and so it has North American Warranty. I am not residing in US. Thus for RMA, I have to ship my tablet back to US which will be expensive as well as an overhead . So I am planning of trying all the possible steps before I have to ask the Asus support in my native country. Please let me know if you know any stable version of Stock ROM. I read and found that some of the stock ROM's are having serious issues with Wifi/GPS etc.

harshbedi said:
I am just curious to know as to how this problem started when it was not there till the point I flashed a custom ROM.
Click to expand...
Click to collapse
Something could have gone bad during flashing.
What version of CWM are u using?
---------- Post added at 07:55 AM ---------- Previous post was at 07:51 AM ----------
harshbedi said:
I will try these steps today. I never did these 2 steps while flashing ROM's
1. clear cache partition
2. wipe dalvik cache
Click to expand...
Click to collapse
YOU HAVE TO DO THOSE. Wipe dalvik cache is under Advanced.

I am using CWM 3.2.0.1 for recovery.
I am just hoping that it should be software/flashing issue.I just don't want to go for RMA .

harshbedi said:
I am using CWM 3.2.0.1 for recovery.
I am just hoping that it should be software/flashing issue.I just don't want to go for RMA .
Click to expand...
Click to collapse
i would first get on the newest version of recovery:
http://forum.xda-developers.com/showthread.php?p=16557195
it is touch based, but i just went into cwm and the regular method of volume and power keys work fine. AND you have to store the rom on the internal sd card in order to flash, it can't access the external card once you update.
and personally i'd wipe EVERYTHING like 3 times seems kinda of the standard.. i'm super ocd so i wipe it all 5 times before i flash.. might want to pick up an ASOP rom like
EOS:
http://forum.xda-developers.com/showthread.php?t=1520764
or KANG:
http://forum.xda-developers.com/showthread.php?t=1542302
see how that works.. could always pick up the stock ASUS rom though
FYI: to flash those new EOS and KANG roms you NEED to be on that version of cwm i linked

I have tried with various ROM's that are there in Development section but the problem does not seem to go away. I will upgrade my CWM and will check with stock ROM first. Once this is done then I will go for other versions of ROM's.
Just a quick question, for flashing the stock ROM for ICS i.e 9.2.17, I have to download the firmware from ASUS website and then flash it normally the way we do for other ROM's ?

harshbedi said:
I have tried with various ROM's that are there in Development section but the problem does not seem to go away. I will upgrade my CWM and will check with stock ROM first. Once this is done then I will go for other versions of ROM's.
Just a quick question, for flashing the stock ROM for ICS i.e 9.2.17, I have to download the firmware from ASUS website and then flash it normally the way we do for other ROM's ?
Click to expand...
Click to collapse
All this could have been caused by you never wiping cache and dalvik cache.
Yea, download the ICS firmware from Asus website. It will be in a zip. You extract it once. It will have another zip. That's the flashable zip.
You flash it in CWM like you would do for any other ROM.

Yes, I never wiped cache and dalvik cache.
I will check this today and will post my observations. I am keeping my fingers crossed and hoping that this should solve the problem.
Thanks for the info.

Thanks horndroid for the lovely info...It worked.
I cleared the cache and dalvik cache and then I flashed the new revolution 3.2.0 (ICS) Rom and as of no complaints. I have been using the tablet continuously for last 3-4 hours and no issues as of now. I am hoping that it continues to work the way it is functioning right now. I am loving my transformer again . I will use it for few more hours and will update my observations. I am still keeping my fingers crossed.
Moreover, Revolution 3.2.0 is awesome(Thanks to Mike and his team). Very stable and the GPS is awesome. Sitting in my room it acquired my position(No Wifi) within seconds.

horndroid said:
YOU HAVE TO DO THOSE. Wipe dalvik cache is under Advanced.
Click to expand...
Click to collapse
Yes. This is worth pointing out again and again.
Most roms (in my experience) wont even boot unless you wipe cache and dalvik.
And the roms that do boot runs like ****.

Now I have used my tablet for 16 hours..No issues..Running perfectly fine. I believe wiping cache has solved the issue.
I was reading about dalvik cache and came to know that during boot Android always create this cache (if it is not there). So if this problem comes again, can I wipe the cache and dalvik cache without flashing a new ROM. Is this advisable?

[Q] Hyperdrive rls13

Im running hyperdrive rls12, and i dont have enough posts to put this in the appropriate section, however i need to know if i can avoid a full factory reset when flashing rls13, since it is the same rom and all. any help would be appreciated!

katrais said:
Im running hyperdrive rls12, and i dont have enough posts to put this in the appropriate section, however i need to know if i can avoid a full factory reset when flashing rls13, since it is the same rom and all. any help would be appreciated!
Click to expand...
Click to collapse
As with most roms, it's ALWAYS a good idea to do a factory reset & wipe caches before installing. In fact, the dev recommends doing it 3x to ensure proper installation and minimal problems. I always wipe everything before installing a new release, but that's just me. You can use apps like "Titanium Backup" to backup your apps before you wipe if you don't wanna re-download everything. Btw, rls13 is AMAZING!

daniverse said:
As with most roms, it's ALWAYS a good idea to do a factory reset & wipe caches before installing. In fact, the dev recommends doing it 3x to ensure proper installation and minimal problems. I always wipe everything before installing a new release, but that's just me. You can use apps like "Titanium Backup" to backup your apps before you wipe if you don't wanna re-download everything. Btw, rls13 is AMAZING!
Click to expand...
Click to collapse
i dont understand the difference from rls 12 in the changelog

[Q] NS4G: How to start from scratch? And other questions...

Had a bit of trouble trying to do this last night, which resulted in a few hours lost sleep. I went formatting everything in CWM and realized after the fact, I also formatted the internal SD card. Luckily ADB worked in transferring the zip (learn something new every day).
Anyway, after all said and done, all my apps were still on the phone. This is after formatting and new ROM...
How can I truly start from scratch to make sure this new ROM is 100% fresh and free of any unnecessary apps from previous ROMs?
Also, what would be the best current radio and link to said radio?
TIA
EDIT: I had just realized the issue with Factory Reset/Wipe Data. This one I had forgot to mention as I could never use it as all options said no and the menu was not scrollable. Just decided to try and use the volume buttons and sure enough there was more to scoll to.
That said, would the following be a proper procedure to follow;
Wipe Data/Factory reset
Wipe Cache
Format: System, Data, Cache, Boot
Wipe: Dalvik then Fix Permissions
Install order: Rom first, Gapps second, Kernel last
Reboot
???

nimrod.sixty9 said:
Had a bit of trouble trying to do this last night, which resulted in a few hours lost sleep. I went formatting everything in CWM and realized after the fact, I also formatted the internal SD card. Luckily ADB worked in transferring the zip (learn something new every day).
Anyway, after all said and done, all my apps were still on the phone. This is after formatting and new ROM...
How can I truly start from scratch to make sure this new ROM is 100% fresh and free of any unnecessary apps from previous ROMs?
Also, what would be the best current radio and link to said radio?
TIA
EDIT: I had just realized the issue with Factory Reset/Wipe Data. This one I had forgot to mention as I could never use it as all options said no and the menu was not scrollable. Just decided to try and use the volume buttons and sure enough there was more to scoll to.
That said, would the following be a proper procedure to follow;
Wipe Data/Factory reset
Wipe Cache
Format: System, Data, Cache, Boot
Wipe: Dalvik then Fix Permissions
Install order: Rom first, Gapps second, Kernel last
Reboot
???
Click to expand...
Click to collapse
The method I follow is
1. Wipe Data/Factory Reset (this takes away all your downloaded apps?
2. Wipe system/cache/dalvik (this wipes everything else)
3. Flash ROM, Gapps, Kernel
The thing with android is, even if there are some files left over from the previous ROM, they'll get overwritten with the ones from my new ROM, taking them away regardless. The reason you wipe everything to make sure there aren't any files that won't get overwritten. So basically, wipe everything and flash, and you'll have a fresh new ROM also you don't need to fix permissions after you wipe everything because they'll be no permissions to fix! Lol
Sent from my Nexus S 4G using Tapatalk 2

beneath-a-burning-turtle said:
The method I follow is
1. Wipe Data/Factory Reset (this takes away all your downloaded apps?
2. Wipe system/cache/dalvik (this wipes everything else)
3. Flash ROM, Gapps, Kernel
The thing with android is, even if there are some files left over from the previous ROM, they'll get overwritten with the ones from my new ROM, taking them away regardless. The reason you wipe everything to make sure there aren't any files that won't get overwritten. So basically, wipe everything and flash, and you'll have a fresh new ROM also you don't need to fix permissions after you wipe everything because they'll be no permissions to fix! Lol
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Thank you, good sir! Now running nice and clean!
Still need that newest radio if ya know it.

nimrod.sixty9 said:
Thank you, good sir! Now running nice and clean!
Still need that newest radio if ya know it.
Click to expand...
Click to collapse
I don't know it offhand but its probably somewhere on the development forums. I just noticed I said "my new rom" in my original post, I meant "the new rom" just in case you were a little confused (probably not but that would've annoyed me if I didn't address it)
Sent from my Nexus S 4G using Tapatalk 2

beneath-a-burning-turtle said:
I don't know it offhand but its probably somewhere on the development forums. I just noticed I said "my new rom" in my original post, I meant "the new rom" just in case you were a little confused (probably not but that would've annoyed me if I didn't address it)
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Newest radio I can find is from last year. Maybe that the newest. I know for certain signal and data is a million times better. However, I still have no 4g
And Im having an issue I ned to report about the ROM but XDA wont let me post... :crying:

[Q] Wondering what to expect by an overwrite of a ROM?

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.

[Q] Phone is incredibly slow after re-flashing CM 11

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.