Yeah, is there any file explorer for non-HTC phones out there? I'm tempted to get a lumia 800.
Several (and most don't rely on device-specific code the way TouchXplorer does). Hell, WP7 Root Tools has been out for over a year, though it used to be Samsung-only. However, all of the file browsers require at least interop-unlock, and most require root-unlock (or full-unlock). Only a very few Lumia 800s can be unlocked that far; it requires an older bootloader that new models don't come with anymore,a nd nobody has found a way to flash the old bootloader back onto them (the Lumia 710 can be reverted, but not yet the 800; the 900 and 610 never used the relevant bootloader).
Aside from the Lumia 710, two of the gen2 HTC phones (Titan and Radar) can be full-unlocked using custom ROMs. Currently there are no custom ROMs for the gen2 Samsungs, but if you get one with old enough firmware (unlikely, but you may get lucky) you can use WindowBreak and then install Root Tools.
Meh, so my best bet is to wait and see what WP8 comes up with?
The only reason is mostly using other formats (e.g. PDF) for different things. I'm not a huge internet user, and I'm not too jolly that I gotta move some files in the cloud and then download them to my phone.
I wouldn't hold my breath for a WP8 file browser. Microsoft does not seem to be interested in giving anyone this capability. Furthermore, it could take very long time until there will be any WP8 unlock, due to the inclusion of Secure Boot (if there will be any at all - in case Microsoft implements proper bottom-up validation it could be possible that no application can run on SYSTEM privileges unless signed).
Be that as it may, why is a file browser so important to you? I don't find it too helpful in WP (except for hacking/developmental purposes) as you have IsolatedStorages (which are a mess to dig in from a file explorer), other folders like Windows and the Zune content store (of which the latter could be accessed per USB if wanted).
Anyways, the HTC Titan is a very nice phone to have, and so is the Lumia 800. I wouldn't purchase too much after what is unlocked yet, but rather after what you find best value in.
Related
I have Purchased the G1 Thinking the overall architecture of Open Source Application, Android API, Equality of Application bla bla.
But after see the Handset i think it only Open for Source Code
neither we can create own on Modified Images nor we can change the Device at Root level. Its same f*cking thing like Apple iPhone Jailed and no Root Access.
We got some Android SDK but whats the use we can Create same Application for iPhone and Windows Mobile also. Infact in WinMob we have thousand of Software running nicely.
I am very Disappointed the way G1 is Locked with the Open Source OS.
i think in the name of Openess G1 device have locked everybuddy to f**k around with T-Mobile and Google only Service. Android Market have very Little apps which can Surprise me after all that hype of Software Availability. Infact 1st Generation iPhone had more Application which Developers have Developed without help of any SDK from Apple. G1 really sucks.
Well, i regret that fact too, but in fairness they never said the device would be open. What they said was "You can make your own device and use Android on it".
It's sad that T-Mo didn't get the "open" part but in all case my hopes are with chinese device manufacturer who don't care for 5 minutes what you do with their hardware as long as you buy it. Or maybe OpenMoko but their design is really ugly
Okay, being able to type commands on the keyboard and have them executed as root from anywhere on the device IS NOT SAFE.
What happens when someone tells you to type rm -rf / and hit enter? Brick? YES from anywhere on the device. Even from the lock screen.
They are not locking down the phone again, they are fixing a MAJOR bug. The phone is not "Jailed."
its said when god closes doors he opens new ones
Since the door is closed, how to put your own native lib to the system? Is there any way to use native lib?
sadly i find both Android and iPhone OS as restrictive.
because nope of Future Manufacturer is gonna allow us the Flash the Customised Android to Phone unless we know the Private Key of that Manufacturer. There is nore of Legal way to do much powerfull Developements in Kernal , drivers or boot loader of Android etc. What we got is that Ugly ADB thing which itself is so much Restrictive. I feel like am developing the software again as what we have done in Java on Mobile for Sony Ericson etc.
Google could have offered us a Safe but Power full access to hardware for Customized OS. and they could also have safeguarded device from Possibly bricking by bad flashing.
I think Phone OS should more like Installing Linux / Windows into Computer rather then Boot loader and so on.
hetaldp said:
I have Purchased the G1 Thinking the overall architecture of Open Source Application, Android API, Equality of Application bla bla.
But after see the Handset i think it only Open for Source Code
neither we can create own on Modified Images nor we can change the Device at Root level. Its same f*cking thing like Apple iPhone Jailed and no Root Access.
We got some Android SDK but whats the use we can Create same Application for iPhone and Windows Mobile also. Infact in WinMob we have thousand of Software running nicely.
I am very Disappointed the way G1 is Locked with the Open Source OS.
i think in the name of Openess G1 device have locked everybuddy to f**k around with T-Mobile and Google only Service. Android Market have very Little apps which can Surprise me after all that hype of Software Availability. Infact 1st Generation iPhone had more Application which Developers have Developed without help of any SDK from Apple. G1 really sucks.
Click to expand...
Click to collapse
Well, I also miss a lot of stuff in G1 at least. System is so powerful, but closed, only thing in G1 is you can change batter if necessary and put bigger size transflash. I miss SIP, for every text entry I have to type using keyboard everytime. The other major issue, which Kaiser (Tilt) addressed very well, is removing battery cover to change SIM card. I have good number of Windows Mobile phones and iPhone before G1. I take different phone, whatever matches my belt or whatever I feel like, and changing SIM card is pain except for Kaiser and iPhone. G1 taking out the battery cover is so bad, it is like having older Dell desktop lying under the table and plugging a usb device. For older dell lattitudes, you have to knee down and push your usb cable angularly, otherwise it would either screw the usb port or you could push it for good time. The same goes to G1, you have open the keyboard, push the latch little and push your battery cover slowly to righside. Not a good idea, if you change phones daily like me.
Like the other one said, if you have root privileges, you could brick your device, if you don't have one, you don't know what you are doing. TMob and HTC screwed Google big time on this. I don't know how much control Google has on device makers and carriers. I see same pattern that Microsoft is struggling with WinMo devices here. At least in the case of Microsoft, we can easily play around devices without bricking like writing apps is easy, finding apps is easy and hacking device without bricking easy, at least if somebody doesn't have time to hack, they could easily look at our forum (XDA) and be creative.
my 2 cents.
--Ram--
I hate to say it but 99.9% of the customers T-Mobile is marketing don't care about having root access or installing operating systems on their phone or having easy access to their SIM card. I'm a programmer and I don't even care about that kind of stuff for my phone. The difference between this and something like the iphone is that you can write an app to replace pretty much anything you see on any screen on the phone and post it in the marketplace. Even with things like an on-screen keyboard there's no reason why it can't be done, there's just nobody who's made one yet. Hell, we already see apps that won't ever exist for non-hacked iphones(the 3 or 4 video players out there, tunewiki and other audio players, AndNav and things like the app that turns on your screen when you get an SMS message). If you really care about that stuff, return your G1 and get a OpenMoko or something similar.
I'm interested to see what the future holds for factory unlocked Android devices. Maybe T-Mobile decided the G1 cant be offered unless they have control over the firmware. When the handset manufacturer isn't tied down to these restrictions, it is possible that will grant root access by default.
As far as the possibility of bricking the phone, that is a stupid argument IMO. First of all, its my phone which I paid for which should give me the right to do what I want with it. Second of all, it should be brick proof to begin with. If I completely corrupt the filesystem, I should be able to go into the bootloader and and flash a new image to the device.
Hi,
As per the subject, I have been given a Windows Phone 7 device and been tasked to see if a root/user certificate can be extracted from the phone.
We install certificates onto mobile devices such as iPhones, to allow IPSEC VPN tunnels and secure access to exchange servers.
Using the tools I found on this site, I have managed to unlock my test WP7 device, installed the root and user certificates on my WP7 (I downloaded it from our test site) and I also install Advanced File Explorer on WP7 phone.
Based on my rudimentary research, the Certificate Store is not accessible on a WP7 device and the only to remove a certificate from the store is to reset the phone to factory settings.
In the root of the WP7 phone, there is a file called drmstore.dat. I have used Advanced File Explorer to copy this file to my desktop and using NotePad++ see that it does have some MS root certicates in there. But is this the file that would contain the user installed certificates?
My WP7 experience is limited to 3 days so far, so was hoping somebody could point me in the right direction wrt to file location. From what I've read, the OS does seem to be designed really well, so I am hoping that it is indeed impossible to extract the certificate from the device.
The only reason we are doing this test is to work out if the new phone is secure as it is getting difficult to get hold of Windows mobile 6.5 phones as the days progress. The problem is that WP7 phone dont support disk encryption yet (or so I believe) hence the worry ...
Many thanks in advance for your help and pointers.
if the phone is locked then it is really impossible to get it off the phone.
after the update from MS we aren't able to unlock the phone again so I think it is pretty save.
maybe you could look at a dump of a rom to find out where the serts are stored.
Thanks for your reply.
There are interesting times ahead.
The Chevron WP7 exploit will be closed but hte Touchxplorer developer claims that his solution will still allow full file access to system, so I am waiting with bated breadth to see how it all pans out. And who knows, we may have Nokia announcing that they will be using WP7 as an OS for their Nokia hardware on Friday.
Since I am not to au fait with the structure of WP7 phone (and I don't even know why I was given this job considering my hacking skills are about 5%) would you have an inkling as to where they sort of could be kept or how to read or even create a dump of the ROM?
Many thanks. I will search on the forums to see if I can get more information.
Thanks again.
Hi,
exist or someone developing homebrew app for sending files over Bluetooth ?
Thanks.
not at the moment
that's shame
I think it will come only if MS decides to bring this feature to WP. Search this forum there are links where you can vote for it.
Actually, it *might* be possible to implement it using homebrew - there are standard WinCE APIs for BlueTooth. If they are available on WP7 as well as WinMo and Windows Embedded, and aren't security-restricted, then it could be done.
I'd volunteer to take a look but I'm working hard on something else (and far more promising, IMO).
GoodDayToDie said:
Actually, it *might* be possible to implement it using homebrew - there are standard WinCE APIs for BlueTooth. If they are available on WP7 as well as WinMo and Windows Embedded, and aren't security-restricted, then it could be done.
I'd volunteer to take a look but I'm working hard on something else (and far more promising, IMO).
Click to expand...
Click to collapse
Would be great if you tried once. What are you working on right now?
btw, your OEM marketplace xaps were great. Keep up the good work
Right now, I'm working on the HtcRoot project, and various offshoots of it. Essentially, I want to add the advantages of a custom ROM into stock ROMs and, where possible, without forcing people to reset their phones. Part of this process involves writing tools for my own use, some of which I also publish. For example, the HtcRoot Webserver has essentially replaced TouchXplorer for me, though TX used to be a standard part of my toolset.
Considering the existence of the Contacts Transfer app in the Nokia store, which uses Bluetooth to transfer contacts from other phones and appears to run on non-Nokia phones (yep, I used my own OEM Marketplace XAPs to get it), I'm pretty sure at least some level of access to Bluetooth is possible from a WP7 app (using native code, of course).
GoodDayToDie said:
Actually, it *might* be possible to implement it using homebrew - there are standard WinCE APIs for BlueTooth. If they are available on WP7 as well as WinMo and Windows Embedded, and aren't security-restricted, then it could be done.
I'd volunteer to take a look but I'm working hard on something else (and far more promising, IMO).
Click to expand...
Click to collapse
Wow, that's a thrilling news
I'm not sure if you know but there are a lot of users who badly need this.
See here
GoodDayToDie said:
Right now, I'm working on the HtcRoot project, and various offshoots of it. Essentially, I want to add the advantages of a custom ROM into stock ROMs and, where possible, without forcing people to reset their phones. Part of this process involves writing tools for my own use, some of which I also publish. For example, the HtcRoot Webserver has essentially replaced TouchXplorer for me, though TX used to be a standard part of my toolset.
Considering the existence of the Contacts Transfer app in the Nokia store, which uses Bluetooth to transfer contacts from other phones and appears to run on non-Nokia phones (yep, I used my own OEM Marketplace XAPs to get it), I'm pretty sure at least some level of access to Bluetooth is possible from a WP7 app (using native code, of course).
Click to expand...
Click to collapse
yes, lot of people miss sending the files via Bluetooth,
So if you can add it as first priority it will be very helpfull
for all of us "geegs" which want to use WP7 platform
as geeg platform.
Will you be able to convert Junos Pulse client for winmo
to convert WP7 to run it in native mode?
Thanks for info.
GoodDayToDie said:
Right now, I'm working on the HtcRoot project, and various offshoots of it. Essentially, I want to add the advantages of a custom ROM into stock ROMs and, where possible, without forcing people to reset their phones. Part of this process involves writing tools for my own use, some of which I also publish. For example, the HtcRoot Webserver has essentially replaced TouchXplorer for me, though TX used to be a standard part of my toolset.
Considering the existence of the Contacts Transfer app in the Nokia store, which uses Bluetooth to transfer contacts from other phones and appears to run on non-Nokia phones (yep, I used my own OEM Marketplace XAPs to get it), I'm pretty sure at least some level of access to Bluetooth is possible from a WP7 app (using native code, of course).
Click to expand...
Click to collapse
Yes, you are right. The Contacts Transfer App is proof that transfer via bluetooth could be possible. And yes, I installed the Contacts Transfer app using your app
Hey folks, I've done a fair amount of reading up and have come to the conclusion that homebrew apps that access the registry to make changes to phone features (like Advanced Config) will not work on 2nd gen Windows Phones (like my Focus Flash) as the situation stands.
I've seen more complicated methods arise to make some of these same changes (complicated to me, likely not to many of you. I could make these hacks work if I needed to, but am as likely to screw something up). My question is, are we likely to eventually see these 2nd gen phones hacked and opened up the way the 1st gen phones were, with app registry access and even custom ROMs, or are we looking at a different landscape for Windows Phone these days?
Should I wait and keep my eyes open for the status quo to change, or am I currently looking at the extent of Windows Phone development/hacking for the 2nd generation?
Well, Heathcliff74 says that the next version of WP7 Root Tools (v0.9) will support Samsung gen2. WP7RT includes registry and filesystem browsing, but the new version will also allow you to mark any app for running always in TCB ("root" or "admin") which will allow you to use many additional apps, such as Root Webserver and a few other things I'me currently working on (installation of XAPs from IE for example, if I can make it work on partially-locked phones).
Hi guys, is there a clean generic windows phone 7 os? just like desktops were we get a retail os, is there one for phones? and is it flash-able with all phone?
No
No.
It would certainly be interesting to get hold of the OS as Microsoft delivers it to OEMs to begin the process of adapting it to a certain phone model, writing or modifying device drivers, etc., but it seems nothing like that was ever leaked.
WP is closed, as is iOS; for the reasonably open Android there is of course something like a "generic" version; you could even compile and produce one yourself.
There isn't really any such thing as a "clean generic" phone OS, anyhow. Unlike desktop OSes, phone OSes don't ship with support for the massive array of hardware configurations that are found in the wild. Instead, phone OSes rely on a Board Support Package, commonly simply called the firmware, which has the various drivers needed to interface with that specific model's hardware. This is why, for example, even though the source code is available for the Android Open Source Project upon which CyanogenMod is based, it still takes a long time to get fully functional CM ports to each individual device. On things like WP7, where the source code isn't available (except for the kernel and some core libraries), it's even harder.
However, if what you really mean is you want a "clean" ROM that has no carrier customizations in it, there are "open market" ROMs available for many WP7 devices. These ROMs are still specific to the device whose BSP they contain, but are not specific to any mobile operator and usually not to any region.
thanks for the info guys, but it looks like there are no open market roms for the omnia w yet, well, not yet anyway, will keep an eye out now that i know what to look for,
thanks again guys
Answer is yes and no. No oem device created by Microsoft, but there is Nokia. As you know Nokia is part of Microsoft Windows Phone hardware partner. More options etc has Nokia.
Sent from my Lumia 900 using Board Express