Motorola drivers not installed for moto g4 plus - Moto G4 Plus Questions & Answers

I want to unlock my bootloader of moto g4 plus but there is many hurdles which I face.
First I switch on USB debugging and OEM unlocking ,then I installed minimal adb and fast boot.exe setup and move folder to c directory,than I connect my mobile in bootloader mode and login to Motorola page and download moto device manager ,than I go to minimal adb/fast boot folder and click shift+ right click and open command prompt and type fast boot devices but I show one comment,<where my device> now what to do?

keval3492 said:
I want to unlock my bootloader of moto g4 plus but there is many hurdles which I face.
First I switch on USB debugging and OEM unlocking ,then I installed minimal adb and fast boot.exe setup and move folder to c directory,than I connect my mobile in bootloader mode and login to Motorola page and download moto device manager ,than I go to minimal adb/fast boot folder and click shift+ right click and open command prompt and type fast boot devices but I show one comment,<where my device> now what to do?
Click to expand...
Click to collapse
I recommend to follow this guide https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
When your device isn't recognized by your pc you need to check if any firewall, antivirus or the driver signature verification prevents your device from being recognized. Also make sure that you reboot your pc after the installation of the Motorola drivers.

Thanks man !! But in thread which you send is not help me untill I unlock my phone.

keval3492 said:
Thanks man !! But in thread which you send is not help me untill I unlock my phone.
Click to expand...
Click to collapse
Sure, in the first step: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a otherwise please explain where you stuck when it's not the drivers?

In folder called mfastboot I click shift+ right click for open command prompt window.at this time my phone is connected with PC in bootloader mode and I installed moto device manager from moto website.
According to step 3( for unlocking bootloader in moto website) I type in command prompt fastboot oem get_unlock_data and press enter but I found this-<waiting for device>.
So, what can I do???

keval3492 said:
In folder called mfastboot I click shift+ right click for open command prompt window.at this time my phone is connected with PC in bootloader mode and I installed moto device manager from moto website.
According to step 3( for unlocking bootloader in moto website) I type in command prompt fastboot oem get_unlock_data and press enter but I found this-<waiting for device>.
So, what can I do???
Click to expand...
Click to collapse
Type "fastboot devices" when connected to the PC. If it shows your serial number of your phone then ok. If not, problems I mentioned before should be checked at your end.

I enter fastboot devices and again it shown <where my device> ,I reboot PC and also check but again it shown <where my device>.
My friend suggest that Motorola driver not installed properly ,so uninstall it first and install again ,and go to device manager and if yellow mark is shown then definitely driver is not installed ,but he not give any further information about it , because he didn't know. It shows , fastboot Athens 16_mps with yellow mark in device manager .

keval3492 said:
I enter fastboot devices and again it shown <where my device> ,I reboot PC and also check but again it shown <where my device>.
My friend suggest that Motorola driver not installed properly ,so uninstall it first and install again ,and go to device manager and if yellow mark is shown then definitely driver is not installed ,but he not give any further information about it , because he didn't know. It shows , fastboot Athens 16_mps with yellow mark in device manager .
Click to expand...
Click to collapse
Have you checked firewall and antivirus to be disabled?
You can also provide the whole console output here to get better overview of your errors :good:

Actually I don't have PC / laptop ,so for unlocking bootloader I was go to my friend' home and use laptop of him and there is disable firewall as you mentioned.
So ,now I am at my home ,so actually I can't show you actual process of laptop ,I was telling you what is happening to me ,if any solution is find then I will go to his house ,and process unlocking bootloader.

keval3492 said:
Actually I don't have PC / laptop ,so for unlocking bootloader I was go to my friend' home and use laptop of him and there is disable firewall as you mentioned.
So ,now I am at my home ,so actually I can't show you actual process of laptop ,I was telling you what is happening to me ,if any solution is find then I will go to his house ,and process unlocking bootloader.
Click to expand...
Click to collapse
Oh, nice to know...
Unless you did not provide an console output its hard to help. Additional you need to make sure that "fastboot devices" displays the serial number, if it doesn't, you need to check firewall, driver signature verification, antivirus etc etc on the PC of your friend.
It's a common problem and the things to check by your end are the same and everything I've seen and read it's cause of the mentioned problems. Maybe your friend has something wrong configured or whatever.

