yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] Fr4gg0r:
I tried it, but there's no /dev/ubi0_0, only /dev/ubi0..

mounting /dev/ubi0 results in an error.

(maybe I shoud first learn what all those commands do :rolleyes:)
[Galaxy S I9000 Q&A, Help & Troubleshooting] FPRobber:
ubiformat - formats empty flash, erases flash and preserves erase counters, flashes UBI images to MTD devices

Seems like you are erasing the whole image.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Jeshter2000:
Well supercurio is on it too so dont worry . All be good .... Lol ...

Sent from my Intergalactic Supah Dupah Spaceship¡¡!!!
[Galaxy S I9000 Q&A, Help & Troubleshooting] AbuYahya:
It may be worth asking the wider community in the general android hacking/develpoment section!
[Galaxy S I9000 Q&A, Help & Troubleshooting] nCoder:
Good point! :)
[Galaxy S I9000 Q&A, Help & Troubleshooting] nCoder:
some info found in http://www.linux-mtd.infradead.org/faq/ubifs.html

"How do I mount UBIFS?

The modern way of mounting UBIFS is mounting UBI volume character device nodes, e.g.:

$ mount -t ubifs /dev/ubi0_0 /mnt/ubifs

will mount UBIFS to UBI volume 0 on UBI device 0. This is the easiest way to mount UBIFS, but it is supported only in kernels starting from version 2.6.32. The UBIFS back-port trees (see here) also support this mounting method.

The old method is to use device-less mount, just like procfs or sysfs. The volume to mount is specified using ubiX_Y or ubiX:NAME syntax, where

X - UBI device number;

Y - UBI volume number;

NAME - UBI volume name.

For example,

$ mount -t ubifs ubi1_0 /mnt/ubifs

mounts volume 0 on UBI device 1 to /mnt/ubifs, and

$ mount -t ubifs ubi0:rootfs /mnt/ubifs

mounts "rootfs" volume of UBI device 0 to /mnt/ubifs ("rootfs" is volume name). This method of specifying UBI volume is more preferable because it does not depend on volume number.

Note, if X is not specified, UBIFS assumes 0, i.e., "ubi0:rootfs" and "ubi:rootfs" are equivalent.

Some environments like busybox are confused by the ":" delimiter (e.g., ubi:rootfs) and "!" may be used instead (e.g., ubi!rootfs).

In order to mount UBIFS as the root file system, you have to compile UBIFS into the kernel (instead of compiling it as a kernel module) and specify proper kernel boot arguments and make the kernel mount UBIFS on boot. You have to provide the boot arguments to attach the UBI device (using the ubi.mtd= argument, see here). Then you should tell the kernel the file system type by providing the rootfstype= argument. And finally, you should specify which UBI volume has to be mounted on boot using the root= argument. The volume is specified the same way as described above (ubiX_Y or ubiX:NAME).

The following is an example of the kernel boot arguments to attach mtd0 to UBI and mount UBI volume "rootfs":

ubi.mtd=0 root=ubi0:rootfs rootfstype=ubifs"
[Galaxy S I9000 Q&A, Help & Troubleshooting] nCoder:
using a hex editor you can find "mount -t ubifs.1" ...
[Galaxy S I9000 Q&A, Help & Troubleshooting] nCoder:
Another interesting one... :P

"How do I extract files from an UBI/UBIFS image?

Unfortunately, at the moment there are no user-space tools which can unwrap UBI and UBIFS images. UBIFS cannot be loop-back mounted as well, because it does not work with block devices.

However, there is a hacky way to unwrap UBI/UBIFS images. But you have to make sure you have UBIFS support in your host machine. UBIFS is a relatively new file system and is not supported by all Linux distributions. But at least Fedora 11 does include it.

Let's consider a simple example. Suppose you have an ubi.img file. This is an UBI image, which contains a single UBI volume, which in turn contains UBIFS file-system. In other words, this is an image which was created using the mkfs.ubifs and ubinize tools, just like it is described in this section (the image is created for a 256MiB NAND flash with 2KiB NAND page size and which supports sub-pages). Here is what you can do:

# Create an 256MiB emulated NAND flash with 2KiB NAND page size

# (you should see the new MTD device in /proc/mtd)

modprobe nandsim first_id_byte=0x20 second_id_byte=0xaa \

third_id_byte=0x00 fourth_id_byte=0x15

# MTD is not LDM-enabled and udev does not create device

# MTD device nodes automatically, so create /dev/mtd0

