Database Users

[Q] Help! Kernel Stopped Nexus 7 from booting!

My Nexus 7 is at Android 4.2.1 and after installing the Elite Kernel to make it boot faster with CLockWork Mod, its stuck at the X animation. I can still access fastboot mode and clockwork recovery mod but I still can start the device. Please help

reflash your rom in your cwm recovery.

Tried
simms22 said:
reflash your rom in your cwm recovery.
Click to expand...
Click to collapse
I just tried doing that and it said it was succesfully installed but I need to reboot. After tapping reboot system my Nexus 7 is still stuck in that X animation and wont boot.

1100G19 said:
I just tried doing that and it said it was succesfully installed but I need to reboot. After tapping reboot system my Nexus 7 is still stuck in that X animation and wont boot.
Click to expand...
Click to collapse
go into the bootloader/fastboot and try booring from there. you also might need to wipe data/factory reset then reflash your rom. also, sometimes force rebooting from a bootloop will boot it(long press the power button while in the bootloop, hold the power button for 10-20 seconds).

I had this happen to me yesterday when trying to flash a custom kernel to use with CM 10.1. The way I was able to fix it, was to pull the boot.img from the ROM zip and flash it through fastboot in the bootloader. The short and simple way is this:
Open the command prompt or terminal in the folder where fastboot is on your computer, extract the boot.img from the zip file of the ROM your using and place it in the folder with fastboot, then on your Nexus 7, hold in power + volume up + volume down to turn it off. Then hold down volume down and press power to boot into the bootloader. Once there, type in the command prompt/terminal: fastboot flash boot boot.img then reboot and you should be good to go.

Can I just remove the ROM?
simms22 said:
go into the bootloader/fastboot and try booring from there. you also might need to wipe data/factory reset then reflash your rom. also, sometimes force rebooting from a bootloop will boot it(long press the power button while in the bootloop, hold the power button for 10-20 seconds).
Click to expand...
Click to collapse
So if I back up the devices files with CWM and factory reseting it will remove the backup, so is there a way to send the backup onto my laptop?
Also is it possible to just remove the rom because I feel like my life would be easier if I unintalled it.
Thank You!

Hmmmmmm
Hanger84 said:
I had this happen to me yesterday when trying to flash a custom kernel to use with CM 10.1. The way I was able to fix it, was to pull the boot.img from the ROM zip and flash it through fastboot in the bootloader. The short and simple way is this:
Open the command prompt or terminal in the folder where fastboot is on your computer, extract the boot.img from the zip file of the ROM your using and place it in the folder with fastboot, then on your Nexus 7, hold in power + volume up + volume down to turn it off. Then hold down volume down and press power to boot into the bootloader. Once there, type in the command prompt/terminal: fastboot flash boot boot.img then reboot and you should be good to go.
Click to expand...
Click to collapse
Its a bit complicated. Also how do I get the boot.img to my computer from my nexus 7 because when I connected the Nexus 7 folder is not under "My Computer"
Thank you

Sounds like you need to go to fastboot and flash 4.13 bootloader.
Sent from my Nexus 7 using xda premium

Dont know
rebel1699 said:
Sounds like you need to go to fastboot and flash 4.13 bootloader.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
How do I flash 4.13 bootloader?

All you have to do is download the same ROM on your computer that you have on your phone. If its stock 4.2.1, then download the factory image of it and extract the boot image from the zip file and follow the same steps I outlined, though instead of using: fastboot flash boot boot.img, it would be fast boot flash boot <name of boot image>.img
If you still have trouble, feel free to message me here or on GTalk and I'll walk you through it.
Sent from my Nexus 7 using Tapatalk HD

There's an important lesson to be learned here, and you unfortunately learned it the hard way. Never, ever, blindly flash something. You need to read the OP as well as catch up on at least the last page or two of the thread. Had you done so, you would have noted that Clemsyn's Elite kernels are not compatible with 4.2.1.
I'm not saying this to be a condescending, but rather to save you the possibility of getting into situations like this again. Fortunately, Nexus devices are easily recoverable from various user errors.

Nexus 7 2012 (GSM) Booting Failed/No OS

