I think I have a working bootloader

[Tobias Lange]

Hey guys,

i have been watching this group for a week now and I want to help this
project to succeed.

I have been looking over the 'alch'-branch created by Aleksey.
After a few changes and lots of debugging, I got a version which is
able to find and to read a zImage file.
It is also able to recognise a valid kernel and loads it. It runs
until the very end of the bootloader and then it stops.

I have no idea wether this is from an error in the bootloader or some
files missing on the sd-card.
Does anyone of you know what files need to be present on the card to
start the kernel? (I mean besides the zImage-file)

I'm trying to get write access to the repository, so I can share this
(still very dirty) version with you guys.

Best regards
Tobias Lange

[edwin Fong]

Hi Tobias, if you cant get it to the repository, you compress it in zip/rar file and upload to mediafire or anyother file sharing site :)

[Nuno Marques]

Hold on to your britches ladies and geeks! This might just be the start of something :)

Saudações / Regards
Nuno Marques

[Eoghan Cunningham]

upload the version you have so we can look at it to see who you
figured out the problem. if i had access to the repository i would
upload it there but i think only dopi and Aleksey have full access to
it.

On May 20, 8:44 am, Tobias Lange <s9tsl...@stud.uni-saarland.de>
wrote:

[Tobias Lange]

Ok, I uploaded it on mediafire
http://www.mediafire.com/?xzyvguht1ni
You can compile it yourself or just use my compiled version from the
image folder

[Eoghan Cunningham]

thanks i will look at it later when im on ubuntu when i get home

On May 20, 10:08 am, Tobias Lange <s9tsl...@stud.uni-saarland.de>
wrote:
> Ok, I uploaded it on mediafirehttp://www.mediafire.com/?xzyvguht1ni

[Chris]

Hi all,

I've also flashed the bootloader (alch branch) to my phone.
Although I have some C++ knowledge, low-level programming is an
unknown territory for me.
To make progress, we should maybe share some details what is working
(or not) in each case.
On my Jet the BL seems to have troubles in reading from SD Card:

Debug Output:
[...]
Enabled SD-card LDO
try this kernel()
do_block_init()
SHDC size:
block device init failed
try_this_kernel()
do_block_init()
block device init failed
try_this_kernel()
do_block_init()
block device init failed
try_this_kernel()
do_block_init()
block device init failed
No usable kernel image found

I think the cause is an incorrectly formatted SD card with a bad
kernel here.

Now my questions to all those who have also flashed:

