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.
Related
Dears,
Can you please anyone share the windows 7 ADB drivers?
Regards
androidgalaxyman
Get PDA net adb drivers work on all windows. Tested on win 10 developer preview alaoy.
Sent from my AO5510 using XDA Premium 4 mobile app
Thanks
Siddhesh.K15 said:
Get PDA net adb drivers work on all windows. Tested on win 10 developer preview alaoy.
Sent from my AO5510 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks
androidgalaxyman said:
Dears,
Can you please anyone share the windows 7 ADB drivers?
Regards
androidgalaxyman
Click to expand...
Click to collapse
I got mine working with this on windows 8.1. Try just in case.
http://www.koushikdutta.com/post/universal-adb-driver.
PRRash said:
I got mine working with this on windows 8.1. Try just in case.
http://www.koushikdutta.com/post/universal-adb-driver.
Click to expand...
Click to collapse
It wasn't working in Windows 7
The instructions are incomplete so there will be no rooting unless you install proper micromax drivers for adb . Looks like the instructions were emailed and posted by someone else. Disabling driver signature enforcement is also not helpful .Tried it on 4 different systems and a fresh vm with x86,x64 win7 & win8 . drivers from koushik also does not work
Drivers plz
Did anyone found the drivers for YU yureka? Plz upload if u have.. My system detects the mobile when it is switched on but when I enter bootloader the system doesn't detect it..
darshan.devadiga said:
Did anyone found the drivers for YU yureka? Plz upload if u have.. My system detects the mobile when it is switched on but when I enter bootloader the system doesn't detect it..
Click to expand...
Click to collapse
Metoo adb works fine but not fastboot:banghead:
Hey.. I finally got the fix.. Download all in one toolbox for yureka and then try in that.. Worked for me.. Hit thanks if it works
Install Universaladb driver setup
Handset still wontget recognized
Goto device manager and set custom driver for exclamation mark to "android composite interface" confirm the android debugging popup with mac , now boot to adb reboot-bootloader
Again browse the exlamation mark android to "android composite interface" and push in the fastboot command
adb reboot-bootloader
YU will now be in fastboot mode.
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf flash recovery recovery-yu.img
fastboot -i 0x1ebf reboot
boot into newly installed recovery.
adb reboot recovery
Hey
androidgalaxyman said:
Dears,
Can you please anyone share the windows 7 ADB drivers?
Regards
androidgalaxyman
Click to expand...
Click to collapse
Hey dude, i'm using windows 7 Ultimate as well and the adb/fastboot do not work for my yureka. Were you successful in finding the proper drivers?
asim.sidz said:
Hey dude, i'm using windows 7 Ultimate as well and the adb/fastboot do not work for my yureka. Were you successful in finding the proper drivers?
Click to expand...
Click to collapse
I request all the Yureka owers to raise a voice and join the campaign !
[PROJECT] Reviving Hard Bricked YU (QLoader 9008 Mode) at YUPLAYGOD.COM
Hi guys,
I'm having problems unlocking bootloader.
The phone enter into fastboot mode but when I type "fastboot oem unlock-go" in the cmd of windows it doesn't recognize my device.
I have installed Minimal ADB and Fastboot and I have installed ADB Driver installer too but it doesn't recognize the device.
Can anybody help me with this please?
I need to unlock it because I want to root it.
Thanks
Have you tried unplugging and replugging when the phone goes into fastboot mode?
I just got my pro 3, did the OTA to the .19 software and unlocked and rooted just today and my girlfriend's very very fresh windows 10 install.
If that doesn't work just delete the adb driver, replug the device and windows should install the same drivers I used.
Hi guys!
I am trying to flash the factory OS downloaded from the dev website, however I have a problem.
When the phone is booted in Android the ADB Interface is recognized without a problem.
However when I reboot to recovery to flash the FW Windows 10 (latest CU version) does not recognize ADB Interface and says This Device Cannot Start Error 10
I have tried these drivers:
adb-setup-1.4.3
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0
latest_usb_driver_windows /google driver/
OnePlus+5+USB+drivers+-+Technobuzznet
Nothing has helped, the issue remained the same.
Any suggestion what can I do to get OP5 ADB working when the phone is in Recovery ?
Thank you!
ssj3hulk said:
Hi guys!
I am trying to flash the factory OS downloaded from the dev website, however I have a problem.
When the phone is booted in Android the ADB Interface is recognized without a problem.
However when I reboot to recovery to flash the FW Windows 10 (latest CU version) does not recognize ADB Interface and says This Device Cannot Start Error 10
I have tried these drivers:
adb-setup-1.4.3
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0
latest_usb_driver_windows /google driver/
OnePlus+5+USB+drivers+-+Technobuzznet
Nothing has helped, the issue remained the same.
Any suggestion what can I do to get OP5 ADB working when the phone is in Recovery ?
Thank you!
Click to expand...
Click to collapse
same problem.
fix for it -> use linux
setup vmware, install ubuntu
when everything is set up connect device in fastboot mode
open command line:
sudo apt-get update
sudo apt-get install adb
sudo apt-get install fastboot
now you can make adb and fastboot commands, don't forget the sudo before the command e.g.: sudo fastboot reboot
I made the mistake of wiping my entire device when going to do a clean flash so the only thing I could access was recovery. I had no issues with using adb to sort out my mess in Win 10. The last phone I had was an old HTC that I was using between getting my OP3 stolen and the OP5 release and for that I had HTC drivers installed.
Not sure if that is a solution that will help you, but just putting it out there.
ssj3hulk said:
Hi guys!
I am trying to flash the factory OS downloaded from the dev website, however I have a problem.
When the phone is booted in Android the ADB Interface is recognized without a problem.
However when I reboot to recovery to flash the FW Windows 10 (latest CU version) does not recognize ADB Interface and says This Device Cannot Start Error 10
I have tried these drivers:
adb-setup-1.4.3
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0
latest_usb_driver_windows /google driver/
OnePlus+5+USB+drivers+-+Technobuzznet
Nothing has helped, the issue remained the same.
Any suggestion what can I do to get OP5 ADB working when the phone is in Recovery ?
Thank you!
Click to expand...
Click to collapse
Did you enable usb debugging in developer options?
Has anyone ever had an issue of "fast" flashing a fastboot stock ROM? I tried to flash stock OREO ROM but didn't manage to flash it because when I start flash it is done within 1 second, progress bar iz green and it says "Success" but ROM isnt flashed at all. Someone said that the problem is in long folder names where the ROM is extracted and if there are spaces in folder and rom names.
This is what I have tried:
1. Rom extracted with both 7zip and winRar on C: in folder with short name
2. Turned on USB debugging and OEM lock and Unknown sources in phone settings
3. PC connection allowed on device when connected to USB 2.0 and 3.0
4. Proper drivers installed and device detected in Device manager list
5. Device is detected in Mi flash tool when hit REFRESH button
6. Device bootloader is unlocked through fastboot command in command prompt (vShell)
I didnt try:
1. Install custom recovery
2. Flash on lower windows version (i.e. windows 7 or 8) only on Windows 10 pro which I have on 2 PC's.
All suggestions are welcome. Thank you!
I haven't had any issues doing this on a windows 10 pro. Have you tried different cables, or another USB port?
What version of the drivers are you running?
What version of MiFlash are you using?
I tried with original USB cable and aftermarket it is the same. I dont know which driver version is installed but I didnt try to install them separately. I'm using latest version of Mi Flash and drivers installed are probably came with Mi flash tool. I tried old version of Mi Flash tool from 2015 but didnt work. Tried USB 2.0 and 3.0 ports on both computers. It is really odd situation but I believe it is communication matter between PC and phone. Are there any other drivers which I should try?
Try the drivers from the mi unlocking tool
Ok, I will try and post the results here
I did try to install usb drivers from Mi Unlock but again not working. I tried to flash my other phone Mi 5s and flash process went the same way like on Mi A1.
what is the exact version of your mi flash tool? the version i'm using is 2017.7.20.0, and it's working fine in windows 7
also, have you tried executing some fastboot commands in CMD window, like "fastboot oem device-info" just to make sure the fastboot drivers are working fine?
if all else fails, maybe you should borrow a another laptop or PC
Mi flash tool I'm using is the same version like yours. Fastboot is working properly no problems at all. The phone is detected in CMD when I type FASTBOOT DEVICES and in Mi Flash tool also detects device when REFRESH is pressed. Only thing I did not try is installing Mi flash tool on Windows 7.
bpodnar said:
Has anyone ever had an issue of "fast" flashing a fastboot stock ROM? I tried to flash stock OREO ROM but didn't manage to flash it because when I start flash it is done within 1 second, progress bar iz green and it says "Success" but ROM isnt flashed at all. Someone said that the problem is in long folder names where the ROM is extracted and if there are spaces in folder and rom names.
This is what I have tried:
1. Rom extracted with both 7zip and winRar on C: in folder with short name
2. Turned on USB debugging and OEM lock and Unknown sources in phone settings
3. PC connection allowed on device when connected to USB 2.0 and 3.0
4. Proper drivers installed and device detected in Device manager list
5. Device is detected in Mi flash tool when hit REFRESH button
6. Device bootloader is unlocked through fastboot command in command prompt (vShell)
I didnt try:
1. Install custom recovery
2. Flash on lower windows version (i.e. windows 7 or 8) only on Windows 10 pro which I have on 2 PC's.
All suggestions are welcome. Thank you!
Click to expand...
Click to collapse
I'm having the same issue. I tried enquiring about it in various groups both in Telegram as well as WhatsApp but all to vain.
Sent from my Mi A1 using Tapatalk
It is clear that connection is not questionable because the phone is communicating with pc normally within fastboot or mi flash tool. The main suspect is windows 10 pro so it would be nice if someone could try to flash it on windows 7
Hmmm yea might be win 10.. i am on win 7 and mi flash tool works fine
bpodnar said:
Has anyone ever had an issue of "fast" flashing a fastboot stock ROM? I tried to flash stock OREO ROM but didn't manage to flash it because when I start flash it is done within 1 second, progress bar iz green and it says "Success" but ROM isnt flashed at all. Someone said that the problem is in long folder names where the ROM is extracted and if there are spaces in folder and rom names.
This is what I have tried:
1. Rom extracted with both 7zip and winRar on C: in folder with short name
2. Turned on USB debugging and OEM lock and Unknown sources in phone settings
3. PC connection allowed on device when connected to USB 2.0 and 3.0
4. Proper drivers installed and device detected in Device manager list
5. Device is detected in Mi flash tool when hit REFRESH button
6. Device bootloader is unlocked through fastboot command in command prompt (vShell)
I didnt try:
1. Install custom recovery
2. Flash on lower windows version (i.e. windows 7 or 8) only on Windows 10 pro which I have on 2 PC's.
All suggestions are welcome. Thank you!
Click to expand...
Click to collapse
Place the rom folder in the desktop, use the latest Mi flash tool, have the latest drivers & platform tools installed & check for the .net framework as well. Look for these things & rest will go smooth.
Sent from my Mi A1 using Tapatalk
Hi all,
I have this X00TD model, and I recently updated firmware to WW-16.2017.2002.061. The phone has Android recovery, and I want to install Lineage OS. Whenever I try to install Lineage, I get the error 21 "signature verification failed". I read somewhere that I can disable the signature check in TWRP. But TWRP fails to install, whatever I try. I tried 3 different unofficial versions of TWRP (as my phone model has no official version of TWRP) and in fastboot, when I give the command "sudo fastboot flash recovery <filename>.img", nothing happens, and the process just freezes, and I need to kill the terminal to end the process. I have Ubuntu 18.04 installed. ADB and fastboot seem ok. When I type "sudo fastboot devices", my phone entry comes up. Any help would be welcome. I don't have windows os.
Thanks.
akhil520c said:
Hi all,
I have this X00TD model, and I recently updated firmware to WW-16.2017.2002.061. The phone has Android recovery, and I want to install Lineage OS. Whenever I try to install Lineage, I get the error 21 "signature verification failed". I read somewhere that I can disable the signature check in TWRP. But TWRP fails to install, whatever I try. I tried 3 different unofficial versions of TWRP (as my phone model has no official version of TWRP) and in fastboot, when I give the command "sudo fastboot flash recovery <filename>.img", nothing happens, and the process just freezes, and I need to kill the terminal to end the process. I have Ubuntu 18.04 installed. ADB and fastboot seem ok. When I type "sudo fastboot devices", my phone entry comes up. Any help would be welcome. I don't have windows os.
Thanks.
Click to expand...
Click to collapse
Fastboot flash recovery twrp.img
Sent from my ZenFone Max Pro M1 using Tapatalk
If you can't install TWRP on pie, try reverting to Oreo with AFT and then flash TWRP in fastboot. Also make sure you have unlocked the bootloader whether by the official tool or the unofficial method. THIS WILL DELETE ALL DATA SO BACK UP.
Thanks arko. Is there Asus Flash Tool available for Linux also? Will try and revert. Thanks :svetius
Tried reverting to Oreo with AFT, doesn't work. I installed windows 10, but fastboot doesn't work.
#fastboot devices gives me no output. I have the Oreo zip file, any alternate way I can install it? As you mentioned, there seems to be an issue with the pie ROM on my phone. Any way I can downgrade to Oreo using windows/Linux?
akhil520c said:
Tried reverting to Oreo with AFT, doesn't work. I installed windows 10, but fastboot doesn't work.
#fastboot devices gives me no output. I have the Oreo zip file, any alternate way I can install it? As you mentioned, there seems to be an issue with the pie ROM on my phone. Any way I can downgrade to Oreo using windows/Linux?
Click to expand...
Click to collapse
Windows 10 ? Its bcuz Driver Signature Enforcement
Disable it and reinstall adb and fastboot drivers, it will work for sure.
Windows driver security wouldn't accept drivers without proper Signatures,so like i said, just disable it and you are good to go.
:good:
Tried steps you mentioned, doesn't work. In fastboot mode, #fastboot devices gives me no output. Looks like my pie ROM is buggy. Basically, I need to install lineage on the phone.
Hi all,
Finally got everything done in about 5 mins I booted up Ubuntu Mate (32 bit) on my other laptop, and found I'd already installed adb and fastboot on it from the repositories (not from google). I booted my phone in fastboot mode, and tried the #fastboot devices command, and voila, my phone got detected! After that, it was a matter of a few minutes, following the installation instructions (of twrp and lineage) from the lineage website. Thanks for all your inputs and help
P.S: I realised (again), after more than 2 decades, that windoze mighty sucks lol.