i have access to ADB and fastboot mode.
i also try google factory image(see the attach picture for the result)

niceguy01 said:
i have access to ADB and fastboot mode.
i also try google factory image(see the attach picture for the result)
Click to expand...
Click to collapse
Yes, me too. I can't load anything except ADB & Fastboot. I used the Nexus 7 Toolkit to try to update to Kit Kat and now I have a soft bricked device. HELP!!!:crying:

Have you tried using adb shell command prompt to push the files to your device instead of a root toolkit?

cr0wnest said:
Have you tried using adb shell command prompt to push the files to your device instead of a root toolkit?
Click to expand...
Click to collapse
what file do i need to push in my device??

Effing toolkits again. When will they be banned for once and for all?
Oh that's right. They bring in ad revenue from lazy people.
Sent from my Nexus 5

niceguy01 said:
what file do i need to push in my device??
Click to expand...
Click to collapse
Check out this sticky here, it gives instructions on how to do it and what files are required. Its quite a lengthy guide, but its the safest method. http://forum.xda-developers.com/showthread.php?t=1907796

Pirateghost said:
Effing toolkits again. When will they be banned for once and for all?
Oh that's right. They bring in ad revenue from lazy people.
Sent from my Nexus 5
Click to expand...
Click to collapse
sorry im just a newbie:angel:

UPDATE: booting failed already gone by flashing cyanogen rom
the problem now is stuck in booting.see the attach picture
what is the meaning of
archive does not contain boot.sig
archive does not contain recovery.sig
archive does not contain system.sig

