Database Users

I'm bricked .. Getting worries. (Yes I've read the forums ...)

Attempted to flash Liquid Jelly Bean, then got stuck on the animation boot screen. I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen.
I've also tried to unbrick manually however even though I have the correct files placed in my Platform Tools folder of Android SDK ... I constantly get stuck at the CMD prompt steps. Any time I type in "ADB reboot loader" or ..."fastboot flash bootloader bootloader-grouper-3.34.img" or anything similar I get the error message in CMD saying "___ Is not recognized as an internal or external command"
I'm not sure what to do. The bootloader does say that my device is locked, I just can't get passed the splash screen!

Rovon said:
Attempted to flash Liquid Jelly Bean, then got stuck on the animation boot screen. I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen.
I've also tried to unbrick manually however even though I have the correct files placed in my Platform Tools folder of Android SDK ... I constantly get stuck at the CMD prompt steps. Any time I type in "fastboot flash bootloader bootloader-grouper-3.34.img" or anything similar I get the error message in CMD saying "___ Is not recognized as an internal or external command"
I'm not sure what to do. The bootloader does say that my device is locked, I just can't get passed the splash screen!
Click to expand...
Click to collapse
Use Wugfresh's toolkit and press "return to stock"

rohan32 said:
Use Wugfresh's toolkit and press "return to stock"
Click to expand...
Click to collapse
"I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen. "

Here's an update:
I think I've made it worse ...
Nothing will boot now and it's currently locked. Any time I hit "Start" it says "Booting Failed"
My CMD now says; Error: Cannot Load "Bootloader Grouper-3.34.img"
I'm seriously lost. I've been working on this for about 6 hours now ....

Can you get into bootloader and then recovery by holding the power and volume down buttons? Was ADB actually working before all of this??

markj338 said:
Can you get into bootloader and then recovery by holding the power and volume down buttons? Was ADB actually working before all of this??
Click to expand...
Click to collapse
Nope. Nothing is allowing me to get into recovery. At first it was just stuck on the google screen now it says "boot failed"

Rovon said:
Nope. Nothing is allowing me to get into recovery. At first it was just stuck on the google screen now it says "boot failed"
Click to expand...
Click to collapse
Where does it say boot failed? On the device?

markj338 said:
Where does it say boot failed? On the device?
Click to expand...
Click to collapse
Yes. Top left hand corner.

Rovon said:
Yes. Top left hand corner.
Click to expand...
Click to collapse
I know I have asked this before but I don't know if I was clear
You can't go to bootloader, and press the volume buttons to go to recovery?

markj338 said:
I know I have asked this before but I don't know if I was clear
You can't go to bootloader, and press the volume buttons to go to recovery?
Click to expand...
Click to collapse
No I can't get into the recovery at all. When I turn on the device I don't even need to use the rocker keys to get into bootloader either. Actually my bootloader is a bit different now too. I have the 'Google' logo and at the top the regular options for Start, Recovery, Power Off, etc.
In simple terms: I can't even get to the animated splash screen anymore

Open the command prompt IN the directly WITH fastboot
Fastboot oem unlock
Then wipe / flash factory images. Fastboot -w update image whatever the image name is.
Then uninstall / delete that stupid toolkit and never use them stupid craps again.

Are you still able to communicate with the device via fastboot? If you issue the command 'fastboot devices' does it return a serial number?
Edit: I'm going to bed so if you are able to use fastboot, download the factory image pack from https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
Extract the archive. Inside are there will be an install script, manually issue the commands contained in the script in fastboot. The only thing you need to add is the location of the .img and .zip files from the archive you extracted e.g. 'fastboot flash recovery c:/Users/name/desktop/recovery.IMG'
There is no reason this will not get you up and running again.
Sent from my Nexus 7 using xda app-developers app

