I wanted to root my phone and also have a different skin but there are so many different versions like rc33, rc32, cupcake...etc what are the differences between the versions and which is the best version I should use and also the benifits of reflashing different radio versions.
The RCxx builds are based off of the official released (OTA, or Over The Air) that T-Mobile sent out to G1 owners. The xx numbers are the release version numbers. Rc29 had the 'root bug' that was patched in RC32. That is why the first step in rooting your phone is to go back down to that version, so that you can get root.
If you want to stick to the official releases from there, you just want to go to the highest RC version that's out.
You may also see the 1.1 and the 1.5 version numbers.. these are the versions of the android OS itself. Currently, all of the OTA versions released have been 1.1 - the newest update to android is 1.5, which will start to be released by T-Mobile via OTA this week.
From here it get's tricky. Since HTC makes the phone, Google (sort of) makes android and T-mobile releases it for their phones... there are multiple avenues by which the android OS can be obtained (and I'm sure as more manufacturers come on board, there will be more)
As these different flavors of the new 1.5 version (nicknamed cupcake) have been released in official and non-official ways, different developers have tried to create their own released.. this is how all the different versions have appeared. Karkuro relased different versions based on the HTC code and the Google code respectively. TheDudeOfLive released a couple versions based on the Google code... You'd have to read the individual forum threads on each versions to get the gist of the actual differences.. the first post of the threads will usually list what the major differences are.
Basically, like any open source project, there are several forks of the base code - expect this to get even more interesting/complicated in the near future.
Is there a good breakdown on the differences anywhere?
I already asked on AC, but no luck so far.
All - following up on a post in AndroidForums which referenced a comment on the root story here. The comment (from Gee):
Correct me if I’m wrong, but I remember hearing that the drivers/kernel are either encrypted, unusable, or simply unavailable. Meaning that while you can root the Galaxy S and put custom ROMs, you still can’t put unofficial ROMs (like Cyanogen) on it without expecting to break a lot of functionality.
That means that you WONT be putting Froyo on it until Samsung officially releases the ROM which can then later be modified. And if Samsung moves away from the Galaxy S after that update, you’ll never see a fully functioning Gingerbread ROM. Ever. That’s a hard pill for me to swallow.
Click to expand...
Click to collapse
Can anyone shed further light on this?
Sounds counter productive. I heard they will be releasing source code. Would be odd if they kept the rest under wraps or took extra measures to prevent access....
Methinks this is definitely worth further investigation. Need some experienced SGS modders to find this thread...
From what I have seen, the drivers are provided in binary form only (which is basically the same as how drivers are provided on Windows). So long as there isn't some code written into the drivers that would prohibit their running on non-official ROMs, there shouldn't be any problem using the drivers in custom ROMs.
I downloaded the entire sourcecode from the samsung website. Its a 150MB zip file and everything is in there in binary form. It must be compiled. I'm certainly not a linux or android dev but it seems like thats what you need. There's even readme.txt files in there to tell you how to build new versions of software.
I'm wondering how long it'll take for someone to put out a custom ROM for the captivate based on 2.2?
I read couples of threads and realize that if a CM mod is wanted, MS2 must have its bootloader unlock.
Since most work is done in /system partition, why do a bootloader modify is needed?
According to the update.zip, we can modify /system partition already, so why do we need bootloader unlock?
CyanogenMod needs its own kernel.
I guess that, since cyanogen is based on gingerbread now,
it runs with a more up-to-date kernel than the milestone's.
The locked bootloader and the efuse thing prevents updating the kernel.
It's possible that someone, using Cyanogen source, makes a backport running on our kernel, but I think it's a huge work...
However, the clever guys from freemymoto.com have created a hack that is capable of launching an other kernel after the legit one starts.
If salvation comes (Cyanogen alleluia ), it will certainly come from this project.
Actually, the hack works on DroidX, and Droid2. So it is 99.9% sure that with some work, it may run on milestone 2 as well.
So, to get Cyanogen work on MM2, we need :
- A very good developer, with android (of course !), linux kernel and kinit knowledge, able to port freemymoto's hack, and Cyanogen
- Hardware drivers for the Milestone (bluetooth, lan, gsm, 3g, touchscreen...)
If we find the golden dev, I personnally think that CyanogenMod could be out for milestone2 sooner than what most people think...
momus87 said:
CyanogenMod needs its own kernel.
I guess that, since cyanogen is based on gingerbread now,
it runs with a more up-to-date kernel than the milestone's.
The locked bootloader and the efuse thing prevents updating the kernel.
It's possible that someone, using Cyanogen source, makes a backport running on our kernel, but I think it's a huge work...
However, the clever guys from freemymoto.com have created a hack that is capable of launching an other kernel after the legit one starts.
If salvation comes (Cyanogen alleluia ), it will certainly come from this project.
Actually, the hack works on DroidX, and Droid2. So it is 99.9% sure that with some work, it may run on milestone 2 as well.
So, to get Cyanogen work on MM2, we need :
- A very good developer, with android (of course !), linux kernel and kinit knowledge, able to port freemymoto's hack, and Cyanogen
- Hardware drivers for the Milestone (bluetooth, lan, gsm, 3g, touchscreen...)
If we find the golden dev, I personnally think that CyanogenMod could be out for milestone2 sooner than what most people think...
Click to expand...
Click to collapse
I LOVE YOUR REPLY!
Well, this is the first reply to me in this forum.Ya...nobody reply me before...so bad..
Milestone has also a locked bootloader, but a CM7 port running on it. That is what makes me want to do something on my MS2.
I'm a C++ programmer, so I learn everything about this these days.
Thank you, really.
And I think I'd read all the freemymoto.com site RIGHT NOW~~
Well, if you think you can be the golden dev, you just made my day...
If you try this, I (and almost everybody here) will at least help providing the hardware drivers.
But the first step is to make the hack work on MM2...
Edit : For the milestone1, the bootloader security has been compromised using a leaked unofficial rom build,
which lead to custom kernels, without needing a hack like freemymoto's.
In fact, freemymoto's hack is based on a milestone1 project, which was abandoned after the rom leak.
It circumvents both bootloader lock and efuse by starting a second kernel after the first one.
(What I couldn't figure out is what happens of the first one... Still in memory? Still using some ressources?)
I read the site yesterday, however sadly, I don't have any experience about writing drivers of cell phone.
So I just sent a e-mail to them to ask if I can provide any help and what to do.
Hope I can help. I'll try my best.
For about the second kernel...I guess I have to read source to know what happened to them...
Anyway, thank you for your reply. At least I get a way to help^^
I didn't mean that we will have to write the drivers from scratch. But we will have to find them.
Hopefully, most of them are open-source. Wifi/bluetooth per example, is handled by a wl1271 chip. Drivers are available on texas instruments website...
You should get in touch with Pizzaroll, who is also trying to make the hack work on milestone2
It's really good news that there maybe a hack bootloader, i like my mm2 but it is really a pity that no much ROM.
liuyanghejerry...
Polish team try to broke bootloader with Boinc (many computers calculate 1 thing), maybe You and Yours friends can join to project?
In China lives maaaaany peoples, this can be speed up calculations
I don't think that distributed computing is the solution...
Even if the boinc project lets us find the signing key, we will have to do the same for the efuse thing.
The freemymoto's hack is a solution to circumvent both of these protections, and doesn't need any computing.
We only need someone to modify some parts of the code to make it work on Milestone2.
Tomszyn said:
liuyanghejerry...
Polish team try to broke bootloader with Boinc (many computers calculate 1 thing), maybe You and Yours friends can join to project?
In China lives maaaaany peoples, this can be speed up calculations
Click to expand...
Click to collapse
Currently I'm studying kexec method now, thanks to PizzaRoll and momus87's help^^
Well, in fact, I like to program and burn my brain. However, the Boinc method seems not really interesting...
Well Boinc is the best solution if you want to use bruteforce.
But even with a whole army of core i7, bruteforcing a 1024bits key is unthinkable actually...
Is this eFuse thing harder to break than the one used in iPhone? If it is then Mr Jobs should adopt a similar approach.
What is the likelihood that updated versions of Android will be available for the Touch (official or homebrew) ? It would be superfly if we could get a CyanogenMod release for it but I don't know how feasible that would be.
At some point, a sticky needs to be created saying that no custom roms are being developed at the moment, and won't be for a while.
Since it's been a while since this exploit has been known, and I know the CM team officially patched the current versions of their ROMs, but does anyone (CM team or not) know if all CM versions will be patched? I'm currently using the official nightly 3/1/2013 CM7 (http://get.cm/?device=jordan), and would really like to be safe from this exploit. I know it's an older version of CM, but it's the best ROM for me, and I really don't want to change ROMs just for a patch.
Well since nobody seems to care, or just didn't get to this thread yet, I did some searching. It seems like the CM team will eventually patch it, but in the meantime if you use CM7 you can use Maniac's version which has the patch built in. Here's some info for both versions:
http://www.cyanogenmod.org/blog/this-week-in-cm-july-12-2013
"We will likely do a legacy release to CM7 to address these in the future as well, but for now, users of legacy releases of CM 9 and 10.0 are encouraged to update to the latest nightlies available; as always, stay vigilant and safe."
http://forum.xda-developers.com/showthread.php?t=2359305
http://translate.google.com/transla...genmod-7-android-2-3-7-a-707.html#post6064392
Enjoy.