Database Info

Totally n00b question - from not-a-n00b

I just received the Pixel 2. Connected it to a Windows 10 box. Windows installed Microsoft drivers. I can't install Google drivers because Winblows says that the best drivers for my device are already installed. So I open an Explorer window, and there's the Pixel 2. I open that and it's a totally blank window. No, it's not the phone - ES shows directories in internal storage. (To make sure, I took a picture. It's in /DCIM/Camera.)
Enable debugging. Enable unlock. adb devices. No devices.
Okay, manually reboot to the bootloader. (The last line is Device State: locked) Fastboot sees the device.
fastboot boot twrp.img (I renamed it to make it easier). "FAILED (remote: Operation is not allowed in Lock State)"
I've owned Samsungs for so long I forgot that there were other manufacturers. What am I doing wrong? (I know it's got to be me, not the phone.)
How do I force Windows to replace the drivers (or do I really have to boot into Linux?) And how do I get the thing unlocked? Yes, I googled it. I searched here. I'm still stumped.

Maybe try this all in one tool
https://forum.xda-developers.com/pixel-2/development/tool-tool-one-driversunlocktwrpfactory-t3730228

Then check this out:
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417

flashing unlock did it. Thanks. Now to see if I can install everything (TWRP, Magisk, etc.) then a day of reinstalling all my apps and data.

Okay, TWRP and Magisk installed - thank you. Now only one thing is driving me crazy - plugging the Pixel into the PC doesn't show the Pixel. I hear the USB recognizing the phone, Device Manager sees the phone, but I can't find it as a drive, so I can copy data to it.
Oh, and when it's time to update to the next monthly, do I have to back my data up, flash stock, restore my data and reinstall Magisk? Or how does it work every month with a Pixel? (One update says it failed - I'm on the January update.)

Rukbat said:
Okay, TWRP and Magisk installed - thank you. Now only one thing is driving me crazy - plugging the Pixel into the PC doesn't show the Pixel. I hear the USB recognizing the phone, Device Manager sees the phone, but I can't find it as a drive, so I can copy data to it.
Oh, and when it's time to update to the next monthly, do I have to back my data up, flash stock, restore my data and reinstall Magisk? Or how does it work every month with a Pixel? (One update says it failed - I'm on the January update.)
Click to expand...
Click to collapse
To get your device to show up you have to pull the notification shade down and then change the device mode to mtp storage mode. As for updating to new security patchs I usually just use the factory image from Google and the flash-all script with the -w option removed in order to keep my data. Then flash my kernal and magisk.

I already had it set - I guess unlocking the bootloader resets it.

Rukbat said:
I already had it set - I guess unlocking the bootloader resets it.
Click to expand...
Click to collapse
It resets Everytime you disconnect the device or reboot for some dumb reason. It gets annoying.

Maybe in an update far away ...

Hi, I may be wrong and silly. I want you to check this option when you connected your mobile to PC.
As in attached screen shot when you connect your mobile to pc there will be a notification "Android system" (Not USB debugging connected one) click it and will provide you options screen "Use USB to.." from there select "Transfer files" option instead of "charge this device"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank You

_satish_ said:
Hi, I may be wrong and silly. I want you to check this option when you connected your mobile to PC.
As in attached screen shot when you connect your mobile to pc there will be a notification "Android system" (Not USB debugging connected one) click it and will provide you options screen "Use USB to.." from there select "Transfer files" option instead of "charge this device"
Thank You
Click to expand...
Click to collapse
Attaching Screen shot

Unlock tool seems not to work

I installed the universal adb drivers and rebooted.
I "installed" the tools (adb and fastboot).
I enabled USB debugging.
I run "adb devices", authorized the PC and saw my phone connected.
I successfully signed in with the unlocking tool.
But my phone isn't listed.
The unlocking tool log file mentions my f2 pro, though.
Any hint?

Is the files are same?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you follow this procedure?
https://c.mi.com/thread-2262302-1-0.html