Got the same problem...I used RTK to flash 4.4 and ended up with a soft bricked N7.
Well initially I haven't been able to update any newer versions of CM. I was stuck on 10.2 nightly. I got a notification that there's an update so I downloaded it and tried installing. I get stuck when my N7 will go into recovery, I'll always get the droid with the red exclamation point and I have to stop the update. But I will always be able to do a system reboot and use the N7. After flashing using the RTK, all I can do is boot into the Bootloader mode. Choice at that point it Recovery, Reboot Recovert, Reboot Bootloader and Power Off. If I choose Recovery nothing happens. So the real choice is only to power off or reboot the bootloader.
I tried using fast boot but the guide I got was asking me to put the tablet in debugging mode (which I can't really do). And I get an error when doing the steps in CMD. I think I wasn't able to properly load the drivers because I am not seeing my device listed with serial number when I run >dab devices.
Kindda stuck and waiting where this thread will lead to as well so I can fix my N7.
Also, when I get the factory image (JWR66V) and run 7-zip on it, I don't see these files: bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, flash-base.sh. I only see 1 file.

As mentioned in about 5 billion threads, USB debugging has nothing to do outside of a booted OS.
Fix your drivers.
Unzip the factory image archive.
Sent from my Nexus 5

^Fixed my drivers (via SDK). PC recognised the device via fast boot devices. Ran a set of commands fast boot erase boot, cache, recovery, system, and user data. Flashed boot loader and reboot boot loader. Flashed 4.3 factory image (extracted via 7zip). Flashing/Update FAILED (I think the error was 'too mani links') and it went back to a blinking cursor.
@niceguy01 - just wait for CMD to process the entire thing. I was worried as well when I saw the system does not contain boot.sig etc error. Waited for it and started getting some scripts after. Wasn't able to complete the flash though but little steps getting there.

where should i flash radio.img?
boot,bootloader,recovery.system or userdata??see the picture
thanks

None of the above
Sent from my Nexus 5

Pirateghost said:
None of the above
Sent from my Nexus 5
Click to expand...
Click to collapse
thanks:good:

finally i got manage to fix my N7,thanks anyone who help me:good:
-----------thread close------------
i use google nexus toolkit v4 and install sdk drivers

[Q] Wugfresh stucks on: send bootloader(1280kb)

Well, i tried to install stock Bootloader, stock recovery and stockrom with wugfresh tool under "Back to Stock", and so thats the problem:
When i try to send the bootloader, it stucks and the tablet posts under the infos on the bootloader screen: FASTBOOT STATUS - DATA00140000.
And thats it. I waited 2 hour, it still stucks on sending bootloader. So i downloaded the Unified Android Toolkit, install the fastboot driver and tick the option to install a new recovery... It still stucks on sending bootloader. In Youtube Videos, i saw, that the sending finished about 0,2 s. Thats 1280kb! Why doesnt work it on my tablet. I had root, but i didnt tick the usb debugging. So when i switch on my tablet, it comes to the bootloader, and its the activated bootloader( i can switch to recovery, reboot bootloader, power off, reboot system,..) and its unlocked. If i reboot into the recovery, it also comes to the activated bootloader. Its also when i tick the reboot system. So what can i do? Is it hardware bricked? Or whats the problem? I have the bootloader version MANTAMF01 and the H/W Version 8. Can anyone helps me?
And yes, i am the Admin on my PC

The problem is the toolkit, just use fastboot
fastboot flash bootloader nameofbootloader.img
And your done
But after doing so you effectively wipe a few of your partitions so then flash recovery and ROM as well, the method on doing so slightly varies depending if your going back to stock or what something custom
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
The problem is the toolkit, just use fastboot
fastboot flash bootloader nameofbootloader.img
And your done
But after doing so you effectively wipe a few of your partitions so then flash recovery and ROM as well, the method on doing so slightly varies depending if your going back to stock or what something custom
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am having the same exact problem, and I tried doing as you said with fastboot, but I still can't receive any files. Any other suggestions? Any help would be greatly appreciated.

funkym0nkee said:
I am having the same exact problem, and I tried doing as you said with fastboot, but I still can't receive any files. Any other suggestions? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Are you trying to return to stock? Download the appropriate factory image (just Google android factory image) extract all and flash with fastboot.
If you want more detailed explanation boot to bootloader and write down all info on that screen, pet me know the os of your PC, and the explain a little more what's wrong, I'm not sure what can't receive any files means. It is often helpful to copy and paste all input/output from cmd/terminal
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Are you trying to return to stock? Download the appropriate factory image (just Google android factory image) extract all and flash with fastboot.
If you want more detailed explanation boot to bootloader and write down all info on that screen, pet me know the os of your PC, and the explain a little more what's wrong, I'm not sure what can't receive any files means. It is often helpful to copy and paste all input/output from cmd/terminal
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just resolved this issue on my own about a minute before your response lol. The problem was that I wasn't using the stock USB cord. Holy cheese and rice, I've been sitting here for the past 5 hours at wits end trying to figure out the problem. My problem was exactly like MrCreeper's, it was just stuck on "sending 'bootloader'" with no progress whatsoever on either PC or tablet. Who woulda thunk the problem was simply that I was using the incorrect USB cord -_- *sigh*
Anyway, thank you for your prompt reply. I did use a few of your tips from your other posts when I ran into other problems trying to flash stock image, so cheers for that!

[GUIDE] How to flash Factory Images from Google for the Nexus devices

Guide also available here: http://rirozizo.blogspot.com/2013/11/guide-how-to-flash-factory-images-from.html (WITH PICTURES )
Sit back, relax, don't be scared, it's fast, and easy...
So you want to upgrade your android version, or you're rooted and on a custom ROM... either way, you want an upgraded version of your android, you want it official, unrooted, but you can't wait for OTA.
Go to developers.google.com/android/nexus/images and download the appropriate image for your device, pick the android version you want.
Preparing yourself
-You'll get a tgz file, extract that
--There's a file in that extracted tgz, a zip file, when you extract it it's gonna show you all the .img files we're interested in.
-Extract that file.
--Now you'll see all the .img files... that's what we're intrested in.
Click to expand...
Click to collapse
Let's get to business!
--I really hate anything automated (exceptions apply), so let's do it the manual way.
-Boot your nexus into bootloader by plugging it in the PC, and typing this into the cmd:
adb reboot bootloader
--When you're in bootloader, leave it there.
-Type this:
fastboot devices
--Check if your device is shown. If it is, type these, and let every command finish before typing the next one:
fastboot flash system system.img
fastboot flash userdata userdata.img NOTE: This WILL wipe your DATA!
fastboot flash recovery recovery.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
Now that every command has finished, you flashed your factory image. so reboot.
when it boots, finish the setup and reboot once again and let it settle for about 5 minutes to let android relax after some hard work.

nexus 4 - stuck in boot loop
My nexus 4 is stuck in boot loop.
Will this method work on my phone - usb debugger was not on when the phone went in x loop

ashu347 said:
My nexus 4 is stuck in boot loop.
Will this method work on my phone - usb debugger was not on when the phone went in x loop
Click to expand...
Click to collapse
What did you do to get into a bootloop? A factory reset in the stock recovery will normally get you past a bootloop, but it will wipe your device
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 08:19 PM ---------- Previous post was at 08:18 PM ----------
Good guide
Sent from my Nexus 5 using XDA Free mobile app

nexus 4 - stuck in boot loop
Okay..this is how it happened...
when i checked my mobile couple of days back ..apps were crashing..."[app] stopped working" message was coming for many of the goggle apps....In past - a restart used to fix this.
I restarted my phone - but it got stuck in the bootloop (circles)
What i need next
went in bootloader menu (power and - volume)
selected factory reset
power button
blank black screen
nothing happened for a long time
then i searched on google ..downloaded SDK, nexus 4 image ..and tried to flash ..evrything went fine I till tried to flash the bootloader image and got message "failed (remote flash write failure)"
And I am stuck at this stage please advise
Now when i retstart phone goes directly into bootloader menu - may as i have erased other stuff while flashing..
Please help me ---- I do not want to loose my phone....

Yes, it will do. You can skid the userdata.img to save the data.
ashu347 said:
My nexus 4 is stuck in boot loop.
Will this method work on my phone - usb debugger was not on when the phone went in x loop
Click to expand...
Click to collapse

[Q] Boot doesn't go beyond rotating circles. Help!!

I tried to search, but in vain.
Hardware: Nexus 4
Software : Android 4.4.4
For reasons that are not clear to me the machine restarted and is stuck in those 4 rotating circles, and doesnt go beyond it. Tried multiple things such rebooting, rebooting into recovery and booting again, tried adb to see if it can see the machine in recovery mode, but to no avail.
Can someone please help? Thanks in advance.

Did you do anything, flash anything to get the boot loop? Boot loop can usually be cleared by doing a factory reset. But you'll have to reset up your phone afterwards
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Did you do anything, flash anything to get the boot loop? Boot loop can usually be cleared by doing a factory reset. But you'll have to reset up your phone afterwards
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This is a stock android and have no changes whatsoever except automatic update to 4.4.4. Only thing that is different is it is unlocked.
For last one week the phone kept complaining that it was unable to back up photos and videos. So I kept the wifi on over the night, and next morning I saw what i thought was it was trying to reboot but unable to do.
Is it possible to connect to machine while it is in recovery mode? My ADB can't discover the device either in recovery mode or while it is trying to boot. Is there a way to press some button and hard reset it?

Concoran said:
This is a stock android and have no changes whatsoever except automatic update to 4.4.4. Only thing that is different is it is unlocked.
For last one week the phone kept complaining that it was unable to back up photos and videos. So I kept the wifi on over the night, and next morning I saw what i thought was it was trying to reboot but unable to do.
Is it possible to connect to machine while it is in recovery mode? My ADB can't discover the device either in recovery mode or while it is trying to boot.
Click to expand...
Click to collapse
Can you get into the bootloader? If so you can flash a custom recovery. ADB won't work in the stock recovery.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Can you get into the bootloader? If so you can flash a custom recovery. ADB won't work in the stock recovery.
Click to expand...
Click to collapse
I can get into bootloader - if you mean by pressing down volume button and powering on - so you see a few options such as 'Start', 'Restart Bootloader' et al.'
If I can get into this, what option do I have? How I can I some custom recovery such as TWRP?
Also, I saw a youtube video where a gentleman shows how to completely reset from Recovery mode (hold power button and press up volume key), but that doesn't seem to work for me.

Concoran said:
I can get into bootloader - if you mean by pressing down volume button and powering on - so you see a few options such as 'Start', 'Restart Bootloader' et al.'
If I can get into this, what option do I have? How I can I some custom recovery such as TWRP?
Also, I saw a youtube video where a gentleman shows how to completely reset from Recovery mode (hold power button and press up volume key), but that doesn't seem to work for me.
Click to expand...
Click to collapse
Yes, that's the bootloader. Google 15 second adb install xda and install that. Then download the latest version of this http://techerrata.com/browse/twrp2/mako
Rename it recovery and put it in the same directory as fastboot.exe which will be installed with the 15 second adb install
Open a Windows command prompt in the same directory as fastboot and then with your phone connected to the pc and in the bootloader type the command in the command window
fastboot flash recovery recovery.img
This will instal twrp to your phone
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Yes, that's the bootloader. Google 15 second adb install xda and install that. Then download the latest version of this http://techerrata.com/browse/twrp2/mako
Rename it recovery and put it in the same directory as fastboot.exe which will be installed with the 15 second adb install
Open a Windows command prompt in the same directory as fastboot and then with your phone connected to the pc and in the bootloader type the command in the command window
fastboot flash recovery recovery.img
This will instal twrp to your phone
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
My Biggest concern right now is not TWRP. I need to somehow get the machine to boot. It is stuck in those 4 circling things, and I need to somehow get the OS to work (or re-install if needed).
I am able to get to recovery where I see options to 'apply aupdate from ADB,' 'wipe data' and 'wipe partition'. I have wiped off everything, now I need to somehow get OS to install, and I don't know how. I tried using 'adb sideload 'image-occam-ktu84l.zip', but it fails.That file was extracted from occam-ktu84l-factory-0d3fd624.tgz from Android site.
Update: Great, now TWRP is installed. What next? I don't want CM at this point. Just stock Os. How do I get on to the machine?

Concoran said:
My Biggest concern right now is not TWRP. I need to somehow get the machine to boot. It is stuck in those 4 circling things, and I need to somehow get the OS to work (or re-install if needed).
I am able to get to recovery where I see options to 'apply aupdate from ADB,' 'wipe data' and 'wipe partition'. I have wiped off everything, now I need to somehow get OS to install, and I don't know how. I tried using 'adb sideload 'image-occam-ktu84l.zip', but it fails.That file was extracted from occam-ktu84l-factory-0d3fd624.tgz from Android site.
Update: Great, now TWRP is installed. What next? I don't want CM at this point. Just stock Os. How do I get on to the machine?
Click to expand...
Click to collapse
Adb side load this http://forum.xda-developers.com/showthread.php?p=47476426
Edit, you could also flash the .zip you mentioned in your post by
fastboot update your file.zip
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Adb side load this http://forum.xda-developers.com/showthread.php?p=47476426
Edit, you could also flash the .zip you mentioned in your post by
fastboot update your file.zip
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Now that I have TWRP, how do I install CM? I would eventually like to return to stock, but at least for now, I need to get the phone going.
UpdateOk, the TWRP wasn't functioning well (swipe function wouldn't work), so got CWM recovery, and installed CM. CM too goes into infinite loop. Now I am completely stuck, I have no idea what else I can do.