- Does the BL show any SD Card Details to you (SDHC size etc.)?
- Which SD Card are you using? (Sandisk 4GB SDHC)
- How exactly did you format the SD Card? (I created a bootable ext2
and a ext3 partition with the gnome partition editor)
- Which tools did you use for that? (I think the .sh Scripts in the
repo are only useful for the original Qi)
- Which kernel are you using? (I tried a CyanogenMod Kernel because I
couldn't build the JetKernel without errors)

Building the Kernel is also a problem we should probably not
underestimate.
Especially the Kernel configuration has many possible settings.
I think the original Qi is looking for .bin Bootfiles on the SD Card,
I haven't checked yet how dopi has changed that in JetQi.
Well, there are still many problems to solve, but Tobias' news look
promising.

Regards,

Chris

[Tobias Lange]

@Chris
1. Does the BL show any SD Card Details to you?
The version from the alch and the testing branch don't show anything,
because there is no function to output numbers of any kind on the
display.
In my version I added a function that does that. I'm pretty sure that
there is nothing wrong with your card. I had the same problem.
Also there was a bug that prevented the bootloader from going on after
it detected a valid SD-card.

2. Which SD Card are you using?
I'm using a Transcend 16Gb SDHC

3. Which kernel are you using?
Right now I'm trying a self-compiled version of "linux-2.6-samsung"
which I found over the links in the wiki.
But until now, it is just recognised but not started (or at least it
seem like it).

[alfonzobonzo]

I get this if I have NO SD card inserted

On May 20, 10:26 am, Chris <zeeha...@googlemail.com> wrote:

> Debug Output:
> [...]
> Enabled SD-card LDO
> try this kernel()
> do_block_init()
>      SHDC size:
> block device init failed
> try_this_kernel()
> do_block_init()
> block device init failed
> try_this_kernel()
> do_block_init()
> block device init failed
> try_this_kernel()
> do_block_init()
> block device init failed
> No usable kernel image found
>

otherwise I get

> [...]
> Enabled SD-card LDO
> try this kernel()
> do_block_init()

> do_partitions()
Pulling the Kernel
error found:
failed to mount ext2 filesystem
unable to mount ext2 filesystem
try_this_kernel
> do_block_init()
> do_partitions()

[Nuno Marques]

The card IS formated with the right fs, isn't it?

Saudações / Regards
Nuno Marques

[alfonzobonzo]

ext2?

2GB intergral

On May 20, 2:40 pm, Nuno Marques <nmgmarq...@gmail.com> wrote:
> The card IS formated with the right fs, isn't it?
>
> Saudações / Regards
> Nuno Marques
>

[Nuno Marques]

I think there has to be a bootable ext2 partition and a ext3 partition as well.
I remember reading something about that... Can't quite remember when and where though.

Saudações / Regards
Nuno Marques

[Aleksey Cherepanov]

Hi people!

I think that bl may not work with sd cards but work with sdhc.
Because in code types are cared in different ways.
So some tests with both sd and sdhc are needed.

Regards,
Aleksey Cherepanov


2010/5/20, Nuno Marques <nmgma...@gmail.com>:

[alfonzobonzo]

Think your both right maybe

formatted boot partition to ext3

then get

> partition signature missing

On May 20, 3:38 pm, Aleksey Cherepanov <aleksey.4erepa...@gmail.com>
wrote:

> Hi people!
>
> I think that bl may not work with sd cards but work with sdhc.
> Because in code types are cared in different ways.
> So some tests with both sd and sdhc are needed.
>
> Regards,
> Aleksey Cherepanov
>

> 2010/5/20, Nuno Marques <nmgmarq...@gmail.com>:

>
> > I think there has to be a bootable ext2 partition and a ext3 partition as
> > well.
> > I remember reading something about that... Can't quite remember when and
> > where though.
>
> > Saudações / Regards
> > Nuno Marques
>

[Thijs]

Hi Tobias,

Great work!

What's your last debug message? Does loading initramfs succeed or do
you get up to the "Kernel should take over now" message?

---

For everyone wondering how to partition their SD card, check:
http://www.youtube.com/watch?v=xFx2r_n96k0 or follow these steps
(6-13):

(source: http://androidcommunity.com/forums/f9/how-to-create-ext2-partition-14232/)

6. Login to Ubuntu. Now we will need to install the partition editor:
-Go to Applications and click "Add/Remove Programs"
-Search for "Gnome Partition Editor"
-Check the box next to the name and apply the changes
-That will install the partition editor you need.
7. Plug in your microSD to your computer. Click on "System" and pick
"partition editor"
8. From the drop down, select your SD card (probably second option on
there). Make sure you select your SD card and not your hard drive.
Check the size of the partition you are working with because this can
mess up your computer if you format your hard drive instead of the SD
card.
9. Right click on the partition and select "Unmount" then Delete the
existing partition.
10. Create a new partition (FAT32 format) and allocate a certain
amount of space. (I have a 8GB card so I gave it about 6.5 GB)
11. Create a new partition out of the unallocated space (EXT2 format)
and give it the rest of the remaining space (which was about 1.5 GB in
my case). If you did it correctly, you should see two primary
partitions, one as FAT32 with most of the space and one as EXT2 with a
smaller portion of space (depending how much you want to give to each
partition).
12. Apply the changes and it should say it was successful.
13. Close the window then click the top right corner (power icon).
Shut down the computer. Reboot your computer. You are done.
----

Best regards - Thijs


On May 20, 9:44 am, Tobias Lange <s9tsl...@stud.uni-saarland.de>
wrote:

[Thijs]

After partitioning your SD card this should do the trick according to
the Andromnia2 project (download Andromnia2 via
http://rapidshare.com/files/381541433/andromnia2_alpha_pack.zip)

1. unpack files and put zImage, initrd.cpio.gz, default.txt into root
directory of your SD Card (Storage Card)
2. put rootfs.img into root directory of your internal memory (using
TKFileExplorer?)
3. Boot your Jet while holding the magic keys
4. you should see the "JetDroid mode" (debug) messages

This is what we hope for :-)
5. now kernel is booting, many messages and logo are visible.
6. successful booting results in some long-last message and "android"
animation
7. in minute or two you will see desktop

On May 21, 8:47 pm, Thijs <tbress...@gmail.com> wrote:
> Hi Tobias,
>
> Great work!
>
> What's your last debug message? Does loading initramfs succeed or do
> you get up to the "Kernel should take over now" message?
>
> ---
>

> For everyone wondering how to partition their SD card, check:http://www.youtube.com/watch?v=xFx2r_n96k0or follow these steps
> (6-13):
>
> (source:http://androidcommunity.com/forums/f9/how-to-create-ext2-partition-14...)

[Bonsitm]

Wait, does this mean its actually working???

On May 21, 8:13 pm, Thijs <tbress...@gmail.com> wrote:
> After partitioning your SD card this should do the trick according to

> the Andromnia2 project (download Andromnia2 viahttp://rapidshare.com/files/381541433/andromnia2_alpha_pack.zip)

>
> 1. unpack files and put zImage, initrd.cpio.gz, default.txt into root
> directory of your SD Card (Storage Card)
> 2. put rootfs.img into root directory of your internal memory (using
> TKFileExplorer?)
> 3. Boot your Jet while holding the magic keys
> 4. you should see the "JetDroid mode" (debug) messages
>
> This is what we hope for :-)
> 5. now kernel is booting, many messages and logo are visible.
> 6. successful booting results in some long-last message and "android"
> animation
> 7. in minute or two you will see desktop
>
> On May 21, 8:47 pm, Thijs <tbress...@gmail.com> wrote:
>
> > Hi Tobias,
>
> > Great work!
>
> > What's your last debug message? Does loading initramfs succeed or do
> > you get up to the "Kernel should take over now" message?
>
> > ---
>

> > For everyone wondering how to partition their SD card, check:http://www.youtube.com/watch?v=xFx2r_n96k0orfollow these steps

[Chris]

I also had the idea to test the Andromnia Kernel.
The bootloader stops at "Kernel should take over now".
Seems that there are still BL problems in loading the kernel because I
don't think that there are files missing on the SD card.
Same result with other Android Kernel versions.
Do you have the same debug outputs?

Here's the full output:

Initializing baseband...
Enabled SD-card LDO
try_this_kernel()
do_block_init()
do_partitions()
Pulling the kernel
kernel file read
invalid uimage
Size [KiB]: 1733
Kernel recognised
Cmdline:
loglevel=6 rootwait s3cfb.ba
cklight=80 root=/dev/mmcblk1
Starting--->

Kernel should take over now

Regards,

Chris

[Aleksey Cherepanov]

Hi Thijs!

It seems that you found tut about how to start kernel with haret
because default.txt is file specific for it. We also do not have
initrd. And it seems that it is not need because as i understand
android does not require double stage loading. So we need only one
partition that is ext2 with zImage or other type of kernel image
inside.

Regards,
Aleksey Cherepanov


2010/5/21, Chris <zeeh...@googlemail.com>:

[Aleksey Cherepanov]

Hi people!

I am happy that you did progress.

So it would be good to test bl with different environments with
different card types (sd, sdhc) with different partitioning (mbr +
ext2, mbr + ext3, ext2 without mbr (when full card formatted)) with
different image types (zImage and others).

On other hand work is not done and build our own kernel is still needed.
While we do not have kernel it is possible to make test kernel image
with simple app that shows string using bl function LCD_print or other
similar.

And finally sources should be cleaned or even rewrited to be clear and pretty.

Regards,
Aleksey Cherepanov


2010/5/22, Aleksey Cherepanov <aleksey....@gmail.com>:

[Thijs]

Hi Aleksey,

But we do have "initrd.cpio.gz" in the Andromnia2 files.

I think we need to change (in jet.c):
".linux_machine_id = 1626"
into
".linux_machine_id = 1866,"

Furthermore I think we need to change the function
sd_card_block_read_jet() (in jet.c) into:

int sd_card_block_read_jet(unsigned char * buf, unsigned long
start512, int blocks512)

{
unsigned long s3c6410_mmc_bread(int dev_num, unsigned long blknr,
unsigned long blkcnt, void *dst);

return s3c6410_mmc_bread(0, start512, blocks512, buf);
}

And finaly I think we have to remove the line (from jet.c):
.block_init = s3c6410_mmc_init,

Finaly, if all the above doesn't do the trick we might try to add this
line (to jet.c):
.initramfs_filepath = "initrd.cpio.gz",

where it's commented out now... just below " .filepath = "zImage",
--> Please note that this last trick implies you follow the Andromnia2
installation I mentioned earlier!


source:
http://gitorious.org/0xlab-bootloader/qi-bootloader/blobs/5c8f74ac149a48120070254198713f3b5754a744/src/cpu/s3c6410/smdk6410-steppingstone.c


Best regards - Thijs


On May 21, 10:22 pm, Aleksey Cherepanov <aleksey.4erepa...@gmail.com>
wrote:

> Hi Thijs!
>
> It seems that you found tut about how to start kernel with haret
> because default.txt is file specific for it. We also do not have
> initrd. And it seems that it is not need because as i understand
> android does not require double stage loading. So we need only one
> partition that is ext2 with zImage or other type of kernel image
> inside.
>
> Regards,
> Aleksey Cherepanov
>

> 2010/5/21, Chris <zeeha...@googlemail.com>:

[Aleksey Cherepanov]

Hi Thijs!

It sounds very interesting.
Did you try it?
Can you commit your changes into the repo?

Regards,
Aleksey Cherepanov


2010/5/22, Thijs <tbre...@gmail.com>:

[Thijs]

Hi Aleksey,

I didn't try it, and I can't commit the changes into the repo. As my
computer crashed recently I even haven't got the development
environment (for now). So I was just wondering through different code
bases.

Could you (or someone else) give it a try?

best regards - Thijs


On May 21, 11:18 pm, Aleksey Cherepanov <aleksey.4erepa...@gmail.com>
wrote:
> Hi Thijs!
>

> It sounds very interesting.
> Did you try it?
> Can you commit your changes into the repo?
>
> Regards,
> Aleksey Cherepanov
>

> 2010/5/22, Thijs <tbress...@gmail.com>:

>
> > Hi Aleksey,
>
> > But we do have "initrd.cpio.gz" in the Andromnia2 files.
>
> > I think we need to change (in jet.c):
> > ".linux_machine_id = 1626"
> > into
> > ".linux_machine_id = 1866,"
>
> > Furthermore I think we need to change the function
> > sd_card_block_read_jet()  (in jet.c) into:
>
> > int sd_card_block_read_jet(unsigned char * buf, unsigned long
> > start512, int blocks512)
>
> > {
> > unsigned long s3c6410_mmc_bread(int dev_num, unsigned long blknr,
> > unsigned long blkcnt, void *dst);
>
> >         return s3c6410_mmc_bread(0, start512, blocks512, buf);
> > }
>
> > And finaly I think we have to remove the line (from jet.c):
> > .block_init = s3c6410_mmc_init,
>
> > Finaly, if all the above doesn't do the trick we might try to add this
> > line (to jet.c):
> > .initramfs_filepath = "initrd.cpio.gz",
>
> > where it's commented out now... just below " .filepath = "zImage",
> > --> Please note that this last trick implies you follow the Andromnia2
> > installation I mentioned earlier!
>
> > source:

> >http://gitorious.org/0xlab-bootloader/qi-bootloader/blobs/5c8f74ac149...

[Tobias Lange]

Hi everyone,

the entry .initramfs_filepath (jet.c) doesn't mnake any difference.
I added it to try wether it has an effect or not. But if it is
activated it just reads the file, says its ok, and stops at the same
point.
(As far as I know it is also possible to create zImage files that
already contain the initrd)
Right now, I'm trying some stuff with different kernels, but got no
results so far.

I don't think that the reading function for blocks is the problem,
since the results from reading ther kernel oder the initrd are all
correct.

I'm away tomorrow, so I can't do anything until sunday, but perhaps
you come up with some good ideas ;-)

Best regards
Tobias

[viggee]

Let's say we get the kernel to load and start properly...would the
kernel alone (without initramfs and any further programs) be able to
make output on our jet?
Maybe it's a dumb question but what if it's already starting and we
just don't see where it stops?

[Thijs]

Hi All,

Seems really stupid... The andromnia kernel is compiled for the
Marvell PXA 3xx processor. As the Jet has a s3c6410 cpu we will never
get the precompiled Andromnia kernel running on a Jet. Other pre-build
kernel's which are compiled for the s3c6410 don't show any output on
our screens as the video interface probably is incompatible with the
Jet its AMOLED screen.

So if we re-compile the Andromnia kernel for our s3c6410 cpu we might
get some Android type of screens.

Here's how to build the Andromnia kernel for the Marvell PXA 3xx
processor:
http://andromnia.sourceforge.net/wiki/docs/howto_build_linux_kernel

Can rebuilding the Andromnia kernel for our s3c6410 based Jet be the
solution?

best regards - Thijs

[Aleksey Cherepanov]

Hi Thijs!

Try to look at andromnia2 project that is about porting android to i8000.

Regards,
Aleksey Cherepanov


2010/5/22, Thijs <tbre...@gmail.com>:

[Thijs]

Ah, thanks for the rectification. Alfonso already contacted a
developer of the i8000 android project and requested their kernel
sources. Hopefully we can extend these with Jet debug messages to see
where it stops.

best regards - Thijs

On May 22, 3:09 pm, Aleksey Cherepanov <aleksey.4erepa...@gmail.com>
wrote:
> Hi Thijs!
>

> Try to look at andromnia2 project that is about porting android to i8000.
>
> Regards,
> Aleksey Cherepanov
>

> 2010/5/22, Thijs <tbress...@gmail.com>:

[Thijs]

Tobias,

As we pass this parameter to the kernel, is it worth to try to change
this (in jet.c):

".linux_machine_id = 1626"
into
".linux_machine_id = 1866,"

best regards - Thijs

[Chris]

On May 23, 7:38 am, Thijs <tbress...@gmail.com> wrote:
> Tobias,
>
> As we pass this parameter to the kernel, is it worth to try to change
> this (in jet.c):
> ".linux_machine_id = 1626"
> into
> ".linux_machine_id = 1866,"
>

Hi

I've tested your suggestion, there was no significant change at all.
Furthermore I got the same result after some changes in the kernel
command line.
The search for the error continues...

Regards,

Chris

[Thijs]

Hi Chris,

Thanks for trying.. sorry it didn't work.

I've contacted Almar of the i8000 android porting project and
requested their source as well.

Hopefully he posts the i8000 kernel sources soon... adding some debug
messages is probably faster than wild-guessing.

best regards - Thijs

[alfonzobonzo]

I get the same results on my particular SD card, no matter how I
format it. Just tries the steps illustrated in Thijs post, but no
change.

[Eoghan Cunningham]

I was getting the same error today but give it a week are so and we
should have a fully working bl.

[Eoghan Cunningham]

Has anyone got any updates to the bootloader?

p.s. i have emailed samsung to see if they will help us out with this
project hopefully they agree to help and if not i will start a
potition lol

[tux78]

Hey guys,

you did a great job so far. In reference to the current process just
some remarks:

I don't know if you already did, but might it be possible that the SD
just needs some (more) time to initialize? Qi homepage states, using
the "rootdelay=5" command provides some more time for SD to
initialize. Maybe you could try this.
Furthermore I am not sure wether you have to put the correct path to
the kernel as bootcommand (Qi: "root=/dev/mmcblk0p2").

I am not a hardcore linux freak, but maybe these could help to sort
some problems...

Regards,

Seb

[Chris]

Hi Seb,

thanks for the hint, but I've already testet those things in my kernel
command line experiments.
The BL shows the same behavior, doesn't matter which commands you
choose.
I'm checking the code for possible error sources now.

Regards,

Chris

[Eoghan Cunningham]

thanks chris for the update i have been looking at the code for a few
day now and because im new to this im not sure what to look out for
lol but i will figure it out probably when the BL is completed ;-)

p.s. were is dopi it would be great if he had some input to see if he
no's whats wrong.

[Aleksey Cherepanov]

Hi people!

I tried current bootloader with both sd and sdhc card in the same environment.
My results is that with sd card it said that mounting ext2 failed and
that with sdhc card it said "kernel should take over now".

I think problems with sd cards will be solved later.
What do you think about it?

Regards,
Aleksey Cherepanov


2010/5/24, Eoghan Cunningham <eogha...@yahoo.co.uk>:

[alfonzo bonzo]

I don't have an sdhc, but your findings tie-in with my sd card.

[edwin Fong]

Which means, the bootloader is working for SDHC? by the way, Jet did support SDHC?

[alfonzo bonzo]

I think so yes, looking at the specs, i think Jet is sd & sdhd compatible, & upto 16GB

[edwin Fong]

Guess what, just checked minutes ago, i found that i m actually using SDHC since the first day i bought my jet, but didn realise it. -_- till now, i shall test the current bootloader and see the result.

By the way, i have to compile it in a linux environment? I tried but was stucked at 

repo init -u git://android.git.kernel.org/platform/manifest.git -b eclair

It says something like the "repo" is not exist.

[Damir Perisa]

indeed, jet works with 8 gb sdhc for me

[Chris]

Hi,

I've never used a SD card on my Jet, so I can only say that my SDHC
4GB works well with the bootloader.

@edvin:

Copy the repo file into your "android" directory.
After that move into that folder (cd ~/JetDroid/android).

Now use "./repo" instead of "repo" in the following steps.

@Topic:

I think it's time to make a working Kernel for the s3c6410 platform
now.
Otherwise we won't find out whether the BL or the Kernel fails.
But I could't build any of those Jet related Kernels linked in the
Wiki.
They make some trouble when I want to config/make them.
Had anybody of you success with that?

Regards,

Chris

[edwin Fong]

So now it is confirmed to have a working bootloader, the only requirement is to have a sdhc. i think the next development should be on the kernel.

[Nuno Marques]

Wishing you all the best of luck. Can hardly wait in anticipation!

Saudações / Regards
Nuno Marques

[alfonzobonzo]

we "should" have the i8000 (Samsung S3C6410 ARM 1176 800MHz processor)
source from Almar (MoDaCo) in a couple of days. that would be a nice
starting point.

On May 24, 4:01 pm, edwin Fong <edwu...@gmail.com> wrote:
> So now it is confirmed to have a working bootloader, the only requirement is
> to have a sdhc. i think the next development should be on the kernel.
>

[Peter Jaško]

So the bootloader IS WORKING?

IF YES: only with SDHC?

2010/5/24 alfonzobonzo <bonzoa...@gmail.com>

[alfonzobonzo]

the bootloader progresses further with sdhc then it does with sd. I
cant say if it is 100% working with sdhc or not. I'm not sure we'll
find out till we have a kernel to run with it. hope this makes sense.

On May 24, 4:57 pm, Peter Jaško <electro...@gmail.com> wrote:
> So the bootloader IS WORKING?
> IF YES: only with SDHC?
>

> 2010/5/24 alfonzobonzo <bonzoalfo...@gmail.com>

[Peter Jaško]

So we are officialy starting to build the kernel?

2010/5/24 alfonzobonzo <bonzoa...@gmail.com>

[Peter Jaško]

And BTW it makes sense ;) 