NOSS8 said:
Is the files are same?
View attachment 5389529
Did you follow this procedure?
https://c.mi.com/thread-2262302-1-0.html
Click to expand...
Click to collapse
Very similar but not exactly the same: I downloaded the files from the link in lineageos lmi page.
In particular, the tool is "miflash_unlock-en-5.5.224.24.zip" from mi.com: it's the latest version.
Will try again with your link, even if it's not 100% clear.
Thanks: will keep posted with news.
Current steps.
1. Log into the unlocking tool
2. Put pone in fastboot mode
3. Run the tool, connect via USB and hit refresh: NO OUTPUT
4. Close the tool and from CMD run "fastboot.exe devices": NO OUTPUT
5. Put phone in normal mode w/ USB debugging
6. From CMD run "adb.exe devices": device is listed
7. Hold on

I am unable to execute step no.3 from MI forum:
> 3. Use another PC (64-bit) to unlock if MI Unlock Tool fails to detect your device/ unknown error.
As I only have 1 Windows PC, as per my religion.

Uqbar said:
I am unable to execute step no.3 from MI forum:
> 3. Use another PC (64-bit) to unlock if MI Unlock Tool fails to detect your device/ unknown error.
As I only have 1 Windows PC, as per my religion.
Click to expand...
Click to collapse
I am using version 4.5.813.51.
I had a similar problem in 2020 with MiUnlock, the phone would disconnect when launching the program, solved using an older w10 pc.
Try to use an old version of miUnlock to have the same files as on my capture above.(Install the programs at the root of the disk).
Remove all drivers and restart (show hidden devices).
Install platform-tools. (Install the program at the root of the disk)
With Miunlock install the drivers.
Don't forget to enable usb debugging.
Connect the phone before launching miUnlock.
good luck.

Do you mean i shouldn't install the universal adb drivers?
Which drivers is the mi.com website referring to?

Uqbar said:
Do you mean i shouldn't install the universal adb drivers?
Which drivers is the mi.com website referring to?
Click to expand...
Click to collapse
yes.and verify in peripheral devices(remove manually if if necessary).
All drivers are with Miunlock ant platform-tools.

you can also download this program (which will be useful later) and install the drivers with it.
Are you logged in with your Xiaomi account on Mi Unlock? No need to connect the phone

Yes i am logged in...

NOSS8 said:
you can also download this program (which will be useful later) and install the drivers with it.
Are you logged in with your Xiaomi account on Mi Unlock? No need to connect the phone
Click to expand...
Click to collapse
So I don't need any USB driver (they are thus irrelevant). It's all internet-bound.
Are you sure? I don't see my phone, yet. How long do I need to wait?

Uqbar said:
So I don't need any USB driver (they are thus irrelevant). It's all internet-bound.
Are you sure? I don't see my phone, yet. How long do I need to wait?
Click to expand...
Click to collapse
Install drivers with Miunlock and miflash
Usb debugging do you see your phone on the pc?
Fastboot mode do you see your phone on the pc?
which version of W10?

If you have whatsapp ,message me here,its easy bro,you are doing something little wrong

Uqbar said:
I installed the universal adb drivers and rebooted.
I "installed" the tools (adb and fastboot).
I enabled USB debugging.
I run "adb devices", authorized the PC and saw my phone connected.
I successfully signed in with the unlocking tool.
But my phone isn't listed.
The unlocking tool log file mentions my f2 pro, though.
Any hint?
Click to expand...
Click to collapse
disable drivers signature check in windows, afyer that install fastboot drivers

Question ROG phone 5s not recognized in fastboot mode, but ADB works... Windows driver issue?

