Not sure where to post this... but now that the Android OS source is realsed, what is needed to compile a native version for Hermes?
http://source.android.com/download
MrCeddy said:
Not sure where to post this... but now that the Android OS source is realsed, what is needed to compain a native version for Hermes?
http://source.android.com/download
Click to expand...
Click to collapse
Already on kaiser, maybe can be ported:
http://forum.xda-developers.com/showthread.php?t=396782
Keep in mind this is the official OS which was released today.
Its been noted that its not that easy.
1) the CPU in the Hermes is a older ARM that doesn't support all the needed instructions.
2) We couldnt "port it", it would need to be recompiled for the Hermes's older ARM, and that would be HARD.
3) We would then need Storage/wifi/touchscreen/ect ect drivers, and someone would need to write them, theres not going to be a device with the same chipset as the Hermes to steal the drivers off, like there is for the Kaiser.
So, unless you know a lot about writing drivers/recomplieing linux, tisnt going to happen
veyka said:
Its been noted that its not that easy.
1) the CPU in the Hermes is a older ARM that doesn't support all the needed instructions.
2) We couldnt "port it", it would need to be recompiled for the Hermes's older ARM, and that would be HARD.
3) We would then need Storage/wifi/touchscreen/ect ect drivers, and someone would need to write them, theres not going to be a device with the same chipset as the Hermes to steal the drivers off, like there is for the Kaiser.
So, unless you know a lot about writing drivers/recomplieing linux, tisnt going to happen
Click to expand...
Click to collapse
Thanks for your input!
So, are you planning to fiddle with the idea??
joshkoss said:
Already on kaiser, maybe can be ported:
http://forum.xda-developers.com/showthread.php?t=396782
Click to expand...
Click to collapse
so somebody wrote the drivers for kaiser ??
Originally Posted by veyka
Its been noted that its not that easy.
1) the CPU in the Hermes is a older ARM that doesn't support all the needed instructions.
2) We couldnt "port it", it would need to be recompiled for the Hermes's older ARM, and that would be HARD.
3) We would then need Storage/wifi/touchscreen/ect ect drivers, and someone would need to write them, theres not going to be a device with the same chipset as the Hermes to steal the drivers off, like there is for the Kaiser.
So, unless you know a lot about writing drivers/recomplieing linux, tisnt going to happen
Click to expand...
Click to collapse
if somebody did manage to get it working in kaiser, it can be done for hermes ?
don't we already have working linux ports for hermes? can't the drivers be pulled from there ?
Related
CAN ANYBODY GUIDE ME ON HOW TO INSTALL WM6 ON MY SE M600i
of course NOT!..
its like saying "can i LOAD PSP to my Gameboy Color"
double_ofour said:
of course NOT!..
its like saying "can i LOAD PSP to my Gameboy Color"
Click to expand...
Click to collapse
lol lol
ravinbajaj said:
CAN ANYBODY GUIDE ME ON HOW TO INSTALL WM6 ON MY SE M600i
Click to expand...
Click to collapse
You cannot put Windows Mobile to SE M600i, It is a diffrent OS platform.
hahahahaha
can I load the ROM from other type? like can I load a WM6 from an Atom to a XDA III?
That's about like asking my wife if I can have a sex change...
I really don't know whether to laugh or cry at your ignorance.
sorry for this silly question
I was considering if it's like PC OS that have almost the same core and can be modified before deploy to another station.
imnewer said:
sorry for this silly question
I was considering if it's like PC OS that have almost the same core and can be modified before deploy to another station.
Click to expand...
Click to collapse
It could be possible like using the HTC Wizard rom for a Charmer... This has already been done... Still it's a silly question without having checked the inner hardware, etc.
So yes, this CAN be done... (if the hardware is not too different)
It is not like PC OS at all. I should probably send you to the WiKi but I do have a bit of time to burn so here is the explanation:
First, you can not load Windows Mobile on to devices with other OS. It would be the same as trying to run Windows on a Mac or Mac OS on a PC, the BIOS (or in our case bootloader) wouldn't support it, plus I am fairly sure there is some difference in processor architecture so it can't "understand" the code at all.
Second you can not change ROM between different Windows Mobile devices because unlike desktop PC Windows Mobile comes in an image bundled with drivers and other hardware specific components. Flashing the wrong image will brick the device, and there is no such thing as "generic" WM installation.
To conclude: You can not put WM on anything other that the devices that have official or unofficial update to this OS.
thank you so much guys for guide me a lot.
I knew that different devices might built in different architectures, but some of the devices use same series of cpu. and also did concern about different hardware need respective driver...but not aware of the encryption there might be...
thx for the explanation~
levenum said:
It is not like PC OS at all. I should probably send you to the WiKi but I do have a bit of time to burn so here is the explanation:
First, you can not load Windows Mobile on to devices with other OS. It would be the same as trying to run Windows on a Mac or Mac OS on a PC, the BIOS (or in our case bootloader) wouldn't support it, plus I am fairly sure there is some difference in processor architecture so it can't "understand" the code at all.
Second you can not change ROM between different Windows Mobile devices because unlike desktop PC Windows Mobile comes in an image bundled with drivers and other hardware specific components. Flashing the wrong image will brick the device, and there is no such thing as "generic" WM installation.
To conclude: You can not put WM on anything other that the devices that have official or unofficial update to this OS.
Click to expand...
Click to collapse
have a look at the facts you can run windows xxxx on a imac and mac mini and you can run mac osx on a pc so it may be possible to run windows mobile on se m600
jim
HI-JET said:
have a look at the facts you can run windows xxxx on a imac and mac mini and you can run mac osx on a pc so it may be possible to run windows mobile on se m600
jim
Click to expand...
Click to collapse
Well it may very well be possible, but not with the tools available to us or any other average joe.
masr1979 said:
Well it may very well be possible, but not with the tools available to us or any other average joe.
Click to expand...
Click to collapse
go to link and read for you self how it done run oxs on a pc
http://www.osx86project.org/
---------------------------------------------------------
go to link and read for you self how it done run windows on imac and mac mini
http://www.apple.com/macosx/bootcamp/
jim
this thread has to be the dumbest one ive seen in awhile..
HI-JET said:
go to link and read for you self how it done run oxs on a pc
http://www.osx86project.org/
---------------------------------------------------------
go to link and read for you self how it done run windows on imac and mac mini
http://www.apple.com/macosx/bootcamp/
jim
Click to expand...
Click to collapse
I wasn't referring to osx on pc as I'm well aware of that. The question is can you direct me to a link where it shows some readily available hardware and software to port WM6 to a sony M600? not that I could do anything with the info, simply for arguments sake.
it becomes boring...Linux can be load on Xbox...just imagination, maybe there will be some way to load a WM rom within sort of hardward series...(like Dopod 828 & 838 & P800 are most the same series for TI cpu etc)...
Settle down, pleas I did not mean to start a debate.
When I was talking about Mac and PC I just wanted to use the older, Motorola processor based architecture as an example. (Forgot Macs use Intel these days).
Any way - Windows Mobile like any OS can be adopted to any platform - in theory, but the radical changes required are beyond the scope of private enthusiasts such as on this site.
Even if processor architecture is the same, you would at the very least have to rewrite all the drivers for the given device, and that is an enormous task.
it would most likely require access to the sourcecode (not something ms let you download being they hate opensoufce) and a team of developers to make new developing to support hardware they might not have any spcs on (not something sonyE hand out at the door)
depending one how much backward enginering would be required
1 man year of developer time
for each enuiqe platform
this is not counting the lawsuits from ms and or sonyE
and the man years of answering questions of people wanting to know if it works on their old nokia 3110
I cannot work out how to enable HSDPA on my commodore 64, could some one tell me if installing WM6 would help with this?
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
im not sure i get whats going on with this new winp7 rom thats been posted.
has anyone run it on an emulator? if not how do you know its even real? and when you guys are talking about dumping it what exactly does that meen, sorry for nuub questions but im not that up on the dev scene
Well, it can't be run in the Emulator, as the Emulator uses x86 ROMs, while actual devices are based on the ARM architecture, so basically as of now no one can say for certain if it is real (although some things look promising).
As the ROM is intended for use on a not yet known device it also can't be flashed to a device anyone owns.
Dumping means that they are trying to extract the files which are contained in the ROM image, which is difficult as the format is different from WM6.5 and no documentation exists for it.
If they can extract the files they then could be repackaged to known formats which then could be flashed - nobody knows if that will boot on any existing device though.
StevieBallz said:
Well, it can't be run in the Emulator, as the Emulator uses x86 ROMs, while actual devices are based on the ARM architecture, so basically as of now no one can say for certain if it is real (although some things look promising).
As the ROM is intended for use on a not yet known device it also can't be flashed to a device anyone owns.
Dumping means that they are trying to extract the files which are contained in the ROM image, which is difficult as the format is different from WM6.5 and no documentation exists for it.
If they can extract the files they then could be repackaged to known formats which then could be flashed - nobody knows if that will boot on any existing device though.
Click to expand...
Click to collapse
ahh ryt. i get the emulator part, i actually have the visual studio 2k10 for win phone so i understand that there is a difference between computer based roms and mobile roms. but i thought maybe there was a tool out ther that could use mobile roms, lik a virtual box for phones, i know that people know the hardware specs for win phone 7.. 3 buttons, 1g processor, capacative touch screen etc etc so i thought maybe sumone had used it through a virtual phone
96edwy said:
... i know that people know the hardware specs for win phone 7.. 3 buttons, 1g processor, capacative touch screen etc etc so i thought maybe sumone had used it through a virtual phone
Click to expand...
Click to collapse
No, we've been told the minimum specs by MS.
Casey
Perhaps the old Emulator from the WinCE6 SDK might be able to run it, as it had to support native ARM Code, it had to emulate the CPU architecture, but most likely features of newer ARM Cores are missing and WP7 seems to be using them.
But obviously (as seen from the emulator) there is a way to compile the System to the x86 architecture, so maybe Intel gets around to include a decent graphices core and we might see some ULV Atom powered WP7 phones - or not ;-)
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.
Windows 10 compiled for the original Surface RT devices has leaked.
Source: BetaWiki
It would be super cool if this community managed to create a working image for the OG RTs (de-bombed & with correct drivers). Anybody here who could share the leaked image with us?
Avonlady said:
Windows 10 compiled for the original Surface RT devices has leaked.
Source: BetaWiki
It would be super cool if this community managed to create a working image for the OG RTs (de-bombed & with correct drivers). Anybody here who could share the leaked image with us?
Click to expand...
Click to collapse
Well, it hasn't exactly leaked yet. Do you have the actual file? I can add the correct drivers and remove the timebomb if I can get my hands on it
Unfortunately no, I don't have access to BetaArchive's FTP. But I would be shocked if nobody on this forum had... Fingers crossed it gets reuploaded soon.
Avonlady said:
Unfortunately no, I don't have access to BetaArchive's FTP. But I would be shocked if nobody on this forum had... Fingers crossed it gets reuploaded soon.
Click to expand...
Click to collapse
Another thing we need to find out, does it require configuration to boot? Or is it just a bootable install image?
Well I manage to get the file. Its not iso its a zip. But I have honestly not Idea what to do with it, and I try in all inventive ways, LOL!. I could make a torrent file if any its interested on. With the compromise on do a tutorial later if some one manage to do anything with it.
Qiangong2 said:
Well, it hasn't exactly leaked yet. Do you have the actual file? I can add the correct drivers and remove the timebomb if I can get my hands on it
Click to expand...
Click to collapse
To benefit the community and have more people working on this, Did you think you could do some quick howto on doing this. Or point us on the right learning path! Im so eager to learn this stuff!
hackinc2000 said:
To benefit the community and have more people working on this, Did you think you could do some quick howto on doing this. Or point us on the right learning path! Im so eager to learn this stuff!
Click to expand...
Click to collapse
In the end, I won't know how exactly to fix the timebomb unless I can see the file itself. Replacing the drivers are just as easy as copy paste into the wim file.
Qiangong2 said:
In the end, I won't know how exactly to fix the timebomb unless I can see the file itself. Replacing the drivers are just as easy as copy paste into the wim file.
Click to expand...
Click to collapse
PM you in a moment!
I've been trying to get this running on Surface 2, the way I've been trying with this is a dual boot with RT 8.1 and I've partitioned my device to allow roughly 12GB for the Windows 10 installation.
Unfortunately there is an issue with nvpep causing a BSOD that is beyond my abilities to solve, without nvpep nothing else will work. I don't have a Surface RT to test with but I read that this issue does not manifest on those devices, however it still won't work out of the box.
I've pieced together some information that might be of help if your trying to install that applies to RT and 2.
Make sure secureboot debug policy is applied and don't forget to enable testsigning and nointegritychecks. If you have Jailbreak killing updates installed its probably faster to factory reset your device.
You will need to replace sdbus.sys and ststor.sys in \Windows\system32\drivers\ with versions from RT 8.1.
You will need to edit the registry on build 15035 to disable UAC - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System - EnableLUA set value to 0.
Before booting 15035 you will need to create new directory on EFIESP in \EFI\Microsoft\Recovery and then create an empty BCD Store in that location.
If you don't add the Surface 2 drivers it will actually boot to the desktop but no devices will work (Pretty much every device requires nvpep up and running first), you can play around with it using a USB keyboard and mouse but its a little pointless at the moment.
Would it be possible to share the build with wider community, so more people can have a shot at getting it up and running? I know I would love to play around with it.
Avonlady said:
Would it be possible to share the build with wider community, so more people can have a shot at getting it up and running? I know I would love to play around with it.
Click to expand...
Click to collapse
Please make no mistake on the significance of said leak. There is no other known more-recent ARM 32bit Windows 10 build available on the Internet. The driver hacking community could appreciate a more open leak very much (just look at what it did to the Lumia 950/XL hacking scene around gus33000).. Sites like uup dot rg-adguard dot net fail to list this build.
Avonlady said:
Would it be possible to share the build with wider community, so more people can have a shot at getting it up and running? I know I would love to play around with it.
Click to expand...
Click to collapse
Found this on MDL (Mega.nz Download - I can't seem to post full URL's so remove the "_")
Code:
h_t_t_p_s:/_/mega.nz/#!mJ8BSABD!kgdXbJUTKDehFlAMJ9EXswgZs1gYvijeMEZjDNeBfqU
ChumpDrive said:
Found this on MDL (Mega.nz Download - I can't seem to post full URL's so remove the "_")
Code:
h_t_t_p_s:/_/mega.nz/#!mJ8BSABD!kgdXbJUTKDehFlAMJ9EXswgZs1gYvijeMEZjDNeBfqU
Click to expand...
Click to collapse
I might try it.
Well, what about compatibility with the Lumia 2520? Do you think it would be possible to install Win10 or at least 10S on that one too? It runs 8.1RT, like the old surface RT...
mivas said:
Well, what about compatibility with the Lumia 2520? Do you think it would be possible to install Win10 or at least 10S on that one too? It runs 8.1RT, like the old surface RT...
Click to expand...
Click to collapse
h-t-t-p-s-:-/-/-betawiki.net/wiki/Windows_10_build_15035
lxy3427 said:
h-t-t-p-s-:-/-/-betawiki.net/wiki/Windows_10_build_15035
Click to expand...
Click to collapse
Thank you very much for the link.
Sadly, it says that it doesn't support Lumia 2520... It requires a driver...
I think I won't even ask for unreleased protos, like the Lumia 2020 ("Illusionist") etc
Here's a guide how to install this build on Lumia 1520: https://translate.google.com/translate?sl=auto&tl=en&u=https://www.ithome.com/0/468/534.htm
Avonlady said:
Here's a guide how to install this build on Lumia 1520: https://translate.google.com/translate?sl=auto&tl=en&u=https://www.ithome.com/0/468/534.htm
Click to expand...
Click to collapse
Wow! Soo Nice! This makes me want to buy this phone... :good:
Can someone upload these files somewhere else from baidu?
Hello!
This is a guide to install Windows 10 ARM on Surface RT 1/2. https:_/_/_m_.ithome.com/html/469731.htm (remove all _ signs)
What do you think about this?