Develop Bugs

HELP! I rooted my phone and not touchwiz is gone

Hello,
Last night I rooted my device using this (http://forum.xda-developers.com/showthread.php?t=1265429) method and file from zedomax and everything worked great except when I booted my device there was a yellow triangle with a black “!” in it. I figured that just indicated the device was rooted or running a 3rd party kernel so I didn’t worry about it.
Today I launched my camera app and it failed to load the interface but showed the image from the camera momentary then crashed back to the home screen. I restarted my device and when the device restarted it was very slow and unresponsive and after unlocking it my live wallpaper was gone replaced with the last background I used before selecting a live background a couple weeks back. No icons or widgets loaded and I am unable to open the settings tray. The only things I am able to do with the phone is pull down the notification bar, respond to text messages, adjust the volume and hold power to restart the phone. All of which are very slow and delayed.
When I connect the device to my computer windows is no longer able to load the drivers and Kies is unable to connect with the device. I am not sure what caused this or how to resolve this issue so any advice or known fixes would be fantastic! I am unable to get to clockwork mod to restore my backup and I am unable to get to Kies or the phone settings to do a factory reset so I really don’t know what to do they were supposed to be a last resort and now I don’t even think I can do them. I am an experienced techie but I am new to android and this is the first device I have rooted so any advice would be great no matter how basic it may be.
UPDATE: I just connected the phone via USB to my laptop at work and it was able to discover and install everything it needed to connect with the phone. I am installing Kies now so at least there is hope of a factory restore, although I really hope it doesn't come to that!

Boot into download mode and flash the stock eg30 tar file from crawrj.
Sent From My Evo Killer!!!

Thanks Already started doing that waiting for it to download now

Still no touchwiz... great!

Try flashing a stock rom via clockworkmod.

efarley said:
Still no touchwiz... great!
Click to expand...
Click to collapse
You can root again and restore your backup, or go to this website www.lostandtired.com (midnight roms blog) click on android development and download and flash the sprint bloat and TW restore zip. Hope that helps.

I flashed the stock rom which didn't change anything so then I used clockworkMod to do a factory reset which ended up trapping me into a boot loop. I could use Odin to flash new roms but the device would never go past the 4G logo
I ended up taking the device back to Best Buy and since the loading screen showed the stock rom and they couldn't get past the 4G logo I just had to say it wasn't rooted and they gave me a new one.
I would love to know if anyone has any idea of what went wrong here so that I can feel comfortable rooting again. Also if anyone has some basic articles handy that teach basics of rooting that would be great, I didn't even know about clockwork mod until after I had this problem so knowing things like that earlier would have helped a lot I think. I'll be spending the weekend looking up everything I can find on the subject so any reading you guys can suggest would be fantastic.

efarley said:
I flashed the stock rom which didn't change anything so then I used clockworkMod to do a factory reset which ended up trapping me into a boot loop. I could use Odin to flash new roms but the device would never go past the 4G logo
I ended up taking the device back to Best Buy and since the loading screen showed the stock rom and they couldn't get past the 4G logo I just had to say it wasn't rooted and they gave me a new one.
I would love to know if anyone has any idea of what went wrong here so that I can feel comfortable rooting again. Also if anyone has some basic articles handy that teach basics of rooting that would be great, I didn't even know about clockwork mod until after I had this problem so knowing things like that earlier would have helped a lot I think. I'll be spending the weekend looking up everything I can find on the subject so any reading you guys can suggest would be fantastic.
Click to expand...
Click to collapse
If you a clockwork and "stock rom" you were still rooted...Doing a factory reset will send you into bootloop when rooted. Trying to flash other roms on a bootloop is not going to work. You need to have grabbed a backup such as Zedo has on his post and put the backup in clockwork folder on your phone. Then flash that in CWM. Would of brought you out of bootloop to a stock rom with his kernal. Now you can flash Roms and kernals or could of flashed crawf or anyone else FULL stock rom and been back to stock kernel and rom and not rooted.

dallastx said:
If you a clockwork and "stock rom" you were still rooted...Doing a factory reset will send you into bootloop when rooted. Trying to flash other roms on a bootloop is not going to work. You need to have grabbed a backup such as Zedo has on his post and put the backup in clockwork folder on your phone. Then flash that in CWM. Would of brought you out of bootloop to a stock rom with his kernal. Now you can flash Roms and kernals or could of flashed crawf or anyone else FULL stock rom and been back to stock kernel and rom and not rooted.
Click to expand...
Click to collapse
Ohhhh that's what happened! Awesome thanks. I will be much better prepared with backups out the wazoo this time haha.
Now if only I could figure out why Touchwiz died in the first place hmmm....

I hope you can figure it out, just postin here to say that when I saw this thread, it reminded me of the thread over in the EVO forums about the guy who claimed that sprint removed his Sense from his phone.

Khilbron said:
I hope you can figure it out, just postin here to say that when I saw this thread, it reminded me of the thread over in the EVO forums about the guy who claimed that sprint removed his Sense from his phone.
Click to expand...
Click to collapse
haha SPRINT removed it?! So that person thinks sprint monitors every device and has a team of techies on staff to hack your phone and brick it if you break their rules?... yeah that totally makes more sense than a file got corrupted when you were messing with the kernel.. some people maybe shouldn't be rooting their devices in the first place haha

[Q] Calkulin's Rom won't allow recovery..

So I I've had 2 different recoveries so far that have worked fine.. both came from Rogue though. One was from the 1.5 kernel (Hitman) which installed CWM Touch recovery, the other came with the normal recoveries based off CW 5.0.2.7. They were working fine until I installed Calkulin's Rom(2.8.1). Not sure if they're just incompatible or what, but when I go to recovery it shows the background image of the recovery but none of the options show up. It shows for about half a second and then it goes back to the original boot screen, then to the 2nd screen and turns on. So it basically skips right through the recovery and reboots. Do I need a new Rom or can I fix this? I really like the battery life and visuals of Calkulin's Rom and would love to be able to keep it.
EDIT: One more thing.. Since I installed the ROM, I've been getting market error 492. It doesn't allow me to install anything in the market..
I haven't tried a full wipe yet, so I guess I'll try that and then see how that works with the recovery and Rom..

I did the same thing to my phone this week, and I'm running Blazer, so i'm sure it has nothing to do with either ROM.
Not sure how I caused it but with so many folks running both without this error, I'm guessing that your issue (like mine was) was probably some how self induced.
I flashed back to stock and started over, and things have been working great. Might be worth a shot flashing back, or restore a backup and start fresh.
Haven't seen the market error before. I'm sure someone here has
Good Luck

If you got it off here, could you show me which stock you flashed..?

Everything you need is in the Epic 4G Touch Android Development section
Here is the post I used from Sfhub
http://forum.xda-developers.com/showthread.php?t=1433101
Watch the videos by Qbking77 They walk you thru everything step by step. (I hear his video intro rif every time I close my eyes now so you've been warned) Makes it super easy.
I would read everything you can and watch the videos before you get in too deep. I've had this phone since December, and just flashed my 1st ROM this week cause I've been reading up, and learning all I could before I jumped in the pool.

Well I've done all this with 2 phones before but I've never had this happen.. normally I just get the Rom and I'm good to go..

I think I must've gone wrong somewhere when I originally rooted through a stock rom.. It already seems to be more respondful.

premo1 said:
I think I must've gone wrong somewhere when I originally rooted through a stock rom.. It already seems to be more respondful.
Click to expand...
Click to collapse
Try booting while holding the volume up and power button.
If that does not work, flash recovery from rom manager, and that should get you into recovery to flash whatever kernel/recovery u want.

I've done all that.. None of it works.. I'm currently ODIN'ing Factory Stock Rom with root. Hopefully after that I can redo all of these and eventually end up with a working, corresponding Rom and kernel..

premo1 said:
I've done all that.. None of it works.. I'm currently ODIN'ing Factory Stock Rom with root. Hopefully after that I can redo all of these and eventually end up with a working, corresponding Rom and kernel..
Click to expand...
Click to collapse
Good Luck.

Recovery and market are now working Thank you Adanorm!

Glad your back up and running

Unfixable boot loop... Help?

Hey everyone,
So this is my last ditch effort to attempt to save my device. I would really prefer not to perform another warranty exchange given that I am not under insurance, but I'm afraid I have no choice.
My phone was rooted and I was using Darkside without issues, as I had been for the past two weeks. I am always careful when I flash roms and I made sure to follow every possible protocol. That's the background information.
My battery life was running at approximately 6 percent yesterday and I sent a text message as normal, and it was stuck at sending. I tried turning wireless data off from the toggles in the pull-down and it was unresponsive. When I went to Wireless Network in the settings option, my phone rebooted. Once it started up again, my service would not come back, and the phone would continually bootloop once it got past the traditional "media scanner running", etc. My window of opportunity to do anything was really slim.
I charged my phone to see if it made a difference, but it didn't. Tried with my SIM card removed and it still bootlooped. I was able to get to CWM from the advanced power menu before it rebooted again and I fixed permissions and cleared cache and dalvik. Now the phone wouldn't even get past the boot animation before rebooting.
I put the phone into download mode and reverted back to stock using Odin. The phone now got past the boot animation in stock mode, but was unable to find service and after about 10 seconds fell into the same bootloop pattern. I tried removing the SD card but that didn't help either. Using Odin again, I reflashed recovery, followed by root and tried reinstalling a rom through CWM (I have only used regular CWM, not the touch version) with a superwipe to ensure a clean flash. Once again, it wouldn't make it past the boot animation before bootlooping. I reverted back to stock using Odin, and this is where I stand.
I have tried all traditional methods to salvage the phone and, for the life of me, I cannot understand what happened. The only thing I notice is that regardless of how long the phone stays on before rebooting, it is never able to find service. It's like the radio or modem broke and the phone has no other choice but to restart forever. But reflashing the stock UVKL1 should also reflash the proper modem and radio, right?
Has this ever happened to anyone? Any suggestions (aside from the typical reverting to stock) as to how I might be able to stop it? I searched but haven't been able to find a situation quite like this one. Thanks in advance for your help.

Really sorry to hear about your problem. Assuming the 2.3.6 stock image you flashed via Odin is the one provided by Przekret and that that didn't work, then I'd try one or both of these two longshots to try to clear possible corruption problems in either the kernel or modem spaces:
For each of the following wipe cache and Dalvik cache in CWM before flashing and again wipe Dalvik afterwards and also fix permissions:
1) Format system (do this 3x) under mounts & storage in CWM. Flash the standalone Darkside kernel X v1 final immediately after flashing, e.g., the current Darkside rom. (You'll need to wipe data, too, if not coming from a Darkside rom. Do not do any Superwipe - neither the standalone version nor using a flag.)
2) Flash the KID modem (do this 3x). Both Odin- and CWM-flashable versions are available. (You can always flash back to KL1 if the problem is fixed.)
Hope this is clear. It's late! These are both things that have helped get my phone out of troubles, though not as bad as yours. Good luck!
Sent from my SGH-T989 using XDA App

Also if u used the one from przekret then I'm almost positive that Odin package flashes the new radio too. If memory serves me right. Op let us know what happened

Thanks for your help. Unfortunately, nothing has worked. I'm on the phone with T-Mobile, I see no other solution but to get it exchanged under warranty and it's not getting here until March 15th, according to the representative. I suppose I'll just use a replacement phone in the meantime. It's just really weird and frustrating... I could understand a bad flash or something similar, but I followed every step accurately as I always have and everything was working just fine until it randomly decided to die without warning.

Well since you're getting another one anyways I would continue trying to fix this one, just in case you come up with a solution and for another worst case scenario for your new phone.
Powered by the SGSII....

I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA

shehrammajid said:
I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Forgive me for asking, but what is the EFS folder?

My once bricked E4GT!

To be honest,
Once I got to the rogue et recovery I cried a little (because I actually got there.)
7 hours worth of beating sleep, numb legs from sitting down, afro being dry, and Samantha (samsung support person, cause I really was going to send my phone in..)
Two batteries *thank god!
Don't really, can't explain much. Just a load of reading of the "download shabby's/acs leaked fb17...." thread, xda search tool, google, and youtube.
I'm just glad, I found some way to enable recovery. No, 2 weeks without a phone, no going to the shipping retail location, no "not having my little cloud(white e4gt) in my hand." ....cheesy
I hear birds chirping outside, wow, and the sun is starting to come up.
Now I must figure out what I need to do next in recovery, then get out this desk chair (because my dsfgh...), and go to sleep!
XDA ROCKS!

Wut? You saying you brought your E4GT back from a brick?
Sent from my SPH-D710 using Tapatalk

How did that happen?

I'm guessing it wasn't a real brick as in blue light of death. Probably stuck in a boot loop or something.
Sent from my SPH-D710 using Tapatalk

What type of brick lol? A soft brick all you need to do is go into download mode and ODIN over some new firmware, forget recovery lol. Unless it was a super brick from flashing ICS recovery where you luckily have recovery... your still pretty screwed. But if it was just a bootloop, soft brick the fix is simple.

slick_rick said:
I'm guessing it wasn't a real brick as in blue light of death. Probably stuck in a boot loop or something.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
How do you fix from boot loop ( the yellow triangle )? I can get in recovery and odim but which ever rom I flash it will not boot up...only to the triangle. In the recovery mode it take very long time to format the data and setting.....waiting time is like one minute. Any help?

K.0.0.L. said:
How do you fix from boot loop ( the yellow triangle )? I can get in recovery and odim but which ever rom I flash it will not boot up...only to the triangle. In the recovery mode it take very long time to format the data and setting.....waiting time is like one minute. Any help?
Click to expand...
Click to collapse
...People lack so many details. What rom where you on when the phone last worked, what were you flashing when it screwed up. What is ODIN getting stuck on?
Your either easily fixable, really screwed or completely screwed. Welcome to the 3 possibilities. Without any details for all I know your on Gingerbread and did something retarded or you were flashing in Ice Cream Sandwich and screwed yourself not following directions.

RainMotorsports said:
...People lack so many details. What rom where you on when the phone last worked, what were you flashing when it screwed up. What is ODIN getting stuck on?
Your either easily fixable, really screwed or completely screwed. Welcome to the 3 possibilities. Without any details for all I know your on Gingerbread and did something retarded or you were flashing in Ice Cream Sandwich and screwed yourself not following directions.
Click to expand...
Click to collapse
I was on wicked sensation and flash to AOKP build 39....It never happen to me before but somehow this time it did. I use culklins format all and during the data format it get stuck for long time then I remove the battery and it just never able to go pass beyond that. Just couple hour ago I let it sit on that process and it finally format the data and system..I then flash the AOKP but it get stuck on the boot animation......so I decided to ordin to stock kernel EL26 and now same old thing again...unable to go beyond boot loop. My custom binary download is 11 counts...........I have order the USB jig from ebay to see if it can help to erase the counts, maybe that is the issue why not booting up

K.0.0.L. said:
I was on wicked sensation and flash to AOKP build 39....It never happen to me before but somehow this time it did. I use culklins format all and during the data format it get stuck for long time then I remove the battery and it just never able to go pass beyond that. Just couple hour ago I let it sit on that process and it finally format the data and system..I then flash the AOKP but it get stuck on the boot animation......so I decided to ordin to stock kernel EL26 and now same old thing again...unable to go beyond boot loop. My custom binary download is 11 counts...........I have order the USB jig from ebay to see if it can help to erase the counts, maybe that is the issue why not booting up
Click to expand...
Click to collapse
Wicked sensation is an ICS rom right? Did you flash AOKP 39 from ICS Recovery? The one thing you should not do? If the rom does not have a safe updater binary there is a high chance of super brick when flashing from even a safe ICS recovery, and even higher from the regular repacks. NEVER factory reset from any non safe ics recovery and never flash a zip in ICS recovery unless it is marked as safe to do so.
If when trying to ODIN stock firmware it gets stuck at Data.img then you really did it this time. From what I have heard there are 2 levels of the super brick. The kind where you can still get to download and recovery and the kind where you cant. Stuck on Data.img on the first kind is a bad sign.
As far as the triangle goes that comes up any time you odin an unsigned kernel etc like the el26 cwm one. It is just an indicator and should not be a part of your problem.

Flash any stock gb kernel it should remove the triangle! (ODIN)

I don't really know what's up right now...
The whole reason I'm in this mess is me changing settings when I first flashed AOKP 39. Like setting display, changing the wallpaper. Just going straight down the whole setting page.
I got to the DPI settings, changed it to something lower, 240 i think. Rebooted... Didn't like it, changed it back to the original, rebooted... the words and all were original but not the status bar, not the lock screen, not the navi bar.
It was super weird!
So I thought:
"...doing a factory reset would allow me to start fresh again. If that doesn't work, I can just start completely over(odin back to gb). that way I can install gapps(the arrangement of back and enter buttons confused me, causing me to restart)"
All of a sudden, phone didn't work. Can't really remember what happened at the time. If it went into boot loop or not. But it didn't go into the rom.
Somehow, I ending up doing stuff, since I just got it a week ago I really didn't know much, was just learning as I went. "new phone, new things to learn"
Anyways, ending up with "A" recovery, and I've always been able to get into ODIN.
recovery that works is: rogue_ET-recovery-1.2.2-FB27-rc0.tar
Now that I have some kind of recovery and odin I thought, maybe I could get back to stock. Just don't know how, thats were doing more searches came in. Still got NOTHING. lol.
I was aware of not flashing ics from an ics dadada messages. hint: i read stuff
I did a factory reset which caused all of this. Kinda know I shouldn't of done it now, ...never came across anything about not doing it at the time. I still haven't, I'll google that too.
Umm.. flashing stuff through pda doesn't work. to be more specific
when I look at the progress, it doesn't include data.img (so it PASS)
if I odin something and it says data.img, then its stuck there.
so that recovery I'm using: (volup+pwr)
bootscreen(samsung galaxy s II) -> quick led(blue) -> bootscreen(samsung galaxy s II) -> recovery
any other tries when getting into recovery WITHOUT odin rogue_ET-recovery-1.2.2-FB27-rc0.tar: (volup+pwr)
quick led(blue) -> bootscreen(samsung galaxy s II) -> quick led(blue) -> bootscreen(samsung galaxy s II) bootloop bootloop bootloop. Sometimes it will stay there for a few minutes then bootloop again.
-----
so right now, ....still trying to find a solution. I'm still on google and xda searching. I really don't want to do anything else because both batteries I think are nearly dead...
When I started flashing, I was on ParanoidAndroid, then I found AOKP 39. It worked, was awesome. But I did a factory reset from the settings within the rom and now Im typing this...
flashing in recovery, when trying to erase data(it doesn't work.) though cache and dalvik does.

AndroidRocksSocks said:
When I started flashing, I was on ParanoidAndroid, then I found AOKP 39. It worked, was awesome. But I did a factory reset from the settings within the rom and now Im typing this...
Click to expand...
Click to collapse
Suicide.
AndroidRocksSocks said:
flashing in recovery, when trying to erase data(it doesn't work.) though cache and dalvik does.
Click to expand...
Click to collapse
Because the /Data partition is borked.

RainMotorsports said:
Suicide.
Because the /Data partition is borked.
Click to expand...
Click to collapse
Right, had* to be something.
CPR?

If all you get is the blue led.... Its done. That's what I was seeing when I bricked my first e4gt. On AOKP it says in red all caps too, do not do anything with this kernal.. Probably not word for word, but unless its a safe recovery as stated, you can't do anything with it, not even wipes.

evo-t said:
If all you get is the blue led.... Its done. That's what I was seeing when I bricked my first e4gt. On AOKP it says in red all caps too, do not do anything with this kernal.. Probably not word for word, but unless its a safe recovery as stated, you can't do anything with it, not even wipes.
Click to expand...
Click to collapse
....lol he already said he is getting past that. Still the same issue though he is Super Bricked.
AndroidRocksSocks said:
Right, hand to be something.
CPR?
Click to expand...
Click to collapse
Your at the level where some people seemed to have been able to repartition the eMMC around the origina /Data area consuming space other partitions normally used. Its not considered stable.
There is no premenant fix that can be applied by you, a sprint store, or even jtag service. The Super Brick bug corruption occurs at the lowest possible level. You basically need Samsung to fix it, though just about anyone on the eMMC partner list technically can.
Phone replacement is the primary option or you can see about getting info about the repart here - http://forum.xda-developers.com/showthread.php?t=1644364

Great, ha-ha.
Well, I look into that repart info. If I can't handle it. All I have to do is print out the ups shipping label and send it in. So sad... anything I need to do when sending it in? As in, do I need to put it at some kind of "ok" state? Ugh, I hate this.

AndroidRocksSocks said:
Great, ha-ha.
Well, I look into that repart info. If I can't handle it. All I have to do is print out the ups shipping label and send it in. So sad... anything I need to do when sending it in? As in, do I need to put it at some kind of "ok" state? Ugh, I hate this.
Click to expand...
Click to collapse
I would see about odining over the stock EL29 kernel but the yellow triangle is still going to say hey look at me. If that USB jig arrives should be able to reset the counter.
If its via insurance it wont matter.

RainMotorsports said:
I would see about odining over the stock EL29 kernel but the yellow triangle is still going to say hey look at me. If that USB jig arrives should be able to reset the counter.
If its via insurance it wont matter.
Click to expand...
Click to collapse
Ya know, I was planning to go outside today...
This test thing looks alright though.
I guess I'll follow the steps and the following questions from others who have or are doing it.

AndroidRocksSocks said:
Ya know, I was planning to go outside today...
This test thing looks alright though.
I guess I'll follow the steps and the following questions from others who have or are doing it.
Click to expand...
Click to collapse
Which test? The AOKP 37/ CM9 Alpha 5 test? That was for people wanting to flash things without bricking their phone. I think you caught my link before i changed it to the original post.

RainMotorsports said:
Which test? The AOKP 37/ CM9 Alpha 5 test? That was for people wanting to flash things without bricking their phone. I think you caught my link before i changed it to the original post.
Click to expand...
Click to collapse
Oh wait a min...
Right, yea I did.
This one: Discussion thread for /data EMMC lockup/corruption bug

please help! phone freezes after every app lounched- after trying to install cwm ...

hey guys!
i will realy appriciate any help on this one:
i am in a light panic attack as i might bricked my first phone..
today i have updated my t989 to ics 4.0.4 via kies, and then rooted it.
of course the root was so i can flash a rom. i chose to try cm9.
any ways, in order not to get the phone stuck in boot loop, i have tried to install the touch version of the cwm recovery.
i did it through the zip on sd option.
the version i used was: CWM6013-TOUCH-CM9-recovery (file size 4.201)
it seemed ok at first.
but then when i retsrted the phone, i noticed that every app i am trying to launch takes forever to respond (about a minute)...
i have tried to do factory reset and it did not help - the phone was sluggish even on the first setup screens..
now i am in the process of downloading the stock version again, to unroot. is this the way to go? did i miss something?
please let me know what info i can provide so you will be able to help me.
again, and i can't say it enough: every help will be very much appreciated. so, did i brick my phone?
thanks!
cvbn

Dude wrong section.

cvbn52 said:
hey guys!
i will realy appriciate any help on this one:
i am in a light panic attack as i might bricked my first phone..
today i have updated my t989 to ics 4.0.4 via kies, and then rooted it.
of course the root was so i can flash a rom. i chose to try cm9.
any ways, in order not to get the phone stuck in boot loop, i have tried to install the touch version of the cwm recovery.
i did it through the zip on sd option.
the version i used was: CWM6013-TOUCH-CM9-recovery (file size 4.201)
it seemed ok at first.
but then when i retsrted the phone, i noticed that every app i am trying to launch takes forever to respond (about a minute)...
i have tried to do factory reset and it did not help - the phone was sluggish even on the first setup screens..
now i am in the process of downloading the stock version again, to unroot. is this the way to go? did i miss something?
please let me know what info i can provide so you will be able to help me.
again, and i can't say it enough: every help will be very much appreciated.
thanks!
cvbn
Click to expand...
Click to collapse
What all did you do to install the ROM?

Something like this happened to me on my original Galaxy S when I updated it via Kies to the new stock version. Everything was running extremely sluggish. I don't remember what I ended up doing to fix it but I most certainly did not keep the stock update on there. I rebooted it and let it sit for about 30mins and then rebooted it again and tried using it. It was a bit better but still not good so I just flashed another Rom and then it was lightning quick.
The good news is you didn't brick it if you can still boot up and run stuff. I'd suggest updating your recovery to TWRP as that seems to be the preferred one now a days, it's the one I've been using to flash countless Roms without any problems, and most Devs recommend it. Apart from that, follow the install instructions precisely and you shouldn't have a problem. To be sure, after upgrading your recovery to TWRP, you could do the wipes (cache/dalvik/factory reset/system) 2-3 times before installing your new Rom, that seems to help some people coming from previous troublesome Roms.
I've noticed a few problems people seem to have around here come from the recovery, mainly those not using TWRP and/or using some form of outdated or beta CWM. Hopefully you can fix your problem, I know first hand how awful that sluggish feeling is. Good luck!