So I'm on CM 11 and I would like to go back to insertcoin, however I can't very work to work once booted. I also don't get a boot animation at all... What do I need to do?
Just look around in Development and other Q&A threads (or right in the InsertCoin thread) for discussion on how to update the firmware. This has been discussed in probably dozens of other threads already.
This isn't related to being on AOSP. Its simple a matter of outdated firmware not compatible with InsertCoin (and other current Sense ROMs).
Related
Hey guys I have been doing quite a bit of searching through the forums and still have a couple questions about custom roms and rooting. Forgive the noobness but the droid incredible is my first android device and I only recently got it.
1. My first question is what is the simplest way (rom + root I assume) to get a stock version of android on my incredible? Also what rom would you recommend (I have seen a pretty big list but know nothing about them)?
2. What is the difference, if any, between a kernel and a rom? Ive seen both words used a lot and have seen kernels that are stock and roms that are as well. Which would I use between the two?
I know these questions may be dumb but I have been searching for a couple days and have gone through hundreds of threads trying to find the definitive answer (there were some benefits though, I use launcher pro and the droid x's keyboard now) any help would be appreciated.
1. You are right in assuming that the quickest (and only) way to get a stock version of Android on your phone is to root your phone and install a custom recovery that will allow you to flash a rom. It is not really possible for me to recommend a rom because rom's are all about personal preference and my preference may be different from yours. That being said, if you are interested in stock Android, check out Cyanogenmod. The biggest thing right now is that for the Incredible, Cyanogenmod is the only true stock Android that is compiled from AOSP (Android Open Source Project) however it is still in its early stages for our device, so it's still buggy. The other roms are modified versions of our stock sense rom, so some of the roms are modified to have the bulkier parts of of the Sense UI removed, but it is still a Sense rom.
2. I'm not going to profess to be extremely in the know about kernels, but a kernel is the go-between for the hardware and the os/applications. If you want to learn more about kernels, you can read the wikipedia page about kernels found here. Basically what you need to know is that the rom is the operating system, so if you wanted to change the OS such as from Sense to Vanilla Android, you would flash a rom. If you wanted to change the way the system runs, such as if you want your processor to be overclocked or undervolted, you would flash a kernel.
Hope this helps.
That answered everything! Thanks for the reply and I will keep checking the forums for stock roms that seem stable!
I just upgraded my Sensation to ONE X.. and YES there is a difference
i unlocked the phone but i have not rooted yet.. and i got a little confused why there are 2 development sections.
What is the difference between oneX and the original oneX
I noticed that after flashing new ROMs you have to flash the boot.img?! is that every time? i`m a little confused since everything was more straight forward with the sensation
Thanks
Since we don't have s-off for our hox, you have to flash boot.img manually every time you change ROMs or if instructed to do so by the rom dev.
As for why there are two different sections, there is an explanatory anouncement post by forum mods describing the two sections.
EDIT: I cant seem to find the anouncement. What it boiled down to is, for a rom/kernel/mod to be included in the original android dev section, it must be original work or add something innovative to an already existing rom. Simple additions or tweak of an already existing one does not qualify a rom to be included in the original section.
eyosen said:
Since we don't have s-off for our hox, you have to flash boot.img manually every time you change ROMs or if instructed to do so by the rom dev.
As for why there are two different sections, there is an explanatory anouncement post by forum mods describing the two sections.
EDIT: I cant seem to find the anouncement. What it boiled down to is, for a rom/kernel/mod to be included in the original android dev section, it must be original work or add something innovative to an already existing rom. Simple additions or tweak of an already existing one does not qualify a rom to be included in the original section.
Click to expand...
Click to collapse
Yeah,
Basically "Original" is built from the ground up by the member who posted it
The "Android Development" is a developed version of an existing ROM?
nice, now i understand. So basically if i choose a AOSP or AOKP (which right now from what i read have lot's of issues) i go with the original thread.
It's a shame we do not have S-Off. i don't want to be stuck on Sense but from the looks of it, i might not have a choice (buggy AOSP)
qiuness said:
nice, now i understand. So basically if i choose a AOSP or AOKP (which right now from what i read have lot's of issues) i go with the original thread.
It's a shame we do not have S-Off. i don't want to be stuck on Sense but from the looks of it, i might not have a choice (buggy AOSP)
Click to expand...
Click to collapse
All the AOSP/AOKP/CM10 ROMs are usable as daily drivers, none of them are buggy...
Hey all, I hope this is an okay place to post this and I tried searching around but wasn't able to get good information.
Essentially I'm really annoyed with the extra Samsung software and really want to try a custom rom but I also need to use my phone for work so it needs to be pretty reliable. As far as I can tell CM is still in a beta / alpha state for Note 2 (unless I am mistaken).
Are there any specific roms that have been tested well / known for being the most reliable? I love playing around with roms but I am having a rough time trying to figure out which roms are most stable, which are experimental, etc.
There are several roms that are very stable. Depending on your personal taste, you will want to first decide if you want a TouchWiz based rom or a AOSP based rom. Then find the rom that interests you and read the forum for the roms and see if there are stability issues for those roms. You should probably stick with a more stock rom that has been debloated. I personally use Synergy rom and you have the option to install the rom without the bloat apps or with them. Its within the Aroma installer during the flash process that allows you to customize your Os install. I would download and flash an earlier version between r51 and r85. The newest version has significant issues as it is still being debugged. Other than Synergy there a few other TouchWiz based roms that are debloated and offer different tweaks etc. CM based roms are very stable actually.I hope this helps.
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
So as I understand it, if I have this radio the only roms I can run are rhythmic and ics roms.
I really a want to flash Pac but end up with boot loops no matter what kernel I flash.
is there currently anyway to get this rom running on this phone. If not is there any development still in the works that might allow us to use JB roms in the future?
Sorry if this had been answered but I read though like ten pages of the forums and did didn't see this answered completely.
I've tried multiple builds of DU and CM on my HTC One m8 and I'm getting random reboots nearly everyday. I figured I should try a different kernel. Never used a custom kernel before so I tried finding some on Google but all I could find where articles talking about why I should use a custom kernel, but not where I can get one. Is there a list or database of popular kernels out there?
You'll find a number of kernels if you look in the Development and Original Development forum sections. But unfortunately, nearly all are for Sense and GPE ROMs, and won't work on AOSP ROMs like DU and CM. On that note, since AOSP ROMS use different kernel(s) from Sense and GPE; you already in fact have tried 2 different custom kernels.
If you still want to try different kernels, what you can do, is take the boot.img from another similar base (same Android version) AOSP ROM, and flash it using fastboot. Such as the DU kernel with CM (or Slim kernel, etc.). But honestly, I have no idea how much the devs tinker with the kernels on these AOSP ROMs.
Be sure to make a TWRP backup of your current ROM before flashing a different kernel; in case it doesn't work and things go south, you can easily revert.