Hi. So When I installed JIO TV Application on my Windows 11 Laptop, it did OTP verification successfully but after that it Crashed Stating that "The Device Does Not Support Required DRM Scheme".How to solve this?
You likely tripped SafetyNet. This can occur when you modify the OS.
Do you have an error code or more info on what could have triggered this?
The problem is that DRM requires DMA, which is much faster than IPC/sockets. I think in order to get it to work right with DMA (and without rewriting your X/Wayland clients, you would need to have NT drivers that were directly aware of WSL.
You must turn on developer mode in wsa and the drm issue will fix...it works for me....but jio tv still crashing when try to change channel (most of the time)...I don't know how to fix ot
dwaparr said:
Hi. So When I installed JIO TV Application on my Windows 11 Laptop, it did OTP verification successfully but after that it Crashed Stating that "The Device Does Not Support Required DRM Scheme".How to solve this?
Click to expand...
Click to collapse
It aims to protect digital content from piracy. You can watch DRM protected content if you have a device that supports DRM. If your device does not support DRM, you could face video viewing issues while watching DRM protected content. If you're watching on an Android phone.
Related
Dear All,
My application requires to to send an ARP(Adress Resolution protocol ) request from the Android application layer.
As ARP is based on RAW Sockets,with the initial investigation, It is shown that RAW sockets are not accessible from Java or through any android API's.
I also tried to send a request via a native language, but this requires super user permission. Rooting a phone to run this is not a feasible option as this is just an application development.
Please let us know if there any way to send an ARP request from Android application without rooting a phone.
Thanks in Advance,
I am facing also same problem. Do you got answer?
Most likely not as this is protected info.
I've seen some threads about accessing the WhatsApp messages backup database files on iPhone, Android and older Windows Phone versions (7.x). However, none of the methods seem to be compatible with the WhatsApp messages backup database file found on Windows Phone 8.1. I am looking for a way to either extract/decrypt or restore an older messages backup database. Tried so far:
- Place messages.db file on SD card and reinstall WhatsApp. WhatsApp does NOT find the backup on installation. It only restores the most recent chats (not the ones from the backup file)
- Tried available tools for iPhone/Android (Python scripts with crypto 5/7/8). Database format is incompatible
- Tried opening the database file directly in Microsoft Access, SQLite Browser. Unrecognized file format
- Tried the Zune/WP Device Manager approach. Seems to work only with Windows Phone 7.x, Windows Phone 8 is not seen by the tool
- Tried Windows Phone Power Tools to access Isolated Storage for the WhatsApp app, but access to an apps isolated storage is not possible in Windows Phone 8 anymore.
- Tried the WhatsApp Xtractor, but it contains the same iPhone/Android python scripts that don't work with the Windows Phone version
- Even tried asking WhatsApp support directly, but they have not given any response yet
Can any WhatsApp / encryption wizard please help me out. I am more than willing to reward/tip you for it if the solution works!
i have the same problem ,pls pls pls tell me about the solution thx
Given that you already enabled full FS access on your phone or have control over an app wich has the ID_CAP_OEMPUBLICDIRECTORY capability, you can extract the unencrypted sqlite database from C:\Data\SharedData\OEM\Public\WhatsApp.
The structure of the database is quite complex (I suppose it grew over the years), but not too hard to understand.
However, I have no experience in using this mechanism as a backup/restore solution.
Source: blackhat . com/docs/ldn-15/materials/london-15-DeFulgentis-Witchcraft-For-Windows-Phone-Breakers.pdf page 68f
Sorry for broken link, I'm a new member.
I realize this is a pity, I want the Microsoft support seriously and updating applications
If you do not want to unlock / flash your phone in order to enable the full FS unlock, you can try the hack as shown in the Blackhat slides posted above.
It works by replacing an apps' core files with your own, but keeping the capability restrictions of the original app. (Use http://forum.xda-developers.com/win...p-customwpsystem-patch-xaps-wpsystem-t2975419 for example)
So just target an app with ID_CAP_OEMPUBLICDIRECTORY, deploy your custom payload and use it to copy the WhatsApp files somewhere.
Given the full FS access, is there any way to access the Whatsapp key file like on Android. That's what you would need to access the backup files instead of the unencrypted current message database, which is easily opened as SQLite database?
Hello ... I'm new here ... just wondering if there is any answer to this question ... I know it's not a recent discussion, but I really need some help from you guys. I have a wp where whatsapp is installed, but it's asking for verification and I dont have no more the sim card related to that account ... I saw chats, but then I made a huge mistake (opened whatsapp while I was online) and now I cannot access to those anymore ... I have messages.db but I'm unable to retrieve the key to decrypt that ... there are tons of posts about similar issue on android or IOS, but I need the same for WP ... is it something someone can drive me through? Thanks a lot in advance
If your phone has the Full-FS-Unlock enabled you can get the unencrypted databases at C:\Data\Users\DefApps\APPDATA\Local\Packages\5319275A.WhatsApp_cv1g1gvanyjgm\LocalState (or similar package name).
Or you can get unencrypted backups from C:\Data\SharedData\OEM\Public\WhatsApp
Or you can use a interop-unlocked File Manager App
jumpz said:
If your phone has the Full-FS-Unlock enabled you can get the unencrypted databases at C:\Data\Users\DefApps\APPDATA\Local\Packages\5319275A.WhatsApp_cv1g1gvanyjgm\LocalState (or similar package name).
Or you can get unencrypted backups from C:\Data\SharedData\OEM\Public\WhatsApp
Or you can use a interop-unlocked File Manager App
Click to expand...
Click to collapse
The files in C:\Data\SharedData\OEM\Public\WhatsApp seem to be encrypted as well … Or can you just not open them with a standard SQLite viewer?
weaselmc said:
The files in C:\Data\SharedData\OEM\Public\WhatsApp seem to be encrypted as well … Or can you just not open them with a standard SQLite viewer?
Click to expand...
Click to collapse
No, these files are indeed encrypted.
The winwazzapmigrator software did a good job migrating my database to a new android phone.
Tool to access file system on Windows 8.1 mobile
jumpz said:
If your phone has the Full-FS-Unlock enabled you can get the unencrypted databases at C:\Data\Users\DefApps\APPDATA\Local\Packages\5319275A.WhatsApp_cv1g1gvanyjgm\LocalState (or similar package name).
Or you can get unencrypted backups from C:\Data\SharedData\OEM\Public\WhatsApp
Or you can use a interop-unlocked File Manager App
Click to expand...
Click to collapse
Can anyone help me with a tool to access the file system where app files are stored on a windows 8.1 mobile?
me too
PritiM said:
Can anyone help me with a tool to access the file system where app files are stored on a windows 8.1 mobile?
Click to expand...
Click to collapse
I do have the same request...
Dear all,
I'm searching for some help regarding system certificates on Android.
First of all, a little bit of context : I'm in charge of the migration of mobile devices from one Airwatch server to another. All devices are managed by MDM (Airwatch MDM Agent) that allows deployment of configuration profiles and apps. One of those profiles is called "CertAuth" and pushes some certificates that are needed to access internal ressources.
A few months ago, we have discoverd that one of the system certificates (Thawte Primary Root G3) was missing on some devices, mainly old versions of Android.
So we decided to push this certificate through the "CertAuth" profile.
Now the problem whith that method is that once the devices are unenrolled from the first server, profile "CertAuth", all corporate content and apps are removed (normal behavior). As Thawte Primary Root G3 certificate is part of the system certificates, it cannot be removed. So it is simply disabled.
This certificate is needed to access the target server, so once devices try to enroll, they receive some error message "cannot connect to host". Connection is simply refused due to the disabled Thawte G3.
Of course it can be manually enabled, but as you all may know, basic users are not always able to find the correct option in the device settings...
So (finally) my question is : is there any way to remotely enable this system certificate (little swich OFF/ON) in order to void manual action on more than 5000 devices?
By using a script or something that would be deployed on devices as third-party content/not removable content?
Recently, some users have said that they are unable to use Multi-screen Collaboration after installing certain applications on their laptop. Whenever this occurs, a dialog box pops up indicating that the hardware decoder is faulty, and that Multi-screen Collaboration does not work. Even restarting the laptop multiple times does not resolve the issue.
What went wrong?
First, let's take a look at the two main causes of this issue.
The first is the launching of certain third-party applications using the administrator permission, which causes the dynamic-link library (DLL) name of the operating system under the path (C:\windows\system32) to be modified, which can affect the running of Multi-screen Collaboration, and the system's video player.
The second involves the potentially faulty source mirror, after installing Windows system on your own, on a Linux system laptop.
How can this issue be resolved?
To use Multi-screen Collaboration, simply perform the following steps:
1. Set the preferred graphics processor to auto-select in the NVIDIA control panel.
2. If you are still unable to use Multi-screen Collaboration.
Check whether you have modified "msmpeg2vdec.dll" and "msmpeg2adec.dll" to "msmpeg2vdec.dll.bak" and "msmpeg2adec.dll.bak" under the path "C:\windows\system32".
3. If yes, delete the suffix bak.
Press the Win key and enter "CMD" in the search box on the taskbar, and right-click Command Prompt and select to run it as the administrator.
Enter the following commands:
regsvr32 C:\Windows\System32\msmpeg2vdec.dll
regsvr32 C:\Windows\System32\msmpeg2adec.dll
regsvr32C:\Windows\System32\evr.dll
4. If you still cannot resolve this issue, check whether this issue happens due to the second cause. It is recommended that you download the official source mirror from MSDN, and confirm that you can use this feature. Alternatively, display CMD and enter "winver" in the search box to check your system version. If your system version is lower than 1903, update your Windows system. If this issue is still unresolved, re-install the system.
I hope that you found this helpful. If you're still having difficulty using Multi-screen Collaboration, feel free to contact me!
More questions to ask? you will definately get some help here
Can you describe your problem in detail?
Freemind R said:
Can you describe your problem in detail?
Click to expand...
Click to collapse
So I've encountered the situation (and heard people saying as well) that the multi-screen collaboration does not work well after installing certain applications: a dialog box might pop up indicating that the hardware decoder is faulty, and that Multi-screen Collaboration does not work. Even restarting the laptop multiple times does not resolve the issue.
My post here is meant to provide a possible solution.
I'm building an application that requires the use of the depth sensor on my Samsung Galaxy A80. However it seems like it's impossible to access it through Camera2 and ARCore. I asked Samsung directly and the tech support guys best guess was that Samsung has locked it from being used by third parties.
I rooted my phone and started digging through the file system and eventually found a file called 'com.samsung.sensor.imx316.so' located in /vendor/lib/camera (imx316 is the depth sensor). There are also some similar files that ends in '.bin', but .so files seems to be runnable code if I understood the google results correctly.
That file has the same name as the sensor I can't seem to access. Can this file be used somehow? Can I run it in my own app to get access to the depth data? And if not, there should be a way of getting that data right? I mean, it obviously exists somewhere in the phone since pre-installed apps are using it, and a rooted phone has access to everything?
Did you check REQUEST_AVAILABLE_CAPABILITIES_DEPTH_OUTPUT? How do you know it's impossible?
Most likely you need to reverse engineer the Camera app from your phone.
Your app can call com.samsung.sensor.imx316.so , it's really "just" a linux elf library.
The problem you face is the exported routines from the library, you won't really know
1) the parameters to the functions inside the library
2) any specific order to call functions inside the library i.e. like an init function first , release memory last...
You need to disassemble / reverse engineer the library to make some sense of it (see ghidra / radare2/ ida pro etc ).
Use strace on the current process/app which uses the library to make some sense of the order of calls into the library.
The depth data will be coming from a kernel level driver, you can likely obtain the Samsung kernel source and the driver source should be there. Then it's up to you whether you can make user space library/code to read what the driver exposes. The kernel driver source code will have an uapi header file to investigate.
idk if it helps but i used for a Huawei P30 Pro this https://github.com/Nufflee/tof-camera