Related
Android is a new open source mobile operating system that Google developed and an SDK has just been made available.
It would be great to see this ported to the Universal if its possible.
I don't see why it would not run since the Universal can already run Linux (to some extent) and Android is just based on that. Whether and to what extent the hardware can be supported is another question that only our programmers can answer. As we can surely count HTC out on supporting their legacy devices it might not be worth anybodies time in the end.
SDK for Android would not help at all. It is just a set of headers and import libraries. To port something to a device you need complete source codes of its kernel, software, etc. Even more - we don't know hardware requirements for Android. It may require the NOR flash to run from it - and we don't have it on our device at all.
mamaich said:
Even more - we don't know hardware requirements for Android. It may require the NOR flash to run from it - and we don't have it on our device at all.
Click to expand...
Click to collapse
Nobody uses NOR these days, it's too expensive and provides no real
benefit over NAND. The XIP days are over.
I hate java with passion, but i don't see any reason why Android software
will not be running on the universal.
Any news? I mean: can Universal run an Android ROM?
I saw something on tytnII, is there an hope?
can anyone confirm if android requires a customised hardware or minimum requirements....
By The Looks Of It I Shouldnt See Why Not...
I Saw That Video Of It On The Tytn And It Looks Like Its Just A Linux Based Kernel Booting Though Haret.
Theirs Already Some Pretty Good Progress With Linux On The UNI And I Dont See Why It Shouldnt Be Possible To Patch This Up. (Wish I Could But Im Not A Linux Coder )
maybe something like this
(click on the emote)
could be done for univ.
Getting A Replacement
I Get My Replacement XDA Exec On Monday Hopefully So Ill See If I Can Do Anything. No Promises Though
Regards,
OllieD
It looks promising but I am also awaiting the Ubuntu Mobile edition for PCC: it looks awesome!
if it has to run java bytecode
hi a .CAB solution should be possible. tis my prefered choice at present. KVM with class jar anyone??
any news ?
Kaiser can run Android, any ROM for Uni?
In this thread we have Android ported in to a Kaiser, hope someone is working on an Android ROM for UNI!!
It looks very nice the interface
Does anyone knows more info about this?
Thanks
Gracias
Any news on Android for Uni?
I've been trying to get it to work on my ELFin too, but i gave up when i only managed to get the Linwizard running without startx... (i dont know how to telnet and startx -.-)
Any news on this?
I'm thinking of getting a universal but i'm gathering info on it atm!
Has anyone been able to get some real progress on this matter?
I installed this onto my main memory, but when I run it I get a blank screen and the phone vibrates continuously, what am I doing wrong? I think this version is supposed to work on the Universal.
hye !
i also tried to install android on my universal, but it didn't work at all, i only had a black sreen and it vibrate without stopping. if someone has an idea, or a new thread were we can find out a running android os for uni... i take it !
Very keen on this
Is there a project? .. I'm a developer and would be willing to assist, but i haven't got enough experience with these devices to start the project off myself...
Count me in as a beta tester
It would be great to have Android on Uni!!
So this news means that very soon developers can start working on android to be ported on other devices!!!
http://android-developers.blogspot.com/
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
Hey guys was wondering about flashing my HTC Touch Diamond, But I want a decent ROM.
Something that's not too packed up full of junk, Easy to use and a better performance.
Also maybe a guide to unlocking/debranding this phone along with a flash guide if that's not too much?
cheers.
xelasha said:
Hey guys was wondering about flashing my HTC Touch Diamond, But I want a decent ROM.
Something that's not too packed up full of junk, Easy to use and a better performance.
Also maybe a guide to unlocking/debranding this phone along with a flash guide if that's not too much?
cheers.
Click to expand...
Click to collapse
From one newbie to another, you should read the sticky posts... they are full guides and information about flashing your phone's ROM / Radio etc.
The forum 'Search' facility is your friend, it like's to be used. That's what I did and found all I needed to know about the available ROM's and Flashing process without having to ask a single question.
The New World ROM introduced a much-improved version of the Open Firmware interpreter, version 3.0, which added many missing features, fixed most of the bugs from earlier versions, and had the capability to run CHRP boot scripts. The Toolbox ROM was embedded inside a CHRP script in the System Folder called "Mac OS ROM", along with a short loader stub and a copy of the Happy Mac icon (in Mac OS X 10.2 and higher, this was replaced with a silhouette of the Apple logo on a blank gray screen) suitable for display from Open Firmware. Once the ROM was loaded from disk, the Mac boot sequence continued as usual. As before, Open Firmware could also run a binary boot loader, and version 3.0 added support for ELF objects as well as the XCOFF files versions 1.0.5 and 2.0 supported. Also, version 3.0 (as well as some of the last releases of version 2.x, starting with the PowerBook 3400) officially supported direct access to the Open Firmware command prompt from the console (by setting the auto-boot? variable to false from Mac OS, or by holding down Command-Option-O-F at boot).
rajas
new rom
The result of probably more than 100 hours of solo hackery: a working COM DLL for allowing any application to elevate itself to SYSTEM (root) permissions.
What you need:
An interop-unlocked HTC phone. Sorry second-gen and Arrive users.
A working HtcUtility driver. It's possible some HTC update at some point crippled this. It works for me; if it doesn't work for you let me know what updates you have.
What it does:
Allows changing the security token of any application to give that app unrestricted permissions. At this point, you can call any user-mode API, perform any operation, with full access.
It also allows you to read or write any value from memory, even kernel memory (this is how it modifes the security token).
What it can be used for:
Darn near anything. If it can be done while the phone is booted, you can do it.
What it can't be used for:
Modifying the ROM - the R and O stand for "read only" and they mean it.
Interop-unlocking a phone - it requires interop-unlock to get root in the first place.
How to use it:
In your app, include the HtcRoot.dll library.
Include the code from DriverAccessTest.cs in the test app (defines the COM API and enables using it).
Call the OpenHtcUtility function (will throw an exception if your device is incompatible).
Call the MakeMeRoot function (can also throw exceptions).
(OPTIONAL) Call the ReturnZeroIfRoot function to make sure your app is elevated (does not throw exceptions, will return an error code if you get one).
Do stuff with SYSTEM permissions (probably using another COM DLL, such as for registry or filesystem access).
Call the RestoreToken function (failure to do this *might* cause a kernel memory leak).
Call the CloseHtcUtility function (OS will probably handle this if program just exits).
What you can do right now:
Try the test app. It should pop up a series of messge boxes. Hopefully none of them say anything like "FAILURE".
Report any bugs or failures you discover.
Build things with this library, and publish them!
Breakdown of the download:
There are two folders in the ZIP, one for the Visual Studio 2010 C#/Silverlight XAP project, and one for the Visual Studio 2008 C++/COM DLL project.
The test XAP is in the HtcUtilityTest\bin\Debug folder.
The native (COM) DLL is also available in that folder, or under its own project.
If you want to mess with this, I'm going to assume you are already familiar with hybrid native/managed development for WP7. If not, Heathcliff74 has posted an excellent tutorial on this forum.
Special thanks to:
Heathcliff74 for the hybrid app tutorial and interop unlock info.
Paul_Hammons for the links and info about HtcUtility, the driver that makes this possible. Thread: http://forum.xda-developers.com/showthread.php?t=1434793
Supported devices / firmware versions / ROMs
All HTC devices (if interop-unlocked and with the right firmware numbers) should be compatible.
Some custom ROMs work, some do not. This will depend on the version of the firmware that the ROM's HtcUtility driver is taken from.
I believe I compiled the test app as Mango-only, but the native library doesn't care at all.
Compatible:
Stock ROMs with compatible firmware for HD7, Trophy, Mozart
HD2 (BttF [XBmod-Yuki] v2 SP1)
Not compatible:
Firmware version 2250.21.51004.401 or newer
Verizon Trophy firmware version 2305.13.20104.605 or newer
DFT ROM with build 8107, Firmware 5.10.401
Arrive (except on pre-Mango), Titan, Radar, Titan 2 (no interop-unlock)
Others are untested or results are incomplete.
Goals and future work:
Support more devices:
* Try and add support for newer firmware.
* Help ROM cookers ensure the library is supported.
* Look for similar openings in other OEM libraries.
Future-proofing:
* Allow installation of a mod to support this capability after known updates.
* Resilience against possible future updates.
* Allow users with incompatible devices to downgrade (possibly to NoDo), install the mod, and be able to use the phone after upgrading.
Improve the library:
* Fix some memory leaks.
* Clean up the code - remove dead code and improve comments.
* Allow reading/writing more than 4 bytes at a time from managed code.
* Add APIs to elevate other processes (by name or ID) to SYSTEM.
Develop homebrew around the library:
* Support accessing common APIs (filesystem, etc.).
* Resurrect the Advanced Explorer app, perhaps (registry and filesystem).
* Support native app launching on stock ROMs.
Also reserved
Reserved for OP #2
It does not work on HTC 7 Mozart (HTC Europe):
Error to Write the value 1337 to test address - System.Runtime.InteropServices.COMException (0x8007001F): A device attached to the system is not functioning
Click to expand...
Click to collapse
OS: 7.10.7740.16
Firmware: 2250.21.51101.401
Radio: 5.71.09.02a_22.51.50.21U
Boot: 5.11.2250.1(133487)
Please include the full error message or a description of what went wrong.
Failure on fully updated devices is unfortunately possible - my phone is (intentionally) a few updates behind. I'm looking into ways to make it work anyhow (either sending an older CAB update to roll back, or using the root acess to create an unlocker/root-enabler that survives subsequent updates). I'm going to look into how the full-unlock ROMs differ from standard ROMs, and see if I can do the same thing in running software.
Does it works with custom roms?
If the custom ROM has a working HtcUtility driver, then yes. My goal is to unlock the kind of capabilities normally restricted to custom ROMs on stock firmware, though.
@bleh815: Thanks for the report. That's frustrating; it looks like it is capable of doing read but not write. Write might just be restricted in what addresses is allowed, or it might be disabled entirely (the driver gives the same error code for every problem that I've encountered so far). Time to figure out
A) what update causes the problem (I'm on 2250.21.30102.531, HD7, stock ROM)
B) what restrictions that update introduces
C) how to work around those resrtictions (possibly by downgrading and then using root access to add something that will still work after upgrade).
GoodDayToDie said:
A) what update causes the problem (I'm on 2250.21.30102.531, HD7, stock ROM)
Click to expand...
Click to collapse
I've just downgraded a mozart of mine back to stock NoDo (TMOB-DE) to find out which OEM update breaks (actually fixes) it.
Cool, thanks! It's one of the post-Mango HTC updates; a Microsoft update wouldn't have modified an HTC driver, and my phone has all the pre-Mango HTC updates but it still works.
.
..........
Hi, at first it says "SUCCESS!", then it says "Trying to open a file gives error 1260" and then it says "Now opening a file gives error 0" and finally "Finally, opening a file gives error 1260".
System informations:
OS=7.10.7720.68
Firmwareversion=2250.21.12200.162
Radio=5.68.09.05a_22.50.50.21U
Bootloader=4.6.2250.0(129185)
HTC 7 Trophy.
That is *exactly* the sequence of messages it is supposed to give!!
In particular, the messages I need to see are the "SUCCESS" (the rest is potentially interesting info, but not very important) and then the "Now opening a file gives error 0".
The "SUCCESS" means that a sequence of read/write tests succeeded.
The "Now... error 0" means that the process has been elevated to full permissions.
The "Finally... error 1260" means that the security token was successfully restored at the end, so it was unable to open the file again. This is the expected and correct behavior.
I don't recognize your Firmware Version number; I'm guessing it's specific to your phone. What method did you use to upgrade to Mango?
how do i install it?
Tried on interop-unlocked HTC Surround, not working Tested any call in VS debug mode - no luck at all.
I can confirm that it works with any OS version, from 7004 to 8107.79
On a HTC 7 Mozart (TMOB-DE) it works with firmware 2250.21.13201.111 (Stock NoDo ROM) but the hole gets fixed with 2250.21.51101.111 (1st Post-Mango HTC Update).
You guys are gods taking programming to a hole new level!
I wish to see ms take you all more serious and not let wp7 fail like minmo6.5 did!
I wish I could get on your level!
I realy need some help lerning basic silverlight my self!
But I have read how hybrid working ant this is just fantastic!
conradulations on all your developments so far you guys are truly amazing!
Oh, that code, beautiful reading that!
Thanks for sharing this learnfull code!
I'd like to try it on my Verizon HTC Trophy, I would love to get file access back....
I downloaded the package and I even have VS 2010 installed but beyond that I have no idea as I am not a programmer.
Can someone post a compiled XAP for us to try to see if our phone works with it or not ?
Or some step by step VS 201 directions to try would also be helpful.
@Ttblondey: *FACEPALM* The path to the test XAP is given in the opening post. You install the XAP on your phone using any XAP deployment tool. It requires that your phone be interop-unlocked; Heathcliff74 has a nice long thread about that. The app is called called HtcUtilityTest. Run it, and report the results. If you want to actually *use* the DLL, the instructions for doing that are given too but you need to write some code.
@sensboston: PLEASE give a more complete report! Success and error messages, at the least. Also, your phone version info. Thanks!
@bleh815: THANK YOU! I mean, it's a little annoying to know how far back this was fixed ("First post-Mango HTC update" means the one that was included *with* Mango for most people, or the one after that?) but good to know. Now, to look at exactly what they changed...
@jackrabbit72380: Thanks man! As for working with it yourself, like I mention below, I'm planning to provide a universal homebrew library that people can easily use to do whatever they want.
@fiinix: You're welcome! Honestly, I didn't expect anybody to call my mess of debug-commented and mildly hacky C++ "beautiful" but that hack itself *is* pretty awesome. My only concern with using it is the risk of a context switch causing the wrong app's token to get overwritten, and I should probably look into that, but I think it's OK for the moment. There are bigger fish to fry.
In the meantime, it should open up a huge list of capabilities for tools like your DllImport project. I'm currently considering reviving Advanced Explorer (like TouchXplorer + Registry Editor, but open source; was never ported to Mango though) using the root access instead of using ComFileRW and the provxml driver. Let me know what you want to do with it!
One other thing I'd like to add is the ability to easily elevate *another* process; it's not hard to do but I haven't written it yet. This could be handy for apps where we don't have the source code (for example, elevate Schaps registry editor, which uses low-privilege native code for browsing, so it can read *all* registry locations instead of just some of them).
@DavidinCT: Well, running the test app is easy, just install the XAP. It just runs a battery of tests though, it doesn't actually *do* anything useful. To get filesystem access, you'll need to write some native code (which means using Visual Studio 2008 and the CE/Smart Device plug-in, see Heathcliff74's toturial on the subject). Basically, you would first use this DLL (accessed via COM, you can look at my own C# code for how to do that) to opent he driver handle and elevate the process to root. You could then write your own COM DLL that uses the standard Win32 filesystem APIs (CreateFile, etc. - all are documented on MSDN) and exposes those APIs, or the results of them, to managed code via COM. Then, back in your phone app (the one that called into my HtcRoot DLL) you can call into your own DLL to access the file system.
If that's too big a leap, don't worry. I plan to release a general-purpose high-privilege homebrew DLL that exposes some of the most-used functionality (filesystem, registry, provxml, and other things by request), is easily extensible (possibly using something like the DllImport project, where you just specify the function you want to call and the DLL it's located in right from C#), and that will be a lot easier to hack with. You'll still need to know C# and basic Silverlight, but it'll be a lot easier (and hopefully useful without knowing any C++ or COM).
GoodDayToDie, you are amazing, always keeping me interested!
When starting the test xap, I get the below, it then goes into the "Page Name" and that's it.
Device Info here, running a FullUnlock DFT Rom by a Chinese dev from the DFT Forum.
Nonetheless, top work on getting this started and can't wait to keep reading about the progress!
XeKToReX
Full Unlock v4.6
Not much to write here
Features:
App precaching
Native application support.
Selective root access for applications alongside with possibility to open full access to system for all applications altogether.
Root access usage notifications.
Enhanced security.
IMPORTANT:
1) That's a squeezed release - some registry entries were removed to reduce a number of dependencies
2) Terms of usage are the same as for Dynamics ROM.
FOR ROM CHEFS ONLY!
Thank you my good friend very much!
big thank's my friend
Thank you my god!you are my god!:victory:
Thanks for the new unlock.
Full Unlock hanging logo, whether the missing package?
eg: Pkg_PlatformInterop
Thank!
ultrashot said:
It was a nice experiment almost every chef took part in - and it answered "who is who" in this community. Just changing a phrase "wait for two weeks" to something less suitable (for some rom makers it is less suitable on purpose) and some "word" magic radically modifies one's behaviour.
Anyway, things go as planned, and today Full Unlock v4 sees broad launch.
Full Unlock v4.0
Not much to write here
Features:
Native application support.
Selective root access for applications alongside with possibility to open full access to system for all applications altogether.
Root access usage notifications.
Enhanced security.
IMPORTANT:
1) That's a squeezed release - some registry entries were removed to reduce a number of dependencies
2) Full Unlock v4.0 is available for all, but all the rest from Dynamics 2.0 and derivatives is still prohibited. v1.21 stuff is allowed to use.
Click to expand...
Click to collapse
Thanks a lot！
Good Job~
Thank you so much for sharing my friend
Big thank's
Edit
You have DLLs in some Modules ?
I have changed all folders OEM
PkgOem_AccountManager Changed
PkgOem_AccountManagerWorker Added
PkgOem_XapDeployer Changed
Pkg_FullUnlock Changed
Pkg_HtcUnlock Changed
Pkg_InteropUnlock Changed
Pkg_InteropX Added
And XIP
Pkg_XipUnlock Changed
But Account manager open and close immediatly.
Old Account manager Works with ?
Omnia 7 Try every way themselves rather Full Unlock V4 to the hanging logo, anyone know the cause?
I must be missing something - which devices are supported? Is the Lumia 900 supported? Does it needs to be dev-unlocked, or interop unlocked?
efektos said:
I must be missing something - which devices are supported? Is the Lumia 900 supported? Does it needs to be dev-unlocked, or interop unlocked?
Click to expand...
Click to collapse
its not an installable cab or xap, I believe this needs built in to the ROM. as far as I know there is still no interop unlock for the 900 let alone new bootloaders and custom ROMs
Big thanks
Ultrashot, thank you for your major contribution for wp7.
Greetz,
xuantunt said:
Omnia 7 Try every way themselves rather Full Unlock V4 to the hanging logo, anyone know the cause?
Click to expand...
Click to collapse
Im haveing the same problum trying to buld a rom for the hd2 with sys 8858 a diffrent unlocking method works fine but not these files cause? unknowen. it seams that hd2 owener did use this metod in his dnynamics rom. witch is custom but still omatter what i do im stuck at boot logo!
it would be nice if someone could post better dicriptions as to what the packages do? like for instance witch one will give added sicurity and witch one is for native applications?
When i cook my Rom for Titan with FU v4 my HTC_OEMapps are not installed and With v3 all are installed.
can anyone upload compatable pkgs for htc hd2 with sys 8858?
jackrabbit72380 said:
can anyone upload compatable pkgs for htc hd2 with sys 8858?
Click to expand...
Click to collapse
its compatible with all devices.
ultrashot said:
its compatible with all devices.
Click to expand...
Click to collapse
okay well why are we getting stuck at the boot logo? why are thare dll's in some Modules? & is this download missing package?
eg: Pkg_PlatformInterop
is something missing or we just need some instuction?
I spend 12 hr's trying to get it to work with no luck can anyone help?
New Port XIP, the new no crashes logo, other apps to run it.