2010/5/24 Peter Jaško <elect...@gmail.com>

[Thijs]

Hi guys,

Ok, SDHC it will be then.

Almar of the i8000 android port thinks they'll have sound working
within 2 days. Then he will put their sources in some git.
Furthermore, he have me 2 hints worth trying:

1. Change the following line in jet.c for all 4 configurations:
.linux_mem_size = (128 * 1024 * 1024),
into
.linux_mem_size = (64 * 1024 * 1024),

2. Try to boot the i8000 kernel binary from internal SD (just re-
partition approx. 512 Mb of your internal SD memory to ext3). This
implies that our bootloader supports ext3, which I believe, isn't the
case right now. ----> CAUTION: I don't know the risks of re-
partitioning your internal SD memory ---> ONLY FOR EXPERTS!

Note: Looking at his last hint it seems their kernel (only?) supports
ext3 while our bootloader only supports ext2... maybe that's a clue?

Best regards - Thijs

On May 24, 6:49 pm, Peter Jaško <electro...@gmail.com> wrote:
> And BTW it makes sense ;)
>

> 2010/5/24 Peter Jaško <electro...@gmail.com>

>
> > So we are officialy starting to build the kernel?
>

> > 2010/5/24 alfonzobonzo <bonzoalfo...@gmail.com>