Alkaloid said:
Are you still able to communicate with the device via fastboot? If you issue the command 'fastboot devices' does it return a serial number?
Edit: I'm going to bed so if you are able to use fastboot, download the factory image pack from https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
Extract the archive. Inside are there will be an install script, manually issue the commands contained in the script in fastboot. The only thing you need to add is the location of the .img and .zip files from the archive you extracted e.g. 'fastboot flash recovery c:/Users/name/desktop/recovery.IMG'
There is no reason this will not get you up and running again.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response.
I've followed the instructions in the file. From previous research, I've had these files. My device does communicate with Fastboot. When I give the command for Devices it gives me my serial. Also, when I ask it to reboot-bootloader in CMD it does.
My issue is when I get to "Fastboot flash bootloader-grouper-3.34.img". CMD states "Error: Cannot load bootloader-grouper-3.34.img"
I've followed the commands previous to that. (Erase boot, cache, recovery, system, userdata)
Open the command prompt IN the directly WITH fastboot
Fastboot oem unlock
Then wipe / flash factory images. Fastboot -w update image whatever the image name is.
Then uninstall / delete that stupid toolkit and never use them stupid craps again.
Click to expand...
Click to collapse
Yes my device is unlocked again, but I still can't get into recovery mode. It just tells me "Recovery Failed" in small text in the upper left hand corner of my N7.

UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.

Rovon said:
UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.
Click to expand...
Click to collapse
For the love of God..stop using the toolkit from here on out.. learn how to use ADB and Fastboot so you can avoid these issues.
Sent from my Galaxy Nexus using Tapatalk 2

So you erased the recovery then wonder why you could not boot into recovery....
You flashed or tried to flash the bootloader. You already had the same bootloader installed and there was no need to do so to try and fix your issue.
You still don't know what you're doing and are back using the tool that lead you to this issues. A toolkit. Learn what you're doing and you wont face this type of silly issue again.

Rovon said:
UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.
Click to expand...
Click to collapse
I think you should reread this post and hit the thanks button of everyone who took the time to help you out of this mess - its good manners. Oh, and learn how to use adb & fastboot
Sent from my Nexus 7 using xda premium

Inaccessible boot loader :/
If you try to fastboot flash all you get nothing?
Sent from my Nexus 7 using xda app-developers app
---------
nvm you fixed it, good job
Don't use toolkits. Most people don't have a clue what the toolkit is actually doing so if something goes wrong they aren't in a good position

Its always nice to see threads like these where the N7 in the face of death but in the end with cutting edge medical technology it is brought back to life and healthy.

bricken N7, no OS installed

i was stuck in a bootloop after flashing a ROM, and didnt have any backups or other ROMs on the devices storage, so i was attempting to push files to it via ADB, but it wouldnt connect. i went back into the custom recovery image, and accidentally wiped the whole thing, so now i have no OS installed, and not even the seeminly 'faulty' ROM in /sdcard either. i can still get into the bootloader and the custom recovery, but cant seem to get it to connect to ADB. any ideas what i can do?

If you could boot into fastmode, then just flash stock rom.

Leonhan said:
If you could boot into fastmode, then just flash stock rom.
Click to expand...
Click to collapse
how do i boot into fastmode? all that i can access is the bootloader, and TWRP. when on the bootloader screen it sort of connects to my PC. i can go into device manager, and will see 'android bootloader interface' in there, and i have updated the drivers as per the instructions in the nexus root toolkit, but it wont seem to talk to ADB for some reason.
edit: ok, this is really odd. when i use the NRT to try pushing a zip file, if i start the it trying to push the file, then open a command line and use 'adb usb' NRT will say that it has connected to the device, and goes through its various steps, and ends up booting the device into recovery, but the actual zip it was supossed to have pushed isnt there...
it made it enter twrp, so it must be communicating in some way, but when i type 'adb devices' it doesnt show up...

bmoreyce said:
how do i boot into fastmode? all that i can access is the bootloader, and TWRP. when on the bootloader screen it sort of connects to my PC. i can go into device manager, and will see 'android bootloader interface' in there, and i have updated the drivers as per the instructions in the nexus root toolkit, but it wont seem to talk to ADB for some reason.
edit: ok, this is really odd. when i use the NRT to try pushing a zip file, if i start the it trying to push the file, then open a command line and use 'adb usb' NRT will say that it has connected to the device, and goes through its various steps, and ends up booting the device into recovery, but the actual zip it was supossed to have pushed isnt there...
it made it enter twrp, so it must be communicating in some way, but when i type 'adb devices' it doesnt show up...
Click to expand...
Click to collapse
Stop using the toolkit and read the sticky that's not too far above your post... the one titled, "[GUIDE] Flashing a Factory Image with fastboot / return to stock." Coincidentally, it happens to be exactly what you need.