# (we assume that you do not have other MTD devices)

mknod /dev/mtd0 c 90 0

# Copy the contents of your image to the emulated MTD device

dd if=ubi.img of=/dev/mtd0 bs=2048

# Load UBI module and attach mtd0

modprobe ubi mtd=0

# Mount UBIFS

mount -t ubifs /dev/ubi0_0 /mnt/ubifs

Now you have the file-system in /mnt/ubifs. Use the following to get rid of it:

umount /mnt/ubifs

rmmod ubifs ubi nandsim"
[Galaxy S I9000 Q&A, Help & Troubleshooting] ale0crysis:
Lol it seems we do ask first to SamFirmwares how open it :D:rolleyes:
[Galaxy S I9000 Q&A, Help & Troubleshooting] nCoder:
Extract and rebuild a UBI image Customize Rom:

http://www.chinadigitalcomm.com/android-a81/extract-and-rebuild-a-ubi-image-customize-rom-t1501.html
[Galaxy S I9000 Q&A, Help & Troubleshooting] nCoder:
You assume they know how to open it :)

They stated this rom is still RFS :)

We already found these are UBI images ;)
[Galaxy S I9000 Q&A, Help & Troubleshooting] Fr4gg0r:
That are exactly the same instructions as in the already posted link.

They do not work.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Richthofen:
My my ;)

So Mr "Fraser" is finally here.

S5PC110 AP

PowerVR SGX540

800x480

But who said anything about Android?

Good night :p
[Galaxy S I9000 Q&A, Help & Troubleshooting] nCoder:
Great news then for our Galaxy S!!!! :D

There are a lot of Android references everywhere in the image files. Everything points to Android being inside, of course ;)

(unless BADA uses some Android code)
[Galaxy S I9000 Q&A, Help & Troubleshooting] exstatica:
Here is a mirror

http://mirrors.mednor.net/Android/Devices/SamsungG2/I9200XXJP2.rar

:)
[Galaxy S I9000 Q&A, Help & Troubleshooting] sac23:
hey anyone know the password to rar
[Galaxy S I9000 Q&A, Help & Troubleshooting] nCoder:
samfirmware.com
[Galaxy S I9000 Q&A, Help & Troubleshooting] Aery:
It seems that's not a "normal" ubi image. Tried everything possible to extract it.

Could be a multi image with some ubifs and maybe some btrfs content?

Binarysplit?
[Galaxy S I9000 Q&A, Help & Troubleshooting] KCutrer1:
That means what exactly? In terms of actually getting at the files inside
[Galaxy S I9000 Q&A, Help & Troubleshooting] luniz7:
10 char...
[Galaxy S I9000 Q&A, Help & Troubleshooting] rajendra82:
How do we go about finding where to do binary splits? Has anyone tried to build a "normal" ubi.img containing some fake data, and see if they start with a header and have some size information embedded inside. May be we can go that route and see where the splits are.
[Galaxy S I9000 Q&A, Help & Troubleshooting] cnn888:
what good does it do to galaxy s? can it be installed on galaxy s?
[Galaxy S I9000 Q&A, Help & Troubleshooting] rajendra82:
Nothing and no. Now let us solve this ubi.img puzzle.
[Galaxy S I9000 Q&A, Help & Troubleshooting] somberi:
MeeGo??? :D lol

Coz N900 uses UBIFS :rolleyes:
[Galaxy S I9000 Q&A, Help & Troubleshooting] GwynBleidd:
Just in case this hasn't been mentioned before...

http://www.linux-mtd.infradead.org/doc/ubifs.html
[Galaxy S I9000 Q&A, Help & Troubleshooting] xHausx:
That only creates a volume of 252MB, the image is 300 something MBs

"dd: writing `/dev/mtd0': No space left on device"

I started snooping through the image and found some interesting stuff. It appears this is for a GSM, and possibly a CDMA, phone and then there is this

"[PLATFORM_INFO]

platform_name = vita;"

