Database Info

Root, Rom mod, what next?

As a new Android user who is very familiar with the command line and with Linux/Unix environments, I still feel extremely overwhelmed with the amount of 'fixes' and 'root' hacks going around.
I've played with linux for 100's of hours and have broken the install and fixed it...
But this is a phone that bricks, not a computer. I don't like playing "oh I'll just try this and see what happens" with my $400 phone.
Plus I honestly can't determine which one is best for me.
I started this thread so that someone could assist me in creating a guide for what you want to do and what is best to do it.
For example, I want to upgrade to Froyo when it releases.
In the mean time I want to install a lag-fix/ custom rom.

mymansionisabox said:
As a new Android user who is very familiar with the command line and with Linux/Unix environments, I still feel extremely overwhelmed with the amount of 'fixes' and 'root' hacks going around.
I've played with linux for 100's of hours and have broken the install and fixed it...
But this is a phone that bricks, not a computer. I don't like playing "oh I'll just try this and see what happens" with my $400 phone.
Plus I honestly can't determine which one is best for me.
I started this thread so that someone could assist me in creating a guide for what you want to do and what is best to do it.
For example, I want to upgrade to Froyo when it releases.
In the mean time I want to install a lag-fix/ custom rom.
Click to expand...
Click to collapse
Do people not know how to read stickies? there are guides and how-to's in this section alone. There are more in the development section. If you don't know how to search a forum, I'm not entirely sure you should be messing with your phone's firmware.

Kaik541 said:
Do people not know how to read stickies? there are guides and how-to's in this section alone. There are more in the development section. If you don't know how to search a forum, I'm not entirely sure you should be messing with your phone's firmware.
Click to expand...
Click to collapse
I actually have read all of the stickies.
Im not asking 'how-to' do anything.
What I am saying is that this forum has an absolute overload of 'information' and 'solutions'
There should be a more concise sticky discussing the advantages/disadvantages of each rom/lag fix/flash/recovery/etc. (Or at least about the ones anyone cares about)
If this exists, I sure as hell don't see it.

mymansionisabox said:
I actually have read all of the stickies.
Im not asking 'how-to' do anything.
What I am saying is that this forum has an absolute overload of 'information' and 'solutions'
There should be a more concise sticky discussing the advantages/disadvantages of each rom/lag fix/flash/recovery/etc. (Or at least about the ones anyone cares about)
If this exists, I sure as hell don't see it.
Click to expand...
Click to collapse
I think you're in a wrong forum if you want someone to give you any kind of "distilled", spoon-fed info just because you're afraid to mess with your "$400" phone.
Again, to second the other reply, all the info is posted. Just RTFW/S.

mymansionisabox said:
I actually have read all of the stickies.
Im not asking 'how-to' do anything.
What I am saying is that this forum has an absolute overload of 'information' and 'solutions'
There should be a more concise sticky discussing the advantages/disadvantages of each rom/lag fix/flash/recovery/etc. (Or at least about the ones anyone cares about)
If this exists, I sure as hell don't see it.
Click to expand...
Click to collapse
there are tons of guides and they're all condensed. I have to agree with the other poster, if you aren't going to take the time to read and learn what you're doing, don't do it. each sticky offering to help you through all of these processes are there for a reason.
There's the "Pimp My Captivate" thread which is exactly what you say you want. And there have been comparisons of each lagfix by Zilch25, clockwork recovery by Koush is clearly explained in his thread, each ROM is discussed in their own thread.
Ironically, you're asking for a sticky so as to have less stickies. Finding out which ROM you want to use is up to you and if you're not going to take the time to figure out what each tool offers or what each base ROM means, then maybe flashing your phone is something you should steer clear of for now.

If you're afraid of bricking it, just do a Nandroid backup. If something goes wrong, then you can just flash back and it'll be A-OK. If you seriously brick your phone and it's 100% messed up, it's probably because you tried to mess it up.

Hydrocharged said:
If you're afraid of bricking it, just do a Nandroid backup. If something goes wrong, then you can just flash back and it'll be A-OK. If you seriously brick your phone and it's 100% messed up, it's probably because you tried to mess it up.
Click to expand...
Click to collapse
Even guys that intentionally tried to brick their phone can't do it. I don't have much to say as it already has. Just take the time to read. There is a condensed version of what you can do to your phone, the pimp my captivate. Otherwise there are many different ways of rooting, lax fixes, firmwares to flash etc...so there is not one thing that you can do that will make your decision easier.

