yashsingh1/xdaforums huggingface dataset:
[Windows Phone 7 Development and Hacking] Heathcliff74:
Correct :)

Correct :)

Correct :)
[Windows Phone 7 Development and Hacking] iEatRappers:
Nice looking forward to 1st gen HTC windows phone support...time to donate :D
[Windows Phone 7 Development and Hacking] DavidinCT:
Same here, I hope to see it ASAP :)
[Windows Phone 7 Development and Hacking] lucasryan:
Heathcliff, just wanted to see if it was possible to add a search option when inside the windows folder? I know it may seam pointless for some reasons, but i was using the app today and wasn't near my computer and wanted to see if i had a specific rom file, i flashed a rom and couldnt remember if the file was in the rom or not and i had to just scroll thru all the files to check.
[Windows Phone 7 Development and Hacking] derausgewanderte:
I am confused, you list LG compatible with your upcoming v0.9. I thought access to the system folders on LGs is not possible. Did I miss something ?
[Windows Phone 7 Development and Hacking] GoodDayToDie:
Well, elevating an app to TCB (effectively, "root" or "Administrator") is not supposed to be possible on *any* WP7 device. If Heathcliff74 managed that on Samsung & HTC, why not on LG?

WP7 Root Tools doesn't work the same way as the existing registry or filesystem apps (like TouchXplorer), which use OEM DLLs to provide access to OEM drivers that expose certain APIs, like registry or provxml. These drivers run with high permissions and can be used to access the whole device, but they typically only allow a few operations, so their usefulness is limited.

Instead, Heathcliff74 found a way to either elevate his Root Tools app to TCB directly, or execute arbitrary code within the driver, and used it to change the policies that control what user account (and therefore what permissions) an app runs under. Once an app has enough permissions, you can access the whole device just using the standard native APIs, including CreateFile and so on for filesystem access.

This is similar to how the HtcRoot Webserver works, using a hack to become TCB and then using native APIs to access the whole device. The difference is that Heathcliff74's hack works on a lot more devices and makes persistent changes to policies, whereas HtcRoot (currently) just elevates an already-running app.
[Windows Phone 7 Development and Hacking] derausgewanderte:
thank you for the explanation!
[Windows Phone 7 Development and Hacking] dmw_4814:
When can we expect to see version 0.9? I can NOT wait to get that on my Focus S!!

Dennis
[Windows Phone 7 Development and Hacking] LiFePo4:
Do not pester the devs; it will come in due time.;)
[Windows Phone 7 Development and Hacking] kennyx10:
Any news on Lumia 800 support for v0.9 yet?

Is Nokia really making it THAT hard? :(
[Windows Phone 7 Development and Hacking] Heathcliff74:
To all those dozens of people who mail/PM/DM/Tweet/post to me every day asking if a certain brand/model is already hacked:

There is really no point in asking these questions everywhere. I mean, if I or someone else finds a nice unlock-method, you'll read it everywhere on XDA and other sites.

With the hacks I have developed now, it is, for most devices, not hard to add support in WP7 Root Tools once a device is Interop Unlocked. Same for Nokia's. The main problem is Interop Unlock. Hacking and developing takes A LOT of time. I can't develop tools and hack all devices at the same time, you know. And YES! It is THAT hard to hack these phones. It's not only Nokia making it hard; it is mainly Microsoft making it that hard. Their security is really tough. If it were easy, then there would be an army of people hacking these devices in no-time. But it isn't that easy! I have a couple of angles to work on with Nokia and HTC devices. After I released the new WP7 Root Tools version I will concentrate on Interop Unlock for more devices and running native custom executables on stock ROM's. Those will be my next two projects.

So just be patient.. Bear with me, or start hacking yourself ;)

Ciao,

Heathcliff74
[Windows Phone 7 Development and Hacking] Rcf686:
Well said Heathcliff.
[Windows Phone 7 Development and Hacking] ManelScout4Life:
I'm not trying to sound rude but why announce 0.9, have it on several wp news sites, show screen shots but then not release it.

Kind of a tease
[Windows Phone 7 Development and Hacking] Heathcliff74:
I announced it because it is "nearing completion" and I'm excited about that. I've been working for months and months on this. And now it is almost ready to release, but not quite yet. So it won't be long before a release. I did call that screenshot a "teaser" and that's just what it is, for now.

Also, I didn't have it on serveral wp-sites. They write the news there, not me.

