i was trying to install a custom ROM and wiped all the partitions. I accidentally rebooted my Xiaomi redmi note 8 and now it is stuck in fastboot. i tried to flash TWRP using ADB however it shows that it is waiting for device. (I'm guessing that the USB DEBUGGING turned off). Anyone know how to fix this? Thanks in advance!
I would try possibly checking drivers on your computer, or just try a different cable. USB Debugging is not necessarily a thing in fastboot. Or, better said, there is not a toggle switch for turning on USB access. Plugging in a USB cable gives you full access to fastboot commands on the device that you're using. If that doesn't work, you might want to try checking out the Redmi Note 8 sub-forums since others might have the same issue. Try drivers and/or cable changes and share the results
Related
All I see is a google logo, not rebooting just staying on the screen. I am pretty sure I deleted the operating system, but I can't seem to get in recovery. What lead up to this was me not being able to connect the device to windows over usb, nothing in device manager, I couldn't even get adb to connect even through twrp sideload. But now I think I caused a whole new issue. I'm just trying to get back to stock rooted lol. Advise?
Edit: unpluged battery and replugged it in, got into recovery now, still having issues connecting so I can flash a rom.
Edit: I have the google usb driver installed from the android sdk. I still can't see my device in windows device manager nor I can't see it through adb. still searching around for a solution.
Edit: I found my old rom still on the device so I was able to install that to actually use the device. I still can't seem to connect to the pc in any way though. I have usb debugging checked drivers installed. Windows just doesn't seem to think a device is there.
s101999 said:
All I see is a google logo, not rebooting just staying on the screen. I am pretty sure I deleted the operating system, but I can't seem to get in recovery. What lead up to this was me not being able to connect the device to windows over usb, nothing in device manager, I couldn't even get adb to connect even through twrp sideload. But now I think I caused a whole new issue. I'm just trying to get back to stock rooted lol. Advise?
Edit: unpluged battery and replugged it in, got into recovery now, still having issues connecting so I can flash a rom.
Edit: I have the google usb driver installed from the android sdk. I still can't see my device in windows device manager nor I can't see it through adb. still searching around for a solution.
Edit: I found my old rom still on the device so I was able to install that to actually use the device. I still can't seem to connect to the pc in any way though. I have usb debugging checked drivers installed. Windows just doesn't seem to think a device is there.
Click to expand...
Click to collapse
Try toggling MTP and/or PHP in USB options.
Your device might show up as an adb device in Device Manager.
Edit:
Some more info here:
http://forum.xda-developers.com/showpost.php?p=57205550&postcount=146
Use a different usb port, different cords, or even a different computer, until you get a pc to recognize the phone.
I had this. It was because not all USB leads have data. Even some that do are wired different. Use the original or HTC work fine with N5 as I've both brands
howard bamber said:
I had this. It was because not all USB leads have data. Even some that do are wired different. Use the original or HTC work fine with N5 as I've both brands
Click to expand...
Click to collapse
Well on my 4th cable, what do you know it works just fine. Feel a little silly but thanks everyone.
Hello,
i tried to update my Nexus 5 to 5.1 by using adb sideload.
First i installed the driver which did not work, i removed them and used an another and the device was recognized after that on windows.
So I started the sideload and it stopped at about 60% and the USB Connection was lost. I can not see the device in the device manager and if i use my linux computer i can not see any new entry if i use 'dmesg'. I used an another USB cable to check if this is broken. I tried to format the cache and it now still boots to the recovery mode.
Can it be that the USB driver in the N5 is broken now?
I wanted to prevent a factory reset, but i dont think that a FR will help here if i can not connect even in the recovery mode
Any suggestions?
Thank you!
wwwiesel said:
Hello,
i tried to update my Nexus 5 to 5.1 by using adb sideload.
First i installed the driver which did not work, i removed them and used an another and the device was recognized after that on windows.
So I started the sideload and it stopped at about 60% and the USB Connection was lost. I can not see the device in the device manager and if i use my linux computer i can not see any new entry if i use 'dmesg'. I used an another USB cable to check if this is broken. I tried to format the cache and it now still boots to the recovery mode.
Can it be that the USB driver in the N5 is broken now?
I wanted to prevent a factory reset, but i dont think that a FR will help here if i can not connect even in the recovery mode
Any suggestions?
Thank you!
Click to expand...
Click to collapse
Hmmm, intermittent ADB occured before attempted sideload falure.
Boot to bootloader and see if you can
fastboot devices
If you can detect the device in fastboot, but still cant ABD, then maybe take a look here http://forum.xda-developers.com/showpost.php?p=59420668&postcount=322
After looking there, if you are absolutely certain that it is not a driver issue, you might be looking at a hardware failure of the charging port.
https://www.youtube.com/watch?v=qqCEXEmcj4Y
If it were me, I'd replace the port and re-attempt ADB sideload.
I am in dire need of help with my K1! I am trying to root it (7.0) with a Linux Mint 18.2 machine. I was able to temporarily get adb authorization to unlock the bootloader, but it somehow revoked itself before I could flash TWRP or SU. I have searched the forums and tried all the suggestions, to no avail. I am not a pro at using Linux, but I am not afraid to try different suggestions. So far I have unplugged and replugged the usb cord, tried a different usb cord, tried the usb 2.0 & 3.0 connections (no 3.0 in Linux), turned off usb debugging/revoked authorizations/turned on debugging (while plugged into usb and not plugged in to usb), and I cannot get the box on the K1 to reappear asking to allow authorization for adb connection. I know there are some files in the Android folder on my computer that needs to be deleted, but that is locked and will not give me access to that folder, and I do not know how to change that.
As I said, I have an unlocked bootloader at the moment, but cannot proceed further with installation of TWRP or SU until I can authorize again. Can anybody provide any info that I might try in addition to what has already been tried?
BTW, I have been trying those things all weekend long, numerous times, with the same results.
Thanks!
Seriously, no one can offer any suggestions? Also tried a factory reset on the K1, but still get no box to authorize adb connection to the computer. Any ideas at all??????
Problem resolved.
I'm hoping someone can help me out here. I've rooted phones before and didn't have any trouble previously. I just bought a used Pixel 3 on eBay with the plan to root using Magisk. The only problem is I can't get the device to be recognized at all on my PC. I've tried all the usual things like different USB ports, different cables, cleaning out the port, etc. I have the latest drivers installed and I have a Pixel XL that is recognized by my PC immediately so I know I have the correct drivers installed. Pixel 3 does not show up in Device Manager at all. I have USB debugging enabled on the device, but it never prompts me to Allow USB debugging when I connect the Pixel 3 to my PC.
Now, here's the weird part. I know the cable is working fine because I use the same cable and plug it into my Mac. The Pixel 3 is recognized immediately and I'm prompted to enable USB debugging. ADB then works just fine on my Mac. 'adb devices' shows my phone. But I then try to use 'adb reboot bootloader' and my phone reboots to the bootloader as it should. At this point my phone says it's in FastBoot Mode, but the device isn't recognized using 'sudo fastboot devices' and if I try 'sudo fastboot flashing unlock' it just sits there saying 'waiting for any device'. I've also tried putting it into FastBoot mode manually by using the Power and Volume Down key, but run into the same issue with it not being recognized while in FastBoot mode.
Could the previous owner have done something to the bootloader to cause the device to not be recognized in FastBoot mode? And is there any way to fix it? Why would the phone be recognized on my Mac without issue, but using the same cable and multiple different ports on my PC, it never gets recognized?
Any help would be very much appreciated here as I'm at a loss as to what I can do and fear I just spent money on an expensive paperweight.
I tested the cable I'm using with my Pixel XL and it's immediately recognized by my PC and the notification for USB debugging shows on the phone, so I know the cable is working out. No device ever shows in the device manager when I have my Pixel 3 connected though. I've even uninstalled the drivers while my Pixel XL is connected to hopefully put Windows into a driverless state hoping my Pixel 3 would then show up as an unrecognized device, but no device. I can't get it to show up at all in Windows for some reason and it's not recognized while in fastboot mode on my Mac. Fastboot mode information all seems to match what a Pixel 3 should look like as well, so I don't think the previous owner installed the wrong software causing device id mismatch. Anyone have any other suggestions for what I can try?
I am trying to unlock Redmi note 6 pro but facing issue in fastboot. whenever I try 'fastboot devices' command, on 1st query it shows ID but on 2nd time query it shows '????????". when this happen, on phone screen messege appears as " press any key to shutdowd". pls check the attached image and tell me the solution. Have tried uninstall/reinstall driver, updated phone through phone's updater but nothing helps. phone always kicks out from fastboot mode. due to this problem mi unlock tool never detect my phone.
@Narrry84
Change USB port, change USB cable, install Android USB Driver matching your needs if not already done yet
jwoegerbauer said:
@Narrry84
Change USB port, change USB cable, install Android USB Driver matching your needs if not already done yet
Click to expand...
Click to collapse
Have done already these steps. will try changing PC tomorrow..