[Flv]

Just a question. Is it not possible to load the i5700 versions of
Android with the bootloader? Does it exist a source version of it? It
has the same hardware of the S8000 I think with the less differences
possible.Or eventually the S3C6410 opened ported version of Android
for that developmetn board we see on youtube?

Isnt worth to force it in some way considering it should be already
optimized for s3c6410?

[Aleksey Cherepanov]

Hi people!

I suggest to make a little example to check bootloader completness.
I see it as a binary blob inserted into some existing zImage and
triing to boot it.
I tried something but it seems that i know not enough about it to do fast.
Other variant is to build new image from sources. But it should be a
kernel only a little sample.
Do you have any other fast solution?

Regards,
Aleksey Cherepanov


2010/5/24, Flv <flvl...@gmail.com>:

[Chris]

Hi, good news my friends:

I've extracted the zImage out of the Spica Firmware and the BL seems
to load it.
The screen shows some random distortions and turns off (no idea if the
phone is shutting down, too...).
I'll check if some boot commands can change that, but i think the
wrong display driver is the cause of the problem.

Regards,

Chris

[cedricm]

wow, that's really good news! good work

[Bonsitm]

Amazing! Keep at it!

[Chris]

Hi,

i think the bootloader is working now (I hope that I can say the same
when we have a suitable kernel image...).
After the screen shows distortions (for 3 seconds) the phone turns
off.
Maybe I'll upload a photo of it if you want.


