Develop Bugs

[GUIDE FOR DEVELOPERS] How to create HOMEBREW apps with NATIVE code on MANGO

When we were back on NoDo there were quite a few homebrew apps that used native code to apply tweaks to WP7 devices. Most of those apps seized to work after the device is upgraded to Mango. There a several reasons for this behavior. I've done research on this, because I wanted to make WP7 Root Tools compatible with Mango. In this topic I'd like to explain how developers can fix their apps to work on Mango again. It has taken me quite some time to compile this guide, but I hope to give the Homebrew development on WP7.5 Mango a boost.
This guide is NOT about creating homebrew executables (exe-files) for WP7. This guide aims to utilize native code DLL's (C++ / ARM) from within your Silverlight app.
Note that with native code you get access to a lot of extra API's. But that does not mean you automatically get access to resources you normally won't have access to. For example, you can use the CopyFile() API. But if you try to copy a file to the \Windows folder, you will get errorcode 0x4ec (1260), which means "Blocked by policy". So you are still bound to the rules of the sandbox of your app. If you want Full Root Access for your app, you have to wait for a new version of WP7 Root Tools, which will allow you to give your app root-access. I'm also working on an SDK for that, which wraps all common task into a neat managed library. But don't hold your breath for that, because it's all taking a bit longer than I expected.
To understand everything in this guide you need basic knowledge of C++, COM-interop and Silverlight for Windows Phone. If you are new to all this, you might want to do some reading on these topics first. Currently there is no way to debug the native code. The only thing you can do is create test-functions which return formatted debug-info. This makes things pretty difficult. Read the guide carefully, because a little mistake can make your app crash easily!
Important note: If you have any long-running tasks, they may work fine while you are debugging. But you need to make sure that you start a new thread to run this code. Because, when you run without debugger the WatchDog will monitor your application and if the User Interface thread is blocked for more than 10 seconds the WatchDog will exit your app ungracefully!
It has been suggested that native homebrew DLL's need to be signed with approved code-signing keys. This is in fact not true! You can use native DLL's on Mango devices, which are not signed at all!
Basically there are two reasons why homebrew apps are not working anymore:
- Interop Lock
- DLL's were built against libraries, which are not supported anymore on Mango
Interop Lock is discussed in this thread. Interop Lock is a new protection mechanism in WP7.5 Mango. Basically it means you can't use apps with ID_CAP_INTEROPSERVICES, unless a device is Interop Unlocked. Without ID_CAP_INTEROPSERVICES an app can't call any drivers. And most homebrew apps call these drivers directly or indirectly. So if an app uses the Interop Capability, it can only run on devices that are Interop Unlocked. If you're going to build an app that uses this capability on Mango, you'll have to give your users instructions on how to apply Interop Unlock on their device.
Most of the native code libraries that were used on NoDo, were based on a hand full of projects. These projects were created and then extended for their own needs by other developers. The result was that most of these projects had the same project-types and library-references. In Mango, a lot of DLL's that were not used anymore by Microsoft, have been removed from the OS. Mostly in the ShellCore. The DLL's were meant for MFC-type functionality, which was never even supported on WP7. Actually, these DLL's are not even used by the homebrew apps either, but there are references to these DLL's in the homebrew libraries, which will cause the library to fail loading into memory. You can see this behavior when you try to run an app with non-Mango-compatible native code on an Interop Unlocked device from within the Visual Studio 2010 development environment. When the COM-class is instantiated it will throw an COMException: "COM object with CLSID '{...}' cannot be created due to the following error: The request is not supported." This is errorcode 0x80070032. This exception is actually caused due to the fact that the previous call to RegisterComDll() failed. If you get the returnvalue of that function you should have 0. In this case the return-value is probably 0x8007007E, which is "Module Not Found". This actually means that you directly or indirectly refer to a DLL, which cannot be found on the device. To fix this we need to create a clean project and add our new or existing native code to that project.
Here are the steps to setup your development environment and create a new, clean project for your native code. Please keep in mind that this guide is still work-in-progress. I may add more detailed instructions and examples later on, when people ask for it.
Update 2011/10/15: Some improvements in the guide, based on comments of rudelm and GoodDayToDie.
Install Visual Studio 2008 with latest service pack and hotfixes. Make sure you install C++. You need Visual Studio 2008, because the necessary SDK does not support Visual Studio 2010.
Install Windows Mobile 6 Professional SDK Refresh.
Install Visual Studio 2010 with latest service pack and hotfixes. You need this to create your Windows Phone Silverlight app.
Install Windows Phone SDK 7.1.
Download the attached Microsoft.Phone.InteropServices.zip. After you downloaded the zip-file, open the file-properties and make sure the file is "unblocked" (Windows will block downloaded files). Some unzippers, including the built-in unzipper from Windows will mark the unzipped files as "blocked", which would give problems later on if you don't unblock first.
If your developmachine is 32-bit you go to "C:\Program Files\Reference Assemblies\Microsoft\Framework\Silverlight\v4.0\Profile\WindowsPhone71" or if you have a 64-bit machine you go to "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\Silverlight\v4.0\Profile\WindowsPhone71". Extract the DLL from the zip-file in this folder.
Open the Visual Studio Commandprompt and change directory to the folder where you just extracted the DLL. Then enter this command:
Code:
SN -Vr Microsoft.Phone.InteropServices.dll
In the same folder there is a subfolder called "RedistList". Open that folder and open the file "FrameworkList.xml". Add this line to that file:
Code:
<File AssemblyName="Microsoft.Phone.InteropServices" Version="7.0.0.0" Culture="neutral" ProcessorArchitecture="MSIL" InGac="false" />
Thanks to Tom Hounsell for this tip!
Install the latest version of Zune.
Open Visual Studio 2008 and create a new project.
Choose Visual C++ / Smart Device / ATL Smart Device Project and fill in a name and location for your native library. Do NOT choose MFC, or your library won't work on WP7! The name will be the name for the DLL. Later on you will create a COM-class. Choose a different name for your library and for your COM-class!
In the new wizard click "Next".
Remove the "Pocket PC 2003" from the Selected SDK list and add "Windows Mobile 6 Pro SDK" to the selected SDK's. Click "Next".
In "Application Settings" keep everything default and click "Finish".
Set your configuration to "Release", because you won't be able to debug anyway.
Go to Project Properties / Configuration Properties / C/C++ / Preprocessor / Preprocessor Definitions and add this: _CE_ALLOW_SINGLE_THREADED_OBJECTS_IN_MTA
Right-click the project and click "Add" / "Class" and choose "Simple ATL object".
In the new dialog enter the "Short name" for your COM-class. All other names are filled in automatically. Keep those names default to avoid naming-conflicts. Also make sure the name of your COM-class is different from the name of the library. All other options can are default, so you can click "Finish" now.
The basic layout for your native project is now ready. Note that you have these files: for your library you have a header-file (.h), a code-file (.cpp) and a COM-definition-file (.idl) and for your COM-class you have a header-file (.h) and a code-file (.cpp). I will refer to these files in the following steps, so make sure you can identify these files.
The COM-class you have now is based on IDispatch. IDispatch is the COM-interface that supports reflection-like functionality. The COMBridge in WP7 does not support this interface. Instead we should use IUnknown, which is the base-interface for all COM-objects and supports reference-counting.
In the header file of your COM-class you can see the public inheritance of IDispatchImpl. This is no problem and you can leave it as it is. But you can also see this COM-mapping:
Code:
COM_INTERFACE_ENTRY(IDispatch)
You need to remove that line.
In the IDL file of your library you need to change the inheritance of the COM-class from IDispatch to IUnknown.
Your native code layout is now ready to add your methods. A method in COM-class should always have HRESULT as return-type. This value should be 0 or positive in case of success (normally use constant S_OK for success). If you have an errorcode which should throw a COMException do a logical OR with 0x80070000 and return that value. If you want to return a variable, you'll to declare that as parameter of your method and decorate it as returnvalue in the IDL-file. The parameter-types are bound by the definition of COM. You can read about the supported COM-datatypes here and here. Study those parameter-types closely, because any mismatch in your managed and unmanaged declarations will make your app crash definitely. You need to add all your methods in 3 different places: in the COM-class code, in the COM-class interface and in the IDL-file. Later on you need to add an exactly matching interface to your managed code. All the declarations have their own specific format and decoration. I will give an example of two different functions for these 3 files. Note that in these examples, the COM-class was named "Native", so the class implementation is called "CNative" and the interface is called "INative". You have to change that if your class has a different name.
In the COM-class implementation (.cpp-file) add this code:
Code:
STDMETHODIMP CNative::TestMethod1()
{
BOOL result = ::CopyFile(L"\\Windows\\0000_System.Windows.xaml", L"\\Windows\\Test.xaml", TRUE); // This will fail due to insufficient privileges. This is expected behavior to show how errors can be handled.
if (result)
return S_OK;
else
return 0x80070000 | ::GetLastError();
}
STDMETHODIMP CNative::TestMethod2(BSTR InputString, BSTR* OutputString)
{
size_t size = 1000; // in chars
TCHAR* msg = new TCHAR[size];
wcscpy_s(msg, size, L"\0");
LPWSTR value = new WCHAR[20];
_itow((int)wcslen(InputString), value, 10);
wcscat_s(msg, size, L"Length of string is: ");
wcscat_s(msg, size, value);
*OutputString = SysAllocString(msg);
delete[] msg;
delete[] value;
return S_OK;
}
In the interface of the COM-class (.h-file) add this code immediately after END_COM_MAP():
Code:
STDMETHOD(TestMethod1)();
STDMETHOD(TestMethod2)(BSTR InputString, BSTR* OutputString);
Locate your interface in the IDL-file of the library. This may look a bit weird, because there are a lot of attributes that decorate the empty interface. Add these declarations to your interface (note the decoration of the parameters, read more here):
Code:
HRESULT TestMethod1();
HRESULT TestMethod2(BSTR InputString, BSTR* OutputString);
Now we need to locate two GUID's and copy them in a text-file, because we need these GUID's later on. These GUID's are in the IDL-file. We will call the first GUID "interface-GUID". It is the "uuid" in the tag RIGHT ABOVE the interface-declaration. We will call the second GUID "coclass-GUID". It is the "uuid" in the tag RIGHT ABOVE the coclass-declaration. There also a "uuid" in the tag above the library-declaration, but we don't need that one.
Open Visual Studio 2010 and create a new project: Visual C# / Silverlight for Windows Phone and choose a project-type, name and location.
Now go back to your native project in Visual Studio 2008. The compiled result DLL of this project will be used in your Windows Phone app. To make sure you always use the latest version of the native DLL in your Windows Phone app, you can add a Post Build Event to this project. This example assumes you will have a folder with a subfolder for the native solution and a subfolder for the Windows Phone solution. Go to Project Properties / Configuration Properties / Build Events / Post-build Events and add this (change the paths according to the soluton-foilder you will create for your Windows Phone app):
Code:
copy "$(TargetPath)" "$(SolutionDir)..\MyApp
If you checked the option "Create folder for solution" when you created the Windows Phone project, you may want to add another subfolder "\MyApp" to the path.
Now build your native project! The compiled DLL should now also be copied to the folder of your Windows Phone app.
Create a new file called "WPInteropManifest.xml" in the folder of your managed Windows Phone app. Copy this content in the file:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<Interop>
</Interop>
Switch back to Visual Studio 2010. In the solution explorer click on "Show all files". Your native DLL and the "WPInteropManifest.xml" should be shown now.
Select the "WPInteropManifest.xml" file and in the file-properties set "Build action" to "Content" and set "Copy" to "Always". You will always need this file in your project, regardless you will be calling drivers or not. If you don't have this file in your project, you won't be able to use your native DLL.
Select your native DLL and in the file-properties set "Build action" to "Content" and set "Copy" to "Always".
In the solution explorer, right-click on the project and choose "Add Reference". Then select "Microsoft.Phone.InteropServices".
Open the "WMAppManifest.xml" file and add this line below the other capabilities:
Code:
<Capability Name="ID_CAP_INTEROPSERVICES" />
Later on, you can try if your app will work without this capability. If you only use native code without calling drivers (directly or indirectly), you don't need the capability and your app will also work on devices that are not Interop Unlocked then. This specific example does not call any drivers, so in this example the ID_CAP_INTEROPSERVICES can be omitted and then it would run on non-Interop-Unlocked devices.
Now add a code-file to your project and copy this code into the file. You need the the coclass-GUID and interface-GUID you copied into a text-file earlier and you also need to replace the name of the class and interface to the names you used. Also note that the declaration must be an exact match (order and parameters) with the declaration in the IDL-file, although the IDL-file is differently formatted.
Code:
using System.Runtime.InteropServices;
[ComImport, ClassInterface(ClassInterfaceType.None), Guid("YOUR-COCLASS-GUID-GOES-HERE")]
public class CNative
{
}
[ComImport, Guid("YOUR-INTERFACE-GUID-GOES-HERE"), InterfaceType(ComInterfaceType.InterfaceIsIUnknown)]
public interface INative
{
void TestMethod1();
[return : MarshalAs(UnmanagedType.BStr)]
string TestMethod2([MarshalAs(UnmanagedType.BStr)] string InputString);
}
Note that the interface is declared as IUnknown.
Now you need to call the native code. You can add this code to the constructor of your Page or to the eventhandler of a button, or anywhere you like. Be sure to replace the DLL-name, interface-name and class-name and use your coclass-GUID. The exception is a well-known error-code and the exception will be casted to a UnauthorizedAccessException, instead of a COMException.
Code:
uint retval = Microsoft.Phone.InteropServices.ComBridge.RegisterComDll("WP7Native.dll", new Guid("YOUR-COCLASS-GUID-GOES-HERE"));
INative MyNativeCodeInstance = (INative)new CNative();
string result1 = "OK";
try
{
MyNativeCodeInstance.TestMethod1(); // UnauthorizedAccessException is thrown due to insufficient privileges. This is expected behavior to show how errors can be handled.
}
catch (Exception ex)
{
result1 = ex.Message;
}
string result2 = MyNativeCodeInstance.TestMethod2("Hello, Mango!");
MessageBox.Show(result1 + Environment.NewLine + result2);
You can now run your project! Be sure that you deploy it to your device. The emulator won't work, because you project uses native ARM code. The emulator runs on x86, so your native DLL won't load in the emulator.
When you go more advanced, you may need the Marshal-class. For example to copy a native memory-block to a managed byte-array. Be aware that there are actually two "Marshal" classes. There is "Microsoft.Phone.InteropServices.Marshal" and "System.Runtime.InteropServices.Marshal". They both look the same. But be sure you are using "Microsoft.Phone.InteropServices.Marshal", because it will allow you to do a lot more! Most methods in "System.Runtime.InteropServices.Marshal" will throw a MethodAccessException, because they are tagged [SecurityCritical], while the same methods in the other Marshal class will work.
I hope this will help you port your homebrew apps to Mango or create some fresh new homebrew! If you created an app with native code, drop me a line here. Show me your Screen Recorders, Accent Changers and more!
Ciao,
Heathcliff74

