Database Info

[Q] Back to stock Telus Fascinate after flashing Darky 10

Hi,
I have a Telus Fascinate (T959D) that I've flashed with Darky's 10.0 "Final".
I've read countless threads that tell me NOT to flash bootloaders to this phone, but we were adventurous (I don't own the device, a friend does) and wanted to try the latest Darky on it since it was working beautifully on my GT-I9000M.
Sadly, Darky's ROM requires a different bootloader, and it comes from an I9000.
After following the guide to install Darky, it effectively puts an I9000 bootloader, kernel, and ROM on the phone. (Shame on me, I know).
OK, so the problems are:
1.) No way to get into download mode or recovery mode without booting completely and issuing a 'reboot download' or 'reboot recovery' from a su terminal (or adb)
2.) The home and search softkeys act like left and right instead
There are other Darky related bugs, but not important to this discussion.
My question is: What is the safest/most reliable way to go back to stock Fascinate, bootloader and all? At this point since we don't have access to download mode without the phone booting properly, we don't want to flash anything else unless it's going to give us download mode back.
I've read the guides on going back to stock, but they all say you needed to have flashed a certain Telus ROM before going custom, and I don't know what exactly this phone had on it for sure. My friend says it was whatever was the latest update from Telus, but he hasn't plugged it into Kies in a while so I couldn't confirm for sure.
The idea here is to go back to stock then flash a custom kernel and possible a different modem to help with battery life and signal problems, and possibly some custom roms that don't require changing the bootloader.
Any insight would be greatly appreciated. If any additional info is needed, I'll provide it.

Hey just curious if you ever solved this problem as i currently have the exact same problem with a different Rom it won't allow me to boot into recovery and cwm won't recover my nandroid

Very unreliable TF101 and confused

Hi,
I have had a TF101 for over a year. However it was used by someone else who upgraded it 0.17 and when it came to be me was unreliable and would often randomly reboot and then get stuck on the 'EEEpad' screen (before it says ASUS etc).
I am new to Android (been on webOS for a few years) so rooting etc is new ground for me, but I am pretty technical. Had lots of webOS patches and overclocking installed.
I 'upgraded' to 0.24 and then started reading as much as I can on this site after the reboots remained. I now realise I made two fundamental mistakes
1) Going to 0.24 at all seems to be a no-no from what I'v read.
2) I didn't do a clean restart before upgrading.
I'm not too worried about staying with stock but I do need the thing not to re-boot as often (15 times yesterday !!), so I am wondering.
1) Is 0.24 on a factory reset machine better for rebooting ? If so how do I get back to that state given that I have 0.24 already so can't reset and then re-install 0.24 (as I think I should have) ?
2) Is the only way to make it reliable to go for a customised ROM/Kernel/Bootloader etc ?
3) If (2) is true and I need a different ROM/kernel etc which is the most reliable ?
I know I need to do the downgrade, root, clockworkmod etc but can probably handle that from other threads.
Many thanks for anyone taking the time to respond.

1: A factory reset *May* help, but there's problems with official ICS anyway.. I haven't tried stock ICS and have no intention of trying it with all the horrid reports I read.
2: I would say this is your best option, put a ROM on, you won't regret it.
3: You will need to flash a ROM, boot it once, then wipe caches again and flash a kernel. As for kernel IMO your best choice is Guevor's kernel, (I'm using v20.6 and it's perfect.) As far as ROM I recommend ARHD or Revolver if you like stock look, and Megatron or AOKP if you like AOSP based roms. (its all preference here)

15 reboots in one day? Have you tried a factory reset yet? That sounds excessive.
But I have zero problems with ARHD 3.4 and Guevors kernel.

As the 2 previous posters suggest - I think a factory reset could possibly help.
If not then I would root, and install a custom ROM. I'm using Revolver and stock kernel with zero RR or SOD. I tried Guevor's kernel and it just didn't agree with my particular TF-101. I also tried ARHD and it worked great but I just prefer the aesthetics of Revolver. Good luck and I sure hope you get your reboot issues fixed soon.

Many thanks for the help, I will do a factory reset.
I suspect that won't work so will look in to rooting and custom roms etc.
I gather I need to downgrade ?
I know there are instructions out there so I will go and have a look at them in preperation !
Thanks again.