@Aleksey: It would be nice if you could upload my modified jet.c to
Github. :) http://www.2shared.com/file/zpxaceJa/jet.html


Regards,

Chris

[Flv]

I knew it could be the right start!!! Spica share pratically the same
hardware and PROBABLY it's already optimized for the s3c6410 as much
as it would not be possible to do ourself.
Make your effort on this I think it's the right start!!

[Flv]

What about this

http://files.samdroid.net/files/i5700-LkMod/i5700-PDA_zImage-LK10.rar

[Chris]

Hi flv,

i'm playing around with a Samsung Moment Kernel now.
Seems to be the better base for experiments.
I even get a little loading bar before the phone turns off. :)

Regards,

Chris

[Aleksey Cherepanov]

Hi Chris!

I pushed your file into the repo.
It also seems that i pushed all changes from alch branch into testing branch.

What is your github accaunt name?
Dopi needs it to grant you write access.

Regards,
Aleksey Cherepanov

2010/5/25, Chris <zeeh...@googlemail.com>:

[alfonzobonzo]

[URL=http://s66.photobucket.com/albums/h268/alfonzobonzo/JetDroid/?
action=view&current=2010-05-2521-10-29945.flv][IMG]http://
i66.photobucket.com/albums/h268/alfonzobonzo/JetDroid/
th_2010-05-2521-10-29945.jpg[/IMG][/URL]

