The Moto E4 Plus Mediatek variant VCOM (flashing) driver for Windows is here.
How to install:
Download and extract the archive.
Disable driver signature enforcement (DSE) through cmd as administrator. Command: bcdedit /set testsigning off
For enabling DSE enter the same command in the same way replacing 'on' in place of 'off' and reboot.
Remove phone from usb.
Install the executable as administrator.
Reboot PC.
Done.
Related
In this guide I'm going to assume you know how to get SDK working. Here's the video if you don't: http://www.youtube.com/watch?v=oaNM-lt_aHw
This is in reference to Hascode's guide [http://forum.xda-developers.com/showthread.php?t=2128175]
for steps 4.5 AND BEYOND or if you just want to enter Fastboot for yourself.
1. 1. Download this: https://dl.dropbox.com/u/54456659/KFFirstAide64.zip (64 bit) OR https://dl.dropbox.com/u/54456659/KFFirstAide32.zip (32 bit)
Latest version of Java: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
Source: prokennexusa
2. Extract it to your C Drive (or primary), keep the folder name the same KFFirst AIDE (Do not change it)
3. Make a Path to that folder, as shown in the video. Instead you will put ;C:\KFFirstAide
4. Download Hashcode's files and place them in that FirstAide Folder.
5. Before going further, uninstall any previous drivers for the Kindle in Control Panel and Device Manager.
6. Install ADB Drivers found within KFFirstAide - KindleADB
7. Open up RunMe.bat and run option 11 to verify ADB is working.
8. Now run option 15 to boot into Fastboot, it may take a min.
9. Once in Fastboot, open Device Manager and update the driver, browse to C: - Program Files - Amazon - Drivers - WinUSB
10. Open CMD and type in cd C:\KFFirstAide
11. Now type in Hashcode's Fastboot lines and it should run (you can verify this because the files pushed will also show up on your Kindle)
NOTE: It's important that you do not have any ADB or Kindle drivers installed prior to installing the one in the FirstAide folder (Check Device Manager)
If you have questions, post a comment down below and I will try to answer them.
So I have Pixel C (1502W)
ADB and Fastboot work
As it boots up, I get the following:
Support API:3
Failed to open driver control: No such file or directory
Failed to open driver control: No such file or directory
Now send the package you want to apply
to device with "adb sideload <filename>"...
-----------------------------------------------------------
on PC:
s\AndroidStudioProjects\picel>adb devices
List of devices attached
6119000470 sideload
------------------------------------------------------------------------------
Have trouble knowing what image I should use.
Like to load correct OS and root the device. Any help is appreciated.
I have the latest Google driver on Windows 10 Pro. I have the latest 29.0.6 platform tools. I open a cmd prompt with admin privileges in platform tools and run "adb devices" and I get an error that I have attached. I have uninstalled and reinstalled Google driver to no avail. I have downloaded the platform tools again to make sure it was not corrupt, that didn't help. Afer I connect to the phone with usb debugging turned on it does not ask me if I want to trust the fingerprint of the computer. Can anyone give me some help? Thank you.
first attempt
Holysmoke99 said:
I have the latest Google driver on Windows 10 Pro. I have the latest 29.0.6 platform tools. I open a cmd prompt with admin privileges in platform tools and run "adb devices" and I get an error that I have attached. I have uninstalled and reinstalled Google driver to no avail. I have downloaded the platform tools again to make sure it was not corrupt, that didn't help. Afer I connect to the phone with usb debugging turned on it does not ask me if I want to trust the fingerprint of the computer. Can anyone give me some help? Thank you.
Click to expand...
Click to collapse
Download the latest:
https://developer.android.com/studio/releases/platform-tools
Unzip in a dir.
Copy following files to test dir:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
Create one .bat file in the same 'test' dir:
adbreboot.bat:
@Echo off
set PATH=%CD%;%PATH%;
adb reboot
save it .... connect your device ... and run it (if necessary with admin privileges)
Good luck
Thanks for the advice but nothing happened.
I attached the folder contents. That is correct?
second attempt
Holysmoke99 said:
Thanks for the advice but nothing happened.
I attached the folder contents. That is correct?
Click to expand...
Click to collapse
Download and extract:
https://www.uwe-sieber.de/files/devicecleanupcmd.zip
On a windows X64 machine:
copy DeviceCleanupCmd.exe from extracted x64 folder to your previous test folder (with adb.exe, AdbWinApi.dll, etc...)
set the properties of DeviceCleanupCmd.exe for all users to run as administrator
create 2 .bat files:
DeviceCleanupCmdLoad.bat:
@Echo off
set PATH=%CD%;%PATH%;
DeviceCleanupCmd.exe * -t
PAUSE
DeviceCleanupCmdRemove.bat:
@Echo off
set PATH=%CD%;%PATH%;
DeviceCleanupCmd.exe * -s
PAUSE
Run the 2 . bat files (don't connect your device yet !)
Follow the instructions on the messages: ex: 'press any key to close': press any key, etc...
After that:
1. connect your device and run adbreboot.bat... see what happens
2. if no luck, run DeviceCleanupCmdLoad.bat and DeviceCleanupCmdRemove.bat again : REBOOT your windows, connect your device and run adbreboot.bat... see what happens
Good luck
It still did not work. Thanks again.
third attempt
Holysmoke99 said:
It still did not work. Thanks again.
Click to expand...
Click to collapse
- Disconnect USB between PC and device
- On device use "Revoke USB debugging authorizations" in "Developer Options"
- Reboot device
- Reconnect the device to the PC
- You should see now: the fingerprint of the computer ... allow it!
- run adbreboot.bat... see what happens
Thanks again, I have tried to revoke authorizations all day to no avail. I tried all the steps above and added revoking but it still won't give me option to trust fingerprint.
Holysmoke99 said:
Thanks again, I have tried to revoke authorizations all day to no avail. I tried all the steps above and added revoking but it still won't give me option to trust fingerprint.
Click to expand...
Click to collapse
last attempt
fully uninstall magisk (root)
update to the latest OTA firmware of google....
revoke the authorizations again
I had altered boot.img to obtain root. This morning the phone was running very slow so I did a factory reset. I updated to the latest OTA. Is magisk still on the phone?
After installing 15 seconds ADB Installer v1.4.3 your batch file worked and brought up the prompt to accept fingerprint!!!!!!!!! Thanks so much for taking the time to help me!
Holysmoke99 said:
I had altered boot.img to obtain root. This morning the phone was running very slow so I did a factory reset. I updated to the latest OTA. Is magisk still on the phone?
Click to expand...
Click to collapse
I always complete remove magisk before installing the latest OTA ... just in case
biontx said:
I always complete remove magisk before installing the latest OTA ... just in case
Click to expand...
Click to collapse
do you have to alter boot.img each time you install OTA to keep root?
Holysmoke99 said:
do you have to alter boot.img each time you install OTA to keep root?
Click to expand...
Click to collapse
Each time before I install an OTA I remove root and magisk
Download the latest factory image for you device:
https://developers.google.com/android/images#bonito
Unzip it and copy boot.img to a dir on your device
Reinstall magisk apk with the permissions (my favorite: Magisk v20.4: MagiskManager-v7.5.1.apk)
https://github.com/topjohnwu/Magisk
Patch your boot.img with MagiskManager-v7.5.1.apk
Copy your magisk patched . img to your computer to a dir with: adb.exe; AdbWinApi.dll;AdbWinUsbApi.dll;fastboot.exe
Create 2 .bat files:
0001fastbootmagicpatched.bat:
@Echo off
set PATH=%CD%;%PATH%;
fastboot boot <FullPathTo your magisk patched img file>\magiskpatched.img
example:
fastboot boot D:\PROJECTS\NOUGAT\PIXEL3A\magisk\20200405Stable\magiskpatchedboot\magiskpatched.img
0002fastbootflashbootmagicpatched.bat:
@Echo off
set PATH=%CD%;%PATH%;
fastboot flash boot <FullPathTo your magisk patched img file>\magiskpatched.img
example:
fastboot flash boot D:\PROJECTS\NOUGAT\PIXEL3A\magisk\20200405Stable\magiskpatchedboot\magiskpatched.img
Put your device into bootloader.
Connect your device and run 0001fastbootmagicpatched.bat
Disconnect your device.
After a full start of your device, don't start any other app... put your device into bootloader again.
Connect your device and run 0002fastbootflashbootmagicpatched.bat
After de cmd window ends on your computer, press start on your device
Once fully started, all should be well on your device.
Start magisk app and adapt to your needs
System Power app
@Holysmoke99
System Power app (see attachment): could you test this app please:
Preview: see pictures in attachment.
Made for android 10 or higher.
Root is needed.
Contains a tile to be added in your quick settings: makes it more easy to take a screenshot.
Contains the following functions:
- Power off
- Restart
- Recovery
- Bootloader
- Torch (toggle torch: added v 3.1 b 30013)
- Screenshot
- Screen off
Any comments appreciated
So I have the drivers
usb_driver_r13-windows: from google they do not work and as far as I can see they are the latest
They are from 7/23/2020 but they are the latest Google provides.
I have installed OP9P_Default_Drivers, do not help at all either
I also downloaded: https://oneplusdriver.com/download-oneplus-driver, again no help in fastboot
Now they are in C:\Program Files (x86)\OnePlus USB Drivers
however trying to point here to use this driver fails "The hash for the file is not porsent ..." and it refuses to use this driver.
tool_amd64, can not install thr driver either as it also fails to install, the lost is clean:
Code:
OnePlus USB Drivers install...
Get system info ...
CPU architecture: AMD64
Operater System: Windows 8
Install drivers command:
tool_amd64.exe /PATH . /LM /SW
mtp & rndis drivers not need install.
set adb environment...
find ANDROID HOME = C:\Android
ANDROID HOME already exist!
adb path already exist in path!
check system environment...
system32 is not in USER path
system32 path already exist in path!
install drivers success!
I also tried: L2 drivers which should not and do not work.
Simply put I'm unable to locate any driver that supports "USB\VID_18D1&PID_D00D"
I'm un sure how anyone is doing anything in fastboot, if there is not a driver that supports this ID, but based on multiple Google searching I'm not locating any others that I'd even trust to try, or that would make any sense to try.
So at this point I'm completely blocked, from unlocking the phone (step 0 for me), as there is no driver that is supported for fastboot and the One Plus 9 Pro and Windows 10 20H2 with the latest patches from 05/2021, as something seems very wrong with the one plus driver.
Very unhappy right now with One Plus!
ERIC
Win 10 right...I had fastboot issues and found a thread eventually that walked me through booting win 10 in a way that gave me the option to disable security checks on driver's, and then I was able to install the OP driver I needed and voila fastboot could see my device.
sbcdave said:
Win 10 right...I had fastboot issues and found a thread eventually that walked me through booting win 10 in a way that gave me the option to disable security checks on driver's, and then I was able to install the OP driver I needed and voila fastboot could see my device.
Click to expand...
Click to collapse
That is not a safe thing to do, it is on One Plus to provide a valid signed driver, right now I'm using a Linux VM as fastboot and linux = however oneplus needs a valid WIndows 10 driver that is signed
egandt said:
So I have the drivers
usb_driver_r13-windows: from google they do not work and as far as I can see they are the latest
They are from 7/23/2020 but they are the latest Google provides.
I have installed OP9P_Default_Drivers, do not help at all either
I also downloaded: https://oneplusdriver.com/download-oneplus-driver, again no help in fastboot
Now they are in C:\Program Files (x86)\OnePlus USB Drivers
however trying to point here to use this driver fails "The hash for the file is not porsent ..." and it refuses to use this driver.
tool_amd64, can not install thr driver either as it also fails to install, the lost is clean:
Code:
OnePlus USB Drivers install...
Get system info ...
CPU architecture: AMD64
Operater System: Windows 8
Install drivers command:
tool_amd64.exe /PATH . /LM /SW
mtp & rndis drivers not need install.
set adb environment...
find ANDROID HOME = C:\Android
ANDROID HOME already exist!
adb path already exist in path!
check system environment...
system32 is not in USER path
system32 path already exist in path!
install drivers success!
I also tried: L2 drivers which should not and do not work.
Simply put I'm unable to locate any driver that supports "USB\VID_18D1&PID_D00D"
I'm un sure how anyone is doing anything in fastboot, if there is not a driver that supports this ID, but based on multiple Google searching I'm not locating any others that I'd even trust to try, or that would make any sense to try.
So at this point I'm completely blocked, from unlocking the phone (step 0 for me), as there is no driver that is supported for fastboot and the One Plus 9 Pro and Windows 10 20H2 with the latest patches from 05/2021, as something seems very wrong with the one plus driver.
Very unhappy right now with One Plus!
ERIC
Click to expand...
Click to collapse
Check your windows updates section, I was having the same issue. Was available through there for me, no problems after that.
egandt said:
That is not a safe thing to do, it is on One Plus to provide a valid signed driver, right now I'm using a Linux VM as fastboot and linux = however oneplus needs a valid WIndows 10 driver that is signed
Click to expand...
Click to collapse
I'm not sure this is valid. Would Windows 10 accept the driver if it was signed with LetsEncrypt certs... I doubt it.
Go to Windows Update -> Optional Updates.
You'll find the fastboot and adb drivers there.
If you're using a USB dock, try putting the USB cable directly into your PC instead, I've seen that fix problems where the phone isn't being seen
Reli4nth said:
Go to Windows Update -> Optional Updates.
Click to expand...
Click to collapse
worked so much easier than messing with external questionable drivers.
We have to disable the signature checks on windows. Run CMD as Administrator and paste the below codes and Hit Enter. Reboot your PC after doing this.
bcdedit.exe -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Now try to install the one plus drivers again, and it should be done in 5 mins. After this windows will identify your device in fastboot mode.
Reli4nth said:
Go to Windows Update -> Optional Updates.
You'll find the fastboot and adb drivers there.
Click to expand...
Click to collapse
hey, where did you find the fastboot and adb drivers? When i enter "optional updates" in the search bar i can only see a very limited number of updates.
thx
EDIT: found out my problem was the missing driver. The Driver CD showed no files so i installed a driver from here: https://www.technobuzz.net/oneplus-6-usb-drivers/
Deavtivated the signature with the help of this
bcdedit.exe -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Now i can find my phone in fastboot.
My only hope is that the installed driver was legit. Couldnt find an official version.. :S
Yikes....forgot there was a time I didn't know this.
Direct from Google (no "questionable about 'em, they are Google's own tools/drivers) -
ADB and Fastboot:
SDK Tools release notes | Android Studio | Android Developers
Learn about the Android SDK Tools component for the Android SDK.
developer.android.com
(Set PATH in Envorinment Variables to whatever folder you extract these to in order to have access to adb/fastboot in any folder using command-prompt.)
USB-Drivers (ADB fastboot):
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
(extract, right-click on android_winusb.inf file and select "install", go to Device Manager, right click "Android" device and update driver - choose "pick from list", Android, Bootloader - for fastboot/bootloader, obviously)
Download the SDK tools and update the ADB/Fasboot folder with every release of Android to try and keep it up to date. The USB drivers have worked for every device I have had to use them on.
The Hero SP-001 is a free Lifeline phone from Access Wireless made by Shenzhen Eternity Technology Co., Ltd.
You must Unlock the phone before Rooting it. The Steps for both are provided below.
[Unlock Phone]
****Be aware that you will lose all user data when you unlock bootloader***
1) Unlock Developer options
2) Enable OEM unlocking from Dev options
3) Enable Android Debugging from Dev options.
4) Connect phone to computer
5) From command line type 'adb devices'
6) From command line type 'adb reboot fastboot'
7) From command line type 'fastboot devices'
8) From command line type 'fastboot flashing unlock'
9) Press the volume up button to accept unlocking warning
10) From command line type 'fastboot reboot'
You will see a warning saying it is unlocked everytime you reboot phone.
**EDIT** You can use the RE Live Distro mentioned below to do the above commands if you dont want to fuss with installing adbd on your computer.
----------------------------------------------------------------------------------
[Root+Magisk]
If your'e on Windows you will have to download and install python and git and MTKClient and UsbDK 64 and abdb. I'm not going to get into how to do all that because there is an Ubuntu image tailored made for all MTK based devices. It has all the programs installed. it is called RE Live made by viperbjk . I recommend doing it this way especially if you have any other devices using MTK chips.
Download Re Live DVD V3. The account credentials are Username: user Password: user
You can create the bootable usb thumb drive with Rufus if you're using windows.
The following steps are based on using the Re Live DVD:
***Your phone must be unlocked before you can root it. *****
1) Power off the phone and do not have it connected to the computer.
2) Boot up RE Live and type 'user' at the login screen.
3) Double-click the 'MTK' icon on the desktop.
4) Plug the USB cable into the computer. Do not plug it into the phone.
5) In the terminal type: python mtk r boot,vbmeta boot.img,vbmeta.img
6) When you see "Preloader - Status: waiting for PreLoader VCOM, please connect mobile" in the terminal you will hold the down volume button and plug the cable into the phone. Let go of the button a second or two after you connect phone. It will show you a progress bar as it downloads the 2 images you need.
7) Unplug the phone and power it on.
8) from that same terminal screen type: wget https://raw.githubusercontent.com/v...9e22fa276698f6c03bc1168df2c10/app-release.apk
or use the shortened url if you dont want to type all that: wget https://tinyurl.com/magiskmtk
9) plug the phone and type in the terminal: adb install release-apk [ look at the phone and accept auth rsa request on mobile screen so it can install the app.]
10) in the terminal type: adb push boot.img /sdcard/Download
11) Start magisk, tap on Install, select boot.img from /sdcard/Download.
12) in the terminal type: adb shell ls /sdcard/Download [You should see the boot.img file and another file name 'magisk_patched.something.something.img']
13) in the terminal type: adb shell mv [name of the patched file] boot.patched
14) in the terminal type: adb pull /sdcard/Download/boot.patched
15) Unplug the phone and turn it off (keep the usb plugged into the computer)
16) in the terminal type: python mtk w boot,vbmeta boot.patched,vbmeta.img.empty
17) When you see "Preloader - Satus: waiting..." hold the volume down button and connect the phone. release button when u see it connect and let it do its thing.
18) Unplug phone and power it on. Phone will now be rooted.