Can't unlock the bootloader on my Xiaomi Redmi Note 5 - Android Q&A, Help & Troubleshooting

Hey!
I am having difficulties unlocking the bootloader of my Redmi Note 5. I have already rooted a meizu phone and a lenovo tablet before and had no problems. However, with this one, I am able to enter the bootloader using the following command.
Code:
adb reboot bootloader
However, when I do this:
Code:
fastboot oem unlock
It outputs the following:
Code:
FAILED (remote: 'Token Verify Failed, Reboot the device')
fastboot: error: Command failed
The command
Code:
fastboot oem unlock-go
outputs the same results and rebooting my phone doesn't resolve the issue.
Additionnaly, using the Miui Unlock App doesn't work because it doesn't recognise my phone when in bootloader.
Please help!
Thanks in advance.
PS: I am using a Win10 64bits PC
Edit: I tried an older version of Miui Unlock and it detected my device, but couldn't unlock it. It stopped at 99% and output "couldn't unlock"

IMHO it's always recommended to check for boot-loader can get unlocked
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.

0

Seppppx said:
You are supposed to use the mi unlock tool. Not these simple fastboot commands (xiaomi wants to make unlocking complicated)
Here is a steb-by-step guide
1. Make a Mi account
2. Apply for an unlock here https://en.miui.com/unlock/
3. Download Mi unlock by clicking on the unlock now and then download Mi Unlock.
4. Download the Mi Unlock app to PC, and sign in with your Mi Account;
5. Shut down your phone manually, and hold Volume down key and Power button to enter Fastboot.
6. Connect your phone to PC using USB cable and click "Unlock".
You will probably have to wait some time (3 days, maybe a week or even a month).
it's been some time since I have unlock my Xiaomi phone so these steps might be wrong. If yes point that out please.
Click to expand...
Click to collapse
As I said in my post, I have tried using Mi Unlock. I have done all your steps up to the 6th because the app doesn't allow me to click unlock. I am guessing that it doesn't detect my phone in fastboot mode. About the time I have to wait, is it the time between when I apply for an unlock and when I can unlock my phone? This would explain why I can't unlock it. However I saw on another thread that Xiaomi removed the need to apply and wait to be able to unlock a phone. I don't really know how to feel about this one...

0

Seppppx said:
Do you have fastboot/adb drivers installed?
Click to expand...
Click to collapse
I'm pretty sure I do, because I have already rooted devices before. How do I check?

0

Seppppx said:
To check your drivers (and install) do this.
1. Plug your phone to the Pc.
2. Boot to fastboot (use googles platform tools, download below)
3. Open CMD as an administrator.
4. Navigate to the folder there you have platform tools in.
5. Type "fastboot devices" if you see no output you either have the wrong drivers installed or not installed
(Download the Google USB driver linked down)
6. To install drivers you open your Device Manager in windows.
7. Look for something like "Android Device" there. If it also has a warning sign that means that there are no drivers.
8. Right click on "Android Device"
9. Click on "Update driver"
10. Click on "Browse my computer for driver software"
11. Click on "Let me pick from a list of available drivers on my computer"
12. Click on "Have Disk..."
12. Browser for a driver under "Copy manufacturer's files from:"
13. Find the driver folder in the folder you saved it to and open it.
14. Double click on "android_winusb.inf
15. Click on "OK"
16. Click on "Next"
Done, you have installed a driver.
Download the Google fastboot/adb here https://developer.android.com/studio/releases/platform-tools
Direct download https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Download the google fastboot/adb driver here https://developer.android.com/studio/run/win-usb
Direct download https://dl.google.com/android/repository/usb_driver_r12-windows.zip
Click to expand...
Click to collapse
Well, I tried and went up to step 5 and there was no output. So I continued the steps, on step 7 I saw that my Adroid Device Driver had no warning sign, meaning that I have the wrong drivers. I continued on with your steps. After step 11, the control pannel shows 2 drivers named as "Android Bootloader Interface", however before step 15, the control pannel shows 3 different drivers named as "Android ADB Interface", "Android Bootloader Interface" and "Android Composite ADB Interface". The second one is selected by default, so I click ok and it installs. However, the "adb devices" and "fastboot devices" commands still show nothing in the command prompt. Is there something I am doing wrong?

