Anyone using Sky-ICS on T989? - T-Mobile Samsung Galaxy S II SGH-T989

I would like try out the Sky-ICS ROM for the i727 Skyrocket:
http://forum.xda-developers.com/showthread.php?t=1377087
Has anyone successfully flashed this ROM on their T989? I flashed it's RC 7 version then used the conversion zip from here:
http://forum.xda-developers.com/showthread.php?t=1360355
Everything seemed fine until using Market forces a reboot, so I'm curious if any T989 owners have played around with this ROM?

Im running Sky ICS speed 7.4 with darksides kernel, runs beautifully. Little bit of playing around to get it running right but its been fine since (flashed this morning). I flashed the RC 7 let it boot and set everything up with the SR kernel first and let it sit for 5 mins, then flashed the 7.4 update, let it boot and sit for about 5 minutes, reflashed the darkside kernel did a few more reboots and it seems perfect. I didn't flash the conversion zip at all. No wifi/gps issues, market works great.
Good Luck

running skyics for a while now, no problems so far
did not flash the conversion zip, just any t989 kernel

Thanks both for responding. I'm still having difficulty with Market
I did a Darkside Superwipe, then flashed RC7. Market works fine at this point.
I then tried faux's T989 kernel and Market forces reboot.
Re-wiped and flashed RC7, this time with the Synergy T989 kernel, and same thing with Market.
I haven't gotten to 7.4 yet, but am thinking I'll just be content with our T989 ROMs for now...

You need to wipe factory data cache and format system then flash ROM then flash kernel after first boot should fix force close of market of not pm me cuz I have the srgs2 conversion file
Sent from my SGH-T989 using xda premium

Battery life is terrible but rom is nice.

Related

Problems flashing MIUI?

Anyone having problems flashing the most recent MIUI, or is it just me?
I'm on MYN Warm with stock kernel. I'm using Amon, factory reset and cleared the Dalvik.
It says that MIUI is installed, but when I reboot, it just goes to the default white EVO screen and stays there.
I've downloaded and tried it several times, but same result.
Is it because it is a Sense kernel? And do I flash the AOSP kernel or MIUI ROM first?
Sorry for my scrub questions - just rooted.
Sent from my Evo - WarmTwoPointTwo
Wipe data again then flash
sent from my HTC evolution running a freshly baked gingerbread with the 4gs in it
Do a full wipe, then flash the rom first; always the rom first. And if you flashed the kernel first, fine, but when you install the rom, that kernel will override the kernel you flashed, and then have to flash it again.
Also to make sure.. if your flashing the 1.3.5.. you need to install the 1.3.4 first.. then the 1.3.5.
1.3.4 - http://bit.ly/ePj9IF
1.3.5 - http://bit.ly/eY4Oal
(english)
Also, it has been noted several times.. and I've had much better luck with this rom since doing it this way.. But do a complete wipe.. then wipe cache.. then wipe dalvak.. And for good measure.. do it all at least 1 more time completely. I thought it was bs but I used to get force closes and reboots Constantly whenever i flashed this rom but ever since I wiped everything a couple times it works every time just fine. Hope this helps you out.
So I have to flash 1.3.4 first... okay, gotcha, thanks much. Just wondering, what AOSP kernel do you use/recommend? I know most people say that you need to experiment, but just wondering.
Sent from my Evo - Myn
After wiping your phone to your heart's content, flash 1.3.4, stay in recovery, flash 1.3.5 hotfix, stay in recovery, flash whatever else you need to (kernel, other mods, etc.)
I'm using the Tiamat 2.1.5 kernel, but I think I like the performance of Savage (NOT SavagedZen) 1.6 better/
Aight, thanks guys. Made a Nandroid backup, flashed everythink like you said and Savage 1.6 kernel, and everything is running smooth as butter. Thanks for the help

[Q] 6month of flashing and finally stump!!!

