Building replicant for the Galaxy Player 50 (YP-G50).

[Josh Branning]

On 29/05/12 14:28, Igor Almeida wrote:
> On Tue, May 29, 2012 at 10:15 AM, Josh Branning
> <lovell.joshyyy at gmail.com> wrote:
>> On 29/05/12 00:11, Denis 'GNUtoo' Carikli wrote:
>>> On Mon, 2012-05-28 at 21:47 +0100, Josh Branning wrote:
>>>> The galaxy player 50 has the same SoC as the galaxy S. What version of
>>>> the kernel does the galaxy S use with replicant?
>>> 2.6.35 I think. there is also a 3.0 available but replicant doesn't use it yet.
>>>> The sources I have downloaded for the YP-G50 are for the 2.6.29 version
>>>> of the kernel. There are two modules, bcm4329 and fm_si4709.
>>> bcm4329 is the bluetooth+wifi chip and the si4709 is an FM radio chip.
>>> forget about the modules for now, concentrate on the zImage.
>>>> I compiled the kernel into a zImage and tried flashing, and there is a
>>>> definite improvement (instead just the logo SAMSUNG appearing, I now get
>>>> that and a black screen for about a second). The kernel modules once
>>>> compiled, turn into dhd.ko and Si4709_driver.ko.
>>> good, maybe it works but don't boot the rootfs.
>>>> I do not have access via adb.
>>> hmmm that is a problem.
>>>> What should I do next to get replicant working on my device?
>>> I heard that the rootfs and the kernel were tied together in Android,
>>> because the bionic libc was tied to the kenrel you compile
>>> against(trough the kernel headers).
>>> I'm not sure if it's true or still true.
>>>
>>> So try compiling a recovery with your custom kenrel:
>>>  * add the kernel to replicant sources
>>>  * compile the recovery and the kernel together.
>>>
>>> Denis.
>>>
>>
>> I deleted the kernel-aries folder and copied across the one from
>> samsung, renaming it to be the same. I hope this is kind of what you
>> meant? Then I ran:
>>
>> source build/envsetup.sh
>> lunch replicant_galaxysmtd-eng
>> export ANDROID_JAVA_HOME=$JAVA_HOME
>> parallel_tasks=$(echo "$(grep 'processor' /proc/cpuinfo | wc -l ) + 1" | bc)
>> make -j$parallel_tasks bootimage
>>
>> Which created a ramdisk.img at out/target/product/generic/
>>
>> Which I then flashed with heimdall.
>>
>> Now the samsung logo appears and just hangs, but the phone doesn't
>> reboot automatically anymore, not sure if this is progress?
>>
>> Please let me know if I'm on the correct path, or what I should try and
>> do next with it.
> 
> Is adb still not working?
> 
>> _______________________________________________
>> Replicant mailing list
>> Replicant at lists.osuosl.org
>> http://lists.osuosl.org/mailman/listinfo/replicant
> 
> 
> 
No, adb isn't working yet, I get 'device not found'.