0

Seppppx said:
You should reboot your phone after installing these drivers. I had the same problem, that fixed it.
Click to expand...
Click to collapse
Still nothing... There is no output to "adb devices" even after I install the driver and reboot my phone.

0

DemonBlu3000 said:
Still nothing... There is no output to "adb devices" even after I install the driver and reboot my phone.
Click to expand...
Click to collapse
{
"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"
}
Xiaomi USB Drivers are essential while connecting your smartphone in Fastboot Mode & Emergency Download Mode [EDL].

Seppppx said:
Do you get an output to "fastboot devices" that's the thing that matters when unlocking. I managed to my redmi note 4 to unlock without adb.
You also can get adb in the classic system where you boot. That works for me.
Click to expand...
Click to collapse
No, "fastboot devices" has no output on my computer, but it has one on another computer for some reason. On mine it doesn't and I need it to on mine.

0

Okay guys I figured it out. I was missing a step. I indeed had to use the Mi Unlock tool, but before doing so I had to enable an option beneath the "OEM unlock option", I don't remember how it was called but everything's fine now!

Related

XT1022: Failed to validate system image. Connect USB Cable. Device Locked - Status 0

Hello Guys,
Laid my hands on a spare XT1022 from my friend that was supposedly junk for him because of the following reason. The phone starts of directly in fastboot mode and there's no sign of a normal startup. Although i've connected the USB cable and it shows up as "Motorola ADB Device" under Device Manager, still the fastboot shows Connect USB Cable error. The exact scenario is depicted in a similar pic below :
{
"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"
}
.
The phone is fully stock and was treated to this message upon a random reboot. I can get this back to life by flashing TWRP & Custom ROM's but for that first of all need to unlock the bootloader, for which the data cable needs to be shown as connected. USB Debugging wasn't enabled.
Would be highly obliged if someone could shed some light in the right direction and help out on this
Regards.
@lost101, Need your expert advice on this. Others, please do help.
'USB Debugging' most likely does not need to be enabled with Condor handsets in order to unlock Bootloader. That is a security feature that only appeared with later devices.
The USB issue seems obviously driver-related. The easiest solution would be to boot into a Linux Live CD (such as Ubuntu), and gain fastboot access that way - drivers are not needed in Linux. Then fastboot flash the latest XT1022 factory firmware image.
*Note: In linux, use the 'sudo' command prefix:
sudo fastboot devices​
lost101 said:
'USB Debugging' most likely does not need to be enabled with Condor handsets in order to unlock Bootloader. That is a security feature that only appeared with later devices.
The USB issue seems obviously driver-related. The easiest solution would be to boot into a Linux Live CD (such as Ubuntu), and gain fastboot access that way - drivers are not needed in Linux. Then fastboot flash the latest XT1022 factory firmware image.
*Note: In linux, use the 'sudo' command prefix:
sudo fastboot devices​
Click to expand...
Click to collapse
Live booted uBuntu Raring Ringtail 13. Added the necessary repositories first ;
sudo add-apt-repository ppa: phablet-team/tools && sudo apt-get update
Click to expand...
Click to collapse
. Further installed the ADB & Fastboot ;
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
. Got success messages.
Further using the terminal, used two commands ;
sudo adb devices
Click to expand...
Click to collapse
sudo fastboot devices
Click to expand...
Click to collapse
The result was exactly the same which i get in Windows command prompt. The list of devices shows a blank. I've installed the drivers and rechecked them, the device is listed as "Motorola ADB Interface" under Device Manager :
and; shows as Fastboot condor S in hardware eject box.
I fail to understand why it isn't showing as connected only in the fastboot menu. Fastboot reason is given as "fall through from not charger boot mode". The device shows only the fastboot screen by default. If any other option like recovery etc is selected, it throws the error message as bootup failed. Scenario is exactly of the same pic which was posted in #1.
Please suggest the next step.
@BBThumbHealer - Starting to look like Bootloader corruption. An unbrick method could be applied to potentially restore a functional Bootloader. One exists for Falcon 5.1 - unsure about Condor at this time.
I would try to eliminate the USB cable as the problem by trying alternatives.
BBThumbHealer said:
Hello Guys,
Laid my hands on a spare XT1022 from my friend that was supposedly junk for him because of the following reason. The phone starts of directly in fastboot mode and there's no sign of a normal startup. Although i've connected the USB cable and it shows up as "Motorola ADB Device" under Device Manager, still the fastboot shows Connect USB Cable error. The exact scenario is depicted in a similar pic below :
.
The phone is fully stock and was treated to this message upon a random reboot. I can get this back to life by flashing TWRP & Custom ROM's but for that first of all need to unlock the bootloader, for which the data cable needs to be shown as connected. USB Debugging wasn't enabled.
Would be highly obliged if someone could shed some light in the right direction and help out on this
Regards.
Click to expand...
Click to collapse
I was stucked in the same problem yesterday. I succeeded and recovered my Moto E to live again.
As in the screenshot you posted. Your bootloader is locked. You need to unloack the bootloader. To do so follow the steps in the link given below :
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
Login or create your Moto ID and follow the steps as described.
After that you'll have to flash the firmware again. hope this helps.

