So... now that I think with hindsight, I did something pretty stupid, and I'm going to need some help, since I have no idea what to do.
I have a Nexus 9 tablet, and I never liked it. The OS is just so slow and laggy, and it overheats, and it has many other problems. Quite a couple of times, I installed custom ROM's and so on, and I never had a problem. Let me explain what I did now.
Around a month ago, while looking on the internet, I heard this thing that if I install the original software, but with no encryption, it would work better. It sounded cool at the time, so I downloaded the Nexus Root Toolkit, and did it.
Everything went well. But then I heard about a custom ROM that was apparently working even better, Dirty Unicorns, so using the same toolkit, I installed it. For the first time, my Nexus 9 actually worked the way it is supposed to work, but the custom ROM still had its problems, it crashed from time to time. I was thinking about possibly returning or selling the tablet, so that's why using the Toolkit, I reinstalled the original software. But, if I went all the steps, and also locked the OEM, my device then showed a flag saying that it was a development device, while booting up. So, after messing around with the settings of the Toolkit a little, I decided to reinstall the software, but leave the bootloader unlocked.
But after some time, I reinstalled my Windows, and I also reinstalled the Toolkit. But that's when I started to have problems. My tablet wouldn't connect to my laptop anymore. I used the toolkit and uninstalled drivers, reinstalling others quite a couple of times, and that's where I think that I messed something up. I managed to eventually connect my tablet, and I rooted it, after rooting it, I connected it again. But adb wasn't working for some reason. A little annoyed, I simply copy pasted the zip file of CM13 into my tablet's internal storage, and I rebooted it to the recovery, TWRP. But the recovery failed to flash it, saying something about an Error 7.
Now that I think about it, I was stupid, since after that, I performed a complete factory reset, resetting my TWRP backup too. I tried to connect it again, nothing. It didn't connect at all. I plug it in, my computer doesn't even recognize that something is plugged in. No Nexus 9, no Android Device, no anything. I booted it in fastboot mode, and it worked, my computer recognized it, and after I downloaded a ROM zip file again, I tried to connect the tablet back and flash it manually, but nothing. It didn't recognize anything anymore.
I tried to reinstall the drivers countless times. I deleted what I had, reinstalled it, nothing. I uninstalled and reinstalled the Toolkit. But strangely, now, even if I know that I installed the Google USB drivers, and the ADB drivers, as I even installed Android SDK, if I use USB Deview, it doesn't show me any of them. I can't see any Google or ADB drivers, although I tried installing them multiple times. So now, I'm stuck with a tablet with TWRP and no OS, which I can't connect to my PC, and I can't use ADB or fastboot.
Is it something from my laptop? I can't check to see if it will connect to another PC right now, so I don't know for sure. Is there any way to delete all the traces from my (failed) attempts at reinstalling the drivers, and to install them again properly? Or is it something from the tablet itself? I don't have an OS, so I can't enable USB debugging.
So, shortly, I have no idea what's happening. And I'm quite obviously a noob in all of these. Can anyone help me? Please?
If you boot into the bootloader and from a command prompt type fastboot devices you don't get anything?
Sent from my Nexus 9 using XDA-Developers mobile app
I still couldn't get ADB to work, but I managed to work out fastboot. It may be something from my USB cable, it works perfectly.
I flashed the original software back, and I'll go to check my cable, although I feel kinda stupid that I didn't think about that in the first place.
Thanks for the help anyway.
If fastboot is working and bootloader is unlocked, you can still install a factory image.
Depending of your device download for wifi Version:
https://dl.google.com/dl/android/aosp/volantis-mob30p-factory-2cb57a1b.tgz
If you habe the LTE variant:
https://dl.google.com/dl/android/aosp/volantisg-mob30p-factory-ae9ce05a.tgz
Extract the files and put them into the same directory link fastboot and execute the flash-all.bat
WARNING: Any data will be erased!!! Also TWRP
Now it should boot up with stock firmware.
If you want your device decrypted install twrp. format the internal storage and flash the pure nexus rom which i can highly recommend and is decrypted by default. Dont forget do flash gapps
my issue is same
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
rohanzakie said:
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
Click to expand...
Click to collapse
Use fastboot, not adb.
what if fastboot isn't working, either?
uberSkeptic said:
what if fastboot isn't working, either?
Click to expand...
Click to collapse
Is the tablet in fastboot mode?
madbat99 said:
Is the tablet in fastboot mode?
Click to expand...
Click to collapse
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
uberSkeptic said:
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Hi, uberSkeptic...
Just a quick thought... Have you tried a different USB cable?
Rgrds,
Ged.
Edit & Additional...
The command is not fastboot list devices... it's fastboot devices
One last point... Ensure your Nexus 9 is definitely booted into fastboot mode and not just HBOOT (the bootloader). Take a look at the two screenshots below - your Nexus 9 should look like the screenshot on the right, the one with my green explanatory text.
Apologies for the poor image quality; there's no way of taking a screenshot in the bootloader, so I had to take photographs instead.
Hope this helps and good luck.
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
uberSkeptic said:
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
Click to expand...
Click to collapse
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
GedBlake said:
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
Click to expand...
Click to collapse
Sadly, me too. I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Too bad, too - the tablet is otherwise in great condition and even has a custom-painted backplate (long story).
Thanks for trying to help, though!
uberSkeptic said:
...The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Mmm...
uberSkeptic said:
...I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Click to expand...
Click to collapse
Mmm... (scratches head, raises eyebrow quizzically)...
If I was Hercule Poirot and this was a murder case, and with all the suspects gathered in one room, prior to revealing a brilliant deduction... I'd be casting very dark glances in the direction of your Nexus 9's USB port right now as the likely culprit here.
Think about it. Different computers. Different USB cables. An OTG cable... And none of them work. What's the one thing they all have in common?
Answer: The USB port on the Nexus 9 itself, and where you've replaced the USB daughter-board.
Maybe, possibly, that replacement don't go so well. Maybe there's some unknown problem with it. I can't comment too much on this, 'cos it outside the scope of my knowledge - I'm a software guy; circuit boards and dismantling devices to fix 'em isn't something I'm comfortable with. I always think I'm going to damage something or rip a wire out somewhere, so I bow to your superior knowledge in this area, as I may be talking complete cobblers here. It certainly wouldn't be the first time.
Anyway... Sorry I wasn't able to help find a working solution for you. If anything occurs to me that might help, I'll be sure to let you know.
Rgrds,
Ged.
I would be suspect if the replacement as well if it weren't for the fact that I did it only AFTER the other symptoms/problems appeared. Hence the replacement (which is known good because the battery charges no problem). There cables and everything inside the tablet tests just fine... It feels like the firmware for USB is somehow corrupt or something.
Thanks for all the advice, though. ?
So I can't believe I didn't think of this before, but when I run "dmesg" from the terminal app included w/ TWRP, I see that there a TON of errors, mostly referencing problems accessing the recovery image. I could screenshot it, if anyone at all might be able to tell me a little more specifically what the dmesg log is trying to tell me...
Related
First, let me say that I've searched and searched and looked for all the info I can find about people having similar problems. I've yet to find anything that works for me, and I'm at my wit's end on this...
A few days ago I tried [unsuccessfully] to update CWM on a GTab. I can't get into recovery at all now (it just hangs), but this problem predates that.
The problem I have is that I cannot get any PC to recognize the GTab - in any mode - and I've tried 4 computers with various operating systems. I've tried Fedora, Ubuntu, Windows XP and Windows 7 and none of them will see the GTab at all. They won't see it with debugging on, with it off, in APX mode or anything.
I have gone through half a dozen cables and tried every USB port I've got. It just simply will not recognize the tablet in any way.
I'm toying with the possibility that the port might be damaged, but I can't think of a good reason why that would be the case. The tablet has been well taken care of, and all the other ports work just fine (audio, USB storage, SD).
So, has anybody else run into this issue and found a fix for it?
N0ctrnl said:
I'm toying with the possibility that the port might be damaged, but I can't think of a good reason why that would be the case. The tablet has been well taken care of, and all the other ports work just fine (audio, USB storage, SD).
So, has anybody else run into this issue and found a fix for it?
Click to expand...
Click to collapse
Read: Only ClockWork recovery on boot
Check dmesg to see if tablet is detected: A self inflicted wound
Also: [Q] (really) bricked g-tab.
If you can't boot the tablet at all--into either ROM or recovery--, then there's nothing you can do if your USB isn't working. If you can boot into one of them, then there's hope.
I managed to get CWM installed (was my bad on trying to flash the wrong one to upgrade it anyway). It's always booted just fine into the ROM, and everything works but the USB connection to PC.
I am actually a Linux admin by trade, so I kept an eye on all pertinent system logs and outputs when I tried it on the Linux box. No dice.
N0ctrnl said:
I am actually a Linux admin by trade, so I kept an eye on all pertinent system logs and outputs when I tried it on the Linux box. No dice.
Click to expand...
Click to collapse
Well, you have to be careful about these things. APX mode, for instance, only "connects" to the host PC once, so if you unplug and replug hoping to see USB device recognition messages from the Linux kernel, then you will be disappointed.
What about on the gTablet? Does the kernel print anything pertinent when the cable is connected to the host PC (enable USB debugging first)? Are there any other error messages or diagnostics?
That's the troubling part. I'm finding absolutely nothing. Nothing at all to indicate there's any kind of issue. My guess at this point is that the USB port must be physically broken. I can't see any other way to make sense of it.
Here's one final suggestion: Open the gtab up and disconnect the battery. Wait 1 minute then reconnect the cable.
See if it helps. (It's for people who can't even boot the tablet into APX mode, but, try it before concluding that it is a HW problem).
Happy Holidays Everyone!!!
Phone:
Tmobile T959 aka Samsung Vibrant
It is on stock Froyo 2.2
It has the 3E recovery.
I tried on 2 computers but I can NOT connect via USB it gives me USB malfunction error. The phone does charge. I can put it into download mode vie the 3 finger trick. When you connect it does give you the option to click the green Android icon Connect to USB. So it is talking to the computer, the usb is not totally dead.
Problem:
I need to root this phone. I can not use 1 click or anything else because I think there is a problem with the USB port. I can get files onto the phone via wifi or using the external sd card.
I tried using the update.zip file BUT because I am on the 3E recovery it will say signature failed. I can not run the install.bat to get it back to 2E recovery. I can not use ODIN because the Windows will not detect the phone properly.
What workaround can I use to root this phone? How would I use terminal on the phone?
HOW WOULD YOU ROOT THE PHONE IF YOUR USB PORT WAS "broken"?
THANKS for helping!
As far as I'm aware, you can't root your phone without the USB port working as most (if not all) root methods send their commands and files through ADB. Your pretty much stuck, unless your phone is under warranty. In that case, just go to your carrier and see if they'll give you a replacement device.
TheAndroidGod said:
As far as I'm aware, you can't root your phone without the USB port working as most (if not all) root methods send their commands and files through ADB. Your pretty much stuck, unless your phone is under warranty. In that case, just go to your carrier and see if they'll give you a replacement device.
Click to expand...
Click to collapse
It's out of warranty
I think there may be a way to do it via terminal emulator on the phone.
If this is possible, can someone please post how to do it.
anyone with a work around?
damn!
Am I stuck or does anyone have a way for me to root this phone without the using the USB connection (USB does charge, It will know when you connect to the pc for USB storage BUT windows will say not recognized. I tried it on 4 other pc's same results. I think something is wrong with the OS of the phone. I think the previous owner tried to update with Kies and it messed up the phone. The phone does boot and works.
droiduzr2 said:
damn!
Am I stuck or does anyone have a way for me to root this phone without the using the USB connection (USB does charge, It will know when you connect to the pc for USB storage BUT windows will say not recognized. I tried it on 4 other pc's same results. I think something is wrong with the OS of the phone. I think the previous owner tried to update with Kies and it messed up the phone. The phone does boot and works.
Click to expand...
Click to collapse
Try to install phone drivers for the computer i had to do that for my phone.
maikzen said:
Try to install phone drivers for the computer i had to do that for my phone.
Click to expand...
Click to collapse
I did all of that.
I think something is wrong with the phone's OS that is effecting the usb port.
How do I root this phone WITHOUT the USB port?
There has to be a way!
Can you determinate VID&PID of phone?
I can get into the device with airdroid and see the system files.
Which files do I need (or which apps) and where do I copy them manually to get it rooted?
droiduzr2 said:
I can get into the device with airdroid and see the system files.
Which files do I need (or which apps) and where do I copy them manually to get it rooted?
Click to expand...
Click to collapse
Is there not a device forum where you might could get some better information? My thinking is, a lot of the people (or most of the people) who may know some workarounds can probably help, but they don't check this section very often or at all.
Even if there's not a section for that model, I'm thinking there's probably one quite similar. Also a lot of times, a big portion of the userbase of one phone, will migrate to the same model when they upgrade.
Just throwing out some ideas in case that's helpful. My only advice on the problem itself is that I would look further into the driver issue. I've helped several people with very similar issues that we finally were able to correct.
Have you tried to ADB the device just to pull the serial? With USB debugging enabled. Have you installed the SDK and tried the naked drivers? There's some things to pursue possibly so you can have more information for the person who helps you get things straightened out.
So i have a motorola razr xt910 and i was running the jellywiz rom before this thing happened. So what i did was, boot into bmm recovery, restored cid, did a full wipe and immediately tried to flash the mokee rom. When it was done, i rebooted and got a FASTBOOT FLASH FAILURE. Later, i tried to use RSD lite to fastboot it back to europe ics but the com did not detect the phone. I tried lots of stuff
1. Tried another pc
2. Reinstalling the drivers
3. Tried different cables even the motorola OEM one
4. Spent money to replace the micro usb port on my phone
5. Factory resetting my phone a few times
6. I tried with my friend's razr on a pc with all the appropriate drivers, the pc could detect my friend's phone but not mine
But all of them did'nt work, it is still stuck in fastboot flash failure for 3 weeks now. Any solutions? Thanks in advance
http://forum.xda-developers.com/showthread.php?t=2431617
I had a very similar problem- the proper cable was necessary for my computer to recognize the phone. I uninstalled all of my USB drivers, and let windows reinstall them. This has helped with my SGS3 for recognizing the device. I used RSD 5.7, and having adequate power is imperative.
EDIT
When I say I reinstalled the drivers, I don't mean the Moto drivers. I uninstalled my USB device drivers in Control Panel> Device Manager, and then I reinstalled the motorola device manager, which reinstalled the motorola drivers. However, if your computer doesn't even recognize an unknown USB device connected, then it sounds like either A) a USB cable issue, or B) a USB A port issue.
LuckiestNut419 said:
http://forum.xda-developers.com/showthread.php?t=2431617
I had a very similar problem- the proper cable was necessary for my computer to recognize the phone. I uninstalled all of my USB drivers, and let windows reinstall them. This has helped with my SGS3 for recognizing the device. I used RSD 5.7, and having adequate power is imperative.
EDIT
When I say I reinstalled the drivers, I don't mean the Moto drivers. I uninstalled my USB device drivers in Control Panel> Device Manager, and then I reinstalled the motorola device manager, which reinstalled the motorola drivers. However, if your computer doesn't even recognize an unknown USB device connected, then it sounds like either A) a USB cable issue, or B) a USB A port issue.
Click to expand...
Click to collapse
Sorry for the late reply and thanks for trying to help. Okay so I tried what you said, I uninstalled the USB device drivers and let windows reinstall them rebooted my pc then reinstalled motorola device manager. When i plugged in my phone, the pc still did not detect it although i was using a motorola oem cable fresh from the box. It is definitely not a USB port issue as I tried pluggin in my mouse and omy thumbdrive into the other ports and it could detect them and install the drivers. So any solutions? I'm starting to miss her.
Do you have access to the fastboot menu at all? Any of the options, aside from AP fastboot? What is the battery status?
LuckiestNut419 said:
Do you have access to the fastboot menu at all? Any of the options, aside from AP fastboot? What is the battery status?
Click to expand...
Click to collapse
I have access to the fastboot menu all the options available and the battery is OK. Its just that when i plug it in to the pc it does not detect the phone.
Will the PC recognize the phone under any of the other boot options? (BP Tools, diag, BP SBF flash, Recovery, etc.) When I got to the point where my power source was adequate, and all I had trouble with was PC-Phone recognition, I purchased an OEM Moto charger from Verizon with a cable that said "factory data" on it. I wish I could be of more help, but that was the last step to fix my problem. It recognized immediately, and I successfully flashed. It sounds like you've covered all your bases on the PC end. Let us know if you find a solution!
LuckiestNut419 said:
Will the PC recognize the phone under any of the other boot options? (BP Tools, diag, BP SBF flash, Recovery, etc.) When I got to the point where my power source was adequate, and all I had trouble with was PC-Phone recognition, I purchased an OEM Moto charger from Verizon with a cable that said "factory data" on it. I wish I could be of more help, but that was the last step to fix my problem. It recognized immediately, and I successfully flashed. It sounds like you've covered all your bases on the PC end. Let us know if you find a solution!
Click to expand...
Click to collapse
Thanks for your concern. The pc did not detect the phone in an of the other options so the last resort is using that cable. Is it the same as the factory cable, can i make one myself cause i have a soldering iron at home. Or ordering one online would be better?
I would say go ahead and make one. Just beware, a lot of USB cables (most) have either rubber or hot glue molded around, so it is difficult to expose the contacts on the Micro B connection. There is a great tutorial by MotoCache1, located HERE, that will give you the rundown. It's worth a shot. My only concern is that the idea of the factory data cable is to trick the phone into thinking there is a good power source (without a battery/dead battery). I would think that finding the right USB cable would effectively solve your problem, but go for it, and let us know how it works. You can order the cable (if TeamBlackHat has them... or you can find one sold out of Cali on Ebay, I've heard), and that may be the ticket. Good luck.
LuckiestNut419 said:
I would say go ahead and make one. Just beware, a lot of USB cables (most) have either rubber or hot glue molded around, so it is difficult to expose the contacts on the Micro B connection. There is a great tutorial by MotoCache1, located HERE, that will give you the rundown. It's worth a shot. My only concern is that the idea of the factory data cable is to trick the phone into thinking there is a good power source (without a battery/dead battery). I would think that finding the right USB cable would effectively solve your problem, but go for it, and let us know how it works. You can order the cable (if TeamBlackHat has them... or you can find one sold out of Cali on Ebay, I've heard), and that may be the ticket. Good luck.
Click to expand...
Click to collapse
Thanks for the tip. I will give it a shot when I have the time. However I was wondering why my phone would run into such a problem. Before that when i flashed roms and soft bricked it, i could still recover it using rsd lite and fastboot files. Secondly, my usb cable was woking fine until just before i landed into this mess. The phone could not be detected by the pc in usb storage mode so i resorted to using google drive instead of actually solving the problem.
By the way, could i have the model number of the motorola oem factory data cable you bought. I dont live in the US so i may need to buy it from another shop. Thanks!
You may very well have a hardware problem, if you were having connection problems before the fastboot errors. Could be the contacts on the micro female in your phone. It sounds like you definitely have a data transfer problem if you couldn't mount for mass storage.
The only number I could locate is SKN6430A.
Sent from my XT912 using xda app-developers app
LuckiestNut419 said:
You may very well have a hardware problem, if you were having connection problems before the fastboot errors. Could be the contacts on the micro female in your phone. It sounds like you definitely have a data transfer problem if you couldn't mount for mass storage.
The only number I could locate is SKN6430A.
Sent from my XT912 using xda app-developers app
Click to expand...
Click to collapse
I already replaced the micro usb port on my phone after i bricked it but it still did not work. How to solve a data transfer problem? Thanks.
Appropriate USB cable, unfortunately. Motorolas are very picky. Even if you weren't having problems with a particular cable before, like me (fastboot flash would start, but not finish, first time I encountered a problem), the right cable solved my it. OEM Motorola data cable.
Sent from my XT912
LuckiestNut419 said:
Appropriate USB cable, unfortunately. Motorolas are very picky. Even if you weren't having problems with a particular cable before, like me (fastboot flash would start, but not finish, first time I encountered a problem), the right cable solved my it. OEM Motorola data cable.
Sent from my XT912
Click to expand...
Click to collapse
Okay I guess it all goes down to the cable. I've got a SKN6378A from motorola but it doesn't work. So what is the appropriate cable i should get or should i just send my phone to the motorola service centre and ask them to help me solve it?
I'm certain they can diagnose the problem, though I couldn't say for certain what the cost would be. You may have better luck purchasing a used phone on eBay. I can understand your frustration, to an extent, though you're problem is turning out to be more complicated than mine! Motorola tech support may also be able to help, remotely.
But But Were
LuckiestNut419 said:
I'm certain they can diagnose the problem, though I couldn't say for certain what the cost would be. You may have better luck purchasing a used phone on eBay. I can understand your frustration, to an extent, though you're problem is turning out to be more complicated than mine! Motorola tech support may also be able to help, remotely.
Click to expand...
Click to collapse
Hey I Know You Said You Already Tried Using A Different Computer But Were They Different Operating Systems? I Had A Similar Problem RSDlite Wouldn't Recognize My Phone On Windows 8 But Connected Just Fine On Windows 7.
fastboot not detected
while the PC recognize the phone under any of the other boot options BP, Tools, diag (here the phone goes black), BP SBF flash, Recovery, why the fastboot is not recognized? im on a xt910, i have no system.. and i remember that previosly, he wasnt able to be recognized even as an mass storage... so weird.. then i messed up, and i cant do nothing because all the do able thing is via fastboot.. is there any chance to do something via recovery stock without getting operation aborted?.. oh, another hint, i mess a little with the entry of the female usb on the xt910, and now i have an "unknown device" maybe is broken.. and if i disarm it, and i cut a cable, and green and white should be data, maybe ill be able to flash something via rsd.. damn is so weird that the bp is recognized in rsd but fasboot not.. and i cant buy nothing, i just have a knife, two cables(i cutted one to put the negative positive directly to the battery) and wi fi. thanks in advances, and yes i know that is an old thread, but i dont know what else to do. /And sorry for my english, i dont speak it.
Hi guys,
I have been searching for hours but I can't seem to find how to fix my problem.
I have a new Z5 Compact that I was trying to flash with the stock firmware but I somehow managed to brick it. I don't think I had the drivers installed properly when I tried to flash with flashtool but since flashtool didn't even detect my phone or appear to begin flashing it I don't know how I bricked it. Anyway after trying for hours to fix it on my own I can't seem to find the information that I need. I have installed the drivers properly as far as I can tell by allowing unsigned drivers on windows 10 but whenever I boot to flash mode the phone isn't detected. Nothing even comes up in Device Manager so there are no options to update drivers or anything. I just hold the volume down button, plug in the usb, the LED briefly flashes red before holding on green and then nothing happens. Neither Flashtool or PC Companion detect the phone and I have tried this on 2 different laptops running Windows 7 and Windows 10. If anyone has any instructions on how to get this to work on Ubuntu I'm willing to try that too as I also have Ubuntu installed but I am really at a loss for what else I can try.
Any help would be greatly appreciated.
Thank you
tokococo said:
Hi guys,
I have been searching for hours but I can't seem to find how to fix my problem.
I have a new Z5 Compact that I was trying to flash with the stock firmware but I somehow managed to brick it. I don't think I had the drivers installed properly when I tried to flash with flashtool but since flashtool didn't even detect my phone or appear to begin flashing it I don't know how I bricked it. Anyway after trying for hours to fix it on my own I can't seem to find the information that I need. I have installed the drivers properly as far as I can tell by allowing unsigned drivers on windows 10 but whenever I boot to flash mode the phone isn't detected. Nothing even comes up in Device Manager so there are no options to update drivers or anything. I just hold the volume down button, plug in the usb, the LED briefly flashes red before holding on green and then nothing happens. Neither Flashtool or PC Companion detect the phone and I have tried this on 2 different laptops running Windows 7 and Windows 10. If anyone has any instructions on how to get this to work on Ubuntu I'm willing to try that too as I also have Ubuntu installed but I am really at a loss for what else I can try.
Any help would be greatly appreciated.
Thank you
Click to expand...
Click to collapse
sounds dumb but have you tried a different port and different cable? i ran into the same problem and found out one of the ports on my laptop doesnt work for data. flashtool is a major pain, it took me three pcs to find one that it worked with and then it took a good 5 tries and reboots to have a successful flash. flashing twrp and then xpower would be easier imo.
civicsr2cool said:
sounds dumb but have you tried a different port and different cable? i ran into the same problem and found out one of the ports on my laptop doesnt work for data. flashtool is a major pain, it took me three pcs to find one that it worked with and then it took a good 5 tries and reboots to have a successful flash. flashing twrp and then xpower would be easier imo.
Click to expand...
Click to collapse
Yeah, I have tried 7 ports and 3 cables across two different pcs. There's a desktop I can try on but I'll wait until tomorrow. It's really frustrating. I just wanted to root so that I could batch install my apps from Titanium but now I have got a brick. In the time that I have spent trying to fix it I could have selected and installed all the apps individually.
tokococo said:
Yeah, I have tried 7 ports and 3 cables across two different pcs. There's a desktop I can try on but I'll wait until tomorrow. It's really frustrating. I just wanted to root so that I could batch install my apps from Titanium but now I have got a brick. In the time that I have spent trying to fix it I could have selected and installed all the apps individually.
Click to expand...
Click to collapse
keep trying, it'll work after you figure out whats wrong with your install, flashtool is real finnicky. If your already soft bricked and only want root id suggest fastboot twrp 3.0.2 then flash xpower 3.0 and be done with it. the only real reason to use flashtool is to flash a new image onto the phone because you cant take an ota.
civicsr2cool said:
keep trying, it'll work after you figure out whats wrong with your install, flashtool is real finnicky. If your already soft bricked and only want root id suggest fastboot twrp 3.0.2 then flash xpower 3.0 and be done with it. the only real reason to use flashtool is to flash a new image onto the phone because you cant take an ota.
Click to expand...
Click to collapse
Thanks for your help. So I can do that without unlocking the boot loader?
tokococo said:
Thanks for your help. So I can do that without unlocking the boot loader?
Click to expand...
Click to collapse
bootloader has to be unlocked before doing any of this.
civicsr2cool said:
bootloader has to be unlocked before doing any of this.
Click to expand...
Click to collapse
Oh, you mean to do that once I have fixed my current issue.
Hmm, I seem to be having a smiliar issue, except instead of flashmode, mine isn't detected in fastboot mode, tried a crap load of drivers and usb ports etc..
EDIT: Got it fixed after following this guide
http://forum.xda-developers.com/z5-compact/general/unlock-bootloader-z5-compact-t3236237
RaunoT said:
Hmm, I seem to be having a smiliar issue, except instead of flashmode, mine isn't detected in fastboot mode, tried a crap load of drivers and usb ports etc..
EDIT: Got it fixed after following this guide
http://forum.xda-developers.com/z5-compact/general/unlock-bootloader-z5-compact-t3236237
Click to expand...
Click to collapse
I tried following that guide but when I try to install the driver it just says "The INF file you selected does not support this method if installation". You didn't happen to have that problem and find a workaround did you?
Just an update on what I have tried if anyone has any suggestions...
I tried inserting a SIM in case that would make any difference. I have also tried it on a desktop pc as well as the two laptops now which is windows 7, 8.1 and 10. The Windows 8.1 attempt was a clean install and I used the advanced boot method to enable the installation of unsigned drivers. I had high hopes for that but it didn't work. What I find curious is there is no activity when I plug the phone in, in flash mode. If I plug it in, in fastboot mode it searches for drivers and the device appears in device manager but with flash mode I get nothing. I'm beginning to think that perhaps the device itself has a faulty flash mode.
tokococo said:
I tried following that guide but when I try to install the driver it just says "The INF file you selected does not support this method if installation". You didn't happen to have that problem and find a workaround did you?
Click to expand...
Click to collapse
Sadly no :/
I managed to flash a Z5 Compact with the same model number without any issues on the same computer that won't detect my handset so I'm pretty sure that it's an issue specific to this handset. Thanks everyone for their suggestions.
March 22 2019 - Solved because I'm an idiot. Story on page 2
Trying to Flash TWRP, but the adb packages and driver's I been using that I can find all over the internet just aren't freaking working.
Specifically it's just Fastboot giving me problems, It doesn't even detect devices.
What I need help with:
Adb communicating with Fastboot
How far I got:
Unlocked bootloader (unlock symbol when booting)
Installed plethora of Adb Driver's via Google, Xiaomi, Qualcomm
Used USBDeview to uninstall all drivers even from my past devices and try reinstalling just drivers involving Xiaomi, Poco ect...
What does work:
Adb commands recognized in Miui
Adb commands recognized in Miui Recovery as sideload (after selecting pc suite option)
Miui unlocking tool (was able to unlock and can still detect the device unlocked in Fastboot)
In Miui File Transfer & PTP mode
What I tried:
Different USB ports 2.0 & 3.0 directly in the back of the PC and the front hub
Different USB C cords with and without extension cord (even though that shouldn't matter)
Different drivers old and new
Powershell & CMD as administrator.
What's already been done before you suggest it:
2nd computer, different ports, satanic ritual, different cords, turning PC on and off again after driver installs.
Trying methods from First 5 results when you Google anything along the lines of "Poco f1 adb Fastboot not recongnized"
Uninstalling drivers and retrying
USB Debugging on, duh.
Oem unlock on, duh.
Basically it's this, clearly the device is being recongnized and being talked to, just able to unlock the device via Xiaomi unlock tool is proof enough of that it's detected in and out of Fastboot, but in a adb window via powershell or cmd-here, it's just not recongnized my device in Fastboot. In Miui or recovery theres no issue, they communicate fine.
Or if there's an alternative way to install TWRP that doesn't involve Fastboot I'm all ears on that.
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
lolmensch said:
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
Click to expand...
Click to collapse
I want the recovery so I have an option that isn't miui.
My phone isn't slow, but it's running more than a fair share of mi bloat.
lolmensch said:
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
Click to expand...
Click to collapse
Also can you roll back to 8.1 without twrp, root, or adb?
I tried rolling back via the update screen and selecting the package/downgrade, but Miui won't allow installing/flashing older software, which is something I tried before.
No one else has this problem?
Chocolina said:
No one else has this problem?
Click to expand...
Click to collapse
Why not try Flashify? It comes in the form of an apk and it only requires root, no fastboot. Through it, you can flash TWRP.
Are you connecting the phone to an Intel computer or an AMD? AMD Ryzen has an issue.
tnsmani said:
Why not try Flashify? It comes in the form of an apk and it only requires root, no fastboot. Through it, you can flash TWRP.
Are you connecting the phone to an Intel computer or an AMD? AMD Ryzen has an issue.
Click to expand...
Click to collapse
Don't you need TWRP to install root?
I haven't rooted 1st and then did recovery since the Nexus 5 days, every device I've had since has had root guides that wanted me to fastboot flash the recovery first and install root that way.
And i dont know if my pc is Ryzen, not a pc gamer so all I have is on board, but it is old amd machine running windows 10. I also don't have a monitor these days, I have my pc setup to accept remote desktop so I interact with it that way because it's rare I need a pc these days
All I know is adb works with miui and recovery (sideload) fine, it's fastboot giving me problems, and all the root guides require fastboot
Also same exact issue regarding my mi pad I just got too
https://forum.xda-developers.com/mi-pad-4/help/please-help-troubleshoot-xiaomi-t3910249
lolmensch said:
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
Click to expand...
Click to collapse
Tell me more about this Linux/your method
I never used Linux, so I don't know what I'd do to get it or if I could boot it temporarily off of another form of storage or something.
Chocolina said:
Trying to Flash TWRP, but the adb packages and driver's I been using that I can find all over the internet just aren't freaking working.
Specifically it's just Fastboot giving me problems, It doesn't even detect devices.
Click to expand...
Click to collapse
Are you running a Ryzen PC ? Xiaomi drivers have been reported to have problems with Ryzen builds.
Dose the roms solve touch issue???????
MasterFURQAN said:
Are you running a Ryzen PC ? Xiaomi drivers have been reported to have problems with Ryzen builds.
Click to expand...
Click to collapse
How would I know if it's ryzen?
It's a prebuilt from 5 or more years ago
Chocolina said:
How would I know if it's ryzen?
It's a prebuilt from 5 or more years ago
Click to expand...
Click to collapse
If it's more than 5 years old, then it's not ryzen. Fyi Ryzen is the newest range of CPUs from AMD.
I went out and bought an Intel laptop and it still won't work!!
Found and addressed my issue, and it was because of my Stupidity and old habits keeping me from following directions. But I'm also a little angry at the directions themselves for omitting information that would have been useful to me.
So an old habit of mine is before flashing anything in fastboot, I alway run adb commands to see if my phone, fastboot, and windows are all taking to each other and playing nice. Every phone and device I've had until now hasn't had an issue.
If adb or other apps was showing me my connected devices in System and in Recovery, then why the hell wouldn't it do so in fastboot. So old habits with all my devices since 2012 have been reinforcing my behavior for years until I got this Xiaomi Pocophone and Xiaomi Mi Pad. So as a requisite I've always had and continued to check my devices in adb and performing a reboot test before performing a flash just to make sure the device was listening and taking commands.
The problem with the dozens of guides and videos I watched, none of them said that checking for device first didn't always work, so before flashing recovery I kept trying everything I could to get devices to read back in fastboot or accept a reboot command.
Then In one of the half of dozen xiaomi mi pad adb packages I downloaded, someone wrote a simple script that did the flash anyway even though checking to see the device was recognized came up empty.
Apparently I could have been sending flash commands all this time despite devices showing a blank.
So I did so on pocophone to find out devices and reboot commands didn't work but apparently flashing commands do.
I went out and bought (with the intent to return) a ****ty Intel laptop (made by RCA lmao) just to come to the conclusion that I should have just followed the guides in the first place and save myself trouble instead of relying on my past knowledge and habits.
Chocolina said:
Found and addressed my issue, and it was because of my Stupidity and old habits keeping me from following directions. But I'm also a little angry at the directions themselves for omitting information that would have been useful to me.
So an old habit of mine is before flashing anything in fastboot, I alway run adb commands to see if my phone, fastboot, and windows are all taking to each other and playing nice. Every phone and device I've had until now hasn't had an issue.
If adb or other apps was showing me my connected devices in System and in Recovery, then why the hell wouldn't it do so in fastboot. So old habits with all my devices since 2012 have been reinforcing my behavior for years until I got this Xiaomi Pocophone and Xiaomi Mi Pad. So as a requisite I've always had and continued to check my devices in adb and performing a reboot test before performing a flash just to make sure the device was listening and taking commands.
The problem with the dozens of guides and videos I watched, none of them said that checking for device first didn't always work, so before flashing recovery I kept trying everything I could to get devices to read back in fastboot or accept a reboot command.
Then In one of the half of dozen xiaomi mi pad adb packages I downloaded, someone wrote a simple script that did the flash anyway even though checking to see the device was recognized came up empty.
Apparently I could have been sending flash commands all this time despite devices showing a blank.
So I did so on pocophone to find out devices and reboot commands didn't work but apparently flashing commands do.
I went out and bought (with the intent to return) a ****ty Intel laptop (made by RCA lmao) just to come to the conclusion that I should have just followed the guides in the first place and save myself trouble instead of relying on my past knowledge and habits.
Click to expand...
Click to collapse
Thank you for the info. I learnt something new today.
I also have the same habit of checking whether the adb devices and fastboot devices commands work before starting any flashing. However I don't check the reboot command. It still is a good habit notwithstanding what you have discovered. What happened to you has not happened to me so far, so I am filing this knowledge for future use if the occasion arises.
tnsmani said:
Thank you for the info. I learnt something new today.
I also have the same habit of checking whether the adb devices and fastboot devices commands work before starting any flashing. However I don't check the reboot command. It still is a good habit notwithstanding what you have discovered. What happened to you has not happened to me so far, so I am filing this knowledge for future use if the occasion arises.
Click to expand...
Click to collapse
It was a headache because my precautions weren't working. Next time I'm just going to check if it'll take flash commands anyway before asking for help.
On the plus side, I got to learn what a laptop made by RCA is like. It's **** sure, I'd expected as much, but it was as bad, if not worse than those $99 "windows 8" tablets from 2014-2015 running those archaic Intel Z3735 Atom series processors. Stay away