Database Info

Convert Android Dev Phone to T-mobile image

Hi,
I'm considering purchasing the android dev phone since I'm not on the t-mobile network and need the phone w/o a contract. I'm aware that the latest version of the dev phone allows you to install paid apps, but not locked apps.
My question is, is there any way to convert my dev phone to an (unlocked) t-mobile image so that it will support paid and locked apps?
Please excuse me in case my question hasn't been framed properly or if it has been asked before, I'm new to these forums and the whole G1 bit.
Thanks in advance.

I'm also curious about a similar question, which is precisely the opposite:
I have a Tmobile phone, running JF1.42. If I change my firmware to ADP1.1, is that going to cause me to not be able to view locked apps on the market?

If you purchase the Android Developer Phone, yes you can flash it to the T-Mobile firmware (search forums for downgrading to RC29 using DREAIMG.NBH and etc) and no, this will not affect your unlock. The unlock is at a separate level (research baseband, and cellphone unlocking).
If you change your T-Mobile G1 to the ADP1 image, yes, you will lose paid apps in the market. Google is blocking the ADP images from accessing the paid apps. (from what i've been told this is done through a user-agent check, and not device id, although i could be wrong).
Hope this helps you guys out

Only protected Apps are not accessible by Dev phones.
Not all paid Apps are protected, only few paid Apps are protected.
As you can see from my sign., I have a T-Mobile G1 phone with a mod Dev firmware. I can buy applications, however, I can't even see protected Apps.

One more question based on this. I've been reading through the forums and I've read that the dev phone comes with a DEV SPL. So basically I wanted to clarify that, the SPL doesn't matter if it is DEV/HARD. I can install the RC33 image by doing the whole RC29 downgrade, etc?
Probably way off here, but if anyone can point me in the right direction. Basically what I'm trying to do is, purchase a dev phone, get the latest rc series on it (and hopefully receive OTA updates). Or is getting OTA updates a bad idea? and I should continue to manually update the image as and when new ones are released?
Thanks in advance.

Flashing custom roms

I'm more of an android guy but my dad uses a hd7 that he also will use to tether. The current way he is doing it is that he is on NoDo (pre-mango) and the dial up hack (his HD7 is chevron unlocked). I was interested in flashing a Mango rom that has wifi internet sharing so I searched and think I have the method down for the most part but just want to make sure.
1. Charge battery up to 50%+
2. Hold power down while rebooting and go into OSPL mode
3. Flash RSPL (the temporary one) (basically follow directions in this thread: http://forum.xda-developers.com/showthread.php?t=1195647)
This is where I'm not quite sure if the steps are correct
4. Download the rom file and launch the .exe file (the phone is a TMO HD7)
Am I missing anything? I'm sorry if there is a how-to flash a rom but I didn't find a how-to that had a step by step.
Also, is there a major difference between the roms in the development section?
Thanks a lot!

You've got the basic idea, yes. I think for a full ROM you *might* need to use HSPL instead of just RSPL, but I'm not sure (and if you can do RSPL you can do HSPL too, easily). Custom ROMs typically come pre-packaged in a "RUU" program - that's ROM Update Utility. If you want one that's just available as a binary image, you can download the RUU separately.
The major differences between the ROMs will be things like:
What devices are supported (HD7 = Schubert).
What features are supported (not all Mango ROMs will have Internet Sharing via WiFi, for example).
What tweaks are included (most should come pre-unlocked, at least).
Anything that *doesn't* work (watch ut for this list).
What update mechanisms the ROM supports (custom CABs are common, for example).
Generally speaking, the DFT ROMs are pretty good, though many people use their ROMs as a base to build in additional capabilities.

GoodDayToDie said:
You've got the basic idea, yes. I think for a full ROM you *might* need to use HSPL instead of just RSPL, but I'm not sure (and if you can do RSPL you can do HSPL too, easily). Custom ROMs typically come pre-packaged in a "RUU" program - that's ROM Update Utility. If you want one that's just available as a binary image, you can download the RUU separately.
The major differences between the ROMs will be things like:
What devices are supported (HD7 = Schubert).
What features are supported (not all Mango ROMs will have Internet Sharing via WiFi, for example).
What tweaks are included (most should come pre-unlocked, at least).
Anything that *doesn't* work (watch ut for this list).
What update mechanisms the ROM supports (custom CABs are common, for example).
Generally speaking, the DFT ROMs are pretty good, though many people use their ROMs as a base to build in additional capabilities.
Click to expand...
Click to collapse
Thanks for the reply, it really helps knowing you have a understanding of something before you actually attempt to do it lol.
I figured out the Schubert information just reading about it and the rest I figured out while browsing over the roms. I think I'm going to go with this one for my first flash.
http://forum.xda-developers.com/showthread.php?t=1271118
Thanks again for the help and hopefully all goes well.

DeepShining is popular as a high-capability ROM (lots of features), but be sure you read the Known Issues list. Things like possible problems with Connection Setup may be a problem if you use it for its legit purpose (fixing connection settings) very often, and the inability to use the CAB sender means future updates will probably have to be full ROM re-flashing.
If your dad has any app data on the phone that he'd like to preserve, such as game progress or things like that, let me know before you flash his phone. I've got an HTC data backup app that I'm ready to start a limited alpha test of. It's actually ahrd to find people who can test it on Mango though, due to the low number of people with interop-unlocked HTC phones, so a custom ROM that supports TouchXplorer (same DLL needed for my backup app) might make a good test. The app isn't even beta quality yet - I'm still adding things to it, and the codebase is a bit of a mess - but it works for the features it does have, most of the time.

[Q] Any WP7 Device as wifistick for PC´s

So here is my request and pleed:
Please create anyone an app which is possible to change the WP7 Device into a wifistick,so that you can connect your pc through your Phone to your wifi,this would be absolutely great,and if it is not possible to create an app for me and all the guy´s who have requests for this missing feature because of time,or other reasons than impossibility then please tell me anyone of you how the code must work,which api´s and so on i´ll need so that i´ll be able to create such´n app by myself,because i´ve visualstudio and can do some programming
thx for any answer

What Phone do you have ? Is it unlocked ?

The app "Mango Webserver" (in dev & hacking sub-forum) can already kind-of do this, because you can uload files using your web browser, then download them later on another computer.
If you want to create an app that is dedicated to the purpose, the first questions would be how do you want the PC to see the phone (using a browser like Mango Webserver app, or using a dedicated program, or what) and do you want this to be a marketplace app, or is using unofficial APIs OK?

So i have an unlocked Omnia 7(fullyunlock + interop(it is really interopunlocked believe me,don´t ask)) ,the way i want to use it is like a wifistick/modem or so,if it is unofficial or not therefore doesn´t interest me,but i thought that it eventually would be able to get this feature for more devices,so that it would have some more attention as only for samsung devices
so thx again for any answer

Hmm sorry, I misinterpreted your request. You want to use the phone as a WiFi network interface for the computer. ("wifistick" doesn't mean anything to me; never heard the term before.)
I don't currently know of a way to do that. You can use your phone to connect the PC to the Internet (using wired tethering), but that just turns the phone into a cellular modem. To do what you're asking, you'd need to either bridge the WiFi and ethernet-over-USB connections, or you'd need to set up Internet connection sharing between the WiFi and USB (like the official "Internet sharing" feature, except that one is between the cellular radio and the WiFi).

Yeah thats what i mean,but i think it must be possible anyway,because for wm devices that was available and also for androidphones such a function is available,why shouldn´t it work with wp7 devices?

Oh, it's possible. You'd need to use native code and probably need to have more permissions than a normal app allows, though. Just because an OS *can* do something doesn't mean that the software to do it is available.
I already listed the two most reasonable approaches to doing it. I'm not sure if WP7 supports connection bridging, so the first might not be possible. The second certainly is, though.

[Q] How to unbrand Samsung Focus

I am not sure how to unbrand my ATT Samsung focus so it can be an open market device and can recieve updates as they come?

Not sure what you mean by open market device?, but i do have a xap that will allow you to unbrand it and also rebrand it. By unbranding it does not allow you to see more in the market if that what your thought may have been?
If you are looking for a way to get to diff device market app then go over to here
http://forum.xda-developers.com/showthread.php?t=1393265
Click to expand...
Click to collapse

Unbranding allows you to receive updates (you know, like the OP said... the things that come over Zune) as soon as they are available. Some mobile operators don't release the updates on time, so you might have to wait weeks or (on occasion) months.
It's somewhat dangerous, though - if your phone is a mixture of branded and unbraded ROM components (some from stock, some from updates), it's in an untested state and there may be problems. If you re-brand after installing the update, you may later get an MO-specific update to bring your phone back onto the official update path... or you might not.
Also, if you want to force updates, there's another method that may work better: sending update CABs rather than doing the updates through Zune.

Yes i can understand the part ( and can receive updates ) just didnt know what he meant by " open market device " thanks for the clarity of the OP

"Open market" is a term used to describe phones which are sold un-branded and not SIM-locked. They're relatively rare in the US, but are the rule, not the exception, in most of the world. Open market phones are not customized for their carrier, so they may lack certain useful carrier-specific features. However, they also lack carrier mandated modifictions that may lower the quality of the OS (for example, AT&T removing the 2G/3G toggle option from their stock ROMs).
According to the guys at the Microsoft store, the Lumia 800 is only being sold open-market in the US, for example.

Ahh, i see said the blind man! Learn a little some new everyday.

unbrand
according your question,that's easy to done...
you have two choices to update the new version of OS,change to the phone registry or reture to 7004 version when your phone is running 7720,then flash the custom rom from dft(dark forces team),and your phone can update to 8107 or higher version of WP7.5 easily.

Is there any way to re-interop? Focus S.

Hello,
In all my excitement over Tango, I neglected to read any of the warnings posted around the forums/web. I installed Tango via the cab sender method (neglected to make a backup) and everything still worked, or at least the homebrew apps I launched still did. Searching the forums, I found the Samsung firmware somewhere in the replies to the cab thread, and pushed it also. This was late at night and it wasn't until the next day I noticed I can't launch almost half of my homebrew apps. It's said restoring from a backup (don't have one) or flashing back to Mango is the only way to fix this. Is that true? Well ****. Because there is no ROMs (stock nor custom) for the Focus S..
What should I do?
Thanks in advance,
6-4.

64GUNSHIP said:
Hello,
In all my excitement over Tango, I neglected to read any of the warnings posted around the forums/web. I installed Tango via the cab sender method (neglected to make a backup) and everything still worked, or at least the homebrew apps I launched still did. Searching the forums, I found the Samsung firmware somewhere in the replies to the cab thread, and pushed it also. This was late at night and it wasn't until the next day I noticed I can't launch almost half of my homebrew apps. It's said restoring from a backup (don't have one) or flashing back to Mango is the only way to fix this. Is that true? Well ****. Because there is no ROMs (stock nor custom) for the Focus S..
What should I do?
Thanks in advance,
6-4.
Click to expand...
Click to collapse
Yeah... I want to say you're unfortunately screwed :-\.

To make matters worse, the Wireless manager no longer appears to work for configuring MMS when carrier unlocked. I guess I'll just go back my Quantum's for hacking and hard reset this device ..ill wait a while though.
Sent from my SGH-i937 using XDA Windows Phone 7 App

Do you have *any* homebrew apps that
A) you can still run
B) you marked as Trusted in WP7 Root Tools?
It sounds like what happened is that your phone reverted from interop-unlock to simple dev-unlock (you presumably have an AppHub account?). However, this does *not* revert root-unlock as applied by WP7 Root Tools. Root Tools itself requires ID_CAP_INTEROPSERIVCES, and as such can't be run without interop-unlock. However, the apps that it has marked as Trusted will continue to run with full permissions (root unlock).
So, here's what you do.
First, identify an app that you can run (i.e. that isn't interop) and that is marked as Trusted.
Second, take the GUID of that app, and use that GUID to replace the ProductId of the Tango-update-workaround app (which essentially just restores interop-unlock).
Third, remove homebrew apps from your phone (but not the target app, the trusted one you can still run) until you are able to deploy an app (usually, this means reduce to 9 homebrew apps).
Fourth, use a XAP deployer that supports updating, and do an update-install of the workaround app (upgrade, because it's using the GUID of the already-installed target).
Fifth, run the workaround app, and then re-install your normal apps.

I did as you instructed, however I still have the 10 sideload limit and am unable to deploy any interop services.By tango workaround app, you meant relockprevent, correct?
Is there something I may have missed?
Like I said, I installed the Samsung LE2 update for the Focus S which is basically the KK2 equivalent, so provxml will no longer work.
Also, I do not have an apphub account.

Bump. Anyone have any ideas? A friend put a support ticket in with Samsung internal support to see if they can get the ROM.

64GUNSHIP said:
Bump. Anyone have any ideas? A friend put a support ticket in with Samsung internal support to see if they can get the ROM.
Click to expand...
Click to collapse
Oh so it was that firmware update that just broke interop. Yeah I want to say at this point you are stuck. I doubt that Samsung will give the ROM since it isn't an issue that is preventing you from doing out of the box functionality.
Sent from my SGH-i917 using XDA Windows Phone 7 App

snickler said:
Oh so it was that firmware update that just broke interop. Yeah I want to say at this point you are stuck. I doubt that Samsung will give the ROM since it isn't an issue that is preventing you from doing out of the box functionality.
Sent from my SGH-i917 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
isnt the provxml method using diagnostic tools the reason for this no longer working, what i mean by that is if you were to install the older version of the diag tool would that not restore functionality, or has the lock down of that gone much deeper? if you are able to install XAPs then find an older OEM update version pre KK2/LE2, open it up and rip out the diagnostic tool XAP, remove any previous installed version then send over the XAP....
just a thought, it might not work, but essentially i think thats what happens unless of course there are other dlls or drivers that the tool needs that have also been updated....
course it would be great to find someone willing and able to help crack the bootloader

dazza9075 said:
isnt the provxml method using diagnostic tools the reason for this no longer working, what i mean by that is if you were to install the older version of the diag tool would that not restore functionality, or has the lock down of that gone much deeper? if you are able to install XAPs then find an older OEM update version pre KK2/LE2, open it up and rip out the diagnostic tool XAP, remove any previous installed version then send over the XAP....
just a thought, it might not work, but essentially i think thats what happens unless of course there are other dlls or drivers that the tool needs that have also been updated....
course it would be great to find someone willing and able to help crack the bootloader
Click to expand...
Click to collapse
Yeah I gave the suggestion to him in the Cab Sender thread to try and look on here for the Diag v 0109 or even 0210. That's the version that I have. Actually in the Cab Sender thread, I posted the cab file to the samsung firmware for Mango that should have that diagnostics version in the cab. You may be able to push that to your device

The old version was still installed after updating, it didn't work.

64GUNSHIP said:
The old version was still installed after updating, it didn't work.
Click to expand...
Click to collapse
Ok, that means that the firmware also pushed out new Dlls to prevent proxvml. You are stuck unfortunately :-\

Ive been asking around and doing some research and as of today your stuck, sorry!
I did some poking around on DFTs website as well and there is absolutely ZERO work being done on it, mostly because it seems like the focus S is an AT&T only phone, there just isnt a pressing needed to do anything, plus most folk dont have a focus S to work with.
i dont know what it would take to get some help or even guidance on getting the bootloader replaced but at the moment, until another method is found, thats all there is.
Tho This might be interesting to look in to but DONT DO IT!
did i read somewhere else you dont have a preupdated backup or was it that the backup didnt work?
snickler said:
Ok, that means that the firmware also pushed out new Dlls to prevent proxvml. You are stuck unfortunately :-\
Click to expand...
Click to collapse
There is a lot of changes in those updates, if we could insert our own certificate to allow us to build our own signed cabs we could probably work it out, but alas we can only add a cert in to a custom ROM then flash it...

Yes, unfortunately I bought the phone from a guy here on XDA in May, never had to update it (had been cab updated to 8107 before I got it), never made a backup before installing tango (it's a small update, what could it possibly **** up, right?) Anyway the Focus S was announced yesterday as being available online at some Australian website so maybe there will be ROMs available in the future. I still haven't heard back from internal Samsung support, but have also asked the user I purchased the phone from if he has any backups, which I would restore from and immediately reset again to ensure his privacy.
Honestly, I wouldn't mind losing interop-unlock until 7.8 comes around, or WP8 (whichever I can afford first), but MMS also can't be configured using the Wireless Manager anymore, and that's an absolutely vital feature for me. Although, the WM has been known to not work for a lot of people, even pre-tango, but it worked flawlessly OOB for me prior to updating.

64GUNSHIP said:
Yes, unfortunately I bought the phone from a guy here on XDA in May, never had to update it (had been cab updated to 8107 before I got it), never made a backup before installing tango (it's a small update, what could it possibly **** up, right?) Anyway the Focus S was announced yesterday as being available online at some Australian website so maybe there will be ROMs available in the future. I still haven't heard back from internal Samsung support, but have also asked the user I purchased the phone from if he has any backups, which I would restore from and immediately reset again to ensure his privacy.
Honestly, I wouldn't mind losing interop-unlock until 7.8 comes around, or WP8 (whichever I can afford first), but MMS also can't be configured using the Wireless Manager anymore, and that's an absolutely vital feature for me. Although, the WM has been known to not work for a lot of people, even pre-tango, but it worked flawlessly OOB for me prior to updating.
Click to expand...
Click to collapse
so you updated to the LE2 samsung update, was that via zune? (the last update it does in a row 3rd or 4th perhaps!) or did you cab send that as well?
if you went via zune then it does a backup as well, settings>update>restore

It was all done through the cab sender. There is no backup.

Just wanted to mention here... you know that CAB Sender is perfectly capable of making backups, right? It's one of the core operations the tool is capable of. Don't blame CAB Sender for you pressing S instead of B.
I just don't want people getting the impression that "through the cab sender" implies "there is no backup."

Fully aware, thank you.

?
Hello guys!
Got my device on the 8773 and did the samsung update...
Is there anyway to get my interop back ?
I have my backups (one the last 8773 without samsung update and the other is 7740 without anything =] )
Thanks a lot.

Restore your backup, do a little bit more reading on the subject of Tango with Interop Unlock, install the prevention app and mark it as trusted, and have at it. (Specifically, Tango will reset the "prevent relock" registry values, so you have to avoid the phone connecting to Microsoft until you have cleared them again).