So just hang in there a little bit longer, while I finish up this new release :p:D

Ciao,

Heathcliff74
[Windows Phone 7 Development and Hacking] huismeester:
Thanks heathcliff for your hard work we all respect that you make it realy wonderful :)
[Windows Phone 7 Development and Hacking] GoodDayToDie:
Hey Heathcliff74, quick question: if you install WP7 Root Tools on an HTC phone with v1 (v0) drivers, and have it set the policies for itself to route to TCB, but then later upgrade to the v2 drivers or later, will it still be able to edit policies? In other words, do you only need compatible drivers to bootstrap the process, or are they required every time you want to edit policies?

I'm asking because I'd really like to get my phone back on the official upgrade path, but currently I can't do that because all my high-privilege hacks would stop working. Editing the policies directly is the obvious fix for this, and I'm guessing that once you've elevated the Root Tools app's policy, it will be able to make future policy edits without needing to use the drivers. I want to confirm that, though.

Also, on behalf of HTC Arrive owners, is it possible to compile a build of Root Tools 0.9 for 7.0 (pre-Mango)? That would allow them to install it if they were willing to revert the phone to NoDo (no interop lock) and install a non-ID_CAP_INTEROPSERVICES app that uses the native registry APIs to set MaxUnsignedApp. By elevating that non-interop app with Root Tools, they would be able to upgrade to Mango, interop-unlock their phone, and continue using homebrew. It's one of the things I've been hoping to achieve with the HtcRoot project, but at this point I'm guessing you will publish Root Tools 0.9 before I finish decoding the policy system.
[Windows Phone 7 Development and Hacking] voluptuary:
About the version for pre-mango that would be great. I ask for this also becuase I figured out how to turn my focus into a 100% unbranded 100% MS code base 'CETUS' using magldr and some messing around with custom/official firmware combos, and it would be super helpful if I could edit the registry after I put a clean 7004 rom on the phone to allow zune to update the firmware so I can get a new diagnosis version, although I guess I wouldn't even need the new diagnosis if I had a registry editor... either way +1 to the pre-mango idea.
[Windows Phone 7 Development and Hacking] Heathcliff74:
After initial installation drivers are not necessary anymore. So it will be kinda safe to upgrade. But if you somehow have WP7 Root Tools uninstalled, then you're screwed. You cannot install it again if you did upgrade the drivers in the meanwhile. Also, it is possible to remove root access for WP7 Root Tools itself. So that will lock yourself out too, if you did upgrade the drivers.

That would be kinda difficult. I had to update a lot of components to let it work properly on Mango. So there is no easy fix. But I think I can make some kind of Nodo installer. I will look into that after the release of the tools and sdk.

Ciao,

Heathcliff74
[Windows Phone 7 Development and Hacking] Heathcliff74:
Can you tell me why you want this exactly?

- Why are you flashing 7004 and not a new version?

- What exactly do you need a registry-editor for in that old version?

- Why don't you replace the old Diagnosis app in the rom?

Ciao,

Heathcliff74
[Windows Phone 7 Development and Hacking] voluptuary:
I have to start at 7004 becuase thats the only version I know of directly from samsung. As far as a I know there is no firmware from samsung that is newer for the focus aside from maybe the v1.4 one. Anyways using the official firmware and then using magldr to 'interrupt' the csc from being applied I can get a 'pure' unmolested verion of WP7 on my phone. It's just limited in that the samsung driver updates that enable ICS and new diagnosis version are tied to the carrier.

I would need the registry editor to change the device name and other things that I can't do otherwise since the diagnosis version is too old on 7004.

The reason I don't replace the diagnosis in the ROM is becuase there currently is no way to edit a non-molested samsung rom via the current kitchens. The only option at this time is to use DFT's as a base. There are poeple working on it but... that could take quite some time.

I, mistakenly I guess, assumed you could just re-release an earlier version of root tools (one that had expired) that had been working prior to mango. But if not, no big deal, I'll just wait till the kitchens support stock/dumped roms.
[Windows Phone 7 Development and Hacking] Heathcliff74:
Ok. But you would update to a recent version. So, you could change the device-name right after you updated to Mango, right? Maybe I don't understand it, but in your case I fail to see why you would need the Root Tools in NoDo. Upgrade first, then use Root Tools.

Ciao,

