I read a lot about android is running on this, and that.. lot of devices. Is there a possibility to run it on a T830? I don't know much about android, and it's hardware support, so this question might sound a bit lame
It have to be pda specific like windows mobile?
Android Kernel
Hello,
Well i think it is possible to compile a Android Kernel to boot on FSC T830. But the main problem is its hardware support. Well, FSC T830 has supported Processor and enough ROM and RAM to make Android fit in. I did not test it or did any work to compile such kernel but if you want to work on it then let me know . All we need are some basic info about the hardware to know if its worth trying or not.
k1dugar said:
Hello,
Well i think it is possible to compile a Android Kernel to boot on FSC T830. But the main problem is its hardware support. Well, FSC T830 has supported Processor and enough ROM and RAM to make Android fit in. I did not test it or did any work to compile such kernel but if you want to work on it then let me know . All we need are some basic info about the hardware to know if its worth trying or not.
Click to expand...
Click to collapse
What do we have to know about it?
Hardware Info.
Hi, Tookool
Well we need the chipset info about the GSM controller, mainboard, wlan, gps, bluetooth, display, touchscreen and keyboard.
We need the keyboard and display to work at the very first place else it would be impossible to do anything. I have read on the forum about dual booting from SD card using gnuharet.exe. So we can compile a kernel and boot it on SD memory. Well I'm going to take a look on the Android Kernel and try to compile it and run it over QEMU. Hope for the luck.
k1dugar said:
Hi, Tookool
Well we need the chipset info about the GSM controller, mainboard, wlan, gps, bluetooth, display, touchscreen and keyboard.
We need the keyboard and display to work at the very first place else it would be impossible to do anything. I have read on the forum about dual booting from SD card using gnuharet.exe. So we can compile a kernel and boot it on SD memory. Well I'm going to take a look on the Android Kernel and try to compile it and run it over QEMU. Hope for the luck.
Click to expand...
Click to collapse
Hi!
From where can I obtain these informations? I did a quick search on the net, but...
Hardware info.
CPU: Intel XScale PXA270 (ARMv5TE) :Supported
Display: 240 x 240 (1.7' x 1.7') :Unknown (Supported on other device)
Touch Screen: - :Unknown
Audio: AC97 (not sure) :Unknown
ROM: 128MB :Supported
RAM: 64MB :Supported
GSM: Ericsson EMP U250 :Supported
GPS: SiRFstarIII GSC3f/LP :Supported
Key: QWERTY (Keymap) :Supported
WiFi: Atheros AR6001 ROCm 802.11b/g :Supported
Bluetooth: Broadcom 2040 :Supported
USB: USB 1.1 :Supported
I am trying to build kernel with info i have about the hardware. Hope it will boot at least.
I'm looking for the infos you didn't find
wifi: WLAN 802.11b/g
bluetooth: Bluetooth 2.0
keyboard: QWERTZ
usb: client/host
I found these, but I don't know if this is good or not I'm not really into things liek this
Hi,
I'm using the WM6.1 on my FCS T830 right now, but running Android on it sure sounds like an even cooler idea.
I hope somebody manages to get this working!!!
k1dugar said:
CPU: Intel XScale PXA270 (ARMv5TE) :Supported
Display: 240 x 240 (1.7' x 1.7') :Unknown (Supported on other device)
Touch Screen: - :Unknown
Audio: AC97 (not sure) :Unknown
ROM: 128MB :Supported
RAM: 64MB :Supported
GSM: Ericsson EMP U250 :Supported
GPS: SiRFstarIII GSC3f/LP :Supported
Key: QWERTY (Keymap) :Supported
WiFi: Atheros AR6001 ROCm 802.11b/g :Supported
Bluetooth: Broadcom 2040 :Supported
USB: USB 1.1 :Supported
I am trying to build kernel with info i have about the hardware. Hope it will boot at least.
Click to expand...
Click to collapse
Hey!
Any news?
Well, is this project dead or what happened?
Donno, k1dugar isn't responding
Im sorry for late reply.
Hello,
I am sorry for late reply but somehow i lost the interest on building this image now bcoz of lack in features availability in Android which would make this image useless. I'm waiting for google to launch the full source code for it. I'm Working on making WM6.1 final rom where all feature will be working and stable.
Please carry on the work, i normally dont work in a way that i will do something and upload my final work. I like ppl to research themself and make it themself so they can learn and improve something on there way. Sure untile i think its stable and wont harm someone's hardware in anyway then i will upload the final work, until then just step by step guide.
Let me finsh WM6.1 with help of all you ppl and then we can work on Android, I personally Love *NIX system. I would be more then happy to make my phone run Linux.
A fully working wm 6.1 would be great Just keep up the work with that, android can wait Don't forget about the blue keyboard thing
Before to use Android, the first step must be to have a linux kernel working on T830.
I've tried to compile 2.6.28, but I haven't succes.
It isn't impossible, but it seems hard to make, because the kernel is strictly relate to hardware platform.
There is someone that want to try thiswith me ?
Let me now.
Thanks
tea4two
tea4two said:
Before to use Android, the first step must be to have a linux kernel working on T830.
I've tried to compile 2.6.28, but I haven't succes.
It isn't impossible, but it seems hard to make, because the kernel is strictly relate to hardware platform.
There is someone that want to try thiswith me ?
Let me now.
Thanks
tea4two
Click to expand...
Click to collapse
I would like to help with everything I can. The only thing is that I never made such things like building a kernel or so But if you can provide me with instructions and things like that it would be great!
Hi TooKooL,
First steps to compile the kernel are very easy.
I'm using Fedora 10 so what I write is related.
There is the need to have the right Chaintool to compile.
I've found this information: http://loox-linux.sourceforge.net/chaintool.html
, but I work different:
1 - yum install arm* (is not the rigth command to use, but you need to install all arm-* packages)
2 - Download linux Kernel (i've used latest 2.6.28)
3 - Unpack tha kernel: tax xvzf linux-2.6.28.tgz
4 - make a symbolic link ln -s linux-2.6.28 linux
5 - modify top level Makefile in this way:
ARCH ?= arm
CROSS_COMPILE ?= /usr/bin/arm-gp2x-linux-
6 - run: make menuconfig
7 - Setup the right value in the lernel (drivers, cpu, ecc..) THIS IS THE TRUE PROBLEM!!!!
8 - run: make zImage
To load linux kernel use HaRET.
Copy on root of SD-CARD:
HaRET.exe
zImage
startup.txt
the startup.txt contain olny one row with the word "boot" (without quote)
Run HaRET and linux start to load..... if kernel is compiled rigth..... (i'm not lucky)
Other useful link are:
http://sites.google.com/site/siteofhx/Home/android/android-porting-steps/english
http://loox-linux.sourceforge.net/
Let us know if you have some results...
Regards
tea4two said:
Hi TooKooL,
First steps to compile the kernel are very easy.
I'm using Fedora 10 so what I write is related.
There is the need to have the right Chaintool to compile.
I've found this information: http://loox-linux.sourceforge.net/chaintool.html
, but I work different:
1 - yum install arm* (is not the rigth command to use, but you need to install all arm-* packages)
2 - Download linux Kernel (i've used latest 2.6.28)
3 - Unpack tha kernel: tax xvzf linux-2.6.28.tgz
4 - make a symbolic link ln -s linux-2.6.28 linux
5 - modify top level Makefile in this way:
ARCH ?= arm
CROSS_COMPILE ?= /usr/bin/arm-gp2x-linux-
6 - run: make menuconfig
7 - Setup the right value in the lernel (drivers, cpu, ecc..) THIS IS THE TRUE PROBLEM!!!!
8 - run: make zImage
To load linux kernel use HaRET.
Copy on root of SD-CARD:
HaRET.exe
zImage
startup.txt
the startup.txt contain olny one row with the word "boot" (without quote)
Run HaRET and linux start to load..... if kernel is compiled rigth..... (i'm not lucky)
Other useful link are:
http://sites.google.com/site/siteofhx/Home/android/android-porting-steps/english
http://loox-linux.sourceforge.net/
Let us know if you have some results...
Regards
Click to expand...
Click to collapse
Hi!
So, if I understand I need that chaintool (can't find download link on the page), a kernel (simple desktop linux version???). First of all make these things clear please After that I think I have to work with that chaintool as you mentioned in point 1, 4 ... Right? Sorry, but I'm new to this, I never even used linux before. Edit: ok, I found the kernels you mentioned, what files do I need to download?
linux-2.6.28.tar.bz2
linux-2.6.28.tar.bz2.sign
linux-2.6.28.tar.gz
linux-2.6.28.tar.gz.sign
linux-2.6.28.tar.sign
These?
And what about that arm package installation? It's a shame I'm a novice and I want to make this, but I have to start learning somehow
I've found other informations about to use HaRet to boot linux.
http://www.handhelds.org/moin/moin.cgi/HowtoLinuxHaret
There is the need to partitioning the SD Card in two partitions, FAT16 and ETX3.
The FAT16 is used to boot linux (copy files: Haret.exe, zImage and startup.txt)
The Etx3 is usedt to save all Linux files (/boot, /usr, /bin, /var, and so on)
I've tried to start several kernel images without success.
Haret hang when on the screen appears "Jump to kernel...."
The device hang too, the only way to unlock it's a Factory Default server.
It seems only a Kenrel issue. I don't understand where I must start to compile a new kernel.
There are PDA similar T830 ? This maybe a good starting point.
I don't understand how to use sartup.txt
This file contains information for the boot sequence, I have only "boot" write in It, but other parameter are required (I think).
Surfing the nternet I've found the need to know GPIO, how must I use it ?
Tea4two.
WOW!!!
Little success.....
I've found this project about n560
http://www.elcom.pub.ro/~adrian.popa/n560-linux/
and Linux boot on T830 .... but hang suddenly....
I'm very happy, because this is a good starting point to port Android to T830
Attention!!! You MUST repartitioning SD-CARD before copy files on it to boot Linux.
Then Linux start, but hangs suddenly and the device vibrate endless.
The only way to stop is to remove the battery.....
then before to try: MAKE BACKUP OF YOUR DATA!!!!!
For Developers:
The good starting point is to download HandHeld kernel, running follow command:
cvs -d server:[email protected]:/cvs checkout -d linux-2.6.x-hh linux/kernel26
Then use looxn560_defconfig: make looxn560_defconfig
And after..... we need to understand how change kernel config to match T830 hardware.
We need to use in the rigth way GPIO's.
GPIO's are connected to various devices (led, keyboard, touchscreen, vibrate....), so wrong configuration hang the linux boot.
Good work...
Tea4two
tea4two said:
WOW!!!
Little success.....
I've found this project about n560
http://www.elcom.pub.ro/~adrian.popa/n560-linux/
and Linux boot on T830 .... but hang suddenly....
I'm very happy, because this is a good starting point to port Android to T830
Attention!!! You MUST repartitioning SD-CARD before copy files on it to boot Linux.
Then Linux start, but hangs suddenly and the device vibrate endless.
The only way to stop is to remove the battery.....
then before to try: MAKE BACKUP OF YOUR DATA!!!!!
For Developers:
The good starting point is to download HandHeld kernel, running follow command:
cvs -d server:[email protected]:/cvs checkout -d linux-2.6.x-hh linux/kernel26
Then use looxn560_defconfig: make looxn560_defconfig
And after..... we need to understand how change kernel config to match T830 hardware.
We need to use in the rigth way GPIO's.
GPIO's are connected to various devices (led, keyboard, touchscreen, vibrate....), so wrong configuration hang the linux boot.
Good work...
Tea4two
Click to expand...
Click to collapse
I'll definiately try this later today, and I'm looking for that boot info for haret too.
Related
This thread discusses Linux for HTC Diamond and HTC Raphael
User resources
To get started with android real quick use this site http://wiki.xda-developers.com/index.php?pagename=RaphaelDonut
Further information on progress with Linux and Android and help can be found at the Raphael Linux wiki page.
Developer resources
The wiki of the htc-linux.org project has all the required uptodate research information http://www.htc-linux.org/wiki
If you want to contribute in the kernel porting project, please use this wiki.
The latest kernel code for Raphael, Diamond (and the other msm7xxxA devices) can be found in the htc-msm-2.6.27 branch of the linuxtogo.org git repository.
To view my signature, click my nickname to view the profile and then 'about me'
_______________________________
original post:
Hi,
Would be nice if somebody could try and test if the kaiser linux kernel boots on their diamond. Here's what you need
http://linuxtogo.org/~lgorris/kaiser-bootkit/
It has a small documentation but here's what you need to do again:
Get haret.exe, default.txt, zImage and angstrom-console on your diamond into the same folder, run haret.exe and tap run.
edit: the link above points to a website with kernel builds for the kaiser (msm7200). since diamond has msm7201A, it would be better to build directly from the android-msm-2.6.25 branch which has the halibut machine type. halibut is also an msm7x00A. there are some differences between the A and non-A msms.
google git is at
git.android.com
checkout the branch android-msm-2.6.25 ( it's most uptodate)
Click to expand...
Click to collapse
I have in fact been researching this since yesterday. The vanilla Android is for 7x00A devices, and should work on Diamond without too much fuss. I'm not a Linux developer though, so I'll need some help with that part. (though I am a developer)
The Kaiser boot kit does not work. Once it's done loading the device freezes entirely. Kaiser uses 7200 though, not 7201A, and for all I know it might actually be (partly somewhat) running, but with no frame buffer.
agreed with the freezing part.
From Haret:
WinCE reports memory size 134217728 (phys=118571008 store=115261440)
Where did the rest 64 MByte go?
Ok who's seriously interested in getting this to work?
Whats the progress so far? Lets try to get something packaged and up for diamond.
me
I am definately going to spend some time trying to gets this to work when I get my Diamond.
teddyen66 said:
I am definately going to spend some time trying to gets this to work when I get my Diamond.
Click to expand...
Click to collapse
I haven't been able to compile the kernel, but it sounds like you'll be able to. Give it a shot and I'll test it.
I'll test it too.
k, can you also try the vogue builds? http://it029000.massey.ac.nz/vogue/
http://wiki.xda-developers.com/index.php?pagename=DiamondResearch
the shared memory looks similar to the on on kaiser. So it will probably be easy to make communication with the phone work as soon as it works on kaiser. Of course you need to be able to boot first
Hi guys,
I've been trying to get Android running on my Diamond for a few days to no avail.
I've tried the Kaiser set of files and Vogue set of files. The furthest I've got is to make it display the 'Go Go Go...' message and then it hangs.
Has anyone actually got Android to run on a Diamond before?
Thanks.
Vogue does not work, but might be because of HaRET, don't know.
7201A is different from 7200. I would not expect it to work. However, the vanilla kernel is for Diamond type chips, so if anyone could compile a vanilla kernel it's worth testing. HaRET might need a few modifications though.
Very interesting!
This Android thing, getting it to run, what would the expectations be? Functionality, speed?
Just very curious, having once installed some linux-thingy on my magician.
I don't have a Diamond to test on, but I suspect the dev team for the Advantage could be of help. The build they have is running ok on Advantage, the touchscreen driver even works. No phone yet (last I checked). Maybe it will also run on Diamond?
nopes advantage is a different platform
I believe it'll just be a matter of time before we get a fully functioning Android build for the HTC Diamond because I can foresee it to be a very popular platform for the Android.
If there's any modifications to the default.txt boot file that would potentially make this work I'll be happy to try it out and let you guys know the results.
happyguy82 said:
I believe it'll just be a matter of time before we get a fully functioning Android build for the HTC Diamond because I can foresee it to be a very popular platform for the Android.
Click to expand...
Click to collapse
I hope that too . I can not wait to run Android on my Diamond.
I guess it'd be a matter of setting up a cross compile (toolchains - chroot, binutils, gcc, glibc) environment for the ARM, compiling the kernel with the correct drivers and bootstrapping for the ARM.
Am I right? Or did I miss something?
Would this link be of any help ?
http://nemustech.blogspot.com/2007/12/android-porting-to-real-target-hw.html
I would like to get involved if someone is already working on it
Darn that's running smooth ...
... hope we can get some linux running on this hardware.
adwinp said:
I guess it'd be a matter of setting up a cross compile (toolchains - chroot, binutils, gcc, glibc) environment for the ARM, compiling the kernel with the correct drivers and bootstrapping for the ARM.
Am I right? Or did I miss something?
Click to expand...
Click to collapse
Well, kinda. Where do you intend to get "correct drivers" for Diamond
Its not that easy, since HTC doesnt provide 'em
Android NBHCREATOR [v0.3] on Ubuntu. FROYO SUPPORT & ADVANCED SETTINGS [July-29-2010]
NBHCreator v 0.3
NBHCreator makes the nbh file for flashing android to nand.
This utility works for Vogue, Polaris and Kaiser.
Currently supporting Donut, Eclair and Froyo
Prerequisites:
1. you need to be running Ubuntu (other Debian distros may work, give it a try) NBHCreator v2.0 will be cross-platform
2. you need to have wine installed ( I am using v1.1.42)
Make sure to "Completely" uninstall previous versions before installing newer versions.
Directions as follows:
a. select the zImage you wish to make an nbh for... try one from here:Working Kaiser GPS!! or here:DZO
b. change parameters to your liking...
c. click on the "compile" button...
d. select output folder.
and Flash Away...
Please Search for how to flash if you don't know how.
that being said...
I welcome any and all criticisms of this program
and I would appreciate any advice, suggestions, questions or comments.
Version 0.3b
-Fixed Window issues.
-For now...do not save output to a FOLDER on the Desktop.
-DOES NOT WORK YET WITH 2.6.32 ZIMAGES
Version 0.3 (07-29-2010)
-Now Supporting Froyo
-New Advanced Settings for things like Clock speed and Memory.
-Added a Date Stamp option for output filename.
-Removed internal Error checking[/B]
-This version has window issues with the xfce desktop environment. fixed in 0.3b
Version 0.2b (07-01-2010)
-Fixed false errors when creating for Vogue and Polaris
Version 0.2 (06-15-2010)
- Added ability to select zImage with name extentions ie... "zImage-12-06-10"
- Output filename now refects device type ie... "VOGUIMG, POLAIMG and KAISIMG"
- Added some error checking to make sure nbh was built correctly
- misc internal code fixes.
-False Error messages are popping up for vogue and polaris. Resulting nbh should still be usable. Fixed in 0.2b.
Version 0.1 (06-09-2010)
- should work for Kaiser, Vogue and Polaris
- Device specific options
- Settings for hw3d (donut/eclair)
- Settings for Resolution 240x320, 320x428, 320x480
- Settings for Panel Type 1, 2, 3
- Settings for Battery Capacity
- Settings for ppp.nostart (Data)
- May not work with loser's editor (let me know...)
- more options to come
- NBHs are all being named KAISIMG.NBH will be fixed in v0.2
Honestly? I think it rocks, since I'm to lazy to build my own NBH's
I see the similarities, and also the differences, and I think you should continue development personally, it's a different approach, and I can see the possibility to add to it by being able to include boot splashes perhaps, or edited initrd/zimage combinations for instance.
So yeah, keep at it
Yep, sounds like a great idea. A nbh editor is good for beginners, but it would be nice to be able to build your own. Could open up a lot of opportunities for customization.
Just make a Windows and a Mac port as well, for the future.
ok....so far progress is going along very well. I have this functioning on my setup
but I still have to work out making it transferable to other computers.
while I work on this, are there any additions that you would like to see added.
I will see if I can squeeze any changes into the beta release.
What language and GUI toolkit are you using?
It would be fairly portable if written in Python with GTK or Tk.
I am using gambas2 in ubuntu.
I am still trying to port my visual basic knowledge to gambas. it doesn't all function the same.
I have minimal experience in Python. but if you know any good tips I am all open for suggestions.
Now available for testing
really???? no feedback at all???
I have to get around to install Ubuntu, and I don't have the hard disk space for it just yet. Been meaning to go buy a terabyte hard drive to dual boot.
got sources or anything like that so I can haz on gentoo?
currently attempting to break open the deb, will fall back to a vm in worst case.
Edit: As I expected, I found the solution right after posting. Run NBHCreator.gambas from /usr/bin
I'm fairly new to Ubuntu and I've never use Wine before so can't work out how to get this running
The package installed, along with it's dependencies. Now what? How do I run it?
Sorry if this is basic stuff...
richard.
Working ok here. Still need to flash it onto my Kaiser - will report back if I find any problems.
Thank - this is a handy little tool
Edit: Hmm, output file only 4.8K so something is not right. Probably down to me so I'll keep playing.
richard_s said:
Edit: As I expected, I found the solution right after posting. Run NBHCreator.gambas from /usr/bin
richard.
Click to expand...
Click to collapse
The install deb should have created a 'start menu' item under /Applications/Other/NBHCreator
that is confirmed under the default Ubuntu window manager 'Gnome'
however I have not tested it in KDE or any other non-gnome window manager.
what window manager are you using?
poly_poly-man said:
got sources or anything like that so I can haz on gentoo?
currently attempting to break open the deb, will fall back to a vm in worst case.
Click to expand...
Click to collapse
let me know if you get it. I don't have the source available at the moment. it's on my wife's computer.
richard_s said:
Working ok here. Still need to flash it onto my Kaiser - will report back if I find any problems.
Thank - this is a handy little tool
Edit: Hmm, output file only 4.8K so something is not right. Probably down to me so I'll keep playing.
Click to expand...
Click to collapse
the resulting nbh must be 3M
DON'T FLASH IF IT ISN'T 3M.
make sure the zImage file is named 'zImage' and not somthing like 'zImage-12-06-10'
I am fixing the next version to allow different names for zImage.
mnjm9b said:
the resulting nbh must be 3M
DON'T FLASH IF IT ISN'T 3M.
make sure the zImage file is named 'zImage' and not somthing like 'zImage-12-06-10'
I am fixing the next version to allow different names for zImage.
Click to expand...
Click to collapse
No - I won't be flashing it! The file name is definitely just 'zImage'. Oh well I'll wait for the next version and try again.
richard_s said:
No - I won't be flashing it! The file name is definitely just 'zImage'. Oh well I'll wait for the next version and try again.
Click to expand...
Click to collapse
I haven't built in a error log into the program but could you run
the NBHCreator.gambas in a terminal and post the output.
what device are you building for and what are your settings?
After restarting Ubuntu your program it is all working as expected. Sorry about that - I should have thought to try that first
yeah, had to throw it into a virtual machine. Nice tool, though.
If someone describes the process in great detail (including the binary formats and all that), I can make a slightly more portable version, if you'd like.
I will be releasing a more cross-platform version after I work out all the bugs.
Keeping it ubuntu for now keeps the distribution of a crappy program to a minimal.
on that note... V0.2 will be out very shortly.
this will address
-input filename variations ie.. 'zImage-12-06-10'
-output filename specific to correct device ie.. 'VOGUIMG,POLAIMG and KAISIMG'
-error checking
-misc fixes
Ok, so...
At first I found a ReactOS offical ARM port.
It is here(delete spaces, forum still prevents me from inserting any link): htt p:/ /ww w. rea cto s.or g/wik i/ARM_ Port
At second I don't understand it at all so if anyone are good in this type of thing, tell us is it possible to have it working UNDER HARET?
And finaly at third If yes, is it will be possible to run any applications excluding a orginals one?
And that's all
P.S. There is already a topic here(ht tp:/ /foru m.xd a-deve lopers.co m/sho wthre ad.php?t =791800 ) but it is quite old and not for our device.
Ew, why would you want React on your phone...?
i'd say ehm.. for the heck of it?
don't really think there is a point tho in rOS, both windows that comes natively and android have a massive userbase and for a 'full OS' there is already someone building linux version of Ubuntu.
beside that, the React OS makes use of 'windows' binaries (from what i read on their website.) which are in x86 format as far as i believe, running them on an ARM processor isn't likely to work.
if i'm incorrect please correct me
Not really, all the binaries were written by ReactOS Team and they are open source... So in practise we can compile it and have it running on ARM processor.
And why? Simply. If all the dll's and files can run exe files we should be able to run normal applications like firefox, flash, etc. Maybe not at maxiumum speed(because of alpha build of ReactOS) but still it can be quite useful.
I didn't managed to build it. As far as I read it is imposible beacause of compiler which doesn't compile it correctly, or at all.
If anyone have any ideas how to do it tell us...
P.S. The full source of ReactOS + additional appliactions included is avaible at ReactOS main page.
Well ReactOS to my knowledge doesn't run that well on x86 machines, so I doubt our tired old phones will run it very well...
Rhodbuntu isn't good enough...? I'd say that's your best hope - in theory it will run FF & flash...
ReactOS of course is not the faster system ever but it it a only(actualy) operation system that is in open source and have a fully rewritten binaries, etc.
And BTW you still can't have a flash and Java(SE) running on armel(rhodbuntu)
mafiu95 said:
ReactOS of course is not the faster system ever but it it a only(actualy) operation system that is in open source and have a fully rewritten binaries, etc.
And BTW you still can't have a flash and Java(SE) running on armel(rhodbuntu)
Click to expand...
Click to collapse
Ah didn't realize. What makes you think it'll work on React? lol
Theres a possibility. But as I test the recent version out, there are problems with it, so I dont think its a good idea to port. There are issues from clicking to how things are displayed to windows sticking & not listening to me when I click close or minimize/maximize.
So, this is post made by man with obsession.
I need help with idea.
I told myself i need Amiga emu faster than pocketuae.
Uae4all is kind of emu that could be perfect for porting, so i decided to give it a try.
Natural choice was use of gizmondo port(wince device, similar envinronement etc).
Giz port relies on 0.6.3 so it is old and not sophisticated, but just works for df0: games from a500, and it has minimal amount of tricks made by porters in further developement, that's the point of choice.
I am not a programmer, so you must realize word "desperation" in whole context.
So, i tried to compile sources under cygwin and winxp, after NUMEROUS woes with makefile, sdl libs, etc etc - it compiles with newest mamaich compiler with precompiled SDL set(used to making qemu - ONLY toolset that works for gizuae4all sources - that's interesting) with some warnings - mainly related to FAME m68 core, unfortunately :E, but no general errors.
GUI works, there is no touchscreen support, dpad works, hardenter chooses cursor chosen options, filemanager works fine.
Problems start after "Run":
- uae4all has LED info about df0: and df1: drives, and i can see that df0: is accesed, sectors are changing, i assume it works fine(40's sector boots properly), but emulator quits after few seconds(i see decrunching of rick dangerous 2 cracktro PROPERLY, for example, then it crashes),
- reboot without disc in df0: results in proper 3 color boot defaults of a500(with kick 13), and proper 1 colour(violet) 3.1 boot defaults, but it quits when "begging hand"(1.3) or disc(3.1) img should appear.
Assuming:
some Amiga generated data are displayed, other ones crashes emulator.
I am not sure, where problem lies.
Now:
- is there someone that compiled scummvm for wm/wince here, or have some experience with SDL? I can see it is getting forgotten method, but still useful, though.
(info from original makefile for giz, note SDL_mixer here;/):
SDL_BASE = C:/code/Gizmondo/GizSDL
LDFLAGS = -L$(SDL_BASE) -lSDL_mixer -lSDL -lzlib -static
I tried to compile libs(whole SDL, Mixer, zlib one after another) from sources, but NONE of them compiled properly. So i took easy way of using precompiled set + small modifications...well..there are no lib related errors at last, then..
- or maybe, if it is compiler/crosscompiler envinronment problem, is there someone, that could help me to set up tools properly?
Remember, compiling ends with exe, so i am not sure about this. Other thing i would try is using mingwce-gcc set, but i did not succedeed in proper set-up with that one.
I can provide sources, toolpack or whatever after FIRST response from anyone, that can help or is interested in idea.
upd: ahh, btw gizmondo exe is not working at all, it quits regardless of (wince/wm versions of)dlls replacement. Mainly for hardcoded file/path reasons.
<post written while listening to http://demovibes.de:8000/necta192.mp3 >
Screenshots(skip resolution and all, it just doesn't matter at this moment..i think, only that matters is 4rd one, crash moment, 3.1 kick bkg colour visible):
Hi
* Please help keeping the noise level low: Don't ask for ETA (stuff will be anounced), use Thanks buttons to say thx, etc.
* This will work on "fully unlocked" WP7 devices only and is not limited to specific phones
thx, dcordes
HaRET (Handhelds Reverse Engineering Tool) has been used on smartphones and PDAs with previous WinCE (Windows Mobile) versions to
* boot the Linux kernel (=> use Linux based OS like Android)
* obtain information about hardware and software (=> reverse engineering) in order to accordingly modify the Linux kernel (drivers).
Famous HTC devices that are capable of running HaRET are the QSD8250 based HTC HD2 and a wide range of MSM7xxA based phones like the diamond, raphael and touch pro 2.
WP7 is and will be shipped on many devices with quality hardware. In order to be able to run Linux on these, a novel aim is to investigate the use of HaRET on WP7 based devices. WP7 is known to posess several mechanisms to prevent this.
A discussion about the problem has beend started on the official HaRET development mailing list by Jaxbot:
http://lists.linuxtogo.org/pipermail/haret-devel/2012-January/000150.html
You need to send a subscription mail in order to write to the list. The original creators of HaRET as well as many good developers with low level skills (from XDA: Cotulla, NetRipper, cr2) are subscribed to it but maybe not many of them have access to a WP7 device.
HaRET source code repository with history:
http://git.linuxtogo.org/?p=groups/haret/haret.git
Documentation of the HaRET project (publicly accessible wiki):
http://htc-linux.org/wiki/index.php?title=HaRET
See http://htc-linux.org/wiki/index.php?title=HaRET/Documentation#Development for how to compile.
We should discuss the technical possibilites and challenges (if any ) about this project in this thread.
Update: Lots of insight has been gained. Since progress is rapid, uptades are not listed here yet. Please read the full thread for now.
Hi, I and all WP7 users waiting for your result HaRET project.
Thanks for your great work. And I would like to send you a cup of Heiniken beer.
Confirmation number: 0W3951910E743222Y
Hey dcordes,
I did a bit of housecleaning on this thread as I would hate to see this become your old Android-HD2 port thread
I want to see some real discussions going on in here (for a change).
So, HaRET must be, if memory serves me well, developed based on the processor, right? If it worked so well for the HD2, considering that most WP7+ devices from HTC also use Snapdragon's.... it should only take a few tweaks to get it to run (at least compatibility with HW) with most HTC WP7+ devices. The problems will be (I guess):
* Porting over from WM6.5 to WP7+ (may not be as bad as it sounds);
* Making sure that whatever this thing is coded with, it does not have interoplock code running on it (which I think will be kinda difficult considering that several apps that require access to less critical areas of the device require this). if it is interoplocked, then you will run into the issue of multiple versions out there (see Heathcliff's interopunlock thread to see/learn about the HTC variants on the new drivers, etc);
* Drivers, kernels, etc... but I believe that the HW specs between WP7+ devices and the HD2 are not so different, so you may even be able to get the same kernels to work with a few tweaks.
My Titan is already drooling with expectation
Please let me know if this thread needs further cleaning....
Good to see you back.
I feel somewhat obligated to make an appearance, then
Here's what I know, on the WP7 side of things:
A lot of APIs were removed, but the core pieces of CE still remain. I don't know what HaRET does to load Linux into the memory, but I would be shocked if it wasn't possible.
Part of the APIs that were removed were GUI related. This is why HaRET segfaults when you try to load it on a full unlocked device. If these pieces were removed, making it rely only on the command line, the loader might actually work, more or less. A WP7 Silverlight app could easily be built to serve as a launcher for it.
Those pieces aside, it is basically the technical pieces that have yet to be dug into that we are bound to run into. Curious to see what will happen, glad to see this getting some attention Cheers!
for HD2 ok, but for other phone that hasn't SD card?..... i hope however Ubuntu 0.4 will go on magldr, right?
nikola360 said:
for HD2 ok, but for other phone that hasn't SD card?..... i hope however Ubuntu 0.4 will go on magldr, right?
Click to expand...
Click to collapse
Most wp7 phones have the SD built in or in some form of flash storage capability. But you do make a good point, I guess.
Sent from my 4.7" Titan.... My device IS bigger than yours.
It's still Windows CE, there's nothing to emulate but the missing APIs
As the MAGLDR for Samsung focus/omnia7 will be out in around just now , maybe it will be possible to manage smthng
nhathoa egzthunder1, thank you very much for the kind welcome
Jaxbot said:
Here's what I know, on the WP7 side of things:
A lot of APIs were removed, but the core pieces of CE still remain. I don't know what HaRET does to load Linux into the memory, but I would be shocked if it wasn't possible.
Part of the APIs that were removed were GUI related. This is why HaRET segfaults when you try to load it on a full unlocked device. If these pieces were removed, making it rely only on the command line, the loader might actually work, more or less. A WP7 Silverlight app could easily be built to serve as a launcher for it.
Those pieces aside, it is basically the technical pieces that have yet to be dug into that we are bound to run into. Curious to see what will happen, glad to see this getting some attention Cheers!
Click to expand...
Click to collapse
I don't have much insight on how the kernel is loaded either. Obviously it's important for HaRET to have a non-protected memory region it is allowed to write to and then there is something called trampoline that will flush remaining memory and execute the kernel...
GUI: http://htc-linux.org/wiki/index.php?title=HaRET_Documentation#HaRET_commands
"HaRET is fundamentally a command-line driven application."
Can you try to rename your default.txt into startup.txt ? In presence of startup.txt inside the directory of the exectuable, HaRET will automatically run commands inside that file, rather than first showing the GUI. (Maybe it will still crash cause it still depends on the libraries although they won't be used ? See linload below)
Also be sure to create a file named earlyharetlog.txt and check the resulting log in haretlog.txt which would be a good thing to put on the mailing list.
The other way to invoke HaRET commands is through haretconsole (also check doku above). Once the gui shows you can tap a listen button and haret will launch a telnet server. You can then connect remotly from your computer OR (and that might become our replacement gui from a local telnet client on the phone. There is one available in the wp7 software manager: http://www.windowsphone.com/en-GB/apps/333b1e98-4c72-4cf9-a5d0-9d82b6b18213
One possible way to cut through all GUI right now is the linload feature of haret that will burn loader, kernel, startup.txt and initrd into one single exe . Requires local source code and build environment to create. I think it is very likly that this will not depend on any GUI libs so we should really try in case of startup.txt failure!
Beside linload we might create a HaRET stripped from GUI that will be accessible via haretconsole only until we have a new WP7 compatible GUI.
Regarding compiling: http://htc-linux.org/wiki/index.php?title=HaRET_Documentation doesn't have anything on that. But the source code does: http://git.linuxtogo.org/?p=groups/haret/haret.git;a=tree;f=docs
nikola360 said:
for HD2 ok, but for other phone that hasn't SD card?..... i hope however Ubuntu 0.4 will go on magldr, right?
Click to expand...
Click to collapse
Doesn't matter, why would you need SD card ? I guess if a phone lacks SD, it will come with plenty internal storage that can hold at least a minimal rootfs of any Linux distro.
Yes HD2 Ubuntu will work with magldr, I already picked up the work with that but that's offtopic. I will anounce any news via hd2 ubuntu forum section and twitter.
EDIT: If somebody is willing to try, I can create a linload for HD2s that have WP7 flashed. This will be a perfect test setup because we have a known working Linux kernel for the HD2.
dcordes said:
nhathoa egzthunder1, thank you very much for the kind welcome
I don't have much insight on how the kernel is loaded either. Obviously it's important for HaRET to have a non-protected memory region it is allowed to write to and then there is something called trampoline that will flush remaining memory and execute the kernel...
GUI: http://htc-linux.org/wiki/index.php?title=HaRET_Documentation#HaRET_commands
"HaRET is fundamentally a command-line driven application."
Can you try to rename your default.txt into startup.txt ? In presence of startup.txt inside the directory of the exectuable, HaRET will automatically run commands inside that file, rather than first showing the GUI. (Maybe it will still crash cause it still depends on the libraries although they won't be used ? See linload below)
Also be sure to create a file named earlyharetlog.txt and check the resulting log in haretlog.txt which would be a good thing to put on the mailing list.
The other way to invoke HaRET commands is through haretconsole (also check doku above). Once the gui shows you can tap a listen button and haret will launch a telnet server. You can then connect remotly from your computer OR (and that might become our replacement gui from a local telnet client on the phone. There is one available in the wp7 software manager: http://www.windowsphone.com/en-GB/apps/333b1e98-4c72-4cf9-a5d0-9d82b6b18213
One possible way to cut through all GUI right now is the linload feature of haret that will burn loader, kernel, startup.txt and initrd into one single exe . Requires local source code and build environment to create. I think it is very likly that this will not depend on any GUI libs so we should really try in case of startup.txt failure!
Beside linload we might create a HaRET stripped from GUI that will be accessible via haretconsole only until we have a new WP7 compatible GUI.
Regarding compiling: http://htc-linux.org/wiki/index.php?title=HaRET_Documentation doesn't have anything on that. But the source code does: http://git.linuxtogo.org/?p=groups/haret/haret.git;a=tree;f=docs
Doesn't matter, why would you need SD card ? I guess if a phone lacks SD, it will come with plenty internal storage that can hold at least a minimal rootfs of any Linux distro.
Yes HD2 Ubuntu will work with magldr, I already picked up the work with that but that's offtopic. I will anounce any news via hd2 ubuntu forum section and twitter.
EDIT: If somebody is willing to try, I can create a linload for HD2s that have WP7 flashed. This will be a perfect test setup because we have a known working Linux kernel for the HD2.
Click to expand...
Click to collapse
I've tried startup.txt, it still segfaults, won't even print out a log from what I can tell. I'll play around with some stuff and report back, though.
ok. I updated wiki and added compilation info http://htc-linux.org/wiki/index.php?title=HaRET/Documentation
UPDATE: I attached a linload for HD2. Could somebody please run it on their WP7 HD2 and tell us what happens? TIA!
What's this? A special version of HaRET that is solely for booting a Linux kernel that is included inside the exe.
linload source: http://git.linuxtogo.org/?p=groups/haret/haret.git
linux kernel source: http://gitorious.org/linux-on-wince-htc/linux_on_wince_htc
i have a stupid question, what is reason test it on HD2 where you can install android without problem. on native wp7 phones you will not run this app as I know. or maybe I'm wrong? maybe on custom rom?
I have mozart interop unlocked, I can test something if there will be some staff for my phone.
ronalgps said:
I'm going to test this mate
Click to expand...
Click to collapse
Thanks a lot. this is going to be interesting!
Could you create a file called earlyharetlog.txt inside the same directory of linload.exe ? I don't know if this works but see if it will give you a logfile in the same directory after starting linload.exe
I bet it will just crash, just like normal HaRET.exe when using startup.txt
dcordes said:
Thanks a lot. this is going to be interesting!
Could you create a file called earlyharetlog.txt inside the same directory of linload.exe ? I don't know if this works but see if it will give you a logfile in the same directory after starting linload.exe
I bet it will just crash, just like normal HaRET.exe when using startup.txt
Click to expand...
Click to collapse
Tried it with earlyharetlog.txt in the same directory. No log is spit out, and while there is no error code when running the EXE, it crashes before I can even pull the running processes list.
ok does it show anything ? loading screen or so ? it's what I expected. if you compiled haret.exe before, linload takes 2 seconds to build. It might just be the exact haret.exe ...
dcordes said:
ok does it show anything ? loading screen or so ?
Click to expand...
Click to collapse
Nope, no signs that it even loads, except for the fact the Win32 API reports NO_ERROR after shell executing it.
From what I saw, linload.exe cannot run under WP7 because it depends on libgcc_s_sjlj-1.dll, witch cannot be found in WP7. You can try running Haret.exe. All the necessary APIs are there, so no problem about UI related functions. Only one function is missing: SetKmode, witch is used by Haret to take kernel mode privileges, to flush the memory. In WP7 this function is not available and i don't know any workaround about this. We can try to recompile Haret from source, remove SetKmode call from output.cpp and memory.cpp, update functions ordinals in the import table for new Haret.exe to match those from WP7 coredll.dll (i'm not sure about this, maybe can work without matching ordinals) and see if we have a working GUI.
Thanks for this insight, minDark. may I ask how you found out about the missing dependencies?
It's not so nice that the kernel mode function is missing in WP7. How are we going to start the kernel without it?
I did as you proposed and compiled haret.exe without it. I just commented out lines containing setkmode. But I didn't change the ordinals stuff because I have no idea what that is.
no-kmode haret.exe with minDark's proposed kmode patch is attached. Any WP7 device owners welcome to test.
diff to current haret.git HEAD:
Code:
haret$ git diff
diff --git a/src/memory.cpp b/src/memory.cpp
index ccba659..53c0826 100644
--- a/src/memory.cpp
+++ b/src/memory.cpp
@@ -320,7 +320,7 @@ err: VirtualFree (pmWindow, 0, MEM_RELEASE);
if (slot >= PHYS_CACHE_COUNT)
{
// Go into supervisor mode
- SetKMode (TRUE);
+// SetKMode (TRUE);
cli ();
cpuFlushCache ();
@@ -333,7 +333,7 @@ err: VirtualFree (pmWindow, 0, MEM_RELEASE);
// Back to user mode
sti ();
- SetKMode (FALSE);
+// SetKMode (FALSE);
}
// Move least recently used slot to front
@@ -354,12 +354,12 @@ void memPhysReset ()
if (pmInited)
{
// Go into supervisor mode
- SetKMode (TRUE);
+// SetKMode (TRUE);
cpuFlushCache ();
// Restore the page table entries
for (int i = 0; i < 16 * PHYS_CACHE_COUNT; i++)
pmPT [i] = pmOldPT [i];
- SetKMode (FALSE);
+// SetKMode (FALSE);
VirtualFree (pmL2PT, 0, MEM_RELEASE);
VirtualFree (pmWindow, 0, MEM_RELEASE);
diff --git a/src/wince/output.cpp b/src/wince/output.cpp
index cc65d40..e4be7ed 100644
--- a/src/wince/output.cpp
+++ b/src/wince/output.cpp
@@ -276,9 +276,9 @@ prepThread()
// All wince 3.0 and later machines are automatically in "kernel
// mode". We enable kernel mode by default to make older PDAs
// (ce2.x) work.
- Output("Setting KMode to true.");
- int kmode = SetKMode(TRUE);
- Output("Old KMode was %d", kmode);
+// Output("Setting KMode to true.");
+// int kmode = SetKMode(TRUE);
+// Output("Old KMode was %d", kmode);
}
// Initialize the haret application.
I download it through my hd7 but when I try to open it stated this file isn't safe to open in your windows phone.
Ttblondey said:
I download it through my hd7 but when I try to open it stated this file isn't safe to open in your windows phone.
Click to expand...
Click to collapse
You have to deploy it to your phone, then execute it with native code.