Related
Hello!
I'm from Puerto Rico, my carrier is Claro PR. I've been trying to root my device but so far I haven't even been able to unlock the Bootloader. I get the annoying and indefinite < waiting for device > message on the Fastboot CMD screen. I have installed ADB drivers from Google and it didn't help since the Motorola drivers did not even recognize my device in Fastboot. It seems that the only time my device is recognized in Fastboot mode is when there are no ADB or Fastboot drivers installed and Device Manager lists it as a Fasboot Titan device. Quite honestly this is very frustrating since I've been searching for days to no avail. I do not wish to update to Lollipop(Until it is available officially in my area), which is what most articles I found are for. I just want root access. I'm beginning to doubt if my device is even supported and its just an extremely well made clone.
I was trying this on Windows 8.1 Pro x64. Some people told me Fastboot drivers had some issues with 8.1 so I did my best to clean out old drivers and plug the phone into different USB ports. At first I was trying on my USB 3.0 ports, people also told me USB 3.0 has issues with FB, so I used my 2.0 ports on the front of my computer case. Again, people told me that I had to use ports directly on the motherboard, so I plugged the phone into my PC's back USB ports. I also tried a different micro USB cable, same result. At that time I figured it was probably Windows causing the problems so I pulled a hard drive from and old PC, hooked it up to my own and installed my old copy of Windows 7 Ultimate x64. I installed all the essentials, from ADB to Motorola Device Manager for the drivers. My phone is still not being recognized, although I did get to have it listed under ADB Devices by using USB Debugging, yet it appears offline, as shown in the image below. I figured it was my particular PC because its custom built with salvaged parts from another PC, so I tried the procedure from my family's Dell Optiplex (running win7 Home Premium x32) only to hit the same dead-end. At this point I'm tearing off hair from my head. I don't want to be bald yet! I'm only just turning 20 at the end of the month!
A few details:
Device: Moto G 2014 16GB XT1063. Android Kitkat 4.4.4 (5.0 has yet to be released for my area)
System Version: 21.11.14.titan_amxpr.amxpr.en.PR amxpr
Build number: KXB21.85-14
Inquisitor956 said:
yet it appears offline
Click to expand...
Click to collapse
If you connect your device with usb-debugging enabled in the developer options, a dialog pops up, presenting a RSA fingerprint, asking to allow usb-debugging. If not, type "adb version" in your terminal. If version is below 1.0.31 you have to update adb.
doppelhelix said:
If you connect your device with usb-debugging enabled in the developer options, a dialog pops up, presenting a RSA fingerprint, asking to allow usb-debugging. If not, type "adb version" in your terminal. If version is below 1.0.31 you have to update adb.
Click to expand...
Click to collapse
Thanks solved a problem I had on other laptop that would not show phone
doppelhelix said:
If you connect your device with usb-debugging enabled in the developer options, a dialog pops up, presenting a RSA fingerprint, asking to allow usb-debugging. If not, type "adb version" in your terminal. If version is below 1.0.31 you have to update adb.
Click to expand...
Click to collapse
Thank you! The RSA Fingerprint popup never appeared on my phone. I kept toggling USB Debugging on and off until it did. I managed to get the keys. Now I hit another wall... (image below)
I also tried it onto the Latin America page. This time no matter how I paste my code whether manually typing it or just copy/pasting, it always returns a popup with "Your input text was not recognized as a valid dataset. Please try again." This happens on Chrome, Firefox and even Internet Explorer and combined with the really slow loading of any official Motorola page I try to enter I'm guessing the forces of life itself are preventing me from unlocking this particular phone's Bootloader.
Inquisitor956 said:
preventing me from unlocking this particular phone's Bootloader.
Click to expand...
Click to collapse
Please have a look here: https://forums.motorola.com/posts/f2061da875
doppelhelix said:
Please have a look here:
Click to expand...
Click to collapse
Thank you once again! My device IS unlockable, I was told to wait for some time before requesting my unique unlock key, since the page has been having a few hiccups. I will report back if I was successful or not.
Edit: I successfully unlocked bootloader, installed TWRP and rooted. Thank you for your assistance!
So apparently, I bought a 5X with A1 only ported onto it.
I tried installing GCam, and it's now the biggest mistake of my life. My phone is now booting only up to the MI logo for a quick second, and then it dies.
I believe the bootloader is locked and my device is NOT rooted. If it helps, USB debugging & OEM unlocking are both on.
Is there a way to fix this? I was hoping I could flash this over with something but I don't know how.
I am on a quest to root my phone and i want to unlock bootloader ect... since no application can do this i need to use adb fastboot
i am using a chromebook Acer 15 developer options open all that etc...(i beileve all needed) when moto e5 plus plugged in by data usb cord and tryin to connect by adb devices command it gives me a List of devices attached
ZL522BQ46M unauthorized (did same for my lg g6 but not a galaxy or zte) also it doesnt show up in my files as a attached device or outside storage unit but about 10 mins prior to this it had shown up as attaced but kept dis connecting causing multipule file windows to apper. i hace searched it multiple times on many diffrent acasions and have tried many "fixes" please can i get some assistance.
Enabled developer options
System->About Phone-> Scroll to bottom and TAP on BUILD 5x (I believe)
then go back once , Developer options , Enable USB DEBUGGING , Authorize your Device and you should be able to proceed onto the bootloader unlocking guide on Motorola's Website
whodat711 said:
Enabled developer options
System->About Phone-> Scroll to bottom and TAP on BUILD 5x (I believe)
then go back once , Developer options , Enable USB DEBUGGING , Authorize your Device and you should be able to proceed onto the bootloader unlocking guide on Motorola's Website
Click to expand...
Click to collapse
Still not working. Re set the Chromebook even rest the phone. Did everything from the start did the Linux applications restarted the Chromebook didn't go with the Linux applications even got the ADB extensions for the Chromebook and nothing will work still says no permissions when it pulls up the phone I don't know. This isn't like I'm totally brand new to this just never used a Chromebook thanks for your help anyway
i solved the issue with the no permissions in adb. a few minor issues i should of noticed and actually taking the time to think the problem through solved it......
but i somewhere messed up when rooting my phone (shouldnt of been drinking and thought i could still do it...) and know i am in a reboot coming out of my bootloader... will not boot into my recovery whrn it dows its only for a few seconds and the command lines runnung it says that script is finishing but it quickly reboots to a black screen that says bad key and reboots then says n a on it. fastboot will not do anything but say waiting on device. so...... i guess i got a project for a few days
Hello everyone,
I've decided to unlock my device to flash vanilla android but I couldn't unlock it. I've tried almost everything but even the latest MiUnlock doesn't recognize my device on fastboot, the PC itself recognizes it before and after getting into fastboot, I hear usb device connected sound and can see the phone under Windows devices.
Adb devices command works if the phone is switched on, my dev settings are ok, oem unlocking and adding account under dev settings are ok, I've tried it with disabled windows signature enforcement too but nothing happened. MiUnlock simply doesn't want to see the device on fastboot.
Can anybody help me, please?
abstra said:
Hello everyone,
I've decided to unlock my device to flash vanilla android but I couldn't unlock it. I've tried almost everything but even the latest MiUnlock doesn't recognize my device on fastboot, the PC itself recognizes it before and after getting into fastboot, I hear usb device connected sound and can see the phone under Windows devices.
Adb devices command works if the phone is switched on, my dev settings are ok, oem unlocking and adding account under dev settings are ok, I've tried it with disabled windows signature enforcement too but nothing happened. MiUnlock simply doesn't want to see the device on fastboot.
Can anybody help me, please?
Click to expand...
Click to collapse
The issue that you are experiencing is strictly with your PC.
You need to ensure that you are using an account that has admin privileges, and be sure that you antivirus is not neutering your usb drivers and Miflash program.
Next, if you are using a newer computer with usb 3 ports, you will need to use a USB hub ( USB 2 is your best option.) , then the phone will be seen in fastboot. As long as you have setup developer options, and your MiCloud account is setup.
Finally, it will take 2 weeks to unlock the bootloader , after your first request. Some people who had been syncing the phone to MiCloud for some time before attempting were able to immediately unlock. Personally we have 3 Mi8's in our house and I had to wait 2 weeks on each one.
To reiterate, your main issue is probably the usb ports, and your antivirus the the 2nd most likely culprit. Worst case use another computer. The process is much easier on older PC's.
you can use the the All in one tool to double check that your drivers, adb , and system wide privileges are up to date and setup correctly. https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Instructions are available on that thread.
Thanks for your help, I've already tried almost everything you've said up there and even gave a try on virtualbox Windows 7 with USB 2.0 setup.
I remember I've unlocked my friend's device last year on an only USB 2.0 computer, my laptop has unfortunately only two 3.0s and one USB-C. The phone can be seen under fastboot devices command if MiUnlock is not running, if I click on that cr*p program my device either falls from fastboot devices list or says press any key to shutdown.
The main problem is the ports and that damned program itself, how come it lockdowns the connection and after that pc couldn't even show my phone in devices list but can be seen in device manager. I'm literally shocked by the cheapness of this very software.
abstra said:
Thanks for your help, I've already tried almost everything you've said up there and even gave a try on virtualbox Windows 7 with USB 2.0 setup.
I remember I've unlocked my friend's device last year on an only USB 2.0 computer, my laptop has unfortunately only two 3.0s and one USB-C. The phone can be seen under fastboot devices command if MiUnlock is not running, if I click on that cr*p program my device either falls from fastboot devices list or says press any key to shutdown.
The main problem is the ports and that damned program itself, how come it lockdowns the connection and after that pc couldn't even show my phone in devices list but can be seen in device manager. I'm literally shocked by the cheapness of this very software.
Click to expand...
Click to collapse
Again the issue is with windows, I have personally dealt with the exact same issue. That is why I recommended using an older computer that has not been recently updated.
But you are absolutely right, Xiaomi has not made any development improvements with their desktop applications in over a year and that is ridiculous.
I would suggest using alternate versions of the software : I just did a google search and on this link people were saying just one week ago that this linked software worked for them, note its a video, the software link is in the description : https://www.youtube.com/watch?v=l_PEAJ-n2_c
Finally, I am personally using this version of Mi Flash : https://androidfilehost.com/?fid=11410932744536991669 on a brand new intel PC.
and the last time that I unlocked a xiaomi phone I used unlocker software from here ( Note the multiple versions at bottom of page)
https://mi-globe.com/download-xiaomi-mi-unlock-tool-all-versions/
If one doesn't work try another. just be sure that you have developer options setup correctly and that you are signed in a syncing with mi-cloud. You will get it unlocked eventually. I can assure you that it was a Pain in the A*$ for me too!
Thanks man, these are the exactly same links I’ve found and checked out while trying to connect my phone but I just gave up after three days of struggling and pressing volume+power buttons and ordered a USB 2.0 hub online. Unfortunately there are no older computers around me or anyone I can ask for because of you know, the quarantine. I’m actually using cloud actively, so I should better be prepared for an immediate unlocking, and backup my data beforehand as usual.
Just wanted to write about the news, I've backed up my data and connected my device to MiUnlock on USB 2.0 Hub and ta-da it's immediately unlocked without any waiting time. That was a smooth process, I'm shocked but happy.
abstra said:
Just wanted to write about the news, I've backed up my data and connected my device to MiUnlock on USB 2.0 Hub and ta-da it's immediately unlocked without any waiting time. That was a smooth process, I'm shocked but happy.
Click to expand...
Click to collapse
Nice, so my original suggestion about using 2.0 usb was correct. I am glad that you have the issue sorted. I am also surprised about you being able to avoid the wait time. That is a nice break. Enjoy your phone.
PS: Be sure to make a full TWRP backup and save it to your desktop. That backup will save you if you ever experience a bad issue.
tsongming said:
Nice, so my original suggestion about using 2.0 usb was correct. I am glad that you have the issue sorted. I am also surprised about you being able to avoid the wait time. That is a nice break. Enjoy your phone.
PS: Be sure to make a full TWRP backup and save it to your desktop. That backup will save you if you ever experience a bad issue.
Click to expand...
Click to collapse
Thanks man, and yes that was all about fastboot which is written to be used with older usb versions. After plugging in the hub, it’s connected directly in just milliseconds. I am surprised that I’ve really skipped the waiting for two weeks or maybe more and yeah it makes me happy.
I made a full data backup before unlocking and then all the dangerous partitions including modem, efs and bluetooth in TWRP to avoid any irreversible loss. I never skip my recovery backups since 2010 and my first Android smartphone which was an HTC Desire A8181, I learned it in a hard way to never skip them, if you do, you either lose your data or your mobile device identification. :victory:
A question from a Xiaomi-newbie; If I run clean all and lock command on MiFlash, should I wait for an unknown time to unlock the device again? Or does Xiaomi let users to lock/unlock their devices anytime without waiting if you’ve unlocked your bootloader once before?
abstra said:
Thanks man, and yes that was all about fastboot which is written to be used with older usb versions. After plugging in the hub, it’s connected directly in just milliseconds. I am surprised that I’ve really skipped the waiting for two weeks or maybe more and yeah it makes me happy.
I made a full data backup before unlocking and then all the dangerous partitions including modem, efs and bluetooth in TWRP to avoid any irreversible loss. I never skip my recovery backups since 2010 and my first Android smartphone which was an HTC Desire A8181, I learned it in a hard way to never skip them, if you do, you either lose your data or your mobile device identification. :victory:
A question from a Xiaomi-newbie; If I run clean all and lock command on MiFlash, should I wait for an unknown time to unlock the device again? Or does Xiaomi let users to lock/unlock their devices anytime without waiting if you’ve unlocked your bootloader once before?
Click to expand...
Click to collapse
I have only unlocked my device once. But I wouldn't think there would be an issue to unlock a second time. In fact, I have read about some people needing to wait 72 hours to unlock it again after relocking. if using Mi-Flash just try to be sure uncheck that lock bootloader box, that is unless you want it locked.
One last thing, if you ever decide to restore the phone using the flashall.bat method, the bootloader stays unlocked.
Good morning everyone. I Just bought my redmi note 10 pro, but whether i try to unlock the bootloader via mi unlock or Xiaomi tool V2, It gives 20038 unknown error, haven't found anything on the web, hope someone can help me.
RawKnighy said:
Good morning everyone. I Just bought my redmi note 10 pro, but whether i try to unlock the bootloader via mi unlock or Xiaomi tool V2, It gives 20038 unknown error, haven't found anything on the web, hope someone can help me.
Click to expand...
Click to collapse
hi!! did u check first of all the developer options on your device?..
oem unlock on....then,bootloader unlock status(with wifi off add your device with your accont on it) and then usb debug on
Yeah, did everything...
adversario71 said:
hi!! did u check first of all the developer options on your device?..
oem unlock on....then,bootloader unlock status(with wifi off add your device with your accont on it) and then usb debug on
Click to expand...
Click to collapse
Maybe try updating android drivers on your PC, I also had an error and updating fixed it.
Please check wether your Sim is activated with MI servers.
I already unlocked my Pro Max on Sunday
chandruilkal said:
Please check wether your Sim is activated with MI servers.
Click to expand...
Click to collapse
How do i check that?
Okay nevermind got It,everything activated, dunno what's the problem for real, getting so confused.
Reinsert the sim in different slot and try
I generally connect the cable to my phone first and then connect cable to PC. Looks strange but sometimes works wonders.
Nothing, seems like a server IMEI or id problem...Not really know what It does mean though
I have the same problem. With the latest mi unlock-en-5.5.224.24 my phone is not recognized. Under barrel boat I can see my phone and also have it displayed. But not in the unlock app. I did everything according to the instructions:
1) Mi account linked (settings / mi account)
2) developer options
-oem unlock
- automatic system updates
- usb debugging
- install via usb
- time limit for adb
3) Mi account unlock
- Wlan off / sim on
- klik unlock account connected
4) Staten Mi Unlock app
- sign up for an account
- get sms
- confirm
5) switch off the device
- fastboot mode on
- first cable into the phone then to the laptop
- original cable used
Mi unlock app does not recognize the phone. Tried all drivers. The XiaomiMiToolV2 recognizes the phone. However, when I tried, my waiting time was set back to 168 hours. Should I now just wait 7 days and then try again with the tool ?! Why does he not recognize the phone in fast boat mode? It is displayed in the Windows device manager. in the shell i can find it under fastboot. USB Android driver from google or xiaomi made no difference. Anyone have an idea?
1000 thanks in advance