Develop Bugs

Working Android on BA! (tested myself)

Hi, yesterday i was trying to launch android on my BA and i DID IT!
It works like ****:
Touchscreen doesn't work (you can activate list scrolling by pushing it on the side)
Some buttons don't work
No sound
Navigation:
D-pad (left, right, up, down)
Enter (on the keyboard, since D-Pad center doesn't work)
!WARNING! there is no end call and back buttons, you can't exit applications
How to? Here is the tutorial:
Create a folder on your memory card
Get the latest HaRET from here http://handhelds.org/~koconnor/haret/
Get the latest zImage from here http://www.angstrom-distribution.org/unstable/autobuild/htcblueangel/
(i use zImage-2.6.21-hh20-r16-htcblueangel.bin)
Rename it to zImage
Put that default.txt
Code:
set kernel zImage
set initrd "initrd-android.gz"
set CMDLINE "rootdelay=3 root=/dev/ram0 ramdisk_size=23504 init=/linuxrc"
boot
Now you need the system - Android
Get that: http://it029000.massey.ac.nz/vogue/initrd-android
Don't forget to rename it to initrd-android.gz
I've got it from here http://it029000.massey.ac.nz/vogue/

it stays in jumping to kernel... i followd the steps above, did you copy pasted the command correctly??

rafyvitto said:
it stays in jumping to kernel... i followd the steps above, did you copy pasted the command correctly??
Click to expand...
Click to collapse
Try different kernel. It works for me

GVG said:
Try different kernel. It works for me
Click to expand...
Click to collapse
Could you please tell us how did you install android on Blue Angel? Procedures and everything else. And also your opinion about it's performance. thank you very much

blackout_pt said:
Could you please tell us how did you install android on Blue Angel? Procedures and everything else. And also your opinion about it's performance. thank you very much
Click to expand...
Click to collapse
Just launch Haret.exe
Speed... hm... Almost like WM6

a lot slower than wm6 the android image should be tweaked in order to have proper drivers for touchscreen keys and sound

wow...very cool, I'll be looking for updates (if there are any)

hi friends,
i tested android and seems a good toy
i did make a rar with all files needed, you need only to extract to SD and run haret
Code:
http://rapidshare.com/files/147524450/android.rar.html
i'm really interested to go further on android.
about my tests, i can conclude two things:
- D-pad works, but not very well
- Touch screen is not working, but i know it detect moves on it
(try to dpad a icon, then touch the touch-screen, you ll see)
I'm not a expert on pocket pc, but i have my skills.
I found an other thing, hardware specification.
Code:
http://www.handhelds.org/moin/moin.cgi/BlueAngelHardware
if the information is right, the touchscreen is from the same family that the vogue one.
To continue this adventure, i need some lights. I know we have a developer from the kernel/Opie/GPE in this forum. If you are him, i need some lights about your work.
The other thing, i'll try to do is asking help to vogue/kaiser android project, to give me some lights how they touchscreen work.
The last thing. All the help is appreciated, everybody is invited in this project and all the help is welcome. And i really need it lol
udapte (23/9/2008)
Well i talk do vogue android project man, and the answer from him is simple. His work was only to port kernel to vogue platform. I will have to find who made the one we are using.

The touchscreen is detected, but somehow it doesn't work.

i have failed .
my BA get a FlashDIsk and ramdisk in WM6 enrironment..
when i run haret ....
after jumping to kernal
an error occur
can't mount SDcard .it's halt..
why...

How about your work? I'm working on this task also. Need more information to make it working. Could you give me some patches for BA's kernel.

Also the SC Card Message, any adivice o workaround?

w0w...
it runs on my BA. Great!
However I cant do anything inside. But thanks to all of you that make this possible.
I'm waiting for the next release, hope it will run faster, and all get better.
Thanks.

Is anything happening with this?

Any news?
Is vogue version working? I have try to build a kernel for BA but false to boot
Will try and report later....

kernel
I have A LOT of, like everything I could find, files to load linux on the Blue Angel. Angstrom, Familiar, QT...somethingsomething... Anyway, it works well except the wireless which I think should work until the thing goes into standby. Would the zImage/initrid files or any of the others help? I'd like to help ya get this working, I think most of the works been done. I must say, however, I am just learning about how this stuff works. I can't code, but I have a BA, lots of experience repairing hardware like ppcs and I really would love the chance to finally give back to this wonderful community after they've given me so much.

It would be great to get this working. It would give my pda2k a whole new lease on life.

any updates on this?
Thanks

so, any news? android would be quite nice.

i concur. i'd liketo see a android on the blueangel, why isnt there one? linux runs fine on it, theres an older android that supposidly boots on it.
cmon somebody make the damn thing work.

[2010.2.4 New Testing Package] Online..

Time changes, and things go better and better.
This thread is dedicated to test the android and try to figure out where is the problem
[NEWS]
The NEW KERNEL ROCKS.. With double RAM.
And the new rootfs is cleaner than before.
I am going to release a new package (which I just did some small editing)
What can you do with this package?
Connect ADB (very important for debugging)
Put everything in a folder of your SDCard
Supply with NEW kernel and now you have more free RAM
Enjoy the cleaner rootfs (I have made some small modifications)
Download : http://www.mediafire.com/?1tbnyz2jmky
If any of you know how to enable chat in irc, please let me know.
BASICS:
Current Android boot from HARET which start from Windows Mobiles.
It consist of several components. Each of those is having unique functions.
1. STARTUP.TXT
Passing parameters to kernel which enable users to specify machine specific data
Current parameters including screen size, dpi, rotation, etc.
2. Kernel
The most important piece of code that enable everything to talk to the machine.
Developers here are most focus on this area as the other are greatly supported by google and other developers.
Kernel also determine what the hardware could do, and how it connects to other devices.
3. rootfs.img
This is the root of the linux, which initialize the OS. Especially running some startup scripts and mounting folder.
4. system.sqsf
The is the base Operating System of something call ANDROID. For others, you may considered them the basic environment of mobile Linux. For what we call CupCake / Donut / Eclair are stored here.
What we will be doing is to test out the features and bugs and locate the part of the about components affecting it.
Updated ADB howto:
Grab my base package.
Connect to computer before running Haret.
Wait until Android boot complete.
Install Google SDK USB drive for whatever device show up.
droid explorer or "adb device" to test.
If no device found, replug the usb cable.

This post would be updated with agenda drawing most concerns. We need your testing to see if you have any similar problems.
Agenda:
Top priority:
Device can't be wake.
Rear speaker always on.

This post would updates the testing items, and report the latest status.
Everything here are replaced with most recent findings and once more users confirmed, it moves up.
Do not believe everything in this post, but try falsify it. Reports in here would be presices to the level of component and versions.
So make sure you know what you are testing.

This post is a testing invitation, with trials and errors.
If someone raised an interesting phenomenon, we are going to invites members to test it. And the result format would be given as well.
This post may be changed from time to time to refect the new items needed to test (including the return format)
Now, let's kick start.
#1 To Test the base package in post 1
Return with following format.
Machine Type: BLAC100 (other devices are welcomed, but of course we are BLAC owners and would focus on it)
Test build: 2010.2.4
Radio: 1.17.25.09
WIFI ON: YES (WPA)
WIFI OFF: YES
Calendar / Gmail : BOTH OK
Google Voice: OK
Deep Sleep: YES (To test it, disable WIFI, Any USB, and press END KEY to sleep. If deep sleep is working, the system should not be up with key other than the power key)
Wake up: Crashed sometimes initially and get stablized later
ADB Connection: OK
Additional Package Installed: Facebook, dolphin
Suggestion: Replaced with kernel version xxxx would help to xxxxxxxxxxxxxx (if you found out how to make the build better)
#2 DEEP SLEEP AND WAKE
Please post your kernel version (or if you have no idea, the file name of the wifi module) if you found youself never had problem with sleep and wake (not yourself, but your blackstone android).

Lets begin this thread with a constructive approach to achieve our desired goal.
Will Post the feedback as requested.

Machine Type: BLAC100
Radio: Security unlocked 1.16.25.48 (Kovsky)
WIFI ON: YES (WPA)
WIFI OFF: YES
Calendar / Gmail : BOTH OK
Deep Sleep: YES but say after 10 minutes it wont wake-up.
Market: Working with downloads.
Additional Package: Facebook, Wifi toggle, Currency converter, Battery lite.

imtiyazee said:
Machine Type: BLAC100
Radio: Security unlocked 1.16.25.48 (Kovsky)
WIFI ON: YES (WPA)
WIFI OFF: YES
Calendar / Gmail : BOTH OK
Deep Sleep: YES but say after 10 minutes it wont wake-up.
Market: Working with downloads.
Additional Package: Facebook, Wifi toggle, Currency converter, Battery lite.
Click to expand...
Click to collapse
Thanks for your report. Developers is aware of the wake up issue of blackstone. It is however, seems still not fixed in the new kernel.
And Pierre-Hugues Husson would disable the deep sleep function (consume a little more battery) in up coming kernels, and we can try it on very soon.

mcdull said:
Thanks for your report. Developers is aware of the wake up issue of blackstone. It is however, seems still not fixed in the new kernel.
And Pierre-Hugues Husson would disable the deep sleep function (consume a little more battery) in up coming kernels, and we can try it on very soon.
Click to expand...
Click to collapse
Thanks for the update.

mcdull,
Brendan shanks has changed pid on kernel to "0c01", this should enable working with ADB without hacking the inf file.
This was deployed on Build: [email protected]_071547.
Let us know if this makes any difference for you, and whether HTC sync is now possible.
Thanks

It works perfect
hello,
I am using ANDROID_bLACKSTONE_TESTBUILD_20100125.ZIP & zImage-modules-20100129_022341 and it works perfect on my Blackstone till now.
Wi-Fi - OK
Synchronization with google account - OK
Sleep mode - OK
It is FAST
Call IN and OUT - OK
SMS - OK
this combination is best of the best till now what I tried.
eligius

Roadrunner100 said:
mcdull,
Brendan shanks has changed pid on kernel to "0c01", this should enable working with ADB without hacking the inf file.
This was deployed on Build: [email protected]_071547.
Let us know if this makes any difference for you, and whether HTC sync is now possible.
Thanks
Click to expand...
Click to collapse
AFAIK, HTC Sync will not work just yet. And I was not able to connect to ADB after the change. I need to test on some editing.
- Theory
As I already mentioned, the latest implementation of kernel prevent the proper installation of usb driver, and we need to fall back to old kernel to install the driver first (which the old kernel has 0c02 address).
Now, the modification has put the case into dead end. coz we can have no way to ask the computer to install a correct driver with 0c01 address.
In such case it is more difficult to modify the whole batch of driver setting then just the ini. I still have no go in using ADB.

The HTC Dream driver for windows seems works on ADB again.
As suggested by Brendan Shanks, you need to modify the "eclair.user.conf" (stored in the conf/ folder on your SD card), at the bottom, add this line to the custom_shells section:
echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch
And I have successfully to connect to ADB again.

mcdull said:
The HTC Dream driver for windows seems works on ADB again.
As suggested by Brendan Shanks, you need to modify the "eclair.user.conf" (stored in the conf/ folder on your SD card), at the bottom, add this line to the custom_shells section:
echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch
And I have successfully to connect to ADB again.
Click to expand...
Click to collapse
Thanks for that. I will try also.

Today, I started seeing the traffic animating 3G icon for the first time.
Great.!!

ADB working
Thank's mcdull ,using the Brendan Shanks method , ADB is working very well.
I'm using the 29-01 kernel and i changed the eclair.user.conf.
After that , the Droid explorer works well .
Bluetooth and GPS , the last frontier.
Regards.

cbolumar said:
Thank's mcdull ,using the Brendan Shanks method , ADB is working very well.
I'm using the 29-01 kernel and i changed the eclair.user.conf.
After that , the Droid explorer works well .
Bluetooth and GPS , the last frontier.
Regards.
Click to expand...
Click to collapse
Great. For others information, all needed changes and new kernel has been included in the latest package.

==REMOVED==

can some1 list what is working with this release of android and what isnt..thnx

WiFi don't go ON
In my blackston WiFi is not workng , anyone have some idea how i can solve this problem.

http://forum.xda-developers.com/showthread.php?t=630643
Check Out 7) (2nd post)