rege0039 said:
Many thanks for the help, I will do a factory reset.
I suspect that won't work so will look in to rooting and custom roms etc.
I gather I need to downgrade ?
I know there are instructions out there so I will go and have a look at them in preperation !
Thanks again.
Click to expand...
Click to collapse
As you have had the unit over a year --> old serial# --> it has to be nvflash-able. So you have an option for an easy one-step installation.

Erm, OK - now I am a bit lost !
I want a rooted machine, Clockwork mod and a chance to try custom roms and kernels.
I seem to be able to find instructions for one but not the others, some want to put back stock rom but I am don't want that.
Sorry to be thick, and maybe I'm looking in a panic and getting lost but is there some instructions to follow to take it from 0.24 to being rooted and able to load custom roms. If I get to Clockwork mod I know how to use that to flash etc as I had it on my touchpad before I want completely to Android.
nv-flasable - what does that mean ? Can I check my serial number to know I can do it ? Stickers seems to have come off so not sure I know serial
Sorry for sounding confused and not looking enough - I really have tried but can't seem to get instructions that go from where I am to where I need to be !!!
Thanks again.

NvFlash
NvFlash is a utility that older tabs (With Sbkv1) can use to easily flash a recovery on the system. ASUS has basically two passkeys for the TF101 to get into APX mode, Sbkv1, and Sbkv2. Sbkv1 is the passkey everyone has, and Sbkv2 is currently unknown/locked. What Sbk you have is based on the serial number of your tablet (you can look at the box if you still have it, or find the stickers, also when did you purchase the tab, if it was before July 2011 then you for sure have Sbkv1, if not it may be Sbkv2) If your serial number starts with B60 or below (B50 B40 etc...) it has Sbkv1, if it has B70 or higher, it has Sbkv2. Find out what Sbk you have (it should be version one) then download NvFlash from Rayman's thread. Search nvflash unbricking released in the development forum. Once you have that get an NvFlashable recovery (I recommend Rouge XM touch recovery 1.5, since it reads from internal and external memory, again search in development.) Boot your tablet into APX mode and connect to your computer (Turn off, hold Volume-UP and power.) Install the driver, then follow instructions from NvFlash thread to flash the new recovery. Once you have this, you can place a ROM on your tab (All roms are pre-rooted, no need to install superuser) boot into your new CWM recovery with Power + Volume-DOWN, then press Volume-Up after a few seconds. Wipe data/factory reset, wipe cache, wipe Dalvik-cache, install zip from... find your ROM.zip (don't extract it) and install! Then reboot and let it install, after booting once, you can go back into CWM recovery to install a kernel.zip that you also place on your tab (I recommend Guevor's kernel, make sure you wipe cache and dalvik-cache again.) Then you're all set!
Any other Q's?

Ok. I think I follow all that. Many, many thanks.
I will go to work tomorow and look for the box, but I'm pretty sure it was bought before July 2011.
Need to do something, sure it's cos I am now counting but today held the record at 29 reboots ! Four within 8 minutes at one point.
I think I will go Android Revolution and the kernel you mentioned.
Would be great to bo rooted as I have Titanium license as well.
Thanks again. webOS forums were always good, XDA proving so as well.

Nvflash was just released for Sbkv2, so just use NvFlash, it's easiest good luck!

Thanks for following this up with the latest news !
As far as I can see the wheelie setup is for LINUX only ?
I'm on Windows 7, I could set it up as a dual boot but am complete newbie at Linux !

It's not that bad to set up, just download virtualbox from Oracle, then an ubuntu.iso installation, and run it as a virtual machine within windows. Easier than dual boot. It isn't too hard to set up, essentially download and extract.

So ...
Good news is got it rooted, clockworkmod installed (using the Rogue version that was suggested) and then went installed Android Revolution latest version. Did all the required resets, dalvik and cache wipes etc.
Great I, thought, until ...
All day to day it has rebooted frequently even though I installed no other s/w - just what comes with Android Revolution. It seems to more frequent when the device has powered down after a period of inactivity.
Is it now time to start thinking this is a h/w problem ?
Will a different custom ROM be worth a go or would a different kernel help (which I haven't tried yet) ? If so I wasn't sure which version of the suggested kernel (Guevors) I should go for as there seemed to a lot of them.
Once again, thanks for any and all time. NVFlash was a revelation and really not that hard once I had the drivers installed.

Have now installed v21 of the kernel and got CPU tuner to change minimum cpu speed, wasn't sure about voltages.
Is there a recommended way to set cpu speed, governors and voltages ?
At the point of thinking this will never be stable again. Not even getting 30 minutes without a random reboot.

Try version 17c of guevor's if 21 is giving you issues, and any Cm9 based build will have overclock change built in. I don't use overclock apps, they give me problems. Make sure you SuperWipe, then try reinstalling ARHD (or a aosp/aokp/etc rom) flash either 20.1version6 guevor or 17c and don't overclock (default it overclocks a bit to 1200). See if it is finally stable, if not you might have borked hardware :/

It's charging at the moment, after I night of rebooting I presume.
I've got the SuperWipe zip so I will run that (which I didn't before but did do a reset, cache and dalvik wipe) and then put Revolution on after that.
I looked at Megatrons ROM as well - any comments on its reliability ?
I've not noticed it only does it when the device has been left for a few minutes. If I keep using it and don't let it sleep then things seems OK.

Megatron is really stable, I've found. I like aosp better too.

Those who experience rr or SoD can downgrade via nvflash to Any custom rom , prime 1.4 for example, and then upgrade by way of cwm to an ics aopk to make those problems disappear?
EDIT: megatron is very stable and have an awesome battery life. And the pop ups telling us there's a new update is great too
Sent from my Transformer TF101 using XDA Premium HD app

Hi,
Have been away with unreliable internet access but am now back.
I'm starting to think there must be a h/w problem as nothing seems to make the thing stop rebooting. The only pattern I can see is that if the device is being charged (either from the mains or by being plugged in to the keyboard) then it seems to stay up. Not sure if a certain battery level makes a difference.
I went through the whole SuperWipe clean and Revolution install, then put on the 17c kernel (At least I think I did About shows 2.6.39.4-g8fc25a9-dirty for the kernel, is that right ?) and am still have lots of reboots.
Tried Megatron with the same kernel and couldn't get wifi but still got a couple of reboots.
Any other suggestions ?
Or does anyone know a way of getting repairs done on this in the UK ?

You'll want to RMA to ASUS if nothing works :/

Please help solve software issues w/ Captivate i896. Advice on installing custom ROMS

Hello everybody,
I´ve got a Rogers Captivate i896 with Firmware version 2.2 (stock Rogers firmware(Canada), flashed 1 year ago, upgrading from 2.1 stock)
Kernel version 2.6.32.9
Modem version UXJL1
Rooted, unlocked and 1 click Lagfix
I´m on Rogers network.
Problems:
1) Many applications stop working once updated. IM+ version 4.xx works, anything higher crashes on start. Same story happens with LOTS of apps from Playstore, so I´m forced to be careful when updating apps. This is becoming super-annoying.
2)Recently, installed DROIDVPN and TUN.KO installer to use Dell voice on an Unlimited Mobile Browsing plan(crippled data for WAP browsing). It worked beautifully for 1 day, now starting DROIDVPN or TUN.KO makes the phone restart.
3)I´d like to get rid of built-in garbage, most of which I do not use, to have more control over running apps, especially those that hang themselves into start-up.
4) I´d like to get better battery life. I use my phone more and more, I´ve got 2 batteries and and external charger, and yet i sometimes have trouble getting to the end of the day without my phone dying/I]
Solutions.
I imagine that the only explanation for apps that simply refuse to work is that they are designed for newer Android systems. This happened with Skype that didn´t work with Eclair, but does work with 2.2.
Should I upgrade to ICS?
I have some experience flashing, yet I´m far from an expert. What´s the most fail-safe plan of actions? Would the following work:
1)Backup everything using TitaniumBackup
2)Install custom bootloader that would allow me to flash install.zip from external SD card
3)Choose a custom ROM based on user feedbacks, like Cyanogen MOD.
4)Restore all the apps
5)Experiment with different modem firmware to see which gives me best performance
I no longer have time to tinker around in the dark, so I´d like to have a plan before I get started. Any input on the possible solutions to the problems I´m experiencing?
Thank you in advance.