looking fwd to the native apps , a universal screenshot apps would be awesome..
Update :
scratch that, just ready that the app will be bound to the rules of the sandbox of your app.I guess that means no universal screenshot app yet

Its time to get native! Thanks Heathcliff.. I think I have a very good idea on something I could use native code for.. Ill pm you =)
Sent from my SGH-i917 using XDA Windows Phone 7 App

Suddenly, awesomesauce! Wow, big thanks Heathcliff74! Eve since you said you'd figured out homebrew native DLLs on Mango, I was really excited to see what people could do. I never guessed the real reason homebrew DLLs didn't work on Mango, although in retrospect this makes sense. You're awesome for investigating this for us.
Thoughts that immediately come to mind:
Update the existing screen capture apps.
Update the existing WebServer app.
(As part of the above) update the sockets DLL so we have server sockets again.
Explore how much filesystem access we have. Can files be copied from one app's isostore to another app's isostore?
Explore accessing drivers. The HTC update breaks filesystem access for HTC homebrew, but maybe there's another driver entry point we can use.
Investigate direct access to the SMS store (message backup?)
... and so much more. Oh, this is going to be fun!

the0ne said:
looking fwd to the native apps , a universal screenshot apps would be awesome..
Update :
scratch that, just ready that the app will be bound to the rules of the sandbox of your app.I guess that means no universal screenshot app yet
Click to expand...
Click to collapse
Hi!
Screenshots apps are definitely possible! The API for this can be called from within the sandbox and using OEM drivers it is possible to switch off dehydration. I already discussed this with fiinix and gave him this info. And I believe he almost has a Mango version ready.
Thanks for writing the article
Ciao,
Heathcliff74