PUAE4All - wm port.

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):

Gruessle -> Kaiser Froyo Rom

06/16/2011
The screenshots are not important. This is not a theme!
You can install a theme from here, for example if you like.
The theme it comes with is the:
Go Louncher Classical Theme (The new version of it)
The software installed is also not important, because you can remove it.
Google Market is installed, and you can install what ever you like, just like on your computer.
https://market.android.com
This is the actual Android Froyo operating system for the HTC Kaiser
So, stop asking me for screenshots and software installed, it's not relevant.
And the how to install guide is been posted here
Bug reports are welcome, other then that, I don't wont to hear from you.
Don't post a thank you either, there is a bottom for that, and you can also vote on the poll up there, but install and test it first!
Again Bug reports only, please!​
I been working on this for 3 days straight, and figure I'll share what I got.
Everything seems to be working, except the camera is blurry, but that seams to be the norm.
Included is the rom, radio and kernel
ROM: 2.2.1
Kernel: 2.6.25
Radio: KAISER 1.70.19.09
Panel: 2
Key Map: US Normal
Resolution: 240x320
Storage: Nand & Nand
Most everything is installed in userspace and can be uninstalled or upgraded.
Oh got GO Launcher EX installed (Also in user space)
Credits:
I stole ideas from, and used following tools:
Makers of atools
Makers of NBH creator
HTC Flasher
kallt_kaffe
Krazy-Killa
dzo (dzo's posts wore a big help. just wish he would answer his own questions after he found the solution)
n2rjt
and many more.
@todo
Resize NAND partitions to the smaller system size
Original post and download Links are posted on my blog:
http://press.pzzazz.net

Can you write something more about this? Is this your system and kernel(compiled yourself)? Any changes?

MaRekRM said:
Can you write something more about this? Is this your system and kernel(compiled yourself)? Any changes?
Click to expand...
Click to collapse
Yeah witch apps are include. Some yours tweaks or etc... ???

MaRekRM said:
Can you write something more about this? Is this your system and kernel(compiled yourself)? Any changes?
Click to expand...
Click to collapse
That sounds like a trick question.
Yes, at first I compiled everything my self but then to resolve bugs, I looked at other systems and basically stole stuff from them to fix my bugs. In other words, I can't take all the credit, it was a community effort.

Neo2SHYAlien said:
Yeah witch apps are include. Some yours tweaks or etc... ???
Click to expand...
Click to collapse
I removed most everything from the system and installed it in user space. So the system is very lean. You can uninstall what you don't like.

how is the rom？just waiting to see

gruessle ...!! thanks for your efforts in getting this done... I been looking from long time to install Android on my HTC TyTN II. However i was not able to get the proper build...
can you share the screenshots of the build which you provided as well some steps at high level on installing this..
Thanks in advance.

Please, I don't really understand how to go upgrade this. I find it hard to do. Is everything needed packaged in this download, or please can u list things needed to change to android. I'll appreciate your response.

tundelogic said:
Please, I don't really understand how to go upgrade this. I find it hard to do. Is everything needed packaged in this download, or please can u list things needed to change to android. I'll appreciate your response.
Click to expand...
Click to collapse
here is the howto
http://forum.xda-developers.com/showthread.php?t=680518

kkp said:
gruessle ...!! thanks for your efforts in getting this done... I been looking from long time to install Android on my HTC TyTN II. However i was not able to get the proper build...
can you share the screenshots of the build which you provided as well some steps at high level on installing this..
Thanks in advance.
Click to expand...
Click to collapse
The screenshots are not important.
This is not a theme.
You can install a theme from here, for example if you like:
http://golauncher.goforandroid.com/category/themes/
The theme it comes with is the:
Go Louncher Classical Theme (The new version of it)
The software installed is also not important, because you can remove it.
Google Market is installed, and you can install what ever you like, just like on your computer.
https://market.android.com/
This is the actual android froyo operating system.

Anyone else having trouble getting the kernel to install?
I get to 33% and the phone reboots...
Radio installed fine even though I was already using 1.70.19.09, just to be sure I installed everything in the package.

Installed HardSPL 3.34 and a WinMo 6.1 rom (custom) to see whats wrong. Installed L1q1d's kernel and goes right in like it should.
Checked .NBH with NBHCreator and only found 1 thing wrong: kernel set to Eclair instead of Froyo. Changed to Froyo and saved, attempted reflash and still won't go in...
;(Losted);

I also tried to install this kernel but I can't. Flashing in hardspl after few second give folowing error:
00018003
Os Fail
Update Terminate
UPDATE Fail.
Changing parameters in atools not helping. Every another kernel is flashing without problems so it's not phone fault

Gruessle, thanks for your efforts! I want to try your rom but being a noob waiting for more comprehensive list of known errors before flashing it to my kaiser.

Ok, quick "bug report":
After working with the kernel pack multiple times I have come to the conclusion that there might be a bug in the actual kernel file itself, throwing a code back to HardSPL and RUU (how I install).
I first noticed a problem in that the kernel was originally set up for a Polaris and had no resolution set. The size of the file should be unimportant as Scoot's newer kernel is in the order of 3.2-3.3MB in size (with the RIL patch installed it gets even larger), this one is 3,099KB, and l1q1d's is almost always 3,092KB.
The second issue I noticed is with the Froyo package itself... It's split up into many files (open the package in 7zip and you'll see what I mean). Normally, the packer has the files all listed inside the .tgz file, this one has the files inside many other files.
I have thus not installed the system on either phone because (correct me if I'm wrong), the kernel contains the basic directories for where everything is installed, and if I were to try and install this package on say, l1q1d's kernel, the phone would most likely crash because the files would not be found, including /system.
If ANYONE wants to dig deeper into this problem, feel free to message me. Personally, I think we've about finished getting all we can from the Kaiser, and much respect goes out to those who have done all the work in the past, but there's always that glimmer of hope that someone will find a way to pack this into a working rom installable through RUU or HardSPL.
I have one last thing to say:
Gruessle, please do your homework BEFORE posting things like this. There are people out there who still depend on this phone to operate as it is their only phone. I Personally cannot afford to go spend $100-200 on a replacement phone if this one goes down (thats why I have 2 of them). If you post something that does not work on the platform that you say it will, please correct it or move it to the proper forum.

BTW, I call shenannegans on one of the 5-star votes... just sayin'.

Your kernel have fake ;/ . rom works great ;D
sorry for bad english;p

PoXFreak said:
Ok, quick "bug report":
After working with the kernel pack multiple times I have come to the conclusion that there might be a bug in the actual kernel file itself, throwing a code back to HardSPL and RUU (how I install).
I first noticed a problem in that the kernel was originally set up for a Polaris and had no resolution set. The size of the file should be unimportant as Scoot's newer kernel is in the order of 3.2-3.3MB in size (with the RIL patch installed it gets even larger), this one is 3,099KB, and l1q1d's is almost always 3,092KB.
The second issue I noticed is with the Froyo package itself... It's split up into many files (open the package in 7zip and you'll see what I mean). Normally, the packer has the files all listed inside the .tgz file, this one has the files inside many other files.
I have thus not installed the system on either phone because (correct me if I'm wrong), the kernel contains the basic directories for where everything is installed, and if I were to try and install this package on say, l1q1d's kernel, the phone would most likely crash because the files would not be found, including /system.
If ANYONE wants to dig deeper into this problem, feel free to message me. Personally, I think we've about finished getting all we can from the Kaiser, and much respect goes out to those who have done all the work in the past, but there's always that glimmer of hope that someone will find a way to pack this into a working rom installable through RUU or HardSPL.
I have one last thing to say:
Gruessle, please do your homework BEFORE posting things like this. There are people out there who still depend on this phone to operate as it is their only phone. I Personally cannot afford to go spend $100-200 on a replacement phone if this one goes down (thats why I have 2 of them). If you post something that does not work on the platform that you say it will, please correct it or move it to the proper forum.
Click to expand...
Click to collapse
1) The kernel doesn't care where you place the files. Right now I use a debian system with Ferora and Gentoo in a chroot. Both work fine with the Debian kernel.
In other words, if you have a kernel that works for you then use that it should work with the rest of the installation.
2) I don't get what you mean with files are "split up into many files", I am just guessing but you must be extracting it wrong. Maybe it's a windows thing, I haven't used windows in 15 years so I wouldn't be able to help you with that.
3) I have included everything you need to duplicate what I got, which works for me, and it appears to work for others too. Now i don't use that phone much, and there might be bugs I am unaware of, but don't tell me it doesn't work at all, just because you can't get it to work.