Hi All,
I bought a ROG phone 5s (ZS676KS) direct from ASUS and I've been trying to root it all week. The firmware version is WW_18.1220.2111.160.
So far, I have been able to unlock the bootloader using Asus' app. My phone displays the unlocked bootloader warning on every boot.
I can't make fastboot work... the "adb reboot bootloader" command does work. I can also boot using the power + volume up button. But the "fastboot devices" command always comes up empty.
I found two possible reasons why fastboot doesn't work. So far I failed to fix either one.
First, the "OEM unlocking" option is missing in my developer options menu. I have the "USB debugging" option checked off. But many of the guides I read online say to allow OEM unlocking and I can't do that. But I've also seen people say that it doesn't matter. So, I don't know if this is a real problem. I can't find any reference to this problem except in Samsung phones. I tried the recommended fix but it didn't work.
Second, something's wrong with the fastboot driver on my computer. When get my phone into fastboot mode and plug it into the computer, device manager shows a device called "ASUS_I005D" with an orange caution icon on it. The error message in the properties menu says "The drivers for this device are not installed. (code 28)". This is probably the real problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Windows isn't finding a driver with its online driver search. I spent a few hours playing with Windows drivers to no avail. But maybe I missed something. I did find "ASUS_Android_USB_drivers_for_Windows_20150212" online and it didn't help.
I have tried different wires and USB ports and I'm using the side port of the phone instead of the bottom (although I tried the bottom port too). I tried another computer and that didn't work. But this was before I realized what was happening with windows drivers so I didn't check the device manager. I'm away from home now so I just have access to the one computer for now.
Does anyone know where I can find the correct driver? Or is there another approach I haven't considered? I hope there's nothing fundamentally wrong with the phone. I kind of just bought it without explicitly verifying, assuming the 5s is rootable since the 5 is...
Thanks Everybody,

Success is disgusted by some people, and will not share any files for free in the future.

It's not your device but likely Win 10 playing games with you. First completely uninstall the device driver to clean things up. Reboot your pc into Safe Mode. Plug in your phone from the side connector with a good data capable USB cable. From Device Manager choose "Add Legacy Hardware" from the menu and point the location to where you have saved the latest official Android USB drivers and install. Reboot Windows normally. If things have gone well, you should be able to both ADB & Fastboot into your device.

What a relief.
I am now able to flash my patched boot.img.
Thanks to both of you. I'm off to the races...

For me I just get a Ubuntu iso, boot your computer off a USB stick, install adb and fastboot via apt, and boom, no crappy drivers needed

Doogee S68 Pro - Fastboot commands not working

Hi. So i have this issue. My brother has this phone (Doogee S68 Pro) and like a month ago almost every app in the system started to crash. Even 3rd party apps. I tried to update Android System WebView but it was already on latest version so i tried to opt-in to beta versions and no difference here. He also did make a factory reset through recovery mode and the problem still persists. So resetting the device to factory mode doesn't solve this issue. So i told him i could flash a custom ROM to see if that solves the problem. Only custom ROM for that device i could find was LineageOS 17.1. So i unlocked OEM, enabled USB debugging and adb commands work. Only issue is that when i access fastboot and type "fastboot devices" the command line doesn't output any text. It just send the command and nothing happens. Not even "waiting for any device". Only when i type some random stuff like "fastboot erjsifjes" then it says "waiting for any device". I also tried to install universal adb drivers, but the device shows up as Kedacom USB Device in device manager without any yellow exclamation mark or anything. It just shows up like it's properly installed and it works. But when i try to type any fastboot command other than "fastboot devices" it says "waiting for any device". I'm lost. I tried every possible way to make this work but no luck. What am i doing wrong? I disabled driver verification in Windows 10 (idk how it's named in english i'm using czech version but you know what i mean), so the drivers were installed properly. Is there any way how i can bypass the fastboot? I was looking in the recovery menu and there's a method to install "update" via ADB. So can i unlock bootloader this way? Help me please i don't know what to do now. I'm lost...

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
adb commands work in system but not in fastboot

To get Fastboot working install the Doogee USB Driver suitable to your phone:
Doogee S68 Pro USB Driver for Windows (Official Mobile Driver)
Download the official Doogee S68 Pro USB Driver for your Doogee Mobile. We also provide all other Doogee Mobile drivers for free.
gsmusbdriver.com

Uhhh. I don't wanna disappoint you but i have already tried to install them. Both of the drivers included there . That was actually the first thing i tried. When the official drivers didn't work i tried installing universal ADB drivers, still same issue. Anyway i decided to buy a new phone. This piece of s*** is outdated anyways. If the apps didn't crash i wouldn't tried to flash custom ROM which i can't anyways.