great to hear about the progress
thanks Heathcliff74 for sharing!

Wooohooo nice HowTo! I will definitively try it and will report later. However, that will require that I go back to NoDo and back to Mango first. I'm not looking forward to that procedure... anyways awesome work Heathcliff, thank you!
@GoodDayToDie: you mentioned that the HTC libraries are fixed regarding file access. Julien Schapman from TouchXplorer mentioned something like that a while ago on twitter. Do you have any additional information on that topic? Is it just the DLL files from the HTC apps or is it something with the Mango HTC Update? I'll hope this is reversible, if I go back to NoDo and want to try Heathcliffs instructions :/

@rudelm, I only have experimental knowledge; I haven't dug into the actual update. However, the way that things like ComFileRW.dll work is by calling into some high-permission module in the HTC firmware (probably a driver using an IOCTL, though it could possibly be an RPC call to a privileged process) which then executes the requested action with high permissions. That's why the HTC DLLs don't do anything on other phones; they can't talk to the component that actually does the work.
My guess is that the HTC update simply turned off whatever it was that the COM DLLs are calling into. It could be more complex than that - for example, they could be trying to validate the caller, and prevent it from being used by homebrew - but whatever they did, neither DLL works anymore once you have the HTC update *even though the DLLs themselves did not change.*
Is it reversible? Well, "fixing" whatever component they were calling into is one option. Using Heathcliff74's Root Tools to gain full permissions on a "normal" homebrew app is another. There might be more, but it would need more study.

Thanks. Will try it. Hopefully i can get "GetPhoneNumber" from Windows Mobile 6 SDK to run or maybe trying http://blogs.msdn.com/windowsmobile/archive/2004/11/28/271110.aspx

GoodDayToDie said:
@rudelm, I only have experimental knowledge; I haven't dug into the actual update. However, the way that things like ComFileRW.dll work is by calling into some high-permission module in the HTC firmware (probably a driver using an IOCTL, though it could possibly be an RPC call to a privileged process) which then executes the requested action with high permissions. That's why the HTC DLLs don't do anything on other phones; they can't talk to the component that actually does the work.
My guess is that the HTC update simply turned off whatever it was that the COM DLLs are calling into. It could be more complex than that - for example, they could be trying to validate the caller, and prevent it from being used by homebrew - but whatever they did, neither DLL works anymore once you have the HTC update *even though the DLLs themselves did not change.*
Is it reversible? Well, "fixing" whatever component they were calling into is one option. Using Heathcliff74's Root Tools to gain full permissions on a "normal" homebrew app is another. There might be more, but it would need more study.
Click to expand...
Click to collapse
uhoh... sounds pretty bad for HTC users. If it was a firmware update, we will have a bigger problem. I will try to revert back to Nodo and will try Heathcliffs instructions for Native Code first. InteropUnlock is still something I need to try for Mango

rudelm said:
uhoh... sounds pretty bad for HTC users. If it was a firmware update, we will have a bigger problem. I will try to revert back to Nodo and will try Heathcliffs instructions for Native Code first. InteropUnlock is still something I need to try for Mango
Click to expand...
Click to collapse
No worries. I did some testing with contable and we just got confirmation that my exploits for HTC will still work on HTC Interop Unlocked Mango devices (needs a little adjustment, but No Problem!) Still working on a version of WP7 Root Tools for Samsung/HTC/LG RTM/NoDo/Mango!!
Ciao,
Heathcliff74

A screenshot app is allready there:
TouchXperience for Mango from Schaps.
Atm there is only missing the WPDM Mango update for being able to save the screenshot...

Heathcliff, could you please try to fix that HTC bug first? I am running into this problem with the HTC update and now my old code does not work anymore But at least my phone is finally interop unlocked because I could deploy the app on Mango but I get this error:
COM object with CLSID '{C6BD09B4-96AA-4524-89C4-665A15DD7C9B}' cannot be created due to the following error: The request is not supported. .
Which is one of the errors you mentioned on the first page. So far, so good

rudelm said:
Heathcliff, could you please try to fix that HTC bug first? I am running into this problem with the HTC update and now my old code does not work anymore But at least my phone is finally interop unlocked because I could deploy the app on Mango but I get this error:
COM object with CLSID '{C6BD09B4-96AA-4524-89C4-665A15DD7C9B}' cannot be created due to the following error: The request is not supported. .
Which is one of the errors you mentioned on the first page. So far, so good
Click to expand...
Click to collapse
I don't get what you mean. What HTC bug? What HTC update?

Ok, I will explain it:
There was a HTC Update when I upgraded from Mango B2 Refresh to the Mango RTM from Microsoft. It was followed by a smaller HTC Update. It was called HTC Update for Windows Phone. You can read it here in my blog.
Yesterday, I decided to revert back to NoDo, so that I could Interop Unlock my HD7 before I upgrade to Mango RTM. I did this with these tools and instructions from petbede.
However, ansar found out, that MS changed the update procedure and included the HTC update directly in the 7720.68 update.
Now you mentioned yesterday, that you and contable found a solution to use the HTC DLLs although there was this HTC update on our phones. That was when I already feared that the HTC update will break everything I tried so far.
So I called it the HTC bug, because it breaks my stuff