All the info you need on how to flash (specific to Canadian / Rogers version of Captivate):
http://forum.xda-developers.com/showthread.php?t=1350266
Modems for specific region:
http://forum.xda-developers.com/showthread.php?t=1227717
Just a question: why haven't you upgraded to Rogers official GB?
And BTW, ICS is a massive improvement over 2.1, 2.2 and 2.3.
I have a great experience with this ICS Rom:
http://forum.xda-developers.com/showthread.php?t=1522881
But there are others that are just as good I'm sure.

My 2 cents:
Stay away from ICS. It has the ability to damage your SD card.
Use this post to upgrade to gingerbread. Then use the utility in my signature to get root and cwm. Then choose a GB based ROM that suits your needs. May I suggest Legend?

¨Use this post to upgrade to gingerbread. Then use the utility in my signature to get root and cwm¨
Wouldn´t it be wiser to get clockwork mod before any upgrading just in case things go bad? I vaguely remember using clockworkmod last time I dealt with flashing, isn´t it a loader that allows you to load install.zip from SD card? Or would flashing a new system wipe out the mod as well?
How exactly can ICS damage SD card. Are you talking about the external SD or the built-in SD storage in the phone?
I´ve read partially the threads on Legend and Android Open Kang Project - captivatemtd - Milestone 6. Both sound pretty good. As far as you guys know, which rom is known to give best battery life?

