Related
Can some one compile or point me to a cifs.ko that is compatible with the incredible. The ones I can find do not seem to be. Thanks in advance.
Interesting
http://linux.die.net/man/8/mount.cifs Not that I can help but if anyone wanted a quick reference.
Alot of the roms for other phones have it but its not compatible with out kernel. Is there a guide how to compile kernels? I made a couple in linux that worked. long ago..
here ya go...what app are you using to browse CIFS shares? I haven't tested this module, but just compiled it now.
Forgive me as I haven't actually tried this, but here is the 10,000 foot view:
At a minimum, you will need a linux system, with a gcc-arm cross compiler set up. I believe the android-sdk provides one. The version used by current kernels is gcc-4.4.4.
Then you will need the sources of the kernel you are running. The hydra kernel git tree is here: http://github.com/ejhart/Hydra-kernels.git , and the stock kernel sources are here: http://member.america.htc.com/download/RomCode/Source_and_Binaries/incrediblec_cc1c2268.tar.bz2
The hydra git tree doesn't seem to have a a working .config included, but this isn't so important if you are only building and installing kernel modules. From there, you'll need to configure the kernel in cross compiler mode, add the modules you want, and you will need to make sure the version magic string is identical to the kernel you are using. From there run make, and once the compile is finished, find the .ko 's you want, and push them to the /system/modules folder where you can insmod them.
Edit: You can use the .config from /proc/config.gz, didn't see it in there before.
mattwood2000 said:
here ya go...what app are you using to browse CIFS shares? I haven't tested this module, but just compiled it now.
Click to expand...
Click to collapse
I got one from another user but thanks do you still want me to try it? I mounted my share in a directory on the SDCARD so i can browse it with any file manager. I think any app that scans the sd card will also scan my server with about 8TB so that is a minor issue.
kernel compile guide
A guide for compiling kernels can be found here :
http://code.google.com/p/android-serialport-api/wiki/Htc
I not a techie and a newbie at any android development.
Since the guide is more or less a a set of instructions with no theory.
Got it to run, but not sure what I was doing.
Any assistance in provide either cifs.ko for the HTC Aria w/ kernel version :
liberty-2.6.29-21f066a6 or instructions on how to compile the module would be greatly
appreciated.
BTW - there an app on the store for automating the CIFS mount (CIFSManager
Regards,
-d
veli69 said:
I got one from another user but thanks do you still want me to try it? I mounted my share in a directory on the SDCARD so i can browse it with any file manager. I think any app that scans the sd card will also scan my server with about 8TB so that is a minor issue.
Click to expand...
Click to collapse
Could you please post the cifs.ko file that you have that works. Thanks.
OOMatter said:
Could you please post the cifs.ko file that you have that works.
Click to expand...
Click to collapse
Note that the post you quote was from before the 2.2 OTA, and hence that cifs.ko would be incompatible with the current kernel.
elborak said:
Note that the post you quote was from before the 2.2 OTA, and hence that cifs.ko would be incompatible with the current kernel.
Click to expand...
Click to collapse
Thanks for pointing that out. So does anyone have a compatible cifs.ko for the current DINC kernel?
OOMatter said:
Thanks for pointing that out. So does anyone have a compatible cifs.ko for the current DINC kernel?
Click to expand...
Click to collapse
I do. Check my blog. http://adrynalyne.us
Sent from my ADR6300 using XDA App
veli69 said:
Alot of the roms for other phones have it but its not compatible with out kernel. Is there a guide how to compile kernels? I made a couple in linux that worked. long ago..
Click to expand...
Click to collapse
http://marakana.com/forums/android/examples/111.html
GOOOOOOOOOOOOOOOOOOOOOOOOOOOGLE!!!!!!!!! YEAH!
Thats all fine and dandy except our source isn't on any git.
developer.htc.com
philips w732 vermagic '3.0.13 preempt mod_unload armv7' working cifs.ko and md4.ko modules
narod.ru/disk/63766749001.47b679339538b050028c3c7d87506dd2/md4.ko.html
narod.ru/disk/63743140001.693272f3661d5aac547ecc760f04db05/cifs.ko.html
Hi all,
we are trying to build our own kernel for a Samsung Galaxy S (I9000XWJVB).
What we did so far:
- Download the correct sources from "opensource.samsung.com"
- Studied the README
- Installed cross-compiler toolchain
- Created ".config" as described in README
- Kernel compiled
Compilation worked fine -> zImage was available (but with only 2mb very)
OK, looks like initramfs is missing.
The first question is now, where to get / how to create a correct initramfs?
We copied the initramfs from Leshak and we extracted an ".cpio" from a working zImage.
Then we tried to use them in the ".config" (CONFIG_INITRAMFS_SOURCE) for kernel compilation.
Resultant zImage was larger (around 6mb) so it looks like something changed.
But once we installed the tared zImage on the phone (using Odin), the phone freezes during reboot.
Any advice how to progress here?
Is it possible to use Leshaks initramfs for all Galaxy S phones? Or is this only for a specific version? The CONFIG_INITRAMFS_SOURCE should point to the "initrd.arm.initramfs_list", correct? And not to the initramfs-folder?
And: Is there a way to get any type of kernel boot debugging message from the booting phone back to the PC (or the phone screen)?
Many thanks in advance!
I don't know much about kernels. But i will try to help. Have you tried other itiramfs or reconfig them?
There are not many people that will know answer so ask some kernel developers like hardcore, supercurio...
Sent from my GT-I9000 using XDA Premium App
Just saw 2nd question. I think that it should point to intiramfs folder. You can zip all kernel files and upload it so i can take a look at them
Sent from my GT-I9000 using XDA Premium App
Hi,
themate1987 said:
I don't know much about kernels. But i will try to help. Have you tried other itiramfs or reconfig them?
There are not many people that will know answer so ask some kernel developers like hardcore, supercurio...
Click to expand...
Click to collapse
we tried four different initramfs now, but ended up always with a freezing phone.
I would like to ask the kernel experts directly, but I'm new to this forum and not allowed to post in the developers forums. I hope that one of the gurus will reply to this thread.
themate1987 said:
Just saw 2nd question. I think that it should point to intiramfs folder.
Click to expand...
Click to collapse
My understanding is that the .list file will describe the structure of the initramfs folder and if this file is present, it should by used in the .config. Otherwise the .config should point to the folder.
Please correct me if I'm wrong.
But anyway, we tried both versions, none worked.
Regards!
PM some kernel developers
Sent from my GT-I9000 using XDA Premium App
Use speedmod kernel patches with the readme file he has given..
or else you can go through supercurio threads also ...
they explained the kernel compilation methods....
thanks
Did you get this to work finally? I too am trying to compile and flash a custom kernel ( For SGS4G) I point my INIIRAMFS_SOURCE to an extracted initram dir, but the resulting boot zImage does not proceed past the initial boot screen(s) Please let me know if you succeeded, and if yes, how.
Thanks!
What I got the problem was about initramfs.cpio.
At that moment , the most important point you know is you should make the file in Linux..
When my friend made me a file is initramfs.cpio , it worked well.
But what I made in window made always troubles for compile.
So if you made a initramfs.cpio with hexeditor in window, try it in Linux again..
Thx!
I have installed Cyanogenmod 7.1 and modified my bootanimation. I would like to also modify my bootloader screen, the first screen that appears just after the phone boots. Please help on t this topic! Thanx in advance!
Well that's not as easy as changing the bootanimation.... Cause i think you need to build your own kernel.
Thanx! Could you please make or modify a kernel for the cyanogenmod 7.1 that I'm using. I'm pretty new to this android development, all I know is how to root, change bootanimation, and other basic things. Thanx in advance!
Ya kernel...read it can be changed in the param.lfs without having to build a kernel. Not sure how true this is in the case of mini.
What do I have to read and edit? And where can I find this param.lfs? Thanx in advance dude!
I replies on your other thread in Galaxy Mini General. Try modifying TASS.rle in root folder. I don't know if you need to unpack-then-repack your boot.img though.
Edit :
Since this "TASS.rle" doesn't exist in CM7 update zip file, then it means you do have to unpack your boot.img, open the ramdisk folder then edit the extracted TASS.rle" using image editor or something. I never modified TASS.rle so I don't know exactly how to do it.
If you're using Windows, you can use dsixda kitchen+custom cygwin package+Java Dev Kit to do the unpack+repack. It's somewhere in xda.
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
Thanx a lot dude! But are you sure it'll work? I'll try it out, but is there any simpler method than this. Some way that I can modify it using my phone itself? By the way are you using cyanogenmod 7.2 RC 3 by squadzone? How is it? Please give the link too... thanx in advance!
Like I said, I never modified TASS.rle so I have no clue if it will work or not. I did unpacked and repacked boot.img several times using dsixda kitchen and they worked.
I don't know if easier method exist, so I only suggest what I know from browsing.
It looks like in order to do what you want, several steps are needed :
1. Unpacking your boot.img into zImage file (kernel) and ramdisk folder.
Anything inside ramdisk.folder will be flashed into your system partition each time you boot your device. Examples are init.rc, default.prop and TASS.rle. You can do whatever you want with these files, say modifiying their contents, but the changes only persist as long as you do not boot your phone, which will restore them back to initial state as I explained above.
2. Converting TASS.rle found inside ramdisk folder into editable format such as PNG
3. Modifying the converted PNG in point 2 (using Photoshop or other app)
4. Re-converting the modified PNG from point 3 back into RLE format
5. Re-packing (compiling) zImage file and ramdisk folder (having modified TASS.rle from point 4) back into boot.img
6. Flashing boot.img from point 5 into your phone.
To make it short, you need to learn how to :
1. Unpack and repack boot.img, which you can do using dsixda kitchen from here : http://forum.xda-developers.com/showthread.php?t=633246
2. Converting RLE to PNG and vice versa. More info here : http://forum.xda-developers.com/showthread.php?p=20128066
3. Flashing boot.img into phone. You can compress your boot.img into TAR (type this in cygwin shell window "tar -cf boot.img.tar boot.img" and flash it using ODIN with one package option or you can create a flashable zip file.
CM 7.2 RC3 works great for me, better than RC2; but that's my personal judgement and there's a chance you will not agree with me after you try it.
Head over to CM 7.2-RC3 by squazone for download link.
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
@distan
I used Ketut's tools to unpack before...it also had a little something to convert .Rle to raw...only came to my mind now.
Will give this a try tomo.
Shouldn't be that difficult...I think.
And @Nelson
Definitely can't be done in phone.
This is much more than that.
roofrider said:
@distan
I used Ketut's tools to unpack before...it also had a little something to convert .Rle to raw...only came to my mind now.
Will give this a try tomo.
Shouldn't be that difficult...I think.
And @Nelson
Definitely can't be done in phone.
This is much more than that.
Click to expand...
Click to collapse
Nice info buddy, I recall reading his thread too and it's applicable on Galaxy Mini, since both Ace and Galaxy Mini have the same kernel base address and command line parameter (CMIIW).
But I'm not sure if it will work under custom cygwin by dsixda (in case you want to use it under Windows)
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
distan7 said:
Nice info buddy, I recall reading his thread too and it's applicable on Galaxy Mini, since both Ace and Galaxy Mini have the same kernel base address and command line parameter (CMIIW).
But I'm not sure if it will work under custom cygwin by dsixda (in case you want to use it under Windows)
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
Click to expand...
Click to collapse
Thanks.
I have Ubuntu on a vm
And for sure ketut's tool will work if you're using a full linux distro
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
distan7 said:
And for sure ketut's tool will work if you're using a full linux distro
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
Click to expand...
Click to collapse
Ya...but I didn't try cpio to extract ramdisk..simply clicking it mounted the ramdisk and it's contents were visible...I wonder if I make any change and unmount it will be saved or not?! Then no need to gzip and cpio
Thanx guys! roofrider and distan7 for all your help and support! If I had a bank account, I would have donated by now, but since I don't all I can do is click the thanks button! Thanx a lot dudes!
You're welcome mate
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
I've attached the tass.rle converted to tass.png thanks to ketut.
but this is only one of the 2 images that appear while booting.
I have to dump the stl6 to find the other i think...but dumping stl5 bricks the phone (stepph) so a little nervous...but i might give it a try.
edit: no harm done.
but stl6 had nothing....anyone got any ideas?
the .jpg or whatever is hidden somewhere, at least that is how it is for galaxy s variants.
Hi friends of XDA,
I think this might be helpfull for some of you trying to compile kernel from source for S5830i, for the first time.
If you are following the great tutorials to build your first kenrel like:
http://forum.xda-developers.com/showthread.php?t=1748297 from thewadegeek
The first thing taht will happen, is that you cant pull defconfig from /proc/config.gz for S5830i.
Why? There is no such file for your device in there.
Normally the next you will do, is go to the stock sources readme file. And will find out the defconfig is totoro_defconfig
You will compile the kernel with no errors, and you will feel very happy, until you flash your recently compiled kernel and see that you get stuck in the boot_logo screen.
Ok, dont panic, solution is very easy. Samsung readme file is a general readme.
Here is the quid of the question:
totoro_defconfig is not the correct defconfig for S5830i.
S5830i defconfig is bcm21553_cooperve_defconfig
You will find this defconfig in the sources, at:
common/arch/arm/configs folder
Hope this helped. If it helped dont doubt to press the thanks button, this will be very appreciated.
Thank you and sweet kernel development.
Samsung's readme file isn't general, they just took the Galaxy Y's readme (even the model says GT 5360).
What's stranger is that the CHN sources have the correct info.
Also, I didn't need to pull anything. I just used the default config:
Code:
export ARCH=arm
export CROSS_COMPILE=<path>
make bcm21553_cooperve_defconfig
make -j16
Hi GermainZ,
Thats right,never had a look at the CHN readme. I wonder why the other sources are uploaded looooollll strange Samsun guys.
Never the less, forgot to post the next in the original thread.
I recomend to have an original copy of bcm21553_cooperve_defconfig as when you start modifing it some options may fail and its recomended to have a fresh one to copy paste quicly.
Even more for my kernel i copy original file and rename it to nit_defconfig and give it a version number ej nit01_defconfig, its agood practice have latest working defconfig as you will be modifying the file a lot, btw nit is how i call my kernel as you all ready know, this comes from new innovative technologies the name of one of my companys i created recently
But good appreciation GermainZ is always my pleasure to talk with you
Sent from my GT-S5830i using xda app-developers app
Thanks for your tips bro! You had a significant part in booting my kernel. Will add u in credits
No problem hell_lock.
Thank you.
Sent from my GT-S5830i using xda app-developers app
General informations:
This thread's aim is only to represent a central meeting and discussion point for BCM21553 developers and, in particular, for the open Kernel/ROM sources development for the Samsung Galaxy Pocket GT-S5300 (codenamed Cori).
Information for common users:
As already described in the previous section, if you are not a developer, please restrict your posts to the general discussion thread so that developers can maintain good communication. Every post that is not strictly respecting these rules will be reported to the forum moderators. Thanks for your understanding.
For any other BCM21553 device related question or information, please, use this thread as a reference point, instead:
[DEVS ONLY][BCM21553 series] CyanogenMod 11 for BCM21553 Development Discussion
As someone already might know, I'm streambinder, from MoltenMotherBoard team.
I have already followed some projects for the GT-S5300, but especially kept in contact
with some of the events related to the porting of ROM and Kernel sources for BCM21553 chipset based devices.
In this precise moment, the sources in my possession allow you to be able to compile
a bugfree CWM 5.0.2.8 (based on CyanogenMod 7 code) with a kernel based on the Samsung stock one.
The only - fundamental - problem was due to the fact that unless I hadn't used the prebuilt INIT binary
token in the Samsung stock firmware boot.img, the phone would not work - or, better, boot up.
This means that until the situation - regarding this issue - doesn't change, our access to the porting of custom ROM
would be barred.
Recently, I decided to give Cori another chance and rework my sources, looking at the wonderful work brought
by the BroadcomCM team on CyanogenMod 9 (in particular, thanks to @bieltv.3 and @Alberto96) and @psyke83 on CyanogenMod 11.
They've not only been able to run these two ROMs in a more or less crude way, but this developer has been able to write
the necessary strings to make the INIT binary of some of these BCM21553 devices opensource.
Strong of this informations, I readjusted some of the sources of BroadcomCM's CyangenMod 9, which includes
all the progress carried out by both the team and psyke83, in order to make them work even on Cori,
and am now next to the first test of the CWM 6.X.X.X, based on IceCreamSandwich code.
At the same time, @akhbh is working on the KitKat code based CWM.
I hope I can give more information about any progress as soon as possible.
The General Discussion thread for non-development issues is here:
*.[DISCUSSION] CyanogenMod 11 For Galaxy Pocket GT-S5300 Discussion Thread
Made a first test of CWM based on CyanogenMod 9 code.
It seems it cannot flash it as it weighs so much compared to its partition configuration value: in fact, the maximum boot partition size is set up to 5.0MB, but the compiled boot.img weighs 5.3MB.
Will have to resize its weight in order to make it fill into the partition.
@akhbh, have you had any complication in these terms, with CyanogenMod 11 sources?
@psyke83, what do you suggest to do? Do you think an increasement of boot partition would be a better idea?
streambinder said:
Made a first test of CWM based on CyanogenMod 9 code.
It seems it cannot flash it as it weighs so much compared to its partition configuration value: in fact, the maximum boot partition size is set up to 5.0MB, but the compiled boot.img weighs 5.3MB.
Will have to resize its weight in order to make it fill into the partition.
@akhbh, have you had any complication in these terms, with CyanogenMod 11 sources?
@psyke83, what do you suggest to do? Do you think an increasement of boot partition would be a better idea?
Click to expand...
Click to collapse
No, I didn't faced those complications. My boot.img weighted around 4.5 MB in lzma compression mode. In gzip, it increased to more than 5 mb.
akhbh said:
No, I didn't faced those complications. My boot.img weighted around 4.5 MB in lzma compression mode. In gzip, it increased to more than 5 mb.
Click to expand...
Click to collapse
Perfect.
Which kernel have you based your build on?
streambinder said:
Perfect.
Which kernel have you based your build on?
Click to expand...
Click to collapse
Well, I took the GeTux kernel for cori, had to change the board name though and then compile it. CWM was booting even before changing the board name but there was no reaction from the phone on trying to boot cm9/cm11
And after changing board name, a black screen on trying to boot
Another info: When tried to merge cori source into the bcm21553 common one, it did compile but gave bootloop of GT-S5300 logo on trying to boot as well as when trying to go in CWM.
Bieltv.3 recommended to use cori source instead of the bcm21553 common one so we used cori sources
akhbh said:
Well, I took the GeTux kernel for cori, had to change the board name though and then compile it. CWM was booting even before changing the board name but there was no reaction from the phone on trying to boot cm9/cm11
And after changing board name, a black screen on trying to boot
Another info: When tried to merge cori source into the bcm21553 common one, it did compile but gave bootloop of GT-S5300 logo on trying to boot as well as when trying to go in CWM.
Bieltv.3 recommended to use cori source instead of the bcm21553 common one so we used cori sources
Click to expand...
Click to collapse
I suggest to use our Kernel sources for now, too: it will automatically bypass few errors/issues/bootloops that we cannot now fight with.
The most important thing is to make INIT working from sources (hope it will be working
on my CM9 sources, too) and check that every our configuration is correctly working and
making Cori boot into recovery.
Once we'll make it perfectly working without any kind of issue, will be the right time to try
to make Cori supported with the BC21553-common kernel.
streambinder said:
I suggest to use our Kernel sources for now, too: it will automatically bypass few errors/issues/bootloops that we cannot now fight with.
The most important thing is to make INIT working from sources (hope it will be working
on my CM9 sources, too) and check that every our configuration is correctly working and
making Cori boot into recovery.
Once we'll make it perfectly working without any kind of issue, will be the right time to try
to make Cori supported with the BC21553-common kernel.
Click to expand...
Click to collapse
Okay, I will use your kernel sources and try if something is changed once I reach home. For now, I neither have this device nor a PC, as I'm in another city.
Will be keenly watching your work. Will start after reaching home around the end of September
akhbh said:
Okay, I will use your kernel sources and try if something is changed once I reach home. For now, I neither have this device nor a PC, as I'm in another city.
Will be keenly watching your work. Will start after reaching home around the end of September
Click to expand...
Click to collapse
No problem, mate.
Here you have every source in my possession:
platform_kernel_samsung_cori
platform_device_samsung_cori
Keep in contact with me, as I will need some informations by you.
Anyway I'm now making another build, keeping some not so much important binaries excluded, so that I can make the compiled boot.img fill into our little Cori's boot partition. I know it's a dirty workaround, but if it works, I'll use it untill @psyke83 will suggest me a better way to do.
streambinder said:
No problem, mate.
Here you have every source in my possession:
platform_kernel_samsung_cori | github.com
platform_device_samsung_cori
Keep in contact with me, as I will need some informations by you.
Anyway I'm now making another build, keeping some not so much important binaries excluded, so that I can make the compiled boot.img fill into our little Cori's boot partition. I know it's a dirty workaround, but if it works, I'll use it untill @psyke83 will suggest me a better way to do.
Click to expand...
Click to collapse
have u tried to build cwm v6 from cm9 source ??
cleverior.ipul said:
have u tried to build cwm v6 from cm9 source ??
Click to expand...
Click to collapse
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
streambinder said:
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
Click to expand...
Click to collapse
I think we didn't had significant changes. Perhaps the same as totoro. But, that resulted in the internal_sd not mounting error in cwm.
Sadly, as said before, I am away from my home city and can't provide the files to you and can't do the boot.img diffs as well
Try to ask psyke83, he might have a solution for that
akhbh said:
I think we didn't had significant changes. Perhaps the same as totoro. But, that resulted in the internal_sd not mounting error in cwm.
Sadly, as said before, I am away from my home city and can't provide the files to you and can't do the boot.img diffs as well
Try to ask psyke83, he might have a solution for that
Click to expand...
Click to collapse
Then, if you didn't make any massive change upon the sources, then I'll only try using your kernel.
Can you give me your kernel sources, mate, please?
streambinder said:
Then, if you didn't make any massive change upon the sources, then I'll only try using your kernel.
Can you give me your kernel sources, mate, please?
Click to expand...
Click to collapse
Currently, I can provide you the boot.img only. For the sources, @cleverior.ipul can provide the kernel sources coz as said earlier, his kernel is used. Well, we were working together to bring cm11 but weren't successful
akhbh said:
Currently, I can provide you the boot.img only. For the sources, @cleverior.ipul can provide the kernel sources.
Click to expand...
Click to collapse
Ok, please send it to me, will compare it with my package.
streambinder said:
Ok, please send it to me, will compare it with my package.
Click to expand...
Click to collapse
Here it is:
http://www.4shared.com/zip/1nKFbOJ2ba/ccccGetux_CM11.html
streambinder said:
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
Click to expand...
Click to collapse
here the link source https://github.com/cleverior/android_kernel_samsung_cori
i've changed the board name. If your device can not boot after using the zImage from this source, then rename init.bcm21553.rc to init.gt-s5300.rc.
@streambinder, what is grom? As bieltv.3 said that init built grom for cori is required to fix adb over cwm recovery. If adb gets working, then possibly the black screen while booting cm11 might get fixed
akhbh said:
@streambinder, what is grom? As bieltv.3 said that init built grom for cori is required to fix adb over cwm recovery. If adb gets working, then possibly the black screen while booting cm11 might get fixed
Click to expand...
Click to collapse
Sincerely don't what are you talking about.
Anyway, have to try to understand where's the problem with the not-booting CWM.
Will try with your sources and let you know.