I don't think this is gingerbread
[Galaxy S I9000 Q&A, Help & Troubleshooting] nCoder:
:confused: SamFirmware and Richthofen sugest this is may not be Android... :(

I don't know if android code also includes any reference to Linux...

Reference inside to a "SAMSUNG LINUX PLATFORM" and several "linux"... This could be LIMO like the Vodafone H1 (Samsung).

ubi.img has a lot of references to "Android" inside as well.

:confused:
[Galaxy S I9000 Q&A, Help & Troubleshooting] rajendra82:
There are ways to create bigger emulated NANDs by changing the four ID values. Google nandsim.
[Galaxy S I9000 Q&A, Help & Troubleshooting] GwynBleidd:
http://www.unwiredview.com/2010/01/21/samsung-files-for-vita-os-trademark-another-mobile-os/
[Galaxy S I9000 Q&A, Help & Troubleshooting] FPRobber:
It's definitely Android:

"/usr/lib/android/system/app"
[Galaxy S I9000 Q&A, Help & Troubleshooting] xda_101:
Some Images from ubi.img....

Also, unable to extract the ubi image...

Had a snoop through the image file...

managed to extract all PNG images..

LINK:hotfile.com/dl/83808710/985a052/UBI_IMG_Extract.zip.html

It doesn't seem to be gingerbread...
[Galaxy S I9000 Q&A, Help & Troubleshooting] redbull320:
Boring ;(
[Galaxy S I9000 Q&A, Help & Troubleshooting] Rawat:
I think SamFirmware found that out from here. Wouldn't trust them :rolleyes:
[Galaxy S I9000 Q&A, Help & Troubleshooting] nCoder:
Still some hope thogh ;)
[Galaxy S I9000 Q&A, Help & Troubleshooting] nCoder:
This is my assumption as well.	Lots of references to android inside.
[Galaxy S I9000 Q&A, Help & Troubleshooting] StDevious:
WTF ! Pulling our leg or you seriously have something on you ? :D
[Galaxy S I9000 Q&A, Help & Troubleshooting] mickeko:
Crack the code and find a text saying "NOTHING TO SEE HERE, CIRCULATE!" ;)
[Galaxy S I9000 Q&A, Help & Troubleshooting] xHausx:
Yeah, it's Debian based and if it's not Android it definitely borrows a lot from it. It seems to be sharing the same framework and everything just under a different name.

Hell I even saw some HTC RIL drivers in there lol
[Galaxy S I9000 Q&A, Help & Troubleshooting] TrueNix:
Could it be Meego or Bada?
[Galaxy S I9000 Q&A, Help & Troubleshooting] ale0crysis:
It's definetely Android :cool:
[Galaxy S I9000 Q&A, Help & Troubleshooting] SupremeBeaver:
the wait is killing me! someone give me an answer!
[Galaxy S I9000 Q&A, Help & Troubleshooting] bcpk:
Google results for Samsung Vita.. http://www.ubergizmo.com/15/archives/2010/01/is_samsung_vita_os_related_to_its_bada_os.html
[Galaxy S I9000 Q&A, Help & Troubleshooting] ircfox:
this can be nice :D
[Galaxy S I9000 Q&A, Help & Troubleshooting] modest_mandroid:
Use this instead of the one in the file:

'modprobe nandsim first_id_byte=0x20 second_id_byte=0xac third_id_byte=0x00 fourth_id_byte=0x15'

It should create a vol of 512mb
[Galaxy S I9000 Q&A, Help & Troubleshooting] codeworkx:
modprobe nandsim first_id_byte=0xec second_id_byte=0xd3 third_id_byte=0x51 fourth_id_byte=0x95

>> 1024 MB

You cannot mount it as ubifs. We've tried it all.
[Galaxy S I9000 Q&A, Help & Troubleshooting] richiehd:
does this help anyone?

http://permalink.gmane.org/gmane.comp.lib.uclibc.buildroot/20984

that talks about converting ubifs to r(oot)fs [is that samsungs rfs?]

i googled, i dont know code. if they are totally unrelated im sorry. :p
[Galaxy S I9000 Q&A, Help & Troubleshooting] modest_mandroid:
Seems to be a relatively new build:

[Version]

Major=I9200XXJK-20101103;

Minor=pre1;

Order=;

[Build]

Date=2010.11.03;

Time=16:30:15;

It's definitely android (though what version, I'm not sure at this point), seems to be 800x480 resolution, or at least that's what all the evidence seems to point towards:

742314 Network=True

742315 Visible=FalJ

742316 _layout_width=480+T

742317 height=800

742318 Is_horizontal_scaX

742319 Comment

742320 ML Data '5

742321 syncml-ds.desktop

742322 %Name=Android Market

I found the ringtones.. good news, they still have this one ;]

4024170 Bollywood.ogg

So much for these leaked specs?

http://www.unwiredview.com/2010/07/05/samsung-i9200-galaxy-s2-details-leak/

Update:

[SUID]

93 su = ssx root.root

