Hello,
I own a Realme XT phone with Android 10. It is the Russian version and I want to Unlock + Root it.
I think the Review from the App was successful. At least when I click on "Query verification status" on the App the "Review successful" message appears and I can click the "Start the in-depth test" which brings me into Bootloader mode.
The ADB Tools are somewhat working, I can see my device when connected to the PC when typing in ADB devices. I also can it boot into the bootloader with "adb reboot bootloader".
However, once in the Bootloader the device can't be found by the platform tools. If I type ADB devices with the phone connected none are returned. So "fastboot flashing unlock" isn't working because no devices are found.
I think the problem is that the device is not recognized once it is in the Bootloader Mode. In the Device Manager, I saw "Android Device" with an exclamation mark, which meant the driver wasn't properly installed, so Installed the "Android Bootloader Interface" manually, but still, the device is not recognized in Bootloader mode.
Please help me.
Related
No bootloader interface is found !
Hi experts.
ADB interface driver can be easily installed when "USB debugging" is enabled in phone because this way it allows Windows to detect a device with name string "ADB interface driver" and its specific vendor id along with product id. In my case, VID is VID_0bb4 and PID is PID_0004&MI_02 ( this PID is for ADB interface only). There is no problem in installation and detection of "ADB interface". adb reboot-bootloader is working from both Windows 7 64 bit command prompt and Ubuntu 15.04 terminal. Till now it is okay.
Now, this is what I am stuck at.
if anyone understood me with previous part please help me unlocking bootloader because unlocking bootloader requires switching into "fastboot" mode. With ADB command I am able to switch my phone into "fastboot" mode successfully. Now I disconnect USB cable from phone. Phone is still in "fastboot" mode ("=>> fastboot ..." written in lowest left corner on the screen). I connect USB cable again. No other new device is found this time. Fastboot commands that is detecting my phone successfully is with that adb interface port. Why is that ? At least I have learned from Internet that "bootloader interface" is required for Windows to unlock bootloader. Now after searching through many android_winusb.inf file from USB driver folder, I found out that the device id (VID) is same for both "adb interface" and "bootloader interface" BUT product id (PID) is different for both interfaces. Now it is VID_0bb4&PID_0FFF.
According to inf, Windows/Linux will only detect "bootloader interface" when the device which here in this case is a phone provides the VID_0bb4&PID_0FFF through the USB cable. The real problem here is my phone which is Micromax Bolt A065 (Kitkat 4.4.2, Kernal 3.4.67) is providing only one VID/PID in both ADB and fastboot mode and that is of "ADB Interface" only.
How can I get my phone to send that "bootloader interface" vid/pid to Windows/Linux in fastboot mode ?
Latest Android SDK is installed.
Tested with many adb/fastboot USB Drivers from Internet.
Hi everyone.
I apologize if this was already asked.
I own a Symphony H50. I am trying to install windows via change my software but it shows device too slow or protected by manufacturer.
So googled it and found that i need to unlock my boot loader.
So I installed adb,fastboot,drivers including bootloader interface driver. And booted into fastboot mode. And typed "fastboot oem get_unlock_data" and the command prompt shows 3 dots (...) And the cursor keeps flashing. And no confirmation message shows up on my phone.
It only shows "FASTBOOT mode".
Another thing i found out while installing adb drivers that it listed my phone manufacturer as HTC.
So is the problem with my phone?
And how do i fix it?
It may be a problem with driver, uninstall the previous one and install Koush universal adb driver from kaushikdatta.com
Use the link given below for a thorough tutorial to replace drivers.
http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/
Thanks for reply,
I'll try the drivers.
Though my adb drivers are working fine. My issue is with fastboot.
When i boot into fastboot mode it shows "FASTBOOT mode" on a black screen.
But i would try with the
That black screen with fastboot mode written at the bottom comes up on every phone when you boot into bootloader.
Please read the whole guide before proceeding.
You may skip the driver and adb installation part if u have already taken the measures I stated before.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
U can now use Kingoroot or any other tool for rooting.
It's recognized when booting into the system but not in Fastboot mode. I am wondering if there is a specific driver for this device or not?
"Had the same issue, downloaded the Google USB driver, manually set the device driver to "Android Bootloader Interface" and it worked! Device shows up when running "fastboot devices" now."
I used the above method from another user on here. To give credit his name is CheshireShorty, link down below.
Fastboot Drivers
Once I reboot to bootloader and connect to PC, the command "fastboot devices" does not recognize the device, so when I try to unlock it. it says "waiting for device". I've enabled both OEM unlocking and USB debugging.
The phone shows "fastboot_unlock_verify ok"
"The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously. "
EDIT: Solved it by using the correct platform-tools
I have the same problem. I actually thought that I installed the right sdk platform tools. Can you upload the platform tools that work for you?
Thank you
7tyjupiter said:
I have the same problem. I actually thought that I installed the right sdk platform tools. Can you upload the platform tools that work for you?
Thank you
Click to expand...
Click to collapse
I used the ones from here - https://www.getdroidtips.com/download-adb/#How-to-Install-Android-SDK-and-Platform-Tools
Solved.
I downloaded the platform tools 30.0.5 and reinstall it. Then i reinstall the adb bootloader driver right at the moment when the Nord2 is in the fastboot mode.
cheers
I have no developer options for reboot, bootloader, recovery.
platform tools 30.0.5, where?
Try after reboot into bootloader "fastboot devices". Is the Nord 2 recognized?
For me the correct command was "fastboot flashing unlock".
Hier is the link for the Platform tools 30.0.5
adb - platform tools v30.0.5.zip | by abdyasar for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I'm having the same issue. I can't get my Nord 2 show up with "fastboot devices". Sent my phone into the bootloader with "adb reboot bootloader" no problem.
I have used the 30.0.5 platform tools as well as the 31.0.3. Installed Oneplus USB drivers and also tried the universal r13 android drivers (Reinstalled the bootloader drivers while in bootloader mode). Also tried Snoop05s 1.43 adb installer. All to no avail. Just can't get my device to show up in the bootloader.
In Phone settings bootloader is open and USB debugging is on.
Edit: I made it work. Used regular CMD and not powershell and it showed up.
F4t16u3 said:
I'm having the same issue. I can't get my Nord 2 show up with "fastboot devices". Sent my phone into the bootloader with "adb reboot bootloader" no problem.
I have used the 30.0.5 platform tools as well as the 31.0.3. Installed Oneplus USB drivers and also tried the universal r13 android drivers (Reinstalled the bootloader drivers while in bootloader mode). Also tried Snoop05s 1.43 adb installer. All to no avail. Just can't get my device to show up in the bootloader.
In Phone settings bootloader is open and USB debugging is on.
Edit: I made it work. Used regular CMD and not powershell and it showed up.
Click to expand...
Click to collapse
Mine does not show up.... -.-
I'm at a total loss here...
phone has unlocking and USB debugging toggled on.
phone is not a US phone and unlocking is allowed.
phone goes into fastboot mode (by turning on while holding volume)
"fastboot devices" command returns my phone is in fastboot and connected
"fastboot oem unlock 0xPASSWORD" returns FAILED (remote: 'Command not supported in default implementation')
and fastboot: error: Command failed
I have no idea what to do or try from here.
If I try to flash an image i get:
FAILED (remote: 'Download is not allowed on locked devices')
so, defiantly still locked out of the bootloader
Try below steps
1. Ensure you have platform tools 33.x , 34 has issues.
2. Try to reboot to bootloader from pc.
adb reboot bootloader
3. Try running
fastboot flashing unlock unlockcode
Try it :
fastboot oem unlock
or
fastboot flashing unlock
SOLVED I am so happy. I'm on day 3 of trying to get the phone to bootload.
there is definitely a difference between going into fastboot through the phone itself and through adb commands on PC.
fastboot through the phone shows the drop down menu and no blue light illuminated on phone.
fastboot through adb phone is black screen with a blue light on right corner on the phone.
the windows drivers behave differently between the two. I am running windows 10. phone model XQ-CT72
steps that solved the issue. For anyone in the future.
I downloaded and used platform tools version 33.0.3 NOT version 34.
"adb reboot bootloader" used from windows PC
opened windows device manager found my "discovered device" and forced it to use the SONY driver downloaded from sonys website. It would not detect it on its own, or even use the SONY driver without me telling it to specifically. device manager> "andorid" > properties > update driver > browse computer for driver > installed sony driver
everything worked following these instructions here https://www.droidwin.com/unlock-bootloader-and-root-sony-xperia-1-iv/
alexriethmeier said:
There is definitely a difference between going into ...
Click to expand...
Click to collapse
fastboot, part of the android bootloader, abl
fastbootd, part of recovery
I had same issue and same solution fixed it what you showed and did. I was terrified, after investing so much money on this phone and not getting it unlocked.
You won't need to go through such hassle if you just use Linux VM (a Ubuntu distro will do). The driver works out of the box.