Heathcliff74
[Windows Phone 7 Development and Hacking] voluptuary:
I can't interop unlock once upgraded to mango without the new diagnosis version, so I would need to do it pre-mango.
[Windows Phone 7 Development and Hacking] Heathcliff74:
Ok. I don't have a lot of experience with ROM cooking. So excuse my ignorance.. But unlocking should be really easy with custom rom's, isn't it? Just add an rgu and dsm with unlock-settings and you should be good.

What kitchen are you using? I can recommend OS Builder by Barin and Ultrashot.

Tell me where I'm wrong...

Ciao,

Heathcliff74
[Windows Phone 7 Development and Hacking] voluptuary:
Well, as I had said before the current kitchens out, os builder included, don't work with stock/dumped samsung roms. They work with the DFT rom but that one, while having many nice features, is also very buggy and to use that as a base would be less than ideal. I currently am trying to edit the registry using non-cooked means.

Anyhow, if it isn't a simple process, don't worry. I will just wait till AnDim, Barin, and Ultrashot get thier tools to work with samsung roms like they currently do for htc ones.
[Windows Phone 7 Development and Hacking] Heathcliff74:
Ok. I'll ask Cees Heim and Ultrashot to comment on this. I know for sure Cees has had success with creating a working samsung rom with OS Builder.

I will have have a look at NoDo compatibility later.

Ciao,

Heathcliff74
[Windows Phone 7 Development and Hacking] Marvin_S:
have you tried taking the dlls of the most recent samsung apps and then use those for provxml?

Those dlls

*should* work for registry edits on earlier versions than mango also.

I can send you the DiagProvXML project which only uses one mango API to determine the OEM. Since you will use it for a samsung you can easily hardcode/copy the appropriate methods in a 7.0 project.

Just PM me if you want to try it.
[Windows Phone 7 Development and Hacking] ceesheim:
yes I have been able to dump a stock rom from phone and redump it with OSB (htcrie can dump it but I use OSB because it has a real cool .cab installer) I even build a rom using a engineering build (7720) and updated it to 8107.

BUT you need OSB to update the stock to the latest ( and sorry to say but a 7004 build cant be updated to 8107 with OSB)

so I would say , flash a engeneering rom ( build 7720) and dump it before the phone boots again, then dump it with OSB , then Imageupdate it to 8107, then play with OEM updates ( be carfull with some OEM packages because it can mess with the shadow list on .dsm)

then cook the rom and flash it :)

the main key is: don't let the phone boot after stock flash, then dump with magldr, then redump with OSB.

oh and when you flash , DON'T flash the Eboot :) because it will change the phone to a engineering model and you can't flash MAGLDR on a engineering model (you would need to flash a retail eboot then and that can be hard :) )
[Windows Phone 7 Development and Hacking] ceesheim:
Good Work Cliff

don't want to be rude but I don't see any reason why you should look into that , there are easy ways to make custom roms (even stock 100% clean ones :) , and on a custom rom it is a matter of seconds to make it dev/full/interop unlocked :)

if I where you I would use my time for other cool stuff :D

oh and Cliff , you did a hell of a jop and we love you all for that :)

Greetings my friend.
[Windows Phone 7 Development and Hacking] voluptuary:
Well, I guess I'll have to try and find a newer rom for the focus, last I checked there wasn't but perhaps I didn't look hard enough.
[Windows Phone 7 Development and Hacking] bakerahmed:
I have tried running the WP7 root tools 0.8

on (Focus S) but says: incompatible, can work only on samsung device

any help ?
[Windows Phone 7 Development and Hacking] Nickg.:
The 2gen Samsung device isn't supported yet
[Windows Phone 7 Development and Hacking] GoodDayToDie:
Reading, it's fundamental. It's been pointed out many times that the second-gen devices (Focus S and Focus Flash/Omnia W) are not supported by 0.8 or below, due to changes in the high-privilege drivers used by OEM and homebrew apps.

WP7 Root Tools 0.9 will work on the second-gen Samsung phones, but it's not out yet. Please don't ask for ETAs, it's pretty close (there are screenshots in this thread already) but there could still be a lot of work to do, especially if testing turns up any problems. It might not even be fully working on other devices besides Samsung gen1 yet.
[Windows Phone 7 Development and Hacking] djdurance:
Is this the only method of getting a registry editor working? I am waiting for this to work on my Focus S... unlocked and ready to go.
[Windows Phone 7 Development and Hacking] DavidinCT:
oh, where are u 0.9 ?
[Windows Phone 7 Development and Hacking] korrel2008:
Yes i am also waiting for the unlock for the HTC titan, still hate that the tokens are sold out, i hope the guy is making good progress here, i will buy him a couple of beers if he is getting the unlock working. :)
[Windows Phone 7 Development and Hacking] Dr.Mazika:
is there a topic for htc titan unlock or 2nd generation devices unlock
[Windows Phone 7 Development and Hacking] lucasryan:
All thru this thread it says that 2nd genration devices are not supported yet.
[Windows Phone 7 Development and Hacking] korrel2008:
Is there any progress with the unlock?, can you please give us some information?