flashman2002 said:
Even guys that intentionally tried to brick their phone can't do it. I don't have much to say as it already has. Just take the time to read. There is a condensed version of what you can do to your phone, the pimp my captivate. Otherwise there are many different ways of rooting, lax fixes, firmwares to flash etc...so there is not one thing that you can do that will make your decision easier.
Click to expand...
Click to collapse
don't say that. there have been several confirmed bricks from i9000's using the i897 one-click downloader. While there is no immediate, known, for-certain brick method for your phones... you never know who or what may be the first... always read as much as you can in the threads before you attempt to do anything

As someone who was new to the Captivate scene, but not XDA, just two weeks ago the best advice I can give you is start with the "Pimp my Captivate" PDF file. Read through that and then move forward to other stuff like flashing new firmware and using odin. Trust me you will catch on. I am no move on to working on friends phones for them without any worry of breaking (bricking) them.
Just read, read, read, and sometime read some more. If you have a question about a certain hack, fix, firmware...ect then just ask that question in that thread. Trust me there will be very useful helpful people to answer your questions.

I did what is probably the easiest method. I used unleash the beast and then one click lag fix. That's it and my phone is amazing now. I plan on sitting tight until froyo comes out and whatever the top rom happens to be.

I do appreciate everyone's answers.
Despite that, I really don't understand this particular forum's aversion of being more organized and concise. (imo)
I don't think any of you who told me to read actually understood my intentions of making this post since,although I didn't state it, I have already flashed mods to my Captivate and I have modded my previous phones.
I'm new to XDA so maybe this site is far more trustworthy than where I've been.
I'll check it out and read at least the last 10 pages of each thing that I install.
Thanks though.
Mod please close this thread.

mymansionisabox said:
I do appreciate everyone's answers.
Despite that, I really don't understand this particular forum's aversion of being more organized and concise. (imo)
I don't think any of you who told me to read actually understood my intentions of making this post since,although I didn't state it, I have already flashed mods to my Captivate and I have modded my previous phones.
I'm new to XDA so maybe this site is far more trustworthy than where I've been.
I'll check it out and read at least the last 10 pages of each thing that I install.
Thanks though.
Mod please close this thread.
Click to expand...
Click to collapse
we have nothing against being "organized," I just believe your definition of organization is far too complex. You want all the ROMs compared side by side, followed by the tools, and the rooting methods, and the lagfixes and to know which is "best."
Each thing is kept separate from the other because there would be an absolute and definite overload of information in each thread. Look at SRE (a fine example of how to do it properly), he details the result for the end-user and then provides links to where each part of what he did came from. The development section provides a thread on reverting to stock and just that because it should focus on that, rooting can be left for a thread on rooting. SRE shouldn't be tossed into a thread with UTB because they provide different effects.
If you were to compile everything into one big mega-thread, questions would never be answered because there would be far too much crossover. The Pimp My Captivate thread is as good as it gets in that regard, they provide optimizations and suggestions and where to find more information, which is good enough.

I understand.
After this post I am done though, because I'm getting no where with this.
Check out the web page below, this is really what I meant. I can't post links so just close the gap between http:// and ga..
http:// gadgets.boingboing.net/2008/12/17/osx-netbook-compatib.html
I belong to several forums that had been attempting to put mac osx on netbooks and on one of them a chart of compatibility was compiled, which is similar to what I was suggesting we needed.
Ignore the comments below the chart; that would be unnecessary.
All I was proposing to do was have a locked/stickied thread that only a moderator could change up as new changes/improvements occurred.
Each root/lagfix/rom would have a href connected to their actual thread.
So there would be no need to have comments/ questions asked on that particular page. ****.. it could just be a damn wiki page, but I digress..
If no one thinks that would be beneficial to the community, that is fine.
I don't care, I can easily figure it out myself.
Mod, please close thread.

Thoughts on ROM/dev threads.....