94 sulogin = sxx root.root

95 busybox.conf

wtf is this, pre-installed busybox?

Also, probably just garbage, but this one had me laughing - I really hope the devs aren't porning it up on these test devices:

321 nsfw-hL/

This is also odd - notice the SGH-i7800 in there:

8560 system.info

8561 [PLATFORM_INFO]

8562 platform_name = vita;

8563 SGH-i7800;
[Galaxy S I9000 Q&A, Help & Troubleshooting] MrNameless:
password for the .rar ?
[Galaxy S I9000 Q&A, Help & Troubleshooting] modest_mandroid:
samfirmware.com
[Galaxy S I9000 Q&A, Help & Troubleshooting] FPRobber:
Since the error that stops us from mounting the image is that the data offset isn't 6144 I opened the ubi.img in a hexeditor and the data really was at 8192. I tried just removing the FF padding between 6144 and 8192. Now the data was at 6144, exactly what ubiattach is expecting, but it's still complaining "UBI error: validate_ec_hdr: bad data offset 8192, expected 6144". I guess the data offset is set somewhere in the header, does anyone know where? :confused:

Okay, I found the header in the ubi source:

struct ubi_ec_hdr {
__be32 magic;
__u8 version;
__u8 padding1[3];
__be64 ec; /* Warning: the current limit is 31-bit anyway! */
__be32 vid_hdr_offset;
__be32 data_offset;
__be32 image_seq;
__u8 padding2[32];
__be32 hdr_crc;
} __attribute__ ((packed));

So the data offset should be at 4096(header offset)+20 bytes=4116, but all there is, is "00 00 00 00". I'll try replacing it with 00 00 18 00 (can someone confirm that this is 6144?

Oops, that's the wrong header struct.

struct ubi_vid_hdr {
__be32 magic;
__u8 version;
__u8 vol_type;
__u8 copy_flag;
__u8 compat;
__be32 vol_id;
__be32 lnum;
__u8 padding1[4];
__be32 data_size;
__be32 used_ebs;
__be32 data_pad;
__be32 data_crc;
__u8 padding2[4];
__be64 sqnum;
__u8 padding3[12];
__be32 hdr_crc;
} __attribute__ ((packed));

That doesn't help me at all though.

Edit:

The EC header starts at 0 and has the data offset set to 8196 :D

Edit:

I got it to mount!!

