Database Users

[Q] flashed bad kernal and can't get to recovery or usb debugging

So i recently accidently flashed the newest franco kernal onto cm10.1 without realizing it doesn't support 4.2. My problem is now when i go to fast boot my N7 wouldn't read any of my button presses to go to recovery and when i boot it normally i get a chain of FC from NFC services, com.android, and systemUI at the lockscreen. It doesn't seem to enable USB debug at the lock screen.
any ideas?

Grona said:
So i recently accidently flashed the newest franco kernal onto cm10.1 without realizing it doesn't support 4.2. My problem is now when i go to fast boot my N7 wouldn't read any of my button presses to go to recovery and when i boot it normally i get a chain of FC from NFC services, com.android, and systemUI at the lockscreen. It doesn't seem to enable USB debug at the lock screen.
any ideas?
Click to expand...
Click to collapse
Start over using Odin...can you get it into download mode...
Sent from my SGH-T999 using xda premium

phordych05 said:
Start over using Odin...can you get it into download mode...
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I haven't tried that yet. I've never out it into download mode before. How do I reach that?
Sent from my One X using Tapatalk 2

Grona said:
I haven't tried that yet. I've never out it into download mode before. How do I reach that?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Odin won't get you anywhere since it's for Samsung devices.
Download a CM10.1 nightly for your device and extract the boot.img file from the zip.
Flash the boot.img from fastboot to restore the kernel
Code:
fastboot flash boot boot.img
reboot, and done.

comminus said:
Odin won't get you anywhere since it's for Samsung devices.
Download a CM10.1 nightly for your device and extract the boot.img file from the zip.
Flash the boot.img from fastboot to restore the kernel
Code:
fastboot flash boot boot.img
reboot, and done.
Click to expand...
Click to collapse
I don't think I can get it to fast boot, adb doesn't read my device since android debugging doesn't turn on. I'll give it a shot though when I get home.
Sent from my One X using Tapatalk 2

Grona said:
I don't think I can get it to fast boot, adb doesn't read my device since android debugging doesn't turn on. I'll give it a shot though when I get home.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
In your OP you stated:
Grona said:
...My problem is now when i go to fast boot my N7 wouldn't read any of my button presses to go to recovery...
Click to expand...
Click to collapse
So, hopefully you can still get there.
Kernel problems won't affect fastboot. Generally speaking, the only way you wont be able to get to fastboot is with bootloader corruption or hardware failure, neither of which sounds like your issue.

so i have my tablet in fastboot, and i have ADB up and running, but when i type in ADB devices it comes up blank.
any ideas?

Grona said:
so i have my tablet in fastboot, and i have ADB up and running, but when i type in ADB devices it comes up blank.
any ideas?
Click to expand...
Click to collapse
Adb doesn't work in fastboot. You need to use fastboot. Run this:
Code:
fastboot devices
Then try what I previously posted.
Sent from my Nexus 4

comminus said:
Adb doesn't work in fastboot. You need to use fastboot. Run this:
Code:
fastboot devices
Then try what I previously posted.
Sent from my Nexus 4
Click to expand...
Click to collapse
So after flashing the boot.img from the cm10.1 nightly I'm getting a garbled screen after the CM boot screen, any thoughts?
Sent from my One X using Tapatalk 2

Boot to recovery and wipe cache/dalvik. Reboot and try again. If that fails to resolve the issue, try flashing the entire cm10.1 nightly from recovery.
Sent from my Nexus 4

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

[Q] Tried Rooting Nexus 4 following the guide, but now it's not working

I followed the guide from this forum on how to root a Nexus 4, but in the process I think I've broken my phone.
I first tried flashing AOKP and it's GApps, the phone booted fine, and I was able to get to the wifi set up screen, however, I couldn't get wifi to turn on.
So I tried to flash Paranoid Android and it's GApps. But now the phone won't get past the boot screen that comes after the google logo.
I've asked around and Googled around for a solution, but I can't find anything. I've been trying to get this fixed since yesterday.
Can anyone please help me? I just want to be able to use my phone again.

GuyWithBrokenPhone said:
I followed the guide from this forum on how to root a Nexus 4, but in the process I think I've broken my phone.
I first tried flashing AOKP and it's GApps, the phone booted fine, and I was able to get to the wifi set up screen, however, I couldn't get wifi to turn on.
So I tried to flash Paranoid Android and it's GApps. But now the phone won't get past the boot screen that comes after the google logo.
I've asked around and Googled around for a solution, but I can't find anything. I've been trying to get this fixed since yesterday.
Can anyone please help me? I just want to be able to use my phone again.
Click to expand...
Click to collapse
How are you flashing? Adb or a Toolkit?
Edit:: How long did you wait? Sometimes it might take awhile, especially with PA.
Sent from my Nexus 7 (2013)

Berrydroidcafe said:
How are you flashing? Adb or a Toolkit?
Edit:: How long did you wait? Sometimes it might take awhile, especially with PA.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I flashed with ClockworkMod.
I left it on from 12AM to 6AM.

GuyWithBrokenPhone said:
I flashed with ClockworkMod.
I left it on from 12AM to 6AM.
Click to expand...
Click to collapse
It definitely shouldn't have taken that long. Can you boot into the recovery?
Sent from my Nexus 7 (2013)

