Hi,
I just bought Mi A1.
Now, I wanted to install oreo.
So I was trying to root and install twrp.
Now I'm no expert, I just follow the provided steps and have been successful with past devices.
Note :
1) Developer enabled
2) oem unlocking enabled
3) usb debugging enabled
So I'm using this https://forum.xda-developers.com/mi...l-one-driversunlocktwrpfactory-t3695256/page2
But, there are two issues :
1) When I click on Reboot in fastboot/bootloader mode , it shows this in command prompt : http://prntscr.com/i2sn1o
and in the app, it automatically disconnects from the device http://prntscr.com/i2sncw
2) While this is happening and I leave my device, it automatically goes out from fastboot to power off charging mode.
I tried on another pc too, and followed the steps according to video, still no luck.
And I tried manual methods too, like https://www.youtube.com/watch?v=tRcYUMBgvaI
no luck there either.
Please help.
your adb driver is not installed correctly i guess, happened to me too.
try "adb devices" and will show no devices, if this happen, is the adb driver issue.
this fixed for me.
https://forum.xda-developers.com/showthread.php?p=75163858#post75163858
riccetto80 said:
your adb driver is not installed correctly i guess, happened to me too.
try "adb devices" and will show no devices, if this happen, is the adb driver issue.
this fixed for me.
https://forum.xda-developers.com/showthread.php?p=75163858#post75163858
Click to expand...
Click to collapse
I don't know if there is issue with driver. Because during installation there was no error.
Also, when I command "adb devices" it shows me a device as number.
So it is able to connect to the device then right?
You must install adb drivers AND fastboot drivers separately. I always had to install them manually via device manager. If your phone reboots from fastboot mode automatically, I'm 99% sure that you do not have drivers installed correctly.
_mysiak_ said:
You must install adb drivers AND fastboot drivers separately. I always had to install them manually via device manager. If your phone reboots from fastboot mode automatically, I'm 99% sure that you do not have drivers installed correctly.
Click to expand...
Click to collapse
Hmmmmm. Ok, I'll do that then. Thanks buddy. I'll try again and reply back asap.!!
Hi,
Despite my best efforts device manager still shows yellow at Android compesite device..
In ADB SHELL MODE it won't list the device on ADB DEVICES Command.
Can someone help me with the right USB / fastboot drivers for Mi A1 for Windows 10 Pro
Managed to get the fastboot working.
vu2pmc said:
Hi,
Despite my best efforts device manager still shows yellow at Android compesite device..
In ADB SHELL MODE it won't list the device on ADB DEVICES Command.
Can someone help me with the right USB / fastboot drivers for Mi A1 for Windows 10 Pro
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2588979
Compatibility mode, run as admin, you can also try with another source of adb files, because I had issues with the one from magisk manager.
Not working for me
Hi there,
i'd Like to flash the Ressurection Remix Oreo Rom, but i don't get it to unlock the bootloader. I'm on Stock A2017GV1.2.0B10 Nougat. TWRP and Backups are done, but when i try to unlock the Bootloader i geht this message in cmd:
adb: error: connect failed: no devices/emulators found
Tried with Zadigs Drivers, ADB divers are installed and it is showed as QS_Bulk.
Are there still some drivers missing or what am I doing wrong there???
Did you enable USB Debugging on your phone?
Victor13f said:
Did you enable USB Debugging on your phone?
Click to expand...
Click to collapse
Yes, i have OEM unlock and USB Debugging enabled. Dont understand why this is not working at all. Tried it many times, but every Try I get this message in the CMd. Sideload isn't working too...
Have you installed the Google USB drivers and checked in Device manager if everything is working okay? Here's a link to a guide: https://www.drivereasy.com/knowledge/solved-adb-device-not-found-error-on-windows/
HeikoNote3 said:
Yes, i have OEM unlock and USB Debugging enabled. Dont understand why this is not working at all. Tried it many times, but every Try I get this message in the CMd. Sideload isn't working too...
Click to expand...
Click to collapse
Just use the EDL Tool from @djkuz, install it, put your phone into EDL mode and unlock.
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
raystef66 said:
Just use the EDL Tool from @djkuz, install it, put your phone into EDL mode and unlock.
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Click to expand...
Click to collapse
So, Tried this one too. Doesn't work, phone isn't found, error adb interface not found...
HeikoNote3 said:
So, Tried this one too. Doesn't work, phone isn't found, error adb interface not found...
Click to expand...
Click to collapse
Uninstall all drivers you see relating to your phone (adb, usb...)
Try install : http://adbdriver.com/downloads/
And https://androidfilehost.com/?fid=24588232905723896
And see if you can perform with the EDL Tool again or adb
raystef66 said:
Uninstall all drivers you see relating to your phone (adb, usb...)
Try install : http://adbdriver.com/downloads/
And https://androidfilehost.com/?fid=24588232905723896
And see if you can perform with the EDL Tool again or adb
Click to expand...
Click to collapse
Installed the ADB Drivers but in EDL tool the Phone is not recognised. Dont know what could the Problem...
HeikoNote3 said:
Installed the ADB Drivers but in EDL tool the Phone is not recognised. Dont know what could the Problem...
Click to expand...
Click to collapse
First boot into twrp, connect your phone, run the EDL Tool. Normaly the tool should reboot itself into EDL mode
Or try : run EDL tool, instead of power off phone, hold vol down+power, connect usb, just do the same by holding the 3 buttons ( i did that once when my phone was in a state of 'shock' and the 2 button way didn't work)
Btw, did you install the 2 drivers i gave you ?
raystef66 said:
First boot into twrp, connect your phone, run the EDL Tool. Normaly the tool should reboot itself into EDL mode
Or try : run EDL tool, instead of power off phone, hold vol down+power, connect usb, just do the same by holding the 3 buttons ( i did that once when my phone was in a state of 'shock' and the 2 button way didn't work)
Btw, did you install the 2 drivers i gave you ?
Click to expand...
Click to collapse
Yes they're installed. I'm wondering that edl tool shows first ZTE ADB handset etc. And after boot into edl mode it shows no ADB interface... With axon7tool I can choose unlock Bootloader, then MI flash starts and then I don't know the files to flash for an unlock...
HeikoNote3 said:
Yes they're installed. I'm wondering that edl tool shows first ZTE ADB handset etc. And after boot into edl mode it shows no ADB interface... With axon7tool I can choose unlock Bootloader, then MI flash starts and then I don't know the files to flash for an unlock...
Click to expand...
Click to collapse
MiFlash? Where did you read that you had to use MiFlash? ?
You need to use EDL Tool
Edit: Okay, I think I got it. You thought "EDL Tool" was actually axon7toolkit. Well, it isn't. Axon7toolkit, axon7tool, and EDL Tool are 3 different things
Choose an username... said:
MiFlash? Where did you read that you had to use MiFlash?
You need to use EDL Tool
Edit: Okay, I think I got it. You thought "EDL Tool" was actually axon7toolkit. Well, it isn't. Axon7toolkit, axon7tool, and EDL Tool are 3 different things
Click to expand...
Click to collapse
OK, then which tool should I prefer now? In EDL tool I was on a good way to unlock the Bootloader, but when I choose Yes, the unlock begins with load programmer something and stucks until I reboot EDL mode. Then it gives me an error message with: your device could be in Sahara mode. I don't understand anything anymore. Tried every driver, every tool but nothing will work. That drives me crazy...
HeikoNote3 said:
OK, then which tool should I prefer now? In EDL tool I was on a good way to unlock the Bootloader, but when I choose Yes, the unlock begins with load programmer something and stucks until I reboot EDL mode. Then it gives me an error message with: your device could be in Sahara mode. I don't understand anything anymore. Tried every driver, every tool but nothing will work. That drives me crazy...
Click to expand...
Click to collapse
Did you enable OEM unlock and USB debugging?
If you did and it still does that error, just use the manual method and follow Controllerboy's guide. That one uses axon7tool, which is much more finicky and ran by commands, but it works
Thanks for all Tipps. Finally did it. Running RR Oreo!
Hi there,
My device(Nokia 6) is detected by PC(win 10) when it is On but not detecting in the fastboot mode. It doesn't respond for any commands. Also, I'm not able to install ROM using OST.
Please help me in this regard.
Thank you.
sasikiranskl said:
Hi there,
My device(Nokia 6) is detected by PC(win 10) when it is On but not detecting in the fastboot mode. It doesn't respond for any commands. Also, I'm not able to install ROM using OST.
Please help me in this regard.
Thank you.
Click to expand...
Click to collapse
Enable usb debugging mode in developer options .
And and after connecting give permission or allow it
Hello Everyone,
I would like to install fastboot ROM on Redmi Note 7 and my PC cannot recognized it on fastboot mode. I almost tried everything like intall 5sec fastboot driver and latest fastbott drivers but it didn't work. I sincerely ask you guys how can I solve it.
Thank you so much
saonaylinn said:
Hello Everyone,
I would like to install fastboot ROM on Redmi Note 7 and my PC cannot recognized it on fastboot mode. I almost tried everything like intall 5sec fastboot driver and latest fastbott drivers but it didn't work. I sincerely ask you guys how can I solve it.
Thank you so much
Click to expand...
Click to collapse
Install Miflash +drivers.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
and/or
https://avalonsciences.com/wp-conte...Signature-Verification-on-Windows-8-or-10.pdf
I recently started having trouble sideloading updates through ADB. I was using Win 11, PowerShell and had Bitdefender installed as anti-virus. However, I had no problem on a Win 10 machines using the same programs.
To fix it on my primary Win 11 machine, I disconnected from internet after my download of the OTA, killed BitDefender, and used a Command window instead of PowerShell. That worked for me.
Granted fastboot is different than ADB, but it could be the same problem. Also make sure your Platform Tools is up to date.