It seems to me that there is a lot of frustration amongst devs, those in the know, and the unschooled to the ways regarding pretty basic information. Stuff like "is MR2 froyo or gingerbread?". I know I'd be asking and saying some industrial strength stupid and annoying things if I didn't have a good friend in the know. I suppose what I'm suggesting here is perhaps several things. The first would be describing a number of specifications regarding the ROM or kernel at hand. Not just for the latest ROM or kernel, but for all the downloads available on the OP. Usually the change log covers that, but what I'm suggesting here is a certain I uniformity of certain information. That way some noob can go do his homework real fast and not post some stupid question.
The second thought I have is creating the "stupid question thread" (that would grow like a weed, huh?). It would have basic stuff like what the RUU's are, their characteristics, what radios they work with, what the different radios are, setting up ADB, and really basic stuff that I keep seeing posted again and again all over. I was reading through the Tbolt forums months before I got my Tbolt and my last phone was an Incredible so the worlds didn't change a hell of a lot for your average flashing junky. But that isn't everybody's experience. I'm suggesting a thread or the guy that just got his Tbolt and is saying "Now I wanna root it!" then "It's rooted! Now what's out there!" And zap! there's te thread that gives him a rundown of all the basics.
This sound like a good idea to anyone? If so, let me know and I'll work something up.

I am a noob, TB being my first Android phone. When I started reading the forums, my very first thought was: how come I can't find a noob thread that I can actually understand, that explains the basics, etc. It did not exist! Hence al the annoying (to some) posts elsewhere. If such a thread existed it would have been a huge help for me. It could be organized similar to ROM threads, with some introductory remarks, (a radio is XYZ, you flash it this way, etc.) followed by specific questions / comments. I like the idea!
Sent from my ADR6400L using XDA App

This is a good idea.. if no one makes one soon ill take it up
Sent from my ThunderBolt using XDA Premium App

There is no substitute for taking the time to read the various threads and educating yourself. I think the devs do a pretty good job of supporting their work but to ask them to put together super noob threads and FAQs is just not something they're gonna do with any regularity.

The reason why no one has done it is because all of the noobs are to lazy or ignorant to read those threads, then continue to post their stupid and already-answered question anyway, flooding the threads as usual.
Sent from my ADR6400L using XDA App

I think it sounds like a good idea but as stated above people probably won't read it or take it's advice. Typically all the ROM/Kernel threads state EVERYTHING needed to know in the OP. Yet people will still ALWAYS ask something that is answered in the OP. Most people look at screenshots and then jump straight to the download link. This is my 3rd Android phone and when I got the TBolt I read and read prior to rooting. I had one issue that I hadn't seen posted so I asked. Then I ended up figuring it out on my own anyways. If people would just read info prior to downloading and jumping into it they would be fine. Creating a new thread with basics is great but how effective will it truely be?

Mustang302LX said:
I think it sounds like a good idea but as stated above people probably won't read it or take it's advice. Typically all the ROM/Kernel threads state EVERYTHING needed to know in the OP. Yet people will still ALWAYS ask something that is answered in the OP. Most people look at screenshots and then jump straight to the download link. This is my 3rd Android phone and when I got the TBolt I read and read prior to rooting. I had one issue that I hadn't seen posted so I asked. Then I ended up figuring it out on my own anyways. If people would just read info prior to downloading and jumping into it they would be fine. Creating a new thread with basics is great but how effective will it truely be?
Click to expand...
Click to collapse
I agree with you 99%. However, there are several cases especially with BAMF threads where there are hundreds of pages and thousands of posts. The OP many times doesn't have solutions to common problems and the only way to find an answer is to spend hours reading through hundreds of pages. (I admit that BAMF is doing much better with their 3.0 RC2 thread). I know you are going to say to search but when a thread is that large it is hard to find meaningful search results.

Google is a noobs best friend. What is an RUU? Google it! What is deodexed? Google it! Etc. Etc. Etc...... The Devs develop. It's our job to educate ourselves. They do this for free. Between the forums and Google, most if not all questions can be answered. The ones that can't be answered is when the forums should be used. Just my opinion.

mpfstc said:
Google is a noobs best friend. What is an RUU? Google it! What is deodexed? Google it! Etc. Etc. Etc...... The Devs develop. It's our job to educate ourselves. They do this for free. Between the forums and Google, most if not all questions can be answered. The ones that can't be answered is when the forums should be used. Just my opinion.
Click to expand...
Click to collapse
Agree. But, the question "can the X patch from the previous version be used on this version?" People get flamed for asking questions like that and many times there is nothing on the OP.