Stupid question : Your phone is in Fastboot mode when you try the Fastboot commands right ?!
Are you using the latest version of the ADB and Fastboot Tools ?
You could try installing the following tool : https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Make sure you use a USB 2.0 port if possible!
If not then try a USB Hub between the phone and the PC or Laptop
Other things you could try :
- Use Windows 7 instead of anything newer.
- Use a Linux distro instead of Windows for the ADB and Fastboot part.
Good luck!

Update:
I got in touch with Doogee support and their technician. The problem was in trying to flash ROM in fastboot mode. They provide me SP Flash Tool which is used to flash ROMs, recovery, bootloader, etc. But the device needs to be turned off. This is kinda new for me, 'cause every time i was flashing ROMs or anything, i was doing it in fastboot mode with fastboot commands. The SP Flash Tool worked. Kinda. It allowed me to flash stock ROM successfully but it didn't solve the crashing apps issue. So yeah. I managed to progress further but still not the result i was hoping for. Still wanting to flash LineageOS 17.1 based on Android 10 in a hope that it'll solve my problem. When i tried flashing TWRP recovery straight up made for Doogee S68Pro with SP Flash Tool, it shows "Red State" message (see attachment) while booting the system (not able to enter recovery mode). Any ideas how to disable "verified boot"? I am able to access recovery through adb commands from system, however it enters the stock recovery menu, not TWRP which i did flashed. What am I doing wrong?

nero355 said:
Stupid question : Your phone is in Fastboot mode when you try the Fastboot commands right ?!
Are you using the latest version of the ADB and Fastboot Tools ?
You could try installing the following tool : https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Make sure you use a USB 2.0 port if possible!
If not then try a USB Hub between the phone and the PC or Laptop
Other things you could try :
- Use Windows 7 instead of anything newer.
- Use a Linux distro instead of Windows for the ADB and Fastboot part.
Good luck!
Click to expand...
Click to collapse
Yup.
- Device was in fastboot mode while typing fastboot commands. But not a single response from console.
- ADB and Fastboot was downloaded before creating this topic so i assume it was the latest version. Downloaded straight up from official Google page.
- Tried every single USB-C cable that i found, combined with every single USB port on my computer. (that took some time but need to be checked)
- To assure it was not my desktop PC what was potentially the problem, i also tried my brothers desktop PC with totally different HW components and operating system (his was W10, mine W11).
- I was thinking of creating dualboot system on my PC with W11 (primary) and W7 (secondary for this purpose) to try if that was the issue. (still open possibility)
- Same answer above

The drivers ( adb & fastboot ) you downloaded from Google are to be used with Google devices: you have to make use of the relevant drivers provided by DOGEE.

CaptainFedora said:
Update:
Still wanting to flash LineageOS 17.1 based on Android 10 in a hope that it'll solve my problem. When i tried flashing TWRP recovery straight up made for Doogee S68Pro with SP Flash Tool, it shows "Red State" message (see attachment) while booting the system (not able to enter recovery mode). Any ideas how to disable "verified boot"? I am able to access recovery through adb commands from system, however it enters the stock recovery menu, not TWRP which i did flashed. What am I doing wrong?
Click to expand...
Click to collapse
From : https://www.getdroidtips.com/lineage-os-17-1-doogee-s68-pro-android-10/
This should be the way : https://www.getdroidtips.com/twrp-recovery-doogee-s68-pro/
So no VBmeta.img needed it seems ?!

Yes! I was using the method mentioned in the first link. Never found that second link you provided. It looks very promising! I'm gonna try it in this week and post report. Man, that would be awesome.

You have to modify the usb driver .inf file. Add this rows to end of [Google.NTamd64] section:
;Doogee S68 Pro
%SingleBootLoaderInterface% = USB_Install, USB\VID_0E8D&PID_201C
%SingleAdbInterface% = USB_Install, USB\VID_0E8D&PID_201D&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E8D&PID_2006&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
Need a computer restart (shif+Restart in start menu) and have to switch off the signed drivers recommandation.

Hi ksanci ,and thank you very much it is work for me

OnePlus 8 T-Mobile Conversion Problem

