Related
Hello all!
I recently bought a second hand Xiaomi MI A2 online however I found a problem.
The previous owner did a factory reset on it but I'm stuck in the initial set up configuration because it asks me for the google account credentials attached to the phone. I texted the previous owner but had no answer.
So I tried to flash the official ROM to bypass the issue but I get an error message from Xiaomi Flash Tool saying "remote: Flash is not allowed in Lock State".
I think this is happening for one of the following reasons:
The previous owner didn't enable USB Debugging (thing I can't do because I'm stuck in the set up configuration)
The bootloader is locked (and I can't unlock it because I don't have the credentials of the attached account)
Does anyone knows how can I solve this problem?
Thank you for your attention
Joaosacramento said:
Hello all!
I recently bought a second hand Xiaomi MI A2 online however I found a problem.
The previous owner did a factory reset on it but I'm stuck in the initial set up configuration because it asks me for the google account credentials attached to the phone. I texted the previous owner but had no answer.
So I tried to flash the official ROM to bypass the issue but I get an error message from Xiaomi Flash Tool saying "remote: Flash is not allowed in Lock State".
I think this is happening for one of the following reasons:
The previous owner didn't enable USB Debugging (thing I can't do because I'm stuck in the set up configuration)
The bootloader is locked (and I can't unlock it because I don't have the credentials of the attached account)
Does anyone knows how can I solve this problem?
Thank you for your attention
Click to expand...
Click to collapse
Maybe you can see/ask in this thread for mia2 toolkit (I'm not sure but you can ask there )
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
daitalos said:
Maybe you can see/ask in this thread for mia2 toolkit (I'm not sure but you can ask there )
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
Click to expand...
Click to collapse
Thank you, will give it a try!
EDIT: Not working, every time I try to execute the unlock I got an error message "remote: Flashing Unlock is not allowed"
Joaosacramento said:
Thank you, will give it a try!
EDIT: Not working, every time I try to execute the unlock I got an error message "remote: Flashing Unlock is not allowed"
Click to expand...
Click to collapse
(yes...normally, first you must enable "OEM unlocking" from developer option
_ https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unlock-bootloader-xiaomi-t3831484
__but first for your problem with locked device, see here for FRP apk : https://www.google.gr/search?q=com.....69i57j0l5.14869j0j8&sourceid=chrome&ie=UTF-8
__and here frp mia2 : https://www.google.gr/search?q=frp+.....69i57j0l3.7035j0j8&sourceid=chrome&ie=UTF-8
first "unlock" your device & then you can unlock bootloader easy ....
sry for english
Just unlock bootloader(critical too) and use miflash
I also have a Mi A2 stuck in android logo screen can't can't boot into device developer options to unlock bootloader.
Fastboot oem unlock give me error flashing is not allowed.
Is there anyway around this?
You need to do an unlock of critical partitions - "fastboot flashing unlock_critical"
daitalos said:
(yes...normally, first you must enable "OEM unlocking" from developer option
_ https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unlock-bootloader-xiaomi-t3831484
__but first for your problem with locked device, see here for FRP apk : https://www.google.gr/search?q=com.....69i57j0l5.14869j0j8&sourceid=chrome&ie=UTF-8
__and here frp mia2 : https://www.google.gr/search?q=frp+.....69i57j0l3.7035j0j8&sourceid=chrome&ie=UTF-8
first "unlock" your device & then you can unlock bootloader easy ....
sry for english
Click to expand...
Click to collapse
Hey! It worked, thank you very much!
Face_11 said:
I also have a Mi A2 stuck in android logo screen can't can't boot into device developer options to unlock bootloader.
Fastboot oem unlock give me error flashing is not allowed.
Is there anyway around this?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
(or flash stock rom via mi flash tool/ fastboot files) : http://en.miui.com/download-353.html
follow / read fastboot quide : http://en.miui.com/a-234.html
daitalos said:
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
(or flash stock rom via mi flash tool/ fastboot files) : http://en.miui.com/download-353.html
follow / read fastboot quide : http://en.miui.com/a-234.html
Click to expand...
Click to collapse
Thanks. I've tried the MIFlash Tool and I get Error Flashing Not allowed in Lock State. I've also tried the MI A2 ToolKit and get the same message. Basically anything I try and do states device is locked or unable to run in Lock State.
Boot Loader is currently locked and I cannot access developer mode to enable OEM unlocking. Question I have is :
- Can I use EDL Cable to work around this or do EDL cables not longer work with Newer Xiaomi phones?
- If EDL cable doesn't work, is the tespoint method my only option.
thanks in advance
Face_11 said:
Thanks. I've tried the MIFlash Tool and I get Error Flashing Not allowed in Lock State. I've also tried the MI A2 ToolKit and get the same message. Basically anything I try and do states device is locked or unable to run in Lock State.
Boot Loader is currently locked and I cannot access developer mode to enable OEM unlocking. Question I have is :
- Can I use EDL Cable to work around this or do EDL cables not longer work with Newer Xiaomi phones?
- If EDL cable doesn't work, is the tespoint method my only option.
thanks in advance
Click to expand...
Click to collapse
yes it's difficult .... I understand
edl maybe work, but I'm not sure...maybe if you go to a repair shop is a better solution
(see & here : https://forum.xda-developers.com/mi-a2/help/edl-deep-flash-cable-t3828732 )
https://youtu.be/n_7RVmW2Rvs
https://forum.xda-developers.com/showpost.php?p=77327325&postcount=2
Gl
Face_11 said:
Thanks. I've tried the MIFlash Tool and I get Error Flashing Not allowed in Lock State. I've also tried the MI A2 ToolKit and get the same message. Basically anything I try and do states device is locked or unable to run in Lock State.
Boot Loader is currently locked and I cannot access developer mode to enable OEM unlocking. Question I have is :
- Can I use EDL Cable to work around this or do EDL cables not longer work with Newer Xiaomi phones?
- If EDL cable doesn't work, is the tespoint method my only option.
thanks in advance
Click to expand...
Click to collapse
I would try a wipe from the recovery but if that doesnt work then just test point the phone. It isnt that hard, I had to do it myself today because of a soft brick. You just need a T3 screwdriver really. Take out the 2 bottom screws. Take a razor and slide it under the corner of the display and lift it enough the get a credit card in there. Then just work around and you should be able to get the screen off. Take the small metal plate off just above the battery and disconnect the battery and the connector on the right. There will be the test points, short them out, connect the phone to the pc(you can stop shorting out the points when it gets detected) and you have like 10-15secs to start flashing the phone in miflash(obviously you need to have the drivers already set up).
I have same problem with xiaomi mi a2 which had bootloop. Was not able to start device at all so no oem unloco no developer options and no usb debug. It was possible only adb sideload and fastboot. Adb sideload did nothing. I was trying to flash with adb sideload but it stops at 47% with message 1.00 x. Did try several roms with same results. Then i tried fastboot options. Falied to unlock not allowed. Itsl was impossible to get even into phone to activate developer options so i can activate oem unlock and the rest. I tried edl mode which did flash but then i got error message in bootloader it failed to mount system etc. Then i tried mi x6 rom to convert phone to another which doesnt have usual recovery mode but a stripped oem recovery mode. Now when u go back to mi a2 rom its bricked so there is no option of adb at all now. I tried to use mi x6 mi assistant option but app wont recognize usb connection it shows try normal mode then switch. When activating mi assistant on phone it does recognize rom version from recovefy flash in mi assistant app but when it downloads update rom version it cant continue. With pixel you can do anything with adb and it is so easy but xiaomi sucks big time. You cant do anything. Fastboot flashing unlock critical and fastboot oem unlock gets error failed. Flashing not allowed. U tried diferent cables but no luck. So now what? Thats why i hate adb. On samsung odin you can do impossible possible. Even with sp tools on mtk. Even boxes works flawlessly but xiaomi system is just thr worse. It doesnt matter if you get soemthing lost there is always a solution to other phones.
After having device sit as a paper weight for a few months, i broke down and ordered a phone repair kit. Opened device up and flashed via test point method. Worked Flawless. Time to enable OEM unlock so i don't have to open it up again. Thanks to community for all the help.
Use cmd
- go to fastboot then "fastboot oem unlock"
- go to fastboot again "fastboot flashing unlock_critical"
Flash with mi flash
Done
Just stumbled upon this and while may be 18 months too late, here's the step by step process to flash ROM on MI A2 that's giving error "Flash is not allowed in Lock State":
1) switch off device
2) enter fastbood mode (press hold power+vol down few seconds)
3) connect device with laptop
4) install and open adb folder on laptop (https://forum.xda-developers.com/showthread.php?t=2588979)
5) within adb folder -- shift + right click = open powershell here
6) fastboot flashing unlock_critical
7) step #6 may be pointless if phone is bricked but do it anyway
8) fastboot oem edl
9) find and download latest stock rom for your device (FASTBOOT version). It'll be .tgz file
10) extract the image folder from within (would be the same name as .tgz file)
11) open miflash (coudln't find link but look it up, it's easy)
12 select the image folder you extracted in step #10
13) click refresh. device name appear means it's recognized
14) from bottom of mi flash tool select whatever you want. I do "clean all"
15) flash (top right mi flash tool)
Face_11 said:
Thanks. I've tried the MIFlash Tool and I get Error Flashing Not allowed in Lock State. I've also tried the MI A2 ToolKit and get the same message. Basically anything I try and do states device is locked or unable to run in Lock State.
Boot Loader is currently locked and I cannot access developer mode to enable OEM unlocking. Question I have is :
- Can I use EDL Cable to work around this or do EDL cables not longer work with Newer Xiaomi phones?
- If EDL cable doesn't work, is the tespoint method my only option.
thanks in advance
Click to expand...
Click to collapse
Flashing is not allowed in lock state
i got a error recently in my mi a2 no software is installed but locked.
when i try to flash from mi flash tool it says flashing is not allowed in lock state
when i try to unlock in cmd flashing is not allowed in lock state
is there any one to fix this
IamUmesh said:
i got a error recently in my mi a2 no software is installed but locked.
when i try to flash from mi flash tool it says flashing is not allowed in lock state
when i try to unlock in cmd flashing is not allowed in lock state
is there any one to fix this
Click to expand...
Click to collapse
you need to open phone with screwdriver & do the test point ..search for video on YouTube...then EDL deepflash state you can use miflash to put back OFFICIAL only rom to device.
[GUIDE]HOW TO INSTALL CUSTOM RECOVERY, UNLOCK BOOTLOADER & UPDATE FIRMWARE IN Dec2019
I SOLVED THEM MYSELF, GUIDE WILL BE POST WHEN I CAN POST A THREAD
*i posted them here
INITIAL POST
Unable/failed to unlock bootloader/fastboot
It's been 8 hours and I have literally tried everything even to my own method but none of them worked (I follow all tutorial and guidance perfectly on both xda and from a article and youtube). When I click the unlock.cmd, it just flash quickly (probably open command prompt in split second) and do nothing (I had checked with a command; fastboot oem device-info). Then I tried click again and it just stopped at support all device. The folder location is on C aka main storage, I have installed all the required stuff and I'm on 6gb variant. I even wipe clean my phone and it is on Android Pie. Trying to unlock this bootloader is driving me insane. Official TWRP app does not have my variant (M1) instead they have M2 so I doubt I can use flash recovery from there. I just wanted to install TWRP and Havoc OS with Magisk and root. My phone is legit, I have warranty and all that. I just want to unlock my bootloader and able to relock it for future warranty use.
To clarify things further, I have no issues with ADB displaying on Device Manager and I can see Bootloader on Device Manager without any warning sign. I even switch the cable (both are data cable) and for some reason it only worked on usb 3.0 port. I also had tried all connection mode (PTP (no MTP), USB Tethering, File Transfer and nothing). I had make sure I had installed the driver too and my PC already have ADB but I installed them thrice anyway.
EDIT1: I just noticed my warranty had expired so I decided to officially unlock the bootloader and it was a success but I still can't use fastboot command to flash TWRP (fastboot flash recovery twrp bla bla.img) and it does run the command just failed.
EDIT2: Alright it was solved!
I had already written a guide on how to solve it but I couldn't post it.
I AM POSTING THIS HERE BECAUSE XDA SUCKS, I COULDNT POST A NEW THREAD SO HERE WE GO.
HOW TO INSTALL CUSTOM RECOVERY, UNLOCK BOOTLOADER AND INSTALL FIRMWARE IN LATE 2019
*last update 8 december 2019
#I AM NOT RESPONSIBLE FOR HARD BRICK OR SOFT BRICK OF YOUR DEVICE SO TRY AT YOUR OWN RISK AND FOLLOW WITH CAUTION
*this is based on my personal experience of my continuous effort in reading, researching, testing, tweaking all for the past few weeks
*note this is a guide specifically for these problems
-my post on how I failed to unlock bootloader
-command write failed
-phone not detected in bootloader
-adb or bootloader driver showing error on device manager
-other guides not working on amd rig
-unable to flash recovery
-phone not detected in adb
-etc
CUSTOM RECOVERY
#DO NOT INSTALL ORANGE FOX, YOU WILL GET ERROR 7 UPON FLASHING VARIOUS CUSTOM ROM
TWRP
*you can install orange fox later on by dirty flashing it (install without wiping your data)
*lastest one is 3.3.1.0
ADB & FASTBOOT
15 seconds ADB
*this is a system wide adb, there is no need for 'cd' command and you can just use straight up use adb or fastboot command and uninstall other adb along with their drivers because other adb wouldn't work and use outdated client and driver
HOW TO UNLOCK BOOTLOADER
#THIS IS AN UNOFFICIAL WAY TO UNLOCK YOUR BOOTLOADER, I HAVENT TESTED THIS MYSELF
Download this
1. Do not use your stock charger, get data cable or third party one
2. You may need to connect your cable to USB 3.0/3.1 port (blue one)
* if it didn't work, you may need to use USB Hub (even cheap one will work)
3. Open up your CMD (search cmd or use powershell if you like on windows search)
4. Type adb reboot bootloader in cmd or .\adb reboot bootloader in powershell
5. Extract the rar you downloaded
6. Go to unlock folder and double click on unlock.cmd
*if these didn't work then you can officially unlock it (if you unlock it officially, your warranty is really now voided and can't lock back bootloader)
#OFFICIAL WAY TO UNLOCK YOUR BOOTLOADER (two ways)
Method 1
1. Open your cmd or powershell
2. Type adb reboot bootloader in cmd or .\adb reboot bootloader in powershell if you haven't enter fastboot or bootloader
3. Type fastboot oem unlock in cmd or .\fastboot oem unlock in powershell
Method 2
1. Download this on your phone
2. Run it and done
##CHECK TO SEE IF IT SUCCEED OR NOT BY TYPING FASTBOOT OEM DEVICE-INFO IN CMD OR .\FASTBOOT OEM DEVICE-INFO IN POWERSHELL AND MAKE SURE THE COMMAND IS IN LOWERCASE
HOW TO INSTALL CUSTOM RECOVERY
1. Boot to bootloader by either using command or power off then hold both power button and volume up button then release power button when phone vibrate
2. Open your cmd or powershell
3. Copy your custom recovery img name with .img
*it should look like this; twrp-3.3.1-0-X00T-20190526.img
3. Type fastboot flash recovery [paste it here]
*wait 1 minute or longer
4. Boot into recovery by holding both power button and volume down button then release power button when the phone vibrate
TROUBLESHOOT
Use command fastboot fastboot devices (when in bootloader) and adb devices (when device is on systemui/not in bootloader)
A: If the device shows random alphabet or number like JADSHFE2849 then your device is detected
B: If it doesn't, try changing usb port and wires
*remember to put .\ at the front of every command when using powershell
*cmd is command prompt
HOW TO INSTALL FIRMWARE (two ways)
#WARNING THIS OFFICIAL WAY WILL REVERT YOUR CUSTOM RECOVERY INTO STOCK ONE
*doing this will wipe out your internal data
OFFICIAL WAY
1. Download latest firmware here to your sd card
*remember to set your region first by scroll down to bottom left near the language otherwise it wouldn't work or worse, may brick your device
2. Wipe clean your rom (wipe system, data, etc but not vendor)
3. Boot into system even when no OS is available
4. Complete the setup
5. Boot into recovery
6. Apply update from external storage
7. Browse to your download location and tap it
8. Wait around 10 minute - 15 minute for it to finish
9. Congrats, your firmware has been updated and you can proceed to flash custom recovery again
UNOFFICIAL WAY
Flash this on your custom recovery
*direct link if you prefer but may be outdated as time goes on {Mod edit: Link remove}
Looks like you need to use windows 7 with USB 2.0 port. Or wait till warranty runs out and unlock using official app.
What processor does your system has?
Ryzen? Goodluck with that then.
Fastboot driver doesnt work on amd ryzen builds
Same problem here...
Not even on usb 2.0 ports
gdarshan said:
What processor does your system has?
Ryzen? Goodluck with that then.
Fastboot driver doesnt work on amd ryzen builds
Same problem here...
Not even on usb 2.0 ports
Click to expand...
Click to collapse
Ah shoot, yeah I have Ryzen 3 2200g paired with GTX 1050 Ti and Windows 10 Pro.
Vysair said:
Ah shoot, yeah I have Ryzen 3 2200g paired with GTX 1050 Ti and Windows 10 Pro.
Click to expand...
Click to collapse
Ooooooo...... I have ryzen3 2200g(my new pc) and i tried to flash fastboot rom on azmpm1 but after trying almost 3hours i can't abale to flash it, before i have intel pentium and i flashed fastboot rom without a single problem
---------- Post added at 06:20 PM ---------- Previous post was at 05:56 PM ----------
Read this for quick work arround>>
https://www.reddit.com/r/Amd/commen..._source=amp&utm_medium=&utm_content=post_body
Rommaster94 said:
Ooooooo...... I have ryzen3 2200g(my new pc) and i tried to flash fastboot rom on azmpm1 but after trying almost 3hours i can't abale to flash it, before i have intel pentium and i flashed fastboot rom without a single problem
---------- Post added at 06:20 PM ---------- Previous post was at 05:56 PM ----------
Read this for quick work arround>>
https://www.reddit.com/r/Amd/commen..._source=amp&utm_medium=&utm_content=post_body
Click to expand...
Click to collapse
I still don't know how I did it but I use platform tools from google and it worked because the platform tools use the very latest adb client (around 60 or something). I do install something else like sdk tools and twrp 3310 but i had no idea why it worked which is why i havent post link for guidance. I suspect it was only because of my platform tools. (also for windows 10, i doubt you need those adb drivers bull****)
EDIT: I found a better solution, install 15 seconds adb. This is universal ADB and can be use on any directory but I recommend you to delete the drivers and older ADB beforehand.
Hi. Thank you very much for posting this, I'd been frustrated trying to install drivers but somehow I couldn't get it right. I found this and installed the 15secondADB thing, tested a few commands and everything seems to work. I'm just wondering whether I'll need to install any more drivers in order to start flashing staff through Fastboot.
Thank you in advance
Kevo0h said:
Hi. Thank you very much for posting this, I'd been frustrated trying to install drivers but somehow I couldn't get it right. I found this and installed the 15secondADB thing, tested a few commands and everything seems to work. I'm just wondering whether I'll need to install any more drivers in order to start flashing staff through Fastboot.
Thank you in advance
Click to expand...
Click to collapse
I'm glad it helped. For the driver, there's no need for it because 15 seconds ADB should have installed the required driver or update it. However, I recommend you to try do windows update check to install any missing driver just in case. (I haven't tested this myself though since there's no driver to install from there)
Moderator Announcement
Thread cleaned from download links via pling.com!
pling.com is a paid-per-download website, as such violating rule no. 13 of the XDA Forum Rules and therefore not accepted as file host on XDA. Please refrain from sharing those links in future! Thanks for your cooperation.
Stay safe and stay healthy!
Regards
Oswald Boelcke
Forum Moderator
Hi everyone!
I need help, please.
Xiaomi Redmi 4A - 2/16 Gb. Boot unlocked.
Problem after flashing miui 11 with error:
1. TWRP - don`t aviable now and I can`t flash it;
2. Fastboot - I can enter in Fastboot mode, but smartphone not detected by computer (win 7/64) and notebook (win 10/32). all drivers - ADB, Quallcom - installed correctly;
3. I try to enter EDL mode - with two test points on a motherboard. I tried to connect them - without effect - my PC and Notebook can`t detect device...
What can I do ?
Try my suggestions
If you have another smartphone please download apk
https://play.google.com/store/apps/details?id=eu.sisik.hackendebug
Bring your bricked phone to fastboot mode. Using bugjaeger apk you can flash and anyhow you told that bootloader is unlocked if your bootloader is locked then whole procedure will not work
I am providing YouTube link try it
https://youtu.be/G_E8ImOoQZM
Video is about 7:54 Watch the video 4:00 carefully
Dont Flash any custom ROM or recovery
flash all files which is in stock ROM only (zip or rar or tgz)
and don't lock bootloader.
After flashing try to restart phone
If the procedure didn't work
Sorry for wasting your time.
Hello,
I was trying to unlock bootloader and root my device (Redmi Note 9; Mediatek processor). But even after ensuring everything required to unlock, the latest mi unlock tool (miflash unlock tool; Ver: 4.5.707.49 and even miflash unlock tool; Ver 4.5.514.47) can't detect my device while it is in fastboot mode. What is interesting is I tried with older version (miflash unlock tool; Ver: 3.3.525.23) and it detects my device while it is in fastboot mode. But after approaching to unlocking, at the end of the process (99%) it says, can't unlock device, please go to https://en.miui.com/unlock/ and try with the latest version (where it should grant me few hours to wait until I become eligible to unlock it. I've ensured the followings:
I've installed all the required drivers (xiaomi, usb, ADB, fastboot, qualcom)
Enabled OEM unlocking and USB debugging on the device in developer option
I've bind the phone (in developer option>> mi unlock status) with the same mi account the phone is bind with
I've logged in the mi unlock tool with the same mi account
I've tried with the latest mi unlock tool and even with the older versions
my PC is a 64 bit windows 10 installed intel PC (I've heared ADM pcs' causes problem sometimes)
Disabled signature driver enforcement
Restarting the device and computer multiple times
Re installing drivers over and over again
What's going wrong or what wrong am I doing? Can anyone please help?
Try selecting the driver manually by yourself.
Go to device manager, and try to update it.
After it, select anything like "android bootloader" in list.
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
shaan3010 said:
Hello,
I was trying to unlock bootloader and root my device (Redmi Note 9; Mediatek processor). But even after ensuring everything required to unlock, the latest mi unlock tool (miflash unlock tool; Ver: 4.5.707.49 and even miflash unlock tool; Ver 4.5.514.47) can't detect my device while it is in fastboot mode. What is interesting is I tried with older version (miflash unlock tool; Ver: 3.3.525.23) and it detects my device while it is in fastboot mode. But after approaching to unlocking, at the end of the process (99%) it says, can't unlock device, please go to https://en.miui.com/unlock/ and try with the latest version (where it should grant me few hours to wait until I become eligible to unlock it. I've ensured the followings:
I've installed all the required drivers (xiaomi, usb, ADB, fastboot, qualcom)
Enabled OEM unlocking and USB debugging on the device in developer option
I've bind the phone (in developer option>> mi unlock status) with the same mi account the phone is bind with
I've logged in the mi unlock tool with the same mi account
I've tried with the latest mi unlock tool and even with the older versions
my PC is a 64 bit windows 10 installed intel PC (I've heared ADM pcs' causes problem sometimes)
Disabled signature driver enforcement
Restarting the device and computer multiple times
Re installing drivers over and over again
What's going wrong or what wrong am I doing? Can anyone please help?
Click to expand...
Click to collapse
You can check in device manager. Your phone should be on the top. If it is in portable devices then you can select it and then click on update driver manually.
After doing it go to platform tools folder(if you have them), type adb devices
If you device serial number is shown then its good to go.
If it is showing unauthorised then type the command
"adb reboot bootloader"
Now it will be authorised
shaan3010 said:
Hello,
I was trying to unlock bootloader and root my device (Redmi Note 9; Mediatek processor). But even after ensuring everything required to unlock, the latest mi unlock tool (miflash unlock tool; Ver: 4.5.707.49 and even miflash unlock tool; Ver 4.5.514.47) can't detect my device while it is in fastboot mode. What is interesting is I tried with older version (miflash unlock tool; Ver: 3.3.525.23) and it detects my device while it is in fastboot mode. But after approaching to unlocking, at the end of the process (99%) it says, can't unlock device, please go to https://en.miui.com/unlock/ and try with the latest version (where it should grant me few hours to wait until I become eligible to unlock it. I've ensured the followings:
I've installed all the required drivers (xiaomi, usb, ADB, fastboot, qualcom)
Enabled OEM unlocking and USB debugging on the device in developer option
I've bind the phone (in developer option>> mi unlock status) with the same mi account the phone is bind with
I've logged in the mi unlock tool with the same mi account
I've tried with the latest mi unlock tool and even with the older versions
my PC is a 64 bit windows 10 installed intel PC (I've heared ADM pcs' causes problem sometimes)
Disabled signature driver enforcement
Restarting the device and computer multiple times
Re installing drivers over and over again
What's going wrong or what wrong am I doing? Can anyone please help?
Click to expand...
Click to collapse
will this work
Manjotbenipal said:
You can check in device manager. Your phone should be on the top. If it is in portable devices then you can select it and then click on update driver manually.
After doing it go to platform tools folder(if you have them), type adb devices
If you device serial number is shown then its good to go.
If it is showing unauthorised then type the command
"adb reboot bootloader"
Now it will be authorised
Click to expand...
Click to collapse
Hi Manjotbenipal,
My device shows the 'serial number unauthorised', but when I tried the 'adb reboot bootloader' & 'adb devices' nothing is listed.
Thanks
troybarbas said:
Hi Manjotbenipal,
My device shows the 'serial number unauthorised', but when I tried the 'adb reboot bootloader' & 'adb devices' nothing is listed.
Thanks
Click to expand...
Click to collapse
All good now 'serial number device' is now shown after the phone restarted.
But still the Mi Unlock ver 6.5.406.31 software does not enable the unlock when in fastboot mode.
'adb device' show no devices...
troybarbas said:
All good now 'serial number device' is now shown after the phone restarted.
But still the Mi Unlock ver 6.5.406.31 software does not enable the unlock when in fastboot mode.
'adb device' show no devices..
Click to expand...
Click to collapse
When in fastboot mode
Type 'fastboot devices' in cmd and then you'll be able to see if you have proper drivers installed
Note : adb and fastboot are not same
'adb devices' command will never work in fastboot mode and same is for 'fastboot devices' when device is booted
shaan3010 said:
Hello,
I was trying to unlock bootloader and root my device (Redmi Note 9; Mediatek processor). But even after ensuring everything required to unlock, the latest mi unlock tool (miflash unlock tool; Ver: 4.5.707.49 and even miflash unlock tool; Ver 4.5.514.47) can't detect my device while it is in fastboot mode. What is interesting is I tried with older version (miflash unlock tool; Ver: 3.3.525.23) and it detects my device while it is in fastboot mode. But after approaching to unlocking, at the end of the process (99%) it says, can't unlock device, please go to https://en.miui.com/unlock/ and try with the latest version (where it should grant me few hours to wait until I become eligible to unlock it. I've ensured the followings:
I've installed all the required drivers (xiaomi, usb, ADB, fastboot, qualcom)
Enabled OEM unlocking and USB debugging on the device in developer option
I've bind the phone (in developer option>> mi unlock status) with the same mi account the phone is bind with
I've logged in the mi unlock tool with the same mi account
I've tried with the latest mi unlock tool and even with the older versions
my PC is a 64 bit windows 10 installed intel PC (I've heared ADM pcs' causes problem sometimes)
Disabled signature driver enforcement
Restarting the device and computer multiple times
Re installing drivers over and over again
What's going wrong or what wrong am I doing? Can anyone please help?
Click to expand...
Click to collapse
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows/releases/latest/download/Latest-ADB-Installer.bat
Download this. Connect your device with usb debuging on and permitted debug.
Run the bat file with an internet connection. Wait and walah. Device will reboot to fastboot and reboot again.
Manjotbenipal said:
When in fastboot mode
Type 'fastboot devices' in cmd and then you'll be able to see if you have proper drivers installed
Note : adb and fastboot are not same
'adb devices' command will never work in fastboot mode and same is for 'fastboot devices' when device is booted
Click to expand...
Click to collapse
understood..
I followed this guide https://new.c.mi.com/global/post/101245
"You have already done that on the phone, so you should get Phone connected message on Mi Unlock. If you get Not connected to the phone message, reinstall Mi USB driver and try again."
Currently device is using winusb.sys driver, ran (Mi Unlock ver 6.5.406.31) MiUsbDriver & xiaomiwinusba64.cat, but still Windows 11 keeps using winusb.sys driver...for some reason.
troybarbas said:
understood..
I followed this guide https://new.c.mi.com/global/post/101245
"You have already done that on the phone, so you should get Phone connected message on Mi Unlock. If you get Not connected to the phone message, reinstall Mi USB driver and try again."
Currently device is using winusb.sys driver, ran (Mi Unlock ver 6.5.406.31) MiUsbDriver & xiaomiwinusba64.cat, but still Windows 11 keeps using winusb.sys driver...for some reason.
Click to expand...
Click to collapse
What is winusb.sys and How to Remove this file (Solved)
in just easy steps learn how to remove winusb.sys file, get full information and solutions for winusb.sys errors
www.exedb.com
I am not responsible if this breaks more stuff
LR7875 said:
What is winusb.sys and How to Remove this file (Solved)
in just easy steps learn how to remove winusb.sys file, get full information and solutions for winusb.sys errors
www.exedb.com
I am not responsible if this breaks more stuff
Click to expand...
Click to collapse
so too is regedit in removing winusb.
Hi Guys,
I have a pixel 4a 5G. I managed to install the CalyxOS bramble on the phone.
There where some bugs with this OS so I wanted to switch to lineageOS.
Since a few days I´m trying to install the OS.
The issues is that abd is not finding my device.
Fastboot somehow finds my devices and I was able to "fastboot flashing unlock" to unlock the phone.
Fastboot is also only working while I’m in the boot option menu.
When I’m leaving to Recovery Mode my device is not even recognized by fastboot.
Somehow, I can´t even get to the normal OS anymore to enable USB Debugging.
What I have tried:
Reinstall the drivers. (once manually and once via Android Studio in the SDK options)
Tried following Linux OS with preinstalled drivers (same issue - fastboot works in boot option - abd not): https://forum.xda-developers.com/t/...-installation-and-driver-issues-v3-2.3526755/
Download the latest platform tools.
Different PC.
Google service to install the default OS. Same issues when the API tried to boot to fastboot menu connection to the pc was gone.
What else can I try?
thanks for any help!
synced21 said:
Hi Guys,
I have a pixel 4a 5G. I managed to install the CalyxOS bramble on the phone.
There where some bugs with this OS so I wanted to switch to lineageOS.
Since a few days I´m trying to install the OS.
The issues is that abd is not finding my device.
Fastboot somehow finds my devices and I was able to "fastboot flashing unlock" to unlock the phone.
Fastboot is also only working while I’m in the boot option menu.
When I’m leaving to Recovery Mode my device is not even recognized by fastboot.
Somehow, I can´t even get to the normal OS anymore to enable USB Debugging.
What I have tried:
Reinstall the drivers. (once manually and once via Android Studio in the SDK options)
Tried following Linux OS with preinstalled drivers (same issue - fastboot works in boot option - abd not): https://forum.xda-developers.com/t/...-installation-and-driver-issues-v3-2.3526755/
Download the latest platform tools.
Different PC.
Google service to install the default OS. Same issues when the API tried to boot to fastboot menu connection to the pc was gone.
What else can I try?
thanks for any help!
Click to expand...
Click to collapse
Try a different cable.
houtx2 said:
Try a different cable.
Click to expand...
Click to collapse
houtx2 said:
Try a different cable.
Click to expand...
Click to collapse
i ordered a new one. anyway this is the original cable which was in the pixel box.
i got it had to plug it in and out in recvory mode.... **** this device