Develop Bugs

[Q] Evo 4G Doesn't Like to Boot in New ROMs

Most of this info may be extraneous, but I'll throw it in here just in case.
A few days ago, I decided to root my Evo 4G from the stock, 2.2 OS (HTC Sense?) using the Unrevoked website (using a PC running XP). It worked fine and got me rooted. Trouble began to arise when I attempted to install new ROMs such as CM-6 and Salvage. I decided to fork out a few bucks and pay for the ROM Manager Pro app, thinking that it would save me considerable hassle. After downloading the most recent CyanogenMod 7.0.0-RC2 through the app, I selected the "Install Gapps as well" option but did NOT check "Wipe Data and Cache" before letting the app do its work of installing and flashing and whatever for me. Upon completion of the installation, my phone then automatically rebooted normally, but became stuck on the boot image of the android on the skateboard with the spinning arrow. I let that sit for about 6 hours (I went to bed) thinking it was just first-time setup before I battery-pulled and booted into recovery, restored my original settings, and started over. This time I did everything the same except remembered to check "Wipe Data and Cache," as an online tutorial told me I ought to when switching from stock to another ROM, and it installed and booted correctly. I ran CM-7 for a day before deciding to try out a different ROM, downloading and installing it through the same interface, ROM Manager Pro. Everything went well until it got stuck, again, at the boot image. After about 30 min I battery-pulled and tried to restore back to CM-7, only to be greeted by another endless boot image. I was able to restore back to my original backup, but am now back to square one. What the heck am I doing wrong?
EDIT: That original backup I mentioned was made immediately after rooting the phone in preparation to install CM-7.
Sorry my technical knowledge is grossly lacking, I just got into this game. Patience and any help is GREATLY appreciated.

When switching from one rom to another, it is always important to remember to wipe data and cache. There are a few rare cases that it is not necessary to do this, but I really recommend that if you are just starting out, wipe them both for good measure until you learn enough that you can tell when you can get away with not wiping. Also, I know that one common problem that people experience with Rom Manager is that Unrevoked contains the Amon_RA recovery image, and Rom Manager is designed to with with the Clockwordmod recovery. In Rom Manager, you should be able to see which one you are currently using, and you should also be able to use Rom Manager to download and flash the latest Clockworkmod recovery. I too use Rom Manager as a convenient way of making sure that my rom is up to date, and to download roms, but I recommend that when you want to change roms, you do it by booting into recovery mode, and performing the wipe and install manually, as I have found that this method will help prevent errors like boot loops. I hope this helps!
P.S. Feel free to PM me if you ever need any help.
Sent from my DESTROYED Evo using XDA Premium app

So, for example, if I wanted to restore back to my CM-7 backup, would I want to boot into recovery and just restore to the backup or re-flash the ROM, then boot into recovery and try to restore it? I'm still getting the endless boot image.
Oh, and I am running clockworkmod, as per the instructions for ROM Manager.
Thanks for the quick reply!

Move CM7-RC2.zip and the gapps.zip (or whatever its name; ex: filename.zip) to the root of your SD card by plugging it into your computer via USB and mounting it as a drive. Go ahead and exit all that.
Turn off your phone.
Hold volume down + power.
Go to Recovery.
Wipe the following: data/factory reset, cache, (in Advanced, accessed from same menu) wipe dalvik.
Go back.
Install .zip from SD.
Choose your .zip(s) [CM7, Gapps] from your card, flash, and presto!
I'm not too experienced with ROM Manager as I do not use it whatsoever, but I know the above stated method should work perfectly.
Furthermore,
I'm not sure if a format_all.zip should be used here with CM7. If someone who knows would like to chime in about this, that'd be great.

