Database Users

[Q] help, no rom in my nexus 7

I Did something really stupid, I have a Nexus 7, rooted, unlocked, went to twrp and did a back up of the stock rom, it said successful, then rebooted used the rom, everything perfect but I had tablet mod on it, decided to go back to full stock, booted to recovery, wiped everything, tried to restore and my backup is not there, and I deleted the rom as well, so now I have no rom to flash and I'm stock in recovery, anyway to push a rom into the nexus in recovery or bootloader? I tried flashing it with root toolkit 1.5.5 but it doesn't find the tablet,(all the drivers are installed), any and all help is appreciated...

Your PC won't see your N7 in Android because you haven't turned on USB debugging, and probably can't now.
You should be able to push an updated TWRP in fastboot that will see your 4.2 backup. The older version can't find its backups in 4.2,as you've discovered.
I'm not the lowest of the low, but I am the slowest of the slow.

I did have it on, I can see the tablet from control panel, but when I run the kit it says adb device not found..
Sent from my EVO using xda app-developers app

The drivers will let your PC see the N7, but you have to be in USB debugging for ADB to work. You lost it when you wiped your system, as the failure of the toolkit to see the ADB proves.
I'm not the lowest of the low, but I am the slowest of the slow.

exglynco said:
The drivers will let your PC see the N7, but you have to be in USB debugging for ADB to work. You lost it when you wiped your system, as the failure of the toolkit to see the ADB proves.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
USB Debugging doesn't need to be on for ADB through recovery to work.. Why would it? The system isn't even on it is in recovery.
Try the toolkit in fastboot.
Sent from my Full Android on Grouper using Tapatalk 2

joshnichols189 said:
USB Debugging doesn't need to be on for ADB through recovery to work.. Why would it? The system isn't even on it is in recovery.
Try the toolkit in fastboot.
Sent from my Full Android on Grouper using Tapatalk 2
Click to expand...
Click to collapse
when I'm in the bootloader it says it's in fastboot mode, but the toolkit wont find it!
I running recovery 2.3.2.1
tried adb sideload as well and it says "cannot read sideload" any ideas? getting a little crazy here..

Can anybody give me specific commands in ADB or fast boot I'm an idiot when it comes to that, on how to try to push a ROM into the device so I can flash it from recovery, or maybe a link to where I can read about it, I would really appreciate it..
Sent from my EVO using xda app-developers app

While in recovery, type in the following:
Code:
adb push <name of ROM zip> /sdcard
You need to open a command prompt window, change directories (cd) to your Android SDK - platform tools directory, and to make things easy, move the ROM zip file into that directory as well (platform-tools that is). Then type the adb push command above.
EDIT: This puts the ROM zip on the root of your sd card (/sdcard). I have a ROM folder on my sd card, so I would type:
Code:
adb push <name of ROM zip> /sdcard/ROM
This just shows that you can push a file into a folder on your sd card.

[Q] Adb not recognize in fastboot[Q]

I tried updating my nexus 7 to 4.2.1 and i thought everything went okay but now adb doesn't recognize my device in fastboot and i can't boot up my nexus 7 because everything got wiped on my sd card. I can boot into recovery but i can't mount my sd card either. It tells me there is an error. Apparently there is no OS installed. Any help is welcomed.

YoungCorruptionV2.0 said:
I tried updating my nexus 7 to 4.2.1 and i thought everything went okay but now adb doesn't recognize my device in fastboot and i can't boot up my nexus 7 because everything got wiped on my sd card. I can boot into recovery but i can't mount my sd card either. It tells me there is an error. Apparently there is no OS installed. Any help is welcomed.
Click to expand...
Click to collapse
You can boot into the bootloader, and use fastboot commands to reflash the stock Android 4.2.1 OS.

RMarkwald said:
You can boot into the bootloader, and use fastboot commands to reflash the stock Android 4.2.1 OS.
Click to expand...
Click to collapse
Fast boot commands don't work because adb can't recognized my device while in fastboot. I tried "adb devices" and no devices were listed
Sent from my EVO using Tapatalk 2

YoungCorruptionV2.0 said:
Fast boot commands don't work because adb can't recognized my device while in fastboot. I tried "adb devices" and no devices were listed
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
You can't use adb in fast boot . Reboot to the boot loader. If you type 'fastboot devices' in fast boot your phone will show
Sent from my One X using xda app-developers app

I had the same problem.
What version of adb.exe Ade you using?
The latest is dated sometime in November this year. If it's earlier than that, download the SDK from android development site and use newer version of adb.exe
That should fix the issue...
Sent from my Nexus 7 using xda premium

From bootloader use fastboot commands, from recovery use adb commands.

You can't do adb commands in fastboot mode. To do adb commands you either need to be in Android or in a recovery.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!

If you have twrp recovery installed you can boot to recovery and use adb sideload.
So just download a rom on your computer boot to recovery and sideload the rom to your device and then install it.
Not sure if this can be done with cwm though
Sent from my Nexus 7 using Tapatalk 2

[Q]Manually updated to 4.2.2... Now locked out of adb and recovery. Help.