najaboy said:
Stop using the toolkit and read the sticky that's not too far above your post... the one titled, "[GUIDE] Flashing a Factory Image with fastboot / return to stock." Coincidentally, it happens to be exactly what you need.
Click to expand...
Click to collapse
when i use ADB in a cmd window, it just says theres nothing connected. ive downloaded the stock image, and am currently writing it using the toolkits function, and it seems to be working so far, whereas doing it the other way, i cant seem to even get ADB to work. no idea whats going on, but it seems to be working with the toolkit
EDIT: the toolkit worked. am back on stock. thanks for your help guys.

bmoreyce said:
when i use ADB in a cmd window, it just says theres nothing connected. ive downloaded the stock image, and am currently writing it using the toolkits function, and it seems to be working so far, whereas doing it the other way, i cant seem to even get ADB to work. no idea whats going on, but it seems to be working with the toolkit
EDIT: the toolkit worked. am back on stock. thanks for your help guys.
Click to expand...
Click to collapse
You don't need ADB if you are in the bootloader- you use fastboot.

Soft brick (Already searched up and down)

So I messed up my Nexus somehow. I was trying to install MIUI coming from Carbon ROM but something went wrong as it got stuck on the miui logo. So I rebooted to TWRP and restored my backup. So then I tried to install PA and then it just got stuck on the google logo. So i restored my backup again and tried again to no avail. Then after that I couldn't restore my backup ( I keep getting FAILED as soon as the data restore starts). I can boot to Recovery but I dunno what to do. I tried sideloading but that's not working. I tried the toolkit but everytime it tries to download the factory image it says 404. The phone charges and whatnot but I don't know what to do. I only have the PA rom on my phone and reinstalling it doesn't do anything. The only weird thing is that when I try to install the PA gapps I get a FAILED message. Any help would be appreciated

varem said:
So I messed up my Nexus somehow. I was trying to install MIUI coming from Carbon ROM but something went wrong as it got stuck on the miui logo. So I rebooted to TWRP and restored my backup. So then I tried to install PA and then it just got stuck on the google logo. So i restored my backup again and tried again to no avail. Then after that I couldn't restore my backup ( I keep getting FAILED as soon as the data restore starts). I can boot to Recovery but I dunno what to do. I tried sideloading but that's not working. I tried the toolkit but everytime it tries to download the factory image it says 404. The phone charges and whatnot but I don't know what to do. I only have the PA rom on my phone and reinstalling it doesn't do anything. The only weird thing is that when I try to install the PA gapps I get a FAILED message. Any help would be appreciated
Click to expand...
Click to collapse
Have you tried to install another rom on your nexus?
you can put it on with adb push command from recovery though a pc, and then wipe everything and try to install it.
Or you can download stock 4.2.2 rom here: http://forum.xda-developers.com/showthread.php?t=2147281
Here you can find your factory image directly from google: https://developers.google.com/android/nexus/images#occamjdq39

How do I adb push?

varem said:
How do I adb push?
Click to expand...
Click to collapse
you must enter into recovery, connect your phone to your pc with usb cable and then you should be able to see your device,
try
Code:
adb devices
on CMD and it can see your phone type
Code:
adb push **your-rom-from-computer** /sdcard/
then just install it from the recovery

When you say recovery do you mean the main menu? I'm using TWRP and when I'm on the main menu my PC doesnt read the device

http://forum.xda-developers.com/showthread.php?p=34674471
My bad I should have read.....you tried a tool kit already
Sent from my Nexus 4 using xda app-developers app

mmh i don't have twrp so i don't know, do you have the option to mount sdcard to usb?

