Hello, Sorry for my bad English. If someone tries to open source: http://opensource.samsungmobile.com/index.jsp?page=2
On 16 Jan., 13:22, Joerie <j.de.g...@gmail.com> wrote: > While there are currently two phones on the market running the 360 > LiMo OS (SamsungM1and H1), they fundamentally differ in hardware > design, and thus should be considered different porting targets (H1 > runs on top of a OMAP3430, whereas theM1is powered by a S3C6410). > > I do think both have great potential for running Android (baseband > aside), given the number of devices already running it using similar > hardware. > > I own a Samsung H1 myself, which has never appealed to me due to the > (in my opinion) flawed LiMo implementation. I've done some basic > research on various parts of the updating process, OS and bootloader > as getting my own code/kernel running would be a requirement before > even considering porting Android. > > Unfortunately, whilst toying around with the bootloader I've managed > to turn the phone into a paperweight, so my effort is on-hold until I > manage to ressurect it via JTAG. > > As I've mentioned before, first a reliable 'way in' needs to be found, > probably by directly communicating to the bootloader (as the updater > is not capable of flashing custom firmware packages). I will gladly > share my findings so far with anyone interested (having knowledge of > the ARM architecture wouldn't hurt, though). > > Please hop along at #h1 on Freenode or send me an email. As I'm quite > certainM1runs the same bootloader, it might be of interest to bothM1and H1 > owners. Do note, my personal ability to continue working on > it depends on wheher I manage to revive my H1. > > On Jan 8, 11:42 pm, Aliaser <thealia...@gmail.com> wrote: > > > Hello, I'm very interested into this port too.. And I would really > > like to help.. > > > I think that with theSamsungPC Tools suite you can already replace > > the firmware of the phone via usb... > > (Btw I think the firmware must be packaged in a format suitable for > > those tools...) > > > However I noticed something inside the limo package list > > here:http://opensource.limofoundation.org/index.php/limo-open-source.html > > Into the limo OS package list there is also openssh... > > This means that there must be some kind of shell subsystem already > > present on the phone... > > And maybe under certain conditions it must even be accessible via > > ssh.... > > > I wonder if this could be a way to lurk inside the filesystem of the > > phone... > > > On 8 Gen, 19:16, Chris van de Steeg <ch...@chrisvandesteeg.nl> wrote: > > > > The limo distro is customized for Vodafone, though the source is > > > available, > > > there's currently no way to customize that source and then put it on > > > the phone again. > > > > If someone gets this done, then we're all go to install android on > > > it... > > > > On Jan 8, 9:37 am, Trystam <francisco.card...@gmail.com> wrote: > > > > > The Application Framework aint from Vodafone , the UI is .... > > > > The general ideia for it would be to exploit the way to hack and slash > > > > to get to the bootloader code . > > > > > On Jan 5, 8:07 am, Chris van de Steeg <ch...@chrisvandesteeg.nl> > > > > wrote: > > > > > > I have theSamsungH1myself and would also LOVE to have android 2.0 > > > > > on this device. > > > > > > I'm willing to help for sure but have no clue where to start. Vodafone > > > > > hasn't even > > > > > released an sdk to write native applications, so there currently is no > > > > > way to at least > > > > > launch some app that could explore the current partition on the > > > > > device... > > > > > Like I said, I have no clue as where to start > > > > > > On Dec 30 2009, 1:32 pm, Celegorm <ndres...@googlemail.com> wrote: > > > > > > > Come on guys, is there no one willing to try this? > > > > > > The phone (together with theH1) is going to be quite common I think. > > > > > > > Please... > > > > > > > On 28 Dez., 02:55, Trystam <francisco.card...@gmail.com> wrote: > > > > > > > > First of all one needs to know how to hack theM1to install a > > > > > > > custom > > > > > > > firmware. > > > > > > > That should be the hard part as theM1seems to be comonent wise on > > > > > > > the HCL of Android 2.0. > > > > > > > > Anyone up for giving it a shot ? > > > > > > > > On Dec 7, 12:39 pm, Celegorm <ndres...@googlemail.com> wrote: > > > > > > > > > Hello from Germany, > > > > > > > > > well, I am happy I found this group. > > > > > > > > It certainly looks like I could use some help from you guys! > > > > > > > > > I have a big problem with my new phone: aSamsung360 M-1 from > > > > > > > > Vader- > > > > > > > > ehm Vodafone. > > > > > > > > I got the device from a friend who in turn got it through an > > > > > > > > extension > > > > > > > > of his contract. > > > > > > > > Unaware of their new service called "360" I was quite happy > > > > > > > > with it > > > > > > > > (nice hardware and look and feel to it). > > > > > > > > Of course I use it with another service provider, but no > > > > > > > > troubles so > > > > > > > > far. > > > > > > > > Now that I got my first bill, I was completely shocked. > > > > > > > > Apparently the phone is always on. Not a good thing when you > > > > > > > > don't > > > > > > > > have a flatrate. > > > > > > > > While this is certainly my own fault, I have no way of > > > > > > > > returning the > > > > > > > > device. > > > > > > > > OR deleting the nice 360 application from it (Vodafone made > > > > > > > > that very > > > > > > > > clear)! > > > > > > > > > So, without resorting to unlawful forms of violence, here is my > > > > > > > > question: > > > > > > > > > Is it possible to get Android 2.0 running on theSamsungM1? > > > > > > > > The hardware should support it (360 is a LiMo-OS). > > > > > > > > And if so, how is it been done? > > > > > > > > > I certainly hope you can help me. > > > > > > > > Please remember, you are my last hope against this evil empire. > > > > > > > > > Many thanks, > > > > > > > > > C -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