rudelm said:
Ok, I will explain it:
There was a HTC Update when I upgraded from Mango B2 Refresh to the Mango RTM from Microsoft. It was followed by a smaller HTC Update. It was called HTC Update for Windows Phone. You can read it here in my blog.
Yesterday, I decided to revert back to NoDo, so that I could Interop Unlock my HD7 before I upgrade to Mango RTM. I did this with these tools and instructions from petbede.
However, ansar found out, that MS changed the update procedure and included the HTC update directly in the 7720.68 update.
Now you mentioned yesterday, that you and contable found a solution to use the HTC DLLs although there was this HTC update on our phones. That was when I already feared that the HTC update will break everything I tried so far.
So I called it the HTC bug, because it breaks my stuff
Click to expand...
Click to collapse
I see. Well, I didn't find a solution. I just checked if MY exploit still works. And it does! I don't even know what you use exactly (I assume you use some HTC DLL's, but I don't know which and I don't know which functions). I don't use the HTC DLL's myself. Mainly because I don't want to get copyright issues when releasing WP7 Root Tools. Just look at the current release of WP7 Root Tools. No OEM code in there. So I don't think I can fix that for you.
Ciao,
Heathcliff74

Hm ok, I understand. I was using a HTC dll for changing a registry value (overriding DHCP DNS Server). However, it is interesting to know why the HTC DLLs all of sudden stopped working after this update. The DLLs inside the HTC tools seem to be the same size and should not be changed by the update.
But this shouldn't then influence the DLL made with your instructions in this thread i guess?

@rudelm:
The HTC devices have HSPL support, so why you don´t flash the latest xboxmod rom ? This saves a lot of time and all available types of unlocking can be sent via cab sender.
For writing registry keys or doing file operations you can use DiagProvXML til Heathcliff has finished the next version of WP7 Root Tools.
Is there any other reason why you are updating your phone the official way ?

@rudelm: The HTC DLLs don't actually have elevated permissions by themselves. To do things that an app n ormally lacks permissions for (like accessing the whole filesystem or writing to the registry), it needs to call into a high-permission component (probably a driver or a high-permission process). All HTC had to do to make the registry and filesystem COM DLLs stop working is to change that component so it didn't do what the COM DLLs told it to do.
@contable: I've heard enough reports of things that *should* work on HTC phones not working on the custom ROMs that I'm hesitant to install one. Then there's the risk of bootloader issues. Then there's the lose-all-your-data-because-your-phone-gets-reformatted issue - until I have my backup app working fully, I prefer to avoid the last one in particular.

Edit: If you are looking for working attachments, please look at this posting.
@contable:
I need an unmodified version of WP7 for my master thesis. The other thing is that I don't want to play around with HSPL without having the original SPL or firmware. It's like GoodDayToDie said: I'm still hesitating of the said reasons.
@GoodDayToDie:
The HTC applications still work and they were not updated afaik. So they are using the same DLL files. If there would be some driver running in TCB or ECB and they changed something, then their applications should stop working too. However, they can still be executed without problems. I am not sure what DLLs are used by advancedexplorer, but I think it were also the HTC dlls. My own application which used the HTC dlls stopped also.
@Heathcliff:
I've tried your instructions and found some errors in it:
step 23: *OutpuString = SysAllocString(msg); instead of *OutputString = SysAllocString(msg);
step 25: ; missing after OutputString)
step 28: add \MyApp to path, because VS2010 Solutions always have a subfolder with the same name of the solution
step 36: [return : MarshalAs(UnmanagedType.BSTR)] should be [return : MarshalAs(UnmanagedType.BStr)]
step 37: result 2 needs a type => string result 2 = ...
on first run:
Error 1 Could not load the assembly file:///C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\Silverlight\v4.0\Profile\WindowsPhone71\Microsoft.Phone.InteropServices.dll. This assembly may have been downloaded from the Web. If an assembly has been downloaded from the Web, it is flagged by Windows as being a Web file, even if it resides on the local computer. This may prevent it from being used in your project. You can change this designation by changing the file properties. Only unblock assemblies that you trust. See http://go.microsoft.com/fwlink/?LinkId=179545 for more information. NativeTestApp
Click to expand...
Click to collapse
This is because you forgot to register the DLL first. Look here: http://thounsell.co.uk/2010/11/avoi...g-the-interopservices-library-to-the-wp7-sdk/ and then down in the comments:
You must open the visual studio 2010 command prompt as administrator and call:
SN -Vr Microsoft.Phone.InteropServices.dll
then close and reopen Visual Studio, now it should work
Click to expand...
Click to collapse
In addition that, you will have to unblock the file in Windows Explorer, Properties of the file. Otherwise you will get this error in Xaml view:
Could not load file or assembly 'Microsoft.Phone.InteropServices, Version=7.0.0.0, Culture=neutral, PublicKeyToken=24eec0d8c86cda1e' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)
Click to expand...
Click to collapse
This unblock will only work, if you use the Windows Explorer in administrator mode. The DLL file should be copied to a path were every user can access the file. Unblock it there and move it than back to the WindowsPhone71 folder. I've extracted it directly to the WindowsPhone71 folder and I couldn't change its properties there.
I've created a VS2008 and VS2010 sample project on your instructions and tried to add some comments to the sources. I've attached them to this post. Here are a few extra information to my project:
Interface-GUID: D28D8CB9-F8BC-4379-9D0A-FA77C87EF814
coclass-GUID: 7300CD4A-03F4-4569-B2D8-F1515385D46D
COM Class: NativeTestClass
INativeTestClass and CNativeTestClass
Always results in retval 0 and this exception:
System.MethodAccessException was unhandled
Message=Attempt to access the method failed: System.IO.FileInfo..ctor(System.String)
StackTrace:
at Microsoft.Phone.InteropServices.ComBridge.RegisterComDll(String dllFileName, Guid clsid)
at NativeTestApp.MainPage.actionButton_Click(Object sender, RoutedEventArgs e)
at System.Windows.Controls.Primitives.ButtonBase.OnClick()
at System.Windows.Controls.Button.OnClick()
at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
at System.Windows.Controls.Control.OnMouseLeftButtonUp(Control ctrl, EventArgs e)
at MS.Internal.JoltHelper.FireEvent(IntPtr unmanagedObj, IntPtr unmanagedObjArgs, Int32 argsTypeIndex, Int32 actualArgsTypeIndex, String eventName)
Click to expand...
Click to collapse
I've rechecked every step but I am still stuck. The phone itself should be interop unlocked, otherwise I couldn't have deployed the app with the capability activated. Could you please look into it? I know this error from my earlier attempts to access the HTC dll directly, but then I used the NativeLibrary here from XDA which took care of all the GUID things etc.

[Source][Dll][XAP] The HtcRoot project - Testers needed

The result of probably more than 100 hours of solo hackery: a working COM DLL for allowing any application to elevate itself to SYSTEM (root) permissions.
What you need:
An interop-unlocked HTC phone. Sorry second-gen and Arrive users.
A working HtcUtility driver. It's possible some HTC update at some point crippled this. It works for me; if it doesn't work for you let me know what updates you have.
What it does:
Allows changing the security token of any application to give that app unrestricted permissions. At this point, you can call any user-mode API, perform any operation, with full access.
It also allows you to read or write any value from memory, even kernel memory (this is how it modifes the security token).
What it can be used for:
Darn near anything. If it can be done while the phone is booted, you can do it.
What it can't be used for:
Modifying the ROM - the R and O stand for "read only" and they mean it.
Interop-unlocking a phone - it requires interop-unlock to get root in the first place.
How to use it:
In your app, include the HtcRoot.dll library.
Include the code from DriverAccessTest.cs in the test app (defines the COM API and enables using it).
Call the OpenHtcUtility function (will throw an exception if your device is incompatible).
Call the MakeMeRoot function (can also throw exceptions).
(OPTIONAL) Call the ReturnZeroIfRoot function to make sure your app is elevated (does not throw exceptions, will return an error code if you get one).
Do stuff with SYSTEM permissions (probably using another COM DLL, such as for registry or filesystem access).
Call the RestoreToken function (failure to do this *might* cause a kernel memory leak).
Call the CloseHtcUtility function (OS will probably handle this if program just exits).
What you can do right now:
Try the test app. It should pop up a series of messge boxes. Hopefully none of them say anything like "FAILURE".
Report any bugs or failures you discover.
Build things with this library, and publish them!
Breakdown of the download:
There are two folders in the ZIP, one for the Visual Studio 2010 C#/Silverlight XAP project, and one for the Visual Studio 2008 C++/COM DLL project.
The test XAP is in the HtcUtilityTest\bin\Debug folder.
The native (COM) DLL is also available in that folder, or under its own project.
If you want to mess with this, I'm going to assume you are already familiar with hybrid native/managed development for WP7. If not, Heathcliff74 has posted an excellent tutorial on this forum.
Special thanks to:
Heathcliff74 for the hybrid app tutorial and interop unlock info.
Paul_Hammons for the links and info about HtcUtility, the driver that makes this possible. Thread: http://forum.xda-developers.com/showthread.php?t=1434793

