Install Via USB not working - on 7.0 device - android-usb

I have red mi note 4 devices after update device with miui version 9 attempt to enable installation via application via USB, it doesn't work and shows "This device is temporarily restricted". The solution I found didn't work.
Without that feature, I can't develop an application.
Model redmi note 4
miui version: 9.0.5.0

I faced the same issue. I was not able to enable Install Via USB option, however, I found a solution that actually worked.
Here are the steps to enable it.
Install PlexVPN app on your mobile phone
Open PlexVPN then set VPN to China (e.g China-Shanghai) and connect
Go to Developer Options and enable Install Via USB option
Enjoy :)

For me, the only solution that worked is to toggle on OEM unlocking
Only then I could enable Install via USB and other options that previously restricted

yes the solution is VPN you need chinese serevr for proxy , should is buy vpn or i can do it for free , follow the links below
i faced the problem before so here is answer

Related

Uninstall H2O in Windows 10

As my plan was to exclusively use H2O's web GUI, I installed H2O following these steps: https://docs.h2o.ai/h2o/latest-stable/h2o-docs/downloading.html#download-and-run-from-the-command-line. I got a Windows Firewall popup asking me to allow h2o to communicate on public networks (I was connected to a public network at that moment). I accepted.
Now I would like to uninstall it, but I have not been able to find info about it. Also, it does not appear in the list of installed applications in Windows 10 settings. I have not found any rules related to H2O or port 54321 in Windows firewall either.
Please note:
This is the first time I install programs this way.
I do not have Python or R installed in my computer, as it was not necessary for using H2O's web GUI.
Uninstalling a simply a matter of deleting the H2O jar file in your case.
To my knowledge Windows will only open the port for the given piece of software. Once you remove H2O from your computer the firewall rule will no longer apply.
This is more of a Windows-firewall question rather than H2O question, so please take my answer with a grain of salt.

Flashing firmware Google Enterprise Edition 2

My GEE2 is currently running on version OPM1.190831.007, and I can't find a way to get a more recent version running. I've tried the flashing tool and manual flashing, but both methods came with their own issues. I'll give them below:
Flashing tool: I get either a 'device already in use' connection error or the device is offline. This besides the more common message that the flashing tool has some problems on windows sometimes, and that I should try refreshing the webpage.
Manual flashing: once I have given the adb reboot-bootloader command, the fastboot devices command won't recognize the device (listed as ???????? instead of the device name/number) or it will be offline. As a result, the commands that should be given afterwards according to the Readme file don't work.
I have the adb debugger from the Android Studio SDK platform-tools folder, so I updated the driver software of the GEE2 with the use of that folder initially. Afterwards I tried installing other adb software as well but that didn't help either.
I have also tried a couple of the simpler solutions, as unplugging and plugging, refreshing the site, using another computer, using another internet browser, deinstallation of the driver software, a factory reset of the GEE2, installing less recent firmware instead of the latest. None of these things changed the outcome.
Any suggestions would be highly appreciated!
Firstly, check if you have enabled developer options on EE2.
I had a hard time flashing it on Windows due to driver issues. My Android studio or ADB had no problem deploying apps to EE2, but the fastboot never worked. I ended up flashing it on a Mac using brew installed adb.
I had similar issues with Windows, the driver, and fastboot not working using the flash tool. I was told by support to use a USB 2.0 port. I used a Mac with USB 2.0 to flash it and it was successful.
There's a flaw with the instructions on google glass firmware update - for Windows only, there's a USB driver you need that is glass-specific which isn't mentioned anywhere on the page. I can't even find the page where I found that out right now and I know what I'm looking for. Which isn't very helpful.
The best I can give you is a link to this installer tool might sort out your problem judging this reddit post.
If that doesn't work, use a mac or linux.

VMWare Remote Console not showing any GUI Dialog on MacOS Mojave

Installed VMWare Remote Console 10.0.4 (latest as of writing this) on MacOS Mojave 10.14.3. installation went well, but running the app, nothing is shown on the Mac. seen some unanswered similar questions on VMWare forum here and added my question here. Have anyone seen the same issue and have a solution?
I may have sound something - when i go to a vSphere VM, i have two options: 'Launch Web Console' or 'Launch Remote Console' - if i click the latter, i get the application to open with the UI displaying as it should. so, unlike VMWare Horizon, Player and others, here it seems you need to connect to the VM first via browser, to open the desktop client. weird choice from VMware in my mind, but still some solution. See image below

Installing AD and MSExchange 2016 in AWS EC2