[dacot]

This is GGGGGreat, only a matter of time now ya think, you guys ar
doing an amazing job. is there any chance someone could put a video up
to show how to test and do this? or when its all done. isit easy to
get back to ur own firmware after testing?

> > > Chris- Hide quoted text -
>
> - Show quoted text -

[Aleksey Cherepanov]

Hi people!

May be i8000's kernel was working long without turning off because it
is good for us but we cannot see something. May be adding a proper
video driver will change situation. Or may be it is possible to build
kernel with support lan over usb to talk with loaded linux over usb.

Any thoughts?

Regards,
Aleksey Cherepanov

2010/5/26, dacot <davey1...@aol.com>:
> Thanks for the video.
> (music) its coming on. its coming on. its coming on. its coming on....
> it's <nearly> there.

>
> On May 25, 9:15 pm, alfonzobonzo <bonzoalfo...@gmail.com> wrote:

[edwin Fong]

How sure are u the i8000 kernel is working? i mean it was running in the background when there are no output from the screen.

[Flv]

I think that the best kernel would be the one of the SHW-M100S model
coming out... and actually watching at that phone I understand why
Samsung would not ever give us an hand for this project....

anyway I'm searching for some kernel but it's quiet a new phone.

[Flv]

Found something very intersting!!!!

http://randomtechinfo.com/Moment/SHW-M100S_SHW-M100SDB19_DB19_SHW-M100SDB18_DB18_SHW-M100SDB17_DB17_SHW-M100SDB17_DB17_KR_SKT.zip

GREAT! That's the TAR file

and these are diveded...

http://www.joeyconway.com/sdx/android2.1/m100/M100-a2.1-s-Ze10.2-k.tar
http://www.joeyconway.com/sdx/android2.1/m100/M100-a2.1-s.tar
http://www.joeyconway.com/sdx/android2.1/m100/M100-a2.1-sk.tar
http://www.joeyconway.com/sdx/android2.1/m100/M100-a2.1-sm-Ze10.2-k.tar
http://www.joeyconway.com/sdx/android2.1/m100/M100-a2.1-k.tar
http://www.joeyconway.com/sdx/android2.1/m100/M100-a2.1-m.tar

From modaco.com

This is Android 2.1 in Korean for the Samsung m100.

The main .tar file which can be downloaded here -
http://randomtechinfo.com/Moment/SHW-M100S_SHW-M100SDB19_DB19_SHW-M100SDB18_DB18_SHW-M100SDB17_DB17_SHW-M100SDB17_DB17_KR_SKT.zip

contains 4 files, modem.bin, ramdisk.img, system.rfs and zImage.img.
A few different methods can be used to test flashing this file.

A few different variations of the files to test flashing - report back
following the posting guide below:
Flash the .tar posted above with everything in it, exactly how we
received it, using the Sprint Update Tool
M100 Android 2.1 System and Ze10.2 (Android 2.*) Dev Kernel - M100-
a2.1-s-Ze10.2-k.tar
M100 Android 2.1 System Only - M100-a2.1-s.tar
M100 Android 2.1 System and Kernel - M100-a2.1-sk.tar
M100 Android 2.1 System and modem along with Ze10.2 (Android 2.*) Dev
Kernel - M100-a2.1-sm-Ze10.2-k.tarr
M100 Kernel Only - M100-a2.1-k.tar
M100 Modem Only - M100-a2.1-m.tar

[Flv]

And this is the packed firmware version I think

http://rs915.rapidshare.com/files/365069283/SHW-M100S_SHW-M100SDB19_DB19_SHW-M100SDB18_DB18_SHW-M100SDB17_DB17_SHW-M100SDB17_DB17_KR_SKT.zip

This phone has got VERY similar hw packing a 800Mhz S3C6410 and most
important I think driving an AMOLED screen! That probably could be one
of the many reasons Spica firmware driving an LCD one cannot show
anything on Jetdroid.
I bet that's the right direction in wich we should test.