How to install fastboot adb drivers on windows

Hello, it is better if you view this thread on pc or on browser. Viewing via XDA app or XDA Lab app will make you crazy.
{
"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"
}
Can't you use fasboot commands even your phone is in fastboot mode and connected to computer?
Can't you install TWRP or anything via fastboot mode even if have entered fastboot mode and connected to computer?
Here is the solution! You just need to install your drivers on your computer correctly. On this thread, I will show you how to install fastboot and adb drivers on computer for our Redmi 3s.
Requirements
-A windows based computer
-15 seconds adb installer by @Snoop05
This method will work for every android devices which are based on Android Marshmallow (SDK 23) or devices with android Nougat 7.1.1 (SDK 25) by Custom ROMs.
OK, let's start!
Step1-Disconnect your android device from computer,
Step2-Download and install 15 second ADB installer from here:https://forum.xda-developers.com/showthread.php?t=2588979
Step3-Enter your android device to fastboot mode,
Step4-Connect your android device to computer,
Step5-Open device manager in computer,
Step6-Right click on the 'Android' under 'Other devices' and select 'Update Driver Software...',
Step7-Select 'Browse my computer for driver software',
Step8-Click on 'Let me pick from a list of device drivers on my computer',
Step9-Select 'Android Device' and click 'Next',
Step10-Select 'Android ADB Interface' and click 'Next',
Step11-Do step 6-7-8-9-10 and Select 'Android Bootloader Interface' and click 'Next',
Step12-Do step 6,7,8,9,10 and Select 'Android Composite Interface' and click 'Next'.
If you have already done all steps above, your fastboot mode is working well again, Congrats!
You can see everything that needs fastboot is working well,
Devices I used:
-A computer with windows 8,
-Xiaomi Redmi 3s Prime.
Credits
@Snoop05 for 15second adb installer.
Sorry for my bad English btw.
Thread by MyoHtet (aka BM Heades).
i followed all the steps but in the end get an error of 'could not load recovery.img' pls help
BM Heades said:
Hello, it is better if you view this thread on pc or on browser. Viewing via XDA app or XDA Lab app will make you crazy.
Can't you use fasboot commands even your phone is in fastboot mode and connected to computer?
Can't you install TWRP or anything via fastboot mode even if have entered fastboot mode and connected to computer?
Here is the solution! You just need to install your drivers on your computer correctly. On this thread, I will show you how to install fastboot and adb drivers on computer for our Redmi 3s.
Requirements
-A windows based computer
-15 seconds adb installer by @Snoop05
This method will work for every android devices which are based on Android Marshmallow (SDK 23) or devices with android Nougat 7.1.1 (SDK 25) by Custom ROMs.
OK, let's start!
Step1-Disconnect your android device from computer,
Step2-Download and install 15 second ADB installer from here:https://forum.xda-developers.com/showthread.php?t=2588979
Step3-Enter your android device to fastboot mode,
Step4-Connect your android device to computer,
Step5-Open device manager in computer,
Step6-Right click on the 'Android' under 'Other devices' and select 'Update Driver Software...',
Step7-Select 'Browse my computer for driver software',
Step8-Click on 'Let me pick from a list of device drivers on my computer',
Step9-Select 'Android Device' and click 'Next',
Step10-Select 'Android ADB Interface' and click 'Next',
Step11-Do step 6-7-8-9-10 and Select 'Android Bootloader Interface' and click 'Next',
Step12-Do step 6,7,8,9,10 and Select 'Android Composite Interface' and click 'Next'.
If you have already done all steps above, your fastboot mode is working well again, Congrats!
You can see everything that needs fastboot is working well,
Devices I used:
-A computer with windows 8,
-Xiaomi Redmi 3s Prime.
Credits
@Snoop05 for 15second adb installer.
Sorry for my bad English btw.
Thread by MyoHtet (aka BM Heades).
Click to expand...
Click to collapse
USB not recognized
But in my case it is showing under universal serial bus drivers and written unknown device and when I connect to computer in fastboot mode it says USB not recognised I used it on redmi 4A with A PC running on Windows 7 ultimate x 86 please help me to find out it
Hi to everybody
I am trying to correctly connect my new Ticawatch Pro with WearOS to my notebook win 7 Ultimate TEST MODE
The procedure is asking to put in fastboot mode the device but I can't because I don't know the procedure
Is there any workaround ??
I want underline that on this notebook I am able to connect without problems all my android devices like Xiaomi Mia1, Mi6, LG Nexus 5X and others
EDIT
I have applied the procedure having he smartwatch switched ON (=adb mode)
Now when I connect the device to the netbook it is recognized as ADB device:
I can see it into Manage resources (as Android Composite ADB Interface),
I can see it under list of USB devices (as Ticwatch pro)
BUT I CANNOT see it into Explorer in order to explore its hard memory space
Any suggestions ??