barmalini said:
Gruessle, thanks for your efforts! I want to try your rom but being a noob waiting for more comprehensive list of known errors before flashing it to my kaiser.
Click to expand...
Click to collapse
barmalini, it appears that a few people have trouble installing the Kernel, but the ROM seams to work for everybody as far as I can tell.
According to my server records the files have been downloaded over 200 times and I have yet to hear a complain about the ROM.
So I would say try to install the Kernel, but if you can't still use the ROM with a Kernel that works for you.
If you have trouble installing from windows you can also try a live CD from debian or knoppix. I installed everything from a Debian system. (Knoppix is based on Debian)
If you don't know what a live CD is then go here for info:
http://wiki.debian.org/LiveCD

PoXFreak said:
Installed HardSPL 3.34 and a WinMo 6.1 rom (custom) to see whats wrong. Installed L1q1d's kernel and goes right in like it should.
Checked .NBH with NBHCreator and only found 1 thing wrong: kernel set to Eclair instead of Froyo. Changed to Froyo and saved, attempted reflash and still won't go in...
;(Losted);
Click to expand...
Click to collapse
PoXFreak,
you are not the only one having trouble, installing the ROM it appears.
I am wondering, are you also using Microsoft Windows to install the ROM?
If so can you try again with Linux, because it worked fine for me.
If you don't have Linux you can use a Live CD
Also if you can't get it to work, try the ROM with a Kernel that works for you.
Please report, I will check back.

[Source][Dll][XAP] The HtcRoot project - Testers needed

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