Database Users

Stuck on Google and unlock icon

Since upgrading to Windows 8 the toolkit for android and pretty much the drivers are impossible to get working.
It seems that the device has nothing on it, zip, zero. No matter how I try to recover it what ROM it tried to install it didn't work and when I try to access anything via command prompt it can not find the device.
I look at the devices on system manager and there is one listed as unknown device but I do have android phone listed as a device.
It plugs in, makes a sound knowing there is something but its unknown. Tried using the Samsung drivers, no luck there.
I need to do a complete reboot, get the original folders back on but don't know how to get it to recognise and get things going again.

jozkam said:
Since upgrading to Windows 8 the toolkit for android and pretty much the drivers are impossible to get working.
It seems that the device has nothing on it, zip, zero. No matter how I try to recover it what ROM it tried to install it didn't work and when I try to access anything via command prompt it can not find the device.
I look at the devices on system manager and there is one listed as unknown device but I do have android phone listed as a device.
It plugs in, makes a sound knowing there is something but its unknown. Tried using the Samsung drivers, no luck there.
I need to do a complete reboot, get the original folders back on but don't know how to get it to recognise and get things going again.
Click to expand...
Click to collapse
You need to disable driver signing in windows 8 to be able to install drivers for the Nexus.

Done this already, for some strange reason the device listed in Device manager now knows its a adb interface but still listed as a unknown device.
Try getting to look at the Samsung drivers but still no luck.
When you go into the device properties it states the following;-
Windows has stopped this device because it has reported problems. (Code 43)

Windows 8 doesn't seem to work very well with adb/fastboot etc...
Do you have access to another computer that has Windows 7 (or XP, Linux?)?

Thanks for you help guys so far.
I do have a Vista 32bit laptop that I can use. Going to install the Toolkit, drivers etc on there and see how far it goes.

jozkam said:
Thanks for you help guys so far.
I do have a Vista 32bit laptop that I can use. Going to install the Toolkit, drivers etc on there and see how far it goes.
Click to expand...
Click to collapse
I've read where people who are using Win8 and fastboot flashing .img files to get back to stock, it stops/locks up in varying spots...after three hours of messing with it they try another OS (Win7, Linux) and it works within minutes.
Hopefully, Vista works...and I'm sorry you have to resort to Vista!

Well I seen to be getting somewhere but still with strange issues in Device Manager.
It shows Android device with the following devices below.
- Android Composite ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (working properly)
- Google Nexus 7 BootLoader Interface (yellow exclamation mark)
Further down I have Portable Devices with MTP Device listed (yellow exclamation mark).
I have Google Nexus Toolkit installed.

jozkam said:
Well I seen to be getting somewhere but still with strange issues in Device Manager.
It shows Android device with the following devices below.
- Android Composite ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (working properly)
- Google Nexus 7 BootLoader Interface (yellow exclamation mark)
Further down I have Portable Devices with MTP Device listed (yellow exclamation mark).
I have Google Nexus Toolkit installed.
Click to expand...
Click to collapse
Is this from your Vista machine or Win8 machine now?

RMarkwald said:
Is this from your Vista machine or Win8 machine now?
Click to expand...
Click to collapse
Vista machine.

jozkam said:
Vista machine.
Click to expand...
Click to collapse
Strange. Did you install the USB drivers? Maybe download them from Asus, extract them to your Desktop, right click on your N7 in Device Manager and unistall the drivers for your device, then connect your N7 and browse to the location of the downloaded USB drivers....?

Okay following God knows how many windows updates, following restart I can see that the MTP device is now showing as working properly.
When running the toolkit (version 3.2) it shows the device number at the top under ADB mode but not under Fastboot mode.

RMarkwald said:
Strange. Did you install the USB drivers? Maybe download them from Asus, extract them to your Desktop, right click on your N7 in Device Manager and unistall the drivers for your device, then connect your N7 and browse to the location of the downloaded USB drivers....?
Click to expand...
Click to collapse
Remind me which USB drivers?

Okay, puzzling but it appears to be getting somewhere.
In device manager there is one instance of Google Nexus 7 ADB Interface under Android Device and MTP Device under Portable Devices even though it seems to reinstall the same instance of MTP device every 1 minute or so.
I am installing the Samsung drivers however, the same as before when it comes to the Toolkit. The ADB mode list of devices shows correctly, nothing underneath fastboot mode.
What would be the next stage?

