Develop Bugs

[ROM] 2-18-10 Egzthunder1's 28230 (MetroPCS) - Clean Version

Busy day today
Anyways, I decided to discontinue 25005 since it had a graphical bug, which after spending several hours looking for answers, I couldn't fix...
So, here is the newest build (yes, even newer than 25005)
Build log is pretty much the same as 25005 but with a few exceptions
*Increased pagepool size to 18 MB!
*New Build 25005 (no clue about which COM branch it belongs to, so please don't ask )
*Added Bing
*MSN Widgets are Back
*Removed Opera since there is a newer version out there (with Flash support!). I haven't gotten the cab, so I will let you all install it and let me know
*Internet Sharing Added
*FaceBook Mobile is Back!
*Added QuickGPS (for faster lockons... or so I hear)
*Dialer Lag is gone!!!
*The only extra that I don't like (and I did not put in) was haptic feedback when touching the start menu. If anyone knows how to get rid of this... please.
Click to expand...
Click to collapse
Removed
*Showcase
*Mega dialer (simply left stock). Probably will try to use the GSM dialer from NFS's thread.
*Added Arcsoft MMS to UC Folder
*Added Netfront Concept 4 (latest one) to UC (replace with your choice of browser if you like something else). I find Opera very hard to use without an accelerometer and a scroll wheel, so I decided not to cook it in.
*Updated GoogleMaps to the latest publicly available
*I added a pretty cool looking theme for 6.5 but it was the cause for my funny looking icons and scrollbars, so use at your own risk.
Without Further ado, here is the LINK
[highlight]Installation Notes:[/highlight]
[highlight]Your device must be unlocked for this to work. If you don't know how to unlock it, there is a link on my signature with a guide on how to do this. Also, this is only for the HTC Vogue - which is a CDMA device (no SIM card). It will NOT work for any device that doesn't fall under this. Not sure if you have a Vogue? Go to the WIKI and find out. I am not responsible for damage to your device (not that anything should happen, but legal disclaimers are meant for the "what ifs" )[/highlight]
Drop the XDA_UC folder located in the rar file onto the root of your SD card. Flash and soft reset. The UC process will start upon second boot. You can add/remove any cabs that you want to (or not want) so that the system will install them automatically.
[highlight]CDMA Weather Fix:[/highlight]
Select the weather in your city in the Manila tab prior to installing this fix. Once it is selected, install and soft reset.
LINK to Weather Fix
[highlight]Have a different Carrier than MetroPCS?[/highlight]
Go here (thanks codf4ther!)
Please enjoy and if you like it and feel like buying me coffee... I will gladly accept it

ScreenShots
I know how some of you are picky about this, so here you go...

Bugs
I am happy to say that none so far

Addons, Fixes, and Miscellaneous...
Provisioning CABS Thread (thanks to codybear!!) - Use the cabs located in here only if you are on a carrier other than MetroPCS.
http://forum.xda-developers.com/showpost.php?p=3680840&postcount=3

Egz - glad to see you have a new one out! I'm downloading right now and will flash sometime tomorrow. By the way, in post #2 the screenshots didn't show up, just thought I would let you know. I'll let you know how the new ROM is working once I get it flashed.

Irishpride said:
Egz - glad to see you have a new one out! I'm downloading right now and will flash sometime tomorrow. By the way, in post #2 the screenshots didn't show up, just thought I would let you know. I'll let you know how the new ROM is working once I get it flashed.
Click to expand...
Click to collapse
hehe, I am aware of the screenshots. I was trying to get My Mobiler to see my device, but it just refused to connect. I will try to get something like CapSure or some other tool and get the screenshots directly from my device...

Will this work for Verizon?

Heresfitz said:
Will this work for Verizon?
Click to expand...
Click to collapse
It should as long as you install the Verizon provisioning cab over top NFSFan's roms are built for Bell by default but they run fine on other carriers. I'm not sure if there is something special about MetroPCS that would cause issues but I think you should be fine.

codf4ther said:
It should as long as you install the Verizon provisioning cab over top NFSFan's roms are built for Bell by default but they run fine on other carriers. I'm not sure if there is something special about MetroPCS that would cause issues but I think you should be fine.
Click to expand...
Click to collapse
Right on the money. I will put a link to Codybear's post, which has most of the carrier specific cabs. Thanks for the reminder, cod!

egzthunder1 said:
Right on the money. I will put a link to Codybear's post, which has most of the carrier specific cabs. Thanks for the reminder, cod!
Click to expand...
Click to collapse
Which instructions do you follow for Verizon? The ones he has listed or the ones he links to in NFSFan's ROM post?

scotttr said:
Which instructions do you follow for Verizon? The ones he has listed or the ones he links to in NFSFan's ROM post?
Click to expand...
Click to collapse
The instructions for Verizon that cody gave seem pretty much on the money from what I have read. Try that and if it doesn't work, let me know and I'll get you something else . BTW, the MMS composer in the UC folder is preset for VZW, you may not need to do anything...

The new rom is great, but aggggg the vibration! I did a google to find a registry key to turn it down (not off) and came up dry. Otherwise solid work so far!!! Thanks.!

gjbnh said:
The new rom is great, but aggggg the vibration! I did a google to find a registry key to turn it down (not off) and came up dry. Otherwise solid work so far!!! Thanks.!
Click to expand...
Click to collapse
what vibration??
If you got my 25005, there is a fix for it (you have to edit the registry in a couple of places), which I posted on that thread (it is related to Showcase and it was driving me nuts too ). My advise would be to go with 28230. It seems a bit more stable...

Ouch my bad
Sorry, but I've flash my phone at least 5 times this week, and incorrectly identified the current rom. I need to flash to this one. My Bad

gjbnh said:
Sorry, but I've flash my phone at least 5 times this week, and incorrectly identified the current rom. I need to flash to this one. My Bad
Click to expand...
Click to collapse
That happens
Let me know how you like the rom... and report if there are any bugs.

Your wish is my command (Offer void is most countries, Tuesdays, and full moons)

gjbnh said:
Your wish is my command (Offer void is most countries, Tuesdays, and full moons)
Click to expand...
Click to collapse
Well, it is Friday, in Miami with no moon at all

I've got it up and running this afternoon. Here's s couple of thoughts & questions:
#1) I couldn't get your included ROMUpdateUtility.exe to run on Vista. I just dropped the nbh file in a folder from another rom and it flashed fine. I may have had a corrupted download, but it all extracted fine.
#2) CM Internet Sharing and ICS Control, are these useful on a phone without wifi? I'm curious to know how they can be used.
#3) I'm an EzInput bigot. I still think you should add it
#4) You have a lot of config utils included. Not sure how easy it is to do when cooking, but you might want to throw those in the Tools folder in the start menu. I doubt 90% of users would touch those.
Good job, thanks for cooking these for us.

Is anyone else having marketplace problems in this build? Seems to be slower when running, and I've had several "server" errors..

gjbnh said:
Is anyone else having marketplace problems in this build? Seems to be slower when running, and I've had several "server" errors..
Click to expand...
Click to collapse
I am getting intermittent networking issues on Bell for the last 24hrs. I was blaming it on the ISP...maybe its a problem with 28230

[Q] Android ROM for Raphael!

Will it be possible to make any true standalone Android ROM without using windows?
And for what device are this settings "RAPH800"?

Currently, no, but there is workaround - a light ROM with dualboot or directly HaRET in autorun.

Neopeek is working on it at the moment. It will come in the next few weeks. Be patient!

e334 said:
Neopeek is working on it at the moment. It will come in the next few weeks. Be patient!
Click to expand...
Click to collapse
could you please give more info or a link

In the next days i will look into dzo's script and adopt our kernel + ramadresses to get a full working nbh so that i can flash it onto my device. Hope everything goes well. This will take some serious concentration. This is what I am going to do:
Compile the kernel from scratch
Strip-out nb.os + nb.payload.os from vogue / kaiser / polaris to see what's going on
Recompile a new test-nbh to NAND-FLASH it as bootloader for Android
And last but not least: Adopt NoMoRootFS
I hope I and my device won't get stuck with this (I only have 1 device to test). If you wanna share your thoughts or contribute this then just answer to this discussion and share your ideas. I will keep you updated on this and in my free time I will also try to update the various Android builds. But I can't promise you to do so.
Click to expand...
Click to collapse
-neopeek
http://www.neopeek.com/en/community...67-Flashing+Android+on+our+devices?groupid=13 (mods please remove if this violates any rule of xda..)

Keep in mind that currently us TP user's DON'T have working camera (working on), and faster power drain (working on.) so if you end up using this rom (when it's done and released in time) you will have a phone that drain's faster then WM (meter usage is PRETTY accurate though itself.), and no camera anymore (until they finish adding support, and THEN add to this guy's kernal for the said ROM.), just so you know this
Currently, dual booting works just fine, and haven't experienced any negative's to date since using it this way. Hope that helps.

Ok. Tnx for the answers.
But can someone explain to me why it is so difficult to make working ROM for TP when the HTC Hero have the same hardware and powered up with Android? I am confused about that.
For what phone are startup settings (RAPH800)?
How much it will be faster with ROM flashed in nand memory than one run by heret in WM?
Tnx

mikx said:
Ok. Tnx for the answers.
But can someone explain to me why it is so difficult to make working ROM for TP when the HTC Hero have the same hardware and powered up with Android? I am confused about that.
For what phone are startup settings (RAPH800)?
How much it will be faster with ROM flashed in nand memory than one run by heret in WM?
Tnx
Click to expand...
Click to collapse
Uhm the Hero comes with Android 'from the factory' - it's a native Android device. Just like WinMo is native to our devices...
The brilliant devs are literally trying to reverse engineer drivers so Linux/Android can run on our WinMo phones.
I forgot to answer your other questions... NAND should give some performance boost, but I don't know how much. Probably not much, it didn't do much for the RHOD - albeit a little.
Phone startup settings, you should have a STARTUPS folder and it should have the RAPH800 startup in there...

Edit: (removed post, question was already answered)
Cant wait for nand support , i loved it on my Kaiser

Theoretical question: Will installation to NAND and starting directly from bootloader affect performance positively?

Corias said:
Theoretical question: Will installation to NAND and starting directly from bootloader affect performance positively?
Click to expand...
Click to collapse
In theory yes, but so far the benefits have been minor, if any. Of course the NAND that is functional for the TP2 isn't technically a full NAND, so it's probably not the best example to use.

arrrghhh said:
Uhm the Hero comes with Android 'from the factory' - it's a native Android device. Just like WinMo is native to our devices...
The brilliant devs are literally trying to reverse engineer drivers so Linux/Android can run on our WinMo phones.
I forgot to answer your other questions... NAND should give some performance boost, but I don't know how much. Probably not much, it didn't do much for the RHOD - albeit a little.
Phone startup settings, you should have a STARTUPS folder and it should have the RAPH800 startup in there...
Click to expand...
Click to collapse
Tnx for the answer. I know that I have RAPH800, but it can't work on my TP, only settings that work are RAPH, and I was wondering for what phone are these RAPH800 settings??

mikx said:
Tnx for the answer. I know that I have RAPH800, but it can't work on my TP, only settings that work are RAPH, and I was wondering for what phone are these RAPH800 settings??
Click to expand...
Click to collapse
I'm not sure how to answer your question. Babijoee's builds have a STARTUPS folder, do you not have this?

[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

[XAP + SDK] WP7 Root Tools 0.9

Download: www.wp7roottools.com
Today I am proud to announce the immediate availability of WP7 Root Tools 0.9 alpha and WP7 Root Tools SDK 0.1!
WP7 Root Tools 0.9 brings true Root Access to devices with stock ROM's, but it also works on devices with custom ROM's and Full Unlock. Your device needs to be Interop Unlocked to use WP7 Root Tools!
This is still an alpha-release, because there are a lot of new hacks and the tools are still not feature complete! I have rewritten about 75% of all code from the previous release. So before you install WP7 Root Tools you should make a backup of your device. WP7 Root Tools will make changes to system settings and, although this has been tested, it is still possible that a problem occurs. In that case you want to have a recent backup of your device. Installing WP7 Root Tools will be your own responsibility. The author of WP7 Root Tools and the SDK cannot be held responsible for any damages caused directly or indirectly by installing and using WP7 Root Tools or the SDK!
Windows Phone is a closed system to protect the user and his/her personal data from malware and to protect the intellectual property of the developers. The downside of this closed system is that homebrew developers are very limited in their ability to control and tweak a Windows Phone device. With WP7 Root Tools I attempt to open up the system in a gentle way, so that users stay in control of their device, while homebrew apps can get more control to get the maximum power out of your Windows Phone device!
WP7 Root Tools 0.9 now has a File Explorer, Registry Editor, Certificate Installer and a Policy Editor! Thanks to true Root Access on Windows Phone, this new version of WP7 Root Tools will work a lot faster than previous releases and it supports a lot more devices!
WP7 Root Tools should work on these devices:
- Samsung first and second generation devices
- LG devices
- HTC first generation devices with Mango v1 drivers (SPL 4.x or lower)
- Samsung first generation devices with custom ROM and Full Unlock
- HTC first generation devices with custom ROM and Full Unlock
On devices with stock ROM's WP7 Root Tools need to install Root Access. The first time it runs, a 2-phase-installation will start. The app will inform you to start the first install-phase. Then the device will reboot after a few seconds. After the reboot you need to start WP7 Root Tools again immediately! Then the second phase of the installation will start and your device will be rebooted again. After the second reboot you are ready to use WP7 Root Tools. You can use the Policy Editor to give other homebrew app a "trusted" status. With this you will give the app Root Access privileges. So be very careful to which app you give Root Access!! You are responsible for giving access to an app! If you are not sure, read the forums to decide if an app is trust-worthy.
I also created an SDK, which developers can use to profit from Root Access. It provides a way to gain access to the filesystem and the registry (and more) from their managed Silverlight application. No need to worry about COM interop and C++ anymore! The package contains a read-me with short instructions. More details and examples will follow soon! Over the last days Rafael Rivera from the Chevron WP7 team has tested the SDK and he is finishing up the first homebrew app that will use my SDK. He is planning to release his Backup-app soon.
I also need to thank some people for making this possible:
- My wife! (for having to put up with me while doing all this hacking!)
- YukiXDA (for helping me with research on policies)
- Justin Angel (for sending me a NOKIA)
- Cees Heim (for supplying an HTC device for testing)
- Rafael Rivera and Chevron WP7 team (for pioneering WP7 Unlocking)
- HD2Owner (for helping me make custom ROM's for testing)
- fiinix (for helping me with research on policies)
- Ultrashot
- xb0xm0d
- AndrewSh
- Ondraster
- Barin
- Football
- Cmonex
- GoodDayToDie
- Jaxbot
- Dennis Wilson
I will update the guides and manuals on www.wp7roottools.com and here on XDA in the next coming days. I need some time to update all of it.
Have fun with Homebrew now!
Heathcliff74

reserved*****

reserved***** (2)

reserved***** (3)

reserved***** (4)

thank you for your hard work

SO AWESOME!!! Thank You SOOOO Much!!!

big thx 4 all your work man!thxthxthx...
Sent from my OMNIA7 using Board Express

Previous Versions
Thanks for your great work. Do we need to uninstall previous versions before installing the latest version? I have .8, how do I install .9?

Great news, thanks a lot! Successfully installed on Focus and Surround, no problems at all.
But I've tried "BT file transfer" and "Opera mini" (after install I've enabled "trusted" status for the apps): both apps not working properly. Should we expect updated versions of these apps (built with your SDK) or it's some another issue?

Fantastic work, Heathcliff74. Oh man, this is going to be awesome.
Suggestion: use one of your reserved posts to compile a list of trusted apps that benefit from policy elevation.
Two that I've found so far (one of mine):
Root Webserver (in my sig) - runs better with Root Tools than ever before.
TouchXperience - gives way more access through WPDM.
Two others that are in development:
LockWidgets - the preview build has some bugs, but it can be run with Root Tools.
XapHandler - the test build has some known issues (can't install or update if the app is already installed) but fresh install works at least some of the time.

Awesome work! I can confirm that the install works perfectly on an LG Quantum.

Big day!
I need some free space in C:/ to make backup.

sensboston said:
Great news, thanks a lot! Successfully installed on Focus and Surround, no problems at all.
But I've tried "BT file transfer" and "Opera mini" (after install I've enabled "trusted" status for the apps): both apps not working properly. Should we expect updated versions of these apps (built with your SDK) or it's some another issue?
Click to expand...
Click to collapse
WP7 Root Tools will give Root Access to Silverlight apps. DFT BT and Opera Mini both use native executables. You can't give the executables root access with WP7 Root Tools (in fact, you only give the launchers Root Access). These apps could possibly be recompiled to run under TaskHost.exe (as all Silverlight apps do), but I'm not sure about the inner workings of the apps. You'd have to ask the developers.
I will investigate this matter. With all the hacks I have now, I should be able to give Root Access to executables too, but that needs more research.
Ciao,
Heathcliff74

@sensboston: Those tools both require additional native binaries. WP7 Root Tools elevates apps, including all the DLLs they load (which is how the SDK works - it's a homebrew DLL, similar to the old Native.dll and company). However, it doesn't work with out-of-process binaries. Opera requires an EXE (which is obviously its own process) and BT File Transfer requires a driver.
In theory, supporting these would be possible. They'd need to be signed, and the certificates added to the Code Integrity store, but that's already possible. However, they'd also need new policies added. The current version of Root Tool only supports modifying the policies for installed TaskHost (Silverlight/XNA, possibly including some native code) apps, not adding policies for other apps.
BTW, although it's very limited, it turns out that Application.GetResourceStream can be used on files outside the app (with sufficient permissions). That means, if you want to write an app that only needs to access existing files at known locations, you don't even need to mess with native code... although the Root Tools SDK will make it quite easy to do such apps anyhow.

Thanks HeatCliff
Thanks man for this wonderfull pice off work

Heathcliff74 Installed on My Omnia 7 Thanks a lot for your Hard Work

JamesAllen said:
Thanks for your great work. Do we need to uninstall previous versions before installing the latest version? I have .8, how do I install .9?
Click to expand...
Click to collapse
You can just reinstall. No need to uninstall. From this new version on (version after 0.9) you better do an "UPDATE". Not all xap-installers support updating. A lot of them will do a full-install-cycle. If you do a full-install-cycle, you'll loose the permissions and you will have to do the 2-phase-install sequence again. If you do an in-place-update, you will keep the permissions and everything keeps working as expected.
Heathcliff74

Damn, doesn't work for me.
Verizon HTC Trophy
OS 7.10.8107.89
Firmware: 2305.13.20110.605
Hardware: 003
Thanks for the work! Hopefully I'll see support later. I probably updated to the HTC v2 drivers at some point.

dreamcaster012 said:
Damn, doesn't work for me.
Verizon HTC Trophy
OS 7.10.8107.89
Firmware: 2305.13.20110.605
Hardware: 003
Thanks for the work! Hopefully I'll see support later. I probably updated to the HTC v2 drivers at some point.
Click to expand...
Click to collapse
Hmm. are you interop unlocked? I'm no expert with HTC's but that versionnumber looks like your drivers are not that new and could possibly be supported. If you are not Interop Unlocked, then read the opening post of my Interop Unlock thread. At the end of that post is a section specifically for Verizon Trophy's
Heathcliff74

2175.2907.8858.13030 New firmware available on navifirm

So someone flashed this new rom? What changes? I translated from china lumia 900's forum, here results.
1 used the State Bank 2175.2905.8858.12480 version as mastering.
The 2. Transplantation Lumia900 latest 2175.2907.8858.13030OEM.
3. Latest FULLUNLOCK V4 unlock procedure.
4. Using latest unlocking supporting software the Root rights management, gravity sensor, XAP deployment, file management, WM Device Center, the search key settings and Quick Start 7 software, and all models have added language to facilitate domestic players to use.
5. Supports XBOX game support IE ​​deploy, support for unlimited XAP deployment of PC.
6. Delete multiple languages, or English only reserved yet.
Other registry optimization, debug mode, the default time zone correction.
If you deploy third-party software requires full unlock permission, be sure to set it as a trusted Root rights management, or it may not work properly, no matter what the time, Root permissions to manage the software, you can not delete, or may some other unknown problems. The first time after the start of the Brush to wait a minute or a the Welcome Message pop-up in use. Remember! ! !
http://translate.google.com/translate?hl=ru&sl=auto&tl=en&u=http%3A%2F%2Fwww.wpxap.com%2Fthread-564190-1-1.html
http://www.wpxap.com/thread-564190-1-1.html

2907 is MX (Mexico?) country variant. Anyway works fine for me, better than 2905. Faster and more stable.

2175.2907.8858.13030
wow that's great! downloading!!!!!!!!!!! :fingers-crossed:

Hi there,
can you tell me what's the difference between 12480 and 13030 firmware?
In my custom rom i used the 12480 because it's the latest offical rom for all countrys...
13030 is only for Mexico?
Any recommendations?

Ok, somebody help me out here. I might be stupid. NaviFirm doesn't show this ROM for me. Is there a downloas link on the chinese web page somewhere that I cannot seem to find?

Even the Mecixo one has all languages in.