Gents,
I need your help about "kernel", as I know when installing Android I need the folder named Android and the data.img.
But the kernel what is that?
Thanks for reading and more for helping.
The kernel is the core of the Android OS. Windows too runs on a kernel. Every build already includes one, and usually the most up-to-date or stable version, so you shouldn't have to worry about it, unless you want to update your kernel some time in the future.
I've been running Android for several months now and I've not updated the kernel once.
Still there is somthing to say
First I want to thank you for giving me some of your time.
The answer is clear, but why there is update always (now is 8.6)?
and what the kernel is including, is it the same of Android folder?
I hope I will find some more time.
Check out here for a bunch of explanations of terms that are commonly used around here
http://forum.xda-developers.com/showthread.php?t=852660&highlight=glossary
The reason that the kernels are updated alot is that the people who build the kernels find flaws in them through testing them, and through the feedback they recieve here on XDA.
Then they work to try and find ways to fix those flaws. Sometimes in fixing one flaw, a new one emerges. Generally it is a good idea to use the latest version of whatever kernel came with the build.
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.
I was wondering how hard it would be to alter the patches in the update.zip found here to work with the leon. I know the two phones are almost identical as seen here. as of right now there is only an update for the sprint/boost/virgin g-stylo's but there is supposed to be one coming for the t-mobile/mpcs one soon. i've taken the source and started tinkering with it. I've compiled the kernel changing TARGET_PRODUCT=g4stylusds_global_com to TARGET_PRODUCT=c50_mpcs_us but leaving the config as g4stylusds_global_com_defconfig and get far enough to get the zImage, but not the ko files. I have not yet compiled the rom, and it was about this point i started thinking about the update.zip DominicGresham was kind enough to provide us and maybe it would be easier than editing the source. any input would be appreciated. I like 6.x and would like to have it on my daily driver, and help everyone else that wants it for our device. i'm going to keep tinkering away until i get something besides a bootloop, and will attach the zimage i got after this test compile again on the kernel with the mpcs gstylo defconfig. i guess i should go ahead and try to compile the rom also and see how that goes. https://www.dropbox.com/sh/04pab4lbxncd7rr/AAA_GesYl74E35ikF4weaw1ca?dl=0
natediggler said:
I was wondering how hard it would be to alter the patches in the update.zip found here to work with the leon. I know the two phones are almost identical as seen here. as of right now there is only an update for the sprint/boost/virgin g-stylo's but there is supposed to be one coming for the t-mobile/mpcs one soon. i've taken the source and started tinkering with it. I've compiled the kernel changing TARGET_PRODUCT=g4stylusds_global_com to TARGET_PRODUCT=c50_mpcs_us but leaving the config as g4stylusds_global_com_defconfig and get far enough to get the zImage, but not the ko files. I have not yet compiled the rom, and it was about this point i started thinking about the update.zip DominicGresham was kind enough to provide us and maybe it would be easier than editing the source. any input would be appreciated. I like 6.x and would like to have it on my daily driver, and help everyone else that wants it for our device. i'm going to keep tinkering away until i get something besides a bootloop, and will attach the zimage i got after this test compile again on the kernel with the mpcs gstylo defconfig. i guess i should go ahead and try to compile the rom also and see how that goes. https://www.dropbox.com/sh/04pab4lbxncd7rr/AAA_GesYl74E35ikF4weaw1ca?dl=0
Click to expand...
Click to collapse
Hey are you still working on this rom? i would like to know because i can try to help in any way if needed
### check update notes. anywhere in this thred I have placed ### is a update
Original post is in ()
((Ok so here's the low down. I have the SM-G530T1. am trying to root the stock, deknox, deodex, debloat but leave the MyMetro app and the hotspot app other mods you name it.. but those are for starters. I have not found a stable way to pull this off yet as the only rooting methods I found that lets me use supersu is CF-Autoroot..... but... it is for the SM-G530T not the T1 so even though it works it still messes up which is why I am here.
I am hungry for learning and becoming a dev one day so I'd like to learn my way around the Kitchen but so far the windows kitchens are just bootlooping me.. Bad batches roms... I have tried many many ways and no success yet because the stock rom is such a pain to mess with unless you have root access. I thought about trying to use king root just to get a stock rom pull but im not sure if that idea will workout for me in the end seeing how kingroot is such a dbag and doesn't let you use supersu. I Need all the help I can get I'd really love to get a working rom for my dumb little phone so I can use that as a base to learn from.
The T1 and the T dont have much in differences so if one of you awesome people could maybe check out the stock metro pcs version for me and help me get something stable I'd appreciate that a lot. I am trying to help a few people out with this same phone as well so all credit will go to those who helped make this possible. I have windows 7 64bit that barely works and is not mine so I am limited to what I can do. I think my biggest issue is I am not able to use linux and ubuntu because this laptop is really old and barely works. VM doesn't even register the 64bit on this laptop. really sucks.:silly:
###### UPDATE as of 8/25/16, With the help of @ASSAYYED and his awesome kitchen made for windows. I have been able to at least get proper root access now.. but still need a recovery. I am trying to make one from stock but really need help for my device. Here are the specs.. All I need is either some one to be awesome and make me a quick one or tell me hw to make one for a qcom device like I have please..
my phone info if that helps http://www.4shared.com/photo/ZaSM2d9rce/Screenshot_2016-08-25-07-08-53.html
http://www.4shared.com/photo/G4zmKEw9ce/Screenshot_2016-08-25-07-08-41.html
http://www.4shared.com/photo/Eb7gXgLace/Screenshot_2016-08-25-07-07-00.html
@ASSAYYED , for helping me thus far and providing a awesome windows kitchen to cook in.
here is link to his thread and tool info, http://forum.xda-developers.com/che...-android-roms-editor-assayyedkitchen-t3410545 ####
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.