Related
Just wondering if anyone has made or would make a sort of tutorial about howto upgrade rom, make new rom, customize rom etc. preferable with pictures'n'stuff
Excellent idea jpless.
Does anyone with some experience can do that?
I have a new HTC P3600 Black, at 2 days
I'd like that too, the problem is that there's too much info about this on the forum, some of that info is outdated, valid only for a specific device, and sometimes valid for a couple of devices but posted on a specific device forum( hermes ).
Since we would really like to do this but fear bricking our devices, I think it would help if a known, trustworthy and experienced member had the time and will to start the creation of a centralized source of info about this topic, like one big wiki page divided by main steps and device-specific tools/methods which would later be improved by other users( wiki ).
Who knows, maybe there's someone who just needs a nudge to create something useful to the community.
I really hope someone will do, cause I wanna learn it the easy way
Btw what is this ROM Kitchen thing I keep reading about?
Hi ,
First I'd like to say hello to everybody here. I'm new at this forum (and not a very intelligent one)
I just bought a TyTNII and been reading these forums trying to gather as much info as possible but unfortunately most of it is beyond my intellectual power.
I found people that hate the phone, people that loves it and people that modified/upgraded it to make it more powerful, faster, etc.
I wonder if there is any link (movil phones for Dummies???) where I can learn some stuff since there are a lot of terms that I don't understand.
May be I can ask here some of my questions and some willing soul might spare some time to help...
I intend to use this phone mostly with Skype (through WiFi) but I'd like to get the most out of it.
So, are there any upgrades (Rom or anything else) that I need to do or should I use it as is?
I been reading about all these different roms people post here but to be honest I'm not 100% sure what are they (I guess they are upgrades for windows) but I don't understand why people design these and not the official Microsoft.
Anyway, too many questions at once. If I get any replis to this one I might be encourage to ask again
Thanks,
Fernando
Read this ROM Flashing FAQ To learn more about roms..
Go through the Kaiser Wiki theres a lot of information there.
Thanks, I'll give it a read
Hi all,
I'm quite new to this android stuff, and especially modding. And I have to tell that I feel a bit lost.
After a few days browsing this forum and other places on the internet, I think I know what a ROM and rooting are. But here I see things like kernels, radio, bootloaders... could someone explain me what those are and how they are related together? Or show me an url that explains all this.
Thanks a lot!
Bricolo_fr said:
Hi all,
I'm quite new to this android stuff, and especially modding. And I have to tell that I feel a bit lost.
After a few days browsing this forum and other places on the internet, I think I know what a ROM and rooting are. But here I see things like kernels, radio, bootloaders... could someone explain me what those are and how they are related together? Or show me an url that explains all this.
Thanks a lot!
Click to expand...
Click to collapse
Im not real sure how to explain all this stuff in great detail but i will try and tell you all that i know. I think a kernel has to do with the drivers and things like that. A radio has to do with the everything that uses connections, i guess you would call it. Like your phone's network, wifi, bluetooth, etc. And for the bootloader i don't really know how to explain it but press and hold the power button and the trackball at the same time. thats the bootloader.
This should help some... http://forum.xda-developers.com/showthread.php?t=619153
Bricolo_fr said:
Hi all,
I'm quite new to this android stuff, and especially modding. And I have to tell that I feel a bit lost.
After a few days browsing this forum and other places on the internet, I think I know what a ROM and rooting are. But here I see things like kernels, radio, bootloaders... could someone explain me what those are and how they are related together? Or show me an url that explains all this.
Thanks a lot!
Click to expand...
Click to collapse
Hi Bricolo!
Welcome to the forums!
I'll help you out here, but you're going to have to do some work too.
How about I do two, and you do two?
[Google]: android "what is a rom"
http://forum.androidcentral.com/hacking/6037-general-rom-faq.html
If you’re new to the Android platform (don’t be bashful, all of us were not too long ago), you’ll see terms floating around the forums that you might not be familiar with. “ROM” is one of those terms. A ROM image is a data file that contains information used on a Read Only Memory chip. For our purposes, that means a complete system image of an Android device. Each Android device has it’s own ROM image that contains files and code needed to boot the device up and run Android on it. But this is only part of a ROM. A ROM also contains a GUI (graphical user interface), required and useful applications, support files for those applications and the kernel. Let’s have a look at the parts that make a ROM.
Click to expand...
Click to collapse
http://www.droidforums.net/forum/droid-general-discussions/37418-what-rom.html
"ROM" is just a generic term for the software that makes up the OS, and a bit of a misnomer. This term could easily be changed to "OS sofware" or "system software". It does mean Read Only Memory, but ROM likely comes from that part of the system memory, since you dont want to be able to write over the system files (easily).
Click to expand...
Click to collapse
[Google]: android "what is a kernel"
http://androidforums.com/developer-101/62548-what-kernel.html
A kernel is basically the bridge between applications and the data processing at the hardware level. It serves as a level of abstraction for communication.
Click to expand...
Click to collapse
http://www.applematters.com/article/how-long-will-apple-keep-the-mach-microkernel/
The easy answer is a kernel is the core of any operating system. DOS, Windows, UNIX, OS X and Linux all have some type of kernel. The implementations change but the basic concept remains the same. A kernel interfaces directly with the system’s hardware and is the lowest level of software. There are two types of kernels, micro-kernels and monolithic-kernels.
Click to expand...
Click to collapse
[Google]: android "what is a radio"
Your site(s) here.
[Google]: android "what is a bootloader"
You can do it!
[Google]: android "what is a X"
Google: It really is that easy
Good stuff Paul, it's refreshing to see someone go out of their way to help a newbie every once in a while
There are more polite ways to respond to this guy. Some people learn through interaction. I'm glad someone went out of their way to explain things to this guy. It's a shame how cut throat this community can be sometimes.
I agree, the attitude and lame jokes are really immature at times. Thanks paul for putting a lil effort and explaining few of the key points than cracking the usual radio is a fm/am joke here, the extreme nerdism almost kills me! lol.
As for the cutthroat and "nerdism" out there in this community, you have to remember, most of us that are regulars are ones that have been on this forum for a loooooooong while and not just in the Nexus One sections. I have migrated from WM to Android and see these posts time and time again.
There are Stickied "Noob" guilds galore, there is a search feature, there are TONS of resources out there for someone who puts in a MINIMAL effort can get this BASIC information.
When I first came here, I didn't just open a new post on "what is a ROM and ..." I read, I researched and when something wasn't clear and needed more information that wasn't out there, THEN I posted.
Those of us that may seem like we have an attitude aren't mean people, we don't expect everyone to come here with all the answers an NO questions, we just have an expectation that they at least put forth a LITTLE effort on figuring something out.
Paul did a great job in searching, but you have to wonder why the OP didn't even TRY and google anything or search here?
The impression I got is that it is not worth the OP's time to even try, so they put up a post asking these questions and expected the community to do all the work for them and compile some massive resource into a post that the OP most likely won't read and then start asking questions that were already answered in replies or links.
I have seen this happen time and time again on this board and others, so yeah, I am a bit of a jerk when someone puts forth no effort of their own.
Thanks a lot, Paul and the guys that helped
About me asking, and being new here... I DID search on this forum, but didn't find everything I needed. I used the search function, read the sticky threads, googled... After this, I still had questions, meaning that the information I got was not sufficient and that the additional information I was seeking wasn't accessible enough here. So that's why I asked.
If you don't like new people asking questions, but only expect new members to be experienced ones that will arrive with software/tricks/roms/etc "gifts" for you,you should reconsider your lifes. Maybe as sultans or something similar I agree with the remark about nerdy attitudes. Do you really think this is needed? If my topic is unwanted here, some people called moderators will lock or delete it, it seems it hasn't happened so far...
Back to the initial topic...
Well, maybe I did not make things clear enough. I'm not a complete computer noob. I know what a ROM is (not being specific to android devices), what an OS is, how to write a few lines of code, etc...
From what I understood, the bootloader can be see as the bios in a PC. It can execute a few tasks (diagnostics, rom flash, starting the OS...). The ROM contains the OS, software, config, etc...
As I said, what I don't really see is how all the things are related to each other. On this forum (and other places) I see a lot of alternative ROMs. I do understand what they are and their use. However I also see topics about kernels and radios, and that got me a bit lost. Aren't they already included in the ROMs?
Also, I'd like to learn a bit about how alternative ROMs are created. When additional features (applications?) are added to a ROM (features that were existing on other devices), is it "simply" the application files that from the other device that have been included to the ROM? When new features are added (not coming from other devices, like trackball led), how is that made? I assume it is added to the code somewhere, so is all the code available?
Thanks for helping
I'm going to move this thread to the Q&A section, and also clean up the noob bashing. Remember, not only is bashing discouraged throughout the entire site, but doing it in the Q&A section will likely earn you a short vacation from XDA.
Thanks,
NATF
I'm posting this in the Development section because that is what I am trying to learn about. Please move me if I am mis-posting this.
I'm greatly interested in the the Roms people are making and everything that is being done on these forums. If someone wanted to start to learn about these things, developing and such, where should they start? Do I need to learn Java? Are there certain books I should be reading?
I can flash my phone like its my day job now, and I haven't come across any major problems I couldn't solve by reading, but I have no idea where to start to be able to develop things myself. If any developers here could maybe throw out a few tips on how to get started, what someone should focus on learning, etc., it would be greatly appreciated! I have plenty of time and a great desire to learn so I'm not intimidated by having to do the work, I just have to have some things to focus on. Thank you in advance for any help/advice you can give me!
I always wanted to know how make roms also I was looking around the internet but couldn't find anything that will describe it step by step word for word.
Maccie
It will be a huge writeup.But im sure someone will do it. I am still learning myself. There are some good topics around but different from what we have now
topshelf95 said:
I'm posting this in the Development section because that is what I am trying to learn about. Please move me if I am mis-posting this.
I'm greatly interested in the the Roms people are making and everything that is being done on these forums. If someone wanted to start to learn about these things, developing and such, where should they start? Do I need to learn Java? Are there certain books I should be reading?
I can flash my phone like its my day job now, and I haven't come across any major problems I couldn't solve by reading, but I have no idea where to start to be able to develop things myself. If any developers here could maybe throw out a few tips on how to get started, what someone should focus on learning, etc., it would be greatly appreciated! I have plenty of time and a great desire to learn so I'm not intimidated by having to do the work, I just have to have some things to focus on. Thank you in advance for any help/advice you can give me!
Click to expand...
Click to collapse
There are a number of aspects to android development you have to learn to know how to build a full ROM from scratch. C is of course required for kernel building, and apps are built from java in the dalvik-vm, but can be built against sun java.
of course, to get started, you would need the android sdk available here: http://developer.android.com/sdk/index.html
then there's the cloning of the android git:
http://android.git.kernel.org/
and, specifically for the captivate, there's the captivate source code:
http://opensource.samsung.com/
then there's pulling off the vendor proprietary libs from your phone (which is a ***** and I believe you can grab them from wes's github, though I can't speak for their accuracy) here:
http://github.com/wesgarner/proprietary_vendor_samsung
building the entire android OS from source is a challenge, especially compensating for some changes Samsung has introduced. this is what a real ROM is. now if you're talking about "ROM"s like Cognition and Shep's and even Eugene's Hybrid/Frankin-Twiz... they aren't comparable. Not to belittle any of their efforts, but this is simple "drag and drop" from stuff built by Samsung. While they're very useful tools, there is little actual development going on in them. There are improvements and tweaks, for sure... but it isn't a *true* ROM. All these releases by DesignGears, Eugene, and Shep are good and effective, but it'd be a shame if they weren't because they are just files thrown together from Samsung's already compiled ROM(s). Even the AOSP Beta 3 (which I have a qualm with the name, because it isn't actually AOSP, it's files pulled from an already built AOSP tossed onto Samsung's ROM again) is just modifying binaries (decompile, edit, recompile).
for those, it's as simple as extracting the zip, replacing the files you want, and rezip it. modifying the update-script inside meta-inf if there's something you want to add.
Awesome post Kaik, thanks, I was wondering some of those too.
Thx that explained a bunch
Maccie
Thank you for taking the time to post that Kaik! It's nice to have a place to start! Anyone else have any tips or things they think might be good to check out?
last, but certainly not least and I can't believe I forgot this, is Unhelpful's toolchain to compile against:
http://forum.xda-developers.com/showthread.php?t=761923
he did a lot of testing with various combinations, and this was the best he found to reduce wakeup lag and other issues
Wow. Kaik. That was the most awesome response to that question I have ever seen. Most people just point to developer.android.com and say go learn to program and come back in 5 years.
Thank you for this very useful information. Your the man now dog.
johnyhoffman said:
Most people just point to developer.android.com and say go learn to program and come back in 5 years.
Click to expand...
Click to collapse
Devs are not being mean or pissy, they are being honest and realistic. If development was just "point and click" XDA would not even be here. Give the devs/veterans a break and take it upon yourself to learn the basics and do some searches, if you are that interested.
I would love to just start making my own Android OS just the way I like too but to do that will require much more reading and learning, trying and failing.
You will probably not find "the answer" you are looking for but if you search, read and most importantly, respect the time, energy and anguish people have put into this site you will find the means to get where you want.
Otherwise you can expect... "Let me just glance and peek to see how to do this. Damn what the hell does that mean? Oh well here is a modded ROM. I'll try that. Jeez, that sucks. How do I make my own? Let me just glance and peek to see how to do this. Damn what the hell does that mean? Oh well ..." It is an endless cycle.
I'm not saying this to belittle anyone. Most have been there, including myself. I say this as a vote of confidence to all.
Hang in there, do the work, break some phones, read some books. Really! You have to!
koe1974 said:
Devs are not being mean or pissy, they are being honest and realistic. If development was just "point and click" XDA would not even be here. Give the devs/veterans a break and take it upon yourself to learn the basics and do some searches, if you are that interested.
I would love to just start making my own Android OS just the way I like too but to do that will require much more reading and learning, trying and failing.
You will probably not find "the answer" you are looking for but if you search, read and most importantly, respect the time, energy and anguish people have put into this site you will find the means to get where you want.
Otherwise you can expect... "Let me just glance and peek to see how to do this. Damn what the hell does that mean? Oh well here is a modded ROM. I'll try that. Jeez, that sucks. How do I make my own? Let me just glance and peek to see how to do this. Damn what the hell does that mean? Oh well ..." It is an endless cycle.
I'm not saying this to belittle anyone. Most have been there, including myself. I say this as a vote of confidence to all.
Hang in there, do the work, break some phones, read some books. Really! You have to!
Click to expand...
Click to collapse
this times one thousand. I linked you guys to some very useful sites when it comes to actually putting android together... but understanding how it all works, actually getting a successful build, fixing bugs, etc... I can't even begin to pretend to be able to help with that. if you have little to no experience in C and Java, these things will basically be useless to you. dev's aren't being mean when they brush you off like that, but usually if you can't figure out how to google what to do with the code, they don't have high hopes for what you'll be able to do with it once you find the code.
the idea isn't to be like "f*** off" when they say that, it's more of a "we'll help you when you learn, but you're the one who needs to take the first steps and you need to take the responsibility of learning on yourself."
I was actually referring to the fact that someone like me, a hobbyist programmer for about 10 years now, can make sense of his reply and use it to go forth and actually do something. Most of the guides you find on here that are supposedly pointed at noobs, do not layout things as easily as his post did.
Wasn't criticizing anyone, but I have seen less patience nowadays for any posts such as these.
Was just saying it was a gem of a post for me personally. Maybe it doesn't help the ultra noobs and the more experienced people see it as useless, but for someone with little time right now, it was a perfect post for me.
Don't get me wrong, I am wildly appreciative of all the work going on here & thank those who are working to get a working solution to the B&N 1.1 update.
I am not open to experimenting with my NC beyond trying "verified" hacks. Right now I don't have the time to tinker (wish I did) & try to recover from a procedure that doesn't work. I have read about several attempts to get the 1.1 update & remain rooted or to avoid the update all together only to read farther down (sometimes waaaay farther) that it doesn't work. That's fine & I understand the process, but I would like to see the thread flagged as "Fail" or "unverified" or otherwise indicating that it isn't working. Then, at some point when a bunch of people have success, the thread can be flagged as "verified".
I repeat that I am not complaining here!
Cheers,
kev
Im sorry, but this is the nature of the beast. No solution is 100%, and if you aren't ready to accept that, perhaps this isn't for you. With anything here, it is at your own risk, and frankly, doing something before reading everything you can about it is kind of silly.
As it is, these things happen on every XDA forum, for every device, because of the variable nature of people's setups. Make backups, and work at your own risk..
Just another addition to what Divine_Madcat said was the fact that things change. A fix may be verified for 1.0 or 1.0.1 and then be block or changed with another update or via some other circumstance. The amount of variation from one NOOKcolor to the next simply due to these mods/fixes/kernels/etc. is probably in the thousands of different combinations by now. It would take a whole dedicated team to continue that process of verified/failed, etc.
The very best you can hope for is to see more "works" than "fails" and then have a "works" yourself. I've been really pleased with the quality of documentation and expertise in these forums.
one4thewings said:
Just another addition to what Divine_Madcat said was the fact that things change. A fix may be verified for 1.0 or 1.0.1 and then be block or changed with another update or via some other circumstance. The amount of variation from one NOOKcolor to the next simply due to these mods/fixes/kernels/etc. is probably in the thousands of different combinations by now. It would take a whole dedicated team to continue that process of verified/failed, etc.
The very best you can hope for is to see more "works" than "fails" and then have a "works" yourself. I've been really pleased with the quality of documentation and expertise in these forums.
Click to expand...
Click to collapse
Agreed. I think it's great that so many talented individuals can spend the kind of time required and offer their ideas up to the rest of us!
You might try Nookdevs' Nook Color Portal. They generally won't post a solution until its been around a while and gotten some confirmation from users. Even so, there are always risks and for me at least that's been part of the fun.
Divine_Madcat said:
Im sorry, but this is the nature of the beast. No solution is 100%, and if you aren't ready to accept that, perhaps this isn't for you. With anything here, it is at your own risk, and frankly, doing something before reading everything you can about it is kind of silly.
As it is, these things happen on every XDA forum, for every device, because of the variable nature of people's setups. Make backups, and work at your own risk..
Click to expand...
Click to collapse
QFT
10 Chars
I know & agree with everything y'all have said. I just thought that adding a flag of some sort was a simple enhancement, as some of these threads get very confusing & long & the info is sometimes scattered.
Most of the upgrades here can be implemented whenever I am comfortable with my understanding of the process & it's level of risk. (After reading all of the threads thoroughly). I guess the difference with the 1.1 update is the sense of urgency in having a solution. I am content to leave WiFi off & happy to keep reading, so it's not a big deal.
P.S. I do not in any way find fault with how this forum works & how hard those here are working to make my Nook Color such a fun toy. If not for you, I would be pining for a tablet that I can't afford! Thanks so much for all the hard work & making the info available!
Thanks,
kev