droidisawesome said:
Agree. But, the question "can the X patch from the previous version be used on this version?" People get flamed for asking questions like that and many times there is nothing on the OP.
Click to expand...
Click to collapse
Because most often.. the dev himself does not know the answer.. and honestly.. the best way to know if something works or not is try it yourself. .. so I can understand when devs get frustrated with people asking certain permutation and combination of patches will work with their roms or not.
Once you understand (which comes with experience and lot of googling).. what affects certain aspects of a rom.. then you'll know yourself if a particular patch will work or not.
Patches from previous roms or other roms.. will never brick your phone.. the worst.. your phone won't boot up.. or it'll boot up and FC like crazy.. in which case you can always restore.
and I agree.. the best way for a noob to educate is google..
googling is an art.. once you get good at it.. there is almost nothing that you can't get information about.

And with some of the responses I just read in this thread is exactly why I haven't rooted my T-bolt yet. I rooted my D1 and really enjoyed flashing different ROMs and Themes but the HTC experience is a bit different from the one on the Motorola. I don't feel like getting flamed for asking something that those of you that have been using HTC long enough now find to be a useless question. I ran Blackdroids ROMs because he had an IRC channel where you could ask questions without being flamed openly in a forum for 100+ to see. I learned quite a bit to where I could eventually help others with it but I'm not at all comfortable yet with Hboot and ADB but hope to learn enough from reading to not bother you with questions you find trivial. I've read for a week now so what's another week

It appears there is a need for what I propose. Regarding those who's complaint is that nobody will read it, I say, at least someone put forth the effort and if someone like, linking to the thread is easy. Indeed looking stuff up for yourself is wise, however, it takes more time for people and all too often you don't know how accurate what your reading is or from what authority the writer speaks. I will agree most devs supply ample info on their work, but often its in jargon that makes no sense or lacks context. Part of the purpose for this thread would be to supply sense and context.
Hopefully over the next few days I can find time to whip something up. I welcome all suggestions and comments for content!

[Q] Termonology Aspects and Capabilities

Hello there i am new to these forums, and android to that matter as well, not to mention linux. True Noob- so be it. I hope i have posted this in a relevant section. I was just wondering with all of the vast amounts of information posted on these sites if there is any information that is important to know before getting really in depth. Maybe like a terminology index of sorts that will help u understand the complexity of code and programing i have no education in such matters. yet i have flashed cwm recovery even though i techinically dont understand what flashing truly is. but with that I just wanted to say that the people who take time to write tutorials are very helpful. I am running g2x gingerbread 2.3.3 got from tmobile brand new yesterday. I am intristed in seeing if there is a rom to bypass data cap on there 4g network-fix camera and camcorder issues with potential delivered to what hardware is actually designed to do. also can internal storage be deverted for extra ram?? and overclocking i am intristed in basically just want to thank everyone who is patient and helpful.
I am an intelligent logical person i belive if i could have a 10 min conversation with someone with the know how i could learn alot. or yet maybe people can use this thread to talk about elementaries and the abc's of things also i would be much apprecitve for emails and messages with any advice thank u so much

I would just browse XDA and if you find a term you don't know you could PM me or just post it in the Q&A section.

[Q] how can i help and get involved?

i want to get involved in the community and help bring great things to this device and any other that i can. i have a degree in computer information systems, do systems imaging, and know enough to get by, tweak, and customize, but linux was never taught to me . it is pretty straight forward. i understand the concept, language, and most of the commands, but i am not a programmer by trade. i do know that you don't even have to actually know a lot of languages because, in many cases, there is another program that you can tell what you want to happen and it will write the base language for you. if somebody can point me in the right direction and/or give me a task to help them with, i would love to do so.
thank you
don't mean to sound ignorant. just wanna help.