varem said:
When you say recovery do you mean the main menu? I'm using TWRP and when I'm on the main menu my PC doesnt read the device
Click to expand...
Click to collapse
Ok, wait. I need some clarification. I'm going to try to be as simple as possible, to make sure we are on the same page. When you say your PC doesn't read the device, do you mean through adb or on Windows Explorer?
If you mean through Windows Explorer, then that is not where you need to be. You must get adb working as a bridge to your device. Use this sticky guide to get it set up. I would recommend reading that guide top to bottom anyway, it's extremely informative and new-user friendly. Anyway, the info you need is in the 'Setting up ADB for our device:' section.
If you have adb installed, you need to check to see if it recognizes your device. Do this by opening up cmd and navigating to the folder that adb.exe is located. After that, use 'adb devices' to see if adb recognizes your device. If so, move to the next paragraph. If not, your drivers aren't set up properly for recovery mode. Go into Device Manager on your computer and find your device (under something like 'Other devices', or 'Android device'). If you find it, then get these drivers and install them for the device. Do this by right-clicking, and selecting 'Update Driver Software...', 'Browse my computer for driver software', and browse to that folder. I may have missed a few steps on installing the drivers, it's been a while. If so, just search on how to do it, or post back here. I'm sure I can walk through it and get a more precise guide.
Assuming you have adb installed and it recognizes your device, you need to open up cmd and navigate to the folder that adb.exe is located. Then, use the adb push command as outlined above.

Download stock images from Google's website and flash it via fastboot. If you don't know how to do it then use a toolkit like WuguFresh to do it for you.
Sent from my Nexus 4

You can also use the toolkit for pushing a ROM in your SDcard, or backup your SD in your pc.
Envoyé depuis mon Nexus 4 en utilisant Tapatalk 4 Beta

The PC reads the device as it detects it but when I type in adb devices it doesnt show up. It only ever shows up when I enter the sideload menu in TWRP

atulalvenkar said:
Download stock images from Google's website and flash it via fastboot. If you don't know how to do it then use a toolkit like WuguFresh to do it for you.
Sent from my Nexus 4
Click to expand...
Click to collapse
Thanks man. This toolkit saved my nexus!
Sent from my Nexus 4 using xda premium

