Okay so I'm currently downloading this 'Opensource_Update4.zip' file from Opensource, which I assume is the Official Kernel?
Just a few quick questions that I'd appreciate your help with guys:
1. Am I correct in what I just said above?
2. If so, do I just flash the file through ODIN?
3. Will this wipe my phone back to factory settings?
4. Will this affect my device being rooted?
Thanks in advance
New_World_Order said:
1. Am I correct in what I just said above?
Click to expand...
Click to collapse
No.
New_World_Order said:
2. If so, do I just flash the file through ODIN?
Click to expand...
Click to collapse
Again: no.
New_World_Order said:
3. Will this wipe my phone back to factory settings?
Click to expand...
Click to collapse
You will not be able to flash this, as it's not a flashable kernel, but SOURCE CODE.
So many wrong things in just one post
VAXXi said:
No.
Again: no.
You will not be able to flash this, as it's not a flashable kernel, but SOURCE CODE.
So many wrong things in just one post
Click to expand...
Click to collapse
Woaaaaaah I need a huge slap.
Would you be so kind as to explain please? :$
Sent from my GT-I9100 using XDA
Not really, as it's quite long
But the tl;dr version is: what Samsung published today is the source code (human readable code) for the ICS kernel. The ICS kernel is the "core" of the system, if you want. By compiling the source code, you obtain the machine code (specifically one zImage file) which runs on your device.
They are forced to publish the sources due to GPL requirements, but they're not very helpful in doing this. Inside the source code, there's still binary code (device drivers, etc) which cannot be published due to various agreements with the hardware manufacturers. Having this source code, even incomplete as it is, allows developers to see how the binary code is treated; this way, they can improve their code or even develop open-source replacements for the closed binary part of the kernel.
VAXXi said:
Not really, as it's quite long
But the tl;dr version is: what Samsung published today is the source code (human readable code) for the ICS kernel. The ICS kernel is the "core" of the system, if you want. By compiling the source code, you obtain the machine code (specifically one zImage file) which runs on your device.
They are forced to publish the sources due to GPL requirements, but they're not very helpful in doing this. Inside the source code, there's still binary code (device drivers, etc) which cannot be published due to various agreements with the hardware manufacturers. Having this source code, even incomplete as it is, allows developers to see how the binary code is treated; this way, they can improve their code or even develop open-source replacements for the closed binary part of the kernel.
Click to expand...
Click to collapse
Hahahaa okay thanks...
I think I'll just leave it alone! :')
Sent from my GT-I9100 using XDA
Related
Okay, I managed to fix the sources and got it compiled.
This is based on 4.06/4.08 sources with 4.08 ramdisk.
Use it at your own risk. If you brick your phone, it will be your fault, not mine.
I do not own a Dell Venue and therefore cannot test this.
zImage :
fastboot flash zimage zImage
fastboot reboot
boot.img :
fastboot flash boot boot.img
fastboot reboot
Download :
dell-venue-dbg1.zip
dell-venue-dbg2.zip
dell-venue-dbg3.zip
WiFi module :
dhd.ko-dbg1.zip
Thanks.
Yes, we would.
Cool, right now I have a hard time finding the right defconfig.
In case someone could point me to the right file :
https://github.com/adridu59/dell-venue-kernel/tree/master/arch/arm/configs
Edit :
It seems to be codenamed "toucan".
adridu59 said:
Cool, right now I have a hard time finding the right defconfig.
In case someone could point me to the right file :
https://github.com/adridu59/dell-venue-kernel/tree/master/arch/arm/configs
Edit :
It seems to be codenamed "toucan".
Click to expand...
Click to collapse
I think you'll try all of them, then test on your real device and.....
)
nguyen_vh said:
I think you'll try all of them, then test on your real device and.....
)
Click to expand...
Click to collapse
I made an overlap comparaison and I think that this is it.
Right now I am fixing the sources, they are crap tbh.
adridu59 said:
i made an overlap comparaison and i think that this is it.
Right now i am fixing the sources, they are crap tbh.
Click to expand...
Click to collapse
thanks for your effort :d
Yes
Venue have Custom Kernel! I have one
Kinda busy right now working on my own device but you can contribute if ya want. github.com/adridu59
I'm excited about this topic! Please keep me up to date with this. BTW, I also think that v4.06 source from Dell OpenSource is crappy. Could you please public your change list after you complete the work, it's very helpful to us.
chacona said:
I'm excited about this topic! Please keep me up to date with this. BTW, I also think that v4.06 source from Dell OpenSource is crappy. Could you please public your change list after you complete the work, it's very helpful to us.
Click to expand...
Click to collapse
Well check my github, I haven't worked on this for a while but I'm not letting it down.
First build on first post, follow instructions. Thanks.
406 and 408 apparently use the same kernel according to dell. Though we've had the suspicion that there were differences, apparently there isnt.
TheManii said:
406 and 408 apparently use the same kernel according to dell. Though we've had the suspicion that there were differences, apparently there isnt.
Click to expand...
Click to collapse
Yes, that's what I was thinking. And otherwise they would've published the sources.
I tried to flash your zImage, what I received is "Flashing Error -2", in red background in fast boot mode.
BTW, I would like to ask the way you build the kernel. Did you build directly from /kernel folder (with .config), or you build from ROM's source tree (/kernel folder's parent, using "build/envsetup", then "choosecombo")? I would like to get my hands dirty with this work too!
If my dev pc wasnt broken at the moment, I could glue it together with the stock ramdisk and make a flashable zip.
Here's the stock 408 kernel: boot-408.img
You can glue it together with that ram disk if desired, but shouldnt it also generate a ramdisk when building the kernel?
Just as much the ramdisk's contents arnt that unusual, you could prob guess at a few things and reconstruct it without issue.
chacona said:
I tried to flash your zImage, what I received is "Flashing Error -2", in red background in fast boot mode.
BTW, I would like to ask the way you build the kernel. Did you build directly from /kernel folder (with .config), or you build from ROM's source tree (/kernel folder's parent, using "build/envsetup", then "choosecombo")? I would like to get my hands dirty with this work too!
Click to expand...
Click to collapse
Thanks for testing.
I just use the corresponding defconfig, that is the usual way to do it.
I don't really see what you mean by ROM source tree...
TheManii said:
If my dev pc wasnt broken at the moment, I could glue it together with the stock ramdisk and make a flashable zip.
Here's the stock 408 kernel: boot-408.img
You can glue it together with that ram disk if desired, but shouldnt it also generate a ramdisk when building the kernel?
Just as much the ramdisk's contents arnt that unusual, you could prob guess at a few things and reconstruct it without issue.
Click to expand...
Click to collapse
Nao, the ramdisk isn't compiled code. Usually you extract it from the stock kernel and build with mkbootimg or any similar tool.
Thanks for the link BTW.
Okay, I built the boot.img. Offset is 0x20000000.
Check first post, thanks.
adridu59 said:
Thanks for testing.
I just use the corresponding defconfig, that is the usual way to do it.
I don't really see what you mean by ROM source tree...
Thanks for the link BTW.
Click to expand...
Click to collapse
Sorry for not making it clear. By saying "from ROM source tree", I mean the way below (ftp.dell.com/opensource/venue/v4.06/Venue-HOW-TO-BUILD.txt)
Code:
kernel
1) download source tree of android froyo from Qualcomm.
2) replace kernel
3) build kernel by
. build/envsetup.sh
choosecombo
...
5) make -j4 kernel
# update on 4/27/2012 - 23:18 GMT+7
I built an update.zip, with all the files including boot.img and system/lib/modules. What I got is, the Dell logo is hung there like being fallen into an infinite loop.
chacona said:
Sorry for not making it clear. By saying "from ROM source tree", I mean the way below (ftp.dell.com/opensource/venue/v4.06/Venue-HOW-TO-BUILD.txt)
Code:
kernel
1) download source tree of android froyo from Qualcomm.
2) replace kernel
3) build kernel by
. build/envsetup.sh
choosecombo
...
5) make -j4 kernel
Click to expand...
Click to collapse
First time I see this kind of instructions.
Code:
export ARCH=arm
export CROSS_COMPILE=~/toolchains/arm-eabi-4.4.3/prebuilt/linux-x86/bin/arm-eabi-
make toucan-perf_defconfig
make
chacona said:
# update on 4/27/2012 - 23:18 GMT+7
I built an update.zip, with all the files including boot.img and system/lib/modules. What I got is, the Dell logo is hung there like being fallen into an infinite loop.
Click to expand...
Click to collapse
Would you try again using fastboot please ? thanks.
@Adridu59: still fail, flashing boot.img using fastboot gives the same result as I described above. I will try to get your config files and build a copy myself to see what's going on!
I have a kernel image whose source is not open =| any way to decompile it, so I get an idea to write a kernel from scratch. It is based on linux 2.6.35.7 with some addons
Ok. No more android development by me :sly:
ramoneC said:
I have a kernel image whose source is not open =| any way to decompile it, so I get an idea to write a kernel from scratch. It is based on linux 2.6.35.7 with some addons
Click to expand...
Click to collapse
You cant decompile a kernel zimage
And Questions belong in the Q&A thread, not here.
ramoneC said:
I have a kernel image whose source is not open =| any way to decompile it, so I get an idea to write a kernel from scratch. It is based on linux 2.6.35.7 with some addons
Click to expand...
Click to collapse
Yes, you can't decompile a zImage. Only compiling from the sources is possible.
If you want to get an idea for compiling kernel, then I'd suggest to get the sources from the Manufacture's website (Yes, they'll publish the sources) and compile with adding features or not, and if successful then you can try it on Stock ROM.
ramoneC said:
I have a kernel image whose source is not open =| any way to decompile it, so I get an idea to write a kernel from scratch. It is based on linux 2.6.35.7 with some addons
Click to expand...
Click to collapse
by the open source licence that the kernal is distributed under they are required to provide you with the sources. if not on their website, then send them an email.
how did magisk patch the kernel if not decompile. anyone explain?
kanso said:
by the open source licence that the kernal is distributed under they are required to provide you with the sources. if not on their website, then send them an email.
Click to expand...
Click to collapse
I got SILENCE from them ☺ and this is what i hate the most in many places when there is no response, like in chatting, forum...
Hi guys,
I went to check for the HTC DX source code on htcdev.com, and saw there were around 31 sources, but they're are all CRC's...
Could anyone please explain to me, what is a CRC? I tried googling it, but it didn't really help.
Sent from my HTC Desire X using xda premium
kernel source
Lloir said:
kernel source
Click to expand...
Click to collapse
I have been reading up on making roms, mostly about AOSP and CM, since they have best info and tutorials and such. But at some point, they both say to port to a new device you need to have the proprietary files (non open source device-specific software) to be able to build a working rom, using ./extract-files.sh or ./proprietary-files.sh.
From what I've read, identifying these files is mostly educated (not my case, lol) guessing, trial and error,... But I was wondering : is this CRC source code what they are talking about and would there be a way to get all the necessary proprietary files from it ?
infernal77 said:
I have been reading up on making roms, mostly about AOSP and CM, since they have best info and tutorials and such. But at some point, they both say to port to a new device you need to have the proprietary files (non open source device-specific software) to be able to build a working rom, using ./extract-files.sh or ./proprietary-files.sh.
From what I've read, identifying these files is mostly educated (not my case, lol) guessing, trial and error,... But I was wondering : is this CRC source code what they are talking about and would there be a way to get all the necessary proprietary files from it ?
Click to expand...
Click to collapse
Search for vendor protou github.
Google it. You'll find proprietary files.
Regards
Sent from my Desire using xda app-developers app
Yasir Javed Ansari said:
Search for vendor protou github.
Google it. You'll find proprietary files.
Regards
Sent from my Desire using xda app-developers app
Click to expand...
Click to collapse
Thanks, Yasir, I know lli0r made a device and vendor tree, but he said the vendor tree might be incomplete. He tried to make us a CM9 but hasn't got the device itself. I also read you can extract the files from a running device, but for that you need extract-files.sh or proprietary-files.sh, which isn't in there. I'm sure I can google and find one of those files from another device and try to run them on mine, but they're probably device-specific as well. And there isn't one of those files in lli0r's github. I checked that I'm sorry, I am ompletely new to Android, let alone building roms, but I love to just experiment a bit
Btw, when are you getting your Desire X ?
Hello everyone, I'm a complete noob at compiling. I'm thinking about compiling OmniROM 6.0 for XOLO BLACK. So, I wanted to ask how big is the download size of its source code and do we have a need of Kernel while compiling? Although my device does have an open source kernel. Could be found here: https://github.com/hiveinside/xolo_kernel
I'll be grateful if someone could help me with my questions
You will need about 50-100gb for all the source. Yes you will also need the kernel source as well as the device trees. Then it will just be a matter of fixing the bugs that come up. You didn't think it would just work did you?
zelendel said:
You will need about 50-100gb for all the source. Yes you will also need the kernel source as well as the device trees. Then it will just be a matter of fixing the bugs that come up. You didn't think it would just work did you?
Click to expand...
Click to collapse
No no, I meant what would be the download size? You know after doing the "repo sync" command. Also, I think it'll extract the kernel automatically from my device and what is "device tree?" Vendor files?
Well, I know that I have to face bugs but I think awesome people like you will help me fix 'em.
Wish me luck!
So, after destroying a tremendous amount of data and a whole lot of wait, I finally synced the whole OmniROM 6.0 source code via repo. Now I want to compile it for my device XOLO BLACK (Codename: BLACK) so, can somebody tell me how I can and what am I gonna need (I mean files, like vendor files, kernel etc.)?
Also, how can I extract its device tree? Because it's not available online.
You will need the full kernel source code to even begin and everything I have found says it is not released. Without it you are out of luck.
zelendel said:
You will need the full kernel source code to even begin and everything I have found says it is not released. Without it you are out of luck.
Click to expand...
Click to collapse
No no, kernel is here: https://github.com/hiveinside/xolo_kernel
What do I need now?
NutVolt said:
No no, kernel is here: https://github.com/hiveinside/xolo_kernel
What do I need now?
Click to expand...
Click to collapse
You will need the device tree as well as working on the errors in the kernel as they come up and they will. Also you may have to fix any issues with the source as it only contains the open source parts. Check out some of the building tuts on the site.
It will not be a simple matter of adding the kernel and stuff and then building. It normally takes weeks of bug hunting and fixing to get it to even boot.
zelendel said:
You will need the device tree as well as working on the errors in the kernel as they come up and they will. Also you may have to fix any issues with the source as it only contains the open source parts. Check out some of the building tuts on the site.
It will not be a simple matter of adding the kernel and stuff and then building. It normally takes weeks of bug hunting and fixing to get it to even boot.
Click to expand...
Click to collapse
I know it's gonna take long but if I can't even start then I'll feel very bad, all the hard work I've done to just fetch the source.
Anyway, how can I make a device tree? Can you teach me?