That's a fantastic attitude, and welcome to the doubleshot forums.
The MT4G Slide Compendium is a sticky at the top of general here, and is a great starting point to familiarize yourself with the doubleshot forums. It has links to a lot of the relevant threads scattered around here, as well as some explanations of terminology and so forth. It's designed to help orient you with everything we have going on here.
Here is a link to my Guide Index, which is a collection of tutorials and such i've put here and is also in my sig. The bottom of the post has links to a lot of information about the device off-site, manufacturer and so forth.
One of the best things you can do if you aren't contributing code is to contribute documentation. How to do basically anything you want to do is spread out all over XDA as a whole. If information can be referenced and concentrated here into the MT4GS sub-forums, it would make it easier for people to develop for the device.
Not having to scour XDA at large to figure out how to do something, and someone taking the time to explain how to do it here and provide links to track down more information is always helpful.
I know in searching XDA to learn how to do these things, it's been helpful for others to have been making summaries and guides on how to do them - sharing it here paves the way for others who come behind you and want to learn how to do what you're learning.
And if you aren't interested in posting guides on how to do the things you've learned, then just taking the time to answer questions people ask on the board about the device if you know the answer is a way to be helpful. The longer you hang out here, the more you learn, and the people coming behind you are curious too.
The longer you hang out here, too, you come to learn where information is and in what threads - you can direct newer people by answering questions with links to the relevant threads or posts since you already know what they are. It only takes a few minutes to track down the information if you have a good idea of where it is.
Because XDA is pretty much where we figure out a lot of the new stuff, the board grows randomly, and information gets scattered with pieces here and there in threads to solve problems and such. When people ask questions you can link to the scattered pieces and by doing so it helps index everything we are learning.
Basically, the desire to help is all that you need and these are some ways people can do so without in-depth technical knowledge. You're probably combing the boards learning things anyway, so when people have similar questions explaining what you know helps us all.
We all have different ways of learning, so sharing how you did can teach others new methods and ways of doing beyond just how to do the specific thing itself.
It sounds like you are as excited about all this as some of us are here, and with a device like the doubleshot in your hands I don't blame you.
Any questions just ask, as long as you aren't posting random questions in the dev sections it's all good.
Once again, welcome to the MT4GS forums, you'll have a blast with us here.
Edit:
Kernel stuff is in C flavor language, Android stuff itself is mostly Java, and if you don't have the program Notepad-plus-plus you should pick that up for making mostly all of your general coding edits on the computer with.

Thank you. I am excited. My first device that I toyed with was an htc leo 1024 (us), so I had an edasy entry into the world just because there are so many resources available for it. I will start by posting a couple of guides about things that I know were difficult to grasp/follow when I first started. Thank you very much for the directions and taking the time to post them and reply to me. Time to study...
Sent from my myTouch_4G_Slide using XDA App