I am trying to install an MSExchange 2016 in an EC2 instance from scratch without success. By from scratch, I mean I start from a new EC2 instance without any AD yet installed.
I am not very familial with Windows Server. I got a lot of problem during the installation. By digging the web, I fixed a lot of them, but I think there is something I miss to succeed in my installation. Any help would be greatly appreciated
Here is the procedure I followed:
I created an EC2 Windows Server 2012RC2 instance
I created a simple Active Directory in AWS.
I provided the AD DNS to my Windows Server (via Network and Sharing Center, properties of Internet Protocol v4)
I joined the server into that AD (Via Control Panel > System and Security > System, change computer workgroup to the domain defined in my AWS Simple AD)
Restart computer
Log into the server as Administrator, with the AD domain
Download Exchange from here
Set-up the active directory, as in this procedure: https://judeperera.wordpress.com/2015/07/24/step-by-step-guide-for-installing-exchange-server-2016-preview/
The Step 4.1. of that procedure indicates to execute the following code
Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
When I execute it, I get the following error:
I do not understand what I need to do/fix to continue the installation.
Thanks in advance for your help!
The issue you are encountering is that Simple Directory is not an Active Directory product, it is powered by Samba v4. What you need is to setup a Microsoft Active Directory (Enterprise Edition) or Microsoft AD, which is powered by Windows Server 2012 R2. The Simple AD is powered by Samba v4 and is simply Active Directory compatible but does not support the added schema features which are needed by Exchange Server 2016.
The other option is to back away from hosting your own instance of Exchange server and instead take a look at AWS WorkMail. It is an exchange like service which supports active sync with Outlook 2007+ and all current mobile smart devices such as Android and iOS. I currently use this and it took a lot of the headache out of managing my own mail server as the complexities are offloaded to the AWS environment and all you need to do it add mail accounts and group addresses.
Either option should solve your issue.

virtualbox - virtualization is enabled but not working

Ok, I have the most recent version of virtualbox installed, my computer (HP) has an AMD A10, 64bit Windows 10 OS and 6Gb RAM.
I created a virtual machine with Windows 7, there I wanted to create a new virtual machine (a VM2 in a VM1), but I cant run it because I have no virtualization enabled in the VM1.
ok, so I checked the VM1 configuration and the virtualization is enabled in the virtualbox settings. I've tried with all the Paravirtualization interfaces and always having the Hardware Virtualization enabled (VT-x and AMD-V).
I really don't know why this is happening if this is all suposed to be enabled and there arent documentations of similar issues.
I tried changing the number of CPUs used by the VM1 and all the interfaces.
I seach for 2 days and nothing worked for me.. then i find the solution:
The problem is in Windows 10... u need to disable Hyper-V Manager ...
1) make sure in your BIOS cpu virtualization is enable.
2) open your CMD as administrator
3) in your desktop folder type bcdedit and look for hypervisorlaunchtype in the bottom ... if it is Auto or enable we need to disable it !!!!!!
See this picture
4) type in your cmd bcdedit /set hypervisorlaunchtype off
5) Restart your OS and be happy !!!
i know this is a old question ... but for everyone who have a similar problem i hope it helps !!
Turn off the core isolation security provided in the Windows Defender Security Centre.
I found that enabling it turn off your Intel Virtualization technology feature while it is enabled in BIOS.
Steps to follow:
1. Go to Windows Defender Security Centre.
2. Search for Device Security in the left Panel and click on it.
3. Now click on core isolation.
4. Turn off the memory intergrity security.
If it didnt turn off and show (This is managed by your device Administrator) then follow the steps by searching on google.
You may need to download a file and enter into registry to turn it Off. Just google it.
The answer is correct, however there is something worth mentioning:
Usually the Hyper-V Manager is enabled by Docker (Docker runs on top of HV Manager), in my case it only worked after :
Removing Docker
dism.exe /Online /Disable-Feature:Microsoft-Hyper-V
the command line will ask you to restart, then you will able to run VX images!
In my case, my os is windows 10, I enabled virtualization VTx and Vtd in BIOS, but it didn't work. After seaching online, I sovled this problem. Hope this can help people.
Press Windows key + X and select "Apps and Features".
Then click "Programs and Features" link.
Then click the "Turn Windows features on or off" link on the left pane.
Locate "Virtual Machine Plateform" option and check it.
(These two steps I'm not sure : Locate "Hyper-V" and "Windows Hypervisor Plateform" option and unmark them.)
Click OK to save the changes and reboot.
Below is the screenshot:
enable Virtualization
And you can check if it is working fine in task manager, in the performance tab you can see whether the virtualization enabled or not.