If you're going to upgrade to a custom rom that is Gingerbread or Higher, you will need the Gingerbread bootloaders. That is why I say to go to stock Gingerbread first.
ICS can cause the Encryption Unsuccessful bug as seen here. It will cause you to lose all access to the built-in SD storage. It doesn't happen to everyone, but when it does, you'll wish you had heeded my advice.

Options for Verizon 3G Xoom

I just ordered a recertified Verizon 3G Xoom, and I didn't think about the implications of it being a Verizon device. This is NOT upgraded to 4G LTE -- will the "Stingray" builds of the various ROMS still work? Is there any way to apply WIFI-only ROMS (including stock) if I don't care about the 3G working? Given the age of the device I really want to get Jelly Bean on it.
I will need to cancel this order ASAP if the answers to these questions turn out to be "no"...

Same question from me.
Can we install the WiFi only version of ROMs (CM9 in particular) onto a Verizon 3G Xoom and have it work for everything EXCEPT the 3g? I could honestly care less about ever activating it on Verizonas long as WIFI works.

trunzoc said:
Same question from me.
Can we install the WiFi only version of ROMs (CM9 in particular) onto a Verizon 3G Xoom and have it work for everything EXCEPT the 3g? I could honestly care less about ever activating it on Verizonas long as WIFI works.
Click to expand...
Click to collapse
From reading a bit in the Development sub-forum, it looks like there's a JB leak for the VZW version, and either version (WIFI Only or VZW) of the EOS 3 ROM should work. I think I will keep my order.

magnafides said:
From reading a bit in the Development sub-forum, it looks like there's a JB leak for the VZW version, and either version (WIFI Only or VZW) of the EOS 3 ROM should work. I think I will keep my order.
Click to expand...
Click to collapse
Thanks. I'm placing my order as soon as Wife says OK. If you don't mind, and if you remember, please send me a PM of how it goes with the flashing once to get yours.
Would love to coordinate what we do since there doesn;t seem like a whole lot of certainty exists about what we are trying to do.

I'm probably just going to flash the EOS 3 WIFI Only version. According to one of the devs, it should work fine:
http://forum.xda-developers.com/showpost.php?p=28578030&postcount=8
But I will try to remember to let you know how it goes.

magnafides said:
I'm probably just going to flash the EOS 3 WIFI Only version. According to one of the devs, it should work fine:
http://forum.xda-developers.com/showpost.php?p=28578030&postcount=8
But I will try to remember to let you know how it goes.
Click to expand...
Click to collapse
Any luck? I also have a Xoom 3G MZ600 on the way and could careless about 3G...

hasnt eos got jellybean roms for all versions of the xoom? 3g should work imo
Sent from my Xoom using XDA Premium App

I'm in the same boat and curious to see if anybody has any words of wisdom. I love my refurbed Xoom 3G but am eager to get JB on it. Any help is greatly appreciated.

FWIW everything I have heard/read seems to indicate that it is possible to flash WiFi only ROMs on the 3G Xoom, and apparently everything will work fine except for the 3G (naturally). I haven't taken the plunge yet myself, still running stock ICS.
Is there any word on whether the Verizon 3G Xoom will get Jelly Bean?