totalanonymity said:
Move CM7-RC2.zip (or whatever it's name; ex: filename.zip) to the root of your SD card by plugging it into your computer via USB and mounting it as a drive. Go ahead and exit all that.
Turn off your phone.
Hold volume down + power.
Go to Recovery.
Wipe the following: data/factory reset, cache, (in Advanced, accessed from same menu) wipe dalvik.
Go back.
Install .zip from SD.
Choose your .zip from your card, flash, and presto!
I'm not too experienced with ROM Manager as I do not use it whatsoever, but I know the above stated method should work perfectly.
Furthermore,
I'm not sure if a format_all.zip should be used here with CM7. If someone who knows would like to chime in about this, that'd be great.
Click to expand...
Click to collapse
This is the way I would flash any roms that you want from here on out.
I have used CM7 and have not had to use the format.zip from calk, so I don't think it is absolutely necessary, but it probably wouldn't hurt.
Sent from my DESTROYED Evo using XDA Premium app

I recommend flashing the format all zip whenever switching ROMs. It completely formats the various partitions and leaves a blank slate for the new ROM to be installed. I also recommend using ROM Manager to flash Amon_Ra recovery and do everything manually instead of using ROM Manager. People seem to have a lot less problems with Amon, and I have never had any issues flashing ROMs or kernels or anything with it.
You won't be able to restore a Clockwork backup with it but it never hurts to just flash a new ROM and restore your Titanium backups, assuming that you made them.

Wow, thanks all for the fast replies!
Ok, I now have Destroyer installed and working (finally!), but I am experiencing the apparently common black-on-black text box problem. I downloaded the .zip to be flashed to fix this, but am not sure how to proceed. Do I just do the exact same thing as flashing a new ROM entirely or is there something special I need to do to let the phone know that it is an update?

RossGoldenstein said:
Wow, thanks all for the fast replies!
Ok, I now have Destroyer installed and working (finally!), but I am experiencing the apparently common black-on-black text box problem. I downloaded the .zip to be flashed to fix this, but am not sure how to proceed. Do I just do the exact same thing as flashing a new ROM entirely or is there something special I need to do to let the phone know that it is an update?
Click to expand...
Click to collapse
Not sure with ROM Manager but you can flash that from recovery the same way you flash a ROM. I'm sure there is an option in ROM Manager to flash it, I just couldn't tell you where. Do not wipe anything before flashing that though. Only wipe when flashing ROMs and kernels.

Go back into Recovery and flash that .zip the exact same way you flashed the ROM. Minus the data wipe.
Others: Does he wipe cache/dalvik as well? I've seen some posts say to do that when flashing mods that are flashable .zip and some don't. I've done both ways and seen no negative consequences (as of yet).

Yeah, that last post was dumb, I clicked "Submit" before I tried anything on my own. Flashing it the exact same way minus data wipe worked perfectly, though the prediction boxes for input in the market app (when you hit "search" and start typing, the things that drop down to give suggestions) still appear to be black on black. Bleh.
Also, the Dalvic wipe before installing was a good idea; I don't know for sure if it made a difference but a good habit to get into.
EDIT: By the way, this has got to be the least grammatical/spelling errors in a forum thread I've ever seen. I think I may like this site...

Wiping the cache and dalvik most likely isn't necessary but it can never hurt.

RossGoldenstein said:
Yeah, that last post was dumb, I clicked "Submit" before I tried anything on my own. Flashing it the exact same way minus data wipe worked perfectly, though the prediction boxes for input in the market app (when you hit "search" and start typing, the things that drop down to give suggestions) still appear to be black on black. Bleh.
Also, the Dalvic wipe before installing was a good idea; I don't know for sure if it made a difference but a good habit to get into.
EDIT: By the way, this has got to be the least grammatical/spelling errors in a forum thread I've ever seen. I think I may like this site...
Click to expand...
Click to collapse
I'm really new to this stuff myself (rooted for the first time ~2 days ago) and so I'm unsure how to further fix the blacked out predictions in the Market. Perhaps you could try contacting those within the thread of the ROM you downloaded, specifically citing that you installed the initial blacked out fix so that they don't redirect you back to the fix you've already applied, testing your patience and furthering your wait for perfection.
Aye, this site has got to be full of some of the most fluent English-speaking persons I've found on the internet.

SyndicateROM 1.1.0 twlauncher has stopped unexpectedly

I loaded the syndacite rom about 2 weeks ago and i love it. Yesterday i started gettign this error. "twlauncher has stopped unexpectedly". I try to force close it over and over again and even a reboot doesn't work. I reboot twice and it appears a few times then i'm able to use my phone again. Anyone know what the problem is? I used the syndacite fully loaded rom.

Clear data for the launcher in Settings > Applications.

k0nane said:
Clear data for the launcher in Settings > Applications.
Click to expand...
Click to collapse
I went there but i don't see a clear data option. Can you explain a little bit further to me? thanks!

howufiga said:
I went there but i don't see a clear data option. Can you explain a little bit further to me? thanks!
Click to expand...
Click to collapse
Settings > Applications > Manage Applications > TWLauncher (or TouchWiz Launcher, or com.samsung.twlauncher) > Clear Data

k0nane said:
Settings > Applications > Manage Applications > TWLauncher (or TouchWiz Launcher, or com.samsung.twlauncher) > Clear Data
Click to expand...
Click to collapse
I can't even get to settings. I can only pull down the the menu with the WIFI and GPS settings. any tips on how to get into settings? I keep on getting twlauncher has stopped over and over again.

If you can't open settings, try going into CWM > Advanced, and fixing permissions. Can also clear caches, and if that doesn’t work, reflash the ROM.
Actually, just curious. What happens when you try to go into settings? Does the menu come up to enter settings, does it FC when you open?

i couldn't open applications. Everytime I tried in between hitting force close it would just flash then come back and reload over and over again. I had the bright idea of pulling the battery and then it wouldn't boot at all. Had to reflash the ROM. Now need to reinstall all my apps. lol

howufiga said:
i couldn't open applications. Everytime I tried in between hitting force close it would just flash then come back and reload over and over again. I had the bright idea of pulling the battery and then it wouldn't boot at all. Had to reflash the ROM. Now need to reinstall all my apps. lol
Click to expand...
Click to collapse
If this happens in the future, hold down the search key and say something to search for, this should take you to the browser. Search for and download launcherpro, zeam, or another launcher you don't already have. After it installs, hit home and choose the new launcher, then you can clear data for touchwiz. This happened to me when I had one homescreen on touchwiz and it was full, and an app tried to automatically add a shortcut.
Sent from my always stock, EC05 Epic 4G

howufiga said:
i couldn't open applications. Everytime I tried in between hitting force close it would just flash then come back and reload over and over again. I had the bright idea of pulling the battery and then it wouldn't boot at all. Had to reflash the ROM. Now need to reinstall all my apps. lol
Click to expand...
Click to collapse
It sounds like a bad reflash though. I've had that, where it FCs so repeatedly that I can't do anything at all. When you have it all set the way you want, make a CWM Nandroid backup, and then restore that backup to turn journaling back on... then battery pulls won't affect you.

You made my day!
zanderman112 said:
If this happens in the future, hold down the search key and say something to search for, this should take you to the browser. Search for and download launcherpro, zeam, or another launcher you don't already have. After it installs, hit home and choose the new launcher, then you can clear data for touchwiz. This happened to me when I had one homescreen on touchwiz and it was full, and an app tried to automatically add a shortcut.
Click to expand...
Click to collapse
What a simple and elegant solution! This error showed up for me last night, and then completely ruined my morning. After searching countless forums and finding nothing but overly technical instructions containing so much jargon I had to search forums to figure out what the instructions meant....I nearly threw my phone up against the wall. Just before I was about to restore to factory settings, I found this thread and these instructions worked PERFECTLY!!! I am not a gadget guy and had a Sanyo Katana that was held together with tape until a month ago, so this solution was right up my alley! I actually registered on this site simply to say thanks. Hopefully the Thanks button will show up after I make this post so I can hit it until my finger blisters.

Props here as well
k0nane said:
Settings > Applications > Manage Applications > TWLauncher (or TouchWiz Launcher, or com.samsung.twlauncher) > Clear Data
Click to expand...
Click to collapse
Thanks to k0nane as well. Once I got LauncherPro to download with zanderman's intructions this helped me clear and reload touchwiz.

LdoFoSho said:
What a simple and elegant solution! This error showed up for me last night, and then completely ruined my morning. After searching countless forums and finding nothing but overly technical instructions containing so much jargon I had to search forums to figure out what the instructions meant....I nearly threw my phone up against the wall. Just before I was about to restore to factory settings, I found this thread and these instructions worked PERFECTLY!!! I am not a gadget guy and had a Sanyo Katana that was held together with tape until a month ago, so this solution was right up my alley! I actually registered on this site simply to say thanks. Hopefully the Thanks button will show up after I make this post so I can hit it until my finger blisters.
Click to expand...
Click to collapse
No problem! I forgot about this.
Please click both links below and vote: http://picketfenceblogs.com/vote/3616
http://apps.facebook.com/gerberphotosearch/entry/935/amber.aspx

Oh God bless you, zanderman112. I thought I was going to have to reset my mom's new phone after I finally finished setting it up and she just started getting used to it.

Red Jenny said:
Oh God bless you, zanderman112. I thought I was going to have to reset my mom's new phone after I finally finished setting it up and she just started getting used to it.
Click to expand...
Click to collapse
Thank you. Now, you can also try market.android.com to wirelessly install apps.
Sent from my Samsung Legendary 4G, a Universe UTES Phone, running "two. two"

Sorry to drag up an old thread, but I can't find any help on this thru searches, so here goes:
Does SynFro 1.1.0 clash with CWM5?
My Epic been on Bonsai 4.0.1 (CWM 3.0.0.6, ext4, golauncherex) for a long time. I used Rom manager to update CWM to 5, and to flash the ROM Syndicate Fro_fully loaded 1.1.0 . Seemed to run fine at 1st (hr or so) then while DL'ing a goLauncherex from market, the system froze. after battery pull and reboot, I had constant FC's. Booting into recovery from Rom manager lead to a generic Android recovery system (instead of CWM).
Powered off, 3 fingered into CWM, which suddenly had reverted to v3.0.0.6 . Tried to restore Bonsai, but only got error msgs ("syste.img not found. skipping restore of /system" same with data, android_secure, cache, sd-ext, etc. )
Had to triple wipe (data,cache, dalvik), reflash my bonsai rom and re-update CWM to 5 to get back to a normal functioning phone.
If the issue here seems to be conflicts between older roms clashing with newer CWM versions, is there a way to check which ROMs require which CWM?
thanks for your time.

Epiclectic said:
Sorry to drag up an old thread, but I can't find any help on this thru searches, so here goes:
Does SynFro 1.1.0 clash with CWM5?
My Epic been on Bonsai 4.0.1 (CWM 3.0.0.6, ext4, golauncherex) for a long time. I used Rom manager to update CWM to 5, and to flash the ROM Syndicate Fro_fully loaded 1.1.0 . Seemed to run fine at 1st (hr or so) then while DL'ing a goLauncherex from market, the system froze. after battery pull and reboot, I had constant FC's. Booting into recovery from Rom manager lead to a generic Android recovery system (instead of CWM).
Powered off, 3 fingered into CWM, which suddenly had reverted to v3.0.0.6 . Tried to restore Bonsai, but only got error msgs ("syste.img not found. skipping restore of /system" same with data, android_secure, cache, sd-ext, etc. )
Had to triple wipe (data,cache, dalvik), reflash my bonsai rom and re-update CWM to 5 to get back to a normal functioning phone.
If the issue here seems to be conflicts between older roms clashing with newer CWM versions, is there a way to check which ROMs require which CWM?
thanks for your time.
Click to expand...
Click to collapse
Gonna try to help.
Both SFR and bonsai are oollldddd roms. SFR froze up because it isn't journaled. I highly recommend using ODIN to get to stock EC05, then update to EL30. Then use qbking77s "How to root Samsung epic 4g gingerbread" video to get CWM and root.
CWM 5 can flash any Rom, but those roms in particular are so old and buggy.
Sent from something with a Ｋモ尺れモㄥ.

Epiclectic said:
Sorry to drag up an old thread, but I can't find any help on this thru searches, so here goes:
Does SynFro 1.1.0 clash with CWM5?
My Epic been on Bonsai 4.0.1 (CWM 3.0.0.6, ext4, golauncherex) for a long time. I used Rom manager to update CWM to 5, and to flash the ROM Syndicate Fro_fully loaded 1.1.0 . Seemed to run fine at 1st (hr or so) then while DL'ing a goLauncherex from market, the system froze. after battery pull and reboot, I had constant FC's. Booting into recovery from Rom manager lead to a generic Android recovery system (instead of CWM).
Powered off, 3 fingered into CWM, which suddenly had reverted to v3.0.0.6 . Tried to restore Bonsai, but only got error msgs ("syste.img not found. skipping restore of /system" same with data, android_secure, cache, sd-ext, etc. )
Had to triple wipe (data,cache, dalvik), reflash my bonsai rom and re-update CWM to 5 to get back to a normal functioning phone.
If the issue here seems to be conflicts between older roms clashing with newer CWM versions, is there a way to check which ROMs require which CWM?
thanks for your time.
Click to expand...
Click to collapse
I've got you man.
What you need to do is direct your attention to this thread right here by DRockstar: RECOVERY] ClockworkMod 5.0.2.7 BML Officially supported by ROM Manager
What you had done wrong was you installed through Rom Manager, which is a temporary flash ontop of CWM 3, it in itsellf is not CWM 5 installed. Within that thread you've a choice of an update zip of CWM 5 or a Odin tar, CWM zip is preferrable. But otherwise you should be fine. The zip from within that thread is more final.

