my mi a3 is not recognized when in fastboot mode by the computer
I had this problem just some couple of hours ago and what you have to do (or at least it solved this in my end) is go to Manage Devices, scroll to TP-Link Android Phone, expand it and right click Android Bootloader Interface and uninstall without deleting the driver, then refresh for hardware changes and it will install the driver again and fastboot will work this time.
Jhon_Locke said:
I had this problem just some couple of hours ago and what you have to do (or at least it solved this in my end) is go to Manage Devices, scroll to TP-Link Android Phone, expand it and right click Android Bootloader Interface and uninstall without deleting the driver, then refresh for hardware changes and it will install the driver again and fastboot will work this time.
Click to expand...
Click to collapse
I'm facing this same issue. Please can you tell me where I can see Manage Devices on my computer? I'm using Windows 10.
I had the same issue. I tried all the methods that i researched. Even tried virtual machines running Windows 7 and Linux but same thing happens. I thought it was a Windows 10 issue. Til 1 day i tried to use a different cable, and DAMN! that fixed it.
same here, recognized as adb device but not recognized by fastboot.
I'm using Linux and fastboot work well.
The problem is that with lsusb no device is displayed, so I think it's a bootloader issue, is the bootloader environment corrupted? is there other setting to enable other then enable usb debug and enable OEM unlock?
Go to device manager right klik on android device and update the driver automatic.thats all.
U had the same problem and i solved with this.
Probably you don't have installed correctly fastboot drivers
Barbiox Dogg said:
I'm facing this same issue. Please can you tell me where I can see Manage Devices on my computer? I'm using Windows 10
Click to expand...
Click to collapse
im late but if u still need to know then hold down windows and x, a list should come up and then click device manager from there
deniloo said:
my mi a3 is not recognized when in fastboot mode by the computer
Click to expand...
Click to collapse
Just Update the device driver probably be showing under others in Device manager.
Visit this site to get the driver for your device. https://www.getdroidtips.com/download-latest-xiaomi-usb-drivers/
Dears,
How has this issue just "disable driver signature enforcement"
Search youtube on this and follow instruction
Say thanks if it help please,
Related
Hello, I hope you can help me solve the following problem.
When I try to connect Folio 100 to my PC, this is not recognized as a device and I can not start the adb.
Adb All information displayed in universal bus driver and not as a device.
I suspect there is an error with the driver used by Windows 7, but not how to fix it.
If anyone has a solution, I would be grateful if you share with me.
Greetings to everyone who has read this message
underwear69 said:
Hello, I hope you can help me solve the following problem.
When I try to connect Folio 100 to my PC, this is not recognized as a device and I can not start the adb.
Adb All information displayed in universal bus driver and not as a device.
I suspect there is an error with the driver used by Windows 7, but not how to fix it.
If anyone has a solution, I would be grateful if you share with me.
Greetings to everyone who has read this message
Click to expand...
Click to collapse
http://forums.computers.toshiba-europe.com/forums/thread.jspa?messageID=224451
Error: you do not have permission to view the requested forum or category.
even after creating a profile and login to the site
Use my ADB guide.
i have tried that but it doesn't recognize the driver as new/better and does not install it.
anyone ?
i still can't use the usb driver also not with the adb guide mentioned above
try using the "pdanet" software, it works for me
found it on android for dummier (guess i am)
reboot folio
press power 3 times on boot
and volume up once
install driver on windows
worked !
Jon2555 said:
Use my ADB guide.
Click to expand...
Click to collapse
I can't go into specifics - but having dealt with over 30 seperate folio's for a certain company beginning with t and rhyming with froshiba, I can confirm sometimes a device may just not work and be recognised by a windows machine. Not worked out what causes it, but ADB just can't see the device. Put it on a different windows machine and it will work perfectly. I believe putting it in fastboot mode does get round that, but when working in the OS mode you are pretty stuffed unless you change computer.
Cable6P said:
found it on android for dummier (guess i am)
reboot folio
press power 3 times on boot
and volume up once
install driver on windows
worked !
Click to expand...
Click to collapse
It worked for me right until I restart my folio to get out of fast boot then the device is gone from android adb devices. Any idea why?
hmmm and again it is connected, driver is right loaded, but fastboot and adb don't see the folio....
Basically my phone stops being recognized by the computer once I reboot into the bootloader. To be clear, the phone is recognized just fine and shows up when I type 'adb devices' when the phone is operating in the android os. Seeing that all is well there, I proceed to 'adb reboot bootloader' and it appropriately reboots to the white screen with the android on it. But there the problems begin: It reads on the screen:
FASTBOOT&RESCUE MODE
Please Connect Usb Cable to
Your Computer and Open Hisuite
More information:
the huawei website
Then it displays the droid
Then it says:
Phone Locked
FRP Unlock
I tried going ahead and running 'fastboot oem unlock ###...' but it just sits there waiting for a device to be connected. I have tried multiple USB drivers on my 2 windows 10 computers. I have removed all drivers using USBdeview and tried different drivers. Windows will not allow me to point to manualy choose my driver, instead saying, 'The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems.' So I tried it on an old 32-bit windows 7 system. No joy. I've tried multiple USB cords and ports. In windows device manager it has the device labeled as 'Kedacom USB Device' -> 'Android Bootloader Interface'. I can't figure out what's going wrong other than to say it seems that Windows is not using the correct driver once it enters the bootloader. PLEASE HELP!!!
Surely you have a drivers problem.
Are you using Huawei or Google adb drivers?
I couldn't find any Huawei drivers. So I used the drivers from Android developer site and several others I found here on XDA. If you have a link for specific Huawei drivers that would be AWESOME!
Try HiSuite.
Sent from my Galaxy Tab 3 using XDA Labs
ajalogan said:
I couldn't find any Huawei drivers. So I used the drivers from Android developer site and several others I found here on XDA. If you have a link for specific Huawei drivers that would be AWESOME!
Click to expand...
Click to collapse
Have you tried this?
http://semantic.gs/huawei_handset_adb_interface_driver_download
Google ADB should be fine.
i just unlocked bootloader few hours ago... i using adb driver from this thread , and it worked for me http://forum.xda-developers.com/showthread.php?t=2588979
and i also installed HIsuite before that...
seii3 said:
i just unlocked bootloader few hours ago... i using adb driver from this thread , and it worked for me http://forum.xda-developers.com/showthread.php?t=2588979
and i also installed HIsuite before that...
Click to expand...
Click to collapse
Did you used Huawei oficial site to get unlock code or did you used a 3rd party method?
zinko_pt said:
Did you used Huawei oficial site to get unlock code or did you used a 3rd party method?
Click to expand...
Click to collapse
Huawei official website
same issue, different flavor....
I'm having this issue as well, on a debian system. I have good ADB connectivity, all ADB commands seem to work fine. With fastboot, I get a device listed form them fastboot devices command. After that all fastboot commands are "waiting for device". If this is a driver issue, any hints on how to install those drivers in Linux/Debian? I tried a number of google searches, and have found all sorts of information, but nothing telling me where to put which files where to get the working drivers. Any hints?
Are you on Windows? Check if the device manager shows the device as Android with an exclamation mark inside a yellow triangle.
The problem could be with Windows 8.1/10.
Try with Windows 7
Here are the official drivers for Windows x64, ripped from Hisuite:
Mediafire | MEGA
Windows 10 is fine, it's what I use and have zero problems. Most of the time is other software that conflicts.
I'm facing the exact same issue (using Windows 10). I did the oem unlock using the code from Huawei. However after connecting the phone via cable to the PC, it does not allow me to browse the storage (internal or SD card) of the phone. All I see is a device named KIW-L24 which appears as an empty folder, and a virtual CD drive HiSuite. I installed HiSuite and the software shows me the photos/apps/etc. however there is no way to move files from the PC to the phone storage. Any pointers to the process to install the right drivers?
can you give me the link for huawei official win X32 drivers pls?!
Install hisuite , it will install all huawei drivers that u needed
I have just got my phone today and have spent 5 hours trying to get to the point where the mi unlock software tells me to wait 72 hours.
I put my phone in fastboot mode and as soon as I connect it to the computer it disappears. Tried 5000 different ways to do this and even
wiped my pc with a clean install of windows but no matter what my phone is not recognized in the unlock tool. Please steer me in the right direction.
I'm sure I'm not the first person with this issue.
If I remember correctly, the unlock tool has an installable driver in the settings option. That should make the phone detectable in fastboot
satan89 said:
If I remember correctly, the unlock tool has an installable driver in the settings option. That should make the phone detectable in fastboot
Click to expand...
Click to collapse
yeah I did that
Apgibby said:
yeah I did that
Click to expand...
Click to collapse
You see the problem is within windows 10. I boot phone in fastboot mode
and my phone goes to a black screen and phone becomes unrecognized in windows.
Try using another computer, windows 7 if possible. Otherwise try using another usb cable
thunderskain said:
Try using another computer, windows 7 if possible. Otherwise try using another usb cable
Click to expand...
Click to collapse
no extra usb c cable I will install windows 7 on spare hard drive and try it again will post findings when done. thanks
I was facing the same issue, go to Device manager in Windows 10. In the View tab enable show hidden devices, then you should see Android Phone on the top. Click the right arrow and uninstall drivers under Android phone, connect your phone again and the drivers should be installed.
Windows 10 should detect your device in Fastboot mode now onwards.
Unkn0wNx said:
I was facing the same issue, go to Device manager in Windows 10. In the View tab enable show hidden devices, then you should see Android Phone on the top. Click the right arrow and uninstall drivers under Android phone, connect your phone again and the drivers should be installed.
Windows 10 should detect your device in Fastboot mode now onwards.
Click to expand...
Click to collapse
I did that and the minute I launched the unlocker the green fastboot went away and it says press any key to shut down.
Apgibby said:
I did that and the minute I launched the unlocker the green fastboot went away and it says press any key to shut down.
Click to expand...
Click to collapse
unlocker said proper driver installed but install screen stays greyed out. What a pain the butt this is.
If I recall it right you just have to go to the mi unlock site and apply, the unlock is bouund to the mi account.
Have you tried a different usb port? Heard pocophone is finicky on usb 3.0, maybe use a usb 2.0 port.
Try another USB port. It solved for me.
Apgibby said:
unlocker said proper driver installed but install screen stays greyed out. What a pain the butt this is.
Click to expand...
Click to collapse
If you are using AMD RYZEN, it won't recognise the phone. Use Intel or other AMD machines.
tnsmani said:
If you are using AMD RYZEN, it won't recognise the phone. Use Intel or other AMD machines.
Click to expand...
Click to collapse
no amd here running intel 8 series chipset tried all 6 available usb ports.
Apgibby said:
no amd here running intel 8 series chipset tried all 6 available usb ports.
Click to expand...
Click to collapse
Then try another PC/Laptop.
Apgibby said:
You see the problem is within windows 10. I boot phone in fastboot mode
and my phone goes to a black screen and phone becomes unrecognized in windows.
Click to expand...
Click to collapse
All my Xiaomi phones, including Poco F1, are recognized in Windows 10, and I've unlocked them all in Windows 10. So it shouldn't be Windows.
Why is your phone going to a black screen when you boot in fastboot mode ?
I don't know how to solve your problem though. I reboot my phone into fastboot while not connected to the PC, and it surely will show the fastboot animation screen. Then I plug in the cable to the PC, and the unlock tool will start its work.
Maybe redownload the MI unlocker tool ... or create a new MI account and re-bind that account under developer options ...
unlocking boot loader will wipe all the data right?
That is correct. You need to wait 3 days when unlocking the bootloader. That is Xiaomi's waiting period for the Pocophone.
Better than Samsung's 7 day wait, and better than LG's way of having to request an unlock key.
Sent from my POCOPHONE F1 using Tapatalk
@Apgibby
Are you putting the phone in bootloader mode, connect it to the PC and then opening the Mi Unlocker? The correct sequence is open the Unlocker, put your phone in bootloader mode and then connect it to the PC. Try it.
If still not working, open the adb command window on your PC, put your phone in bootloader mode and connect it to the PC. Now type "fastboot devices" (without the quotation marks). You should get a serial number with alphabets and numerals. If you get it, it is confirmation that your drivers for bootloader are working. Try this and let us know the result.
Lastly, try another PC.
Solved used windows 7 with usb 2.0 ports.
I've waited 17 days after linking my Mi account to my Mi8L. I've unlocked more than half a dozen Xiaomi phones, so it's not new to me. However, it stops at 99% and spits out an error message in Chinese. Does anyone know what it means? https://drive.google.com/open?id=1dl6tPZdx7HfFwxQWel3hhjl9doFE5s8S
It means you haven't been using the phone for the necessary amount of time, so unlock isn't possible.
You're probably on a shop or chinese variant that need you to wait 30 days until unlocking.
Sorry for my bad english
Also, check this thread:
http://en.miui.com/thread-4456547-1-1.html
Snowdine said:
It means you haven't been using the phone for the necessary amount of time, so unlock isn't possible. You're probably on a shop or chinese variant that need you to wait 30 days until unlocking.
Click to expand...
Click to collapse
It's strange because when I tried previously, it told me I had to wait 15 days, and I waited longer than that (I took note of the date and time).
Same with me.
Use Mi Unlock 2.3.803.10 (old version).
Works perfectly.
I do not know if you can help me, I was unlocking the Mi 8 Lite requested 15 days to wait after this period I was unlocking and to my surprise the fastboot mode when I connect the USB cable it erases and I can not unlock.
Developer options enabled, usb debugging enabled and oem unlocking also recognizes more when I log in to fastboot it shuts off
rinampa said:
I do not know if you can help me, I was unlocking the Mi 8 Lite requested 15 days to wait after this period I was unlocking and to my surprise the fastboot mode when I connect the USB cable it erases and I can not unlock.
Developer options enabled, usb debugging enabled and oem unlocking also recognizes more when I log in to fastboot it shuts off
Click to expand...
Click to collapse
Try starting the process from adb, don´t use hardware buttons and see what happens.
With device on connect to pc and pay attention that pops up a message "Allow USB debugging" then tap on "always allow" and "ok".
Now type
Code:
adb devices
to see if pc is recognicing and if it is ok type
Code:
adb reboot bootloader
.
Open normally MiFlash Unlock and sign in to your account and follow the scrren on instructions. Provide some screenshots if something fails.
SubwayChamp said:
Try starting the process from adb, don´t use hardware buttons and see what happens.
With device on connect to pc and pay attention that pops up a message "Allow USB debugging" then tap on "always allow" and "ok".
Now type
Code:
adb devices
to see if pc is recognicing and if it is ok type
Code:
adb reboot bootloader
.
Open normally MiFlash Unlock and sign in to your account and follow the scrren on instructions. Provide some screenshots if something fails.
Click to expand...
Click to collapse
Do you have adb and drives for my 8 lite?
rinampa said:
Do you have adb and drives for my 8 lite?
Click to expand...
Click to collapse
Download from here SDK Platform Tools and unzip it preferably in your main drive, you can do all the adb/fastboot processes inside this folder for easier task: https://developer.android.com/studio/releases/platform-tools
And here they´re the USB drivers for our device, choose from Mi 8, it´s the same https://www.xiaomigeek.com/download-xiaomi-usb-driver-windows.html
SubwayChamp said:
Download from here SDK Platform Tools and unzip it preferably in your main drive, you can do all the adb/fastboot processes inside this folder for easier task: https://developer.android.com/studio/releases/platform-tools
And here they´re the USB drivers for our device, choose from Mi 8, it´s the same https://www.xiaomigeek.com/download-xiaomi-usb-driver-windows.html
Click to expand...
Click to collapse
Unfortunately I do not know what happens adb fastboot does not work, I did all the procedure I rebooted in option 7 I installed adb drive the curious one and that the pc recognizes the device opens the internal storage is difficult, I have always unlocked my devices.
rinampa said:
Unfortunately I do not know what happens adb fastboot does not work, I did all the procedure I rebooted in option 7 I installed adb drive the curious one and that the pc recognizes the device opens the internal storage is difficult, I have always unlocked my devices.
Click to expand...
Click to collapse
I'm not sure if you're doing it rightly. Adb works when device is on and fastboot when device is in bootloader/fastboot mode.
When you type for first time adb devices with device power on then you have to see a message from your android screen asking if you want to allow USB debugging, you have to tap on always allow and then in ok.
Provide some screenshot from your pc to see the fail.
SubwayChamp said:
I'm not sure if you're doing it rightly. Adb works when device is on and fastboot when device is in bootloader/fastboot mode.
When you type for first time adb devices with device power on then you have to see a message from your android screen asking if you want to allow USB debugging, you have to tap on always allow and then in ok.
Provide some screenshot from your pc to see the fail.
Click to expand...
Click to collapse
Yes I am aware I have experience always unlocked my gadgets something strange here on my pc or on the device I will try on another pc thank you attention you are correct, thank you.
SubwayChamp said:
Try starting the process from adb, don´t use hardware buttons and see what happens.
With device on connect to pc and pay attention that pops up a message "Allow USB debugging" then tap on "always allow" and "ok".
Now type
Code:
adb devices
to see if pc is recognicing and if it is ok type
Code:
adb reboot bootloader
.
Open normally MiFlash Unlock and sign in to your account and follow the scrren on instructions. Provide some screenshots if something fails.
Click to expand...
Click to collapse
I did as I wrote I entered the fastboot mode with adb and fastboot and the black screen with something written on top of the mini-screen that can not read appeared again, I open the unlock box and this occurs.
rinampa said:
I did as I wrote I entered the fastboot mode with adb and fastboot and the black screen with something written on top of the mini-screen that can not read appeared again, I open the unlock box and this occurs.
Click to expand...
Click to collapse
Plz provide some screenshot from your pc to see what happens on fastboot windows and on MiUnlock Tool; it could happen that you were missing something.
SubwayChamp said:
Plz provide some screenshot from your pc to see what happens on fastboot windows and on MiUnlock Tool; it could happen that you were missing something.
Click to expand...
Click to collapse
This is so after connecting fastboot mode with MiFlash Unlock
rinampa said:
This is so after connecting fastboot mode with MiFlash Unlock
Click to expand...
Click to collapse
Ok, your pc is not detecting your device connected in fastboot mode.
Try uninstalling all the drivers; those that you don´t use and those related with Xiaomi devices and install Mi PC Suite just to get installed the drivers https://mipcsuite.com open it for first time and connect it with your device on just to update drivers between both but when you´ll go to use MiFlash Unlock close it.
The USB cable used for your device is not to be shared with other devices so any of them creates a kind of data map on data wires and pc can have a sort of mistake trying to detect your device rightly.
Then to make all these steps start the process from adb as mentioned before sending with adb command to your device to bootloader/fastboot mode, this is just to confirm that pc is detecting it at both levels; adb and fastboot.
SubwayChamp said:
Ok, your pc is not detecting your device connected in fastboot mode.
Try uninstalling all the drivers; those that you don´t use and those related with Xiaomi devices and install Mi PC Suite just to get installed the drivers https://mipcsuite.com open it for first time and connect it with your device on just to update drivers between both but when you´ll go to use MiFlash Unlock close it.
The USB cable used for your device is not to be shared with other devices so any of them creates a kind of data map on data wires and pc can have a sort of mistake trying to detect your device rightly.
Then to make all these steps start the process from adb as mentioned before sending with adb command to your device to bootloader/fastboot mode, this is just to confirm that pc is detecting it at both levels; adb and fastboot.
Click to expand...
Click to collapse
É Ask me to update my device use Miui beta 10 9.4.25
rinampa said:
É Ask me to update my device use Miui beta 10 9.4.25
Click to expand...
Click to collapse
Uodate it, maybe this corrects some issues
I discovered what is written on the upper left side of the screen, press Key to shutdow. According to research I did not advance anything is USB input problem try on another Pc or a USB Hub cable.
rinampa said:
I discovered what is written on the upper left side of the screen, press Key to shutdow. According to research I did not advance anything is USB input problem try on another Pc or a USB Hub cable.
Click to expand...
Click to collapse
Of course, this is what´s written.
When PC detects device connected on fastboot or download mode then it holds it to avoid that it reboots while some data is transferring from and to each other.
If you put device on fastboot mode without connecting it to any PC then it will shutdown in 4 seconds aprox.
But like your case when PC detects that a device is connected but not in any transferring mode then it prompts to shutdown device.
For this I said that your PC is not recognicing it at fastboot mode, and installing again the drivers could solve the issue.
alxsduarte said:
Same with me.
Use Mi Unlock 2.3.803.10 (old version).
Works perfectly.
Click to expand...
Click to collapse
You right work ?
Hi guys,
i hope anyone has a solution for me here.
So i have this weired case where the phone shows up in ADB but not in fast boot in the windows device manager when using the Recovery/Fastboot mode.
I already tested 3 different PCs and multiple cables. I as well got lucky and a friend of mine got a note 9 as well. With this the Fastboot and ADB show so it shouldn´t be a driver issue.
Can anyone help me with this problem because i would have wanted to get TWRP on this phone.
...I think it's ok when it shows up in ADB. Did you hear the windows connection sound on the PC when you plug in the device?
You need to install the driver.
Without it, the phone is only detected in adb:
http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Don't forget to disable Driver Digital Signature enforcing in Win10.
kalehrl said:
You need to install the driver.
Without it, the phone is only detected in adb:
http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Don't forget to disable Driver Digital Signature enforcing in Win10.
Click to expand...
Click to collapse
As I wrote before, I got 2x the same Phone on hand one gets recognized and all by windows and shows up with the correct device driver in fastboot. The other phone doesn't show a thing, windows isn't even recognizing that it got connected in fastboot.
Strange is that the phone that doesn't get recognized in fastboot mode does get recognized in edl and adb mode.
So in the end I am looking for an information if this could be fixed or if the main board is some kind of damaged.
opg2000 said:
...I think it's ok when it shows up in ADB. Did you hear the windows connection sound on the PC when you plug in the device?
Click to expand...
Click to collapse
No sadly not, with the second device I could hear it connect and show correctly. The problem phone shows in adb and edl but not fastboot
Knoppersd said:
As I wrote before, I got 2x the same Phone on hand one gets recognized and all by windows and shows up with the correct device driver in fastboot. The other phone doesn't show a thing, windows isn't even recognizing that it got connected in fastboot.
Strange is that the phone that doesn't get recognized in fastboot mode does get recognized in edl and adb mode.
So in the end I am looking for an information if this could be fixed or if the main board is some kind of damaged.
Click to expand...
Click to collapse
I got the same issue but by installing the above driver and changing the new type-C cable.... helped me and solved my problem......
Knoppersd said:
Hi guys,
i hope anyone has a solution for me here.
So i have this weired case where the phone shows up in ADB but not in fast boot in the windows device manager when using the Recovery/Fastboot mode.
I already tested 3 different PCs and multiple cables. I as well got lucky and a friend of mine got a note 9 as well. With this the Fastboot and ADB show so it shouldn´t be a driver issue.
Can anyone help me with this problem because i would have wanted to get TWRP on this phone.
Click to expand...
Click to collapse
have yu got the solution of this because I am also facing the same issue.
No sorry, the phone is still dead and i moved on from it.
kalehrl said:
You need to install the driver.
Without it, the phone is only detected in adb:
http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Don't forget to disable Driver Digital Signature enforcing in Win10.
Click to expand...
Click to collapse
Managed to connect my Redmi Note 9 (merlin) to Fastboot with my Windows PC and install stock ROM with MiFlash thanks to this driver.
To install the driver i did:
1. Download driver from link above (ignored Firefox's warning of potential risk).
2. Unpack the rar file.
Now we must disable Windows Driver Signature for the driver to install correctly. It will only be disabled during a single boot and the automatically revert to active and secure again after reboot.
3. Restart Windows while holding the "Shift" key through Start Menu -> Power ->Restart.
4. The blue Windows Advanced Boot menu should appear. Select: "Troubleshoot" -> "Advanced Options" -> "Startup Settings" -> "Restart"
5. Computer will restart to the Startup Settings Menu. Press number "7" key on your keyboard to select "Disable driver signature enforcement". Windows then will boot to Desktop.
6. Search and open "Device Manger" on Windows menu.
7. Under "Other devices" right click "Android" (for me it appeared with a caution sign because of the default driver error) and then "Update driver".
8. Browse my computer for Drivers -> "Let me pick from a list..." -> Select "ADB Interface" (not sure if it is important which type of device is selected) -> "Have Disk".
9. Browse the downloaded driver folder that was unpacked on step 2 and select "android_winusb.inf" (this is the Windows driver).
10. On the Windows Security prompt select "Install this driver anyway".
From here on Fastboot mode should be recognized by the PC and you can install a ROM using MiFlash or following any other guide to install via Fastboot in this forum.