I'm in a bit of jam. I flashed the official zip from google to update to 4.2.2 and the flash seemed to work fine. I cleared both caches after the update
However, now I seem to be completely locked out of adb and the phone doesn't prompt me for authorization (the new feature in 4.2.2) http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ . I am showing connected but offline just like this article. I have tried multiple reboots (phone/computer) as well as different USB ports. I have not tried another computer yet.
When I try to go to recovery I get a red exclamation point dead robot as I assume the flash wiped TWRP and I can't reflash TWRP without adb/root.
I would like to try to avoid a complete internal memory factory reset from the rom which I'm not sure would work anyway.
Please help.

update your adb / sdk.

bodh said:
update your adb / sdk.
Click to expand...
Click to collapse
Fortunately, I was able to reflash TWRP using fastboot w/o using adb. At the bootloader, I ran
Code:
fastboot flash recovery recovery.img
which got my recovery back up and running.
I decided to do a factory wipe and even after that adb was showing as offline and not prompting. I am very confident that your suggestion of updating the platform tools is going to fix my issue.
Thank you.

Locked on 4.2.2
My Nexus 7 is locked on 4.2.2. I tried to Unlock with Nexus Root Toolkit and I get "adb offline". I did the command "adb devices" and the device showed up, but when I tried to unlock again, it gets stuck on "checking adb status". I updated SDK and copied the new adb.exe, fastboot.exe, etc into the platform-tools folder and it still doesnt work. So basically my oem is locked on 4.2.2 and I can get adb or the toolkit to work properly.. Is there a way to downgrade back to 4.2.1 or get the Wugfresh Nexus Toolkit to actually unlock my Nexus 7 on 4.2.2??

Yea, there's a way to downgrade if you have a nandroid and know what you're doing. The toolkit will need to be updated, and it helps to know how to do it manually first.

bodh said:
Yea, there's a way to downgrade if you have a nandroid and know what you're doing. The toolkit will need to be updated, and it helps to know how to do it manually first.
Click to expand...
Click to collapse
If you know the steps or can link me to a page, that would be much appreciated. I want clear steps.

Basically the same thing just happened to me. I updated to the newest android sdk then followed the steps here http://forum.xda-developers.com/showthread.php?t=2010312
I had to restore the complete stock image first, then I sideloaded the update. I made sure all of my files were in C:\Development\sdk\platform-tools (thats the directory I used, yours may be different). Open a command prompt on the platform-tools folder and run fastboot devices, if you see a number there you are good to go. Just follow the steps in the link above to flash each file.

Why cant people wait..
lol

Bronk93 said:
Basically the same thing just happened to me. I updated to the newest android sdk then followed the steps here http://forum.xda-developers.com/showthread.php?t=2010312
I had to restore the complete stock image first, then I sideloaded the update. I made sure all of my files were in C:\Development\sdk\platform-tools (thats the directory I used, yours may be different). Open a command prompt on the platform-tools folder and run fastboot devices, if you see a number there you are good to go. Just follow the steps in the link above to flash each file.
Click to expand...
Click to collapse
I'm going to try this. Can i just type "fastboot devices" in the command prompt and it'll work?
EDIT: I found a simple fix for anyone with this problem: CREATE A BACKUP FIRST, THIS WILL ERASE EVERY THING
1. Go into the platform-tools and open the command prompt by pressing Shift + Right Click.
2. Type in "adb reboot bootloader"
3. Then type in "fastboot oem unlock"
4. WALA! It'll take a while to start up, don't worry. Set up your device and that's all.

AJ Bryant said:
I'm going to try this. So would I have to copy a fastboot.exe into the platform-tools folder? Or can i just type "fastboot devices" in the command prompt and it'll work?
Click to expand...
Click to collapse
If you downloaded the new android sdk fastboot should already be in there

I found a simple fix for this problem: CREATE A BACKUP FIRST, THIS WILL ERASE EVERY THING
1. Go into the platform-tools and open the command prompt by pressing Shift + Right Click.
2. Type in "adb reboot bootloader"
3. Then type in "fastboot oem unlock"
4. WALA! It'll take a while to start up, don't worry. Set up your device and that's all.
---------- Post added at 12:05 PM ---------- Previous post was at 11:55 AM ----------
XX-RAZOR-XX said:
Why cant people wait..
lol
Click to expand...
Click to collapse
No need to wait because I found the fix, by myself.

Can't wait to get home and try this. I got stuck last night at adb offline
Sent from my Nexus 4 using xda app-developers app

But with oem unlock, you'll still be on 4.2.2. This thread should offer good info on flashing, albeit for a galaxy nexus, but it should be mostly applicable for a nexus 7. http://forum.xda-developers.com/showthread.php?t=1626895

bodh said:
But with oem unlock, you'll still be on 4.2.2. This thread should offer good info on flashing, albeit for a galaxy nexus, but it should be mostly applicable for a nexus 7. http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
That's the point; we want to be unlocked and rooted on 4.2.2. I previously thought that in order to get an unlocked and rooted Nexus, I'd have to be on 4.2.1, unlock and root, then upgrade to 4.2.2 but that's not the case. I just unlocked and rooted via ADB since the Nexus Root Toolkit wasn't working for 4.2.2. I (and probably others) kept getting the "adb offline" error even after allowing USB debugging between the device and PC. Point is, if you're on 4.2.2 with a locked bootloader, you'll need to unlock and root using ADB commands. I don't know how many people have this issue but if someone requests it, I'll just post the steps on how to unlock and root 4.2.2 jelly bean using the ADB commands.