I would boot into fastboot, change directory to your Android SDK - Platform Tools directory, and if you type: fastboot devices
does anything show up?
Well, I would reflash stock images completely. Hopefully you have a backup of whatever is/was on your internal sd card because doing this will erase it.
You can get the image from here (note, I am assuming you have the N7 Wifi Only): https://developers.google.com/android/nexus/images#nakasi
Then, you can revert to stock by following this post: http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/#entry764332
NOTE: Step 10 the file name will be different than shown.

Ok so I have managed to get into the ClockworkMod recovery v6.0.1.9, going with the 'install zip from sideload', used the command adb sideload nakasi-jop40c-factory-6aabb391.tar.
The screen on nexus says:
Restarting adbd...
Finding update package...
E: Cant open /tmp/update.zip
(bad)
Installation aborted.
Sorry about this I am a complete amateur when it comes to this stuff, thanks for the help so far.

UPDATE: - I used the CLEANROM 2.5 zip file and it has now gone back to its original state, YES, thank you so much.
This may have happened when I started to use Paranoid Android, they brought out a beta 5 version, which originally worked but I can't see to get it updated via the 'update recovery' step.
http://forum.xda-developers.com/showthread.php?t=1800268
Thanks once again.

RMarkwald said:
I would boot into fastboot, change directory to your Android SDK - Platform Tools directory, and if you type: fastboot devices
does anything show up?
Well, I would reflash stock images completely. Hopefully you have a backup of whatever is/was on your internal sd card because doing this will erase it.
You can get the image from here (note, I am assuming you have the N7 Wifi Only): https://developers.google.com/android/nexus/images#nakasi
Then, you can revert to stock by following this post: http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/#entry764332
NOTE: Step 10 the file name will be different than shown.
Click to expand...
Click to collapse
Steps done, back to stock which is great, thanks a lot.

Oh man just when I thought my problems were finished.
One thing I forgot to do was run the superuser zip file to give permissions on the clockworkmod recovery. Even trying to do something with Rom Manager within jellybean itself but it says I need permissions.
How can I reverse back and get the superuser.zip from working? At the moment I can not access recovery, tried using command prompts and Rom Manager but to no avail.

jozkam said:
Oh man just when I thought my problems were finished.
One thing I forgot to do was run the superuser zip file to give permissions on the clockworkmod recovery. Even trying to do something with Rom Manager within jellybean itself but it says I need permissions.
How can I reverse back and get the superuser.zip from working? At the moment I can not access recovery, tried using command prompts and Rom Manager but to no avail.
Click to expand...
Click to collapse
You can boot back into fastboot, and download the latest TWRP Recovery from here: http://teamw.in/project/twrp2/103
They even give you instructions on the command to run type in: fastboot flash recovery <name of recovery file>
Put the .img file in your Android SDK - Platform Tools folder as well.
Type in the flash recovery command, then reboot to recovery.
From there, you can flash the Superuser.zip (I assume you have it?). If not, here it is: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
You'll also want to make sure that the following files are deleted/removed:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
The reason being is that if they are there, it will reload the stock Android recovery at reboot, which will remove TWRP or CWM if you have flashed those. I would just rename them by putting a .bak on the end of the file names. But to do this, you'll need root first. You may have to: fastboot flash recovery, flash SuperSU zip, reboot, browse to those two locations to verify if those files exist/rename them, fastboot flash recovery again...reboot, and recovery may stick. When I went back to stock and fastboot flashed TWRP, I checked for those files and they weren't there, and recovery stuck just fine.
You're learning the manual way, congratulations! Not too bad is it?!

RMarkwald said:
You can boot back into fastboot, and download the latest TWRP Recovery from here: http://teamw.in/project/twrp2/103
They even give you instructions on the command to run type in: fastboot flash recovery <name of recovery file>
Put the .img file in your Android SDK - Platform Tools folder as well.
Type in the flash recovery command, then reboot to recovery.
From there, you can flash the Superuser.zip (I assume you have it?). If not, here it is: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
You'll also want to make sure that the following files are deleted/removed:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
The reason being is that if they are there, it will reload the stock Android recovery at reboot, which will remove TWRP or CWM if you have flashed those. I would just rename them by putting a .bak on the end of the file names. But to do this, you'll need root first. You may have to: fastboot flash recovery, flash SuperSU zip, reboot, browse to those two locations to verify if those files exist/rename them, fastboot flash recovery again...reboot, and recovery may stick. When I went back to stock and fastboot flashed TWRP, I checked for those files and they weren't there, and recovery stuck just fine.
You're learning the manual way, congratulations! Not too bad is it?!
Click to expand...
Click to collapse
Wouldn't have got this far without you, really appreciate your help, now its stable with 2.54 Paranoid Android.
:good:

