Develop Bugs

WP7 Unlocking, Sideloading etc. Problems and Solutions

Now, I know no-one actually likes reading threads, and would prefer to just post a new question at the end (I'm guessing partly because the threads are so long, but that's because everyone is doing it) so I'm going to try and give solutions to as many of the issues with ChevronWP7, sideloading and anything else that's not quite working.
Note, none of this is to facilitate any kind of software pirating (we will notice if it gets discussed, and it's in the forum rules - and kinda immoral).
Firstly, Windows Vista (I think SP2) or Windows 7 is required, this won't work on XP without a few hacks/tweaks, and it's not worth me writing the whole process out, plus I don't have an XP machine to hand, so I can't try things.
The most common issues can be fixed with just installing the correct software.
You NEED to have the official WP7 Developer Tools installed, they're a free download from Microsoft, and if you're planning on doing development (which is after all part of the reason for wanting sideloading) you kind of need them.
There's a guide on how to install them (provided by Microsoft) here. You only need the basic toolset from here, but installing the October update won't cause any issues.
This should solve the following exception:
Code:
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SmartDevice.Connectivity, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
as well as a few other issues.
When running any of the tools, if you encounter issues, try either running the tool as an administrator or turn of UAC (for both, do a search if you've no idea what I'm on about), this may solve some issues with access rights etc.
Once you've got that installed, Chevron issues are in post #2, sideloading XAPs in #3.

ChevronWP7 Issues
With Chevron, most things are explained well in the opening post of this thread. Read it.
Chevron works by tricking your phone into thinking it's communicating with Microsoft servers, when it's actually just communicating with Chevron, this means certain web based activities may interfere (Skype for example).
The best way of finding out what's going on, is to use the following guide, it should work, if that fails, then post a question.
sushovande said:
Okay so here is *everything* I did to succeed in re-unlocking my Samsung Focus
1. Have Winphone developer tools installed
2. Connect Phone via USB
3. Wait till zune starts and sync completes
4. Verify that zune is not in a guest relationship
5. open a command prompt, type netstat -a to confirm that port 443 is not being used
6. open an admin command prompt, navigate to c:\windows\system32\drivers\etc\ then type notepad hosts and delete any references to windowsphone developer services
7. go to the settings on the phone and turn airplane mode on (so that the phone is forced to use internet via zune)
8. While the phone is still on the settings page, run Chevron with admin privileges
And it worked!
Click to expand...
Click to collapse
There's no way to know whether a device is unlocked or not until you come to sideloading, which is the point where it matters anyway. Nothing (visible) will change on the device, so don't bother looking for any changes.
WP7 devices occasionally phone home (as far as I know they only do so when connected with Zune) to check whether they should be unlocked or not. If not, they quietly re-lock themselves, and non-marketplace apps will say something along the lines of "This application has been revoked". You'll need to try unlocking again with Chevron and possibly reinstall the apps. There's not much that can be done other than legitimately unlocking your devices.
There's a sideload limit of 10 applications, though there's a version of Chevron that has this limit hacked out of it, I just can't remember where it is. For most legitimate uses, this limit should be fine (and is better than the student/DreamSpark limit of 3).

XAP Installation
A first port of call if Toms XAP Installer doesn't work is to use the official one. It does work.
If you've installed the Developer Tools linked to in the first post, you'll have it already, and should be able to sideload, if your device has been unlocked. If it hasn't you'll have issues, and you should take a look at post #2 in this thread.

[Q] Limitations of INTEROP-UNLOCK

I have used the INTEROP-UNLOCK and sorted the GRPS connection....
My question is what are the limitations of this unlock?
I have not been able to get MMS working even after reloading the network profile, I have a locked phone to 3UK network.
I believe that when a phone is carrier unlocked MMS does not function, isn't is the INTEROP-UNLOCK similar?
I cant use the official Samsung Network profile app in the market place as I am locked to 3UK, but if I carrier unlock the phone, will I be able to use this official app to reconfigure (as a new phone) the 3G settings and the MMS settings to work as a stock phone.
Also, for carrier unlocked phones, via a 3rd party when we get an unofficial update from Microsoft, does it re configure the settings to work with the official Samsung network app.
I have posted a couple of times to find info on one of the above items, and have been told to to look at the forums, I have spent a lot of time reviewing them and I dont think the above points have been answered concisely....
Your help would be greatly appreciated.

http://www.wpxap.com/thread-171460-1-1.html
here you can see

Even when the page was translated from simplified Chinese, the link didn't explain any of the questions raised above...

Search for Samsung Tools in this forum. Install it and run it. Checkmark the prevent device from relocking, unlock, and run adc checkmarks. Press ok, after it reboots it will fix your mms issue
Sent from my SGH-i917 using XDA Windows Phone 7 App

W99DEY said:
I have used the INTEROP-UNLOCK and sorted the GRPS connection....
My question is what are the limitations of this unlock?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1265321
A Quote from it... Dont forget to hit thanks !
Heathcliff74 said:
On WP7 there are already a lot of different unlocks:
Developer-uplock/ChevronWP7 unlock: This will allow you to side-load apps from your desktop to your phone. A legit developer-unlock costs $99 per year (this will also allow you to deploy your apps in the Marketplace). ChevronWP7 made an unlock tool, which allows you to dev-unlock your phone for free. This method only works on WP7 version 7.0.7004.0 and 7.0.7008.0. It does not work anymore since version 7.0.7355.0 (pre NoDo). But it is possible to unlock your phone on version 7.0.7008.0 and then use some tricks to upgrade your phone and keep the unlock. You can even upgrade to Mango RTM and still have the unlock. Look in this thead to get full instructions. Also the ChevronWP7 team will release an unlock-method that will only cost a few bucks and will apply an official dev-unlock on any version of WP7, but it won't allow you to release apps to the Marketplace.
Interop-unlock: On RTM and NoDo versions of WP7 it was possible to run apps with native code. These apps would use a COM-Interop-Bridge to transit between managed and native code. These apps need to be tagged with the Interop-capability called "ID_CAP_INTEROPSERVICES". These apps don't seem to run on Mango. Not even when you have a legit Developer Unlock. There are two reasons for that. The first reason is that most native libraries need some modifications to run on Mango. I found out how to do this and modified WP7 Root Tools so that it is compatible with Mango. The other reason is a deployment-restriction. That is the Interop-Lock that needs to be Unlocked. If you have a normal Dev-unlock on Mango and you try to deploy an app with that uses COM interop, the deployment will fail with error 0x81030120. contable and Marvin_S found out that the MaxUnsignedApp registry-value is responsible for the Interop-Lock. I did more research and I identified the code that checks this value. In fact, if you have the MaxUnsignedApp value set to 300 or higher, your interop will be unlocked. The value of MaxUnsignedApp is determined by the type of developer-unlock you have. A normal AppHub account will have it set to 10 and a student account will have it set to 3. So a value of 300 or higher is not a realistic value for a normal developer account. It is probably only set to this value for Microsoft employees and OEM developers. Until now, the only way to do an INTEROP-UNLOCK for MANGO meant that you have to downgrade to NoDo first, then prepare your device by loading provxml files to your device, upgrade to MANGO and then use OEM tools to execute the provxml files and do the necessary unlocks. But that is a lot of work and for some devices not even possible, because there are simply no ROM's available. But I have found an exploit that works on Samsung and HTC devices, which allows you to UNLOCK INTEROP your MANGO device. For it to work, it must already be developer-unlocked! Read this guide for instructions.
FullUnlock: This a type of unlock which allows you to run Native Executables. Normally you can only compile Silverlight apps, which will be run in a sandbox. The app is compiled as a DLL, which will be run in TaskHost.exe. I you would like to compile Test.exe, you won't be able to run it, because there is a policy-system and certificate-system that prevent you from running it. Cotulla already cooked a ROM with FullUnlock, but unfortunately this is not yet working as expected. I also did research on this together with fiinix. Thanks go out to him for working with me on that matter. We did not get it working back then, but I think I now have enough exploits to get this working. I will do some more testing on this later on. WP7 Root Tools does not need FullUnlock to be able to run.
Full Root Access: As stated previously, Silverlight apps and system executables have their own sandbox, which is defined by a Least Privilege based policy system. Even when you break into native code, you are still running in your sandbox. For example, you can try to copy a file in managed code. You will only have access in Isolated Store. If you use COM interop to call native code and you try to use the FileCopy() API, you can still only copy files in your Isolated Store. To break out of the sandbox, there are a couple of possible exploits. But they are still limited in their possibilities. To get unrestricted access to the API's and Resources on your device you will need to completely bypass the policies that the system has defined for your app. YukiXDA and I have in close contact with eachother for a period of time and we learned a lot from eachother. I found some of the exploits, thanks to him! YukiXDA unfortunately has left the community. A very big thanks to YukiXDA for working with me on this matter. Before he left he cooked a ROM for HTC HD2 which has Full Root Access cooked into it. The way he did it was to effectively shut down the policy-sytem. Although this opens up a lot of possibilities for homebrew, this is also kind of risky, because the system is also open to malware. And this technique only works on devices which have an unlocked bootloader (currently HTC HD2 and most HTC WP7 devices have unlocked bootloaders). I developed another type of Full Root Access. I can enable Full Root Access for the entire device (differt than what YukiXDA did, but effectively the same). But I can also enable/disable this per app. So the user can decide which app is trusted enough to get Full Root Access. Other apps will still run in their predefined sandbox. I am currently developing a new version of WP7 Root Tools which will support Full Root Access. To do this I will apply Full Root Access for WP7 Root Tools first. A user can use WP7 Root Tools to enable Full Root Access for another app. So if a developer wants to create an app that needs Full Root Access (for example some type of backup-app), the user of the app must use a ROM which has Full Root Access cooked into it, or the user must run WP7 Root Tools to allow Full Root Access for the app. There are two disadvantages. WP7 Root Tools must first install Full Root Access for itself. Obviously WP7 Root Tools does not have Full Root Access at that moment yet. So there are other exploits necessary to apply this. Currently I have exploits for this, but they use some device-specific features. I have exploits for Samsung, HTC and LG. Other brands, or possibly a device-independent exploit, may follow later. This means that WP7 Root Tools only works on these devices, and with that also the apps that need Full Root Access will only work on these devices. The other disadvantage is that, with the current state of Interop-unlocking, all users of WP7 Root Tools, and with that also all users of the apps that need Full Root Access, will need to be on dev-unlocked-NoDo first, in order to apply an Interop-Unlock for Mango. Because WP7 Root Tools and all apps that use Full Root Access need Interop Unlock. When I have the version of WP7 Root Tools with Full Root Access finished I will release an SDK, which will make access to the system a lot easier. The SDK will consist of a native library and a managed wrapper library. Developers will be able to access the Registry and Filesystem using only managed code and the libraries from the SDK. The app will of course need to be unlocked, using WP7 Root Tools on the device. But using the SDK is mandatory. You can also write your own native code. I will write a guide on how to do that later on. An app that has Full Root Access (provided by ROM or by WP7 Root Tools does not need any device-specific libraries. All API's can be used. For API's that are not in the SDK libraries you need to write your own COM wrapper.
Click to expand...
Click to collapse

Hi W99DEY
I had the same problem as you - I am on the three uk network, with a samsung omnia 7, updated to mango, interop unlocked, reset mms/internet settings and the mms does not work.
I spent a while trying to figure this out, but I found a solution as to how to get mms working after interop unlock.
Here's how you do it:
1. Revert to your last back up of your phone - this needs to be pre interop unlock and your mms should be working at this point. Do this by connecting to zune, going to update and clicking backup.
2. Install mango updates.
3. Once zune says you can unplug your phone after the updates, unplug it and use heathcliffs method of interop unlock: http://forum.xda-developers.com/showthread.php?t=1271963
But stop at stage 10 - don't try and repair your mms yet.
4. Deploy any other provxml you may want. May I suggest this one, to enable tethering:
http://forum.xda-developers.com/showthread.php?t=1238519
Don't try to repair the mms yet.
5. ***This is the important bit*** Currently your mms won't work, and there is only one method which will get it to work:
Run the Diagnosis app and dial this to enable auto configure sim setting: *#94765#
It will ask you to restart the device. Confirm that.
Other methods like - setting apn, using samsung tools, etc. do not work so don't try them.
6. Plug your phone back into zune, it should want to update again (mine did) Saying it needed to install Samsung updates. Install them.
7. You're done and your mms should now work - make sure you're not connected to the wifi when trying to send a mms as it may not work.
------
***Important*** After you've applied the fix and got the mms to work do not run any more provxml files as that will screw your settings again, and this method only works once for some reason.
Also don't run any other methods of fixing mms settings like using samsung tools etc. as this will not work, and if you try these before using the diagnosis method, then the diagnosis method will not work. And the diagnosis method will only work once.
If anyone has any ideas as to how to make this fix work more than once for 3uk samsung omnia 7's please let me know.
If this was helpful please say thanks

Cheers Parsl for the response.... More or less did what you did, think I tried Samsung Tools 1st.... ;-)

