Hi everibody
at the beginning of the 2012 the source code of symbian^3 has been relased by nokia, bootloader included. I can't understand why this great news has been almost totally ignored by everybody. Ok, nokia it's no more the #1 seller of mobile phones, but I think that it would be great, if it's possible, to port android on those devices, expecially to those one with symbian belle that have a pretty decent hardware (above 1 Ghz processor, enough RAM and good camera). So, why nobody is working on that project, if it's theoretically possible?
gigsaw said:
Hi everibody
at the beginning of the 2012 the source code of symbian^3 has been relased by nokia, bootloader included. I can't understand why this great news has been almost totally ignored by everybody. Ok, nokia it's no more the #1 seller of mobile phones, but I think that it would be great, if it's possible, to port android on those devices, expecially to those one with symbian belle that have a pretty decent hardware (above 1 Ghz processor, enough RAM and good camera). So, why nobody is working on that project, if it's theoretically possible?
Click to expand...
Click to collapse
Symbian it's dead and buried by Nokia ! If not look what devices it's taking out Nokia: lumia series without symbian.
Sent from my RK29 tab...
Yeah, I agree with you, and that's exately for this reason that I'm writing this post. Probably nokia will abandon those devices because there is a gape between symbian and the other os that can't be filled, but the hardware of this phone is ok. Why not giving the possibility to the owners of this devices (and are a lot of people) to install android on those terminals? With the relase of the source code I think it would be possible...
gigsaw said:
Yeah, I agree with you, and that's exately for this reason that I'm writing this post. Probably nokia will abandon those devices because there is a gape between symbian and the other os that can't be filled, but the hardware of this phone is ok. Why not giving the possibility to the owners of this devices (and are a lot of people) to install android on those terminals? With the relase of the source code I think it would be possible...
Click to expand...
Click to collapse
Not at all their interest is to sell devices !
Hope you get something, you'll need to enter in bootloader. But I don't know how to adapt it to Nokia ones !
Sent from my RK29 tab...
For now that's what has been found out from symbian^2 (the only one taken into account for now, but I think that Symbian^3 wouldn't be so far different):
- The whole bootloader code (verified to be present even in symbian^3, in "Symbian-OS layer" and the folder is: os/kernelhwsvr/brbootldr)
- This code contains options for dual booting
Boot options:
- Boot from NOR area
- Boot from NAND area
- Boot from USB (Memory Card) in Mass Storage mode
Flash options:
- Flash ROM from ZIP
- Flash ROM from Symbian Image
The problems found:
- Accessing the bootloader on current Symbian devices (how to get into bootloader mode on the phone?)
- In the USB booting (the source code refers to a separate executable what should do the booting, but this executable ISN’T AVAILABLE anywhere, nor in the source, neither in any current device)
I think that here we DO have the concrete possibility to open up Symbian devices, and I can't believe that on this forum, with 4,580,619 users registred, NOBODY is interested in this thing.
Related
Hello all!!
I'm new to Android and i'm interested in learning a bit and maybe get involved with it but there are some things that i don't get about android and can't find the answers.
My main question is why Android which is based on Linux is so hard to get updates for all devices at once?
For example we got ICS lately why it's only available for Nexus S and not for all devices that support android?
In pcs if there is a new Ubuntu version every pc can get it no matter the hardware it uses as there are drivers for it.
Is it so hard to have drivers for all the android devices?
Why do we need to wait forever for the X company that makes the phone to build a new kernel?
Is it about the libaries?The drivers?
Say i got a device that is not supported by ICS what would i need to make it supported? I got my libs from 2.3.5 can i toss them to overlay compile and works? If not y not?
Thanks in advance for your answers and sorry if my questions are too noobish, everyone has to start from somewhere
Serafym said:
Hello all!!
I'm new to Android and i'm interested in learning a bit and maybe get involved with it but there are some things that i don't get about android and can't find the answers.
1. My main question is why Android which is based on Linux is so hard to get updates for all devices at once?
2. For example we got ICS lately why it's only available for Nexus S and not for all devices that support android?
- In pcs if there is a new Ubuntu version every pc can get it no matter the hardware it uses as there are drivers for it.
3. Is it so hard to have drivers for all the android devices?
4. Why do we need to wait forever for the X company that makes the phone to build a new kernel?
5. Is it about the libaries?The drivers?
6. Say i got a device that is not supported by ICS what would i need to make it supported? I got my libs from 2.3.5 can i toss them to overlay compile and works? If not y not?
Thanks in advance for your answers and sorry if my questions are too noobish, everyone has to start from somewhere
Click to expand...
Click to collapse
1. Manufacturers don't release updates for all their devices all at once (some not at all).
2. It's ready (most stable so far) for that device (SDK ports; (almost) official update)
- Not true. If you tried to place Ubuntu 12.04 LTS on a PC with a 368 MHz and 32mb ram, it would not run .
3. Yes. Android is on devices from many different manufacturers with many different designs and hardware.
4. See here: http://en.wikipedia.org/wiki/Linux_kernel (to know what it is). Different hardware will require different commands, etc. If the manufacturer doesn't release the kernel source, development cannot be done on that device (properly).
5. Yes and yes (much more too).
6. Create a working port from some other device (with similar hardware) which is supported. Sometimes. Some versions of android have backward compatibility of those files but ICS isn't really backward compatible which is why many ports of ICS (for various devices) don't have a working camera, etc. See the 2nd paragraph here: http://www.cyanogenmod.com/blog/cm9-progress-update.
Just for the fun
http://translate.google.com/transla...ation-de-le-tama-the-king-of-the-rom/&act=url
Nice
Anybody knows why google translates "firmware" to "shower"?
Nice, now we know a bit more of the guru
God, Google translation is awful
Here is my approximate translation of cajl interview:
1) Le Tama, master of archos roms, present yourself
I fall into computers when I was very young (11 year old, no personal computer at this time, I start programming on paper with a book ) and since then virus never left me. I'm 42, I'm technical director of a small software development company. As my current job don't give me much occasion to dig into code, I'm pursuing my passion as a leisure, and especially on Archos tablet these days.
2) Why Android ?
I came to Android with my HTC HD2. At that time, Android just started to show some great potential and Windows Mobile was getting old. I started to follow HD2 development efforts on Android. It was stuck on a kernel problem, it pushed me to start looking into linux kernel source code. I then took part of the desire kernel port to HD2 with Cotulla and the others and I also participated to the first Android release working on HD2.
3) Why Archos
I started looking at Archos when Google annonced ICS and annonced that they will be using Omap as reference platform. I always wanted to have a look at omap (too much qualcomm with hd2 ), so I started to look for a platform that would let me play with it without being too costly. That's why I naturally came to Archos. I started toying with my co-worker A70 and then purchased my A101G9.
The more I work on Archos, the more I like the "openness" of the platform. Gen8 bootloader is easy to crack, gen9 bootloaders are not even locked. Better, Archos thinks about us, hackers, by letting entry points like SDE, a reserved partition on gen9,...
4) By the way, what's the purpose of rooting ?
Ah! What's the purpose of root:
From a developer point of view, to give complete access to resources. With root, we can do a complete dump of disk and partitions to study firmware, install things we couldn't do without, like SDE for Gen9. It's the first necessary step to modify stock firmware. It's also mandatory if you want to do some specific operations like partitioning.
From an user point of view, it let you use application that demands root. My favorites are:
- Busybox
- Root Explorer
- Titanium backup
- Chainfire 3D
And I certainly forgot some. Just looking at market, we see thousands of applications that requires root to work.
5) Easy or not easy to find exploits ?
No, not easy with a well-made firmware. Except big mistake from manufacturer, exploits (weakness abused to obtain a temporary root) are fixed after discovery, and it's getting more and more difficult to find new weaknesses. Thankfully, our current exploit is not fixed, crossing finger.
6) What are you currently working on ?
I'm working a bit on too many fronts and not enough free time, but here is what I'm working on:
- Internal disk partitioning for g9 to let us install sde firmware on a separated native ext4 partition, without interfering with stock firmware and internal storage. It works on mine, I'm working on way to do it simply and safely to let everyone benefit from it.
- Clockworkmod Recovery. It also works on mine, but is only useful if tablet has been partitioned. It let us do complete backups, rom+apps+internal storage (nandroid backup), it let us use zips to install firmware and firmware updates, and it make our tablet feels more "android native".
- CM9: I built one for gen9 that worked not too badly, but there is a lot of work to get something completely functional.
- I also launched a first overclocked kernel for 1.0Ghz Gen9, stable on mine up to 1.2, almost at 1.3. I will have to work on this again when Archos will release a new firmware that fix current ICS problems.
- I'm working on the IT2, I activated SDE and I have a rooted firmware. I will try to port 3.0 kernel and ICS on it.
- I'd like to work on bootloader too, but this is another story...
7 How can we help ?
Explain my boss that I have to stop working on his projects! More seriously, I'll certainly need beta-testers that are willing to take risks for their tablets with partitioning, but I'm not there yet.
8 Why this nickname ?
Le Tama ? This is a wink to my wife! Sshhh!
9 Anything more ?
Nah, enough talk, back to work!
letama said:
God, Google translation is awful
Click to expand...
Click to collapse
Naaaah, it's pretty funny (I had no idea that Gen9 has a shower onboard)
letama said:
7 How can we help ?
Explain my boss that I have to stop working on his projects! More seriously, I'll certainly need beta-testers that are willing to take risks for their tablets with partitioning, but I'm not there yet.
Click to expand...
Click to collapse
Count me in
letama said:
- Clockworkmod Recovery. It also works on mine, but is only useful if tablet has been partitioned. It let us do complete backups, rom+apps+internal storage (nandroid backup), it let us use zips to install firmware and firmware updates, and it make our tablet feels more "android native".
Click to expand...
Click to collapse
Oh my god! This is by far that feature that I am missing most on my G9. I hope this dream comes true one day.
letama is great!!!
Hi all,
i'm a noob to android, but i have nit of experience on other unix based systems.
I was wondering, why there is no custom roms for GT-S5690?
What's the problem?
Is bootloader locked some other way or is it somehow different from example Gio/GT-S5660?
There is a bunch of roms for gio..
I have one xcover, wich has no screen and covers, i thought i could use it for testing.
I think there are too less people who have a xcover, and I was actually pretty disappointed when I say there is a successor to the xcover available only in the US (Rugby Smart / Pro <-- with ICS!).
From the technical side, I don't know. Even the source code of the firmware is available at opensource.samsung.com. The Bootloader seems pretty much unlocked.
For me, the xcover is the best phone ever, it takes so much abuse. Maybe someday someone will port a newer ROM from the Ace/Gio/idk. It's a shame Samsung abandons their old phones :crying:
xkawer said:
I think there are too less people who have a xcover, and I was actually pretty disappointed when I say there is a successor to the xcover available only in the US (Rugby Smart / Pro <-- with ICS!).
From the technical side, I don't know. Even the source code of the firmware is available at opensource.samsung.com. The Bootloader seems pretty much unlocked.
For me, the xcover is the best phone ever, it takes so much abuse. Maybe someday someone will port a newer ROM from the Ace/Gio/idk. It's a shame Samsung abandons their old phones :crying:
Click to expand...
Click to collapse
I didn't were aware of successor models, now i'm very dissappointed.
I'm downloading these source codes at the moment, i'll check these out.
I'm not a developer, atleast YET..
AFAIK, hardware of s5690 is way different from any other samsung phones,
correct me if i'm wrong..
jonezy82 said:
AFAIK, hardware of s5690 is way different from any other samsung phones,
correct me if i'm wrong..
Click to expand...
Click to collapse
Seems like it's the only one with a Marvell MG2.
Let me know if you do anything interesting with the sources
Just flashed my xcover to XXLJ2 yesterday. At least it seems a bit faster now, but I have a weird bug when scrolling. If I give a list (for example settings) momentum, it doesn't stop when I put my finger on it again. But it does stop if I release the finger the second time.
jonezy82 said:
I'm downloading these source codes at the moment, i'll check these out.
Click to expand...
Click to collapse
Did the same. The GT-S5690_Platform.txt says:
Code:
How to build platform
1. Get android open source.
: version info - Android gingerbread 2.3.6
( Download site : http://source.android.com )
2. Remove external\webkit module in android open source which you got.
And then execute "clean build"
2. Copy files and modules to original Gingerbread source tree (overwrite)
3. build
- ./build.sh user
So wouldn't it be possible to download the JB sources, and compile them with the original kernel? Would be so cool.
Edit: It seems you need device specific binaries (drivers) since ICS. see: http://www.freeyourandroid.com/guide/compile-ics
Found a git https://github.com/manakeri/android_device_samsung_xcover, there is a
Code:
cyanogen_xcover.mk
file, this seems interesting. Apparently someone is trying to port it.
Edit2: In this git, there is also a "extract-files.sh"-file, which is neccessary to pull the proprietary files from the phone! With this I think we actually have everything we need to compile ICS/JB, like in the "freeyourandroid" tutorial.
I have never done this before, but someone must try it lol.
Oh look, there are more people who care about it!
http://www.droidevelopers.com/f338/14412-gt-s5690-opensource-kernel-available.html
Someone discovered my link and made a overclock kernel from the sources! This is so cool.
I hope we are going to see more :good:
xkawer said:
Oh look, there are more people who care about it!
http://www.droidevelopers.com/f338/14412-gt-s5690-opensource-kernel-available.html
Someone discovered my link and made a overclock kernel from the sources! This is so cool.
I hope we are going to see more :good:[/QUOTE
I own an xcover too a developer on another forum looked at some files i pulled using adb to try to port clockworkmod but no success. Told me the files i sent weren't standard android img but he would continue to look into it. Apparently the teamhacksungs goal is to port cyanogenmod for every Samsung device surely they can get it done. I've been waiting a long time to see some development for the awesome xcover
Click to expand...
Click to collapse
If its possible on the galaxy mini its got to be possible on xcover!. Ive tried to get involved and learn to port cyanogenmod but when it comes to git, repo, source tree, source code e.t.c e.t.c its a bit behond me for now.
Step in the right direction it seems. Fingers crossed
Hello i want to know how to develop a bootloader for a windows phone device..i am of the logic that even though there are different wp7 devices manufactured, they all have very similar hardwares..i am talking about wp7 devices here and not a wp8 devices..as they have similar hardwares and the devices are NOT manufactured with bootloaders in them already, i say that basically all custom bootloaders have very similar characterestics..so taking the modifications by OEMs secondary to what MS has done in its OS, it should be possible to develop a custom bootloader for all devices with little or moderate modifications and so u can have the same pizza base for different toppings..
this is how i have understood the bootloader concept in wp7..anybody like cotulla please be kind enough to correct me if i am wrong and please be kind to create a tutorial on how to create a bootloader..stock bootloader is and has been one of the culprit that does not allow unsigned cabs and ROMS to be installed on a wp7 device except in case of some lumia 710 and 800 that came with unlocked bootloaders..we can preferably take a 2nd gen wp7 as example..say samsung focus s or htc titan 2 or samsung omnia w..
and develpoers, please remember that more people(but not too many) working on a project may help speeding up the work..
INTRODUCTION
Have you ever dreamed to get not any device but YOURS on the wide screen of your computer? Create a custom ROM and emulate it, or just check another custom ROM compatibility virtually without having to flash and risk your everyday tool? Well I did and I still do!
In the old times this was possible but, unfortunately, it's no longer the case. Since our beloved mobile devices got more features, system has become also more complex. This is why we can't run a custom ROM only with system and data images as before anymore. Unless you still want to develop on Gingerbread and below — seriously? — we need to move to another solution.
And this is what this project is for!
According to the fact that we're not all pro developers and / or we're not all rich enough to buy multiple devices in case of brick, I think such project is necessary to avoid taking stupid risks like we do now.
ORGANIZATION
Currently the project is committed under the name of "AndROMega".
It is planned to work under the Windows and Linux environments. An eventual port for Mac OS isn't envisaged for now but still welcome if someone wish to work on once a version is released.
By the way, this project being free and open-source, everybody can join, improve it but thieving (including copying then claiming project as-is / unmodified is your and, worse, selling this common work) is absolutely UNALLOWED. This must still free, open-source and mention the original authors (me and other devs eventually joining) in case of copying to make custom release. All of this juridical stuff will be put in a license file as usual anyway.
The QEMU emulating software will be used to facilitate the cross-platforming of the project software. It is fast, powerful, reliable, and, moreover: FREE.
Edit: Great new! Editing a custom Android emulator from scratch won't be in the question anymore!
A Github repo has been created allowing to run a stock AOSP Android ROM, so one step is made
Link to this repo: https://github.com/aosp-mirror/platform_external_qemu
Other notes coming soon in this thread...
Reserved.
Atronid said:
INTRODUCTION
Have you ever dreamed to get not any device but YOUR on the wide screen of your computer? Create custom ROM and emulate it or just check another custom ROM compatibility virtually without having to flash and risk your everyday tool? Well I did and I still do!
In the old times this was possible but, unfortunately, it's no longer the case. Since our beloved mobile devices got more features, system became also more complex. This is why we can't run a custom ROM only with system and data images as before anymore. Unless you still want to develop on Gingerbread and below — seriously? — we need to move to another solution.
And this is what this project is for!
According to the fact that we're not all pro developers and / or we're not all rich enough to buy multiple devices in case of brick, I think such project is necessary to avoid taking stupid risks as we do for now.
ORGANIZATION
Currently the project is committed under the name of "AndROMega".
It is planned to work under the Windows and Linux environment. An eventual port for Mac OS isn't envisaged for now but still welcome if somebody wish to work on once a version is released.
By the way, this project being free and open-source, everybody can join, improve it but thieving (including copying then claiming project as-is / unmodified is your and, worse, selling this common work) is absolutely UNALLOWED. This must still free, open-source and mention the original authors (me and other devs eventually joining) in case of copying to make custom release. All of this juridical stuff will be put in a license file as usual anyway.
The QEMU emulating software will be used to facilitate the cross-platforming of the project software. It is fast, powerful, reliable, and, moreover: FREE.
Edit: Great new! Editing a custom Android emulator from scratch won't be in the question anymore!
A Github repo has been created allowing to run a stock AOSP Android ROM, so one step is made
Link to this repo: https://github.com/aosp-mirror/platform_external_qemu
Other notes coming soon in this thread...
Click to expand...
Click to collapse
So what do you mean by custom rom environment builder? Do you mean when you port a rom and it has glitches and the environment fixes it or what? I'd be happy to help with this.
NonStickAtom785 said:
So what do you mean by custom rom environment builder? Do you mean when you port a rom and it has glitches and the environment fixes it or what? I'd be happy to help with this.
Click to expand...
Click to collapse
I don't really understand your question, but I'll sum up what the project is, hoping it will help you understand.
It's nothing more or less than a tool that mimic hardware and specific components and architecture of a phone model. It is supposed to be more than an AVD, allowing you to literally flash a custom ROM and debug it virtually instead of having to buy the phone, flash it, screw everything if something goes wrong, restore backup, etc.
Back when I got this idea (before it got forgotten among the million projects I have) I thought the hardest part was to get the core component of every phone (ramdisk, ROM, bootloader — assuming it's possible, otherwise "create" a replicant) and get the hardware spec mimicked with QEMU. Now I grew a bit and got a new-featured phone (seamless partition system that was pretty new to me), I know it will be even more complicated.
Since I'm not really available this year because of my exams, this project will still idle for a while. But I won't abandon it, so if the principle interest you and you're ready to give a hand you are welcome !
I'm In!
Atronid said:
I don't really understand your question, but I'll sum up what the project is, hoping it will help you understand.
It's nothing more or less than a tool that mimic hardware and specific components and architecture of a phone model. It is supposed to be more than an AVD, allowing you to literally flash a custom ROM and debug it virtually instead of having to buy the phone, flash it, screw everything if something goes wrong, restore backup, etc.
Back when I got this idea (before it got forgotten among the million projects I have) I thought the hardest part was to get the core component of every phone (ramdisk, ROM, bootloader — assuming it's possible, otherwise "create" a replicant) and get the hardware spec mimicked with QEMU. Now I grew a bit and got a new-featured phone (seamless partition system that was pretty new to me), I know it will be even more complicated.
Since I'm not really available this year because of my exams, this project will still idle for a while. But I won't abandon it, so if the principle interest you and you're ready to give a hand you are welcome !
Click to expand...
Click to collapse
Well this is a very interesting idea. It would be very useful for the rooted phones that don't have any custom roms already built.
Maybe you wouldn't have to get the core components of every phone all at once. Maybe it you could make the program to extract a twrp or cwm backup, and have a database of all the ramdisks and chipsets that the program will have access to.
I think this project is very useful and I would like to start in the development of it or aid you in it. PM me with more details :good:.
NonStickAtom785 said:
Well this is a very interesting idea. It would be very useful for the rooted phones that don't have any custom roms already built.
Maybe you wouldn't have to get the core components of every phone all at once. Maybe it you could make the program to extract a twrp or cwm backup, and have a database of all the ramdisks and chipsets that the program will have access to.
I think this project is very useful and I would like to start in the development of it or aid you in it. PM me with more details :good:.
Click to expand...
Click to collapse
Yes, backup extraction and component database was the original idea
Thank you for your help! I'll PM you as soon as the project starts :fingers-crossed:
Atronid said:
Yes, backup extraction and component database was the original idea
Thank you for your help! I'll PM you as soon as the project starts :fingers-crossed:
Click to expand...
Click to collapse
Thanks:laugh:
Best thing ever, life saver etc, I am ready to do whatever you want just this thing to succeed!
ender1324 said:
Best thing ever, life saver etc, I am ready to do whatever you want just this thing to succeed!
Click to expand...
Click to collapse
That's very nice, thanks!
As mentionned earlier, the project won't start right now due to my work, but in theory I should be available and ready to start it in the next months! I'll DM you as soon as it gets its first kick !