Too bad it's completely empty. I'm out of ideas. :(

Edit:

At least I got an error.

[26453.907053] UBI warning: process_eb: valid VID header but corrupted EC header at PEB 0
[26453.951087] UBI warning: ubi_scan: 1333 PEBs are corrupted
[26453.951089] corrupted PEBs are: 25 27 29 31....and many more...
[Galaxy S I9000 Q&A, Help & Troubleshooting] nCoder:
What if this is Honeycomb? (Android 3.0) as referred in the articles?

It's been in development and is supposed to be released in 2011. It's a PRE built - i.e. not even alfa version.

I suppose Samsung, HTC and others already have PRE releases of Honeycomb already.

this is speculation of course, but definitely we can see some .apk's and a lot of android in the file system contents
[Galaxy S I9000 Q&A, Help & Troubleshooting] modest_mandroid:
I was under the impression that honeycomb was a tablet only thing? At least that's the impression I got from all the tech blogs.

Would be a nice surprise if it turned out to be an all-inclusive thing though.
[Galaxy S I9000 Q&A, Help & Troubleshooting] StDevious:
Is that an android ringtone ? Because if not then it might be a verizon thing because I have it on my droid x too
[Galaxy S I9000 Q&A, Help & Troubleshooting] modest_mandroid:
Yeah, it's some stock android ringtone. I have it on my Captivate and it enrages me each time I hear it.

Going through the modem.img file now, haven't really found anything interesting yet.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Last-Chance:
honeycomb will allow bigger screen sizes, but it will be available for phones as well.

Also this is 100% android. If it has anything with android system (like apks and such), then there is no way this can be a different OS. If it is, the developers of it are most likely looking at a huge lawsuit coming their way.
[Galaxy S I9000 Q&A, Help & Troubleshooting] xHausx:
nah, Samsung is a founding member of the open handset alliance. It's no more illegal for them to borrow parts of Android and use it in their OS than it is for Android and iOS to use Linux kernels. The only thing is they have to share the source for whatever Android code they use.

The android market on the other hand, that is Google's property there.
[Galaxy S I9000 Q&A, Help & Troubleshooting] nCoder:
So either this is Android derivate OS, or this is a new Android OS different from anything we've ever seen (Honeycomb is supposed to be a revolutionary version of Android, right?).
[Galaxy S I9000 Q&A, Help & Troubleshooting] glukosio:
How I can open these .img files? I've got tried many programs but all give back error...

P.S.: Sorry for my English
[Galaxy S I9000 Q&A, Help & Troubleshooting] LeviathanPT:
Thats if someone is able to decrypt and run it :p else they will just say PWNED!
[Galaxy S I9000 Q&A, Help & Troubleshooting] RieGo:
well it really seems to be some kind of android system:

i found build.prop (i couldn't extract the contents) and there are some interesting lines i think:
[Galaxy S I9000 Q&A, Help & Troubleshooting] GwynBleidd:
http://www.siliconimage.com/news/releasedetails.aspx?id=624

Damn nice
[Galaxy S I9000 Q&A, Help & Troubleshooting] franklin01:
Dont know if it is possible to port but we can try to "mix" FW to run it on our gt-i9000.

Basically all gt-i9000 rom have lots of common files and a few that differs:

modem.bin (use for radio, we can use a gt-i9000 modem here so radio should work)

firmware (folder specific to each rom, we can try to mix folders but there is work to do here)

lib (folder for lib, copy/paste and update old lib so it should work)

camera fw (folder for camera firmware, we can use a gt-i9000 folder here so camera should work)

I ll try to figure something but since I dont have internet anymore it ll take some time...
[Galaxy S I9000 Q&A, Help & Troubleshooting] RieGo:
but it's siliconimaging.com not siliconimage.com. i think that's not the same company...

so i wouldn't count on that
[Galaxy S I9000 Q&A, Help & Troubleshooting] GwynBleidd:
Yea I noticed that but taking into consideration that last news on siliconimaging.com date back to 2005...
[Galaxy S I9000 Q&A, Help & Troubleshooting] [Ramad]:
Open ubi.img with a hex editor like Hex Editor Neo and search for words like Android, Linux kernel, debian, samsung..etc...

This is android, all inside is linux.

The resolution is no higher than 800x480.

Graphics is PowerVR SGX540

Processor is ARM (Coretx-A8)

Audio is Wolfson-micro.

I do find pulsaudio, alsa and gstreamer0.10.
[Galaxy S I9000 Q&A, Help & Troubleshooting] paultje162:
Ok.. i just looked a bit further.

i looked into the rom and found a bootanimation whit this line

open(flagship_)

i think this means that it is the samung flagship.

so the samsung flagship is the GT-I9200
[Galaxy S I9000 Q&A, Help & Troubleshooting] LuffarJoh:
How do we know this really is from fus-servers? Could just be a hoax from samfirmware.

Can you pls provide the original download-link from fus.samsungmobile.com?
[Galaxy S I9000 Q&A, Help & Troubleshooting] [Ramad]:
Can anyone try mounting using:

modprobe nandsim first_id_byte=0x55 second_id_byte=0x42 third_id_byte=0x49 fourth_id_byte=0x23
[Galaxy S I9000 Q&A, Help & Troubleshooting] dwillMUFC:
Please could you check the framework?

That would give a clear indication wether it is android and 2.3 thanks

Dan
[Galaxy S I9000 Q&A, Help & Troubleshooting] kirkcody:
You guys should follow barakinflorida on twitter i think hes working on cracking this puzzle also....hes a genius :d
[Galaxy S I9000 Q&A, Help & Troubleshooting] nCoder:
There is nothing in his twitter suggesting he's looking at it :(
[Galaxy S I9000 Q&A, Help & Troubleshooting] :
For reference, Google TV is a derivative of 2.1, but can still work with market.

Wouldn't surprised to see this be the same thing.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Daneshm90:
Here u go :
[Galaxy S I9000 Q&A, Help & Troubleshooting] [Ramad]:
The kernel that I see all over the file is 2.6.32.

Sometimes it's 2.6.32.9
[Galaxy S I9000 Q&A, Help & Troubleshooting] modest_mandroid:
Confirming this. I don't know how the other guy definitively proved that it's android 2.2, kernel 2.6.29. There's no mention of android version from what I've seen, and references to both 2.6.29 and 2.6.32.9 are inside. Something tells me they aren't going to be launching this device with an old kernel version (2.6.32.9 is actually what the leaked Froyo-Captivate rom runs, no reason why their next-gen device would run something older).

You guys can easily confirm this yourselves by dumping the strings in the image files. If you have some flavor of linux installed:

open a terminal and type 'strings ubi.img > ubi.strings'

then issue: grep '2.6.32' ubi.strings

Also, dig this dudes, references to Maemo:

26282 3-2~maemo2+s1

I'm not trying to be a **** or anything, I'm just trying to make the point that this is a really weird firmware, and finding one line that says 'sdk=8' and '2.6.29' is about as definitive proof of android 2.2 as a line reading 'maemo2' being definitive proof of it being maemo.

Update:

He could be right.. I did find this just now and there aren't any other references to the release, confirming what he found:

4125334 release=2.2)

4125335 Nov 1 14:06:36 KST

4125337 host=vienna)
[Galaxy S I9000 Q&A, Help & Troubleshooting] LeviathanPT:
And there it goes, it was fun and exciting while it last :|

