I flashed a 4.4 stock rom on my 2012 32g N7, and unfortunately, didn't notice until too late that it was also overwriting my custom recovery with the stock. Also, in the flashing process I received an error while flashing GAPPS. When I first booted the tablet, everything was fine except for no GAPPS, but I figured it would be simple to just download an APK or two and load them - well, when I tried that with several play store APKs I got "cannot open file" error.
I have now resorted to ADB to "sideload" the apks (and a custom recovery) to the tablet. At first I had trouble with the drivers, but I have followed numerous tutorials and have a solid grasp of how ADB works now. (more on that later)
I also tried WUG's toolkit, but no matter what I tried (or how many drivers I un/installed) I could never get past the "no fastboot device" error.
I used a second version of the ADB from another XDA thread, and was finally able to get my PC at the command prompt to communicate with the N7, and recognize it with "ADB devices" - the result was "<serial> sideload". This is of course when I have the tablet in the stock recovery "adb sideload" mode.
I about yelled for joy, when after six hours of rebooting and tutorials, I was able to get "adb sideload update.zip" to load, but the joy was short lived - as it consistently hangs at "sending: 'sideload' 53%"
I have tried several different zips, of varying names. and even some APK's (which hang at 78%)
Any assistance which can be offered to get this N7 functional again would be greatly appreciated!
SOLVED
I was using a company computer, for which I did not have administrator rights......
I just face palmed so hard I gave myself a well deserved concussion.
Notable said:
I was using a company computer, for which I did not have administrator rights......
I just face palmed so hard I gave myself a well deserved concussion.
Click to expand...
Click to collapse
If you're flashing the stock KitKat, you shouldn't need to flash a separate gapps package. Aside from making sure you have UAC control, make sure you update boot to 4.23, if you haven't already done so. Flashing 4.4 is easy, as long as you don't make the mistake of ever owning another An droid device and plugging it in to your pc... Dealing with missing/conflicting Windows drivers might require a vacation day and a fist-full of xanax,
Sent from my Nexus 7 using Tapatalk
Related
Background, I've done this many times, I currently have the latest CWM installd on my manta and I change ROMS and Kernels pretty frequently (I just like trying new things).
Recently I tried the preview build of Ubuntu Tablet and I can't get it to boot. Problem is I don't have any other zips on my internal storage to flash back to.
No problem I thought, I'll just side load using adb and the sideload function of CWM.
I've done it before and it worked perfectly but now I'm getting an error.
I do have my rom .zip in the correct foler (platform-tools) and I am running my command prompt from the right place.
If I do adb devices I do see my tablet serial number and it says sideload, just like it should.
But when I use the adb sideload MYROMNAME.zip I get an error that reads, *Can't read `sideload`*
If I try to use adb push MYROMNAME.zip /sdcard/ it says error:closed.
I tried completely removing my ADT bundle and redownloading the latest version and reinstalling everything including the google usb driver but I get the exact same error... I'm using win 7 32 bit.
Any ideas??? My tablet currently is bricked until I find a solution.
parakalien said:
Background, I've done this many times, I currently have the latest CWM installd on my manta and I change ROMS and Kernels pretty frequently (I just like trying new things).
Recently I tried the preview build of Ubuntu Tablet and I can't get it to boot. Problem is I don't have any other zips on my internal storage to flash back to.
No problem I thought, I'll just side load using adb and the sideload function of CWM.
I've done it before and it worked perfectly but now I'm getting an error.
I do have my rom .zip in the correct foler (platform-tools) and I am running my command prompt from the right place.
If I do adb devices I do see my tablet serial number and it says sideload, just like it should.
But when I use the adb sideload MYROMNAME.zip I get an error that reads, *Can't read `sideload`*
If I try to use adb push MYROMNAME.zip /sdcard/ it says error:closed.
I tried completely removing my ADT bundle and redownloading the latest version and reinstalling everything including the google usb driver but I get the exact same error... I'm using win 7 32 bit.
Any ideas??? My tablet currently is bricked until I find a solution.
Click to expand...
Click to collapse
Grab one of the many toolkits from the development sections and flash the factory image. Then u can just start over. I've had to do this myself, thanks to the first release of Ubuntu for our tablets.
Sent from my Nexus 10 using Tapatalk HD
newellj79 said:
Grab one of the many toolkits from the development sections and flash the factory image. Then u can just start over. I've had to do this myself, thanks to the first release of Ubuntu for our tablets.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Thank you very much!! This fixed it and was super easy.
Appreciate your help getting me out of a sticky situation!
I have two Nexus 4s. Both were running 4.2.2, rooted, with custom recovery and the Franco Kernel. On a Mac, using the command line, I flashed stock recovery and the stock kernel in preparation for taking the 4.3 OTA.
First, on the newer N4, which has far less thing loaded on it and doesn't have a SIM card...
I tried to install the OTA letting the device/OS do it via the prompt after it was downloaded. But though it tried to start the process, it failed.
So I tried to install the full OS using the command line on a Mac following efrant's instructions in http://forum.xda-developers.com/showthread.php?t=2010312. Fastboot commands have always worked there, but I've never been able to execute adb.
Code:
./fastboot-mac flash system system.img
This is something I've done successfully before. But not this time. I flashed recovery and the radio, but when I tried to flash the system, I got an error message (usb_write failed with status e00002be or something about a partition not existing). So I took the phone to a Windows machine and used Wugfresh's tool. I couldn't successfully set up the drivers, but fastboot worked. So I did the return to stock and root thing. And it worked, getting me back to 4.2.2 in an out of the box state. I ran the OTA right away and easily got to 4.3.
Then, since I was already on the Windows machine, I used Wug's tool to try and root. No success. I can't seem to install custom recovery, either temporarily or permanently. I don't get an error message, but I can't boot into it, either. I just get the dreaded lying down Android icon with the red exclamation point.
Any ideas why I couldn't install system.img on the Mac command line? And why can't I get custom recovery? And what I can do to get it right?
Now, the older N4, which is my main phone. I have a current Titanium Backup, but not a Nandroid, at least not a current one. I haven't tried, yet, to update it to 4.3. But as mentioned, I did try to go back to the stock kernel and recovery in preparation. The problem there is that I also get the lying down Android instead of stock recovery and even worse, occasionally slow and laggy performance, which I hadn't had to begin with. Otherwise, it's 4.2.2 with that radio and kernel.
Any thoughts or help on this would be much appreciated.
I'm still hoping someone can offer me some sort of insight on this.
Dev Options and USB Debugging have been enabled on these N4s. I also want to say that I'm not trying to do anything I haven't done a bunch of times before both with NRT and from the command line with N4s and N7s. But I'm stuck in ways I haven't been before and I don't understand why or what to do about it.
I dont know exactly what you mean but the android laying down is the stock recovery.
Sent from my Nexus 4 using xda app-developers app
Hmm. I thought there was another, simple, volume key driven recovery interface from prior experience with this. I'm probably confusing a non-touch version of CM Recovery. Thanks for clarifying.
I finally got drivers working on the Windows 8 machine (the Universal Naked Driver that I found here at XDA). I was able to use the command line through NRT to get custom recovery onto the first of the N4s I described. I couldn't do that on the Mac via the command line or through the NRT interface before that. It just didn't work. Once that was in place, rerooting was easy. But it was a long road to get there with obstacles I hadn't encountered on earlier rooting and updating adventures.
I haven't tried to update my daily driver, yet. I may wait until things stabilize more with 4.3 and the various ROMs. Since I may have little choice other than to start over, I might do something other than the stock ROM.
One thing I've discovered is that running a more recent version of fastboot and adb helps. I can do some things on the Mac from the command line that I couldn't do with versions a few month older. (April, 2012 vs. November, 2012).
I still can't successfully run the OTA on one of my N4s, though. Maybe I need to unroot first, though I never have before.
Everything I found on this says volume + and power, which kicks me into download mode, not fastboot.
I've gone into adb and typed adb reboot bootloader, but that just restarts the phone and turns in on like normal.
I google the how to enter fastboot mode on LG G2 and can find plenty of post about being stuck in fastboot, but nothing on how to get into fastboot in the first place.
Found a tutorial here about setting up and using fastboot and thought I was set until I got to the part about "and using fastback", where it just says:
Make sure you have android debugging turned on in your phone (not really needed for fastboot but you do need for ADB), plug it into your computer and boot into fastboot mode...
I felt like watching "Much ado about nothing" when Denzel says; "The learned constable is too cunning to be understood"
Any direction is appreciated.
Hmm, I may have written that guide... Just checked and yeah should have been more clear I'll change that up. It should have read the USB debugging was needed for adb (not for fastboot) so when you can issue
adb reboot bootloader
But after that I did mention to check device specific forum for answers on how to get into fastboot/bootloader and being I've never held an lg g2 I took a quick look around.
Unfortunately the only way that I found that people said works every time is to wipe recovery to get into bootloader mode as the recovery you guys currently have disables something due to a patch getting custom recoveries to work
So yeah, I would advice to speak with someone knowledgeable about your specific device before you just wipe recovery
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Click to expand...
Click to collapse
the current thing I've been trying to straighten out is that despite being rooted and installing TWRP, I can't install ROMS. I tried CM 11 and Hellfire so that I could put kitkat on, but gave the following:
Error executing updater binary zip.
One of the answers I found said that I had to go back to TWRP 2.3 (I'm using 2.6) and I believe that's where the whole bootloader thing came into play, because it was the way to 'downgrade' -
So then I found Philz touch 6 (as I understand it a mode of CM 11), but here he talked about fastboot and lokifying items. Here's the link:
http://forum.xda-developers.com/showthread.php?t=2554053
In the end it still comes back to the "can't load ROMs" issue. Just want a completely stripped down Kitkat that I can add the stuff I want without the bloatware.
Thanks in advance.(and the thanks button was hit on your reply)
For KitKat you should need a newer recovery with SELinux support which I believe is 2.6.x and newer for twrp, 2.3 I doubt would work if there even is one for your phone
But yes fastboot is often the best way to change recoveries but not the only way.
If there is a flashable.zip you could install new recovery from old
If your current ROM supports the flash image binary you can use a terminal emulator
You can use adb to install
Or even apps from the market
I would look for the latest recovery for your device, twrp, cwm, shouldn't matter so long as its new and then find what way works best changing for your phone.
The update-binary issue is often a sign that you need to change recoveries
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Click to expand...
Click to collapse
Thanks again. I have adb and the script for loading TWRP 2.6.xx. I unrooted and rerooted the phone, because I wasn't sure how to replace the recovery... Now I think I realize that I could just find another recovery image and place it in the same file as the loki flash and that will flash it (At least that's what I understand at present).
If that's the case, then downloading the Philz touch 6 would work... but not wanting to brick it, I'm still asking and reading.
Hello Guys.
I am having a similar issue. I have a new ROM that will not run because of a faulty lg set up wizard that always force closes and I can not get passed it and a nandroid that for some reason is corrupted. So. This fastboot seems to be a dead end it looks like a quick learning curve of ADB is the only viable answer. I have installed all SDK Manager with ADB Tools and also the required Jarva JDK and LG drivers. The phone is turned on (at the beginning of the faulty setup wizard) In CMD my device is found when typing in 'adb devices' So. I am already to push a new ROM over to the phone.
Do either of you guys know the adb command?
Help would be appreciated.
Thanks
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
I found that the best way was to load flashify, that did the trick so I could start trying out ROMs... so no on to the next step - finding a 4.4.2 stripped down stock and the LG stuff I actually like.... thanks again.
demkantor said:
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
dodge3003 said:
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
Click to expand...
Click to collapse
I HAVE SOLVED THE ISSUE! Thanks for your assistance mate but in the end I just went back to stock using this amazing thread:-
http://forum.xda-developers.com/showthread.php?t=2432476
in conjunction with this amazing video;-
http://www.youtube.com/watch?v=IixQjo_hyz8
So! I am now un rooted and back to stock. Time to start the rooting ana ROMing all over again.lol
Thanks
Glad to here!
You need a space after push
But it usually easier not to enter the location of a file while pushing so cd to the directory first like
cd C:\Users.....
Then once there adb push /nameoffile /locationonphone
But if you don't want to cd, I see you have widows, depending on version you can just right click in the folder your file is located and choose open cmd here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Need Help
As I thought I bought LG G2 D-802, but it was D-800 and I accidentally install the lollipop of D802 and now it's in bootlap.... I can only get into fastboot and whenever I try to flash .img of D-800 or D-802 it just stuck at "writing .img"
What to do to unbrick the phone and bring it back to live. I tired the adb and fastboot cmd method on windows 10 and windows 7 but no success. It's just stuck at writing .img file.
Just switched over to Tmobile from Sprint and before even signing into google i went ahead and tried to root my phone. Rooting was a success. Used Flashify to flash twrp recovery. Downloaded rooted stock D80110G rom and began debloating it (like I did with the Sprint version) and then booted to recovery, wiped twice, flashed and reboot. Well, now it will just keep rebooting back to recovery and thats it!
I still have access to download mode
still have access to custom recovery
Did not do a nand backup unfortunately
cant mount in twrp because computer no longer recognizes phone!
shows up under unknown devices as LG D801
Tried the stock recovery using LG Flash tool posted in generals but ran into the "can not update because of your device policy" or something like that. Reinstalled and tried it again many times, even switching languages and countries (the last step)
Tried using the ubuntu method posted by partager.info but even ubuntu does not recognize the device. Matter of fact nothing even happens when i plug the phone in.
Tried reinstalling drivers, tried on 2 different laptops (one windows 8.1, one windows 7, and an ubuntu usb boot) and my desktop computer (windows 8.1) and am just unable to mount using twrp because none of them recognizes it!
tried using the adb sideload but twrp just stays trying to load adb sideload forever and adb terminal cant even find the connected usb device.
Tried factory reset but that just takes me to twrp.
I've redownloaded the rooted stock rom and left everything as is. I'm assuming I just need to get it onto the phone somehow so I can flash it.
I have an otg cable but not quite sure how to work it wit twrp or if that's even an option; I've just purchased it.
I feel like I've exhausted my options. Anything else I can try?
Thanks in advance.
EDIT: Should've just used Titanium to debloat instead of trying to do a fresh install! I know I know
Figured it out! not sure how to delete this thread now
zaft1 said:
Just switched over to Tmobile from Sprint and before even signing into google i went ahead and tried to root my phone. Rooting was a success. Used Flashify to flash twrp recovery. Downloaded rooted stock D80110G rom and began debloating it (like I did with the Sprint version) and then booted to recovery, wiped twice, flashed and reboot. Well, now it will just keep rebooting back to recovery and thats it!
I still have access to download mode
still have access to custom recovery
Did not do a nand backup unfortunately
cant mount in twrp because computer no longer recognizes phone!
shows up under unknown devices as LG D801
Tried the stock recovery using LG Flash tool posted in generals but ran into the "can not update because of your device policy" or something like that. Reinstalled and tried it again many times, even switching languages and countries (the last step)
Tried using the ubuntu method posted by partager.info but even ubuntu does not recognize the device. Matter of fact nothing even happens when i plug the phone in.
Tried reinstalling drivers, tried on 2 different laptops (one windows 8.1, one windows 7, and an ubuntu usb boot) and my desktop computer (windows 8.1) and am just unable to mount using twrp because none of them recognizes it!
tried using the adb sideload but twrp just stays trying to load adb sideload forever and adb terminal cant even find the connected usb device.
Tried factory reset but that just takes me to twrp.
I've redownloaded the rooted stock rom and left everything as is. I'm assuming I just need to get it onto the phone somehow so I can flash it.
I have an otg cable but not quite sure how to work it wit twrp or if that's even an option; I've just purchased it.
I feel like I've exhausted my options. Anything else I can try?
Thanks in advance.
EDIT: Should've just used Titanium to debloat instead of trying to do a fresh install! I know I know
Figured it out! not sure how to delete this thread now
Click to expand...
Click to collapse
Hi, I have the exact same problem as you. Did you end up using otg? how did you finally end up getting a rom in your device and flashing it? I sent you a pm hope fully you see it. please respond im desperate!
mnb91 said:
Hi, I have the exact same problem as you. Did you end up using otg? how did you finally end up getting a rom in your device and flashing it? I sent you a pm hope fully you see it. please respond im desperate!
Click to expand...
Click to collapse
Hey sorry, I haven't been on the site for a couple days.
I used the flashtool to go back to stock. Had to enter download mode and work from there. The big issue I was having was a driver issue. Uninstalled every driver related to android and then reinstalled after a restart and that did the trick. For some reason android phones are giving me a lot of driver issues on windows 8.1
follow these steps here but make sure you read a chunk of the thread as the steps in the main post are not complete
http://forum.xda-developers.com/showthread.php?t=2432476
Hi hope I have come to the right place for help. My Nexus 7 16GB 2012 wifi is freezing after the google logo during the boot animation of the spinning circles and stays like this. I have done some reading and I can get into recovery mode and would like to retrieve pictures/personal data but I have not enabled USB debugging, have a stock rom kitkat, but not sure which version, and have a locked bootloader, not rooted. Is it possable to still get the data off of the device. If someone could point me in the right direction it would be much appreciated.
Thanks in advance for a response
Sent from my GT-I9100 using XDA Free mobile app
alscott51 said:
High hope I have come to the right place for help. My daughters Nexus 7 16GB 2012 wifi is freezing after the google logo when booting at the spinning circles and stays like this. I have done some reading and I can get into recovery mode and would like to retrieve pictures/personal data but I have not enabled USB debugging, have a stock rom kit kat, but not sure which version, and have a locked bootloader, and not rooted. Is it possable to still get the data off of the device. If someone could point me in the right direction it would be much appreciated.
Thanks in advance for a response
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
Use adb pull command
Ok Im not familiar with this programme but have read a bit about it. I will try and venture into this alien world of abd and see what happens.
Sent from my GT-I9100 using XDA Free mobile app
Installed Minimal ADB and Fastoot, connected the Nexus installed the ADB driver from Asus in device manager. Booted into the bootloader and when I used "Fastboot devices" I can see my devices seial number. When I try "ADB devices" nothing is seen. I have read I need USB debugging selected and the device booted to use ADB, both of which I can not do as I am stuck in a boot loop.
Sent from my GT-I9100 using XDA Free mobile app
You can't use adb in fastboot mode. It seems possible to pull files with fastboot, but it isn't fun.
Maybe you can flash something via fastboot to make it boot again? That would be the best way imho.
alscott51 said:
Installed Minimal ADB and Fastoot, connected the Nexus installed the ADB driver from Asus in device manager. Booted into the bootloader and when I used "Fastboot devices" I can see my devices seial number. When I try "ADB devices" nothing is seen. I have read I need USB debugging selected and the device booted to use ADB, both of which I can not do as I am stuck in a boot loop.
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
Go to recovery and try adb commands. In bootloader you can use only fastboot commands.
Ok I booted to the bootloader, from here selected recovery where the little Android is laying on its back. Now device manager showed nothing connected. Used the power + volume-up combo to get to the four recovery options, still nothing in device manager. Selected side load adb option and bingo welcome sound of device being connected. Windows didn't find a driver so downloaded adb driver from Asus but device manager refused to use it. Did some reading and downloaded Koush's universal driver and now device manager showed device connected and driver installed. The ADB devices command now shows the Nexus info. Now to learn the pull command. ....
Sent from my GT-I9100 using XDA Free mobile app
Done lots if reading on this and think I am beat. From what I have read the with the Nexus 7 in its current state (stock, locked bootloader, unrooted, no usb debugging) the sdcard is not reachable through the stock recovery sideload option in any way. I had a ray of hope from the above link to pull files via fastboot but I have read the thread and it seems the person says it was misleading information that they posted. I followed information in another thread and tried extracting boot, recovery and system files from a nexus factory image and flash them via fastboot but it fails stating the bootloader is locked. If I unlock the bootloader I will lose the sdcard data I want, as I will have to perform a factory reset. So as suggested I could install a CWM/TWRP recovery, but to do this via fastboot I need to unlock the bootloader......
I am thankful for people taking the time to help and for all suggestion posted but unfortunately I can not find a fix. I would be sooo grateful if someone could prove my finding wrong....
Off to do some reading about mounting the sdcard via adb shell but don't think this will work via stock recovery
Sent from my GT-I9100 using XDA Free mobile app
Install and configure any ftp/sftp/ssh server from Google play and download data wireless.
jkkk88 said:
Install and configure any ftp/sftp/ssh server from Google play and download data wireless.
Click to expand...
Click to collapse
Can't get the nexus to boot up, just bootloader and recovery accessible so don't think I'll be able to do this.
Sent from my GT-I9100 using XDA Free mobile app
Fixed it and saved all data.
Sent from my GT-I9100 using XDA Free mobile app
Sideload fix
Managed to fix this without losing anything (sdcard, docs, pictures, apps, setting etc). Took a while mostly due to lack of understanding of fastboot and ADB sideload from the recovery options.
Lots of posts advising to boot into the bootloader and use adb and fastboot. Everything I read to do with using fastboot commands via the nexus bootloader (insatalling boot/system/recovery etc) involved having an unlocked bootloader or having to unlock it as in my situation. This of course involves a factory reset of the Nexus resulting in a loss of the data that I was trying to retrieve, so i ruled this option out.
As suggested I should try the ADB pull command, but because I had not previosly enabled the USB debugging option via the setting menu everything I read said this was not an option. Read in one forum post something like "As you have not enabled USB debugging ADB is dead to you, just flash a factory image via recovery".... and lose all your data... this is not what I wanted to hear so I abandoned this option aswell.
Then I discovered sideloading. With this you can manually install an OTA update (the ones that pop up in your notification window saying something like "System update available") via the Nexus recovery option "apply update from adb". This does not invlove wiping any data , apps etc as it would just install the differences between what you are currently running eg. 4.4.2 and the updated android you want to go to eg 4.4.3. This is different to flashing a full factory image via fastboot were everything would be erased/formatted and an entirely new install would be flashed. Of course... simple when you know what the option is for and what you are doing. Of course I had had no clue what sideloading was all about.
So with my new knowledge I downloaded an OTA update from here:
http://forum.xda-developers.com/showthread.php?t=1745781&highlight=4+23
but wasnt sure what version of KitKat was running prior to the bootloop. I knew it was somewhere around 4.4.2.. so took a chance and tried KTU48L from KOT49H (4.4.3 from 4.4.2) and copied it to the Minimal ADB folder.
I booted the Nexus to the recovery mode and selected "apply update from adb". The tablet then conected to the PC (windows) as shown by Device manager. (I used Koush's universal ADB driver as windows failed to find anything of use). https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
I opened Minimal ADB downloaded from here
http://forum.xda-developers.com/showthread.php?t=2317790
and typed "adb devices" which showed the Nexus was connected.
I then typed "adb sideload nexus OTA file name.zip"
Lots of sending files messages appeared in the adb window the Nexus disconnected from the PC and showed this...
Finding update package...
Opening update package...
Verifying update package...
Insatlling update...
Verifying current system...
Removing unneeded files...
Patching system files...
Patching boot image....
Unpacking new files...
Unpacking new recovery...
Symlinks and permissions..
Patching remaining system files...
script succeeded: result was [/system]
Install fromADB complete.
All looked good so I rebooted the Nexus but I was still stuck in a bootloop at the four spinning circles. I tried clearing the cache from the recovery menu several times powering it down and leaving it to boot but after half an hour accepted failure.
So I tried downloading KTU84P from KTU84L (4.4.4 from 4.4.3) and repeated the procedure. this time not as much files seemed to be sent to the Nexus, I guess this was just a small update. Again it showed "script succeeded" but still failed to get past the spinning circles of the boot animation.
Thinking I was defeated again I was going to give up but tried downloading LRX21P from KTU84P (5.0 from 4.4.4). This time when I sideloaded a mass of files were sent to the Nexus much much more then the other two updates, obviously KitKat 4.4.4 to lollipop 5.0 was a big update. Again I got the "script succeeded" but this time I got the new Lollipop boot animation and the Nexus fully booted.
I can only guess that the big update to Lollipop removed or replaced files or did something to replace the faultly part of my install that other OTA updates did not change.
Anyway I did not find any other fix that advised sideloading an OTA update to fix a bootloop, maybe I just looked in the wrong places. I tried to write this in laymans terms for non techie people in the hope that it may help someone else in the same situation who like me knows very little about android.
Thanks to the forum for the information...
Also link here with some info about half way down page on effects of usb debugging being enabled for sideloading, and near the bottom of the page a good link to a sideload pdf guide.
https://productforums.google.com/forum/#!topic/nexus/Fhl6VVb0kio