[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

Help, bootlooped! Locked bootloader.

Hello!
I have the Nexus 6P and I have successfully rooted 16 phones over the past 4 years and never had a problem I couldn't fix. Today I made a mess of my new phone.
I had a perfectly working custom ROM with an unlocked boot loader with TWRP (2.8.7.2) installed. I installed some custom soft keys and got into a boot loop. I went and flashed what I thought was the stock ROM according to the website I was following, and I re locked my boot loader like a fool and was going to eventually unlock it.... turns out I was still boot looped.
I have tried:
sideloading 3 different zips, always get the message "cannot read zip" whatever the zip is
I tried changing the names, doing the full names, doing a stock rooted zipped ROM, nothing works.
I have used SkipSoft and Wugs toolkit and I can't flash ANYTHING or transfer files onto the phone unless the bootloader is unlocked.
I have installed the Google drivers multiple times, ADB devices always works, it seems to not be a driver issue because I can do everything else fine.
I have let the phone sit for 35 minutes in bootloop waiting for it to come back online so I can tick that "OEM unlock" button in the settings menu.
I have also done a dozen other things, the problem is nothing I have done or tried allows me to get any ROM or any file onto the device to flash in TWRP.
Help?

ok shot in the dark here. I had a boot loop until I flashed the flashable vendors zip
I got it in this thread:
http://forum.xda-developers.com/nexus-6p/development/rom-pure-nexus-layers-fi-wifi-calling-t3244563
Give it a whirl if you haven't already.
Found this in the Pure Nexus Project thread, so props to them for providing this.

-MotoNexus- said:
Hello!
I have the Nexus 6P and I have successfully rooted 16 phones over the past 4 years and never had a problem I couldn't fix. Today I made a mess of my new phone.
I had a perfectly working custom ROM with an unlocked boot loader with TWRP (2.8.7.2) installed. I installed some custom soft keys and got into a boot loop. I went and flashed what I thought was the stock ROM according to the website I was following, and I re locked my boot loader like a fool and was going to eventually unlock it.... turns out I was still boot looped.
I have tried:
sideloading 3 different zips, always get the message "cannot read zip" whatever the zip is
I tried changing the names, doing the full names, doing a stock rooted zipped ROM, nothing works.
I have used SkipSoft and Wugs toolkit and I can't flash ANYTHING or transfer files onto the phone unless the bootloader is unlocked.
I have installed the Google drivers multiple times, ADB devices always works, it seems to not be a driver issue because I can do everything else fine.
I have let the phone sit for 35 minutes in bootloop waiting for it to come back online so I can tick that "OEM unlock" button in the settings menu.
I have also done a dozen other things, the problem is nothing I have done or tried allows me to get any ROM or any file onto the device to flash in TWRP.
Help?
Click to expand...
Click to collapse
Thanks, the problem is I can't find a way to sideload anything or move a file over. Everything results in a myriad of errors.

tigercranestyle said:
at worst, you would have to invoke the flash-all command via adb once you extracted the couple of times that you have to. directions are on google's factory image site.
may not be the answer that you were looking for, but it always feels great having a clean device to work with. i mean as it stands, you would have to set everything back up on whatever rom anyway if you somehow got out of the problems you were having. you would spend more time doing that instead of just going the factory image route.
toolkits are fun, but learning your way around them is even more so.
Click to expand...
Click to collapse
I'm gonna check the flash all,I've never done that before. I think that would be all the images in the tgz factory image? Anything to get my phone back yeah, I just need it working again.
-UPDATE- I tried the flash all batch in the system image and I tried the flash all batch command and neither work.

Hey man - crazy story - I literally just got done messing with a toolkit and the EXACT same situation happened to me. Locked bootloader, bootloop, everything. What you need to do is do a complete wipe of everything in TWRP so you can access /data from your PC (unless it isn't messed up currently, and you can decrypt within TWRP, I couldn't...) Then, download Cataclysm (maybe something else will work, idk, but I just did it with cataclysm) and bam - it boots, head to developer options and get the box checked.
Stock images didn't work, nothing did... was scared I had a brick. The saving grace for us is that we both got TWRP installed. No more toolkits for me!

Melamunna said:
Hey man - crazy story - I literally just got done messing with a toolkit and the EXACT same situation happened to me. Locked bootloader, bootloop, everything. What you need to do is do a complete wipe of everything in TWRP so you can access /data from your PC (unless it isn't messed up currently, and you can decrypt within TWRP, I couldn't...) Then, download Cataclysm (maybe something else will work, idk, but I just did it with cataclysm) and bam - it boots, head to developer options and get the box checked.
Stock images didn't work, nothing did... was scared I had a brick. The saving grace for us is that we both got TWRP installed. No more toolkits for me!
Click to expand...
Click to collapse
I have already done the advance wipe and the format data, I just tried again and my computer will not read it as storage with MTP enabled.
Thanks though!

tigercranestyle said:
after extracting the tgz file, it should become a tar file. after extracting that tar file, it should become the six files listed below. these files should be in platform-tools to start from scratch.
bootloader-angler-angler-02.45.img
flash-all.bat
flash-all.sh
flash-base.sh
image-angler-mmb29m.zip
radio-angler-angler-02.50.img
once they are, open command line in that directory (platform-tools) and then "flash-all" should work. if it doesn't make sure you post the error that you're getting on your computer so that others can help.
Click to expand...
Click to collapse
I followed all these steps, I unzipped it and everything and put it in my fastboot folder. I still get the "unknown partition "all" " orrr flash is not recognized as an internal or external command, operable program or batch file. In an attempt with desperation I tried opening every version of the batch file, in the tgz and tar and unzipped AND in the fastboot and it all gives the radio img error.
I still do have my fastboot device connected, to my knowledge that means it can't be a driver problem right?

-MotoNexus- said:
I followed all these steps, I unzipped it and everything and put it in my fastboot folder. I still get the "unknown partition "all" " orrr flash is not recognized as an internal or external command, operable program or batch file. In an attempt with desperation I tried opening every version of the batch file, in the tgz and tar and unzipped AND in the fastboot and it all gives the radio img error.
I still do have my fastboot device connected, to my knowledge that means it can't be a driver problem right?
Click to expand...
Click to collapse
You can't flash anything in fastboot with a locked bootloader. The only way you can get your device to work is by using TWRP to flash a rom.

The flash all command doesn't work because the extracted tar file has A zipped folder inside that has to be extracted also with radio and I think recovery zipped up. You have to extract those two files to put them in the tar file and then you might be able to flash all. But as long as you can fastboot devices you should be able to flash all 6 files and have a brand new device.

tigercranestyle said:
sorry for the late reply. not always here.
1. did you unlock the bootloader again before doing all of this?
2. list the files that are in your platform-tools folder.
3. when you executed the "flash-all" command earlier, you did do it with the dash in between flash and all... right? also, you're doing it without the quotation marks, right?
sorry if they seem silly. just never really know.
Click to expand...
Click to collapse
He can't unlock the bootloader without booting into a rom. He needs to use twrp to flash a full system but I am not sure how to help with that when he can't sideload.

just an unrelated question... why did you lock the bootloader again? what was the purpose?
also, as mentioned... locked bootlader, odds arre USB debugging and OEM unlock are also not checked.... afaik, youre in trouble... hopefully someone else can sav you, im out of ideas

akellar said:
You can't flash anything in fastboot with a locked bootloader. The only way you can get your device to work is by using TWRP to flash a rom.
Click to expand...
Click to collapse
Are you telling me that I'm bricked?
I have no way of transfering files to the devices, it won't read as anything to transfer files and ADB won't sideload anything.

tigercranestyle said:
sorry for the late reply. not always here.
1. did you unlock the bootloader again before doing all of this?
2. list the files that are in your platform-tools folder.
3. when you executed the "flash-all" command earlier, you did do it with the dash in between flash and all... right? also, you're doing it without the quotation marks, right?
sorry if they seem silly. just never really know.
Click to expand...
Click to collapse
Neither am I , I just got back from a trip. I have the fastboot exe adb exe mfastboot exe the ADB api files, and the ROMs I tried to sideload along with all the images I pushed to the device.
Originally I had the bootloader unlocked, like I said I was being a fool blindly following a tutorial to get back to stock and I locked it too soon.
Yeah, I tried flash-all flash all and flash flash-all / flash flash all

dontbeweakvato said:
The flash all command doesn't work because the extracted tar file has A zipped folder inside that has to be extracted also with radio and I think recovery zipped up. You have to extract those two files to put them in the tar file and then you might be able to flash all. But as long as you can fastboot devices you should be able to flash all 6 files and have a brand new device.
Click to expand...
Click to collapse
Okay I unzipped that folder and put all the files in the fastboot folder, I still get the same error. The thing that scares me here is I can use the batch file now and it just gives me an error saying it can't flash because it's bootloader is locked.

Soulfly3 said:
just an unrelated question... why did you lock the bootloader again? what was the purpose?
also, as mentioned... locked bootlader, odds arre USB debugging and OEM unlock are also not checked.... afaik, youre in trouble... hopefully someone else can sav you, im out of ideas
Click to expand...
Click to collapse
They are default unchecked, hence the reason I can't unlock the bootloader again. I said it in my first post, I was being a fool following some guide to get back to stock and ******* up a step.

rift999 said:
He can't unlock the bootloader without booting into a rom. He needs to use twrp to flash a full system but I am not sure how to help with that when he can't sideload.
Click to expand...
Click to collapse
Is there not a way to fix the sideload? Or a way to get my computer to read it as a media devices so I can transfer files or something? It's always worked with previous phones but my computer reads the 6P differently. (even when it was working)

Stop trying to fastboot flash anything, it will not work as I've already started multiple times. The only option you have is to get something moved to storage and flash it from twrp.

akellar said:
Stop trying to fastboot flash anything, it will not work as I've already started multiple times. The only option you have is to get something moved to storage and flash it from twrp.
Click to expand...
Click to collapse
I've tried every driver from Google and Nexus 6P, I can't get it to read the MTP for a file transfer, what would you suggest I do? it doesn't show up as my old phones used to in the computers drives.
I have found 0 success with getting a file on through file transfer or ADB push file.

-MotoNexus- said:
I've tried every driver from Google and Nexus 6P, I can't get it to read the MTP for a file transfer, what would you suggest I do? it doesn't show up as my old phones used to in the computers drives.
I have found 0 success with getting a file on through file transfer or ADB push file.
Click to expand...
Click to collapse
Can't help too much personally, but you might give this a shot:
http://forum.xda-developers.com/showpost.php?p=64317181&postcount=20
Sent from my Nexus 6P using XDA Free mobile app

So I just got it............!!!!! I have spent a total of 16 hours with videos, forums and trial and error. When I was going back the 5th around time messing with drivers I turned my ADB driver into a USB composite because I had no idea I could and instantly I was able to file transfer!!!! Problem solved, I have my ROM on now.
Thank you all for your help! I am so sorry I derped at this, I have been doing this a long time and just got sloppy.