Yeah, I used Samsung tools and that didn't work. I found the only thing that worked was the diagnosis method. But only once - as the first time round I then applied the tethering provxml and then the diagnosis method didn't work a second time, so rebooted and then did it all in the order I mentioned.
Have you got your mms working now?
Sent from my OMNIA7 using XDA Windows Phone 7 App

[V50030A] Root with Lollipop installed

Hi,
I installed V50030A yesterday from Korean version, which is great. Now I need to root (to be able to use dual window with whatever app).
Anyone ever succeeded ?
Thanks.
Dripple_

Have succeeded in doing so here..
Use iRoot to root the tablet.. this will install Kingroot, a couple of chinese apps and a service..
Download iRoot for Windows PC here ::
iRoot - English Version (not tested)
iRoot - Chinese Version (tested and works) Your browser may block the download as google has stated this as untrustworthy.. bypass it.
After install make sure you have the most recent LG drivers for the tablet installed. (if you have installed the kdz i'll presume you already have done so)
make sure 'USB Debugging' in the developer options is active and that 'Unknown Sources' is enabled in Security.
Connect tablet to pc... Start iRoot/vRoot.. wait for it to connect to your tablet. Hit the green button to start root procedure.. here it will install a couple of apps and a service (these you will want to delete later) along with Kingroot and a rather bad version of busybox.
Do not touch the tablet and let it go through the whole procedure and reboot.. If it fails first time round, just repeat the whole thing again.
Hopefully you should have root.
Now this is important... You need to replace Kingroot with something that aint a piece of ****.. I suggest Supersu. For me this did not work straight off and it kept failing to update the binary.
What I did in the end was download Super-Sume. This is designed to aid installation and properly removes Kingroot while installing the most recent Supersu free addition.
Hopefully now you are rooted with Supersu.
install busybox from the play store so it replaces the bogus version that came with iRoot and you should be ready to go.
Delete remaining chinese apps and service that appeared and you free to go.
if you're wanting to install TWRP follow this thread by revi_buz ::
http://forum.xda-developers.com/lg-g-pad-83/help/v500-how-to-install-twrp-stock-lp-t3165846

Help rooting a BLU Dash M

I need some assistance trying to find a method to root my Dash M (which appears to be extremely rare to find a rooting method for).
I already tried framaroot (tool I used to root my tablet before) and Kingroot and such, but none were able to do it (and all google searches led to videos on rooting a BLU Dash 5.0 or another device from the Dash range, which isn't what I needed).
The Dash M is running Android 5.1 and custom build BLU_D030U_V16_GENERIC 28-01-2016 15:41
If anyone could help it'd be very much appreciated c:

Unlock OEM in developer mode and try it whit Kingroot

AnarchyPhoenix746 said:
I need some assistance trying to find a method to root my Dash M (which appears to be extremely rare to find a rooting method for).
I already tried framaroot (tool I used to root my tablet before) and Kingroot and such, but none were able to do it (and all google searches led to videos on rooting a BLU Dash 5.0 or another device from the Dash range, which isn't what I needed).
The Dash M is running Android 5.1 and custom build BLU_D030U_V16_GENERIC 28-01-2016 15:41
If anyone could help it'd be very much appreciated c:
Click to expand...
Click to collapse
I have a Blu Advance 5.0, from the same exact family. In May, they had an OTA sent out to it to update the security. And little did I know, that meant no more root. Before the OTA to V06, I was on V04, and was able to root with Kingroot in less than a minute, perfectly. After the update, nothing good came of it.
For the past months I've tried hundreds of things to flash custom roms and recoveries (which I figured it out eventually) and then it crashed, due to a "damaged OTA". This meant that it couldn't update because I was rooted.
So here's the solution... If there's any older versions of your model or chipset (AKA Mediatek D030UX, D030U {MT6580}), download that firmware to your computer desktop as a (.zip) file. Then download the SP Flash Tool (Smart phone flash tool) from their website, and plug your phone into your computer via Media Transfer (MTK).
If you already have developer's options enabled, skip this.
- Go into your settings, go all the way down to "About Device", and find where it says "Build Number" (which will most likely have the phone brand in the file name). Tap on that about 8 times until it give a toast notification saying "Developer's Mode Enabled".
After you get that done, go back into your regular setting and now there should be a box above your "About Device" button that says "Developer Options". Tap that, then turn them on (press OK/YES if a prompt pops up) and then select the following options ,if available.
-OEM Unlock
-USB Debugging
Now plug your phone into a computer and install the drivers for your phone (it should do it automatically) and launch the SP Flash Tool that you had downloaded (extract to desktop before you launch, or it will show "error"). Now open the SP Flash tool and click on the "Scatter Loading" button. Navigate to your desktop, and find the firmware folder you downloaded. Click on that, then click on "Firmware", and it should bring up a .TXT file (Scatter file) with the desired firmware version you want. Click on it and press open.
A chart will appear in the space below with all the things the firmware has built in. All of them should be checked. Take out your battery now (from your phone) and plug the phone in without the battery. Wait for the model on the left to name your device, and click on the drop down list above the chart, it should give 3 options. Firmware Upgrade, Download only, and Format All + Download. Press Format All + Download. The bar at the bottom will turn a few colors, depending on what it's doing.
Now you're done! It's flashed. From that version, try to figure out a way of rooting it.
WARNING: Flashing erases all data on device, please backup to an external storage (SD CARD), before attempting this, in case you brick your device.
Sent from my RCT6873W42M using XDA Labs
---------- Post added at 03:04 AM ---------- Previous post was at 02:56 AM ----------
TechTeen17 said:
I have a Blu Advance 5.0, from the same exact family. In May, they had an OTA sent out to it to update the security. And little did I know, that meant no more root. Before the OTA to V06, I was on V04, and was able to root with Kingroot in less than a minute, perfectly. After the update, nothing good came of it.
For the past months I've tried hundreds of things to flash custom roms and recoveries (which I figured it out eventually) and then it crashed, due to a "damaged OTA". This meant that it couldn't update because I was rooted.
So here's the solution... If there's any older versions of your model or chipset (AKA Mediatek D030UX, D030U {MT6580}), download that firmware to your computer desktop as a (.zip) file. Then download the SP Flash Tool (Smart phone flash tool) from their website, and plug your phone into your computer via Media Transfer (MTK).
If you already have developer's options enabled, skip this.
- Go into your settings, go all the way down to "About Device", and find where it says "Build Number" (which will most likely have the phone brand in the file name). Tap on that about 8 times until it give a toast notification saying "Developer's Mode Enabled".
After you get that done, go back into your regular setting and now there should be a box above your "About Device" button that says "Developer Options". Tap that, then turn them on (press OK/YES if a prompt pops up) and then select the following options ,if available.
-OEM Unlock
-USB Debugging
Now plug your phone into a computer and install the drivers for your phone (it should do it automatically) and launch the SP Flash Tool that you had downloaded (extract to desktop before you launch, or it will show "error"). Now open the SP Flash tool and click on the "Scatter Loading" button. Navigate to your desktop, and find the firmware folder you downloaded. Click on that, then click on "Firmware", and it should bring up a .TXT file (Scatter file) with the desired firmware version you want. Click on it and press open.
A chart will appear in the space below with all the things the firmware has built in. All of them should be checked. Take out your battery now (from your phone) and plug the phone in without the battery. Wait for the model on the left to name your device, and click on the drop down list above the chart, it should give 3 options. Firmware Upgrade, Download only, and Format All + Download. Press Format All + Download. The bar at the bottom will turn a few colors, depending on what it's doing.
Now you're done! It's flashed. From that version, try to figure out a way of rooting it.
WARNING: Flashing erases all data on device, please backup to an external storage (SD CARD), before attempting this, in case you brick your device.
Click to expand...
Click to collapse
You can download the tool at the bottom of this thread.
Sent from my RCT6873W42M using XDA Labs

Root BLU Dash M
AnarchyPhoenix746 said:
I need some assistance trying to find a method to root my Dash M (which appears to be extremely rare to find a rooting method for).
I already tried framaroot (tool I used to root my tablet before) and Kingroot and such, but none were able to do it (and all google searches led to videos on rooting a BLU Dash 5.0 or another device from the Dash range, which isn't what I needed).
The Dash M is running Android 5.1 and custom build BLU_D030U_V16_GENERIC 28-01-2016 15:41
If anyone could help it'd be very much appreciated c:
Click to expand...
Click to collapse
i know this is an old thread but.... i rooted mine (Dash M) with KingoRoot (look it up on Google)... i tried lots of stuff with no results, everything failed (i've already tried to root with KR in windows) but the only thing that worked was rooting with the android app in KR page... i felt really stupid after trying everything with no results when i've been using KR for other "hard phones".... either way, the only downside is that their SU manager displays all the time ads no matter where in the phone you are... but you can freeze the app to fix this and unfreeze it when you need to assign permissions....
BTW: its KingoRoot not kingroot (just in case)

Alcatel One Touch Fierce 2 One click root and fix for su is occupied

After dealing with KingRoot, Kingo Root and iRoot with all of their add-on apps and the awesome adware they install I was fed up, plus the fact that there was no "really easy" way to get rid of their files and keep root to install SuperSu or have the problem of "su being occupied"
So I decide to do some searching for something less complicated and found Dr. Fone.
This is a true one click root that installs the real SuperSu, Busy Box binaries and gives the King the boot in less than ten minutes.
I confirm this method works on my Alcatel One Touch Fierce 2 7040N (Metro PCS) and I'm sure it may work on many other devices.
I didn't have to delete or freeze any other root apps before re-rooting. You can do the cleanup with any descent root file explorer after Dr. Fone is done. The process took less than ten minutes for the root.
Hopefully this will help somebody out.
Another word of advice is don't use iRoot because it will install relentless adware and garbage apps on your phone and render it useless.
Connect your phone to the computer using a USB cable. If your Android version is 4.2.2 or above, you will get a pop-up message on your phone.
click on "OK" to allow USB debugging. Then dr.fone will automatically recognize your device and install the proper drivers and adb.
After your phone is connected just follow the prompts. The detecting process will take a few minutes depending on different phone models.
You can also unroot with this tool.