Hi all,
I am trying to convert my T-Mobile IN2017 OnePlus 8 to have a global rom. I am currently on 10.5.7.IN55CB and I am following this tutorial here. My bootloader is unlocked (by using the official binaries I got emailed from OnePlus). My PC has driver signature verification off and is in test mode. It seems that my installer is stuck at this point:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
because the driver is not installed for recovery I think:
I have tried installing/reinstalling the OnePlus drivers to no avail. The installer runs perfectly fine while in fastboot mode, but does not work once rebooted into recovery. If someone can send me the driver or show what I am doing wrong, it would be much appreciated!

Costik said:
Hi all,
I am trying to convert my T-Mobile IN2017 OnePlus 8 to have a global rom. I am currently on 10.5.7.IN55CB and I am following this tutorial here. My bootloader is unlocked (by using the official binaries I got emailed from OnePlus). My PC has driver signature verification off and is in test mode. It seems that my installer is stuck at this point:
View attachment 5499393
because the driver is not installed for recovery I think:
View attachment 5499395
I have tried installing/reinstalling the OnePlus drivers to no avail. The installer runs perfectly fine while in fastboot mode, but does not work once rebooted into recovery. If someone can send me the driver or show what I am doing wrong, it would be much appreciated!
Click to expand...
Click to collapse
See my post here:
https://forum.xda-developers.com/t/...with-bootloader-re-lock.4345305/post-86144965
You're having the same issue I had. You need to install the fastboot drivers while it's connected in that state from your screenshot. Grab the drivers from Foxy Drew's post (linked in mine above), run the installer until it hangs, then update the drivers on the PC. When I did this the flash-all installer immediately kicked back into gear and finished the process.
The problem, I, think, is that you need to install adb drivers and fastboot drivers while the phone is in 3 different boot modes: normal, fastboot/recovery, and bootloader. So you need to get the phone to be recognized in all of those states so you can apply the drivers to the device the PC "sees" when it's connected in each of those states. Every boot mode basically presents itself as a different device to the PC, and that 3rd fastboot mode is hidden until you get to the spot you show in your screenshot.
Hope that works for you.

SilverZero said:
See my post here:
https://forum.xda-developers.com/t/...with-bootloader-re-lock.4345305/post-86144965
You're having the same issue I had. You need to install the fastboot drivers while it's connected in that state from your screenshot. Grab the drivers from Foxy Drew's post (linked in mine above), run the installer until it hangs, then update the drivers on the PC. When I did this the flash-all installer immediately kicked back into gear and finished the process.
The problem, I, think, is that you need to install adb drivers and fastboot drivers while the phone is in 3 different boot modes: normal, fastboot/recovery, and bootloader. So you need to get the phone to be recognized in all of those states so you can apply the drivers to the device the PC "sees" when it's connected in each of those states. Every boot mode basically presents itself as a different device to the PC, and that 3rd fastboot mode is hidden until you get to the spot you show in your screenshot.
Hope that works for you.
Click to expand...
Click to collapse
Thank you so much for your help! I was actually able to get it to work by doing something really similar. I'll post what I did just in case someone runs into this exact issue:
1) I made sure that I had all the drivers installed
2) I did the entire process over again until I got to that part where my device was no longer recognized
3) I went into device manager > IN2017 > update driver > drivers installed on this pc > chose from a list > Android phone > Android bootloader interface
I did this all while the converter was running and my phone was plugged into my pc. Once I did this, the program continued and I was able to finish the install.

Costik said:
Thank you so much for your help! I was actually able to get it to work by doing something really similar. I'll post what I did just in case someone runs into this exact issue:
1) I made sure that I had all the drivers installed
2) I did the entire process over again until I got to that part where my device was no longer recognized
3) I went into device manager > IN2017 > update driver > drivers installed on this pc > chose from a list > Android phone > Android bootloader interface
I did this all while the converter was running and my phone was plugged into my pc. Once I did this, the program continued and I was able to finish the install.
Click to expand...
Click to collapse
Yep, I think that's exactly what I did. I can't remember which fastboot drivers I updated to bit I'll bet they're both the same, and that's the point in the process where I updated drivers as well.
Cheers!