Supported devices / firmware versions / ROMs
All HTC devices (if interop-unlocked and with the right firmware numbers) should be compatible.
Some custom ROMs work, some do not. This will depend on the version of the firmware that the ROM's HtcUtility driver is taken from.
I believe I compiled the test app as Mango-only, but the native library doesn't care at all.
Compatible:
Stock ROMs with compatible firmware for HD7, Trophy, Mozart
HD2 (BttF [XBmod-Yuki] v2 SP1)
Not compatible:
Firmware version 2250.21.51004.401 or newer
Verizon Trophy firmware version 2305.13.20104.605 or newer
DFT ROM with build 8107, Firmware 5.10.401
Arrive (except on pre-Mango), Titan, Radar, Titan 2 (no interop-unlock)
Others are untested or results are incomplete.
Goals and future work:
Support more devices:
* Try and add support for newer firmware.
* Help ROM cookers ensure the library is supported.
* Look for similar openings in other OEM libraries.
Future-proofing:
* Allow installation of a mod to support this capability after known updates.
* Resilience against possible future updates.
* Allow users with incompatible devices to downgrade (possibly to NoDo), install the mod, and be able to use the phone after upgrading.
Improve the library:
* Fix some memory leaks.
* Clean up the code - remove dead code and improve comments.
* Allow reading/writing more than 4 bytes at a time from managed code.
* Add APIs to elevate other processes (by name or ID) to SYSTEM.
Develop homebrew around the library:
* Support accessing common APIs (filesystem, etc.).
* Resurrect the Advanced Explorer app, perhaps (registry and filesystem).
* Support native app launching on stock ROMs.

Also reserved
Reserved for OP #2

It does not work on HTC 7 Mozart (HTC Europe):
Error to Write the value 1337 to test address - System.Runtime.InteropServices.COMException (0x8007001F): A device attached to the system is not functioning
Click to expand...
Click to collapse
OS: 7.10.7740.16
Firmware: 2250.21.51101.401
Radio: 5.71.09.02a_22.51.50.21U
Boot: 5.11.2250.1(133487)

Please include the full error message or a description of what went wrong.
Failure on fully updated devices is unfortunately possible - my phone is (intentionally) a few updates behind. I'm looking into ways to make it work anyhow (either sending an older CAB update to roll back, or using the root acess to create an unlocker/root-enabler that survives subsequent updates). I'm going to look into how the full-unlock ROMs differ from standard ROMs, and see if I can do the same thing in running software.

Does it works with custom roms?

If the custom ROM has a working HtcUtility driver, then yes. My goal is to unlock the kind of capabilities normally restricted to custom ROMs on stock firmware, though.
@bleh815: Thanks for the report. That's frustrating; it looks like it is capable of doing read but not write. Write might just be restricted in what addresses is allowed, or it might be disabled entirely (the driver gives the same error code for every problem that I've encountered so far). Time to figure out
A) what update causes the problem (I'm on 2250.21.30102.531, HD7, stock ROM)
B) what restrictions that update introduces
C) how to work around those resrtictions (possibly by downgrading and then using root access to add something that will still work after upgrade).

