Related
This is my first attempt at creating something for users on xda, so be gentle .
Eternityproject has released a fine script for rooting our Motorola RAZR phones on the 4.0.4 update. As a windows-user that used to use batch scripts for everything I could not help but want some more output than just the [rebooting] echo's that the script print on the screen. As a bonus I thought it would be nice to see how long the script will take before my phone is rooted. I have made these wishes into an application, and pedrotorresfilho kindly allowed me to use their script in my application.
So what does it do?
It roots your Motorola RAZR and shows you what the script originally did. It also calculates how long your phone takes to reboot, and shows you how much time you have to get a nice cup of [insert drink here]. Or soda if you prefer that. In theory it is possible to root multiple phones at the same time, which saves time if you have to root 10 RAZRs at once (LOL... as if).
How does one use it?
- Install the program using Microsoft's Awesome ClickOnce distibution system
- Install the Motorola Drivers (Download MotoHelper from here)
- Enable 'Unknown Sources' (on your phone: go to settings, go to security, tick the box next to 'Unknown Sources') (needed to install supersu.apk)
- Enable 'USB Debugging' (on your phone: go to settings, go to developer options, tick the box next to USB Debugging) (needed to communicate with your phone over USB)
- When connecting your phone, please set the USB Mode to 'Media Sync - MTP', to be sure that mounting points won't interfere with the rooting process.
When the application is opened all the connected Android devices will be selected. This means that as soon as you press the 'Root' button, they will be rooted.
In principle the application does nothing more or less than the script. You don't have to have extensive knowledge of adb or android internals, it's just an app that shows the connected devices and a root button . If you are already rooted, it's easy to unroot using SuperSU.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download links:
Open ClickOnce Application (works only if you have .NET 4.0 installed!)
Download page (use this if the above link does not work/you do not have .NET 4.0)
You can update by opening the application. If there is an update, you will be prompted to download the latest version.
Required:
Windows (with .NET Framework 4.0 Client Profile installed)
Motorola RAZR running ICS (other phones might work, but you will get a warning)
I ask all of you kindly NOT to mirror or reshare the application without my permission. Please share the ClickOnce Application link. Is assures that you are running the latest version!
Credits:
Eternityproject (pedrotorresfilho & kholk) - for writing the script
miloj - For finding the exploit binary to root the phone
Dan Wager - For creating AndroidLib, a .NET wrapper for ADB on Windows
Chainfire - For creating and providing SuperSu and his su binary - http://forum.xda-developers.com/showthread.php?t=1538053
Changelog:
1.0.0.6:
Added more strings to the logging output
Fixed the blocking of the root button if there are no devices selected
Added a splash screen to indicate that the application is actually loading
Changed the location where the splash as well as the credits/welcome screen appear
1.0.0.5:
added credits for Chainfires SuperSU and su
Removed the message that rooting was not successful
Added a few more messages about the script itself (in the script output)
Updated SuperSU and binary to 0.94 (su binary still says it needs to be updated )
1.0.0.4:
The application now properly disposes of the AndroidLib instance, disabled the CheckedItem event on the DeviceList because it was a tad buggy. This won't harm anyone.
1.0.0.3:
Enabled Microsoft ClickOnce Update deployment. If I fix a bug, you are able to update to a less buggy version
DJFliX said:
This is my first attempt at creating something for users on xda, so be gentle .
Credits:
Eternityproject (pedrotorresfilho & kholk) - for writing the script
minoj - For finding/creating the exploit binary to root the phone (please correct me if this is not correct)
Dan Wager - For creating AndroidLib, a .NET wrapper for ADB on Windows
Click to expand...
Click to collapse
+1 congratulations for this work
thanks
My Razr is already rooted, but I can test.
nespresso33 said:
My Razr is already rooted, but I can test.
Click to expand...
Click to collapse
I have sent you a dm .
Can you try with this root method. It's simpler.
http://dev.crackflasher.com/ROOT_TOOLS/razrs_edge_windows.zip
For guys already rooted that wanna test it, first unroot your phone:
Run SuperSU app and press 'full unroot'. If you have superuser app also installed remove it first.
Cheers
whirleyes said:
Can you try with this root method. It's simpler.
http://dev.crackflasher.com/ROOT_TOOLS/razrs_edge_windows.zip
Click to expand...
Click to collapse
Hmm... I will have a look at this. What are your reasons for using this except that it's simple? It's just a matter of preference, right?
pedrotorresfilho said:
For guys already rooted that wanna test it, first unroot your phone:
Run SuperSU app and press 'full unroot'. If you have superuser app also installed remove it first.
Cheers
Click to expand...
Click to collapse
Thanks man! Much appreciated!
Well, I tested the 2 versions ( I got a notification to update your tool ).
It is working great but the installer is strange, ( I had all requirements but for people which don't, it's not great ).
SuperSu and binary are not latest version. And I get at the end a message who say " the phone does not seem to have root" but I had root
nespresso33 said:
Well, I tested the 2 versions ( I got a notification to update your tool ).
It is working great but the installer is strange, ( I had all requirements but for people which don't, it's not great ).
SuperSu and binary are not latest version. And I get at the end a message who say " the phone does not seem to have root" but I had root
Click to expand...
Click to collapse
Yeah, the installer should be extra user friendly. I should probably just advice users to use the .application link. But the link will only work if .NET client profile is already installed. I'll adjust the message about root, It seems that the library that I use does not query root status from the phone, but rather from it's cache. Maybe I have to update the phone data before querying for root. Thanks for your feedback!
Edit: I am now uploading version 1.0.0.5, I added credits for Chainfires SuperSU, removed the message about the rooting. Too bad my connection is bad (3G in the mountains in La Palma) so bear with me while the updated version is uploaded. Should be up within about 10 minutes, users that already have the application installed will asked to update to the latest version.
nespresso33 said:
Well, I tested the 2 versions ( I got a notification to update your tool ).
It is working great but the installer is strange, ( I had all requirements but for people which don't, it's not great ).
SuperSu and binary are not latest version. And I get at the end a message who say " the phone does not seem to have root" but I had root
Click to expand...
Click to collapse
1. Installed and executed (had to confirm the download since google chrome didn't allow setup.exe files to be directly donwloaded)
2. Upon start it updated.
3. First run the app didn't recognized my connected Razr after changing USB to Media Device - MTP and enable USB debug.
3. Closed and reopened the app and it recognized and root went fine.
Notes: Application said to 'Refresh' when ADB has being enable, but theresn't a Refresh button.
Really nice!
pedrotorresfilho said:
1. Installed and executed (had to confirm the download since google chrome didn't allow setup.exe files to be directly donwloaded)
2. Upon start it updated.
3. First run the app didn't recognized my connected Razr after changing USB to Media Device - MTP and enable USB debug.
3. Closed and reopened the app and it recognized and root went fine.
Notes: Application said to 'Refresh' when ADB has being enable, but theresn't a Refresh button.
Really nice!
Click to expand...
Click to collapse
The refresh button is the button next to root . I'll put a tooltip on that button. Glad to hear all is fine. I'm uploading 1.0.0.5 to polish out the small annoyances and update SuperSU. Thank you so much for testing .
Edit: 1.0.0.5 is out . The download link is now public. Please leave suggestions and improvements in this topic or send me a DM. Thanks!
Hi guys, I wanted to try this database system, so I'm expanding upon this thread: http://forum.xda-developers.com/showthread.php?t=2272066
Introduction
CASUAL will guide you through the process. Put your device into “Developer Mode>USB Debugging”. Click the do it button. If you experience a problem, PLEASE USE THE PASTEBIN button to post a log. Just press Ctrl+L then Pastebin and fill out the information.
Overview
You are expected to be STOCK.... Stock anything, but stock. If you are not stock and have a custom recovery, this will cause you to only be able to flash back to stock using Odin or Heimdall. Be stock. You will need to download and execute the CASUAL application below. Then click the Do It! button. You need Java. Do you have Java?. The exploit was developed by Elite Recognized Developer Ralekdev and packaged by AdamOutler.
note: if it fails, try turning everything off and back on, then run it again before posting for help.
Windows 32/64 Users: CASUAL will put your device into Download Mode. It will automatically flash everything. If drivers are required, jrloper's CADI (CASUAL Automated Driver installer) will handle it. Make sure you're connected to the internet.
Linux 32/64/raspberry pi Users There may be a permission escalation in order to install heimdall, either way sit back and relax. CASUAL automates the entire process.
Please run the following in a terminal first:
Code:
sudo apt-get install openjdk-7-jdk dpkg
Mac Users: Mac works easier than any other system at the time of this systems. Please report problems.
Download
CASUALnightly No You Verizon! Always use the highest revision with the latest date. To run CASUAL you need Java. Do you have Java?
For nightly builds click here: http://goo.im/devs/AdamOutler/VZWGalaxyNote2
Help and Troubleshooting
Are you having a problem? First check this post out for remedial troubleshooting. . If that doesn't fix it, then press CTRL+L, press the Pastebin button, come back here and press CTRL+V to paste your log. Don't hit the donate button, that doesn't fix it. Donate only if you feel it's worth donating to. Use CTRL+L and then hit Pastebin and paste the log here if you need help.
Jailbreak video for Windows users only!
This video desmonstrates CASUAL used with Odin to flash the Galaxy Note 2 firmware. Thanks to DroidModderX. While the video uses an old version the procedure is mostly the same.
Jailbreak video for LINUX only!
This video demonstrates the one-click CASUAL Linux Unlock method... at 2AM.. so don't expect me to be cheerful. While the video uses an old version, the procedure is mostly the same.
image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About CASUAL
CASUAL stands for Cross-platform ADB Scripting, Univeral Android Loader. CASUAL jar files are a wrapper for the CASUAL scripting language. CASUAL allows rapid and accurate deployment of hacks and exploits. At any time, if a serious problem is detected with any script, the kill-switch will be flipped and you will be brought to a support page (most likely here) so you can download the latest version. Otherwise for minor corrections, new CASUAL scripts can be deployed remotely.
Updates
CASUAL provides updates WAAAAY quicker than Verizon. As soon as I push an update to the Subversion repo it appears automatically in EVERY casual. See below for the change log.
31July13: initial release
XDA:DevDB Information
CASUAL- NO You Verizon, a Tool/Utility for the Verizon Samsung Galaxy Note II
Contributors
AdamOutler, jrloper, loglud
Version Information
Status: Testing
Current Beta Version: No You Veriz
Beta Release Date: 2013-07-31
Created 2013-07-31
Last Updated 2013-08-02
Very nice work
MY DIRTY LIL NOTE 2
couldnt get the latest nightly to fully load. recog device connection but the do it wouldnt work because the top of the app stayed on loading... please wait.
edit: diff build shows the top, but says disconnected on the bottom. fml
all the videos say to use windows 7. can it work with vista?
master0fursinz said:
all the videos say to use windows 7. can it work with vista?
Click to expand...
Click to collapse
yeah, it should work with Vista. @jrloper could tell you more if there are driver issues.
idkwhothatis123 said:
couldnt get the latest nightly to fully load. recog device connection but the do it wouldnt work because the top of the app stayed on loading... please wait.
edit: diff build shows the top, but says disconnected on the bottom. fml
Click to expand...
Click to collapse
I'm also having this problem. Any help Adam?
Edit: This is what you're looking for http://forum.xda-developers.com/showthread.php?t=2272066
Hi,
I'm currently running Windows 8.1 64 bit and my phone is the Samsung Galaxy Note II android version 4.1.2 stock, model SCH-i605, and baseband version i605vramc3. After downloaded the latest nightly build, the .jar file opened and gave the following error in the application:
There was a problem while excuting the command.
C:\Users\Zack\AppData\Local\Temp\CASUALZack-2013-12-26-17.09.35\adbexe devices
Then it repeated this same error every second or so infinitely until the application was closed. It did this whether the phone was connected, disconnected, in USB debugging mode, in download mode, etc. I have tried everything and I continually get this same error with the "Do It' button greyed out and disabled.
Next I downloaded the previous two builds, and I found that the December 13 build did not get this error and actually found my phone. However, after I clicked "Do It" and confirmed the warning, It rebooted my phone into download mode like it is supposed to. My phone then went into download mode like usual. However, the CASUAL program then said:
looking for download mode devices..........................................................
And kept on looking without ever finding my phone, and every minute or so it came up with a prompt asking why it can't find my device. I also found that my phone would not exit this download mode without doing a battery pull.
Next I retried the entire process with both builds using (a) 3 different USB cords, (b) 3 different computers running windows 8.0 and 7, and (c)every possible USB port on each computer. These options all gave the same exact results.
I have tried everything I can think of but it is not working! Has anyone encountered this problem before or do you have any proposed solutions?
Thanks so much!
Zack
Still can't figure it out.
http://pastebin.com/W3W1HwJi
I keep getting a libusb error -12 at the start and then it ends up failing.
Really need help here. Verizon was trying to force update me and I had to turn it off and go back to my old phone till I can get this done.
Thank you Adam!!
BrickeD?
Hi guys.
I am certain I followed all instructions to the letter, but I have ended up rendering my Note 2 pretty much useless. CAUSAL informed that the device would be started in android but then the next thing my phone displayed was:
"System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
Can I restore my device to the previous state?
thanks
Tried the second time around with CASUAL R570 and got error.
http://pastebin.com/Gpss6vtZ
UPDATE: Gave up hopes (for now) of rooting SCH-i605 running KitKat. Flashed stock rom and revived the device.
Spy26 said:
Tried the second time around with CASUAL R570 and got error.
http://pastebin.com/Gpss6vtZ
UPDATE: Gave up hopes (for now) of rooting SCH-i605 running KitKat. Flashed stock rom and revived the device.
Click to expand...
Click to collapse
There isn't a root method for ND7 4.4.2. for the i605. Also, the bootloader hasn't been able to be unlocked since MJ9 4.3.
mirror
Hosed my phone... infinite bootloop at sammy logo, couldn't get into recovery had to odin a stock image and start over... Had one hell of a time tracking down the casual jar file.
As of this moment the download link in this thread is bad.
the download link in THIS thread, now points to DevHost but the files are not the ~29MB jar file you expect. It is now a 3.5MB exe file that appears to be "shady as hell". All the other download decoy buttons at Dev-host take you to fake java update downloads and other seriously shady looking corners of the interweb.
Additionally goo.im is on holiday...
As such I have posted this temporary Mirror of the .jar file I had in my archives:
http://tweakedrom.com/Other_Files/Note_2.php
(The jar file MD5 appears to be the same as one the developer posted to Dev-Host.)
Outler, if you want me to take this mirror down just let me know.
Cannot find the download to casual sch-i605. All download links I can find lead to nowhere.
mjmplus said:
Cannot find the download to casual sch-i605. All download links I can find lead to nowhere.
Click to expand...
Click to collapse
Well you could go to his very own YouTube video and use the links there
TD Fuzzer
This is a simple Xposed module designed to help those that utilize Nitrodesk's Touchdown to connect to their Exchange Activesync systems. Some EAS implementations prohibit certain device types/models from connecting, or if you'd rather present an alternate device when provisioning, this module can help with that. Keep in mind, if your IT staff/Info Security Office discover that you're circumventing their security controls and/or policies, I can't be held accountable if you get reprimanded and/or fired. This module won't circumvent specific policy requirements, such as device or sdcard encryption, strong password requirements, or disabled feature sets (disable IR, disable BT, etc). All it does is replace device-specific information that is collected during device provisioning, and also during each Activesync session (User-Agent header).
A picture is worth a thousand words, or so the saying goes:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The device on the top is my HTC One (m7) running Touchdown 8.4.00082 on KK 4.4.2, and the one beneath it is an actual iPhone 5s. The only discernible difference is the Device ID (which can't easily be changed in TD without breaking stuff).
This module should work on most devices running most ROMs. It only hooks the Touchdown package, and has been tested on TD 8.1.x, 8.4.x, and the latest 8.5.00086 against Exchange 2010 SP1 (Activesync v14.1) and Office 365 (Exchange 2013).
Install/Configuration
Install Xposed Framework
Activate Xposed app_process
Install this module and enable in Xposed Installer
Open TD Fuzzer settings and configure options
Reboot or soft-reset
Open Touchdown and provision device (or if already provisioned, go to TD Settings, Connection, ActiveSync button, Refresh ActiveSync Settings)
Source
You can find it on my github
Alternate Install
Also available in the xposed repo
@cities516 can you add to your module index?
Until I get around to adding some device presets into the module, here are some examples straight out of OWA:
iPhone 4S
Phone friendly name: Black iPhone 4S
Device Model: iPhone4C1
Phone OS: iOS 7.0.4 11B554a
Device Operating System Language: en
User agent: Apple-iPhone4C1/1102.55400001
SAMSUNG SGH-I747 (AT&T GS3)
Phone friendly name: d2uc
Device Model: SAMSUNG-SGH-I747
Phone OS: Android
Device Operating System Language: English
User agent: SAMSUNG-SGH-I747/101.403
SAMSUNG SGH-I317 (AT&T GN2)
Phone friendly name: t0lteatt
Device Model: SAMSUNG-SGH-I317
Phone OS: Android
Device Operating System Language: English
User agent: SAMSUNG-SGH-I317/100.40102
Great Work!
I've been search for a solution for this for ages and must I say that your xposed module is by far the only and most effective solution. Big congrats and very much obliged, man.
Because without this, although Touchdown can spoof a device name, the OS, protocols during the Activesync provisioning process will still be "Android 4.4.x" and "Touchdown x.x.x". So from the admin's side, it is still able to identify the spoofing by looking at the OWA mobile log.
Three questions:
1. How does it work? Modifying provisioning communication packets between Touchdown and ActiveSync server? I'm asking this because I want to know if future versions of Touchdown can be supported.
2. Will you consider supporting Android 5.0?
3. Will you consider supporting AOSP email apps, (preferably the apks with Exchange Security byPass working for 4.4.4 and 5.0)
Again, many thanks to you for the great work!:laugh:
XDAAdvocate said:
1. How does it work? Modifying provisioning communication packets between Touchdown and ActiveSync server? I'm asking this because I want to know if future versions of Touchdown can be supported.
Click to expand...
Click to collapse
I've replaced the writeDeviceInfo() method, which builds the provisioning XML object (com.nitrodesk.wbxml.WBXMLSerializer object, to be precise). This should be compatible with any version of TD; it's more specific to the Activesync protocol version (14.1 in this case). If MS changes how devices send provisioning data, then it would have to be updated. Also, there's information that's passed to EAS in the User-Agent header, which this module replaces.
2. Will you consider supporting Android 5.0?
Click to expand...
Click to collapse
Sure, once I have a device running Android L and the Xposed Framework.
3. Will you consider supporting AOSP email apps, (preferably the apks with Exchange Security byPass working for 4.4.4 and 5.0)
Click to expand...
Click to collapse
I've run across at least one xposed module out there that bypasses the AOSP email security restrictions for EAS. Since I don't normally run AOSP roms, it's much harder for me to do any sort of debugging/dev work.
agentdr8 said:
......
I've run across at least one xposed module out there that bypasses the AOSP email security restrictions for EAS. Since I don't normally run AOSP roms, it's much harder for me to do any sort of debugging/dev work.
Click to expand...
Click to collapse
Can you tell me where to find the modules to bypass these security restrictions for EAS. There are indeed some modules to bypass the mandatory PIN for example. But no module to bypass and change the device provisioning data.
This is what I needed thanks will try and report
yooidje said:
Can you tell me where to find the modules to bypass these security restrictions for EAS. There are indeed some modules to bypass the mandatory PIN for example. But no module to bypass and change the device provisioning data.
Click to expand...
Click to collapse
You're right; I don't think any of the ones I've seen can modify the device provisioning data, only bypass the PIN/lockscreen restrictions.
agentdr8 said:
You're right; I don't think any of the ones I've seen can modify the device provisioning data, only bypass the PIN/lockscreen restrictions.
Click to expand...
Click to collapse
Is there any possibility that you can also support the AOSP email apps, perhaps?
**please :angel:
yooidje said:
Is there any possibility that you can also support the AOSP email apps, perhaps?
**please :angel:
Click to expand...
Click to collapse
If I have some free time I'll see what I can do on my TF700 running CM11.
agentdr8 said:
If I have some free time I'll see what I can do on my TF700 running CM11.
Click to expand...
Click to collapse
:victory: I am more than willing to test any developments
In case anyone is wondering, this module still works on LP with the latest Xposed Framework.
Still working on the latest Xposed Framework for Marshmallow. Also tested against O365, and works just fine.
agentdr8 said:
Still working on the latest Xposed Framework for Marshmallow. Also tested against O365, and works just fine.
Click to expand...
Click to collapse
Hi, can you confirm if this works with the latest version of touchdown available currently, 8.5?
randallstevens said:
Hi, can you confirm if this works with the latest version of touchdown available currently, 8.5?
Click to expand...
Click to collapse
Yes indeed. I'm running 8.5.00086 with the module just fine. I'll update the OP.
EDIT: Looks like I had already updated the OP with that info. [emoji3]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IMPORTANT ANNOUNCEMENT (11/25/2017): https://forum.xda-developers.com/showpost.php?p=74628972&postcount=1071
IMPORTANT ANNOUNCEMENT (08/02/2020): https://forum.xda-developers.com/showpost.php?p=83193721&postcount=1236
Source code: https://github.com/gus33000/InteropTools
OP update is still Work in progress
READ BEFORE POSTING ANYTHING
Interop Tools can't be installed, like with a lot of other apps that uses restricted CAPs, if you CAP unlocked your phone using vcREG, vcREG changes 2 registry values that breaks the whole deployment system since one build of the rs1 development, so please reset your phone, use only vcREG to install an older NDTK if needed, and install Interop Tools (h/t @vcfan see your DMs)
Interop Tools doesn't require and will never require any CAP unlock
Please read the installation instructions carefully
Interop Tools versions older than or equal to Beta 1.8.1 are not supported in any way, please update the app
I'm not responsible for any damage made by your device if this ever happens even though I'm really careful each time I'm posting a new version
When submitting a bug report, please specify what apps related to Interop/Cap unlock you have installed, if you did anything, some reproduction steps and the phone model you are using, along with if you cap unlocked your device.
INSTALLATION INSTRUCTIONS
If you have an IT version older or equal to Beta 1.7 already installed, please uninstall it and reboot your device prior to installing/updating Interop Tools
Download the latest Interop Tools appxbundle for your device architecture and its dependencies
Extract both zips, and extract the certificate file if you're installing Interop Tools on a desktop device
If you're on a Desktop device, double click the certificate file, select Local Machine as the installation location, press next, select place the certificate into the following certificate store, and pick trusted peoples, then press ok, and next.
Install Interop Tools dependencies like any regular appx, by opening up the Device portal for your device, going into the application section, click on browser for the app package, select the dependency appx, and then press install, do that for each dependency
The install Interop Tools main appxbundle by pressing browser, pick it, then press install.
ENABLE SYSTEM REGISTRY ACCESS INSTRUCTIONS
For x50+ lumia devices by Microsoft
Download and install vcREG and proceed to install the older NDTK version as instructed in the vcREG thread, for support about this whole process, please see the vcREG thread in the same forum section
Don't do any CAP unlock, otherwise Interop Tools might not install properly
Install Interop Tools if you never installed it like instructed on this post
For other lumia devices by Microsoft
Go to the Interop Unlock section of Interop Tools
If restore NDTK isn't on, turn it on, and reboot your device
For all other OEM devices
Download the NDTK packages and the WPAK utilities from here: http://forum.xda-developers.com/attachment.php?attachmentid=3860782&d=1472659473 http://forum.xda-developers.com/attachment.php?attachmentid=3860780&d=1472659433
Go to the Interop Unlock section of Interop Tools, and tap the button that says "Enable installing NDTK on any device"
Put the two NDTK cabs in one empty folder on your PC
Open a command prompt as administrator and make sure you're in the directory where the iutool executable is located from the WP(AK) zip
run "iutool -V -p "<fulllocationwherethetwondtkpackagesarestored>" with your phone connected into the PC
if iutool throws an error, please unplug your device, go to the control panel, devices and printer, select your phone, should be ghosted, click on uninstall device, and then replug the device and wait for it to reinstall. If you still have issues, run GETDULOGS from the same CMD prompt, and post the cab you get along with a message in this thread
When the installation is finished, open Interop Tools, go to the Interop Unlock section, and tap restore the original manufacturer info button.
You can find a Q&A in the post below the OP.
FEATURES
This app allows you to:
Edit the registry through the registry editor
Browse the registry hives through the registry browser
Find sepecific registry values/keys through the search page
Apply tweaks to your device
Interop and Cap unlock your device
Access device information
Remotely edit the registry through the built-in desktop app
Manage Applications
Manage Certificates
Perform standard registry operations such as deleting, renaming, and copying details
Built-In Command Prompt inside the app (coming in pre-1.9)
Manage SSH accounts and more (coming in pre-1.9)
and more.
This app includes a lot of neat features which makes a better experience while editing the registry such as for example, the key suggestion bar in the registry editor, or the jump to button in the browser.
STATE OF THE APP
The app is still in development and has some rough edges. I would appreciate if you could report bugs about it, but before make sure you read the Q&A.
Currently the app has limited support for the registry for all devices running at least Windows 10 Mobile build 10240 by default.
Some specific devices have extra support out of the box, please read the list inside the spoiler below.
Lumia handsets (including other handsets with the ndtk service installed):
SYSTEM level access for editing and reading the following registry values and hives:
HKLM
HKCU
HKCR
HKU
HKCC
REG_DWORD
REG_QWORD
REG_SZ
REG_MULTI_SZ
REG_EXPAND_SZ
REG_BINARY
SYSTEM level access for LG and Samsung devices (untested, please report some feedback about it):
HKLM
REG_DWORD
REG_SZ
You can however enable more access privileges by following the instructions above, about enabling system registry access.
LINKS
See the second post for current pre-releases
Main Mega folder for download links and older versions: http://bit.ly/InteropTools See the current pre-releases
App Twitter account (for direct communication if I'm not available directly): http://twitter.com/InteropTools
My Personal Twitter account: http://twitter.com/gus33000
SCREENSHOTS
Credits:
Snickler, for the SSH stuff
VCFan for the Lumia RPC library.
Myria-Chan for the Test signing hack.
Microsoft for the other libs and the one coming with v1.9
And a lot more peoples helping me testing the app, reporting tweaks (also thanks for some tweaks to the peoples contributing to the WPTweaker project, especially for the brightness slider).
Current Pre-release:
https://forum.xda-developers.com/showpost.php?p=73608163&postcount=1006
Q&A
Q: What does "versatile" means?
A: It means that the app will work on every phone. But that doesn't mean it will work the same everywhere.
Q: Will this app work on Windows Phone 8.1?
A: No this is a Windows 10 UWP app, please fall back to using vcREG and CustomPFD for Windows Phone 8.1.
Q: I'm getting an error while installing one of all dependencies, what should I do?
A: Install all the dependencies first then install the one that throws an error. One of them depends on another one.
Q: The app doesn't install
A: Make sure you're installing the correct package for your processor architecture (x86_x64 is usually for PC, your phone is probably an ARM device) and that you installed all dependencies one by one prior to installing the app.
Q: I have a lumia which is not part of the x50 device family but I can't seem to be able to write some registry values.
A: Make sure under interop unlock, "Restore NDTK" is on, if not turn it on, reboot and try again.
Q; The app crashes.
A: Please submit a bug report with full detailed reproduction steps as well as your device model, if you tampered with ndtk before and other details that may help troubleshoot the crash such as the current running build and etc.
Q: What does TNSTSIGNING do?
A: It enables Test Signing on builds prior or equal to 10572. Don't be stupid and don't turn that on on later builds, your phone will most probably go into a boot loop.
Q: Can't install the versions above Beta 1.7
A: Re-read the installation instructions.
Q: How to install android with this app?
A: No you can't.
Can install this on win phone 8.1 i would like enable dng photos ?
L_u_k_e said:
Can install this on win phone 8.1 i would like enable dng photos ?
Click to expand...
Click to collapse
No this is a Windows 10 UWP app only, sorry. You can fall back to using vcreg and custompfd on wp8.1, or upgrade to Windows 10 Mobile if you wish to use this app.
I've already install version 1.7.157.0. When I uninstall it and reinstall with version 1.8 nothing happens. I tried reboot my phone.
quyleanh said:
I've already install version 1.7.157.0. When I uninstall it and reinstall with version 1.8 nothing happens. I tried reboot my phone.
Click to expand...
Click to collapse
Did you install all dependencies provided with beta 1.8.1 one by one before installing the main appxbundle? Dependencies changed between 1.7 and 1.8 and you need to reinstall all of them.
gus33000 said:
Credits:
dll coming with v1.9
Click to expand...
Click to collapse
Waiting for it.
Question: can you implement .reg files import?
Nice to see you here, Gus.
gus33000 said:
Did you install all dependencies provided with beta 1.8.1 one by one before installing the main appxbundle? Dependencies changed between 1.7 and 1.8 and you need to reinstall all of them.
Click to expand...
Click to collapse
Except Microsoft.NET.Native.Framework.Debug.1.3, I installed all remained dependencies through default File Explorer.
Hope it will work with version 1.9 tommorow.
Finally a post about Interop tools from @gus33000 himself. btw the app is a hope.thanks for all ur hard work mate..
quyleanh said:
Except Microsoft.NET.Native.Framework.Debug.1.3, I installed all remained dependencies through default File Explorer.
Hope it will work with version 1.9 tommorow.
Click to expand...
Click to collapse
Without Microsoft.NET.Native.Framework.Debug.1.3 it will obviously not work. You need to install that, even for 1.9
Note: you need to install that debug dependency after all the other ones actually.
Reg files import? Can be made?
augustinionut said:
Reg files import? Can be made?
Click to expand...
Click to collapse
That's actually planned since a while.
Awesome..
Thanks for share
Please can upload the file in zip? I cant download
Wanna download the lastest version but only appears 1.8, just for test CMD on my Lumia device.
gus33000 said:
Without Microsoft.NET.Native.Framework.Debug.1.3 it will obviously not work. You need to install that, even for 1.9
Note: you need to install that debug dependency after all the other ones actually.
Click to expand...
Click to collapse
I did follow your note and it worked like charm! Thank you very much!
chinitopex said:
Awesome..
Thanks for share
Please can upload the file in zip? I cant download
Click to expand...
Click to collapse
Wait for 1.9-prerelease which I will release today, that's mainly why I didn't attach any file.
Mafworld said:
Wanna download the lastest version but only appears 1.8, just for test CMD on my Lumia device.
Click to expand...
Click to collapse
Wait for 1.9-prerelease
Hello thank you for this app, I was wondering if this app can work on other phone that Microsoft or Lumia. I have a Blu Win HD LTE runing win 10 (14393.67) ?
Thank you
ck32 said:
Hello thank you for this app, I was wondering if this app can work on other phone that Microsoft or Lumia. I have a Blu Win HD LTE runing win 10 (14393.67) ?
Thank you
Click to expand...
Click to collapse
It will work yes, but some registry values might not be accessible to you. The Interop page, ssh/sftp/cmd, some tweaks will not work for example.
I finally did it!
UPDATE: The App is now fully released with the abiltiy to install packages with their dependencies and progress bar notifications on PC and Mobile! This app can now fully replace the built in App Installer and Windows Device Portal for sideloading apps
Source Code: https://github.com/colinkiama/UWP-Package-Installer
NOTE: I don't know if it's a bug or not but on mobile, when I open an .appx or .appxbundle, it asks me what app I want to use to install the package but it doesn't list mine. Maybe it's because I'm on the insider builds so please message me if opening the files works for you on mobile.
For mobile there's a workaround for this shown below. On PCs, the app works exactly like the built in app installer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How To Install: Unzip the file, install the dependencies first then install the appxbundle.
Download it here: https://github.com/colinkiama/UWP-Package-Installer/releases
Oh wow running awesome in mobile... But some bugs showed up...
1. Sometimes install completes, but still showing installing 98-99% in app..
2. Scaling is not quite perfect.. Please fix scaling for portrait devices...
Suggestion:
Please try to show app name and it's icon, like the App installer of pc
maruf8 said:
Oh wow running awesome in mobile... But some bugs showed up...
1. Sometimes install completes, but still showing installing 98-99% in app..
2. Scaling is not quite perfect.. Please fix scaling for portrait devices...
Suggestion:
Please try to show app name and it's icon, like the App installer of pc
Click to expand...
Click to collapse
I can fix 1. and 2.
But I need help with the suggestion. I need a way to get the metadata out of the package. My app handles a StorageFile object so it's pretty difficult. I would only be able to show the app name and logo AFTER the package has installed.
Package installer is now feature complete!
You can now install packages with their dependencies and install progress will show in a notification (on all devices including mobile running on the creators update or above). Devices running earlier versions of Windows 10 will have the install progress inside the app like before but there are some notifications that pop up too.
Download it here: https://github.com/colinkiama/UWP-Package-Installer/releases
Source Code: https://github.com/colinkiama/UWP-Package-Installer
Wow!!! This is freaking Awesome ?
Seriously loved it so much... But maybe a progress bar in app should be appreciated ?
EP1CNESSHD said:
I can fix 1. and 2.
But I need help with the suggestion. I need a way to get the metadata out of the package. My app handles a StorageFile object so it's pretty difficult. I would only be able to show the app name and logo AFTER the package has installed.
Click to expand...
Click to collapse
There's gotta be a way... Built in App installer in PC can read those metadata... Can you investigate it?
maruf8 said:
Wow!!! This is freaking Awesome
Seriously loved it so much... But maybe a progress bar in app should be appreciated
Click to expand...
Click to collapse
It might be possible using the extended execution and the "extendedExecutionUnconstrained" restricted capability. I've released the source code so anyone could add it in. I'm done with the project right now. I'll just open it up as an issue.
EP1CNESSHD said:
It might be possible using the extended execution and the "extendedExecutionUnconstrained" restricted capability. I've released the source code so anyone could add it in. I'm done with the project right now. I'll just open it up as an issue.
Click to expand...
Click to collapse
Alright... Thanks for your hard work ☺
maruf8 said:
There's gotta be a way... Built in App installer in PC can read those metadata... Can you investigate it?
Click to expand...
Click to collapse
There are some things that Microsoft know that they don't document. I'll open this up as an issue too. I've done research of my own but haven't found anything.
I can't seem to get this working in my Lumia 625, whichever app I try to install it just gives me a "The parameter is incorrect" I already installed the dependencies and have interop and cap unlock from Interop Tools, meanwhile Interop Tools can install apps normally (not entirely sure you were aware or not but that has also had the install appx/appxbundle option since a while).
On another note would there be any hope of you adding the option to also install xap?
Ranomez said:
I can't seem to get this working in my Lumia 625, whichever app I try to install it just gives me a "The parameter is incorrect" I already installed the dependencies and have interop and cap unlock from Interop Tools, meanwhile Interop Tools can install apps normally (not entirely sure you were aware or not but that has also had the install appx/appxbundle option since a while).
On another note would there be any hope of you adding the option to also install xap?
Click to expand...
Click to collapse
pm me more details about your phone and what you did to get that error.
I'm also aware that interop tools has had this install feature. I don't know if it can show progress on the notifications like my app can though ?.
Lastly, no I can't add xap support. The API I'm using doesn't support them.
@EP1CNESSHD well this app did start on builds before CU, even on builds before AU, it allowed me to select an app and a dependency but when pressing Install both on a build before AU (10586.36) and after AU but before CU (14393.1066 and 14393.1715) it would give me the "The parameter is incorrect" error as I described, however once I managed to get CU (15063.297 and then 15063.608) it just started working normally, no error anymore, I didn't even update to the new build from after I reported the error (will test that one on 10586.36 and probably AU afterwards since you confirmed the Notification Extension requires AU soon) so my only guess is that something used actually requires CU, I'll have a look and try to find out what that is when I have some free time.
If anyone has devices on the anniversary update, can you try debugging the app on visual studio. You can clone the source code and even open the project directly in visual studio from github. The link is here: https://github.com/colinkiama/UWP-Package-Installer
Please report any errors you find while debugging to this thread.
EP1CNESSHD said:
I finally did it!
Click to expand...
Click to collapse
Yeah! This app is very useful! Thanks a lot!
After lots of testing and feedback, this app is now absolutely amazing for Mobile! Now on the Creators Update, you can check your install progress in the app and/or in your notifications. If you still have a Windows Phone with Windows 10 lying around then you should get this app ASAP!
[PC Users only]
On the other hand, Windows 10 for PC is still really annoying. PCs won't install any appx/appxbundle packages without their certificates existing in the "Trusted People" certificate store.
However, one person has created a working win32 installer that works around this. Unfortunately, they haven't finished it. Microsoft has made this unnecessarily difficult to sideload apps on PC without paying a lot of money for a certificate. I would love to see someone come up with a workaround for this that makes it easy for every developer to distribute their apps to everyone.
Lol, I've just realised that I never actually released the new version with multiple progress indicators so here it is!: https://github.com/colinkiama/UWP-Package-Installer/releases
Please Add support To Install XAP Apps On Pc Or Add Support To Install ARM Apps On X86/X64 Pc
ahmed605 said:
Please Add support To Install XAP Apps On Pc Or Add Support To Install ARM Apps On X86/X64 Pc
Click to expand...
Click to collapse
is not possible
EP1CNESSHD said:
I can fix 1. and 2.
But I need help with the suggestion. I need a way to get the metadata out of the package. My app handles a StorageFile object so it's pretty difficult. I would only be able to show the app name and logo AFTER the package has installed.
Click to expand...
Click to collapse
What's the metadata file (name) do you want to get from Appx file maybe I can help you, do you mean "AppxManifest.xml"?
I want a Msixbundle installed. Can this do it if I rename it to an Appxbundle?