GG

EDIT:

Well at least we have newer pics taken with the Nexus S and it seems to have the camera improved.. not bad at all

http://picasaweb.google.com/bsaitz/DallasCowboysWeekend#5541734952888305714

EDIT2:

SAMSUNG AQUILA, test photo found !

http://picasaweb.google.com/lh/view?q=&uname=bsaitz&psc=G&filter=1&camera=Aquila#5531914964515744370
[Galaxy S I9000 Q&A, Help & Troubleshooting] [Ramad]:
@modest_mandroid

Thanks for confirming..

I have earlier asked if anyone can try mounting by using :

modprobe nandsim first_id_byte=0x55 second_id_byte=0x42 third_id_byte=0x49 fourth_id_byte=0x23

Did anyone try?
[Galaxy S I9000 Q&A, Help & Troubleshooting] modest_mandroid:
I did. I also tried with 0x20 0xac 0x00 0x15 and i still get errors :/
[Galaxy S I9000 Q&A, Help & Troubleshooting] crypticc:
a quick google... something about Aquila doesn't add up

http://www.engadget.com/2010/04/23/samsungs-arm-roadmap-lays-coordinates-through-2013-aquila-ven/
[Galaxy S I9000 Q&A, Help & Troubleshooting] StDevious:
ya. that is Aquila the processor, this is Aquila the model of the device that was used to take those pics
[Galaxy S I9000 Q&A, Help & Troubleshooting] LeviathanPT:
LoL theres a quad core cellphone out there !! GET HIM !!!!!!!!!!!
[Galaxy S I9000 Q&A, Help & Troubleshooting] Brut.all:
Most of Android bits use Apache license, so you could fork Android, modify it and don't release sources. Also you don't have to be a member of OHA - anyone could base his ROM on Android. It's truly open :-)
[Galaxy S I9000 Q&A, Help & Troubleshooting] bilboa1:
Certainly not the case of the kernel
[Galaxy S I9000 Q&A, Help & Troubleshooting] kimlindo:
edit: nevermind.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Brut.all:
Yes, if you would modify linux kernel, then you would have to release these modifications. I guess there are few more copylefted parts of Android, but most of it is fully open.
[Galaxy S I9000 Q&A, Help & Troubleshooting] dbtomas:
Hallo, somebody is working on this? :confused:
[Galaxy S I9000 Q&A, Help & Troubleshooting] LeviathanPT:
http://picasaweb.google.com/bsaitz/20101121BigD#5542383831441187122

NEXUS S on the table ?!

PS: Would be nice if the bastard who took the credit on engadget had said something nice :(
[Galaxy S I9000 Q&A, Help & Troubleshooting] pmos69:
More photos taken with these phones:

http://picasaweb.google.com/lh/view?q="I9020"#

and

http://picasaweb.google.com/lh/view?q="nexus+s"#
[Galaxy S I9000 Q&A, Help & Troubleshooting] dajmeister:
Hey dude it was me, and I linked in my tip to this thread. I'm sorry that engadget didn't put credit where credit was due.

Edit: And here was me reiterating where i got it after they posted: http://twitter.com/dajmeister/statuses/6744625662398464
[Galaxy S I9000 Q&A, Help & Troubleshooting] DirtySoul:
Eldar Murtazin told that there will be two new Samsung phones - one based on the current Hummingbird chip, other - dual-core, and told that he has the dual-core one now... Says - metal body and good camera.

Guess we have the first one here.
[Galaxy S I9000 Q&A, Help & Troubleshooting] LeviathanPT:
I feel happier now :| thanks

PS: The photo is gone :D ahhaah

Thank god i have a backup