Re: [Q]Manually updated to 4.2.2... Now locked out of adb and recovery. Help
What if I'm on 4.2.2 completely stock but with an unlocked boot loader. I get the adb offline message when I try to root using a toolkit. How would I go about rooting?
Sent from my Nexus 4 using xda app-developers app

Place su.zip on sdcard. Reboot in fastboot mode, probably volume up+down+power. In terminal on pc, fastboot boot cwm.img for your device, install zip from sdcard.

bodh said:
Place su.zip on sdcard. Reboot in fastboot mode, probably volume up+down+power. In terminal on pc, fastboot boot cwm.img for your device, install zip from sdcard.
Click to expand...
Click to collapse
What do u mean by terminal on my PC fast boot cwm.img
Sent from my Nexus 4 using xda app-developers app

Rooting Jelly Bean 4.2.2 via ADB
DowntownJeffBrown said:
What if I'm on 4.2.2 completely stock but with an unlocked boot loader. I get the adb offline message when I try to root using a toolkit. How would I go about rooting?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
1. Download the SuperSU.zip from here: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip and place it on your device in the sdcard. I'm assuming you already enabled USB debugging.
2. Download the recovery-clockwork-touch-6.0.1.0-grouper.img from here: https://www.dropbox.com/s/v4hjsb4lse3dwtc/cwm6010touch_INSTALL.zip and place it in the platform-tools folder. Assuming you know where it's located on your PC
3. Locate the "platform-tools" folder on your PC, open it, and press Shift + Right Click & Open the command prompt there.
4. Type in the command "Adb reboot bootloader"
5. Then type in the command "fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img"
6. Now go to Recovery Mode on your Nexus and install the CWM-SuperSU-v0.98.zip from there.
7. Reboot the device once you're done and you have a rooted Nexus 7 via adb. Hope this helps.

AJ Bryant said:
1. Download the SuperSU.zip from here: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip and place it on your device in the sdcard. I'm assuming you already enabled USB debugging.
2. Download the recovery-clockwork-touch-6.0.1.0-grouper.img from here: https://www.dropbox.com/s/v4hjsb4lse3dwtc/cwm6010touch_INSTALL.zip and place it in the platform-tools folder. Assuming you know where it's located on your PC
3. Locate the "platform-tools" folder on your PC, open it, and press Shift + Right Click & Open the command prompt there.
4. Type in the command "Adb reboot bootloader"
5. Then type in the command "fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img"
6. Now go to Recovery Mode on your Nexus and install the CWM-SuperSU-v0.98.zip from there.
7. Reboot the device once you're done and you have a rooted Nexus 7 via adb. Hope this helps.
Click to expand...
Click to collapse
What about for a nexus 4. Do u know where I can get that cwm?
Sent from my Nexus 4 using xda app-developers app

DowntownJeffBrown said:
What about for a nexus 4. Do u know where I can get that cwm?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
For the Nexus 4 use this cwm image instead: http://download2.clockworkmod.com/re...0.2.3-mako.img
When youre doing the fastboot recovery, put in the name of this img file at the end. "fastboot flash recovery [name of the download file].img

Please help! Stuck on

Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.

Zehlek said:
Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.
Click to expand...
Click to collapse
i'm not on twrp at the moment but you may be able to try this
you may also try the nexus toolkit

Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?

Zehlek said:
Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?
Click to expand...
Click to collapse
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.

efan3719 said:
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.
Click to expand...
Click to collapse
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?

Zehlek said:
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?
Click to expand...
Click to collapse
On the main screen of the nexus tool kit there is a radio button option you can click for it.
Sent from my Nexus 4 using xda premium

not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.

exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
This guy sounds like he knows what he's doing.
Sent from my Nexus 4 using xda premium

exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
It says fastboot is not recognized as an internal command

In twrp, it keeps saying starting adb sideload feature

i posted this in another thread. try this...
1. First make sure that you have fastboot driver installed.
2. Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
3. Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
4. Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly. if not, check to make sure Google Nexus 4 drivers are installed correctly.
5. now open Nexus 4 toolkit and Flash Google Factory stock Rom. Once you are back to stock continue on from there...
Good Luck!

Zehlek said:
It says fastboot is not recognized as an internal command
Click to expand...
Click to collapse
my bad, it's fastboot-toolkit. But since you have a recovery with sideload already, just download a rom that's working, put it in your nexus 4 toolkit folder, rename it to flash.zip, and type in CMD
"adb-toolkit sideload flash.zip"

Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2

Zehlek said:
Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium

efan3719 said:
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you. I was beginning to panic when I saw there nothing working that would transfer a rom to my sdcard. Again thank you for all your help
Sent from my Nexus 4 using Tapatalk 2

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