AproSamurai said:
I've got you man.
What you had done wrong was you installed through Rom Manager, which is a temporary flash ontop of CWM 3, it in itsellf is not CWM 5 installed. Within that thread you've a choice of an update zip of CWM 5 or a Odin tar, CWM zip is preferrable. But otherwise you should be fine. The zip from within that thread is more final.
Click to expand...
Click to collapse
Ok, I got the real CWM5 zip, flashed, now all roads lead to CWM5, so that part is fine. And I stopped trying those olds ROMs , tried to flash SynIce.
My Epic runs Bonsai4.0.1, I did the triple wipe and then flashed the rom (from CWM5) but I get the following:
SYN Ice Logo
"Take a shower, pick an outfit, put on some smell good, call my crew.."
then the yellow bar freezes about 15% into its progress. it eventually kicks back out to CWM. no msgs or errors to share. I dont have access to Odin (or a PC) and Heimdall wont recognize my epic....any1 having similar probs? is it my kernel? I see suggestions sometimes to use Odin to switch from "EC05" to "EL30"...i thought flashing the ROMs changed your base ROM (DK28, EL13, etc) to the one it needed....is that not the case?

Epiclectic said:
Ok, I got the real CWM5 zip, flashed, now all roads lead to CWM5, so that part is fine. And I stopped trying those olds ROMs , tried to flash SynIce.
My Epic runs Bonsai4.0.1, I did the triple wipe and then flashed the rom (from CWM5) but I get the following:
SYN Ice Logo
"Take a shower, pick an outfit, put on some smell good, call my crew.."
then the yellow bar freezes about 15% into its progress. it eventually kicks back out to CWM. no msgs or errors to share. I dont have access to Odin (or a PC) and Heimdall wont recognize my epic....any1 having similar probs? is it my kernel? I see suggestions sometimes to use Odin to switch from "EC05" to "EL30"...i thought flashing the ROMs changed your base ROM (DK28, EL13, etc) to the one it needed....is that not the case?
Click to expand...
Click to collapse
Never heard of synice... I would really suggest odining to ec05 just to clean up the phone and then root and flash... just cleaner that way... btw where did you find that rom...
Sent from my SPH-D700 using Tapatalk