thanks

Dave
[Windows Phone 7 Development and Hacking] GoodDayToDie:
Please don't bug the devs with questions like this. Developing hacks is time-intensive, time which must be fit around our existing lives (school/work, social/family, major events which disrupt daily life, etc.). Even when the time is available to work on hacks, it is all but impossible to estimate how close you are until right before release; each piece can be easy or difficult and there's really no way to know in advance. That includes things like taking something that works on one phone and putting it on others, or fixing a bug that only happens 5% of the time but corrupts things when it does, or...

So... yeah. What would you do with this info even if you had it? I assure you, Heathcliff74 is still working on the app. It is a week closer to release than it was a week ago.
[Windows Phone 7 Development and Hacking] DavidinCT:
How's progress coming along?

Not asking for a release date or anything but, it's too quiet in here, so I figured a bump is in order....

Hope progress is moving forward :)
[Windows Phone 7 Development and Hacking] korrel2008:
No news is good news, that is what they say here......but yes i also have the same question...it is indeed to quiet :)
[Windows Phone 7 Development and Hacking] Heathcliff74:
Don't worry! REALLY! ;)
[Windows Phone 7 Development and Hacking] revxx14:
Kind of a noob question, but is there any way for me to use this to use Jaxpot's LockWidgets application? http://windowsphonehacker.com/articl...phone-03-20-12

I'm hoping not to have to try and install a custom ROM, I'm already Dev and Interop unlocked.
[Windows Phone 7 Development and Hacking] voluptuary:
@Heathcliff74: Does Root Tools 0.8 have an expiration date? And if not can I include it in my DFT rom variant? I would be making a small modification to it by having it install in settings as "root tools : sub title 'registry & file explorer'" I ask becuase I don't want to include anything that possibly won't work in the future especially after something like say a hard reset. I kinda want everything to 'just work'
[Windows Phone 7 Development and Hacking] fastbone:
Works like a charm

Thank you!!!

Keep up great work.
[Windows Phone 7 Development and Hacking] EnderPsp:
Current version of WP7 Root tools (0.8) expires on 1st of July 2012.
[Windows Phone 7 Development and Hacking] Heathcliff74:
I don't mind if you use WP7 Root Tools in your rom. 0.8 will indeed expire at july 1st. I don't know why it wouldn't work after a hard reset. 0.9 will also have an expiration date. I will probably keep the expiration data until it is past alpha and beta phase. If users of your rom expirience expiration, they could always update themselves.

Version 0.8 will work normally. Version 0.9 has a completely different approach. On roms with full unlock it will also run normally. But if you run it on a device without full unlock, it will begin with a 2-phase-installation to get true root access. First time you run it, it will perform the first install phase and then reboot. Then you must run WP7 Root Tools again and it will do the second install phase and reboot again. After that you can run WP7 Root Tools normally with full root access and the ability to give root access to other apps too.

Ciao,

Heathcliff74

I can hear the sounds of drums from afar...
[Windows Phone 7 Development and Hacking] ceesheim:
welcome to the club of 1000 :D
[Windows Phone 7 Development and Hacking] Heathcliff74:
Heheh.. Thanks Cees for Thanks Meter @ 1000 ! :D
[Windows Phone 7 Development and Hacking] spavlin:
when we will see version 0.9
[Windows Phone 7 Development and Hacking] ceesheim:
who knows :D
[Windows Phone 7 Development and Hacking] voluptuary:
First thanks! Second, I ment after the expiration and a hard reset it wont 'just work' but as you said it's true they could just update it, though it would end up back in the app list again.
[Windows Phone 7 Development and Hacking] korrel2008:
Seems to me that it will be there soon :)......thanks heathcliff and other devs for youre time to make this for us
[Windows Phone 7 Development and Hacking] Heathcliff74:
I see in your signature that you have an HTC Titan. WP7 Root Tools will need at least Interop Unlock. Currently there is no Interop Unlock for HTC Titan available. I hope you realized that and I don't disappoint you too much.