[Q] TWRP no OS installed, can't connect to PC

Hello,
I just got the OTA message for 4.4 and tried to install it but I got a bootloop. After clearing the cache and performing a factory reset in TWRP (which got installed through Nexus Toolkit) it still didn't work. Someone told me to perform a complete format through TWRP which I did (hindsight, I know) and now TWRP says I have no OS installed, adb won't see my device (I have the drivers installed) and when I go into the bootloader (which says FASTBOOT MODE) fastboot still won't recognize the device (nothing shows up on my PC either but that can be normal).
I'm at my wit's end here, is there anyone who can help me?

You need to realize that if you want to install OTA, you need to use stock recovery. Even though it is possible to flash through TWRP, it can still run into problems. Especially when you made root modifications to your device.
You don't have to do a full wipe for everything. There is a method to flash factory firmware without wiping data (link in my signature). After that if it still don't boot due to existing data, boot into a custom recovery and do a factory reset without wiping the internal storage.
But since you have custom recovery already, just go into the Development section, find a stock KitKat rom, download it and sideload it using TWRP (which is enabled it in the Advance menu).

eksasol said:
You need to realize that if you want to install OTA, you need to use stock recovery. Even though it is possible to flash through TWRP, it can still run into problems. Especially when you made root modifications to your device.
You don't have to do a full wipe for everything. There is a method to flash factory firmware without wiping data (link in my signature).
But since you have custom recovery already, just go into the Development section, find a stock KitKat rom, download it and sideload it using TWRP (which is enabled it in the Advance menu).
Click to expand...
Click to collapse
Yes I've tried that but I don't know how to sideload it. adb doesn't see my device, fastboot doesn't either and windows doesn't recognize the device (although I have the adb naked drivers installed).

fverswijver said:
Yes I've tried that but I don't know how to sideload it. adb doesn't see my device, fastboot doesn't either and windows doesn't recognize the device (although I have the adb naked drivers installed).
Click to expand...
Click to collapse
If it is connected adb should see your device while in TWRP. Fastboot only work in fastboot mode (bootloader screen), not in recoveries. If you have the UND installed then they both should work, if not it wasn't installed correctly. If you are using Windows 8 you need to disable driver signature before you can install UND (search google for that).
You could also make a bootable Ubuntu flashdrive, and use the ADB/Fastboot for Ubuntu link in my signature to install them.

eksasol said:
If it is connected adb should see your device while in TWRP. Fastboot only work in fastboot mode (bootloader screen)
Click to expand...
Click to collapse
I tried both. ADB devices gives me an empty line and fastboot devices (when in bootloader screen) gives me nothing at all. I've tested 2 different computers (both windows 7 x64) and it still won't detect it. When in TWRP windows tries to detect my device but it says "Unknown Device" and gives the yellow triangle.

fverswijver said:
Yes I've tried that but I don't know how to sideload it. adb doesn't see my device, fastboot doesn't either and windows doesn't recognize the device (although I have the adb naked drivers installed).
Click to expand...
Click to collapse
You might have to point the drivers to your phone. If you go into device manager, see if your Nexus 4 has an error. If it does, right click it, and then update the driver. Do a manual install, and point it to the .ini file for the driver

fverswijver said:
I tried both. ADB devices gives me an empty line and fastboot devices (when in bootloader screen) gives me nothing at all. I've tested 2 different computers (both windows 7 x64) and it still won't detect it. When in TWRP windows tries to detect my device but it says "Unknown Device" and gives the yellow triangle.
Click to expand...
Click to collapse
Fix your drivers, uninstall them and select the checkbox to delete the driver files, search Google on how to disable driver signature and try reinstalling the driver again.
or
Make a bootable Ubuntu flashdrive, and use the ADB/Fastboot for Ubuntu link in my signature to install them.

eksasol said:
Make a bootable Ubuntu flashdrive, and use the ADB/Fastboot for Ubuntu link in my signature to install them.
Click to expand...
Click to collapse
I did this and still the same, adb gives an empty list and fastboot gives nothing.

fverswijver said:
I did this and still the same, adb gives an empty list and fastboot gives nothing.
Click to expand...
Click to collapse
Try using a different cable and on different computers.

eksasol said:
Try using a different cable and on different computers.
Click to expand...
Click to collapse
I've tried 3 different computers, 2 different OSes and 3 different cables. Nothing seems to work. I'm really starting to panic now.

