Develop Bugs

Uncloking bootloader on h815

Hello team,
I've been trying to unlock the bootloader of my device for the last couple of days. I have tried installing the drivers from LG suite, couple of drivers from the forum and google as well.
When i try to type in the command line oem device-ID i get "waiting for device"
According to the internet this is an issue with the drivers.
Can anyone suggest suitable ADB drivers ?

gogobaba said:
Hello team,
I've been trying to unlock the bootloader of my device for the last couple of days. I have tried installing the drivers from LG suite, couple of drivers from the forum and google as well.
When i try to type in the command line oem device-ID i get "waiting for device"
According to the internet this is an issue with the drivers.
Can anyone suggest suitable ADB drivers ?
Click to expand...
Click to collapse
did you select usb debuggin in developers options.?
when you go iinto fastboot did you allow phone to acces adb in phone screen?

Yes to both of your questions. I'm using windows 10 x64 with the latest drivers for my laptop

Can't unlock bootloader. Device no longer detected the moment I open Mi Unlock Tool.

Sorry if this is the wrong thread.
Hello guys, I have a Redmi Note 5 (Global Version) with Snapdragon 636, and this phone is really amazing. I'd like however to unlock its booloader so I can install Pixel Experience on it, as I'd like to use other roms than MIUI. The issue is, well, I can't.
Something really strange happens: if I connect my phone via USB 2.0 to my computer, it is recognized as usual. It appears in Device Manager, is recognized by ADB, no problem. Then I reboot in fastboot mode and the device is still there. However, the EXACT moment I open Mi Unlock Tool, without clicking anything (Agree or logging in to my mi account) the phone is instantly disconnected and the "Press any key to shutdown" message appears on the top-left of my phone's screen.
Stuff I've tried:
- made sure OEM unlocking and USB debugging are on
- installed Mi Unlock tool in C:
- installed the ADB drivers in C:/Program Files
- disabled integrity checks from CMD
- installed and checked the MiUSBDriver umpteen times
- used 4 different versions of Mi Unlock Tool (1.0, 2.2, 2.3, and 3.3 - 1.0 halts at 50%, the other 3 won't detect my phone at all)
- made sure the device is bound to my Mi Account
I've tried using Hexerus' guide here (post #18) and everything seems to work fine, until step 6 when my phone instantly disconnects when opening Mi Unlock Tool.
Do you guys have any ideas? Thanks.

use usb 2.0 cable and port

devcon69 said:
use usb 2.0 cable and port
Click to expand...
Click to collapse
Used USB 2.0, didn't work

Happened with me before, and I looked Google and found some solutions like installing the drivers again and using old miunlock tool and using different USB Socket however, none of theme worked,
Next day I opened the laptop to try again and suddenly it worked!
I didn't know what exactly fixed it

After the 720 hours period, I have spent literally weeks of trying to unlock my device's bootloader and what I would add is to switch between computers. I'm running Windows 10 on my room computer and all I had with MiUnlock were errors such as device disconnecting once in fastboot, "Couldn't unlock" messages, chinese characters... Until I decided to use my 2005 Windows 7 desktop and wow !, device unlocked at first try ! No need any other trick

just uninstall Previous drivers or use Windows 7 PC,with latest drivers of ADB ,i also faced same problem:angel:

Redmi Note 8T drivers for Windows 7

I'm trying to connect my Note 8T to my windows 7 to use software such as mpcsuite, tool-all-in-one and others.
I'm struggling to do it, Windows won't recognise it. I've tried all the drivers I've found in this forum and also googling, but no luck. When I connect the phone it does configure some device automatically, but there's always one missing that I cannot find drivers for: TRINKET-IDP _SN:XXXXX
The thing is that if I go into fast boot, then Windows will find the phone just fine and I can for example run the MiFlash Unlock app, but not when the phone is in any other state.
I haven't tried other versions of Windows as I have no other.
any suggestion what I'm missing here?
thanks!

johnsecada said:
I'm trying to connect my Note 8T to my windows 7 to use software such as mpcsuite, tool-all-in-one and others.
I'm struggling to do it, Windows won't recognise it. I've tried all the drivers I've found in this forum and also googling, but no luck. When I connect the phone it does configure some device automatically, but there's always one missing that I cannot find drivers for: TRINKET-IDP _SN:XXXXX
The thing is that if I go into fast boot, then Windows will find the phone just fine and I can for example run the MiFlash Unlock app, but not when the phone is in any other state.
I haven't tried other versions of Windows as I have no other.
any suggestion what I'm missing here?
thanks!
Click to expand...
Click to collapse
download minimal ADB and Fastboot and turn on usb debugging from developer options. Also accept the popup on screen when you connect phone to PC after this

I have the same problem, have you succeeded ?
Thank you

I have the same issue with my Note 8T

i had the same problem with my note8. try to google around 1 hour. & that's the ones topic about it. unfortunately it has no answer poor me

johnsecada said:
I'm trying to connect my Note 8T to my windows 7 to use software such as mpcsuite, tool-all-in-one and others.
I'm struggling to do it, Windows won't recognise it. I've tried all the drivers I've found in this forum and also googling, but no luck. When I connect the phone it does configure some device automatically, but there's always one missing that I cannot find drivers for: TRINKET-IDP _SN:XXXXX
The thing is that if I go into fast boot, then Windows will find the phone just fine and I can for example run the MiFlash Unlock app, but not when the phone is in any other state.
I haven't tried other versions of Windows as I have no other.
any suggestion what I'm missing here?
thanks!
Click to expand...
Click to collapse
Try downloading the Xiaomi unlocking tool, I didn't have problems with drivers, but I saw a messages about downloading drivers and "Driver already installed" for my phone within the application log.
Give that a try!

But problem with Note 8. I don't remember when it started, but on crDroid 6 it definitely worked.
After that I notice in device manager what it determinate as some SAMSUNG Adb Device with Clock World driver. I had ADB Universal Driver installed, after uninstalled everything start work fine.

I have a similar problem with note 8t too. I have Windows 10 x64 and when i put the phone on fastboot mode and plug on the pc nothing happens, nothing shows on the device manager. When the phone is in normal mode the pc recognizes it normally. I want to unlock the bootloader to change the rom to the global version, but neither Mi unlock tool or Mi flash tool recognizes it. Any tips from anybody?

scarlos89 said:
I have a similar problem with note 8t too. I have Windows 10 x64 and when i put the phone on fastboot mode and plug on the pc nothing happens, nothing shows on the device manager. When the phone is in normal mode the pc recognizes it normally. I want to unlock the bootloader to change the rom to the global version, but neither Mi unlock tool or Mi flash tool recognizes it. Any tips from anybody?
Click to expand...
Click to collapse
Use W7
W10 always have problems with some driver signature

loopypalm said:
Use W7
W10 always have problems with some driver signature
Click to expand...
Click to collapse
Thank you very much. I've installed W7 and the pc recognized the cel on fastboot mode. Mi unlock recognize it too, but now i have a message to wait 149 hours to unlock the bootloader. Just have to wait now or have some way to skip this?
Again, thank you very much.

scarlos89 said:
Thank you very much. I've installed W7 and the pc recognized the cel on fastboot mode. Mi unlock recognize it too, but now i have a message to wait 149 hours to unlock the bootloader. Just have to wait now or have some way to skip this?
Again, thank you very much.
Click to expand...
Click to collapse
you have to wait

Motorola Moto G Fast (2020) - Rooting and Custom ROM Suggestions

Hey All,
I just got my first Android phone to have a bit of a project for my first root/custom ROM of a phone. I chose the Moto G Fast because it seems relatively easy to unlock the Motorola bootloader and such, but I am still new to this so I wanted to see if anybody here had any suggestions insofar as rooting goes and what custom ROM to use for the phone. Ideally I would like to use Lineage OS but Lineage 17 (current) does not support the Moto G Fast and the release date of Lineage 18 is yet to be announced. So does anybody here have any recommendations for a custom android ROM and maybe some tips/tricks when it comes to rooting/unlocking the bootloader?
Thank you in advance. Any and all advice is greatly appreciated.

Just a quick bump for this thread. I could use some suggestions/guidance.

To unlock your bootloader, follow the steps from this link: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Rooting is as easy as intalling recovery and flashing magisk.

Beetle84 said:
To unlock your bootloader, follow the steps from this link: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Rooting is as easy as intalling recovery and flashing magisk.
Click to expand...
Click to collapse
Thank you very much for the helpful info. I am looking through this now. I am curious as to whether or not there is a Linux equivalent to the Motorola USB drivers. I only see Windows/MacOSX.

Another issue that I've just come across is that the Android SDK cannot seem to find my phone when it is connected to my computer. When I run the command "fastboot oem get_unlock_data" I am met with a perpetual <waiting for any device> prompt. My phone does not show up in the file explorer or device manager either despite having downloaded the motorola drivers. Also, I have OEM unlock and usb debugging enabled. Does anyone have any ideas as to what the issue could be?

Just a quick bump for the day.

PrettyDumbITGuy said:
Another issue that I've just come across is that the Android SDK cannot seem to find my phone when it is connected to my computer. When I run the command "fastboot oem get_unlock_data" I am met with a perpetual <waiting for any device> prompt. My phone does not show up in the file explorer or device manager either despite having downloaded the motorola drivers. Also, I have OEM unlock and usb debugging enabled. Does anyone have any ideas as to what the issue could be?
Click to expand...
Click to collapse
I hate to ask the stupid question, but you did reboot to the bootloader before the unlock command right?
Otherwise, Linux issues aren't my thing, hopefully someone else can give you a hand there

Beetle84 said:
I hate to ask the stupid question, but you did reboot to the bootloader before the unlock command right?
Otherwise, Linux issues aren't my thing, hopefully someone else can give you a hand there
Click to expand...
Click to collapse
Not a stupid question at all. I am very new to phone rooting/android phones in general so the inquiry is warranted.
To answer your question, I did boot to the bootloader after enabling OEM unlock. When in fastboot mode I receive a green prompt that shows a connection and that the phone is in transfer mode. However, when I execute the commands in Android SDK to unlock the boot loader my computer is unable to locate the device. This problem occurs on both Windows and Manjaro Linux.

On windows 10 you have to disable driver verification I'm pretty sure for the fastboot drivers to work correctly. It's been awhile since I've done it so best bet is to google this.

Beetle84 said:
On windows 10 you have to disable driver verification I'm pretty sure for the fastboot drivers to work correctly. It's been awhile since I've done it so best bet is to google this.
Click to expand...
Click to collapse
I disabled driver verification with the following command "bcdedit /set testsigning off" and then connection my phone. The Win10 machine still does not detect the phone as a usable device. I receive a warning box with the following error "USB device not recognized. The last USB device you connected to this computer malfunctioned and Windows does not recognize it. "

PrettyDumbITGuy said:
.
Click to expand...
Click to collapse

PrettyDumbITGuy said:
Not a stupid question at all. I am very new to phone rooting/android phones in general so the inquiry is warranted.
To answer your question, I did boot to the bootloader after enabling OEM unlock. When in fastboot mode I receive a green prompt that shows a connection and that the phone is in transfer mode. However, when I execute the commands in Android SDK to unlock the boot loader my computer is unable to locate the device. This problem occurs on both Windows and Manjaro Linux.
Click to expand...
Click to collapse
Did you install android tools and android udev on Manjaro

BTK19 said:
Did you install android tools and android udev on Manjaro
Click to expand...
Click to collapse
Yes, I did. The problem I run into on Linux is much the same as the problem that I run into on WIndows. The computer simply does not recognize the phone as a device and the Android SDK tools do not detect the phone. I almost wonder if maybe something is wrong with the phone? Perhaps I purchased a defective device? I know that normally when you plug in your phone to a machine you receive a prompt on the phone asking you whether or not this is a "trusted device" but I receive no such prompt on my Moto G Fast. I'm almost wondering if I should just return the phone and get something else. Perhaps a Moto G8 power or maybe one of the new Nord line of One+ phones.

This may be redundant. But I suggest you try another cord. More often than not I find myself weeding through charge only cords till I find a data cord. Also try using a USB 2.0 port, preferably attached (rear of the computer) as opposed to any front ports or hub.

PrettyDumbITGuy said:
Hey All,
I just got my first Android phone to have a bit of a project for my first root/custom ROM of a phone. I chose the Moto G Fast because it seems relatively easy to unlock the Motorola bootloader and such, but I am still new to this so I wanted to see if anybody here had any suggestions insofar as rooting goes and what custom ROM to use for the phone. Ideally I would like to use Lineage OS but Lineage 17 (current) does not support the Moto G Fast and the release date of Lineage 18 is yet to be announced. So does anybody here have any recommendations for a custom android ROM and maybe some tips/tricks when it comes to rooting/unlocking the bootloader?
Thank you in advance. Any and all advice is greatly appreciated.
Click to expand...
Click to collapse
Unlocking my G Fast was Sooo easy, i asked Boost to unlock phone, no charge! then i 5apped UICC UNLOCK btn under About Phone, done & done.

Question Unlock OEM without a pc ?

Hello
I have a motorola moto e 2020 (xt2052-1 ginna_retail) and i do not own a computer i want to root it but unfortunately to do that there is the oem_locked in gray at the bootloader and as i understood correctly the only known way to root it its to unlock that oem by a pc and with motorola's code
But now i got a question to see if its possible to do it trought a computer emulator or virtual machine im a total noob and i dont want to fudge up my phone for 1controller module from magisk as its not otg compatible
I got termux to work but i dont know enough command to really have fun with it until now i got python and a adb fastboot install (well it says adb fastboot)
So if there is a way to do it without pc plz help me with this ... o_0
Thank you

If OEM unlock is grey the bootloader cannot be unlocked by any means.
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com

Imaunicorn666 said:
Hello
I have a motorola moto e 2020 (xt2052-1 ginna_retail) and i do not own a computer i want to root it
Click to expand...
Click to collapse
You cannot root without a PC either.

Imaunicorn666 said:
Hello
I have a motorola moto e 2020 (xt2052-1 ginna_retail) and i do not own a computer i want to root it but unfortunately to do that there is the oem_locked in gray at the bootloader and as i understood correctly the only known way to root it its to unlock that oem by a pc and with motorola's code
But now i got a question to see if its possible to do it trought a computer emulator or virtual machine im a total noob and i dont want to fudge up my phone for 1controller module from magisk as its not otg compatible
I got termux to work but i dont know enough command to really have fun with it until now i got python and a adb fastboot install (well it says adb fastboot)
So if there is a way to do it without pc plz help me with this ... o_0
Thank you
Click to expand...
Click to collapse
Not possible. Ask someone else but you will probably need a computer later again if something is not working and/or you want to go back. Before rooting be aware of topics like persistent corrupts and how to backup, Widevine L1 (Lost) (may be depending on the device and current os), Update while being rooted, Bricked devices and how to recover, SaftyNet Failure and PlayStore certification. I have a device which is rootet, has Widevine L1 and full SaftyNet/PlayStore Cert. so it's not impossible ;D

I managed to get it rooted and with twrp installed im a newbie and i STILL! dont want to fudge up my phone is there any good and working custom os for this device (motorola moto e 2020 xt2052-1 ginna_retail) thanks so much for the help

You can unlock the bootloader and root it with another rooted phone, an OTG cable, and the magisk ADB module. I've done it with the Moto E 2020, Moto G7 Play, Moto G8 Fast, and the Pixel 4a. Fastboot D and flashing stock firmware via OTG also works for all the phones I've listed.