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.
Related
maybe someone more linux savvy can check into this.
a search on our kernel version 2.6.27 thats on the moment brings up a website with a program for a local root vulnerability.
http://www.milw0rm.com/exploits/9545
not sure if it can be compiled for android... Just trying to help
I compiled it, and i am trying to get it to work but its running me into a brick wall. Its weird cause it works on my computer(full linux)... so Ill keep trying
Intresting indeed. I wish i could figure it out, but i dont know anything about linux.
there is some additional info over at ppc geeks here
http://forum.ppcgeeks.com/showthread.php?t=96237
Have you rewritten the x86 assembly instructions for ARM assembly? Also, I tried one of the milw0rm exploits on my Moment...seems they patched the kernel before the release.
I managed to discover a root exploit but its not the same as we are used to thanks to Samsungs stupid RFS aka FAT16 rom file system.
I'm nor knowledgable to make a rom, but hopefully this can be used to redo the rom in yffs2 so that it will work with existing apps, because even if we COULD keep root, stuff doesnt work, like nandroid, or Root Explorer.
http://www.samsungmomentforum.com/how-to/root-access-(finally-achieved!)/
I know many devs frequent xda and with zefie's root expliot maybe someone with the knowledge can create a rom for it in yffs2 using the source code samsung released.
Link: http://phandroid.com/2009/11/24/sprints-moment-open-source-released-by-samsung/
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?
Hello everybody,
I'm an Android app developer for some time, but from some time ago until now I have been tweaking the framework, trying to enhance, customize and maybe correcting bugs, so I'm working on the emulator, but I would like to test it on my device (Atrix).
Since I'm a newbie on this matters and I found plenty of threads and sites/blogs, I got a little confused on what are the steps to be made, specially because I would like to build from source as to have my modifications flashed. I'm aware of the hardware implications for my specific device, so I decided to use a reported working rom source code for my device, but i'm a little lost. I thoutgh to be using Cyanogem but I don't know the specifics.
Since I already have the source code AOSP, I think It would be painful to make it work on my device (drivers, kernel, so on...).
I just want (for now) see my framework modifications on device. Anyone could point me to the right direction?
I thought of using this firmware here.
Thank you all.
I would really like to get the OS updated on this device, I'm sure I'm not alone.
I've been following many of the guides on this forum, or youtube videos, but with no luck.
Is there anyone who can help me to figure this out better?
Building AOSP or Porting Cyanogen mod would be ideal, is this possible?
I have had the original a7 since it was released and the major hangup has always been, the kernel. The kernel source for 2.2 froyo has been released, but, no one has made or ported a kernel past that. Dexter the great did a lot with only that kernel, CM7 and Honeycomb, but limited because the old kernel. We need a 3.0 kernel for CM9/10 to really move. There are similar tegra devices that have Honeycomb and beyond, but swapping kernels has been reported to only partially work. I hope that it will happen one day, this baby is powerful.
So beyond my ranting we need, device tree, drivers, and a kernel.
I have been trying myself to push all sorts of Linux for Tegra (ubuntu, gentoo, and geexbox) as well as trying to figure out how dexter had started running ICS on his before he dropped the project.
What is known: this is an abnormal Harmony tegra 2.
What you need to know for APX: A7+ uses hsmmc interface, so all nvflash designed for nand or emmc will inherently fail (or at least has been the case thus far)
I dont know how exactly this is, but due to its odd nature most prepackaged or script made bootloaders will fail. I'd love to see ICS or JB on this device for sure, but making an APX backup would need a new bootloader, or at least a new boot.img for sure.
I'm a tinkerer, with very little programming skill. I can google as good as anybody though lol.
Somebody needs to design an uber cross-compiler that can just transform the kernel to 3+ so we can stop wishing for new firmware and just have it lol
Hi, I'm kind new in creating stuff for my phones but I want to give a try and bring CM/AOSP (I know that they are totally different things) to our phones.
I've done a research and all that I found was that it wasn't possible because we haven't the kernel source. But now that it is available in the Samsumg Open Source page could we make that possible?
Thanks a lot!!
If u really did the research, u should know someone had made this before but unable to call success....
http://forum.xda-developers.com/s7-edge/development/cyanogenmod-13-galaxy-s7-edge-t3414697
pigmich said:
If u really did the research, u should know someone had made this before but unable to call success....
http://forum.xda-developers.com/s7-edge/development/cyanogenmod-13-galaxy-s7-edge-t3414697
Click to expand...
Click to collapse
Yes, i did read that, but everything i found was this:
In the case of the S7/S7E because the SOC is either closed source (Exynos) or has a locked bootloader (Qualcomm). The former makes it very difficult to produce a Rom that approaches anything near being stable, the latter makes it literally impossible until the bootloader is unlocked, which is unlikely to happen.
Click to expand...
Click to collapse
But I can't understand why if we already got the kernel source. Can't we just modify the kernel to make a kind of "mask" that allows the ROM to use the hardware correctly?
Maybe I'm asking something really stupid, and if thats the case I'm sorry, but I really want to know why we fail in this and see if I can find a workaround
Start here: http://forum.xda-developers.com/s7-edge/development/cyanogenmod-13-galaxy-s7-edge-t3414697
Get the source, make a local_manifest.xml file, get the rest of the source, edit the source code and build a rom .
But before You try, I can already tell You that it will be extremely hard to do. I've got CM to compile (yeah, compiling is actually a HUGE step) on other devices and then eventually to boot. But it took couple of days of code fixing (which I at this point somehow understand but it's still quite a magic for me).
Couple of days ago I tried building CM 13 and 14 for S7 Edge and after a whole day of fixing code and stuff I gave up. The worst issues are "shared library, excludes, includes" thingys.