keval3492 said:
Actually I don't have PC / laptop ,so for unlocking bootloader I was go to my friend' home and use laptop of him and there is disable firewall as you mentioned.
So ,now I am at my home ,so actually I can't show you actual process of laptop ,I was telling you what is happening to me ,if any solution is find then I will go to his house ,and process unlocking bootloader.
Click to expand...
Click to collapse
In addition to strongst's helpful replies which I concur with (device signature enforcement on Windows 10 is a common issue, as it may stop you from installing the fastboot driver, and thus your device won't be loaded. Disable driver enforcement if you can and it doesn't void the laptop warranty), are you using the original Motorola USB cable or a high quality USB data cable? Also, try another USB port if you can.
For information, I've attached the Device Manager screenshot of my device, booted into the bootloader, and connected via the original USB cable to a USB 2.0 port. You'll note it's loaded as an Android Device via the Motorola ADB Interface (from the Motorola Device Manager software https://motorola-global-en-roe.custhelp.com/app/answers/detail/a_id/89881 ). Your device, loaded as fastboot athene_16mp suggests it's a driver issue.
Furthermore, if you want to unlock your bootloader, you'll need a computer to flash TWRP and may be useful having a computer around for troubleshooting/reverting back to stock Motorola firmware.

Just for curiosity sake I hope you changed the connection from charging to file transfer and switched on usb debugging. Cuz otherwise all what is needed already said by others. :/

Whenever I go to my friend's house and use his laptop to unlock my bootloader I will give you screen shot of display which causes problem for me to unlock my bootloader,thanks sir!!!!! And how to know that any anti virus ,firewall and other things you mentioned is stop me to install moto drivers?

Ayan Uchiha Choudhury said:
Just for curiosity sake I hope you changed the connection from charging to file transfer and switched on usb debugging. Cuz otherwise all what is needed already said by others. :/
Click to expand...
Click to collapse
Yes this is the basic for any unlocking bootloader process which I already done , switch on OEM unlocking,usb debugging,file transfer etc.thanks for it.

echo92 said:
In addition to strongst's helpful replies which I concur with (device signature enforcement on Windows 10 is a common issue, as it may stop you from installing the fastboot driver, and thus your device won't be loaded. Disable driver enforcement if you can and it doesn't void the laptop warranty), are you using the original Motorola USB cable or a high quality USB data cable? Also, try another USB port if you can.
For information, I've attached the Device Manager screenshot of my device, booted into the bootloader, and connected via the original USB cable to a USB 2.0 port. You'll note it's loaded as an Android Device via the Motorola ADB Interface (from the Motorola Device Manager software https://motorola-global-en-roe.custhelp.com/app/answers/detail/a_id/89881 ). Your device, loaded as fastboot athene_16mp suggests it's a driver issue.
Furthermore, if you want to unlock your bootloader, you'll need a computer to flash TWRP and may be useful having a computer around for troubleshooting/reverting back to stock Motorola firmware.
Click to expand...
Click to collapse
Yes!! My device is loaded with fastboot Athens 16_mps and I used original data cable(USB cable) from Motorola(which I receive when I purchased my device moto g4 plus),so how to disable driver enforcement as you mentioned!!I
I downloaded originally moto drivers from moto device and also install minimal adb/fastboot .exe setup. Thanks in advance.