flastnoles11 said:
Never heard of synice... I would really suggest odining to ec05 just to clean up the phone and then root and flash... just cleaner that way... btw where did you find that rom...
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Dude really SynIce is SRF lol wow how did that not click.

Is it possible my phone is cause of my issues?

So I have had my nexus for a month or two now, (LTE) and I have been having hit or miss issues with it, I am currently running the liquidsmooth rom, 1.0.1 but it's not just this rom that I have been having the issues.
What's happening is ill load the rom (properly, not my first rodeo) and it will be fantastic, but what will happen over a period of a week or two is the phone becomes extremely laggy. Like the lock screen takes 2-3 seconds to light up when I press the lock button, keyboard lags out and I have had this keyboard (swiftkey) on my last three phones. And just generally running like crap.
Now like I said it's not my first rodeo when it comes to rooting and flashing, but that's not to say I'm not very good at it, I have been rooting since I had my epic 4g on sprint and qbking77 has been a very helpful resource.. For sprint phones, but I did my best when I got a hold of my nexus.
So, on to my main question, when I unlocked the bootloader I had no issues, but when I went through to load clockwork mod, I don't think I did it right. But it was stable and kinda sorta worked. For example when I went to factory reset the phone to put liquid on, flashed it and booted for the first time, all of my contacts, settings, other miscellaneous things were still on the phone, but like app locations, and apps were no longer there. (weird right?)
So is it worth odining it back to stock, and giving it another try with a more current clockwork?
Thanks for the help
And if anyone has a suggestion for an easy to follow guide on returning to stock and rooting other than what's available on xda?
Thanks again and be gentle on me, lol
-Kyle
Sent from my Galaxy Nexus using XDA