Just put your phone in fastboot mode and flash factory image.

Okay now I have a new problem. I turned the phone off, booted back on and tried entering recovery mode, but now I have an image of an android with a red ! mark.
I was just about to try flashing an older version of the stock.

That's normal for stock recovery, you won't be able to sort your phone from there, stay in fastboot mode. You can use a toolkit to flash back to stock from there if you need it more noob friendly. Otherwise you can use the flash-all.bat script in the factory images.

GuyWithBrokenPhone said:
Okay now I have a new problem. I turned the phone off, booted back on and tried entering recovery mode, but now I have an image of an android with a red ! mark.
I was just about to try flashing an older version of the stock.
Click to expand...
Click to collapse
You mean the android is on it's back, press the volu+ button, press power, and that will take you into the stock recovery.

audit13 said:
You mean the android is on it's back, press the volu+ button, press power, and that will take you into the stock recovery.
Click to expand...
Click to collapse
Oh god thank you.
Okay. I'm trying to reinstall Paranoid Android now. I did the sideboot via ADB.
I couldn't seem to get the stock version of android on it though. I made sure to open the tar file and tried to move the .zip "image-occam-jdq39.zip" onto the phone, but it wouldn't accept it. So I'm trying Paranoid android again.
Edit: I got it booted. But now wifi won't work. Neither the speakers.

It didn't work because that's not how you flash a factory image. You need to be in fastboot mode and flash it from a PC using fastboot program. You used fastboot when you unlocked your bootloaders in the first place. You have stock recovery so you can't flash a custom rom, which is why your adb sideload of PA didn't work.
Like I said before you can use the flash-all.bat in the factory image. It runs the following commands which you can also use manually.
fastboot flash bootloader [path-to-bootloader.img]
fastboot flash radio [path-to-radio.img]
fastboot -w update [path-to-system-image.zip]
If that's too difficult use a nexus 4 toolkit to download and flash a factory image automatically. With your phone in fastboot mode, not recovery.
The above will fix your phone, trying to flash custom roms and system image zip in recovery mode will not.

DrFredPhD said:
It didn't work because that's not how you flash a factory image. You need to be in fastboot mode and flash it from a PC using fastboot program. You used fastboot when you unlocked your bootloaders in the first place. You have stock recovery so you can't flash a custom rom, which is why your adb sideload of PA didn't work.
Like I said before you can use the flash-all.bat in the factory image. It runs the following commands which you can also use manually.
fastboot flash bootloader [path-to-bootloader.img]
fastboot flash radio [path-to-radio.img]
fastboot -w update [path-to-system-image.zip]
If that's too difficult use a nexus 4 toolkit to download and flash a factory image automatically. With your phone in fastboot mode, not recovery.
The above will fix your phone, trying to flash custom roms and system image zip in recovery mode will not.
Click to expand...
Click to collapse
Doing so now. If I had known about this tool before, I probably would have been done with this a lot sooner.
Currently flashing stock and unrooting.

The toolkit is most certainly the way to go. No mess, perfect every time for me.
Sent from my Nexus 4 using Tapatalk

[Q] No recovery, no fastboot?

So, one of my family members was mucking around on their tablet. I was sure that I has locked down the appropriate areas, but as of right now, I think I'm looking at a hard-brick. I'm not sure what kind of fastboot capabilities I have, turning it off, and on again boots to what looks like fastboot, but I have a Google splash screen. Using the vol up/down/pwr button does boot into fastboot, but I'm not sure what I have at my disposal for flashing. Any suggestions? I've just never seen anything like this before.

If you can boot into fastboot, it isn't a hard brick. A brick doesn't turn on.
Just try fastboot flashing the stock image on it from Google.
Sent from my Nexus 5

Another alternative would be to boot into recovery, if you can.
I assume you had twrp or cwm? If so, you could reflash the rom you're using. If not, you could install twrp from fastboot and then sideload a rom of your choice.

Pirateghost said:
If you can boot into fastboot, it isn't a hard brick. A brick doesn't turn on.
Just try fastboot flashing the stock image on it from Google.
Sent from my Nexus 5
Click to expand...
Click to collapse
bsquare said:
Another alternative would be to boot into recovery, if you can.
I assume you had twrp or cwm? If so, you could reflash the rom you're using. If not, you could install twrp from fastboot and then sideload a rom of your choice.
Click to expand...
Click to collapse
ADB push wasn't accepting anything. What I ended up doing, was using the Wug toolkit to force-flash a stock image. Still not sure what the hell happened, I'm just happy it works now.
Thanks for your help!

Verfassergeist said:
ADB push wasn't accepting anything. What I ended up doing, was using the Wug toolkit to force-flash a stock image. Still not sure what the hell happened, I'm just happy it works now.
Thanks for your help!
Click to expand...
Click to collapse
Fastboot and adb are not interchangeable.
Adb doesn't work in fastboot mode
Sent from my Nexus 5

Pirateghost said:
Fastboot and adb are not interchangeable.
Adb doesn't work in fastboot mode
Sent from my Nexus 5
Click to expand...
Click to collapse
I....*facepalm*

[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