COME ON GUYS! :)

[edwin Fong]

Fly, maybe you can test yourself about this? since the bootloader is booting well (it seems).

[cedricm]

yes indeed, i think the SHW-M100S would be a great starting point but
the source isn't available yet on the samsung open source site and
that's why i didn't kept looking further but it looks like you found
the right files...

it's indeed very similiar to the jet hardware imo

i've taken a look at the system.rfs (posted that one under comments in
the JetHardware google project page) and saw that even the camera
could be the same module as of the jet...

On May 26, 8:46 am, Flv <flvlo...@gmail.com> wrote:
> And this is the packed firmware version I think
>

> http://rs915.rapidshare.com/files/365069283/SHW-M100S_SHW-M100SDB19_D...

[Flv]

Yeah if only I get to find my damn micro usb cable cause I've lost it
and have to buy another, damn it...

Anyway, I definitealy will.

[Flv]

I feel it's the right direction even more. I'm searching for service
tech paper to understand more deeply both hardware but it's new phone
and it's difficult. Anyway watching at the files should give us good
info about it and in my opinion it's called Galaxy A this phone but
start from the Jet idea hardware from Samsung mind.

[edwin Fong]

Since the next step is to find a suitable kernel, how about someone upload a "working" jetdroid bootloader to any file sharing site? There are at least more people able to help in testing kernels now. Im still not able to compile the bootloader :( , im using a sdhc and i like to help.

[Chris]

Hi,

@edwin: I think that's a legal problem. If I remember correctly Dopi
once said something about that.

I'll take a look at the M100S files.
The problem is, that those .rfs files are often encrypted somehow.
But as soon as this phone is released, we'll also have the Kernel
source at Samsungs Open Source page.

Regards,

Chris

[David Ramos]

Hello.
At this moment I can not test this kernel because I have the
bootloader loaded or SDHC card I have a ext3 format.
I upload these kernel:
- It is the official kernel Moment samsung M900 has AMOLED screen and
800Mhz CPU, varies the modem. http://www.mediafire.com/?mfjd2tnu5tq
- Unofficial upload a modified kernel to see if more luck:
http://www.mediafire.com/?mwnmemz1fmz

Someone could upload the bootlader? And is compatible with standard SD
cards?

[Flv]

Regarding the modem, probably if these phone has got 3.6mps thourghput
it could be the same baseband MSM6246 by Qualcomm or in 7.2mpbs
version it could be the MSM6296 or something like this.

I don't know about the Galaxy A if it has the first or the second one
but probably regardin drivers it could be similars in both kernel
version (or not?).

On May 26, 11:59 am, David Ramos <atomizas...@gmail.com> wrote:
> Hello.
> At this moment I can not test this kernel because I have the
> bootloader loaded or SDHC card I have a ext3 format.
> I upload these kernel:
> - It is the official kernel Moment samsung M900 has AMOLED screen and

> 800Mhz CPU, varies the modem.http://www.mediafire.com/?mfjd2tnu5tq

[Aleksey Cherepanov]

Hi David!

It is not possible to share the bootloader due to copyright problems.
They can be bypassed if we would share binary noncontext patch for
original bootloader.

Bootloader currently is not compatible with sd cards. It is
complatible only with sdhc cards.

Regards,
Aleksey Cherepanov

2010/5/26, David Ramos <atomi...@gmail.com>:

[Flv]

I've got a 16Gb SDHC card on my Jet and think I could try something if
once uploaded the bootloader I can choose anyway to use the phone with
normal os everyday.

On May 26, 12:15 pm, Aleksey Cherepanov <aleksey.4erepa...@gmail.com>
wrote:

> Hi David!
>
> It is not possible to share the bootloader due to copyright problems.
> They can be bypassed if we would share binary noncontext patch for
> original bootloader.
>
> Bootloader currently is not compatible with sd cards. It is
> complatible only with sdhc cards.
>
> Regards,
> Aleksey Cherepanov
>

> 2010/5/26, David Ramos <atomizas...@gmail.com>:

>
>
>
>
>
> > Hello.
> > At this moment I can not test this kernel because I have the
> > bootloader loaded or SDHC card I have a ext3 format.
> > I upload these kernel:
> > - It is the official kernel Moment samsung M900 has AMOLED screen and

> > 800Mhz CPU, varies the modem.http://www.mediafire.com/?mfjd2tnu5tq

[cedricm]

why don't you just mail the compiled bootloader to eachother, i don't
see the problem there actually... as long as you don't put it in a
public place...

[viggee]

I have just tested those kernels.
The not modified kernel shows somw graphical glitching and after that
a loading bar for a couple of seconds. Then the phone turns off.
The modified version does practicly the same thing except that it
doesnt turn off. But still you can only see the progressbar
progressing ;)

On 26 Mai, 11:59, David Ramos <atomizas...@gmail.com> wrote:
> Hello.
> At this moment I can not test this kernel because I have the
> bootloader loaded or SDHC card I have a ext3 format.
> I upload these kernel:
> - It is the official kernel Moment samsung M900 has AMOLED screen and

> 800Mhz CPU, varies the modem.http://www.mediafire.com/?mfjd2tnu5tq

[Nuno Marques]