No need to go back to stock. Flash CWM through Rom Manager.
Edit: Also, wipe data and cache on main screen of cwm, then go in advanced and wipe dalvik cache, and in Mounts and Settings format system. Then flash your new rom. Safest bet to wipe all and not just data, although data SHOULD have gotten rid of your contacts etc.

[Q] ROM/Theme/Mod Flashing Issues

I was wondering if anyone could help me out please. I've tried searching the forums, but I haven't been able to find my exact issue. Basically, I feel as if my phone seems to have increasing issues with flashing through Clockwork Recovery; here's the details:
I originally rooted my phone using the Odin flash method. I flashed the Juggernaut available at the time, wiping data/factory, cache, dalvik, and battery stats through clockwork first, and letting it chill for 15 minutes with the first boot. I follow the same steps each time I flash another rom ( I've read that I should also wipe /system, but Juggernaut seems to do that itself, so I haven't ). A month and a half ago, I wanted to add a few things, so I wiped, then flashed the latest Juggernaut, rebooted, let it settle,and then flashed the ICS Ultimate Theme, no wipe, then after another settle, flashed the Pdroid zip ( no wipe ) I made with the v1.27 auto-patcher. Everything seemed to work flawlessly for a month or so, then I started having issues that just kept getting worse: phone freezing while installing market apps then unfreezing, camera lagging, random freeze & reboots, etc. I tried fix permissions, and no luck. I wiped and tried reflashing everything the way I had, and the phone kept freezing after the faux kernel loading screen. Installing Juggernaut or another rom by itself, or a nandroid restore, is the only thing that got it past boot. Not even themes flashed over roms that they're made for get past boot. I restored my phone to stock using this method, wiped both SD cards, and re-rooted then flashed Juggernaut again, but this time I used clockwork's wipes and darkside's super wipe before flashing, but I still can't flash anything but the rom itself without a boot loop, even with fix permissions. I had a similar issue on my old mytouch Espresso; consecutive flashes seemed to almost eat away at my phone and make things worse, but that phone also had hardware issues. I'm using a new MicroSD since then. Also, if it means anything, I tried flashing the new clockwork touch from the zip on these forums after these issues started, and it never took, however, flashing through Rom Manager's after I purchased it worked fine.
Sorry about the long post, but I wanted to detail everything I've tried that I could think of before bothering anyone here. Does anyone know what could be the issue? I would really appreciate some help, because this issue is really frustrating, and I have no idea what's causing it.