Concoran said:
Now that I have TWRP, how do I install CM? I would eventually like to return to stock, but at least for now, I need to get the phone going.
UpdateOk, the TWRP wasn't functioning well (swipe function wouldn't work), so got CWM recovery, and installed CM. CM too goes into infinite loop. Now I am completely stuck, I have no idea what else I can do.
Click to expand...
Click to collapse
Flash the factory image in fastboot
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Flash the factory image in fastboot
Click to expand...
Click to collapse
I installed both TWRP and CWM alternatively, installed factory images using flash-all.bat, install CM11. But in both cases, 1. factory image : The system get stuck in boot mode where those 4 circles keep rotating around each other, 2. In CM11, the arrow keep rotating indefinitely.
I don't know what else I can do.
Any pointers? Thanks in advance.
I am beginning to suspect hardware malfunction. In which case, is there a log somehow I can see?
As an Aside: 1. Adb refuses to see the device in fastboot mode. Not sure if this is an expected behavior. Fastboot can.
2. Stock Android USB Drivers never work. I had to get the WugFresh Development drivers.
This is Windows 8 environment.

jd1639 said:
Flash the factory image in fastboot
Click to expand...
Click to collapse
As I said earlier, both factory image and CM go into infinite loop at bootup. I have no idea what else to do.
Question now is to see if something is wrong with hardware. I don't know how to check that. Is there a way to do some diagnostics