fverswijver said:
I've tried 3 different computers, 2 different OSes and 3 different cables. Nothing seems to work. I'm really starting to panic now.
Click to expand...
Click to collapse
Just to clarify, see attachment for the correct name of the device if UND is installed correctly.
If you tried it with Ubuntu, make sure you do the 1st step from here also:
http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk

Same here
i installed the ota update normally with twrp installed everything went fine but im kind of disappointed in this update:/

eksasol said:
Just to clarify, see attachment for the correct name of the device if UND is installed correctly.
Click to expand...
Click to collapse
These are my findings:
Ubuntu:
- Bootloader (fastboot)
-- running lsusb in Ubuntu shows no device
- TWRP (adb)
-- running lsusb shows no device
Windows 7 (3 different computers)
- Bootloader (fastboot)
-- Windows gives the following popup, no device listed in Device Manager
- TWRP (adb)
-- Windows gives the same popup as on fastboot and this appears in the Device Manager:

fverswijver said:
These are my findings:
Ubuntu:
- Bootloader (fastboot)
-- running lsusb in Ubuntu shows no device
- TWRP (adb)
-- running lsusb shows no device
Windows 7 (3 different computers)
- Bootloader (fastboot)
-- Windows gives the following popup, no device listed in Device Manager
- TWRP (adb)
-- Windows gives the same popup as on fastboot and this appears in the Device Manager:
Click to expand...
Click to collapse
Is file transfering working atleast? If it is, then it's a software problem. If it isn't, then it could be a hardware problem, you can try replacing the USB charging board for the phone. Also some roms with corrupt files can cause this issues, so try a different roms if you haven't.

File transfer used to work but atm I'm unable to even connect it to a computer so I can't actually transfer any files. If I could I would flash a rom but no files = no flashing.

fverswijver said:
File transfer used to work but atm I'm unable to even connect it to a computer so I can't actually transfer any files. If I could I would flash a rom but no files = no flashing.
Click to expand...
Click to collapse
Get one of these: http://www.ebay.com/sch/i.html?_nkw=nexus+4+usb+charging+port+replacement&_sacat=0
If it don't work, then use the phone as a door stopper.

hey guys, I'm having the same problem here but with a Nexus 5 now.
Its been over a month and I've kind of gave up over the situation.
I couldn't resist to write a comment on the thread, since it appears to be the same problem as mine.
long story short, I decided to order an USB charging port to replace the one on the phone (as my last attempt).
Otherwise I will consider using the device as a door stopper.

Do not despair! Check this out: http://highonandroid.com/android-ro...r-android-in-a-bootloop-with-no-os-using-adb/
http://highonandroid.com/android-roms/how-to-copy-files-over-to-your-android-in-a-bootloop-with-no-os-using-adb/

i installed nokia xl rom into my device un fortunately i wipe the os and later i copy a rom file into my sd card and tried to flash tjat but it showing unable to open the zip. iam stuck with my company logo on the screen. twrp cannot open the zip and flash the rom. please help me in this issue.
thanks in advance

[Q] I Think i'm so f....., only CWM 5.5.0.4 and NO OS.

Only Have in the Phone the CWM R 5.5.0.4 nothing more, i try to install the drivers in win 7 64 and allways fail :/ how i can solve this, i'm so nervous OMG

Relax, we got you.
Driver installation for Windows is not straight forward. Plug in your phone, then open device manager. You will see an unrecognized device there. Right click it, select settings. Click 'Update driver', then choose the 'From this computer' option. Select the driver folder you downloaded. This should work. If it doesnt, click on the option 'Chose from list of producers', select 'Android' or simply all devices, search for OPPO and select the appropiate driver (Android ADB interface).
This should install the driver correctly. After that, get ADB and fastboot up and running: http://forum.xda-developers.com/showthread.php?t=2588979
Install a current recovery via fastboot. Search the forum for how to do this in detail. The quick version is put your phone into fastboot mode, plug into PC, start fastboot and type 'fastboot flash recovery recovery.img'.
Then push a current ROM to your phone via ADB. Again, search the forum on how to do this. Do a full wipe in the recovery and install a new ROM.
Please report back if this worked so others with the same problem can use this in the future.