Ciao,

Heathcliff74
[Windows Phone 7 Development and Hacking] korrel2008:
I am aware of that, so no i am not disappointed :o, but it is good to know that when i have interop that i can use this tool also :)
[Windows Phone 7 Development and Hacking] Heathcliff74:
I can confirm this works with WP7 Root Tools 0.9 :D

And by the way, it's "Jaxbot", not "Jaxpot" :p
[Windows Phone 7 Development and Hacking] sensboston:
Wow, wow, wow!!! This sounds very enticing and so intriguing! Seems like you did it... again :) Please don't publish vulnerability details for gen public: it looks like Nokia guys (at least) are monitoring XDA all day long...
[Windows Phone 7 Development and Hacking] kirk999:
maybe they're monitoring, but for sure they can't stop Heathcliff74 :D
[Windows Phone 7 Development and Hacking] sensboston:
Yeah, they can't stop Heathcliff74 but can close the security hole. So, 'cause I'm waiting for Lumia 900...
[Windows Phone 7 Development and Hacking] ManelScout4Life:
Heath, are we close to a release :-D?!
[Windows Phone 7 Development and Hacking] DavidinCT:
Same here... Can't wait to try this on my CDMA Trophy.

This is the first thread I check every day I log in here...
[Windows Phone 7 Development and Hacking] Timb320:
HTC HD7 Interop Unlocked_dev-Unlocked with V2 drivers?

So I'm asking because its not 100% clear, but I have Interop Unlocked Pre Mango + dev Unlocked and updated to V2 drivers and on 8107.

I assume that this should still allow me to run WD7 Root Tools 0.9 in this scenario right? I guess I will need to test and find out. :):D
[Windows Phone 7 Development and Hacking] revxx14:
Sweet, super excited for it.

And thanks for the correction, I caught that a few minutes after posting but didn't have time to fix it lol...Not new to Windows Phone hacking, but I am to following development, so I've been getting the names confused :p
[Windows Phone 7 Development and Hacking] Omnia7xdax:
I know it´s out of topic ,but to funny ,jaxpot wouldn´t have been a bad name:D:p

(because of its sound and the assoziation with jackpot from lottery ,reminds me everytime that jaxbot is a win in everycase for developement;))
[Windows Phone 7 Development and Hacking] Heathcliff74:
Sorry to say this. But in order to get the new WP7 Root Tools working on HTC you need Interop Unlock and you need to have NoDo drivers (SPL 1.x) or Mango v1 drivers (SPL 4.x) or custom ROM with Full Unlock. Mango v2 drivers (SPL 5.x) are not going to work for stock ROM's. I tried to make it work for all Interop Unlocked HTC's, but so far not succeeded.

After the release of the new Root Tools I will concentrate on support for more devices / driver configurations, like HTC 2nd gen and NOKIA.

Ciao,

Heathcliff74
[Windows Phone 7 Development and Hacking] Heathcliff74:
Testers needed!!

Hey guys,

I need some help. I've done some private test sessions. Current status:

- Samsung 1st generation with Interop Unlock: OK

- Samsung 1st generation with Custom ROM and Full Unlock: OK

- HTC 1st generation with Mango v1 drivers and Interop Unlock: OK

- HTC 1st generation with Custom ROM and Full Unlock: OK

- LG with Interop Unlock: Not Tested

- Samsung 2nd generation with Interop Unlock: FAIL

I have done test for LG in the past, but since then a lot has changed. Mango has a lot of extra restrictions, so I made a new test app for LG. First make sure you are Interop Unlocked. Then please run test app and give me the results IN DETAIL! If 1 or more test don't pass, please reboot and try once again. In that case I would like to have test results from both tests! Also report OS version and OEM Firmware version.

I was surprised that the Samsung 2nd generation device did not work properly. I was quite sure it would run without problems. So I made a test app for those devices too. First make sure you are Interop Unlocked. Then please run test app and give me the results IN DETAIL! Also report OS version and OEM Firmware version.

Thanks a lot for testing!

Heathcliff74
[Windows Phone 7 Development and Hacking] Timb320:
Thanks For your efforts Heathcliff74,

It just so happens I have the ATT Nokia Lumia 900 on Pre-order anyway 2 weeks and counting. :)