Concoran said:
As I said earlier, both factory image and CM go into infinite loop at bootup. I have no idea what else to do.
Question now is to see if something is wrong with hardware. I don't know how to check that. Is there a way to do some diagnostics
Click to expand...
Click to collapse
You probably have a failure of the emmc. What happens if you try to lock the bootloader and then reboot? Does it stay locked?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You probably have a failure of the emmc. What happens if you try to lock the bootloader and then reboot? Does it stay locked?
Click to expand...
Click to collapse
Yes, after locking (fastboot oem lock), bootloader the status says locked and I no longer see that unlocked icon when booting.
- At the moment I have CWM, and I see advanced options to format different folders which I have already done. But what I am not able to do is to use adb to copy the image-occam-ktu84l.zip to sdcard. Only way I have been able to install any zip is using sideload. Is that normal? I wonder if I am following right steps to begin with.
- Also, are there tools that can run and check if emmc has no bad sectors etc?
- In CWM I formatted whole log of folders, and now when CWM boots, it can't find /cache/recovery/* files. Which I take as a good sign - since old stuff is now gone. From here I don't know how to proceed. Any help - very thanful.

Concoran said:
Yes, after locking (fastboot oem lock), bootloader the status says locked and I no longer see that unlocked icon when booting.
- At the moment I have CWM, and I see advanced options to format different folders which I have already done. But what I am not able to do is to use adb to copy the image-occam-ktu84l.zip to sdcard. Only way I have been able to install any zip is using sideload. Is that normal? I wonder if I am following right steps to begin with.
- Also, are there tools that can run and check if emmc has no bad sectors etc?
- In CWM I formatted whole log of folders, and now when CWM boots, it can't find /cache/recovery/* files. Which I take as a good sign - since old stuff is now gone. From here I don't know how to proceed. Any help - very thanful.
Click to expand...
Click to collapse
If you can side load you should be able to adb push a rom. When in recovery type adb devices. Does it show that your device is connected? Do you get an error?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
If you can side load you should be able to adb push a rom. When in recovery type adb devices. Does it show that your device is connected? Do you get an error?
Click to expand...
Click to collapse
I can sideload from adb. (adb sideload <filename>.zip while CMW is waiting for abd sideload). But can't push since adb doesn't recognize the device while in fastboot - the way fastboot can.