theevilworm said:
Relax, we got you.
Driver installation for Windows is not straight forward. Plug in your phone, then open device manager. You will see an unrecognized device there. Right click it, select settings. Click 'Update driver', then choose the 'From this computer' option. Select the driver folder you downloaded. This should work. If it doesnt, click on the option 'Chose from list of producers', select 'Android' or simply all devices, search for OPPO and select the appropiate driver (Android ADB interface).
This should install the driver correctly. After that, get ADB and fastboot up and running: http://forum.xda-developers.com/showthread.php?t=2588979
Install a current recovery via fastboot. Search the forum for how to do this in detail. The quick version is put your phone into fastboot mode, plug into PC, start fastboot and type 'fastboot flash recovery recovery.img'.
Then push a current ROM to your phone via ADB. Again, search the forum on how to do this. Do a full wipe in the recovery and install a new ROM.
Please report back if this worked so others with the same problem can use this in the future.
Click to expand...
Click to collapse
Its working, but now when i install the twrp 2.7.0.0 the touch don't work :/

samarain said:
Its working, but now when i install the twrp 2.7.0.0 the touch don't work :/
Click to expand...
Click to collapse
Flash this TWRP edition: http://forum.xda-developers.com/showthread.php?t=2435177

Working now.. Thanks alot for the big help
Sent from my amazing HTC One..

Good to hear! Can you post what you did exactly so others reading this thread can be helped too?
How did you push a ROM to your phone?

theevilworm said:
Good to hear! Can you post what you did exactly so others reading this thread can be helped too?
How did you push a ROM to your phone?
Click to expand...
Click to collapse
The only thing i need to know was what step i need make to detect the Oppo drivers, you say " click on the option 'Chose from list of producers', select 'Android' or simply all devices, search for OPPO and select the appropiate driver (Android ADB interface)." after that problem solved because i do this kind of things many times before in other phones and its easy.
When drivers are installed successfully just need to go to recovery "power + Vol. Down" and after write in the command window ( adb push "name of the rom.zip" /sdcard/ ) and he start copying the rom to the SD card, after that just install in the recovery choosing the rom in the root of the sdcard, and thats it! Easy :good:

[Q] Another way to push root?

I have taken the OTA to KK. I have read how to fastboot the CWM recovery file to get the custom recovery to then flash the SuperSU file. I still can't get my Windows 7 Home Premium 64-bit to recognize my phone to ADB. Here is what I have done so far: (this is not an order what I have done, just steps I did in general)
1. Downloaded an ADB package file I found in another topic/thread on XDA that had everything built in to get adb to work including the 64 bit driver from google. This didn't work.
2. Downloaded the newest Motorola drivers from their website.
3. Downloaded the Universal ADB USB driver files from Koush's website. Still didn't work.
4. Found a thread on XDA that says to download the older Motorola drivers as the new ones from Motorola suck. I did that, still nothing.
I boot my phone into AP Fastboot, and connect the USB cable. It says on the phone that I'm connected. I have made sure USB debugging was checked. In Device Manager, it says MOT ADB interface when I have the phone connected. When I try "adb devices", nothing pops up. I try "adb reboot bootloader", says error: device not found. I made sure to install the ADB installers as an Administrator. Any other way to push the recovery file to the phone?
Thanks for any help!

I also searched and tried to install PDAnet for the adb drivers and that didn't work either
Sent from my XT907 using XDA Free mobile app

Anyone?
Sent from my XT907 using XDA Free mobile app

I had the same problem with the drivers after updating to 4.4.2. This is what I did to solve the problem.
1. Uninstall all Motorola drivers and Device Manager
2. Reboot PC
3. Install Motorola Device Manger (Latest Version)
4. Connect Phone and let Device Manager re-install the drivers

turns out i didn't need to use the command "adb reboot bootloader". i just did the fastboot command and it flashed instantly. Never knew why I didn't try that in the first place.../thread closed

Bricked L5.0.2 No ADB or USB

N4 16Gb : Loliop 5.02, SimpleAOSPv11, AK Kernel, CWM Philz Touch 6.46.3
I foolishly ran "Clean to install new ROM" from Philz recovery (under "Factory Reset").
I don't have a ROM on the device to flash, and can't see the device over USB or ADB.
Can anyone help recover this please? Thanks

fr0d0#2 said:
N4 16Gb : Loliop 5.02, SimpleAOSPv11, AK Kernel, CWM Philz Touch 6.46.3
I foolishly ran "Clean to install new ROM" from Philz recovery (under "Factory Reset").
I don't have a ROM on the device to flash, and can't see the device over USB or ADB.
Can anyone help recover this please? Thanks
Click to expand...
Click to collapse
First off, you're not bricked. When you boot into recovery and your device connected to your pc what do you get when you run the command adb devices from a Windows command window?
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
First off, you're not bricked. When you boot into recovery and your device connected to your pc what do you get when you run the command adb devices from a Windows command window?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks jd
I don't get anything no matter which mode I boot into