It can be done....
I purchased a used 3g Xoom around Apr 2012. After initially unlocking / rooting and installing a ROM (EOS) on my 3g Xoom, the 3G radio wasn't working so I started fresh. I locked the device and SBF'd the original Xoom firmware, then used the official over the air (OTA) upgrades to get back to stock ICS. I thought this might fix the 3g issue; it did nothing.
EOS Roms overclock the GPU by default, which caused problems with my (and my wife's Wifi version) Xoom. My only requirements for a ROM are stability, no clutter from dumb carrier installed applications, compatibility, and of course root access. I found a pre-rooted stock Jellybean rom, but it was for the Wifi Xoom. It worked great on my wife's though; and heard rumors that it could work with mine.
*SO*...I took a leap of faith and installed it. It works great. No 3g radio of course, but I gave up on trying to get that to work anyway...so if you don't care about losing your 3g , this will probably work for you. I don't think my 3g will ever work, but I suspect this won't ruin yours if it is currently working. Don't hold me to that; this is a risk.
Random notes and refresher info:
-you will need an SD card. I'm pretty sure the following instructions will only work if you use one.
-If at any point you get the android guy with an orange exclamation point during boot...it is probably ok, just let it sit there for a couple minutes. it should continue to boot into whatever ROM you are currently on. Make sure you enable usb debugging in settings after boot.
-to access RSD, Recovery, or Fastboot mode, press and hold your power button to start the Xoom booting. When you see the Motorola logo, wait a second then press the volume down button. Then you can use volume down again to cycle through your options, and use volume up to choose one.
-the exact differences between RSD / Fastboot and Recovery modes are beyond the scope of this post (and me) so just know that your Xoom can be modified using software on your PC via USB with RSD and Fastboot modes, and stock recovery can be replaced with modified versions to add more functionality. Recovery is used to do all sorts of things...flash Roms, mount drives, format, cleanup caches, etc.
***
General instructions. Just guidelines; you will probably need some previous experience with computers / rooting etc.
(If you are already unlocked, rooted, and have a replacement recovery, skip to the last step.)
1.) Follow this guide to prep your Xoom: (unlocking, rooting, and install CWM recovery)
http://www.xoomforums.com/forum/motorola-xoom-development/15179-how-rookie-rooting-flashing-unrooting-under-one-roof.html
Note: you may have heard of Lord AOI tool; it is supposedly designed to simply the above process. I found it didn't work well and was more difficult to use than good ol' adb commands. I recommend skipping it.
2.) OPTIONAL: Next, I recommend using the latest Rogue recovery. Just use standard CWM recovery to flash it. It is nice because it allows you to use the touchscreen to manipulate instead of having to use the hardware buttons (volume buttons are kind of a pain). See here: http://forum.xda-developers.com/showthread.php?t=1235170
3.) Finally, flash the pre-rooted stock Jellybean ROM. See here: http://forum.xda-developers.com/showthread.php?t=1796335
(here's the direct ROM link for those not needing instructions or extra info: http://www.mediafire.com/?7w5w65l66hgggo8 )
Good luck and let us know your results...

Samsung Galaxy Discover S730M (and S730G) Custom ROM - by doctor_evil

No longer own this phone, and no longer have a copy of the rom so this is no longer being developed.
Thanks to @shifattk and @FitAmp for the overclock
Thanks to @Restl3ss, who is working on a rooted and overclocked, otherwise bone stock ROM
Thanks to @atmu5fear, who made the first flashable rom for the S730M, I based my Rom off your original release.
changes I made from the stock 4.04 image
Rooted
BusyBox
Overclocked to 1000mhz
Nova Launcher
Default Ringtone: Crank
Disabled power on and power off boot sounds
Bloat Removed
Theme Changes
Zipaligned
Replaced Samsung keyboard with the google keyboard (much better IMHO)
Stable
Working and tested. Tested on a S730M as well as a S730G
Flashing instructions:
1. Use CWM 6.0.3.1 Get it here https://docs.google.com/file/d/0B1BxFtN0QItNUExLMHBWT1loQjg/edit?usp=sharing, flash with Odin)
2. Make a backup, if things go wrong for you, you cause use the backup to restore your phone's original firmware.
3. WIPE DATA/CACHE
4. Flash
5. Wipe Dalvik.
6. Reboot
NOTE: I can not and will not be responsible for any damage this rom could potentially cause on your phone, http://en.wikipedia.org/wiki/Caveat_emptor
Download Version 1.0 here

Good to see someone still working on this device
Sent from my HTC One using Tapatalk

FitAmp said:
Good to see someone still working on this device
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
It's a nifty little phone. I personally think it's better than a Nexus S but just suffers from the typical Samsung pump and dump routine where they sold all their inventory to the carriers then stopped supporting it with any updates.

Good job! I have 3 versions of the stock ROM available for this device as well, may have been more appropriate for a base, there's stock, stock + root + Busybox, stock + root + Busybox + overclock. Find them here
http://forum.xda-developers.com/showthread.php?t=2677332
Sent from my SGH-T989D using XDA Premium 4 mobile app

r740c
Will these ROMS work with the Cricket version?

kadeleblanc said:
Will these ROMS work with the Cricket version?
Click to expand...
Click to collapse
If the cricket model you have is a GSM version then yes it should so long as its a S730M or S730G. If its a CDMA model then no.

CDMA
doctor_evil said:
If the cricket model you have is a GSM version then yes it should so long as its a S730M or S730G. If its a CDMA model then no.
Click to expand...
Click to collapse
It doesnt take a sim card so no GSM. Is there any other ROMs that you would know of? We are kind of stuck out with this model, it kinda sucks lol.

kadeleblanc said:
It doesnt take a sim card so no GSM. Is there any other ROMs that you would know of? We are kind of stuck out with this model, it kinda sucks lol.
Click to expand...
Click to collapse
You may be able to use the same CWM recovery on that model,
you should be able to probably use the same kernel to overclock your model too, and you can probably use the kitchen app we used to cook these different version roms for the 730M and 730G models to do your own custom rom, just remember before you start working, to do a full nandroid backup of the current rom so you can restore it back to the original (mostly stock except for the cwm recovery) firmware if you need to later on.

By any chance this will unlock it or do you know a way for me to get the unlock using hex?

Thanks to doctor evil for this ROM I was able to flash my phone but not before removing more apps (bell apps and oothers ).
I was wondering if anyone was successful in unlocking the tethering? Tried a few things out there and the best I could get was Bluetooth tethering with foxfi.

And it works!
@doctor_evil: I flashed your set after having played with @atmu5fear's version (http://forum.xda-developers.com/showthread.php?t=2673097). I like them both very much and am still looking which one I will keep. I have not wiped data/cache (i.e. Factory Reset) before overlaying your version over @atmu5fear's one, and it did not hurt. I noticed the following:
Flashing your ROM did not again trip the ROM counter after applying the triangleaway script after @atmu5fear's ROM load (it did go off then).
When having a SIM in the S730M and after putting in the phone unlock password, the keyboard stays on top (this does not happen when no SIM is present)
My Battery-drain problem when having the phone powered fully off with a SIM installed is still there. Probably need to await a cooked custom ROM for this to be solved
The triangleaway script for the S730M can be found at http://forum.xda-developers.com/showthread.php?t=2420184
The Battery-Drain S730M issue has been noticed by quite a few people (TELUS and BELL, both in Canada), and is unexplainable. When the phone is on (with SIM installed), power usage is normal, but when you power off the phone (with SIM still installed) the power-drain goes up dramatically (draining the battery completely within a few hours). When the SIM is removed, or when the battery is removed there is no abnormal drain perceived. The other thing is, that, when the device, with SIM and battery installed, is powered off, both the battery area and the SIM area get warm (not really hot), indicating SIM activity WHILE THE DEVICE IS OFF... Very odd. I am hoping that a new KK custom ROM would fix this issue as both 'custom' 4.0.4 ROMS I have tried now show the same issue, indicating it is either a hardware or a 4.0.4 implementation issue...

I am sorry I never responded back to you. I had my Cygwin install with my kitchen build environment running on a SSD hard drive with my OS and the drive crapped out on me and had to be sent in for a RMA. I had a easus todo workstation backup of my drive I was able to restore, but the backup wasn't current so I lost my kitchen environment. I never tried to set it up again as I had hoped that someone would have ported Cyanogenmod to the phone.
I may give it a try again as I just setup a vmware ESX host server here at home and I can allocate multiple cores and plenty of ram to the linux Virtual Machine I created on it once I figure out the best build environment and how to actually go about building CM successfully. Anyone know of a porting cyanogenmod for dummies guide I can use? LOL