Could someone help me with this please? I can try and get a log cat if needed. I'm just really hoping to get to the bottom of these issues.

I will be glad to help you out!
One big problem I see is that your not using Darkside Superwipe before flashing new roms.
So I would highly recommend you flash Darkside Superwipe first (clears all cache, partitions, ect very very thorughly) Better option than manually clearing cache and all that in clockwork mod.
Try Darkside Superwipe install the rom and see if you get any problems.
Here's how to use it if you dont know how to:

techfanatic9 said:
I will be glad to help you out!
One big problem I see is that your not using Darkside Superwipe before flashing new roms.
So I would highly recommend you flash Darkside Superwipe first (clears all cache, partitions, ect very very thorughly) Better option than manually clearing cache and all that in clockwork mod.
Try Darkside Superwipe install the rom and see if you get any problems.
Here's how to use it if you dont know how to:
Click to expand...
Click to collapse
I'd like to point out that he does in fact use tdjs super wipe.
OP: have you tried other ROMs or kernels. In my past experiences, faux kernel did not meet my expectations so I moved along to another one. Give my configuration a go (refer to my signature) and let me know of the problem persists
Sent from my Galaxy Nexus using Tapatalk 2

Thanks for the replies!
techfanatic9 - I originally just wiped through clockwork ( before darkside superwipe was standard ), but now I use that too, and I'm still having those issues. I watched through the entire video just in case, and I'm doing it just like they say to.
iLeopard - I have tried Digital Warfare, but I still have the same issue when flashing things over it ( ICS Theme and/or PDroid ), even if it's supposed to be compatible, though I haven't tried kernels yet. I'll give your sig's setup a try and report back.
Meanwhile, could anything else be the issue? As you can probably tell, I've tried almost every mistake I could think of, and since my last phone had the same issue, a similar hardware issue seems unlikely.