LGK9 TV BootLoader Unlock

Hello, I'm trying to unlock the bootloader of my cell phone which is lg k9 tv to be able to root but I can't do it at all, I've tried the tutorials of the entire internet, the adb drivers don't appear to be updated in the windows device manager 10, even with the help of a friend who has more knowledge on cell phones he was unable to unlock, and I also can't get into fastboot mode which is essential from what I saw, I've seen a tutorial on how to get into fastboot but my lg k9 doesn't no way in fastboot, if you can help me thank you.
diego998kk said:
Hello, I'm trying to unlock the bootloader of my cell phone which is lg k9 tv to be able to root but I can't do it at all, I've tried the tutorials of the entire internet, the adb drivers don't appear to be updated in the windows device manager 10, even with the help of a friend who has more knowledge on cell phones he was unable to unlock, and I also can't get into fastboot mode which is essential from what I saw, I've seen a tutorial on how to get into fastboot but my lg k9 doesn't no way in fastboot, if you can help me thank you.
Click to expand...
Click to collapse
LG's USB driver doesn't get updated by Windows: it's on you to ensure to have driver's latest version installed.
Visit LG's website.
To root device's Android 1st of all these 2 options must be enabled/allowed
{
"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"
}
and FASTBOOT binary must be installed.
After device got rebooted
Go to the folder where ADB and Fastboot binaries are installed.
Right-click in an empty location inside the folder while holding the Shift button.
Then select ‘Open command window here’ or ‘Open PowerShell window here.’
Enter the command fastboot flashing unlock and hit Enter-button
You will see an option for bootloader unlock on your device’s screen.
Use the volume buttons to move up and down and select the option to unlock the bootloader.
A prompt will pop up, asking for confirmation. Use the power button to confirm your selection as yes, and you are done.
The phone will now reboot to fastboot mode.
Enter the command fastboot reboot and it will boot into PC.
jwoegerbauer said:
LG's USB driver doesn't get updated by Windows: it's on you to ensure to have driver's latest version installed.
Visit LG's website.
To root device's Android 1st of all these 2 options must be enabled/allowed
and FASTBOOT binary must be installed.
After device got rebooted
Go to the folder where ADB and Fastboot binaries are installed.
Right-click in an empty location inside the folder while holding the Shift button.
Then select ‘Open command window here’ or ‘Open PowerShell window here.’
Enter the command fastboot flashing unlock and hit Enter-button
You will see an option for bootloader unlock on your device’s screen.
Use the volume buttons to move up and down and select the option to unlock the bootloader.
A prompt will pop up, asking for confirmation. Use the power button to confirm your selection as yes, and you are done.
The phone will now reboot to fastboot mode.
Enter the command fastboot reboot and it will boot into PC.
Click to expand...
Click to collapse
a question, can it be the universal drivers or does it have to be the device itself?
jwoegerbauer said:
LG's USB driver doesn't get updated by Windows: it's on you to ensure to have driver's latest version installed.
Visit LG's website.
To root device's Android 1st of all these 2 options must be enabled/allowed
and FASTBOOT binary must be installed.
After device got rebooted
Go to the folder where ADB and Fastboot binaries are installed.
Right-click in an empty location inside the folder while holding the Shift button.
Then select ‘Open command window here’ or ‘Open PowerShell window here.’
Enter the command fastboot flashing unlock and hit Enter-button
You will see an option for bootloader unlock on your device’s screen.
Use the volume buttons to move up and down and select the option to unlock the bootloader.
A prompt will pop up, asking for confirmation. Use the power button to confirm your selection as yes, and you are done.
The phone will now reboot to fastboot mode.
Enter the command fastboot reboot and it will boot into PC.
Click to expand...
Click to collapse
When I try to put it on bootloader mode it fails.
Follow the steeps I've done:
1. Turn On USB Debug mode and OEM Unlock at Developer menu.
2. Plug in and do adb command "adb devices"
3. When appear the list with my phone I do the command "adb reboot bootloader"
But when it restarts it goes to system and not to bootloader screen.
Ive tried also "adb reboot fastboot" and "adb reboot download" but the same happens.
@diego998kk
Press and hold the volume down and power buttons until the LG logo appears, then release them. If this doesn’t work, you may have to release the power and volume down buttons for a second when the LG logo appears, then re-press them until the bootloader shows up what may take some seconds.
jwoegerbauer said:
@diego998kk
Press and hold the volume down and power buttons until the LG logo appears, then release them. If this doesn’t work, you may have to release the power and volume down buttons for a second when the LG logo appears, then re-press them until the bootloader shows up what may take some seconds.
Click to expand...
Click to collapse
None worked
diego998kk said:
When I try to put it on bootloader mode it fails.
Follow the steeps I've done:
1. Turn On USB Debug mode and OEM Unlock at Developer menu.
2. Plug in and do adb command "adb devices"
3. When appear the list with my phone I do the command "adb reboot bootloader"
But when it restarts it goes to system and not to bootloader screen.
Ive tried also "adb reboot fastboot" and "adb reboot download" but the same happens.
Click to expand...
Click to collapse
Me too
Someone did unlock LG K9 TV bootloader