GoodDayToDie said:
A) what update causes the problem (I'm on 2250.21.30102.531, HD7, stock ROM)
Click to expand...
Click to collapse
I've just downgraded a mozart of mine back to stock NoDo (TMOB-DE) to find out which OEM update breaks (actually fixes) it.

Cool, thanks! It's one of the post-Mango HTC updates; a Microsoft update wouldn't have modified an HTC driver, and my phone has all the pre-Mango HTC updates but it still works.

.
..........

Hi, at first it says "SUCCESS!", then it says "Trying to open a file gives error 1260" and then it says "Now opening a file gives error 0" and finally "Finally, opening a file gives error 1260".
System informations:
OS=7.10.7720.68
Firmwareversion=2250.21.12200.162
Radio=5.68.09.05a_22.50.50.21U
Bootloader=4.6.2250.0(129185)
HTC 7 Trophy.

That is *exactly* the sequence of messages it is supposed to give!!
In particular, the messages I need to see are the "SUCCESS" (the rest is potentially interesting info, but not very important) and then the "Now opening a file gives error 0".
The "SUCCESS" means that a sequence of read/write tests succeeded.
The "Now... error 0" means that the process has been elevated to full permissions.
The "Finally... error 1260" means that the security token was successfully restored at the end, so it was unable to open the file again. This is the expected and correct behavior.
I don't recognize your Firmware Version number; I'm guessing it's specific to your phone. What method did you use to upgrade to Mango?

how do i install it?

Tried on interop-unlocked HTC Surround, not working Tested any call in VS debug mode - no luck at all.

I can confirm that it works with any OS version, from 7004 to 8107.79
On a HTC 7 Mozart (TMOB-DE) it works with firmware 2250.21.13201.111 (Stock NoDo ROM) but the hole gets fixed with 2250.21.51101.111 (1st Post-Mango HTC Update).

You guys are gods taking programming to a hole new level!
I wish to see ms take you all more serious and not let wp7 fail like minmo6.5 did!
I wish I could get on your level!
I realy need some help lerning basic silverlight my self!
But I have read how hybrid working ant this is just fantastic!
conradulations on all your developments so far you guys are truly amazing!

Oh, that code, beautiful reading that!
Thanks for sharing this learnfull code!

I'd like to try it on my Verizon HTC Trophy, I would love to get file access back....
I downloaded the package and I even have VS 2010 installed but beyond that I have no idea as I am not a programmer.
Can someone post a compiled XAP for us to try to see if our phone works with it or not ?
Or some step by step VS 201 directions to try would also be helpful.

@Ttblondey: *FACEPALM* The path to the test XAP is given in the opening post. You install the XAP on your phone using any XAP deployment tool. It requires that your phone be interop-unlocked; Heathcliff74 has a nice long thread about that. The app is called called HtcUtilityTest. Run it, and report the results. If you want to actually *use* the DLL, the instructions for doing that are given too but you need to write some code.
@sensboston: PLEASE give a more complete report! Success and error messages, at the least. Also, your phone version info. Thanks!
@bleh815: THANK YOU! I mean, it's a little annoying to know how far back this was fixed ("First post-Mango HTC update" means the one that was included *with* Mango for most people, or the one after that?) but good to know. Now, to look at exactly what they changed...
@jackrabbit72380: Thanks man! As for working with it yourself, like I mention below, I'm planning to provide a universal homebrew library that people can easily use to do whatever they want.
@fiinix: You're welcome! Honestly, I didn't expect anybody to call my mess of debug-commented and mildly hacky C++ "beautiful" but that hack itself *is* pretty awesome. My only concern with using it is the risk of a context switch causing the wrong app's token to get overwritten, and I should probably look into that, but I think it's OK for the moment. There are bigger fish to fry.
In the meantime, it should open up a huge list of capabilities for tools like your DllImport project. I'm currently considering reviving Advanced Explorer (like TouchXplorer + Registry Editor, but open source; was never ported to Mango though) using the root access instead of using ComFileRW and the provxml driver. Let me know what you want to do with it!
One other thing I'd like to add is the ability to easily elevate *another* process; it's not hard to do but I haven't written it yet. This could be handy for apps where we don't have the source code (for example, elevate Schaps registry editor, which uses low-privilege native code for browsing, so it can read *all* registry locations instead of just some of them).
@DavidinCT: Well, running the test app is easy, just install the XAP. It just runs a battery of tests though, it doesn't actually *do* anything useful. To get filesystem access, you'll need to write some native code (which means using Visual Studio 2008 and the CE/Smart Device plug-in, see Heathcliff74's toturial on the subject). Basically, you would first use this DLL (accessed via COM, you can look at my own C# code for how to do that) to opent he driver handle and elevate the process to root. You could then write your own COM DLL that uses the standard Win32 filesystem APIs (CreateFile, etc. - all are documented on MSDN) and exposes those APIs, or the results of them, to managed code via COM. Then, back in your phone app (the one that called into my HtcRoot DLL) you can call into your own DLL to access the file system.
If that's too big a leap, don't worry. I plan to release a general-purpose high-privilege homebrew DLL that exposes some of the most-used functionality (filesystem, registry, provxml, and other things by request), is easily extensible (possibly using something like the DllImport project, where you just specify the function you want to call and the DLL it's located in right from C#), and that will be a lot easier to hack with. You'll still need to know C# and basic Silverlight, but it'll be a lot easier (and hopefully useful without knowing any C++ or COM).

GoodDayToDie, you are amazing, always keeping me interested!
When starting the test xap, I get the below, it then goes into the "Page Name" and that's it.
Device Info here, running a FullUnlock DFT Rom by a Chinese dev from the DFT Forum.
Nonetheless, top work on getting this started and can't wait to keep reading about the progress!
XeKToReX

Are there yet any ssh libs working in mango?

My plan is to build an app which could transfer a printable file to a remote unix based system, send some bash commands and read the results.
I haven't found any confirmation about working ssh libs. Are there any?
My phone is unlocked so accessing the file system and unnative libs aren't a problem but it would nice if that isn't compulsory.
Thanks in advance!

opaounari said:
I haven't found any confirmation about working ssh libs. Are there any?
Click to expand...
Click to collapse
Have you ever tried to google "Silverlight SSH"? The very first link should bring you a reference to http://sshnet.codeplex.com/ (already ported to WP7/SL)
Also you may try to look/port these free libs:
http://granados.sourceforge.net/
http://sourceforge.net/projects/sharpssh/

Whopsie! I only tried to google "c# ssh" or with windows phone. Only found out about sharpssh, granados and else but their functionality wasn't guaranteed... Thanks alot I try'll that out and sorry!

opaounari said:
Thanks alot I try'll that out and sorry!
Click to expand...
Click to collapse
Here (on XDA) we do have a "Thanks" button, located under helpful post. Don't hesitate to use it

Of course! Thanks for pointing that out.
I tried to use the lib u mentioned
By these steps:
1: Download & unzip
2: In visual studio I have my windows phone project open
3: Solution Manager -> Right click on my project -> Add reference -> Projects tab -> Renci.SshNet -> OK
Then it just displays error:
Microsoft Visual Studio 2010 Express for Windows Phone
Unable to add the selected project reference. The project reference must be another silverlight for Windows Phone project that is the same or lower version.
-> No clues :S even after googling this alot.

You should use Renci.SshNet.WindowsPhone.dll (http://sshnet.codeplex.com/releases/view/83611#DownloadId=352294)
Or download source code tree and add WP7 project as reference (http://sshnet.codeplex.com/SourceControl/list/changesets# )

Looks like there is a nuget package too:
http://nuget.org/packages/SSH.NET

Interop Tools Appx for Windows 10 Mobile - registry editor

Interop Tools is a brand new registry editor that works on Windows 10 Mobile, It allows you to View, Browse and Edit of registry entries. Great news is that this tool doesn’t need your device to be interop-unlocked for this. The tool has been developed by Gustave M, who is a well-known Windows enthusiast and developer.
How to Download & Install Interop Tools on Windows 10 Mobile:
1. Download the Interop tools Appx file from attachment, unzip
2. Now all you need to do is to turn on the developer option by going to Settings—>Update & Security–>For Developer–>Select Developer Mode and select “yes” when prompted. This enables side-loading of apps.
You should be now able to install “Interop Tools” by tapping on the Appx that you have downloaded in first step.
3. You should be ready to have some fun, though be careful before editing registry unless you know what you are doing.
4. Once installed, the app appears under installed apps
The tool is not Lumia-specific but seems access to restricted keys is only for Lumias.
Source
http://www.windowscentral.com/interop-tools-windows-10-mobile
edit: if you have problem with newer version, simple uninstall app from storage, restart phone and install again.
Interop Tools Beta 1.7.157.0 (fbl_release(gustavem).160621-0900) changelog:
+ New helper runtime component, all core registry editing functionality have been migrated to registryhelper.winmd, as such, there might be new bugs, especially in the registry browser. Please report them if you find any.
+ WinPRTUtil is now also used in the browser and in registry value deleting operations.
~ Fixed an ux issue with light theme enabled.
~ Fixed an issue where HKD would be incorrectly named in certain areas.
~ Fixed an issue where the tool would incorrectly report the state of offline charging when loading the page.
Click to expand...
Click to collapse
Official download location: http://bit.ly/InteropTools
NOTICE: ARM for mobile, x86/x64 for PC

Now if we could only use a similar method to get an Adblocker on the 950/950XL...

jhoff80 said:
Now if we could only use a similar method to get an Adblocker on the 950/950XL...
Click to expand...
Click to collapse
you cant. this is only for WP8.1 devices with W10M... not for native W10M devices (550, 650, 950, 950XL)... you can install on Lumia 950/950XL and change some registry values but you cant access to MTP to use adblock (change hosts file)

Can this be uninstalled from the phone?
EDIT: nvm. I got it. Disable developer mode, try to open app, get error, uninstall

The file works perfectly in nokia lumia 520 windows 10 mobile build 10586.242
but I have a question
which is the benefit of this application?
I have a nokia lumia 520 with windows 10 mobile build 10586,242
but still not unlocked for use XAP files and appx
so this application can give me those benefits?
I would like to know more about how to install files with this application appx
thank you ... is great news for our lumias

dxdy said:
you cant. this is only for WP8.1 devices with W10M... not for native W10M devices (550, 650, 950, 950XL)... you can install on Lumia 950/950XL and change some registry values but you cant access to MTP to use adblock (change hosts file)
Click to expand...
Click to collapse
Yeah, I know, that's what I meant- This is great progress from the old way of getting access to these things, but what would really be nice is something similar that allowed adblock.
---------- Post added at 04:10 PM ---------- Previous post was at 04:08 PM ----------
DLS123 said:
Can this be uninstalled from the phone?
EDIT: nvm. I got it. Disable developer mode, try to open app, get error, uninstall
Click to expand...
Click to collapse
You can also uninstall from the Storage page in System.

thank you . Awesome Tool

Hi
I tried changing the video resolution (VideoResolution) registry value from 3 to 4. This opens 4k recording resolutions in camera app on my LUMIA 730 dual sim and also the SLOW MOTION option in video recording. But when recording is pressed it shows the device can't save the video. Im new to this, so if anyone can help to find me any turnarounds or is this due to hardware limitations. Thanks

Looks like file explorer. A search button can.t be aded?

Just saying
OP,
You copied all the content from Nokiapoweruser article and gave source link to WindowsCentral. Try to be fair!!

seems to be a nice little tool
but anyone knows what i have to use for sftp accesss as username and passwort when using winscp to connect?

Read this
http://forum.xda-developers.com/windows-10/windows-10-mobile/guide-filesystem-access-sftp-windows-10-t3185766

yes did that, but made a two mistakes figured it out with the dev of the tool, btw he released a new version a few hours ago
https://mega.nz/#!eZNRFRJB!ZszQcU1lAAQhbj14y4E70wIQhbDqWNIvZ0CmCcKHUWY
few bugfixes for th2 branch
finally again full fs access to the public apps folder (had problems with that before with interop unlock)

KNM_THe1 said:
OP,
You copied all the content from Nokiapoweruser article and gave source link to WindowsCentral. Try to be fair!!
Click to expand...
Click to collapse
i not open NPU for months, WC is only WP blog which one i read.... but this one first i see it on one pirate site, but link there lead to WC not NPU

And for those wondering what sort of hacks/tweaks they can do using this prog/tool, there's a thread for that:
http://forum.xda-developers.com/showthread.php?t=2434959&page=41

Has anyone found a key to enable call recording on older phones?

Aj6627 said:
Has anyone found a key to enable call recording on older phones?
Click to expand...
Click to collapse
this not possible via registry.... is already discussed on forum...

The author of Interop Tools is gus33000 aka Gustave M.
Official source links:
https://twitter.com/gus33000/statuses/731780368853041152
https://mega.nz/#F!iZMhSSzI!sGQy4V12ubfvT8Abm2Uo1g
----------
Interop Tools beta 1.2
Changelog:
+ The registry browser value editing dialog now displays the value type and name.
+ The registry browser now correctly handles write errors and will display them to you.
+ The registry editor now saves the history and has a new clear all button to clear all of them.
+ You can now tap a history item in the registry editor and it will fill all fields for you.
~ Improved the Registry browser ui again.
~ The app is now a regular app and not a settings app as there was many requests for this.
~ New icon for the app.
~ Small ui changes on the welcome page.
~ Bug fixes.
Known issues:
* It appears there is an editing issue for the pagingfiles on redstone, where the value is not set, this might be due to the key being reverted automatically. This is under inspection.
? It appears there is an editing issue for the pagingfiles on threshold, where some ";" appears instead of spaces, I can't reproduce it on my side, so if you could confirm or not confirm that to me on twitter that would be great.
Side notes:
* I know I need to add a way to alert from the app of new updates, this is under consideration.
* A small tweak page is in the works, if you have tweak ideas please tweet me them with the page where you found them or yourself if you found it, so I can properly credit peoples.

You may ad poweroff charging. Sure will be a huge succes.

Hi. I am unable to install it. It just closes when tapping from device and confirming install. When in AppDeploy app, I got this error "Error - There is an error in XML document (18, 15)." I'm using Nokia 925 Windows 10 10586.318. Please help what am I missing here?

hacking nac peugeot

hello,
anyone can help me to find a way to unlock/hack the infotainment system on the new peugeot 3008/5008 ecc.
i've tried to hold note button for engineering mode but only for spy menu.
anyone have more differently code for unlock android setting? for example how the kia/hyundai cars?
please sorry for my english....

I found the code 1122 to access the radio monitor...

hi guys, I'm also looking for a way to get into the hidden menu of the NAC (3d Connect Nav) Peugeot. My car is a 2008, with CarPlay, Mirrorlink and Android Auto. Now compared to what I saw for the KIA, I would try to figure out if there is a chance to enter the system that is declared Linux, and find a gateway like an android virtual emulator, on which even turns android auto, to install other applications directly on the multimedia of the car. The only 2 codes we know are: 1111 1122, the first for spylogs, the second one gives us a series of info on the system, but apparently they are only legible and there is no way to get inside. In practice using the code 1122 the first time also gave me only info on the radio, but then typing in increasing order the following codes and typing 1122 again, for several times I have drawn many other info. I took pictures that I would like to share with you to find out if there is a chance to find a way.

umbeluxa said:
hi guys, I'm also looking for a way to get into the hidden menu of the NAC (3d Connect Nav) Peugeot. My car is a 2008, with CarPlay, Mirrorlink and Android Auto. Now compared to what I saw for the KIA, I would try to figure out if there is a chance to enter the system that is declared Linux, and find a gateway like an android virtual emulator, on which even turns android auto, to install other applications directly on the multimedia of the car. The only 2 codes we know are: 1111 1122, the first for spylogs, the second one gives us a series of info on the system, but apparently they are only legible and there is no way to get inside. In practice using the code 1122 the first time also gave me only info on the radio, but then typing in increasing order the following codes and typing 1122 again, for several times I have drawn many other info. I took pictures that I would like to share with you to find out if there is a chance to find a way.
Click to expand...
Click to collapse
First of all, does anyone know that LINUX can run Android within? Would it be possible to enter the NAC system to install Android apps?

Any progress here?
I'm also try to hack in the nac.
I scanned for open ports in Bluetooth and Wifi but all ports are closed.
Does anyone has another idea how i can get access to the system files?

The source code is published here.
https://www.groupe-psa.com/en/oss/

It's from the RCC, not the NAC.
RCC is from Bosch and the NAC from Continental.
And it's useless unless you have the login data or the schematics from the board because all ports are closed.
Maybe a secret code open the ports.
But so far only 1111 and 1122 are known.

Crunchy_Nuts said:
It's from the RCC, not the NAC.
RCC is from Bosch and the NAC from Continental.
And it's useless unless you have the login data or the schematics from the board because all ports are closed.
Maybe a secret code open the ports.
But so far only 1111 and 1122 are known.
Click to expand...
Click to collapse
According to information published on https://fccid.io/ZFW-NACEUR2. This should be the source of the NAC WAVE 2 and 3.
Excludes are sources of proprietary software.
It seems that the software developed for the RCC unit, is (partly?) used for the NAC.
The base of the OS is GENIVI. A linux based OS developed for in car systems.
https://events.static.linuxfound.or...tware updates for Linux-based IVI systems.pdf.
It is designed to prevent the hacking of the system in any way.

For those of you who want to analyze their spy logs after using code 1111, you need to install Qt (qt.io/download) and download the DLT Viewer project (github.com/GENIVI/dlt-viewer). You also need a tool to extract lz4 compressed files (e.g. github.com/lz4/lz4/releases). Once you configure everything you need to extract the .lz4 file (e.g. "1_startup_20190924_181656.dlt.lz4") which results in a .dlt file (e.g. "1_startup_20190924_181656.dlt"). You can then open this in DLT Viewer.
I assume that the Navi 5.0 is using a logger similar to the one described here: github.com/GENIVI/dlt-daemon] . Also based on the information in some of the crash reports, the Navi 5.0 seems to be using Qt apps/objects.

Unfornately I do not really know how to install all these programs.
I could install qt and visual.
But all other failed.
Can you maybe do a tutorial for that?
I would be verry thankful
Regards

i do not understand too how to install these programms , can you eplain , please?
step by step would be the best.
thanks

I'll try to detail the steps for Windows as soon as I get a chance.
I installed Qt 5.12.5 + Microsoft Visual Studio 2015. When configuring the Qt Kit, I selected no C compiler and "Microsoft Visual C++ Compiler 14.0 (x86_amd64)" as the C++ compiler. After that I was able to build and run the DLT Viewer project.
The lz4 command-line utility is pretty straight-forward. Simply run "lz4.exe <file name>.dlt.lz4" to extract the files.

That's a problem fo me, I could install qt and visual but that's all.
I do not have exe files for iz4 and for dlt I do not have too.
So if you could do a tutorial with links step by step it would be verry cool
Thanks

No answer

DLT Viewer - Step by Step for Windows
I have been busy, so it took me some time The output of DLT Viewer will probably make no sense to many people, but you can draw your own conclusion at the end. I uninstalled and re-installed everything from scratch to note down each step. This assumes that you have exported the spy logs using code 1111 and that you have placed them on your PC.
Download a tool to extract the lz4 compressed spy logs.
None of the 7-zip tools/plugins worked for me.
From the command-line you can use one of the binaries here: github.com/lz4/lz4/releases . Simply run "lz4.exe <file name>.dlt.lz4" from the command-line to extract the files.
For a GUI interface, see reboot.pro/topic/22062-lz4-compressor . Within the tool, in the VHD file field you need to select your lz4 file (e.g. "1_startup_20190924_181656.dlt.lz4"). Select the output folder in the Lz4 Folder field. Leave the LZ4 field empty. Click on the COMPRESS button to extract the file (I know, the name of the button doesn't make sense).
You should end up with a .dlt file.
Download and install Visual Studio Community Edition 2015: stackoverflow.com/questions/44290672/how-to-download-visual-studio-community-edition-2015-not-2017
During installation select Custom install and Programming Languages -> Visual C++
Download and unzip DLT Viewer: github.com/GENIVI/dlt-viewer/archive/master.zip
Download and install Qt 5.12.6: download.qt.io/official_releases/qt/5.12/5.12.6/qt-opensource-windows-x86-5.12.6.exe
During installation select the following component: Qt -> Qt 5.12.6 -> MSVC 2015 64-bit
Configure the compiler in Qt
Go to the Tools menu -> Options
Select Kits in the left pane -> Kits tab
Click on "Dekstop Qt 5.12.6 ..." under "Auto-detected"
Select for Compiler C: <No compiler>
Select for Compiler C++: Microsoft Visual C++ Compiler 14.0 (amd64)
Compile and run the DLT Viewer project
Within Qt click on Open Project and open the BuildDltViewer.pro project in the unzipped folder of DLT Viewer.
Qt will switch to the Projects page (otherwise click on Projects on the left)
For the Active Project, BuildDltViewer should be selected
Click on Configure Project on the right
Go to the Build menu -> Build Project ...
When the build is finished, go the Build menu -> Run
Go to File -> Open and open one of the .dlt files.
The DLT Viewer manual can be found here: at.projects.genivi.org/wiki/display/PROJ/DLT+Viewer+Manual
I haven't spent much time looking at the DLT Viewer output, so I cannot help anyone to decipher that. Obviously feel free to share any of your findings.

New Codes Found
Nice work, Bob.
I live in Brazil and my Citroen C4 Cactus seems to use this same unit.
I reached the "Expert Mode" pressing MENU for 10 seconds and the tried the 1111 and 1122 codes.
Here 1111 brings me up the "spy" files, that I extracted using a pendrive, lz4.exe and read with a simple text editor, that does not show the file in a structure but give a good idea that what is inside it.
1122 brings only radio information.
Some news, discovered in this interaction:
1144 disabled the system beep.
1155 enabled the system beep.
I´m just downloading the source code to have an idea on how it works.
I found some schematics at web a few months ago. I will try to recover it and post here.
It will be wondering if we can get Android Auto Wireless working with these units.
Regards,
Estefano
BobM2019 said:
I have been busy, so it took me some time The output of DLT Viewer will probably make no sense to many people, but you can draw your own conclusion at the end. I uninstalled and re-installed everything from scratch to note down each step. This assumes that you have exported the spy logs using code 1111 and that you have placed them on your PC.
Download a tool to extract the lz4 compressed spy logs.
None of the 7-zip tools/plugins worked for me.
From the command-line you can use one of the binaries here: github.com/lz4/lz4/releases . Simply run "lz4.exe <file name>.dlt.lz4" from the command-line to extract the files.
For a GUI interface, see reboot.pro/topic/22062-lz4-compressor . Within the tool, in the VHD file field you need to select your lz4 file (e.g. "1_startup_20190924_181656.dlt.lz4"). Select the output folder in the Lz4 Folder field. Leave the LZ4 field empty. Click on the COMPRESS button to extract the file (I know, the name of the button doesn't make sense).
You should end up with a .dlt file.
Download and install Visual Studio Community Edition 2015: stackoverflow.com/questions/44290672/how-to-download-visual-studio-community-edition-2015-not-2017
During installation select Custom install and Programming Languages -> Visual C++
Download and unzip DLT Viewer: github.com/GENIVI/dlt-viewer/archive/master.zip
Download and install Qt 5.12.6: download.qt.io/official_releases/qt/5.12/5.12.6/qt-opensource-windows-x86-5.12.6.exe
During installation select the following component: Qt -> Qt 5.12.6 -> MSVC 2015 64-bit
Configure the compiler in Qt
Go to the Tools menu -> Options
Select Kits in the left pane -> Kits tab
Click on "Dekstop Qt 5.12.6 ..." under "Auto-detected"
Select for Compiler C: <No compiler>
Select for Compiler C++: Microsoft Visual C++ Compiler 14.0 (amd64)
Compile and run the DLT Viewer project
Within Qt click on Open Project and open the BuildDltViewer.pro project in the unzipped folder of DLT Viewer.
Qt will switch to the Projects page (otherwise click on Projects on the left)
For the Active Project, BuildDltViewer should be selected
Click on Configure Project on the right
Go to the Build menu -> Build Project ...
When the build is finished, go the Build menu -> Run
Go to File -> Open and open one of the .dlt files.
The DLT Viewer manual can be found here: at.projects.genivi.org/wiki/display/PROJ/DLT+Viewer+Manual
I haven't spent much time looking at the DLT Viewer output, so I cannot help anyone to decipher that. Obviously feel free to share any of your findings.
Click to expand...
Click to collapse

NAC Wave 2 codes (from German PSA forum)
1111 Spy log generation
1122 Master mask
1130 Information about amplifier, battery etc
1133 Information about radio / received / freq
1134 Information on satellites and services
1135 TomTom version
1136 Information about WiFi devices
1137 current user status, temp.
1138 Linux, USB, processor utilization
1139 GPU memory load
1140 connection status WiFi, tethering, Bluetooth, rndis, ipadreesen and macadressen and much more.
1141 Connected USB devices
1142 ATB connection
1143 no information without serial connection
1144 tone becomes quieter
1145 Provider status, SMS status
1146 Download status
Hope this would help

Pretty Good work BobM2019!!!
Thank you, I will try it.
For the Swiss man:
What source is the German side for the codes?
When did they wrote these info?

MitchtheMitch said:
What source is the German side for the codes?
When did they wrote these info?
Click to expand...
Click to collapse
https://www.google.com/search?q=peugeot+nac+"1144"+"1155"

Peugeot Naceur wave 2Continental Serial Connection
With TX and Rx it is possible to get in the serial console of the head unit.
But it asks for a login and password.
Imx6x-std login:
Password:
Tried a lot of things, like root and pass.
Left pass empty but nothing works.
Anybody a clue?