All right, I've been running that ROM and kernel combo for a few days now. I don't seem to have any issues when I just flash the ROM and kernel, but I get stuck at the boot screen if I try to flash something else on top of it. Also, when I try to restore my text message backups through Gosms ( around 9800 texts that I want to keep ), the phone freezes halfway through the restore, and from that point on, the phone will freeze 5-10 minutes after rebooting, unless I reflash. I make sure I don't have the phone running and I leave it alone while restoring, and it doesn't help. I've only had this gosms issue since my flashing issue, and sometimes it restores fine.
Does anyone know what could be causing that?

[Q] Brick?

Hey guys. I just updated to Wicked Sensations 1.2 from 1.1. I used 1.1 for a few weeks and loved it, naturally I wanted 1.2 when it came out and I read the changelog. So I downloaded it, put it on the ext SD card. Booted to Clockwork Mod Recovery. I did a Nandroid backup. Then I wiped data 3 times, wiped Dalvik cache 3 times, and then installed from zip file. The install went great. I rebooted after it was done and the rom launched fine. I went through the initial setup and restored my Nova Home Screen settings. Then I went to try out the included Wifi Tether app. I launched it, it asked for root access, I granted it. Something didn't work as it was initializing, so I closed it and rebooted the phone, just to make sure all of it's processes were killed and my normal wifi would work normally. On reboot, the phone decided it needed to "Upgrade Apps". So I waited about an hour and it never left that screen. It didn't show me any sort of progress like it had before either when it optimized apps for Jellybean coming from ICS. So I popped the battery out. Now I'm doomed. Stuck on the boot screen with the "SAMSUNG" text with the animated glow effect. I also can't seem to get it into recovery mode to restore any of my backups.
Any thoughts? I'm fairly new to this so don't rule out dumb mistakes. Also, I noticed in the Wicked Sensations 1.2 instructions that I could have upgraded without doing a full data wipe, but it said to do a full wipe and clean install if you had any trouble with the upgrade, so I don't think that is the cause of my problems. Do I need to turn to Odin?

You have a soft brick since you can get up the boot logo screen....time to bust out Odin to save the day.
http://forum.xda-developers.com/showthread.php?t=1941546
Sent from my SPH-L710 using xda app-developers app

Thanks a bunch. I wasn't sweating too bad since I could turn it off and on and see a spark of life in it. Thanks for the link too. I'll confirm success or failure later tonight after a good few hours drive back home.

That fixed it for me. Thanks again.