That's fantastic.
This is my second Android device, first phone - the other one is a Nook Color.
Much like how you say having a lot of dev interest in the device you came from helped you (and man, does it ever) the advantage the Nook Color had was it's unbrickable. It boots from the MicroSD first, before internal memory, and you can run a self-contained copy of Android from the MicroSD card.
I got a chance to break it in so many different ways, (who needs a build.prop ... let's just delete that) and all I had to do was pop out the memory card and flash a fresh copy of CM7 onto it.
The internal memory is still the stock Barnes & Noble skinned operating system, hasn't been rooted or anything, yet I was still able to get the full-on Android experience in a safe play zone.
Coming to this phone, it's taught me ahead of time what I can and can't mess with before bad things start to happen, and it's a lot easier to play with this stuff if you know where the lines are. The ones you get in trouble if you cross.
It really wasn't until I got my hands on this device that I started to get into a lot of dev work on Android - but now i'm having an absolute blast with it and this device is pretty impressive.
I can't wait to read about what tricks you've picked up along the way, i'm always looking for an opportunity to be educated. Take some time and see what we've got laid out here, in some cases you may be able to add to existing threads instead of making new ones for duplicate topics.
The MT4GS is what, 6 months old now? We'll keep getting more people in here as they come to their upgrades or get warrantied up to this device. I'm eagerly awaiting more devs to end up in our corner of the forums, i'm curious to see what kind of cool things people can make the device do.
The more information we have organized and mapped out about the device and how to do things with it, the easier it gets for people who come behind because they don't have to re-invent the wheel just to get something done.
It's mind boggling to me how much i've learned in the past year here at XDA, especially in the last few months. It's all because people take the time to sit down and explain how they've done the things they've done and are excited to share their discoveries.
Having this device since before root was viable, i've watched this section of XDA grow from literally just a handful of threads into what it is now - pretty soon we'll have a majority of the resources right here for people to just show up and get work done with minimal fuss.
I know my dev time is hit or miss, sometimes I have days on end, other times not - one way i've been trying to help when i'm not around is leaving how-to's and guides behind me that people can reference while i'm gone.
There's still a whole lot that I haven't even gotten into yet, and i'm very appreciative of people taking the time to share some cool discovery or trick that's made their life a lot easier.
(sometimes I ramble a bit, especially when on boring conference calls)
I came to XDA to learn how to do some fun stuff with my Nook Color, and maybe learn how to write apps for the market. Here I am writing ROMs and nowhere close to putting any apps in the market. With the library of knowledge that XDA is everytime I sit down at the keyboard I learn something new, I wish i'd found this place a long long time before I did - it feels like home.

that's pretty cool about the nook color. i may have to pick one up to play with. i'm sure there are all kinds of neat things to be figured out (and easily implemented) with a device that boots from an external source before the internal.
i got pretty lucky with my hd2. as soon as i saw that there was a way to do it, i had to figure it out (of course). however, instead of reading all of the instructions and bulletins on correct procedure, like an intelligent person... you can probably guess where i'm going with that... and VIOLA! an expensive paperweight.
i was very lucky that phone is setup the way it is and for resources like you and some of the other devs and especially the others that learned by trial and error and took the time to post their experiences.

[Q] Flashing/ROM Question

Hi all,
Long time reader of the forums here since I had one of those old and clunky Windows PDA's. I used to mod the PDA's and older Win mobile 5 and 6 phones. I'm on my 2nd Android, the Skyrocket and have had it for abover 2 years now. So far it's the best phone I ever had. I had to start a new account cuz I couldnt remember my username. Yeah I'm getting old...
Anyway, I have had a battery issue since doing the very first OTA update. I have checked everything using multiple guides including the ones here. Either I have a bad battery or a signal issue. When sleeping for 8 hours I lose about 10%. I had the SD card issue and the Play/location services issues but fixed those, I also fixed all wakelocks and it goes into deep sleep. When in the house my signal bar under battery in settings is all grey unless I go outside then it's green. I really dont do all this modding anymore so I never flashed a rom on it. I did just flash my Transformer TF300T (usinf CROMI-X 5.4) tho so I am familiar with the process. So I figured I woulkd flash a new ROM and/or a radio onto the i727. I have been reading all day about flashing the rom and reading about the various roms availabe. most, if not all seem to be AOSP based and in beta. Also they state in the post they require CWM abd not TWRP. I'm looking NOT to do daily or weekly uodates.
I'm looking for:
- stock based ROM that's stable
- no bloat from AT&T or Samsung
- preferably without Touchwiz
- extra modifications are okay (I love extra goodies as long as their useful)
- able to use TWRP 2.7.0.0 as that's what I'm using now (I read TWRP is easier to use and that's what I want)
Android verion 4.1.2 or later
Basically I want to do a Nandroid, do a Ti Backup and backup all my files then flash the rom and restore my crap and that's all. No upodates, nightlies or anything else. Finding a stable stock based ROM was easy on my Asus but can't seem to find much of anything for my phone. I've been looking and reading all day and I have eye issues so now have a migraine. I would appreciate some info from all you flashers out there. If anyone could recommend several rOM's for me, with links, I would greatly appreciate it.
Thanks,
Shannon

lol, if you did actually search and read you would know not ask such a question, read about the roms and decide on ur own, for the skyrocket its fairly easy, read then try them out and see if its what u want
start reading the 1stop sticky, link in my sig, everything u need is there

vincom said:
lol, if you did actually search and read you would know not ask such a question, read about the roms and decide on ur own, for the skyrocket its fairly easy, read then try them out and see if its what u want
start reading the 1stop sticky, link in my sig, everything u need is there
Click to expand...
Click to collapse
Sounds like your presuming I read nothing. when I did the Transformer it was easy. I found a site with a list of stock roms and a list of AOSP roms. That made it easy to read the ones i wanted to look at. On this site, or any other, I dont see any such organization of the roms. All I would like to know is which are stock ROM based. leaving a reply with a small list would have been appreciated. Then I culd read up on them. I had a bad bought with diabetes and my vision kind of sucks sometimes and I get headaches easily. Reading everything there is to read about all the roms will take me much lonhger than someone else. I know you get the similar questions all the time and you cant answer them over aand over again. I wasn't asking for a 10 page tutorial, just a few names of stock roms for me to read up on.
Thanks anyway,
Shannon

I went back and reread the 1stop sticky and say there are 6 stock roms for my phone listed there in a sea of other roms, That small list of roms I didn't notice the first time around. Are there any others besides those?

i was referring to this, did u read this in the sticky and also in the forum rules:
"Do Not Ask For A Which Is The "BEST" Rom Or Any Adjective Thereof For A Rom As The Mod Will Close It, Read About Them In The Dev Forum And Decide On Your Own."
why, because it usually/always starts a pissing war

From the moderator
The Best Rom is the one you like. Preference for Roms & features is subjective and there is no good answer
Before this becomes a Troll session, I will close
Thanks ~~~ oka1
..............THREAD CLOSED..............