Here is what I stand.
I have soft bricked my TF201 and I am trying to restore it using ADB per the recovery thread.
I am stuck in CWM recovery boot loop.
When I entered bootloop USB Debugging was not enabled and I dont have a computer that had/has the TF201 drivers previously installed.
Computer system is Windows Vista.
When the USB plugs into the computer it is recognized as "Transformer".
I have downloaded the drivers from the Asus site, from ADB repositories, and from other sites proportedly hosting drivers that work. None of those drivers have worked when attempting to manually install them (Device Manager > Update Driver Software).
How can I install drivers to get ADB to recognize my device if I cannot enable USB Debugging?
First i would install the recovery using fastboot again. Download drivers (link) and install it, download new cwm touch recovery (link), Restart your prime by holding the volume down button, wait, then press down to switch to the usb symbol, then press volume up. Now you are in fastboot mode. Enter the following command at the terminal or command prompt window : fastboot -i 0x0b05 flash recovery (path to cwm recovery img)
Thanks, Ive got USB working and was able to flash to CWM Touch Recovery.
Now when I try to push (adb push update.zip /sdcard/) I keep getting: Protocol Failure
This happens every 3rd or 4th time I try to push. The rest of the time I get a daemon failure.
Any suggestions on how to push a ROM so I can install it? (I dont have one on the internal SDCARD any longer)
Related
I spent the whole of yesterday trying to add MoDaCo custom rom. from this post http://forum.xda-developers.com/showthread.php?t=552591 The first of my problems was that I couldn't get the right driver which now seems to be fixed now comes up as - ADB Interface -HTC Bootloader.
So this now means that when i go to fastboot I can load cyanogenMod (system recovery) by typing fastboot boot cm-hero-recovery.img
However none of these commands below in the CMD work. All i get is error: device not found
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
Any ideas please
robboy said:
I spent the whole of yesterday trying to add MoDaCo custom rom. from this post http://forum.xda-developers.com/showthread.php?t=552591 The first of my problems was that I couldn't get the right driver which now seems to be fixed now comes up as - ADB Interface -HTC Bootloader.
So this now means that when i go to fastboot I can load cyanogenMod (system recovery) by typing fastboot boot cm-hero-recovery.img
However none of these commands below in the CMD work. All i get is error: device not found
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
Any ideas please
Click to expand...
Click to collapse
Still sounds like a driver issue.. have you installed HTC + the SDK?
Restert ur handset into bootloader, hold power + back, then plugin the USB cable.. "FASTBOOT" (,In the red square) shoud change to FASTBOOT USB..
Skip the "adb shell reboot bootloader" and go straight to the next line and boot the recovery image via fastboot
should be plain sailing from there
It does change to fastboot usb on red. The only thing I can think of is do you have to install the sdk as I couldn't see a setup app. I just have all the files on the c dive. Will try skipping the first step when I get home
you dont install the sdk, just unzip it
thats right just the unzip, sorry, the drivers come with the SDK, if you still have no sucsess, do a Controll pannel > system >device manager then scan for device changes, if it finds the device select to install drivers and point it to the SDK folder
jackdaniels_lee said:
Still sounds like a driver issue.. have you installed HTC + the SDK?
Restert ur handset into bootloader, hold power + back, then plugin the USB cable.. "FASTBOOT" (,In the red square) shoud change to FASTBOOT USB..
Skip the "adb shell reboot bootloader" and go straight to the next line and boot the recovery image via fastboot
should be plain sailing from there
Click to expand...
Click to collapse
Grrrr still no joy. Just device not found. Im deleting all files that I have downloaded for drivers sdk etc and try and start again from scratch.
Do I need to partion my SD card before I do this as i have been having probs with that as well.
jackdaniels_lee said:
thats right just the unzip, sorry, the drivers come with the SDK, if you still have no sucsess, do a Controll pannel > system >device manager then scan for device changes, if it finds the device select to install drivers and point it to the SDK folder
Click to expand...
Click to collapse
Done that as well. If My device runs fastboot this should mean the drivers are correct.
robboy said:
Done that as well. If My device runs fastboot this should mean the drivers are correct.
Click to expand...
Click to collapse
yes if u succeed to enter fastboot, it means it had recognised the phone? are u using windows 7 by the way? cause u have to download the precise drivers for the OS u r using whether x64, win 7 ....
I seem to remember having problems with this until I enabled the USB debugging mode in the options somewhere.
As for drivers, I'm running Windows 7 x64 and the x64 Vista drivers did the job fine.
so its been already 2 months no way i can fix this still doing the same thing turn on boots and then loops to CWM same thing over n over and no connection to my computer so basicly now i feel i waisted 500 billz and used it from feb till now and no way i can fix it no ideas and asking around how can i putit back to live no answers yet nada so my guessin is not way a big amount and send it to asus or is there still a way to save it? i really missed my prime u use it alot but since still stuck on loop from EEE Pad to CWM and no mount :crying:
klutch said:
so its been already 2 months no way i can fix this still doing the same thing turn on boots and then loops to CWM same thing over n over and no connection to my computer so basicly now i feel i waisted 500 billz and used it from feb till now and no way i can fix it no ideas and asking around how can i putit back to live no answers yet nada so my guessin is not way a big amount and send it to asus or is there still a way to save it? i really missed my prime u use it alot but since still stuck on loop from EEE Pad to CWM and no mount :crying:
Click to expand...
Click to collapse
I am having the same problem man......I can't get the PC to detect my prime so I can't push any .zip
if you get adb to work, this is a solution http://forum.xda-developers.com/showthread.php?t=1661128&highlight=boot+loop
@klutch
what have you done before your prime stuck in the boot loop?
tried to flash anything or something like that
if i remember correctly you can't mount the prime as a removeable disk in CWM unless they fixed it
your best bet is to go into CWM and use adb to push the flashable zip files in there
you can do that by the following commands
Code:
adb push [directory/file name.zip] [/mnt/sdcard/]
if your device is not recognized by windows, then ADB does not work. that's the OP's problem.... and mine as well. ~$230 to fix my prime.
have you already tried to enter fastboot mode and flash a fresh rom from there?
I was able to get the PC detect my TFP by installing the driver from this link
[ADB/FB/APX Driver] Universal Naked Driver 0.7
You should be able to adb afterwards....Then follow 'OPTION 1a" from this link
[HOW-TO] Unbrick your Transformer Prime (or not)
I installed nvflash to make sure this won't happen again
hope this helps!
naked drivers
urboy4mbx said:
I was able to get the PC detect my TFP by installing the driver from this link
[ADB/FB/APX Driver] Universal Naked Driver 0.7
You should be able to adb afterwards....Then follow 'OPTION 1a" from this link
[HOW-TO] Unbrick your Transformer Prime (or not)
I installed nvflash to make sure this won't happen again
hope this helps!
Click to expand...
Click to collapse
i dont get how to install naked drivers when everytime i plug in my prime it just says unknown device in device manager and when i try to update the driver it says i have the best or latest driver. plz someone help me!!!!
InkD_up_G33k said:
i dont get how to install naked drivers when everytime i plug in my prime it just says unknown device in device manager and when i try to update the driver it says i have the best or latest driver. plz someone help me!!!!
Click to expand...
Click to collapse
in CWM while the TFP is plugged to your PC, click "update driver" and make sure you point to the location where "android_winusb.inf" file is located.
if you are in CWM the TFP will pick up "android_winusb.inf" driver
if you are in fastboot mode the TFP will pick up "android_apxusb.inf" driver
Also, I had to try on 3 different computers to make this work.
i just found out wat happen the original usb asus was messed up and i brought one on ebay and it worked so all this for a USB cable i was going crazy
urboy4mbx said:
in CWM while the TFP is plugged to your PC, click "update driver" and make sure you point to the location where "android_winusb.inf" file is located.
if you are in CWM the TFP will pick up "android_winusb.inf" driver
if you are in fastboot mode the TFP will pick up "android_apxusb.inf" driver
Also, I had to try on 3 different computers to make this work.
Click to expand...
Click to collapse
Ok so wen i plug in my tfp while in cwm the only thing that pops up in device manager is unown device in the usb controllers section thats it and wen i try to update driver it says i i have the best driver already and im pointing it to a folder on my desktop with the naked drivers and nothing evn with have disk it says its not 64 bit or sumtn. im about ready to give up and just sell it to someone who prolly can fix it cuz i cant seem to get naked drivers to install to let the computer recognize my tfp so i can adb
InkD_up_G33k said:
Ok so wen i plug in my tfp while in cwm the only thing that pops up in device manager is unown device in the usb controllers section thats it and wen i try to update driver it says i i have the best driver already and im pointing it to a folder on my desktop with the naked drivers and nothing evn with have disk it says its not 64 bit or sumtn. im about ready to give up and just sell it to someone who prolly can fix it cuz i cant seem to get naked drivers to install to let the computer recognize my tfp so i can adb
Click to expand...
Click to collapse
as I asked earlier, did you try to set your prime into fastboot mode and flash a fresh rom from there?
if it does not work with windows, you could try linux, e.g. an ubuntu live cd. download the linux fastboot from here
you can flash a new rom with
fastboot -i 0x0b05 flash boot "path to rom blob"
or new recovery using
fastboot -i 0x0b05 flash recovery "path to recovery image blob"
unfortunately i'm not able to supply links to download fastboot, sorry for that.
klutch said:
i just found out wat happen the original usb asus was messed up and i brought one on ebay and it worked so all this for a USB cable i was going crazy
Click to expand...
Click to collapse
wow, I thought you tried a diff cable already?? well, glad it was just the cable for you! I tried 3 diff cables on mine and it still didn't work
apfel.kuchen said:
as I asked earlier, did you try to set your prime into fastboot mode and flash a fresh rom from there?
if it does not work with windows, you could try linux, e.g. an ubuntu live cd. download the linux fastboot from here
you can flash a new rom with
fastboot -i 0x0b05 flash boot "path to rom blob"
or new recovery using
fastboot -i 0x0b05 flash recovery "path to recovery image blob"
unfortunately i'm not able to supply links to download fastboot, sorry for that.
Click to expand...
Click to collapse
yea when i hold power and volume down it doesnt work as usual when it tells you to press up in the next five seconds. and ive tried restoring back up and flashing a new rom but it just boots up into cwm and my sdcard slot is ****ed up becuz of my lil cousins sticking **** inside the slot so it doesnt read anymore so i cant push files or put files on like that either.
pressing vol- + power and vol+ after 5 seconds should lead you into recovery (CWM) but fastboot is somewhat different. if you do not press vol+ after 5 seconds but either wait longer, you will see a screen where to select how to proceed (USB mode, android, and something else). if you select usb and then connect the tablet to your pc you are in fastboot mode and should be able to flash rom and recovery using the fastboot tool on your PC. using this you wouldn't need a working sd card, only a rom and/or recovery in blob format.
apfel.kuchen said:
pressing vol- + power and vol+ after 5 seconds should lead you into recovery (CWM) but fastboot is somewhat different. if you do not press vol+ after 5 seconds but either wait longer, you will see a screen where to select how to proceed (USB mode, android, and something else). if you select usb and then connect the tablet to your pc you are in fastboot mode and should be able to flash rom and recovery using the fastboot tool on your PC. using this you wouldn't need a working sd card, only a rom and/or recovery in blob format.
Click to expand...
Click to collapse
yes i know that but thats the problem im not able to go into fastboot i tried it, it reboots into recovery on its own and i know the only way im going to unbrick this is by adb but my device isnt showing up on my computer just unknown device under usb contollers which i tried to install the naked drivers but is unable to
hmm.. ok thats bad.
do you have a linux machine to check if it is a windows problem?
because it doesn't really make sense to me that CWM is working but adbd not.
i may have found a solution
this is just my experience but it seems like the different adb's that people are posting of the forums are outdated and dont work properly with some primes. I have tried several the windows task manager said "asus transformer prime adb interface" with the naked drivers as soon as i used the adb included in the sdk from <developer.android.com/sdk/index.html> it worked. so install the sdk then in the command prompt navigate to the platform tools inside where it was installed us the adb.exe found there.
as far as using the wrong drivers when you remove the device there might be the option to delete the device driver check that then scan for new devices......point it to where ever you unziped
this may not work for you but this is what finally resurrected my prime after 24 hours
Okay I just had the same problem ... after some research and some trial and error I was able to fix my prime.
First to make your life simple open a command prompt. You will have a flashing cursor next to the directory that you command prompt defaults to.
In my case it was c:/users/peter
You can put the sdk files anywhere on your computer but if you put them in the default command prompt folder you don't have to change the directory with dos commands.
Next with your prime not connected go into the device manager and delete any instances of the prime. Reboot your PC.
Next download the universal naked drivers
Connect your prime, if you go back into device manager you'll find it under USB devices. Click on upgrade drivers and navigate to the universal naked drivers. It should install if not your universal naked drivers might be outdated but uninstalling / deleting the previous instance of your prime should take care of any issues.
Now do the following:
Make sure your Prime is in Recovery mode (CWM)
Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
After this I recommend installing the androidroot.mobi custom boot loader and nvflash to make your prime unbrickable I also changed my recovery from cwm to twrp2 to help eliminate this from happening again.
Same here
What if you only have TWRP Recovery and not CMW? I have the exact same problem, but none of my machines will even detect a new device to find drivers for. I have a laptop with Ubuntu 12.04, another laptop with Windows XP, and an iMac with Snow Leopard. All have Android SDK and ADB but I can not get either to detect the device in Recovery mode. I tried fast boot, but every time I click the USB symbol, the TFP just locks up and freezes and still no detection. Can anyone help? I know if I can get it detected, I will be able to handle the rest.
pcdonovan said:
Okay I just had the same problem ... after some research and some trial and error I was able to fix my prime.
First to make your life simple open a command prompt. You will have a flashing cursor next to the directory that you command prompt defaults to.
In my case it was c:/users/peter
You can put the sdk files anywhere on your computer but if you put them in the default command prompt folder you don't have to change the directory with dos commands.
Next with your prime not connected go into the device manager and delete any instances of the prime. Reboot your PC.
Next download the universal naked drivers
Connect your prime, if you go back into device manager you'll find it under USB devices. Click on upgrade drivers and navigate to the universal naked drivers. It should install if not your universal naked drivers might be outdated but uninstalling / deleting the previous instance of your prime should take care of any issues.
Now do the following:
Make sure your Prime is in Recovery mode (CWM)
Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
After this I recommend installing the androidroot.mobi custom boot loader and nvflash to make your prime unbrickable I also changed my recovery from cwm to twrp2 to help eliminate this from happening again.
Click to expand...
Click to collapse
I am having a REAL BUGGER of a time with my Xiaomi Redmi Note 3 Pro (Snapdragon)!
1. It is not recognized by ADB in Fastboot mode.
2. I suspect it shipped wit a vendor ROM, and I'm trying to flash latest Official MIUI Global Dev (Marshmallow) ROM, but I keep getting errors in MI Flash (screenshot attached).
3. I want to Flash TWRP, BUT ADB isn't working, AND I cannot get to the download page for the cracked bootloader.
4. Seriously considering Resurrection Remix ROM, instead, but most of the above issues still apply.
I am NOT new to custom recoveries, flashing ROMS, ADB etc, BUT I am dealing with a new PC (Windows 10 Home, 64 bit, like my old (dead) laptop), and I'm new to this device.
PLEASE HELP. (Quite frustrated)
Fastboot won't recognize adb commands you have to use fastboot.
What you can try is booting into emergency download mode and using my flash to flash it from there. I think it's " adb reboot edl" while the device is on with USB debugging or using the mi updater app ( tap the three dots I think).
I think that this is not the correct section for your question, and i dont know the procedure that you follow but try to follow this procedure:
-Connect the phone at pc with USB cable
-Make sure that debug mode and OEM unlock was abilitate in dev settings
-Copy twrp.img in adb folder
-Shut down the phone and press power botton and - vol buttons for enter in fastboot mode
-Run this commands by terminal open in adb folder
fastboot devices
-If fastboot recognize correctly the device run this command
fastboot fash recovery nameoftwrp.img
-After reboot the device with this command
fastboot reboot
When the phone reboot press immediatily vol + for enter in twrp
Good luck
GOT IT! FINALLY!
-I finally got ADB to connect, and was able to enter EDL through ADB.
-Re-downloaded ROM from web.
-Re-extracted.
-FLASHED SUCCESSFULLY!
-SETUP COMPLETED SUCCESSFULLY!
-YAY!
(I think the original download was corrupted, somehow.)
I'm trying to flash TWRP, i've got ADB and i've got the Universal ADB Drivers. The device is properly detected when in EUI and my Device ID is displayed correctly when I type 'adb devices', however when I reboot into fastboot and type 'fastboot devices', nothing is listed and cannot continue.
Which drivers do I use? What is it that I need to continue?
Thanks!
Edit: Nevermind, connected it into my linux machine and got it to work easier (lol winBLOWS amirite) and finally got it to recognize the device in fastboot mode. I kept rebooting and failing to get into TWRP. I found somewhere else that before doing 'fastboot reboot' that you should hold VOL UP so you can immediately boot into twrp and make it permanent, which ended up working for me. Freedom!
ItsJono said:
I'm trying to flash TWRP, i've got ADB and i've got the Universal ADB Drivers. The device is properly detected when in EUI and my Device ID is displayed correctly when I type 'adb devices', however when I reboot into fastboot and type 'fastboot devices', nothing is listed and cannot continue.
Which drivers do I use? What is it that I need to continue?
Thanks!
Edit: Nevermind, connected it into my linux machine and got it to work easier (lol winBLOWS amirite) and finally got it to recognize the device in fastboot mode. I kept rebooting and failing to get into TWRP. I found somewhere else that before doing 'fastboot reboot' that you should hold VOL UP so you can immediately boot into twrp and make it permanent, which ended up working for me. Freedom!
Click to expand...
Click to collapse
I believe you need to configure in the developers options that you don't want to have the recovery overwritten on reboot. What also seems to work is to boot into the TWRP from the command line via 'fastboot boot <recovery-file-name>'
I have the exact same problem. I have installed all drivers and adb, but as soon as i am into fastboot and my device doesnt show up in the command line. If i want to install the recovery the command line just says <waiting for device> and nothing happend.
I already enabled the "Enable AT Port" Settings (http://forum.le.com/in/index.php?threads/le-max-2-x820-qpst-not-working.14820/) but i think this is not permanent turned on on my phone, because i have to repeat this step after every reboot.
Anybody got some tips?
Edit: Also booting directly into TWRP doesnt work, 'fastboot boot <recovery-file-name>' just ends up in <waiting for device>..
If you're using Win 8 or Win 10 you should turn off the driver singing verification before installing usb drivers for device.
In your case one of the drivers was blocked from installing and the systom does not see the device after it switches in fastboot/recovery mode.
I am not allowed to post urls, so google this: How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
RovnyiK said:
If you're using Win 8 or Win 10 you should turn off the driver singing verification before installing usb drivers for device.
In your case one of the drivers was blocked from installing and the systom does not see the device after it switches in fastboot/recovery mode.
I am not allowed to post urls, so google this: How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
Click to expand...
Click to collapse
Thanks for this Hint! Didnt know this
Nevertheless, no improvement so far. I Unistalled every driver and installed them again, but the PC doesnt recognize the phone when its in fastboot mode
Kampfgans said:
Thanks for this Hint! Didnt know this
Nevertheless, no improvement so far. I Unistalled every driver and installed them again, but the PC doesnt recognize the phone when its in fastboot mode
Click to expand...
Click to collapse
There is a chance, that your computer has installed the WRONG driver for the fastboot mode, so find any related to the phone entries in Device Manager when the phone is connected in fastboot mode, and if it is not "Android Phone/Android ADB Interface" -> remove them with remove driver checkbox checked. Optionally, if nothing changes -> try to manually pick the device driver to Android ADB Interface
RovnyiK said:
There is a chance, that your computer has installed the WRONG driver for the fastboot mode, so find any related to the phone entries in Device Manager when the phone is connected in fastboot mode, and if it is not "Android Phone/Android ADB Interface" -> remove them with remove driver checkbox checked. Optionally, if nothing changes -> try to manually pick the device driver to Android ADB Interface
Click to expand...
Click to collapse
I tried it now with the fifth computer and after a few strange error messages, it "succesfully" installed TWRP.
BUT: There is no TWRP installed on my phone. I followed every tip which i found how to exit the fastboot mode (pressing Vol+ & Power / Removing USB Cable / Tried TeamSpains Automatic Installer).
What is wrong with this phone ? - I think i will oben a new thread, thanks for your help!
Kampfgans said:
I tried it now with the fifth computer and after a few strange error messages, it "succesfully" installed TWRP.
BUT: There is no TWRP installed on my phone. I followed every tip which i found how to exit the fastboot mode (pressing Vol+ & Power / Removing USB Cable / Tried TeamSpains Automatic Installer).
What is wrong with this phone ? - I think i will oben a new thread, thanks for your help!
Click to expand...
Click to collapse
Kampfgans: Klingt irgendwo zwischen lustig und richtig bedrohlich...
Lots of ROMs (including most CM variants) like to "automatically 'recover'" recoveries, that is they overwrite the recovery partition with a copy of the "original" every time you reboot.
I seem to remember that my first attempt to overwrite the stock recovery using "fastboot flash recovery <twrp-image-name>" also didn't succeed in making TWRP "stick".
Within the CM13 which I installed next (over the stock v15) there is a developer option to control that, but in this case I simply used a trick, which seems to bypass the recovery overwrite: I told the phone to boot the TWRP recovery over USB after flashing.
It went like this:
fastboot flash recovery <name-and-path-of-TWRP-recovery> //puts the TWRP image on the recovery partition
fastboot boot <name-and-path-of-TWRP-recovery> //bypasses the recovery overwrite logic of either the bootloader or whereever it hides
That booted TWRP over USB and allowed me to install CM13.
There I disabled recovery overwrite in the deveoper's options and I've never had issues with TWRP disappearing since.
Actually you should in theory be able to leave the stock recovery in place and still use TWRP by booting it over USB on the fastboot command line.
I install drivers and USB but when trying to go to fast boot I receive "waiting for device"
I'm running into issues with my Compact X. Current situation:
- Omni 8.1 rom installed, but doesn't boot. Stuck on Sony logo.
- TRWP 3.3
- Rooted
- When in fastboot mode (vol up + connect usb cable) the device manager shows: Android Device > Sony Fastboot Interface.
- Windows 10 running in "Test mode"
- adb & fastboot v1.4.3
ADB does not recognize my device when the device is in fastboot mode. When it's in recovery mode the command 'adb devices' shows me the device listed. I can then reboot in fastboot mode, but then the device isn't listed anymore. I'm not sure what happened because a couple of hours ago I installed TWRP using fastboot.
I'm trying to get this thing up and running again, but not being able to flash anything via fastboot complicates things. Any idea's what could be the culprit?
Download official Android drivers by Google and force Install them (search: Force Install Windows drivers" anywhere preferably YouTube
Some random said:
Download official Android drivers by Google and force Install them (search: Force Install Windows drivers" anywhere preferably YouTube
Click to expand...
Click to collapse
Thank you for your reply. As far as I know the official drivers were already installed. Because at first my device did show up listed when using the command 'adb devices' and I successfully flashed TWRP recovery. But to be sure I repeated the process:
- Connected my phone in fastboot mode (vol up + connect usb cable). The blue led lights up.
- Go to the device manager, right click on 'Android ADB interface' device and manually install the driver via 'Have disk'.
- The driver installs with no errors.
But still my phone is not listed and I cannot flash anything.
When the phone is in recovery mode it is listed using the 'adb devices' command. But when I'm trying to flash something I get the message <waiting for device> .
Ok, I restored my computer to a point before I started messing with my phone. After installing the official drivers my phone is still not listed (adb devices), but this time flashing did work. I managed to flash the AOSP 8.1 image. My phone is up and running again!