Hello.
I recently installed the 4.3 ota update. I knew I would have to reroot. After the update I have tried everything I can think of to flash a new recovery or bootloader or anything. All without success. Fastboot simply says "Sending...", the phone says "downloading..." and that's the end of it. They would both sit in that state forever if I let them.
I know I'm not alone on this issue. I have searched and searched without finding a solution. Does anyone know of one?
Thanks.
pfederighi said:
Hello.
I recently installed the 4.3 ota update. I knew I would have to reroot. After the update I have tried everything I can think of to flash a new recovery or bootloader or anything. All without success. Fastboot simply says "Sending...", the phone says "downloading..." and that's the end of it. They would both sit in that state forever if I let them.
I know I'm not alone on this issue. I have searched and searched without finding a solution. Does anyone know of one?
Thanks.
Click to expand...
Click to collapse
1. Usb debugging enabled and bootloader unlocked?
2. Correct drivers installed, try these usb naked drivers for instance https://www.google.nl/url?sa=t&rct=...=RUlfH35SAJki_DdLfo8MeA&bvm=bv.51773540,d.Yms.
3. Used the original usb cable or tried another usb port?
4. If you type fastboot devices in fastboot mode do you see a serialnumber? The same for adb devices in adb mode?
gee2012 said:
1. Usb debugging enabled and bootloader unlocked?
2. Correct drivers installed, try these usb naked drivers for instance https://www.google.nl/url?sa=t&rct=...=RUlfH35SAJki_DdLfo8MeA&bvm=bv.51773540,d.Yms.
3. Used the original usb cable or tried another usb port?
4. If you type fastboot devices in fastboot mode do you see a serialnumber? The same for adb devices in adb mode?
Click to expand...
Click to collapse
USB debugging is enabled.
I've tried the original USB cable and others. I've tried different USB ports.
adb works fine. Fastboot recognizes my phone and prints a serial number. Fastboot even works for locking/unlocking the boot loader.
There are no "drivers" in the Linux world. Should I find someone who has a Windows system and ask to use their computer?
Thanks.
pfederighi said:
USB debugging is enabled.
I've tried the original USB cable and others. I've tried different USB ports.
adb works fine. Fastboot recognizes my phone and prints a serial number. Fastboot even works for locking/unlocking the boot loader.
There are no "drivers" in the Linux world. Should I find someone who has a Windows system and ask to use their computer?
Thanks.
Click to expand...
Click to collapse
Yes, you may try that. I`am talking about a windows pc and never had an issue. I don`t have xperience with linux computers.Good luck bro
Solved
gee2012 said:
Yes, you may try that. I`am talking about a windows pc and never had an issue. I don`t have xperience with linux computers.Good luck bro
Click to expand...
Click to collapse
So. I solved the problem. I now feel like an idiot.
I plugged my phone into a Windows system and a nice notice popped up saying that my device could run faster if it was plugged into a USB 2.0 port. Then it dawned on me that only a few of the ports on my computer are 2.0 and that I had tried one of them previously but with an extension cable (because it's in the back and hard to reach). I unplugged the extension cable and plugged the USB cable directly into the port and all was well.
I hope that others who have had this issue find this useful.
Thank you for your help.
Related
I did OTA update to 4.3 of my N7 3G which was rooted and unlocked (I know now I shouldn't have done it...).
I got an error at the end of the update (when was installing radio).
Rebooted, and got stuck in the google loop...
NOW, I CAN ENTER FASTBOOT MODE, BUT THE PROBLEM IS THAT THE USB DEVICE IS NO MORE DETECTED BY THE PC (I tried Windows XP, Windows 7, Linux), so I cannot re-flash it... It's not a driver's issue, because at USB level the N7 is not even detected when connected to the PC (for instance, dmesg shows nothing in ubuntu and windows does not "beep").
Is it possible that that was corrupted only the "USB stack" of the bootloader??? I could not find a similar issue in this or other forums (??).
Is there any chance to get the USB working again?
Is there any chance to send it for repair to ASUS (I bought it one month ago) with this described symptoms and with the "unlocked" icon on power on?
Is there a payed service to flash it with JTAG?
Thanks to anyone who can give me a clue...
Same problem - updated to 4.3 OTA today, N7 not recognized as an USB device at all. Still haven't tried on a Mac but I doubt it will be any different. The device isn't detected in normal mode or fastboot
c0ldblooded said:
Same problem - updated to 4.3 OTA today, N7 not recognized as an USB device at all. Still haven't tried on a Mac but I doubt it will be any different. The device isn't detected in normal mode or fastboot
Click to expand...
Click to collapse
I solved by sending it to assistance. Excellent service by ASUS... I did not have to pay although the tablet was unlocked/rooted.
Andrea.
since the new update to 4.3, N7 requires authorization with your pc before you can use ADB. I had this issue and had to go into developer options and click on the 'Revoke USB debugging authorization'. when I connect it to the pc again and ran adb, my N7 then asked for authorization to allow pc access. That restore my ADB.
Also make sure you have the lastest SDK installed on your pc too.
If you can enter Fastboot via pc you certainly can reflash it.
dilldoe said:
since the new update to 4.3, N7 requires authorization with your pc before you can use ADB. I had this issue and had to go into developer options and click on the 'Revoke USB debugging authorization'. when I connect it to the pc again and ran adb, my N7 then asked for authorization to allow pc access. That restore my ADB.
Also make sure you have the lastest SDK installed on your pc too.
If you can enter Fastboot via pc you certainly can reflash it.
Click to expand...
Click to collapse
In my case (and probably the same for Colblooded) I got stuck with the N7 NOT BOOTING and NOT DETECTED by any USB host (tried also with dmesg on linux), so there was no chance to re-flash it. The only thing I could do was to send it to Brno for repair...
Andrea
andreabix said:
In my case (and probably the same for Colblooded) I got stuck with the N7 NOT BOOTING and NOT DETECTED by any USB host (tried also with dmesg on linux), so there was no chance to re-flash it. The only thing I could do was to send it to Brno for repair...
Andrea
Click to expand...
Click to collapse
Exactly the case. Unfortunately I can't send it to ASUS
andreabix said:
In my case (and probably the same for Colblooded) I got stuck with the N7 NOT BOOTING and NOT DETECTED by any USB host (tried also with dmesg on linux), so there was no chance to re-flash it. The only thing I could do was to send it to Brno for repair...
Andrea
Click to expand...
Click to collapse
you said you could boot into fastboot, did 'fastboot devices' on your pc not detect it? Does it detect it now?
dilldoe said:
you said you could boot into fastboot, did 'fastboot devices' on your pc not detect it? Does it detect it now?
Click to expand...
Click to collapse
That's the point: I could boot into fastboot but 'fastboot device' was not detected by the PC (so I could not re-flash it). Now if I boot into fastboot the PC correctly detects the device...
What I find very, very strange is that an OTA update to 4.3 caused the USB port to stop working!! From what I read googling around, even with a problem during a system update going to fastboot mode (on + volume down) should always allow a connection to the PC for reflashing, or, at least, you could enter APX mode (on + volume up), which is an even lower level mode that is detected by the PC with different drivers (for direct programming, but need encryption key and SW not yet available for Nexus 7).
Maybe it was just a coincidence: an USB hardware failure just before I did the OTA update, which I realized only afterwards, when I needed USB for reflashing...
However the ASUS Service Repair Report states:
Problem/Symptoms: Pad Battery can't be charged. OS ERROR
Replaced Part:
ME370TG BAT COSLI-POLY FPAC
ME370TG MAIN_BD.1G/T30L/NFC
The first one looks the battery (????)
The second sounds like the mainboard...
Andrea
Hi All,
I bought a Nexus 4 on eBay thinking I could fix it but I am really struggling.
The nexus 4 has TWRP 2.8.6.0 but that is all.
I cannot enable USB debugging as I don't have any rom installed.
I have tried a USB OTG cable with power, but have learned that the phone still cannot output the right power? The light on my usb stick comes on but TWRP does not list any USB OTG.
This phone does not have an SD card slot, so I cannot load anthing this way.
Is it impossible to get this phone working?
Kind Regards,
breaktheblock
Try fastboot from the bootloader, and reflash
ReneX10 said:
Try fastboot from the bootloader, and reflash
Click to expand...
Click to collapse
Hi ReneX10,
Thankyou for the reply, can you tell me the next step after I get to the fastboot screen?
breaktheblock said:
Hi ReneX10,
Thankyou for the reply, can you tell me the next step after I get to the fastboot screen?
Click to expand...
Click to collapse
tbh, going back to stock is a good idea and then the door is open
https://developers.google.com/android/nexus/images?hl=en
there ya go, basically follow the instructions...
ReneX10 said:
tbh, going back to stock is a good idea and then the door is open
there ya go, basically follow the instructions...
Click to expand...
Click to collapse
Will I need adb drivers to be working in windows for me to be able to do this? because so far I have been unable to successfully install any even using NRT to help.
breaktheblock said:
Will I need adb drivers to be working in windows for me to be able to do this? because so far I have been unable to successfully install any even using NRT to help.
Click to expand...
Click to collapse
Afraid I am a Linux baby, can't help you with Windows :/
fastboot etc already on there
my windows computer wont recognize the phone when I plug phone into the PC, driver installation always fails?
how can i connect a phone with just TWPR to my PC, could this be using MTP?
breaktheblock said:
my windows computer wont recognize the phone when I plug phone into the PC, driver installation always fails?
how can i connect a phone with just TWPR to my PC, could this be using MTP?
Click to expand...
Click to collapse
Have a look at this thread ..
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
(Read the thread thoroughly, and take notes, its real easy to get lost in the middle of the procedure and mess it up, and having to start again).
Flashing the stock rom is done entirely via fastboot, so you shouldnt need to worry about adb.
If you can boot into bootloader you should be able to flash stock image, once you get the windows drivers sorted. Luckily I'm on a Mac, so drivers haven't been an issue. I had a similar scenario sometime ago, and after flashing stock, all was good in the world again. I may be wrong, but you'll probably need the latest platform-tools (which contains fastboot) if you're flashing the latest stock images. (Someone correct me if I'm wrong on that one).
Sent from my LG-V500 using Tapatalk
dsbnz said:
Have a look at this thread ..
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
(Read the thread thoroughly, and take notes, its real easy to get lost in the middle of the procedure and mess it up, and having to start again).
Flashing the stock rom is done entirely via fastboot, so you shouldnt need to worry about adb.
If you can boot into bootloader you should be able to flash stock image, once you get the windows drivers sorted. Luckily I'm on a Mac, so drivers haven't been an issue. I had a similar scenario sometime ago, and after flashing stock, all was good in the world again. I may be wrong, but you'll probably need the latest platform-tools (which contains fastboot) if you're flashing the latest stock images. (Someone correct me if I'm wrong on that one).
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
This is good information, but I cannot get any further that plugging the phone into the PC, I have tried 4 different usb cables and with them all windows 7 and XP says "unknown device".
I wasn't sent the original cable from the owner which I am asking to do if they have it, but it may be a long shot for them to still have it.
Looks like I need the original usb cable?
breaktheblock said:
This is good information, but I cannot get any further that plugging the phone into the PC, I have tried 4 different usb cables and with them all windows 7 and XP says "unknown device".
I wasn't sent the original cable from the owner which I am asking to do if they have it, but it may be a long shot for them to still have it.
Looks like I need the original usb cable?
Click to expand...
Click to collapse
I don't think the cable needs to be original, I've used a Motorola cable on my N4 to flash stock, with no problems.
Is the phone in fastboot mode when you connect to pc?
Have you tried these drivers?
http://developer.android.com/sdk/win-usb.html
Sent from my LG-V500 using Tapatalk
dsbnz said:
I don't think the cable needs to be original, I've used a Motorola cable on my N4 to flash stock, with no problems.
Is the phone in fastboot mode when you connect to pc?
Have you tried these drivers?
http://developer.android.com/sdk/win-usb.html
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
For information I am using a cable from a usb cable that came from a Nexus 5.
When the phone is connected to the PC it had an android lying down with an open chest.
When pointing to the android developer sdk drivers as above it does it's usual thing of saying it is already up to date below that still saying unknown device. I'm so frustrated right now.
breaktheblock said:
For information I am using a cable from a usb cable that came from a Nexus 5.
When the phone is connected to the PC it had an android lying down with an open chest.
When pointing to the android developer sdk drivers as above it does it's usual thing of saying it is already up to date below that still saying unknown device. I'm so frustrated right now.
Click to expand...
Click to collapse
Can you reboot to the main bootloader screen?
The reason i ask is .. When you see the android lying down is there a list below showing the phone stats? If not, possibly this is why windows is reporting an unknown device.
You should try to get back into fastboot
This has the info to get to bootloader if youre not sure how..
http://www.androidcentral.com/how-unlock-nexus-4-bootloader
When you're in fastboot, try to connect to pc again.
Sent from my LG-V500 using Tapatalk
dsbnz said:
Can you reboot to the main bootloader screen?
The reason i ask is .. When you see the android lying down is there a list below showing the phone stats? If not, possibly this is why windows is reporting an unknown device.
You should try to get back into fastboot
This has the info to get to bootloader if youre not sure how..
http://www.androidcentral.com/how-unlock-nexus-4-bootloader
When you're in fastboot, try to connect to pc again.
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Underneath the android lying down it has:
FASTBOOT MODE (in red text)
PRODUCT_NAME
HW VERSION
BOOTLOADER VERSION
BASEBAND VERSION
CARRIER INFO
SERIAL NUMBER
SIGNING
SECUREBOOT (in green text - enabled)
LOCK STATE (in red text - unlocked)
Above the android lying down I can use the hardware buttons to toggle between "Start | Restart bootloader | Recovery mode | Power off"
Am I in fastboot?
breaktheblock said:
Underneath the android lying down it has:
FASTBOOT MODE (in red text)
PRODUCT_NAME
HW VERSION
BOOTLOADER VERSION
BASEBAND VERSION
CARRIER INFO
SERIAL NUMBER
SIGNING
SECUREBOOT (in green text - enabled)
LOCK STATE (in red text - unlocked)
Above the android lying down I can use the hardware buttons to toggle between "Start | Restart bootloader | Recovery mode | Power off"
Am I in fastboot?
Click to expand...
Click to collapse
Sounds like youre in the right mode. The problem would likely be on the pc/driver side.
P.S. in fastboot mode, you only need to use fastboot on pc .
Sent from my LG-V500 using Tapatalk
dsbnz said:
Sounds like youre in the right mode. The problem would likely be on the pc/driver side.
P.S. in fastboot mode, you only need to use fastboot on pc .
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
The driver issue is a massive stumbling block.
I'm still not sure if the cable will work.
I understand I can use fastboot after the PC recognises the nexus 4.
I have a Lubuntu PC this may help me but I have no idea where to start in terms of the drivers.
breaktheblock said:
The driver issue is a massive stumbling block.
I'm still not sure if the cable will work.
I understand I can use fastboot after the PC recognises the nexus 4.
I have a Lubuntu PC this may help me but I have no idea where to start in terms of the drivers.
Click to expand...
Click to collapse
I use a mac, so im no use when it comes to linux variants etc.
Depending on the power of your pc, you could try using a virtual machine (i.e. virtualbox running windows xp if you have xp disk, or even windows 7). Ive done this before on the mac (xp virtual machine) and it works. This way you can install the correct drivers on a fresh install of windows, without messing with the host OS.
Otherwise, best bet is to uninstall any drivers in your current windows, and install divers from google link i posted earlier.
Sent from my LG-V500 using Tapatalk
breaktheblock said:
The driver issue is a massive stumbling block.
I'm still not sure if the cable will work.
I understand I can use fastboot after the PC recognises the nexus 4.
I have a Lubuntu PC this may help me but I have no idea where to start in terms of the drivers.
Click to expand...
Click to collapse
just outta curiosity, when you plug the phone in (in bootloader mode) change dir to the one with fastboot.exe in and type (in command prompt):
fastboot devices
what output do you get?
ReneX10 said:
just outta curiosity, when you plug the phone in (in bootloader mode) change dir to the one with fastboot.exe in and type (in command prompt):
fastboot devices
what output do you get?
Click to expand...
Click to collapse
nothing happens at all.
I think I have something similar to this http://forum.xda-developers.com/nexus-4/help/twrp-os-installed-connect-to-pc-t2538794
as in i'm stuffed. :crying:
As in "no devices detected" ...what is the output? Pfffft I tried!
ReneX10 said:
As in "no devices detected" ...what is the output? Pfffft I tried!
Click to expand...
Click to collapse
Just to check I am doing it correctly, I launch cmd in windows, change the directory to the location where fastboot is and type "fastboot devices". The result of this is it just gives the directory name again waiting for another command.
I hope I'm not coming across as ungrateful, I assure you this is not the case.
- How My Phone Got Bricked?: (Chinese Version Oneplus 2) I Was On Oxygen OS 3.0 And TWRP 3.0 And I Decided To Flash The Resurrection Remix ROM, I Did A Full Wipe And I Installed The Rom And It Failed To Installed The ROM. Now My Phone Is In A Bootloop With No OS Installed. I Have The Chinese Version OP2
- Current State Of My Device: My Device Is In A Bootloop With No OS Installed, I Did Notice That My Phone Was Not Being Recognized VIA Fastboot & ADB On My PC. I Went Fastboot Mode And My Phone Is Not Being Recognized By PC, And I Went To TWRP, ADB Was Not Working And ADB Sideload Is Not Working. I Also Tried A USB OTG With A USB Drive And Still TWRP Recovery Is Not Recognizing It. How Ever When I Connect My Device To PC And Check Device Manager And Press Scan For Hard Ware Changes My Device Shows Up As "COM 1". I Also Did Try To Put My Phone Into Qualcomm Mode Trying Alot Of Key Combinations But My Phone Is Not Getting Into Qualcomm Mode Or It Just Might Be Me Since I Heard Its Tricky For The Phone To Get Into Qualcomm Mode. I Did Try One Click ADB And Fastboot Installed And Qualcomm USB Driver, Still No Luck. And I Did Try The MEGA Unbrick Guide. I Have Tried This With 3 Other Computers Which Are All Running Windows 10 And Turned Driver Signature Enforcement Off And Still No Luck, And Also A PC Running Linux Mint And Still No Luck. Please Help Me And I Will Put All Thanks On All Of Your Replies And I Really Appreciate Your Help!
- Whats Working:
- My Device Charges From The PC And Wall
- I Am Using The Official OP2 Cable
- Can Access Recovery + Fastboot
- Turns On But In A Bootloop
I think it's a bad cable... if you can get into fastboot and the PC with Windows 10 and Linux both don't see it.. cable
Not sure whats needed on windows, since I never use it....but after a fresh install of Ubuntu 16.04 a few days ago, I did have to install a few adb and fastboot packages before my devices were recognized. Do you know if the adb/fastboot packages and they're dependencies are installed on the Linux mint computer?
If yes, power off phone and plug into computer. Then start phone in fastboot mode. Open a terminal on the PC and run "adb devices" (without quotes of course) .....any output on screen?
foomanjackel said:
Not sure whats needed on windows, since I never use it....but after a fresh install of Ubuntu 16.04 a few days ago, I did have to install a few adb and fastboot packages before my devices were recognized. Do you know if the adb/fastboot packages and they're dependencies are installed on the Linux mint computer?
If yes, power off phone and plug into computer. Then start phone in fastboot mode. Open a terminal on the PC and run "adb devices" (without quotes of course) .....any output on screen?
Click to expand...
Click to collapse
Yeah I did try typing ADB devices and Fastboot devices in both twrp and fastboot. I think the issue might be the cable
evertking said:
I think it's a bad cable... if you can get into fastboot and the PC with Windows 10 and Linux both don't see it.. cable
Click to expand...
Click to collapse
Yeah I think the cable is probably the problem. Although my phone chargers with the cable. I will look into buying a new cable soon but its a little expensive. I will try to buy it next week
fahad999 said:
Yeah I think the cable is probably the problem. Although my phone chargers with the cable. I will look into buying a new cable soon but its a little expensive. I will try to buy it next week
Click to expand...
Click to collapse
I'm sure you been reading and seen people with the same cable as ours with the same problem.. works with charging but not adb or fastboot. But you can try to issue a command with it.. fastboot devices does sometimes come back empty.. just try to do OEM unlock for example.
evertking said:
I'm sure you been reading and seen people with the same cable as ours with the same problem.. works with charging but not adb or fastboot. But you can try to issue a command with it.. fastboot devices does sometimes come back empty.. just try to do OEM unlock for example.
Click to expand...
Click to collapse
My cable did used to work with adb and fastboot before, and I did unlock the bootloader with it before. I think now the cable got broken
Same issue working cable
Same issue... but my cable is working fine. I have a 2nd OP2 and tried the qualcomm connect with my cable and volume up, and worked perfect. More over, I swapped motherboards and still didnt work. I have access to twrp on the phone and I can get into fastboot. But no way to connect to my pc
I have a big problem with the adb driver. It works perfectly to perfection when the phone is accessed both without usb debugging or with, adb devices detect the phone, and even fastboot when booting into the bootloader. The problem is that when I get into adb sideload from the original recovery my pc (windows 10 x64 build 1703) does not detect it, there is no way to make it work. I've tried changing a pc, cable, usb port, but always the same problem. I have installed and tried every type of driver, but there is no way to run it. I think the problem is oneplus5 stock recovery.
extremeinside said:
I have a big problem with the adb driver. It works perfectly to perfection when the phone is accessed both without usb debugging or with, adb devices detect the phone, and even fastboot when booting into the bootloader. The problem is that when I get into adb sideload from the original recovery my pc (windows 10 x64 build 1703) does not detect it, there is no way to make it work. I've tried changing a pc, cable, usb port, but always the same problem. I have installed and tried every type of driver, but there is no way to run it. I think the problem is oneplus5 stock recovery.
Click to expand...
Click to collapse
Is you're device connected with a USB 3.0/3.1 port maybe ? If so try a USB 2.0 port and install the latest ADB driver
Pieter20 said:
Is you're device connected with a USB 3.0/3.1 port maybe ? If so try a USB 2.0 port and install the latest ADB driver
Click to expand...
Click to collapse
I am also facing same problem...please help me
Does the stock recovery even have adb capabilities?
Tried miui 12 and after flashing rom the twrp is gone I tried to reflash it the same way I did first but sadly when I'm on fastboot PC can't detect it. also tried it with other softwares but same result. Device is fine and responds when open but not in fastboot mode. Currently running miui 11 .0.6 China stable. Stucked. Also all drivers are updated
Same here.
I accidentally flashed china stable 11.0.4 zip rom on my global device through twrp and upon booting up twrp was gone and when i plug in usb the pc doesn't detect anything. In order to make pc detect the phone via usb cable i have to reboot phone while plugging usb to laptop that way file transfer option shows up in laptop and adb works but fastboot doesn't work i can force boot to fastboot through adb but upon booting to fastboot the pc stucks at waiting for device. All the drivers are installed
Currently on china stable 11.0.6
Same issue indeed
That's exactly what's happening right now. I hope someone can help us
Quote me if u find any luck.
Same issues
That happens me sometimes. I only reboot the device into fastboot again, reboot the computer, and that it. This may change depending on your computer CPU, mine is AMD. And ussually I have to use a 2.0 USB or if it still does not work a USB 2.0 hub. I know the hub thing is strange but it worked for me when my pc does not detect the phone in fastboot. Hope it helps .
With my PC I have to open device manager, look for the device, usually has a yellow sign next to it. Right click on the device name, click update driver, click browse my computer for driver software, click let me pick from a list of available drivers on my computer and pick mtp USB device. Then I read it. I hope this helps.
daniml3 said:
That happens me sometimes. I only reboot the device into fastboot again, reboot the computer, and that it. This may change depending on your computer CPU, mine is AMD. And ussually I have to use a 2.0 USB or if it still does not work a USB 2.0 hub. I know the hub thing is strange but it worked for me when my pc does not detect the phone in fastboot. Hope it helps .
Click to expand...
Click to collapse
What hub?
Tried with multiple pcs with no success
epicblue8 said:
What hub?
Tried with multiple pcs with no success
Click to expand...
Click to collapse
I use a usb hub that is very old i guess, as it uses MiniUSB. By the way with multiple computer it should work, your error is very strange, I never saw it. A thing that may work is trying to use fastboot on a Linux system (no, with VMs no). So if you can flash a pen drive with a Ubuntu ISO or any linux distro, boot linux,install fastboot and check if it detects your phone.
daniml3 said:
I use a usb hub that is very old i guess, as it uses MiniUSB. By the way with multiple computer it should work, your error is very strange, I never saw it. A thing that may work is trying to use fastboot on a Linux system (no, with VMs no). So if you can flash a pen drive with a Ubuntu ISO or any linux distro, boot linux,install fastboot and check if it detects your phone.
Click to expand...
Click to collapse
Read my 1st reply to this op
Even file transfer option doesn't show up if i connect my phone via usb to laptop.
In order to make pc show file transfer option i have to reboot phone while connecting the phone to pc so.
That way i can use adb but as soon as i boot to fastboot via cmd pc doesn't detect the fastboot mode.
Tried with 3 laptops
Issue Fixed
epicblue8 said:
Same here.
I accidentally flashed china stable 11.0.4 zip rom on my global device through twrp and upon booting up twrp was gone and when i plug in usb the pc doesn't detect anything. In order to make pc detect the phone via usb cable i have to reboot phone while plugging usb to laptop that way file transfer option shows up in laptop and adb works but fastboot doesn't work i can force boot to fastboot through adb but upon booting to fastboot the pc stucks at waiting for device. All the drivers are installed
Currently on china stable 11.0.6
Click to expand...
Click to collapse
Dude I fixed it and I managed to flash global and maybe reflash EU when miui 12 stable arrive
Try another type c cord preferable the original one. I just change the cord and everything went fine fastboot can now be detected via "fastboot devices".
Chipotle crackers said:
Dude I fixed it and I managed to flash global and maybe reflash EU when miui 12 stable arrive
Try another type c cord preferable the original one. I just change the cord and everything went fine fastboot can now be detected via "fastboot devices".
Click to expand...
Click to collapse
Not with original but tried 3 type c cables and 3 pcs
epicblue8 said:
Quote me if u find any luck.
Click to expand...
Click to collapse
hey have find any solutions? we have the same problem