fr0d0#2 said:
Thanks jd
I don't get anything no matter which mode I boot into
Click to expand...
Click to collapse
Are you on a Windows pc? Do you have adb and fastboot setup on the pc? Had the pc recognize the device in the past?
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Are you on a Windows pc? Do you have adb and fastboot setup on the pc? Had the pc recognize the device in the past?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Windows 8 with adb installed that has previously seen the N4, yes.
I've had an HTC M8 connected recently. Just now, before wiping, I was connected via USB.

fr0d0#2 said:
Windows 8 with adb installed that has previously seen the N4, yes.
I've had an HTC M8 connected recently. Just now, before wiping, I was connected via USB.
Click to expand...
Click to collapse
Ok, so it doesn't seem like a driver or software issue. With your device booted into recovery and connected to the pc what do you see the device in device manager? It should show up as an android adb composite interface, or something like that.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Ok, so it doesn't seem like a driver or software issue. With your device booted into recovery and connected to the pc what do you see the device in device manager? It should show up as an android adb composite interface, or something like that.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I have an exclamation mark next to N4

Driver re-installed - now recognised as Android Composite ADB Device

fr0d0#2 said:
Driver re-installed - now recognised as Android Composite ADB Device
Click to expand...
Click to collapse
Good, download a rom.zip to your pc if you don't already have one. Then you're going to want to boot into recovery and push the zip to your device using adb. Once there you'll be able to flash it in philz
adb push rom.zip /sdcard/Download. I might have the / backwards. I always forget which way they go. For rom.zip use the full name of the rom. You'll want to have the rom.zip in the same folder as adb.exe and open your command window in that folder too.
Sent from my Nexus 9 using XDA Free mobile app

Thanks jd
You had the slashes the right way around - back in a bit

I'm still not getting the device listed at the command prompt, and get an error saying the same when I try the push command.
WUGs toolkit says it's there and in fastboot mode, and says it's pushed the file successfully but there's nothing there.

fr0d0#2 said:
I'm still not getting the device listed at the command prompt, and get an error saying the same when I try the push command.
WUGs toolkit says it's there and in fastboot mode, and says it's pushed the file successfully but there's nothing there.
Click to expand...
Click to collapse
I'm not that familiar with philz. Does it have an option to enable mtp when you're booted into it? If it did you can copy and paste the rom from your pc to the device. Twrp has that option under mount. I may have you boot into twrp with fastboot to use that option. How familiar are you with fastboot?
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
I'm not that familiar with philz. Does it have an option to enable mtp when you're booted into it? If it did you can copy and paste the rom from your pc to the device. Twrp has that option under mount. I may have you boot into twrp with fastboot to use that option. How familiar are you with fastboot?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Not that I can find JD. There are several mount options but USB doesn't work... because it's looking for an external source I presume.
Not very familiar.

fr0d0#2 said:
Not that I can find JD. There are several mount options but USB doesn't work... because it's looking for an external source I presume.
Not very familiar.
Click to expand...
Click to collapse
Well,a good time to learn. Download the latest twrp image from here http://techerrata.com/browse/twrp2/mako. Rename it recovery for simplicity. I'm going to have you re-install fastboot from, Google 15 second adb install xda. That'll simplify the path issues using fastboot and adb, it sets an environment variable so you don't have to worry about the path to adb or fastboot.
Then open a command window in the same folder as the twrp image is in. With your device booted into the bootloader and connected to your pc run the command
fastboot boot recovery.img.
That'll boot you into the twrp recovery. Go to mount and in the lower right hand corner you should see and option to mount mtp. Then you should see your device in Windows just like you normally would. That should make it easy to copy and paste the rom.zip to your device. Once it's copied just install it using twrp. You shouldn't have to reboot or anything.
Sent from my Nexus 9 using XDA Free mobile app

Thank you so much JD
twrp installed and mtp enabled - plain sailing from there on.
I owe you a pint :good: :highfive:

fr0d0#2 said:
Thank you so much JD
twrp installed and mtp enabled - plain sailing from there on.
I owe you a pint :good: :highfive:
Click to expand...
Click to collapse
Glad you got it working
Sent from my Nexus 9 using XDA Free mobile app

For future reference a USB otg cord and pen drive would of been very easy and cheap glad you got it fixed!!
Sent from my LG-VS985 using XDA Free mobile app