keval3492 said:
Yes!! My device is loaded with fastboot Athens 16_mps and I used original data cable(USB cable) from Motorola(which I receive when I purchased my device moto g4 plus),so how to disable driver enforcement as you mentioned!!I
I downloaded originally moto drivers from moto device and also install minimal adb/fastboot .exe setup. Thanks in advance.
Click to expand...
Click to collapse
Tutorials for disabling driver enforcement can be found through a Google search (e.g. here's a link : https://www.drivethelife.com/window...e-enforcement-on-windows-10-8-7-xp-vista.html ) Of course, ask your friend before attempting this, as this allows you and anyone else to install and run unsigned drivers (including the fastboot drivers).

Okk thanks bro

So it is a safe driver(moto device manager)? Because if my friend ask me !!

keval3492 said:
So it is a safe driver(moto device manager)? Because if my friend ask me !!
Click to expand...
Click to collapse
You download it directly from motorola website? Why it should not be safe

Yes I downloaded from Motorola website ,it is also safe ,so why any PC not installed moto driver directly!!!!and gives fastboot _ Athens 16 mp s

Related

Cannot get past "adb devices" command line

I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
I believe part of the instructions are to install the Platform Tools, which should include drivers. Try running the SDK Manager and updating or installing the drivers again. Also ensure you have USB Debugging ON in your Developer settings and OEM Unlocking enabled. Lastly, tap the notification in your shade about the USB connection (I think it defaults to Charging Only) and change it to various modes. Mine seems to only work on PTP mode. When you run the adb devices command you will need to authorize the connection on the phone end the first time by clicking OK so make sure the screen is on and unlocked so you can see it.
Hope this helps.
peckaldee said:
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
Click to expand...
Click to collapse
u enable OEM Unlock under developer settings?
You enable USB debugging?
Me personally do not get any strings of data returned when im on fastboot
i open CMD, run ADB DEVICES, get message saying the port is opening, and then listing devices... which is empty
but i am able to flash anything i want using fastboot....
try this command and see if it works after that... fastboot reboot-bootloader
it should reboot bootloader for u.. thats a easy way to know its responding to u
Is the device showing properly in the Device Manager when it's connected to your system?
hEaTLoE said:
Is the device showing properly in the Device Manager when it's connected to your system?
Click to expand...
Click to collapse
It shows up in windows explorer as "Nexus 6p" when I plug in the USB cable.
I have USB debugging and unlock bootloader checked in settings.
My fastboot devices command returns nothing.
peckaldee said:
It shows up in windows explorer as "Nexus 6p" when I plug in the USB cable.
I have USB debugging and unlock bootloader checked in settings.
My fastboot devices command returns nothing.
Click to expand...
Click to collapse
Did you change the USB mode? Mine shows in Explorer as you described but won't work in ADB/Fastboot until I change it to PTP.
fury683 said:
Did you change the USB mode? Mine shows in Explorer as you described but won't work in ADB/Fastboot until I change it to PTP.
Click to expand...
Click to collapse
Yeah I tried every option. Nothing.
The instructions say the fastboot devices command should return my serial number and it does not.
When booted into the bootloader one it tells me on one line phone LOCKED and on another line says download mode DISABLED.
Don't know if this has anything to do with my problems but I still cannot get a return on the fastboot devices command in order to proceed with the unlock command of "fastboot flashing unlock"
remember that u need latest fastboot for this to work.
did u updated the SDK manager to the latest? i had to do that in order to work for 6P
chaco81 said:
remember that u need latest fastboot for this to work.
did u updated the SDK manager to the latest? i had to do that in order to work for 6P
Click to expand...
Click to collapse
I'm using sdk manager revision 24.4.1
peckaldee said:
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
Click to expand...
Click to collapse
I had the same issue ,it was down to when I plugged the phone into the PC for the first time,it installed the Google.USB driver ,but it didn't install the driver for the adb interface,I had to download it from Google and install it manually
I also had the same issue, I had an old Clockworkmod generic driver that I was using for my Samsung Galaxy S5 installed.
Go to Device manager (either type it in the start menu, or: right click This PC, click manage, and click device manager), plug in your unlocked Nexus 6P phone and watch for a new item to pop up. If it says android something, uninstall it. I had to uninstall 3 times, then reinstall the drivers from the SDK before it would work.
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
mbonus said:
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
Click to expand...
Click to collapse
This worked. Now my commands in terminal are working correctly. thanks all for the help
Got A device to pop up under the command adb devices, but nothing under fastboot devices. Any tips? Had to follow the skipsoft instructions to install adb/fastboot devices. Yes USB Debugging is on and the OEM unlocking is set to allow..
Christ I'm retarded. Sorry boys, thought my phone was in the bootloader when I was trying this command LOL
Same problem
peckaldee said:
When booted into the bootloader one it tells me on one line phone LOCKED and on another line says download mode DISABLED.
Don't know if this has anything to do with my problems but I still cannot get a return on the fastboot devices command in order to proceed with the unlock command of "fastboot flashing unlock"
Click to expand...
Click to collapse
I'm having the same problem. Did you ever figure out what was wrong?
mbonus said:
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
Click to expand...
Click to collapse
Solved my problem as well. Thanks!

[HELP]Device not detecting in fastboot mode

I had installed Moto drivers and also enabled the usb debugging but my my device is not showing in fastboot mode.
Seriously need help.
Thank you.
Just to clarify, when you reboot your device into the bootloader (fastboot), if you type the command 'fastboot devices' (without quotes) in ADB, you get nothing showing up in the device list?
Which Moto drivers are you using, what device do you have and are you issuing the commands via minimal ADB or another ADB command tool?
echo92 said:
Just to clarify, when you reboot your device into the bootloader (fastboot), if you type the command 'fastboot devices' (without quotes) in ADB, you get nothing showing up in the device list?
Which Moto drivers are you using, what device do you have and are you issuing the commands via minimal ADB or another ADB command tool?
Click to expand...
Click to collapse
I am using Motorola device manager drivers and using minimal adb tools
When I type command mfastboot devices nothing shows.
And I am trying to flash TWRP recovery it's saying waiting for device
Robinson#2 said:
I am using Motorola device manager drivers and using minimal adb tools
When I type command mfastboot devices nothing shows.
And I am trying to flash TWRP recovery it's saying waiting for device
Click to expand...
Click to collapse
Turn on your phone and run " adb devices " then see if it's getting connected in power on mode or not.. if not then try to install Adb Drivers..
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Robinson#2 said:
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Click to expand...
Click to collapse
It's same as you do in other Windows, go to "Device Manager" you will find device related name in that Tree,
Uninstall it and update again..
____Mdd said:
It's same as you do in other Windows, go to "Device Manager" you will find device related name in that Tree,
Uninstall it and update again..
Click to expand...
Click to collapse
Tried that but didn't worked
Robinson#2 said:
Tried that but didn't worked
Click to expand...
Click to collapse
Is it same computer that you used to unlock?
Had it worked to get unlock data and for unlocking..?
____Mdd said:
Is it same computer that you used to unlock?
Had it worked to get unlock data and for unlocking..?
Click to expand...
Click to collapse
Yes it's the same computer I used to unlock bootloader and flashed stock nougat with fastboot method 3 months back.
Robinson#2 said:
Yes it's the same computer I used to unlock bootloader and flashed stock nougat with fastboot method 3 months back.
Click to expand...
Click to collapse
If installing drivers again, use of different USB port, different data cable don't work then better to use different PC..
____Mdd said:
If installing drivers again, use of different USB port, different data cable don't work then better to use different PC..
Click to expand...
Click to collapse
I am going to try with a bootable pendrive with linux mint.
Robinson#2 said:
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Click to expand...
Click to collapse
If you're on Windows 10 with an UEFI firmware, I recall you need to disable driver signature enforcement if you wish to use fastboot. Credit to: https://forum.xda-developers.com/showpost.php?p=70792544&postcount=2028
Hopefully it'll work with the Linux distro though
echo92 said:
If you're on Windows 10 with an UEFI firmware, I recall you need to disable driver signature enforcement if you wish to use fastboot. Credit to: https://forum.xda-developers.com/showpost.php?p=70792544&postcount=2028
Hopefully it'll work with the Linux distro though
Click to expand...
Click to collapse
This was very helpful. Took me hours to find it but glad I did. On to step 2. lol How I was able to fix not being able to load anything in fastboot was this.
1. I right clicked on the Motorola_Mobile_Drivers_64bit.msi and selected uninstall. Repair did nothing.
2. Rt click view properties of Motorola_Mobile_Drivers_64bit.msi.
3. On the general tab I noticed it was blocked so I unblocked it.
4. Then switched to Compatibility tab.
5. Selected run compatibility mode, any previous version of windows.
--This stops the version checker
6. Hit apply save and ran it.
MrTwigglesworth said:
This was very helpful. Took me hours to find it but glad I did. On to step 2. lol How I was able to fix not being able to load anything in fastboot was this.
1. I right clicked on the Motorola_Mobile_Drivers_64bit.msi and selected uninstall. Repair did nothing.
2. Rt click view properties of Motorola_Mobile_Drivers_64bit.msi.
3. On the general tab I noticed it was blocked so I unblocked it.
4. Then switched to Compatibility tab.
5. Selected run compatibility mode, any previous version of windows.
--This stops the version checker
6. Hit apply save and ran it.
Click to expand...
Click to collapse
Bro i didi not detecting please help

Windows 10 won't Recognize my Phone in Fastboot Mode but ADB Is working

Hey Guys,
i tried to Root my Moto E4 but Unfortunally i cant get Fastboot to work under Windows 10 Home 64 Bit on Both my Notebook and my PC. I installed The Motorola Device Manager (Since it comes with drivers) and installed ADB and Fastboot but once i Reboot into Fastboot Mode it wont Recognize it for flashing. The CMD Just Says Waiting for Device. I have expierience with Rooting other Phones but i never had this much Trouble getting Fastboot to work properly. Would be awesome if u could show me a Solution to this since i really want a Custom Rom.
Gesendet von meinem SM-A300FU mit Tapatalk
There's no trick, it just works. I have Windows 10 64 bit as well and no issues. Maybe you need to update your platform tools (adb and fastboot). Using old ones can be a problem.
What command are you issuing? Just fastboot devices ?
Make sure you're not using a USB 3.0 port on your computer.
madbat99 said:
There's no trick, it just works. I have Windows 10 64 bit as well and no issues. Maybe you need to update your platform tools (adb and fastboot). Using old ones can be a problem.
What command are you issuing? Just fastboot devices ?
Make sure you're not using a USB 3.0 port on your computer.
Click to expand...
Click to collapse
Few other thoughts:
- try a different cable; a cable that works for charging and adb communication may not work with fastboot
- avoid external hubs if possible
- be sure to reboot both devices after switching drivers if communication isn't immediately established
Marc_Xperia said:
Hey Guys,
i tried to Root my Moto E4 but Unfortunally i cant get Fastboot to work under Windows 10 Home 64 Bit on Both my Notebook and my PC. I installed The Motorola Device Manager (Since it comes with drivers) and installed ADB and Fastboot but once i Reboot into Fastboot Mode it wont Recognize it for flashing. The CMD Just Says Waiting for Device. I have expierience with Rooting other Phones but i never had this much Trouble getting Fastboot to work properly. Would be awesome if u could show me a Solution to this since i really want a Custom Rom.
Gesendet von meinem SM-A300FU mit Tapatalk
Click to expand...
Click to collapse
When you say you booted to fastboot what do you mean ?
Did use adb and your phone was recognized and then you issued adb command or what method are you using ....
You need to ensure you establish USB debugging connection first & grant authorization ...once link with authorization has been established run adb ...from adb check if recognized run command to boot to fastboot
So start from the top && go down
ARE YOU CERTAIN YOU USED CORRECT METHOD TO TURN OFF DRIVER VERIFICATION ON WINDOWS 10 && YOUR DRIVER ACTUALLY INSTALLED
Last noteworthy point ... when unlocking my motoE4 I had to boot to bootloader ONLY to use fastboot NOT "FASTBOOT"
Hold power + volume button
Excellent troubleshooting from our community. OP has not come back yet to confirm, ask another question, or simply a thanks. (Maybe he got it) Hopefully he gets it sorted.
Maybe the junior members underestimate just how quick and helpful our little community can be.
@Marc_Xperia Do not forget to install AndroidBootloaderInterface Driver Software. *android_winusb.inf*
Thats what my Problem is. I installed the Latest Android Studio, i have gone to SDK Manager. Installed the Android 7.1 Files and USB Drivers and this happens everytime i want to unlock my BL. And yes i disabled Driver Signing on Windows 10. I call it Fastboot Mode since im Used to Xperias so im Sorry i confused anyone.
Marc_Xperia said:
Thats what my Problem is. I installed the Latest Android Studio, i have gone to SDK Manager. Installed the Android 7.1 Files and USB Drivers and this happens everytime i want to unlock my BL. And yes i disabled Driver Signing on Windows 10. I call it Fastboot Mode since im Used to Xperias so im Sorry i confused anyone.
Click to expand...
Click to collapse
When you authorize your adb connection do you tick or select always allow connections from this device ...the fact that your device is listed as *unauthorised* is a clear indication in your previous attempts you didn't authorize to "allways allow connections" from this device
#result _when you reboot authorization is revoked
Enter bootloader mode the old skool way using your buttons..
# MAKE SURE TO SELECT "ALLOW OEM UNLOCK OPTION IN DEVELOPS settings
1.AUTHORIZE TO "ALWAYS ALLOW CONNECTIONS FROM THIS DEVICE"
2.enter bootloader using hardware keys
3.plug in usb
4.run fastboot devices to force fastboot to start deamon ...
5.once fastboot can see your device run oem unlock
6.DO NOT USE USB 3 port so try different USB ports on pc
7. Alternatively use a live USB of Ubuntu minimal to do the job
--- doesn't seem like driver problem if adb can see your device
See if that works
KevMetal said:
When you authorize your adb connection do you tick or select always allow connections from this device ...the fact that your device is listed as *unauthorised* is a clear indication in your previous attempts you didn't authorize to "allways allow connections" from this device
#result _when you reboot authorization is revoked
Enter bootloader mode the old skool way using your buttons..
# MAKE SURE TO SELECT "ALLOW OEM UNLOCK OPTION IN DEVELOPS settings
1.AUTHORIZE TO "ALWAYS ALLOW CONNECTIONS FROM THIS DEVICE"
2.enter bootloader using hardware keys
3.plug in usb
4.run fastboot devices to force fastboot to start deamon ...
5.once fastboot can see your device run oem unlock
6.DO NOT USE USB 3 port so try different USB ports on pc
7. Alternatively use a live USB of Ubuntu minimal to do the job
--- doesn't seem like driver problem if adb can see your device
See if that works
Click to expand...
Click to collapse
I did all of that. Next Problem when i boot the device with Vol Down + Power and select meta mode. I will get only the Motorola Logo or a Normal Reboot into System. I set everything up in Developer Settings. Enabled Debugging and Allow Bootloader Unlock.
Marc_Xperia said:
I did all of that. Next Problem when i boot the device with Vol Down + Power and select meta mode. I will get only the Motorola Logo or a Normal Reboot into System. I set everything up in Developer Settings. Enabled Debugging and Allow Bootloader Unlock.
Click to expand...
Click to collapse
Why select meta mode ? When you are in bootloader you use your volume keys to navigate between meta, recovery& factory reset & meta and you use your power key to select different modes ...what do you want to do in meta mode ?
When you are in bootloader you are essentially in fastboot mode too so it isn't necessary to choose any of the other options unless you are trying to get into recovery which is pointless if you haven't flashed custom recovery yet ..
I Succeded. I Booted into Bootloader with ADB and took a look at Device Manager to install the Driver Properly.
i followed this guide https://forum.xda-developers.com/moto-e4/how-to/guide-unlock-moto-e4-bootloader-unique-t3654275.
Thank you for all of your Replys.
Moto e4 magisk manger trying to instal magisk hide props config says install failed
happymedium22026 said:
Moto e4 magisk manger trying to instal magisk hide props config says install failed
Click to expand...
Click to collapse
Download manually and flash inside recovery yourself
Safety net says the response is invalid does that affect ny device being rooted
happymedium22026 said:
Safety net says the response is invalid does that affect ny device being rooted
Click to expand...
Click to collapse
No it doesn't. That's an error in magisk manager when you hide the manager app itself. Just use a different safetynet checker app if you want to check safetynet.
Why are you posting this stuff in this thread?

Need help - OP 6t not recognized in fastboot

Hello, a few weeks ago i got my OP 6t. Due to my positive experience from my previous phones (LG G3 and G5) and what i heard from OP i tried to flash twrp and planned to install magisk. I followed the instructions here on xda to unlock the bootloader, it got recognized as device in adb and i could reboot it into the bootloader, but then it didnt recognized it in fastboot, it looks like im missing some sort of drivers, because when im in fastboot in the win 10 device manager its called "android" with a yellow triangle, i tried multiple guides already, but i had no success. Its the unbranded version with 8 gigs and 128 gig. I can provide more info if needed. Help would be very appreciated.
Did you follow funkwizard's guide in the guides/news/discussion forum? It's stickied at the top.
Anyhow, if you followed the guide, he provides this link (https://drive.google.com/file/d/1L7EZGx5mgeQYXO19Vsp9FWu9GXhF45Qs/view?usp=drivesdk) for the OP6T drivers that need it be installed.
He then provides this link (https://drive.google.com/file/d/1-uWQn-oHu_ROuDVCzIyrExoRbsSBYTtU/view?usp=drivesdk) to update your ADB/fastboot to the latest version.
Complete both of those steps and your phone SHOULD be recognized in fastboot. Good luck.
I have read his complete thread and im still stuck with the same problem. I deinstalled all phone related driver and only installed the one from the thread, opened the command prompt via admin and under device manager is still the yellow triangle beside the android device. I tried to install the driver manually via the google universal driver, but windows never found any compatible drivers.
And just to be certain, do you have USB Debugging enabled in developer options?
Pain-N-Panic said:
And just to be certain, do you have USB Debugging enabled in developer options?
Click to expand...
Click to collapse
Yupp, but i have to say that i had to tap it four to five times until the confirmation window popped up.
I had this problem few hours ago, and this is W10 fault. For me solution was that:
instal drivers from guide,
enter fastboot mode,
remove phone from device manager and unistal drivers,
replug phone,
let windows find drivers automaticly when in fastboot mode.
And that's it, fasboot comands works now.
Bartuc666 said:
I had this problem few hours ago, and this is W10 fault. For me solution was that:
instal drivers from guide,
enter fastboot mode,
remove phone from device manager and unistal drivers,
replug phone,
let windows find drivers automaticly when in fastboot mode.
And that's it, fasboot comands works now.
Click to expand...
Click to collapse
Thanks for the try, but still no change.
lubal21 said:
Thanks for the try, but still no change.
Click to expand...
Click to collapse
forget all the other tips, install the Google USB drivers with the batch file by entering Y on every question. select install driver in the device manager by selecting manually install. in the list presented select on the left Google Inc and on the right the fastboot driver. finish setup and fastboot should work now
lubal21 said:
Hello, a few weeks ago i got my OP 6t. Due to my positive experience from my previous phones (LG G3 and G5) and what i heard from OP i tried to flash twrp and planned to install magisk. I followed the instructions here on xda to unlock the bootloader, it got recognized as device in adb and i could reboot it into the bootloader, but then it didnt recognized it in fastboot, it looks like im missing some sort of drivers, because when im in fastboot in the win 10 device manager its called "android" with a yellow triangle, i tried multiple guides already, but i had no success. Its the unbranded version with 8 gigs and 128 gig. I can provide more info if needed. Help would be very appreciated.
Click to expand...
Click to collapse
Probably this shall help:
How to Fix OnePlus Device not showing in Fastboot Mode
In this detailed guide, we will show you the steps to fix the OnePlus Device not showing in the Fastboot Mode on Windows 10 PC.
www.droidwin.com

[Answered] Oneplus 8 Pro ReLock Bootloader

Q : so I'm trying to relock my bootloader since I can't run some of my banking apps, I followe this link. the problem is when the phone is in fastboot mode, my pc can't detect my device, and I've tried with some cables and still nothing. can someone please help me? thanks
A : Somehow my pc's fastboot driver is not working, so I decided to use my laptop and it works
B1nz said:
Q : so I'm trying to relock my bootloader since I can't run some of my banking apps, I followe this link. the problem is when the phone is in fastboot mode, my pc can't detect my device, and I've tried with some cables and still nothing. can someone please help me? thanks
A : Somehow my pc's fastboot driver is not working, so I decided to use my laptop and it works
Click to expand...
Click to collapse
Hi there is some guides how to get this driver installed on Xda. If your computer can see adb then you will be okay.
When you plug in you'll see a one plus box pop up and you click on that and hit install. Then under device manager you can manually select the driver under c:/ programfiles or (something like that) just to give you the idea. You might have to turn on unsigned drivers in windows (command+reboot) to install the driver, but I just wanted to let you know mostly everyone has been through this ( and so no surprise), and there is a guide on Xda that can do a much better job explaining what to do.

Categories

Resources