I agree with cedricm. Just email it to one another. The more people that have it and can test it, the better. We went from a single developer and over 3 months of almost no progress (no disrespect intended, pretty sure he has a lot to do besides this project) to having quite a few, completing the boot loader and having some mild success with loading a kernel in under a week. The more people we get on this thing, the higher the chances are for success, and in less time too.

That's just my "two cents" worth!

Saudações / Regards
Nuno Marques

[Martin B.]

Is it possible to use the BL with any Firmware? I've got POJB2, and if
yes please mail me the files to flash...

[Flv]

Did you test them all?

[edwin Fong]

Please mail me the bootloader, i badly need it for kernel testing :)

[Thijs]

Hi,

More good news. Almar of the i8000 Android project just mailed me. He
figured out what the problem of the non-working i8000 kernel is. He'll
implement some fixes and will share the complete i8000 Android kernel
source within a few days!

If I read the links below, I've got the feeling this i8000 Android
kernel is the perfect start:
http://code.google.com/p/jetdroid/wiki/JetKernel
http://code.google.com/p/jetdroid/wiki/JetHardware
http://code.google.com/p/jetdroid/wiki/S3C6410Hardware

best regards - Thijs

On May 26, 2:20 pm, edwin Fong <edwu...@gmail.com> wrote:
> Please mail me the bootloader, i badly need it for kernel testing :)
>

[Flv]

I would say that surely from an "already patched work" it would be a
good start but from where the i8000 started? It was already an S3C6410
version of it? What's android-s3c6410 already existing phones is based
the project on? I supposed that it could be based on some generic
s3c6410 version that could remain at an exercise level considering the
final result. We shoud hope in some sort of "lucky" alread present
optmization that should make us solve many many hardware issue like
the main use of the 2D acceleration, the baseband modem, the power
management.. etc...

And the only way could be work on something that share the same
hardware and that was optimized and compiled by Samsung.
Don't we?

On May 26, 2:54 pm, Thijs <tbress...@gmail.com> wrote:
> Hi,
>
> More good news. Almar of the i8000 Android project just mailed me. He
> figured out what the problem of the non-working i8000 kernel is. He'll
> implement some fixes and will share the complete i8000 Android kernel
> source within a few days!
>
> If I read the links below, I've got the feeling this i8000 Android

> kernel is the perfect start:http://code.google.com/p/jetdroid/wiki/JetKernelhttp://code.google.com/p/jetdroid/wiki/JetHardwarehttp://code.google.com/p/jetdroid/wiki/S3C6410Hardware

[Martin B.]

Yeah, but its nice for testing the bootloader if it's working 100%..

On 26 Mai, 15:15, Flv <flvlo...@gmail.com> wrote:
> I would say that surely from an "already patched work" it would be a
> good start but from where the i8000 started? It was already an S3C6410
> version of it? What's android-s3c6410 already existing phones is based
> the project on? I supposed that it could be based on some generic
> s3c6410 version that could remain at an exercise level considering the
> final result. We shoud hope in some sort of "lucky" alread present
> optmization that should make us solve many many hardware issue like
> the main use of the 2D acceleration, the baseband modem, the power
> management.. etc...
>
> And the only way could be work on something that share the same
> hardware and that was optimized and compiled by Samsung.
> Don't we?
>
> On May 26, 2:54 pm, Thijs <tbress...@gmail.com> wrote:
>
> > Hi,
>
> > More good news. Almar of the i8000 Android project just mailed me. He
> > figured out what the problem of the non-working i8000 kernel is. He'll
> > implement some fixes and will share the complete i8000 Android kernel
> > source within a few days!
>
> > If I read the links below, I've got the feeling this i8000 Android

> > kernel is the perfect start:http://code.google.com/p/jetdroid/wiki/JetKernelhttp://code.google.co...

[viggee]

I was actually talking about the m900 kernel.
But right now I am testing the ones you posted.
So far the same results, graphical glitching and a loading bar, that
loads all the way to the end...then the phone crashes or whatever,
nothings happening, i have to take out the battery.

[Thijs]

Did you try and check the following link?

http://code.google.com/p/jetdroid/wiki/S3C6410Hardware

What hardware (cpu, screen, memory, ...) is used in each phone? What
are the differences & commonalities? Which kernel sources are
available? Where can we find them?

Who can supply us such an overview?

best regards - Thijs

On May 26, 3:15 pm, Flv <flvlo...@gmail.com> wrote:
> I would say that surely from an "already patched work" it would be a
> good start but from where the i8000 started? It was already an S3C6410
> version of it? What's android-s3c6410 already existing phones is based
> the project on? I supposed that it could be based on some generic
> s3c6410 version that could remain at an exercise level considering the
> final result. We shoud hope in some sort of "lucky" alread present
> optmization that should make us solve many many hardware issue like
> the main use of the 2D acceleration, the baseband modem, the power
> management.. etc...
>
> And the only way could be work on something that share the same
> hardware and that was optimized and compiled by Samsung.
> Don't we?
>
> On May 26, 2:54 pm, Thijs <tbress...@gmail.com> wrote:
>
> > Hi,
>
> > More good news. Almar of the i8000 Android project just mailed me. He
> > figured out what the problem of the non-working i8000 kernel is. He'll
> > implement some fixes and will share the complete i8000 Android kernel
> > source within a few days!
>
> > If I read the links below, I've got the feeling this i8000 Android

> > kernel is the perfect start:http://code.google.com/p/jetdroid/wiki/JetKernelhttp://code.google.co...