Concoran said:
I can sideload from adb. (adb sideload <filename>.zip while CMW is waiting for abd sideload). But can't push since adb doesn't recognize the device while in fastboot - the way fastboot can.
Click to expand...
Click to collapse
You have to be in recovery to run adb commands. The bootloader is only for fastboot commands. Try pushing while you're in recovery, not the bootloader.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You have to be in recovery to run adb commands. The bootloader is only for fastboot commands. Try pushing while you're in recovery, not the bootloader.
Click to expand...
Click to collapse
Here 's what I see when I to sideload,
In CWM, I choose 'install from zip, which takes me to next page where i chose to select from sideload. I then start sideload from 'adb sideload occam-ktu84l-factory-0d3fd624.tgz' (sometime I use the extracted zip from that tgz),
Following is what I see on CMW,
'Restarting adb
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
installation aborted'

Concoran said:
Here 's what I see when I to sideload,
In CWM, I choose 'install from zip, which takes me to next page where i chose to select from sideload. I then start sideload from 'adb sideload occam-ktu84l-factory-0d3fd624.tgz' (sometime I use the extracted zip from that tgz),
Following is what I see on CMW,
'Restarting adb
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
installation aborted'
Click to expand...
Click to collapse
Ok, you can't use that file (tgz) in cwm, adb or fastboot. What you can do is extract it and then use the zip file. But, you'll have to boot into the bootloader and then use the command
fastboot update update.zip
Sent from my Nexus 5 using XDA Free mobile app