ok i've been flashing roms for over six months and have been able to fix every issues i've ever had until now..
was running cm nightly 21, tried to update to 23 a couple weeks ago and all i got was a boot loop on the white htc evo screen. ok so i re-download the nightly, clear cache dalvik data and reflash. same boot loop occur. so i waited a few days and new nightlys appeared. so i download and tried to flash. same results with the boot loop.
i reverted back to cm nightly 21. tried to flash savage zen 2.1 kernel. reboot. same white htc evo screen boot loop. flash savage zen 2.0 with cm nightly 21 and it works flawlessly. flashed cm rc2 with savage zen 2.0 and ran flawlessly but boot loops with sz 2.1-1.0.
problem: cm nightly 23 and up (23-30), cm rc3, savage zen 0.2.1 and up, and tiamat's latest kernel (3.32?) all would install properly but when phone boots it is stuck on boot loop at the white htc evo screen.
my remedies: wipe cache davik data 1x,2x,3x to no success. used caulkins all format zip plus the wiping of cache, etc to no success. i've tried wiping and flashing with ra mon 2.2-2.3 recovery and clockworkmod 2.5-3.0.5 and still no success. i've unrooted my phone, reroot, wipe and flash and no success. i've even tried to not wipe cache/dalvik and just flashing nightlies 23+ and rc3 and still same boot loop at the htc evo screen.. worth a try since i've done everything else i could think of..
here's my system: latest radio, wimax, prl, pri, hboot.. latest everything update. hardware revision 003. baseband 2.15.00.07.28. S-off. what else..
my thoughts: cm 23 and up, savage 2.1 and up, and tiamat's latest all incorporated hdmi into their builds. i've never used nor have the ability to activate hdmi on my phone. so i'm thinking it's something to do with hdmi? every other rom from cm 21- and rc2- and sense roms seem to work perfectly fine.
i am currently running cm rc2 with savage zen 2.0.. are my days of flashing the lastest and badarse combos of cm and savage zen over? please help if anyone have any ideas and thanks in advance..
losphn said:
ok i've been flashing roms for over six months and have been able to fix every issues i've ever had until now..
was running cm nightly 21, tried to update to 23 a couple weeks ago and all i got was a boot loop on the white htc evo screen. ok so i re-download the nightly, clear cache dalvik data and reflash. same boot loop occur. so i waited a few days and new nightlys appeared. so i download and tried to flash. same results with the boot loop.
i reverted back to cm nightly 21. tried to flash savage zen 2.1 kernel. reboot. same white htc evo screen boot loop. flash savage zen 2.0 with cm nightly 21 and it works flawlessly. flashed cm rc2 with savage zen 2.0 and ran flawlessly but boot loops with sz 2.1-1.0.
problem: cm nightly 23 and up (23-30), cm rc3, savage zen 0.2.1 and up, and tiamat's latest kernel (3.32?) all would install properly but when phone boots it is stuck on boot loop at the white htc evo screen.
my remedies: wipe cache davik data 1x,2x,3x to no success. used caulkins all format zip plus the wiping of cache, etc to no success. i've tried wiping and flashing with ra mon 2.2-2.3 recovery and clockworkmod 2.5-3.0.5 and still no success. i've unrooted my phone, reroot, wipe and flash and no success. i've even tried to not wipe cache/dalvik and just flashing nightlies 23+ and rc3 and still same boot loop at the htc evo screen.. worth a try since i've done everything else i could think of..
here's my system: latest radio, wimax, prl, pri, hboot.. latest everything update. hardware revision 003. baseband 2.15.00.07.28. S-off. what else..
my thoughts: cm 23 and up, savage 2.1 and up, and tiamat's latest all incorporated hdmi into their builds. i've never used nor have the ability to activate hdmi on my phone. so i'm thinking it's something to do with hdmi? every other rom from cm 21- and rc2- and sense roms seem to work perfectly fine.
i am currently running cm rc2 with savage zen 2.0.. are my days of flashing the lastest and badarse combos of cm and savage zen over? please help if anyone have any ideas and thanks in advance..
Click to expand...
Click to collapse
Strange indeed my friend. There have been many reports of bootlooping with cm7, and many can't recover. See the thread titled bootloops and no recovery. Its odd that older cm builds and sense work fine for you, and newer ones don't. Its interesting, your observation about the HDMI kernels. I wish I had some suggestions for you, but it appears as though you've exhausted all the things I would've suggested to you already. You've even ran ruu and rerooted. If that didn't work, I'm not sure what will...
Sent from my PC36100 using XDA App
going into recovery is fine. i've tried reflashing with ra mon 1.8, 2.2, and 2.3 recovery but still end up with the white screen boot loop. than i would switch to clockworkmod 2.5 and 3.0 and reflash the roms. they would all install fine with the recoveries saying "install from sd card complete". but when i reboot, it gets stuck on the htc screen! strange indeed..
losphn said:
going into recovery is fine. i've tried reflashing with ra mon 1.8, 2.2, and 2.3 recovery but still end up with the white screen boot loop. than i would switch to clockworkmod 2.5 and 3.0 and reflash the roms. they would all install fine with the recoveries saying "install from sd card complete". but when i reboot, it gets stuck on the htc screen! strange indeed..
Click to expand...
Click to collapse
Sounds like you tried everything before you even posted! At least you can run sense roms and older cm in the meantime, while you try to figure it out. Do other newer gingerbread builds flash and run for you? Or is it just cm7? I wish I had more to suggest, but like I said, it seems like you've covered your bases..
Sent from my PC36100 using XDA App
i've ran miks, myns, and fresh before from the sense side and all worked fine. from the gb side i've ran evolve, kings? (can't remeber right now), and cm starting from cm gingerbread 4 through 6.1.2 to cm7 nightly 21 where i got stuck. i have not try the newest gb roms outside cm. am downloading the latest from evolve now so will give it a shot.
f.y.i. to those afraid of cm roms, my current fig is rc2, sz 2.0 cfs wimax gb, with dark horse v1.0 cm7 rc2 theme and everything (minus hdmi) works flawlessly. i mean gps tracks and follows without drops, wifi works great, absolutely no issues with bluetooth, no random reboots, wimax connects quickly and doesn't drop, 3g hotspot works great, even 4g wireless hotspot works!! i swear it. tested it out the other night and it connected right away and started working. we used it on 4g for about 20 mins without drop.
if everything is working so great, why would i want to update roms? because the cm dev and team are badarse and i love their work (many thanks to you guys). plus titanium backup doesn't work...only app i use that gets fc. biggest irk though is that it just doesn't feel right not being able to flash the lastest builds..
losphn said:
i've ran miks, myns, and fresh before from the sense side and all worked fine. from the gb side i've ran evolve, kings? (can't remeber right now), and cm starting from cm gingerbread 4 through 6.1.2 to cm7 nightly 21 where i got stuck. i have not try the newest gb roms outside cm. am downloading the latest from evolve now so will give it a shot.
f.y.i. to those afraid of cm roms, my current fig is rc2, sz 2.0 cfs wimax gb, with dark horse v1.0 cm7 rc2 theme and everything (minus hdmi) works flawlessly. i mean gps tracks and follows without drops, wifi works great, absolutely no issues with bluetooth, no random reboots, wimax connects quickly and doesn't drop, 3g hotspot works great, even 4g wireless hotspot works!! i swear it. tested it out the other night and it connected right away and started working. we used it on 4g for about 20 mins without drop.
if everything is working so great, why would i want to update roms? because the cm dev and team are badarse and i love their work (many thanks to you guys). plus titanium backup doesn't work...only app i use that gets fc. biggest irk though is that it just doesn't feel right not being able to flash the lastest builds..
Click to expand...
Click to collapse
I will also say that I had good experiences with cm. It always ran smooth for me, and as you stated, everything worked. Same with all the other recent gingerbread roms have been flawless for me too. All the boot loop and no recovery issues, take it for what its worth. To each his own. I like all roms, but ill be on sense for a little while.
Sent from my PC36100 using XDA App
Have you tried flashing the FORMAT_ALL.zip from calkulin?
housry23 said:
Have you tried flashing the FORMAT_ALL.zip from calkulin?
Click to expand...
Click to collapse
my remedies: wipe cache davik data 1x,2x,3x to no success. used caulkins all format zip plus the wiping of cache, etc to no success. i've tried wiping and flashing with ra mon 2.2-2.3 recovery and clockworkmod 2.5-3.0.5 and still no success. i've unrooted my phone, reroot, wipe and flash and no success. i've even tried to not wipe cache/dalvik and just flashing nightlies 23+ and rc3 and still same boot loop at the htc evo screen.. worth a try since i've done everything else i could think of..
From the OP ^^^^ He's wiped with calk's format all, used different recoveries, he's gone as far as unrooting and then re rooting. wiping again. He's tried everything I could think of. Reflashing recoveries(different versions), ran RUU's, re rooting....what's left?
thanks buckley
Sent from my PC36100 using XDA App
Guys, this is all over the forums now. Something in CM is causing these major problems that people are not able to recover from. One theory is that it's causing a bad block in the internal memory, which apparently, the Evo can't recover from.
I think I got lucky when it happened to me last month, where I suddenly white screened for no reason, while running a CM ROM, and I RUU'd my way out of it, but the problem has gotten much worse, obviously.
I loved CM, but at this point, I'm not stupid enough to try and run it anymore.
I hate to sound rash, but I'd lose any CM Rom's you guys are running until the Dev's can figure this one out.

can't flash anything in cm7 recovery

i'm trying install cm9 or miui 4 or aokp but am running into a problem where i can't flash anything from cwm bundled with cm7. i'm doing these exact steps as stated here in Part 1:
with calk's el29 installed (with Rogue 1.1.2 based off cwm 5.0.2.7), i booted into recovery and wiped data except for battery stats. i flashed cm7 from here. i immediately booted into cm7, then immediately rebooted back into cwm recovery. from here, i tried flashing cm9, miui 4, aokp alpha 1, and aokp alpha 2. they all fail saying "E: can't open /sdcard/romname.zip (bad) Installation aborted."
what am i doing wrong?
I would flash cm7 again, boot, then reboot into recovery again and try to flash another ics ROM. Just make sure to remember not to wipe data until after you flash an ics ROM and gapps
Sent from my SPH-D710 using Tapatalk
Back in the vibrant days (tmobile galaxy s) if you had any problems with flashing the "fix" was to start all over via Odin and a rooted stock ROM...
Dunno if that is something that is still a good idea to do.. But worth a try...
paranoid android85 said:
I would flash cm7 again, boot, then reboot into recovery again and try to flash another ics ROM. Just make sure to remember not to wipe data until after you flash an ics ROM and gapps
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
i've tried aokp and miui4. no bueno. in fact, it wont flash anything i have, including calk's wipe all script.
Bear gri11z said:
Back in the vibrant days (tmobile galaxy s) if you had any problems with flashing the "fix" was to start all over via Odin and a rooted stock ROM...
Dunno if that is something that is still a good idea to do.. But worth a try...
Click to expand...
Click to collapse
tried that like 4 times lol. i'm actually gonna try copying all the ics roms onto my sdcard again, this time from within android itself. all the roms had been transferred over while usb was mounted in cwm and i noticed the transfers would pause at times or not complete at all, forcing me to start them over. perhaps that's the problem.

Ready to flash from stock for 1st time but few questions.

Hey everybody.
I used to flash all sorts of roms on my old galaxy vibrant but I bought a new t989 a few months ago and I want to go to a custom from the stock tmob bloatware infested ICS. I already rooted via odin and installed clockwork recovery, which comes up just fine with the usual volume and power combo so i'm good there.
My question is should I flash my first rom (probably jedi mind trick 5 or x1,or if anyone knows a daily driver ready jelly bean??)
via clockwork mod like on my vibrant? or do I use twrp which I also have via goo manager? I prefer cwm because I am familiar with how to wipe cache, reset and flash with it but I can't figure out why some mods recommend one or the other.
Also,
I keep seeing some roms that come with a radio zip and was wondering if all roms require this or is it just certain roms?
Thanks in advance for any help. I just don't want to wreck my phone the first time. Remember, I've flashed a million times on my vibrant but never on my t989 so any pointers or heads up would be appreciated.
Get darkside wipe scripts (both wipe cache and super wipe)
Go ahead with the Jedi X1 ROM its very stable and fast as hell
But if you want Jelly Bean I recommend Galaxy SBean v8 or Liquidsmooth rc8 they're the most stable JB ROMs from what I experienced
Remember to always wipe dalvic cache and fix permissions (darkside cache wipe) after flashing a new ROM
After you flash your ROM and Gapps then boot that's when you can flash kernels, mods, and apk's so it would have a lesser chance of a soft brick
Happy Flashing!
Sent from my SGH-T989 using xda app-developers app
arthurgreeeen said:
Get darkside wipe scripts (both wipe cache and super wipe)
Go ahead with the Jedi X1 ROM its very stable and fast as hell
But if you want Jelly Bean I recommend Galaxy SBean v8 or Liquidsmooth rc8 they're the most stable JB ROMs from what I experienced
Remember to always wipe dalvic cache and fix permissions (darkside cache wipe) after flashing a new ROM
After you flash your ROM and Gapps then boot that's when you can flash kernels, mods, and apk's so it would have a lesser chance of a soft brick
Happy Flashing!
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Cool. Thanks for the reply. I went and grabbed super wipe and cache wipe. So essentially, I just put those two on my sd and flash like I do a rom zip from recovery and then flash the rom itself and do a darkside cache wipe after new rom is installed before restarting and booting for the first time? Do I still need to do factory reset/wipe or is that part of the scripts? I have the goo app so I can use twrp instead since it's recommended for almost all roms I will be installing. Any major reason why, besides that it has touch function and backup renaming? Is it safe to install from the goo app on stock rom?
I think I will probably try one of the jellybean roms you suggested. I just didn't want random reboots, and I heard that's an issue with jelly bean roms but I think that might have been specific to aokp ones or something. Occasional FCs aren't too big of a deal though.
One other thing though... how do I fix permissions? I kept reading about that but never did it. Do you mean in recovery or under superuser?
how to properly flash a rom
http://forum.xda-developers.com/showthread.php?t=1926754
just follow that and you should be fine.
you can fix permission in recovery. its under advanced in cwm and twrp.
merrygocow said:
how to properly flash a rom
http://forum.xda-developers.com/showthread.php?t=1926754
just follow that and you should be fine.
you can fix permission in recovery. its under advanced in cwm and twrp.
Click to expand...
Click to collapse
Ok thanks. He seems to recommend not using the darkside scripts. I have a slightly older CWM 5.0.2.6 that I did via odin BTW so do I fall into the 'don't' use darkside category or does he mean anything after 5.0.2.7? I don't mind wiping cache and dalvik manually and doing all the formats if that's the case.
Do I fix permissions after I have booted the rom and waited 10 mins and restarted back into cwm or before I boot it for the first time?
benjmiester said:
Ok thanks. He seems to recommend not using the darkside scripts. I have a slightly older CWM 5.0.2.6 that I did via odin BTW so do I fall into the 'don't' use darkside category or does he mean anything after 5.0.2.7? I don't mind wiping cache and dalvik manually and doing all the formats if that's the case.
Do I fix permissions after I have booted the rom and waited 10 mins and restarted back into cwm or before I boot it for the first time?
Click to expand...
Click to collapse
I usually do it after flashing. And you don't need to do it every single time. Also, there's no need to follow everything down to the letter when you flash, wipe cache/dalvik/factory reset/wipe system/fix permissions/sit for 10 mins/reboot/reboot again/etc. Flashing is like cooking. As long as you don't deviate too much from the recipe, you'll get edible food (or a working ROM). If it doesn't work out, just toss the food out and try again (softbricked phone, reflash). If you try something stupid, you'll set your kitchen on fire when you don't have insurance (comparable to hard bricking your phone).
I usually wait till I've restored all my apps before fixing permissions, and then sometimes I don't if everything is working fine. As for recovery, I know you're familiar with CWM, but I'd recommend spending some time using TWRP. It's really great. You don't need the scripts with TWRP, but since TWRP lets you cue up zips, you can set it to do super wipe, ROM, gapps, and cache wipe all in one go. Kinda cool. And if you're itching to try jelly bean, AOKP JB milestone 1 is stable and smooth. There are even a couple custom kernels for it and CM10 (which has also reached a stable version, though I haven't tried it).
Sent from my beastly Galaxy S 2.
Dark side super wipe and cache wipe work perfectly on 5.0.2.6! That's how I got PACman ROM on my phone. I didn't bother with fix permissions. Well, I would say don't worry unless the instructions specify to do so.
Either way, I like CWM because I used it on my Samsung Galaxy Ace. Its just the wipes are broken for this phone so the scripts have to be used and work perfect. Happy flashing!
Sent from my SAMSUNG-SGH-T989 using xda premium
benjmiester said:
Ok thanks. He seems to recommend not using the darkside scripts. I have a slightly older CWM 5.0.2.6 that I did via odin BTW so do I fall into the 'don't' use darkside category or does he mean anything after 5.0.2.7? I don't mind wiping cache and dalvik manually and doing all the formats if that's the case.
Do I fix permissions after I have booted the rom and waited 10 mins and restarted back into cwm or before I boot it for the first time?
Click to expand...
Click to collapse
no it's fine to use the scripts w/ cwm 5. just don't use the scripts on cwm 6. that's what he meant.
i usually fix permission after the first reboot & waiting 10-15 mins.
i second the twrp recommendation...however if you're flashing something old, then cwm is the way to go. i haven't had any problems flashing anything in cwm. the latest twrp however failed me after i tried to flash a gb theme for jugg lol.
merrygocow said:
no it's fine to use the scripts w/ cwm 5. just don't use the scripts on cwm 6. that's what he meant.
i usually fix permission after the first reboot & waiting 10-15 mins.
i second the twrp recommendation...however if you're flashing something old, then cwm is the way to go. i haven't had any problems flashing anything in cwm. the latest twrp however failed me after i tried to flash a gb theme for jugg lol.
Click to expand...
Click to collapse
Ok, just wanted to make sure on that one.
Thanks for all the input everybody. Hopefully I will get a chance to do my flash over the holiday. I plan on going with the Sbean V8. Really all of the roms out look excellent but this one looks good for a JB daily driver. I went ahead and downloaded Jedi X1 too though in case the sbean doesn't work out for whatever reason. I have to tether my phone at home for internet so I thought it might be good to have a backup just in case PDAnet doesn't want to work.
Is twrp ok to install from Goo manager on my stock rom or should I flash a new rom and then use it from then on? I just want to make sure it won't conflict with the stocker or the CWM that I have on it already.
benjmiester said:
Ok, just wanted to make sure on that one.
Thanks for all the input everybody. Hopefully I will get a chance to do my flash over the holiday. I plan on going with the Sbean V8. Really all of the roms out look excellent but this one looks good for a JB daily driver. I went ahead and downloaded Jedi X1 too though in case the sbean doesn't work out for whatever reason. I have to tether my phone at home for internet so I thought it might be good to have a backup just in case PDAnet doesn't want to work.
Is twrp ok to install from Goo manager on my stock rom or should I flash a new rom and then use it from then on? I just want to make sure it won't conflict with the stocker or the CWM that I have on it already.
Click to expand...
Click to collapse
--Update--
I got Sbean v8 installed and working just wonderfully! I used CWM for my install with the darkside superwipe and cache wipe scripts. Everything went fine and i'm very happy with the new rom. Thanks everyone. I hope this thread will help any other first flashers in the future.

Kinda Stuck for now

Hey guys, i just upgraded from our t989 to a moto x and i decided to start testing roms out on the t989 since its not my main phone anymore, i only flashed about two roms and i have already done something wrong, flashed Aokp Milestone first, nothing wrong here enjoyed aokp back in 4.2.2 days. now i have always wanted to use Jedi mind trick but i was worried about the problems with it, so i made a backup of Aokp and Wiped data/wiped cache and flashed darkside wipe then flashed Jedi mind trick and rebooted. it got stuck at the splash screen like the details in the rom said but now when i try to make a backup, wipe data, cache, flash Jedi mind trick, flash darkside wipe it will freeze, i have tried flashing Cyanogenmod 10.2 and still freezes, i decided to just restore to stock but Odin 1.8.5 will not find my Device when it goes into download mode. right now i am trying my aokp Backup it had been going Fine for awhile but it looks like it might have Froze on /storage/sdcard0: mounted. any help please? i dont think i could google this problem.
Edit: now when i boot into cwm it says Can"T open /cache/recovery/last_log twice.
plugged it into a different computer and got odin working, could anyone show me the correct way to install Jedi mind trick? also it comes with that kernel so it can be overclocked to 2ghz right?
Trozzul said:
plugged it into a different computer and got odin working, could anyone show me the correct way to install Jedi mind trick? also it comes with that kernel so it can be overclocked to 2ghz right?
Click to expand...
Click to collapse
Not sure about specific jedi issues, its been inactive a long time.
But for any 4.1.2 touchwiz roms ...personally I flash twrp 2.5.0.0. 2.6.0.0 is probably OK, but any higher can cause issues with 4.1.2.
Also, you should use the infamous wipes. Darkside is outdated. I believe infamous wipes are based on dark side, but they've been updated for jelly bean. Darkside wipes stopped being updated at ICS.
See how that works.
Oh, and for more current 4.1.2 ROMs, @Rushing has a few.

Categories

Resources