Question fastboot command not working | waiting for any device

Hi all,
first of all: yes, I've used the search function but I couldn't find a solution.
I have a Nord 2 5G device and want to install Evolution X Custom ROM.
I followed the instructions in this forum (and other websites) and managed to downgrade to OOS 11 in order to get into fastboot. The adb command to boot into fastboot mode also worked and my device is saying
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 and power buttons simultaneously.
Click to expand...
Click to collapse
However, the fastboot command to flash TWRP does not work. On the command line I can only see
< waiting for any device >
Click to expand...
Click to collapse
and I continuously hear the Windows device attached/device detached chime. The device manager shows this:
{
"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"
}
After opening the properties, I can see this:
As it's German. It says:
The drivers for this device have not been installed. (Code 28).
There are no compatible drivers for this device.
Click to expand...
Click to collapse
So obviously I need additional drivers. I have downloaded the USB drivers from this website: https://developer.android.com/studio/run/win-usb, chose install from hard drive and pointed to the directory I have unzipped the driver set but Windows can't install them. I have also downloaded the OnePlus driver set from https://oneplusdriver.com/download-oneplus-driver and installed them.
Still, it doesn't work.
I am at the end of my rope now. What did I do wrong?
Thanks in advance!
I have same problem did you find solution
mckinley87 said:
Hi all,
first of all: yes, I've used the search function but I couldn't find a solution.
I have a Nord 2 5G device and want to install Evolution X Custom ROM.
I followed the instructions in this forum (and other websites) and managed to downgrade to OOS 11 in order to get into fastboot. The adb command to boot into fastboot mode also worked and my device is saying
However, the fastboot command to flash TWRP does not work. On the command line I can only see
and I continuously hear the Windows device attached/device detached chime. The device manager shows this:
View attachment 5835135
After opening the properties, I can see this:
View attachment 5835137
As it's German. It says:
So obviously I need additional drivers. I have downloaded the USB drivers from this website: https://developer.android.com/studio/run/win-usb, chose install from hard drive and pointed to the directory I have unzipped the driver set but Windows can't install them. I have also downloaded the OnePlus driver set from https://oneplusdriver.com/download-oneplus-driver and installed them.
Still, it doesn't work.
I am at the end of my rope now. What did I do wrong?
Thanks in advance!
Click to expand...
Click to collapse
Have you try to use platform-tools? It has adb and fastboot. I have always used that and no problem
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Look in Eigenshaften > Details > "Device instance path" (k.A. Gerätepfad?).
What's the VID/PID?
Is that in the stock INF file in android_winusb.inf?
If you want, you can just use Zadig drivers. I can give you "fastbogus.exe".
https://zadig.akeo.ie/
Select "WinUSB".
HamdiPiixel said:
I have same problem did you find solution
Click to expand...
Click to collapse
Yes, the thing is, I've installed the drivers in the wrong way. I'll try to give a step-by-step guide:
Go to Device Manager and find the Device (will have the yellow triangle. Right-click on it and choose upgrade driver (hope that's what's shown in the english version of Win 11). You'll see this:
Click the second option. You'll see this:
Here, choose the second option at the bottom. That's where I did it wrong. I selected the drivers in the dropdown menu and that doesn't work.
Click there...
and click there to select the diver *.inf file in the usb_driver folder.
That should work. It's important that you use the official Google Drivers (at least it was important here).
Hope that works.
mckinley87 said:
Yes, the thing is, I've installed the drivers in the wrong way. I'll try to give a step-by-step guide:
Go to Device Manager and find the Device (will have the yellow triangle. Right-click on it and choose upgrade driver (hope that's what's shown in the english version of Win 11). You'll see this:
View attachment 5856845Click the second option. You'll see this:
View attachment 5856867
Here, choose the second option at the bottom. That's where I did it wrong. I selected the drivers in the dropdown menu and that doesn't work.
View attachment 5856869
Click there...
View attachment 5856871
and click there to select the diver *.inf file in the usb_driver folder.
That should work. It's important that you use the official Google Drivers (at least it was important here).
Hope that works.
Click to expand...
Click to collapse
Hi,
I managed to install the ADB google drivers so I can now at least see Fastboot devices response properly but I do not know how to unlock the bootloader as the command "fastboot oem unlock" is not recognized and there is still no menu for the bootloader unlock (only the message on the black screen)
If anyone could help I would be be very grateful.
Thank you.
Best Regards
Lad

Sony Xperia L3 root phone.

I have a Sony Xperia L3 and i have tried to root but it seems impossible. How can i do it? I have tried to root the phone with Sony Xperia C Root but it could not do it. Kingo Root is the same, fail. Also tried dr.fone but it did not support l3.
You must unlock the bootloader and then follow this steps: https://topjohnwu.github.io/Magisk/install.html
I have check and my phone can be unlocked, i have downloaded fastboot but i do not understand what to do next. I got to step 8 https://www.xda-developers.com/install-adb-windows-macos-linux/ i can see my phone in the command line, what to do next?
I cannot find the fastboot icon under devices and printers
I got to https://mobilewithdrivers.com/unlock-bootloader/sony-xperia-l3-32gb-3gb-ram i got it into fastboot mode but no commands works, fastboot flashing unlock, fastboot oem unlock. Unknown command, command not allowed.
Should i have a unlock code? I only see Xpeira L2 on the site for getting a unlock code, no L3 https://www.getdroidtips.com/unlock-bootloader-xperia-device/
It seems to be something wrong in developer mode, oem do not turn on, no green, it is just off.
Oldschool297 said:
I have a Sony Xperia L3 and i have tried to root but it seems impossible. How can i do it? I have tried to root the phone with Sony Xperia C Root but it could not do it. Kingo Root is the same, fail. Also tried dr.fone but it did not support l3
Click to expand...
Click to collapse
What's phone's Android version? Android 8.1 ? If so, look inside here:
[HOW TO] Root Android 8.1 - DevPreview 1 - OPP5
There are probably already a couple guides up, but I wanted to post about how I went about doing this and have everything working. It may not work for everyone, but for me, it worked the first time. 0: Yep, there is a step zero here. :good...
forum.xda-developers.com
Thanks. I cannot unlock the bootloader to try. I do not get the oem under development mode to work. It is only off. I can't get it on to unlock the bootloader.
Why not contact Sony ?
Sony Support Consumer Electronics
services.sony.co.uk
I tried the guide https://www.kingoapp.com/root-tutorials/how-to-unlock-bootloader-android-device.htm i get it to fastboot and the light is blue but i only get. Failed remote: Command not allowed, Finished. total times 0.045s.
What Fastboot command did you run?
BTW: Install the suitable Fastboot driver provided by Sony, if not already done yet.
I tried
Use the Command Prompt window to retrieve your unlock key as described by your manufacturer. If you own a Motorola device run the command: fastboot oem get_unlock_data, HTC run the command: fastboot oem get_identifier_token.
Select the token which is spit out by the Command Prompt window and copy and paste it into the applicable box of the form on your manufacturer's website without any spaces.
And: fastboot -i 0x0fce oem unlock 0x07B7BFEA7AC879F0 https://www.getdroidtips.com/unlock-bootloader-sony-xperia-x-f5121f5122/
I downloaded android_winusb.inf were should i add it?
Don't understand what you've downloaded. It's an ADB driver.
Contents of relevant ADB driver 's .ZIP-file is
{
"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"
}
To install the suitable ADB driver:
Open the Device Manager. To do this, click Start and type Device Manager. Then click Device Manager.
In Device Manager, right-click the name of your computer at the top of the device list, and then click Add Legacy Hardware.
In the Welcome to the Add Legacy Hardware Wizard dialog box, click Next.
Select Select and install hardware manually from a list and click Next.
Select Show all devices and click Next.
Click Disk....
In the Disk... dialog box, click Browse... click Browse, and then select the driver file with the extension adb (written like this: xxxxxadb, where xxxxxx is the unique file name). Click Open.
In the Disk... dialog box, click... Click OK.
Highlight the Sony xxxxxx ADB Interface Driver file and then click Next twice. The installation starts.
Click Finish and restart the computer.
I get this.
I also tried https://techbeasts.com/how-to-unlock-bootloader-of-sony-xperia-devices-guide/ the problem in fastboot seems to be that i- becomes and unknown option
https://forums.androidcentral.com/t...tloader-fastboot-exe-unknown-option-i.895276/ fastboot R26 seems to work for the most i have the 34. platform-tools v 28.0.0 does not work with the provided command from the official manual.
Yes it was the version, it is the second time i try to mess with andriod phones. I learn more and more. I tried fastboot.exe i- 0x0fce getvar version and i got version 0.5, finished, total time 0.000s
I tried fastboot.exe -i 0x0fce oem unlock 0x and got FAILED, command not allowed. I did only find Sony L, L1 and L2 on sony oem https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code can it be that? I remeber i had a Sony Xperia X code.
I also tried fastboot flashing unlock, FAILED unknown command. with fastboot devices i got my phone visable.

Categories

Resources