Database Develop

[Q] No OS Nexus 6 on 5.1 update

I updated my phone to Nexus to 5.1 last night and it got stuck in the boot animation but I figured it would be done when I woke up. Much to my dismay that was not the case so I tried to factory reset and now I get this message that says "No OS found." Tried to plug it up to the computer but it won't connect. I think it may have something to do with the OEM Lock but I cant fix that without the phone turning on. Please help!

How exactly did you upgrade your phone?
Sent from my Benzo'd Google N6 on VZ

lostnthought said:
I updated my phone to Nexus to 5.1 last night and it got stuck in the boot animation but I figured it would be done when I woke up. Much to my dismay that was not the case so I tried to factory reset and now I get this message that says "No OS found." Tried to plug it up to the computer but it won't connect. I think it may have something to do with the OEM Lock but I cant fix that without the phone turning on. Please help!
Click to expand...
Click to collapse
Please provide more info. Stock or custom recovery?

Evolution_Freak said:
Please provide more info. Stock or custom recovery?
Click to expand...
Click to collapse
Custom Recovery.. TWRP v2.8.2

lostnthought said:
Custom Recovery.. TWRP v2.8.2
Click to expand...
Click to collapse
From bootloader, enter the following fastboot commands:
fastboot format cache
fastboot format userdata
This should allow you to get back into TWRP and flash a ROM.

DebianDog said:
How exactly did you upgrade your phone?
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
This may sound silly but I'm not 100% sure. A system notification had been on my screen for over two weeks saying that I had a system update to 5.1 and I finally decided to download and install said update and then it sent me to recovery mode. I don't know why I did but I hit fix permissions.. Just fiddling trying to figure everything out and this is where we are.

Evolution_Freak said:
From bootloader, enter the following fastboot commands:
fastboot format cache
fastboot format userdata
This should allow you to get back into TWRP and flash a ROM.
Click to expand...
Click to collapse
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock

lostnthought said:
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
Click to expand...
Click to collapse
I'm not asking you to boot to recovery. Boot to bootloader.

lostnthought said:
I can get into recovery mode but there isn't a ROM that I can find.. It's gone. And like I said it won't connect to the computer via USB port. (Tried several ports,as well as, different cords) Can't enable OEM lock
Click to expand...
Click to collapse
move a rom via a computer to your phone. either connect the recovery to your computer and move it, or connect to a computer and adb push it to your phone.

Sorry, I guess I misread your post. I thought you said can't get to recovery. From TWRP you should be able to enable MTP transfer. Then your PC should see it and you can transfer files as @simms22 suggested.

lostnthought said:
"No OS found."
Click to expand...
Click to collapse
From TWRP, perhaps you wiped the System partition? Heh, I did that just last night... woops... "round 2"!
As a side note, if you're trying to use adb/fastboot from Windows... I had nothing but problems myself, even with the proper drivers. At worst, I had to open the Device Manager, find the phone, and force-install ("update") the driver to Android->Composite USB Device before it would be recognized. Absurd, but pains of working from Windows. (Conversely, I've had pain-free experiences from OSX and Ubuntu.)

vormund said:
From TWRP, perhaps you wiped the System partition? Heh, I did that just last night... woops... "round 2"!
As a side note, if you're trying to use adb/fastboot from Windows... I had nothing but problems myself, even with the proper drivers. At worst, I had to open the Device Manager, find the phone, and force-install ("update") the driver to Android->Composite USB Device before it would be recognized. Absurd, but pains of working from Windows. (Conversely, I've had pain-free experiences from OSX and Ubuntu.)
Click to expand...
Click to collapse
you dont need adb to move anything to your phone when using twrp. just connect to twrp using the mtp option.

Lost OS after mistaken wipe/format now I am stuck on the Google logo

Long story short I just picked up my Nexus 6 and was trying a few ROMs. Having come from a OnePlus that was stolen I wanted a similar feel. I tried a few, Bliss, Cyanogen and then finally decided after some more research that Pure Nexus was going to be my choice. I have using the Nexus Root Tool kit since I have little knowledge of adb other than what I read if needed. Pure Nexus loaded with the pure-nexus gapps that were suggested seemed to not load properly, I was either getting stuck booting up, a bootloop or when i tried loading it without the gapps it just booted to a blank screen. So I read a littel more and was under the impression I need a clean slate. I think I cleaned it too good. After wiping system, cache and dalvik cache I may have formatted by mistake.
So here I sit with a new phone that with not work. I feel there has to be an easy answer. I tried pushing the ROM to the sdcard with adb push using THIS METHOD HERE but I keep getting 'device closed'.
I feel if I can just get the file on the device I can flash it. I have also tried the 'Flash Stock Unroot' in Nexus tool kit.
HELP!

tjlmbklr said:
Long story short I just picked up my Nexus 6 and was trying a few ROMs. Having come from a OnePlus that was stolen I wanted a similar feel. I tried a few, Bliss, Cyanogen and then finally decided after some more research that Pure Nexus was going to be my choice. I have using the Nexus Root Tool kit since I have little knowledge of adb other than what I read if needed. Pure Nexus loaded with the pure-nexus gapps that were suggested seemed to not load properly, I was either getting stuck booting up, a bootloop or when i tried loading it without the gapps it just booted to a blank screen. So I read a littel more and was under the impression I need a clean slate. I think I cleaned it too good. After wiping system, cache and dalvik cache I may have formatted by mistake.
So here I sit with a new phone that with not work. I feel there has to be an easy answer. I tried pushing the ROM to the sdcard with adb push using THIS METHOD HERE but I keep getting 'device closed'.
I feel if I can just get the file on the device I can flash it. I have also tried the 'Flash Stock Unroot' in Nexus tool kit.
HELP!
Click to expand...
Click to collapse
I'm assuming you have twrp installed? If you do, you can just plug your device in to your pc and you should be able copy files to the phones storage, and then flash them. Or you can goto Advanced, ADB Sideload and "adb sideload purenexus.zip"

you dont need adb to push anything to your phone. you can transfer any rom, gapps, and supersu just using twrp recovery.

obtained said:
I'm assuming you have twrp installed? If you do, you can just plug your device in to your pc and you should be able copy files to the phones storage, and then flash them. Or you can goto Advanced, ADB Sideload and "adb sideload purenexus.zip"
Click to expand...
Click to collapse
I do have TWRP installed but I do not see my phone in my Windows files system.
I tried the sideload and this is where I am met with the device close message. I do see my device when I do a 'adb devices'
simms22 said:
you dont need adb to push anything to your phone. you can transfer any rom, gapps, and supersu just using twrp recovery.
Click to expand...
Click to collapse
Assuming you mean what obtained just suggested, how do I do this if I cannot see my phone in my PC's file system?

tjlmbklr said:
I do have TWRP installed but I do not see my phone in my Windows files system.
I tried the sideload and this is where I am met with the device close message. I do see my device when I do a 'adb devices'
Click to expand...
Click to collapse
When you do "adb devices", does it show recovery or sideload next to the serial?

Sideload. This is what I am not sure how to resolve.
Sorry, I should have mentioned that.

tjlmbklr said:
Sideload. This is what I am not sure how to resolve.
Sorry, I should have mentioned that.
Click to expand...
Click to collapse
The only time I know of sideload showing "error: closed" is when recovery isn't in "sideload mode". Using Windows? Do you see any errors in Device Manager?
Edit: Maybe when you put twrp in "sideload mode", you're waiting too long to send the sideload command before it times out? Maybe get the command ready before you enable sideload in twrp?

obtained said:
The only time I know of sideload showing "error: closed" is when recovery isn't in "sideload mode". Using Windows? Do you see any errors in Device Manager?
Edit: Maybe when you put twrp in "sideload mode", you're waiting too long to send the sideload command before it times out? Maybe get the command ready before you enable sideload in twrp?
Click to expand...
Click to collapse
No errors

tjlmbklr said:
No errors
Click to expand...
Click to collapse
In twrp, do "adb usb" and see if your storage shows up on the pc, if it doesn't, enable sideload and do "adb usb" and the "adb sideload purenexus.zip" again

Quick update. I was using an out dated version of adb. I updated, side loaded the ROM and it booting up now.
Fingers crossed!

tjlmbklr said:
Quick update. I was using an out dated version of ad. I updated, side loaded the ROM and it booting up now.
Fingers crossed!
Click to expand...
Click to collapse
Of course it would be something so simple!

obtained said:
Of course it would be something so simple!
Click to expand...
Click to collapse
I am just happy it was. I recently Hard Brick a Galaxy Tab3 when I failed at loading a custom ROM on it. If I would have ruined this device I would never hear the end of it from the wife.

Inexperienced and messed up big time

I heard of cyanogen mod and was eager to have a play around and try to install it.
I followed a guide on youtube to root my device and things went wrong.
It was running on the latest version of marshmallow, i did all the steps on the video and at the end it said "your device is corrupt it can't be trusted" and then the phone turns off.
I can only get as far as team win recovery project and i've messed up because i've stupidly formatted the data so there are no files or operating system at all on my device.
I'm not being lazy, i've searched these forums and have been trying to sort it out for the last 5 hours.
I'm using a mac too, most of guides are for windows.
I'm really stuck and I'm not clued up with all the terminology used on here.
Can anyone help me in layman's terms? I'm really desperate as now I'm stuck without a phone.
Please don't take the mickey out of me, I know I shouldn't have messed around with these things if I'm not fully aware what I'm doing. I expected it to be straight forward like jailbreaking an iPad.

mikeos89 said:
I heard of cyanogen mod and was eager to have a play around and try to install it.
I followed a guide on youtube to root my device and things went wrong.
It was running on the latest version of marshmallow, i did all the steps on the video and at the end it said "your device is corrupt it can't be trusted" and then the phone turns off.
I can only get as far as team win recovery project and i've messed up because i've stupidly formatted the data so there are no files or operating system at all on my device.
I'm not being lazy, i've searched these forums and have been trying to sort it out for the last 5 hours.
I'm using a mac too, most of guides are for windows.
I'm really stuck and I'm not clued up with all the terminology used on here.
Can anyone help me in layman's terms? I'm really desperate as now I'm stuck without a phone.
Please don't take the mickey out of me, I know I shouldn't have messed around with these things if I'm not fully aware what I'm doing. I expected it to be straight forward like jailbreaking an iPad.
Click to expand...
Click to collapse
I don't know how you went about the processes but based on what you are saying, I'm guessing you used a "toolkit". You situation isn't that big of a deal. If you can get into fastboot, I suggest you get into fastboot and use adb commands to "push" commands to push a custom ROM into your /sdcard then flash it via TWRP.
adb push <source-path> <target-path>
adb devices
adb push filename /sdcard/
Once you boot back into TWRP, flash and you are good to go.

mikeprius said:
I don't know how you went about the processes but based on what you are saying, I'm guessing you used a "toolkit". You situation isn't that big of a deal. If you can get into fastboot, I suggest you get into fastboot and use adb commands to "push" commands to push a custom ROM into your /sdcard then flash it via TWRP.
adb push <source-path> <target-path>
adb devices
adb push filename /sdcard/
Once you boot back into TWRP, flash and you are good to go.
Click to expand...
Click to collapse
I appreciate the help, but imagine you are talking to an idiot who doesn't have the foggiest, I'm clueless with command prompts unless it's something I'm copying directly.
I want to learn this stuff, but I really need all the info stripped down to the bare basics at the moment.
I'm panicking a bit too which isn't helping.

Can't you just drag and drop a ROM and gapps while in twrp... Ive.done it before...good luck

Not likely as the phone plugged into the computer may not read it as a "USB" drive. I have windows and I have no idea what the command prompts are for Mac. Also if your understanding is virtually nothing, you need at least understand the basics of fastboot and custom recovery in order to fix your situation.
The good news is that your phone isn't messed up. The bad news is you need to roll up your sleeves and learn the basics of how the commands work so you can reboot the phone back. Everyone here can describe to you what to do but since you don't know the fundamentals it won't mean anything until you do. Sorry.
Btw, jailbreaking isn't the Apple version of "root". They are 2 completely different things.
What I would do is fastboot erase TWRP and re-flash it as it sounds like you are having problems, then adb pull a custom ROM into your internal storage. Reboot into TWRP and flash it. That's what you need to do.

mikeos89 said:
I appreciate the help, but imagine you are talking to an idiot who doesn't have the foggiest, I'm clueless with command prompts unless it's something I'm copying directly.
I want to learn this stuff, but I really need all the info stripped down to the bare basics at the moment.
I'm panicking a bit too which isn't helping.
Click to expand...
Click to collapse
I don't know anything about flashing a phone from a Mac but if you can boot your phone into bootloader mode and get fastboot to work on the Mac I would follow the steps under Step 5, Method 2 at http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I use that method to upgrade my phone every time a new ROM comes out and it works great.
Note:
1. You this will get you back to stock, you'll still have to flash your custom ROM after you get your phone working.
2. The .img files can be downloaded from https://developers.google.com/android/nexus/images#shamu.

Provided you have custom recovery such as TWRP. Get a USB otg card reader or microusb stick, download a Rom and transfer it onto the OTG, go to twrp, navigate to the USB OTG memory and flash the Rom. Simple.
Sent from my Nexus 6 using Tapatalk

bushako said:
Provided you have custom recovery such as TWRP. Get a USB otg card reader or microusb stick, download a Rom and transfer it onto the OTG, go to twrp, navigate to the USB OTG memory and flash the Rom. Simple.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This, easiest way for you probably. I've done it this way before too. I suppose you could ask someone to TeamView your pc, but you should probably try the usb otg method first.

Can someone PLEASE help me boot my phone into FASTBOOT mode? ( T mobile h811) on CM13

When I first purchased this phone I was able to boot to the default recovery that came with the phone ( which clearly had a *fastboot option*), it came with stock 5.1, and a bunch of bloatware.
I downloaded the one click root method for the h811 which was perhaps the easiest root i've ever done. great. i also had to flash my recovery to twrp 2.8 for some reason.
Rocked out to a newely rooted device on 5.1 until the t mobile bloatware and system update notification kept bugging me, so I said * eff it, i've been holding out for a while*
So I get to the cm 13 wiki for my device, I managed to install the cm recovery ( cant remember how i did this for some reason) and then i was able to flash cm13 to my phone. CM13 is sleek, and smooth but is presenting problems.
First of all, no google play store and the gapps zip wont install through cm recovery ( fails and tells me to use twrp instead which is a problem because i can't boot this phone into fastboot mode)
I am unrooted and can not figure out how to properly root a T mobile h811 running cm13, so the twrp manager doesn't work because it "requires root" then shuts down. ( enable root access in the cm13 developer options does nothing at all and yes, for adb and apps)
FAST BOOT MODE DOES NOT SEEM TO EXIST ANYMORE ON MY PHONE - Following the many tutorials, which goes long the lines of using adb/fastboot, adb devices can see my device, but fastboot devices can't ( figures) because its not in fastboot mode. Any fast boot reboot bootloader or any variant of that command only reboots the phone, to... swipe the screen.
I've installed the lg bridge crap ( which installed an updated usb driver) that doesn't even recognize my phone " no mobile device connected". tried uninstalling and reinstalling, but nothing. When putting the phone in download mode, to see if adb would rcognize it, windows sees this as a new device , installs drivers but says " device can not start, code 10 * in device manager. :silly:
is there anything that can be done?? google searches result in obvious solutions that SHOULD work but don't, or threads where a person coincidentally has the same exact problem as I do, but their response is usually the last response in the thread that goes unanswered
summary : I've install cm13 on my lg g4 h811, I do not have root access, I can not install twrp due to ( no fastboot mode) in effect, i cant install gapps, cant root phone etc..
any help?

did you ever unlock the phone....?

Yes, unlocking the phone is one of the first things you would need to do. In Developer Options > OEM Unlock. Then in bootloader, run the unlock command. This will delete /data and internal storage so back up your files so you can transfer them back via adb or fastboot.
Then you're probably going to need to temp boot TWRP, then flash the TWRP recovery image in TWRP. THEN you can flash properly.
Carefully read through this thread:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Good luck.
Edit: oh and this thread belongs in Q&A.

Alright. Am I only to read the first post or all 30+ pages? ( not that i have a problem, just curious)

Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.

aoaleman said:
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
Click to expand...
Click to collapse
"ARE YOU HAVING TROUBLE WITH LGUP NOT SEEING YOUR MOBILE?
Try this....... take the back off your mobile so you can get at the battery. Connect your mobile via USB. Start LGUP, if it does not see your phone DO NOT DISCONECT, DO NOT RESTART OR TURN OFF LGUP. Take out the battery and then put it back in.......let the phone restart on its own. LGUP should now see it."
didn't work, very frustrating. any clues? on windows 8.1 by the way. tried two computers. none can see this phone. I can connect the phone to the computer and see its storage, lg usb driver is installed

You probably need to reinstall the drivers. It might be the fastboot driver. That's what worked for me.

I've reinstalled the official drivers, uninstalled them... Jusst the mobile USB driver, a combo of both, plenty of times. Don't understand why this software doesn't see my phone
Lgup, lgair, lg bridge, lg USB driver (skinned down) .. Nothing works tested on my gaming rig., and work laptop both running win 8.1 64 bit

Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know

TacoTuco said:
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
Click to expand...
Click to collapse
This section does get more views though haha.
Anyway I feel that the 811 is one of the more finicky devices to get into fastboot at least in my experience. I had to enable and disable dev options while plugging and unplugging device and it finally worked. No idea if that'll work for everyone though.

I reasked the question in Q and A. Please help some one.

You start over. LG bridge.

Having the same issue. I'm on Windows 10. What developer settings did you mess with to get it working, tiskewlio?

The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?

Sunaj1 said:
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Click to expand...
Click to collapse
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing

thevirgonian said:
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
Click to expand...
Click to collapse
silly question maybe, but is there a specific tutorial in getting this to work with the files provided given my situation? (commands, etc..) will this somehow bypass the the lge mobile mtp device that wont install ? I had installed the system wide adb/fastboot drivers, and already had a folder with just the minimal install of the adb but didnt have a few files in the one you provided ( lg root, busy box, etc) so not quite sure what to do with them.
Again, if possible want to flash twrp recovery to my device but can't due to * waiting for any device* and the ( device cannot start ) error
Thanks

* waiting for device* when putting phone in download mode and pushing fastboot flash twrp-2.8.7.1-h811.img.
Any help would be appreciated as I need to get the driver to work first. see attached picture.
Cha h

the issue is largly resolved as i've been able to flash the recovery and install another rom. But i'd still like to know how to get the download mode driver properly working in the event i need a computer and can't do a self contained install.

Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.

travisd4est said:
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
Click to expand...
Click to collapse
i dont know man, i did all that a million times over, but recently i was able to just flash the stock MM rom to the device using LGup. Think i'll just stick with stock rom and root for a while as all this stuff is a little finicky at times. Thanks for your help.

Nexus 6 bootloader troubles

ok i have a bit of an issue.
simply put i was attempting to remove xposed, root, busy box. really just about any and all modifications. so i attempted to flash a stock 5.1.1 from google... i think i flashed the wrong one. because everything went fine through the flashing, but the phone wont boot past the google splash screen.... well as the derp i am. i locked the boot loader after because i was planning on sending it back to at&t. well now. im attempting to try a few different 5.1.1 images. (which in writing this im thinking... that isnt probably the best course of action.)
well i guess what this leads to is..... first.... which image do i use.
i was running 5.1.1 before all the modifications. so i just attempted to flash a 5.1.1 for all carriers cept T-moblie
i used shamu from this site https://developers.google.com/android/nexus/images#shamu
i also want to toss it out that the phone has been dropped....so internal damage might be a possibility, but i doubt thats it since it was fine before the flash.
so over what image should i flash? and is there a way to unlock the bootloader without going into the settings and chekcing the OEM box under dev options? because accessing the phone is basically limited to boot loader and recovery right now.

If you locked the bootloader, you cannot flash factory images. If you still have a custom recovery installed, install a custom ROM. Otherwise, you need to find the Android N Preview 1 OTA zip, which should be on these forums, and flash it through stock recovery. The OTA is a complete system image, and will update your system regardless of whether the bootloader is locked or not.
Regardless of which way you install a ROM, reveal the Developer Options menu and check "Enable OEM Unlock". Then you can unlock the bootloader and flash a fresh Android 6.0.1 factory image from Google, which is carrier agnostic.

Strephon Alkhalikoi said:
If you locked the bootloader, you cannot flash factory images. If you still have a custom recovery installed, install a custom ROM. Otherwise, you need to find the Android N Preview 1 OTA zip, which should be on these forums, and flash it through stock recovery. The OTA is a complete system image, and will update your system regardless of whether the bootloader is locked or not.
Regardless of which way you install a ROM, reveal the Developer Options menu and check "Enable OEM Unlock". Then you can unlock the bootloader and flash a fresh Android 6.0.1 factory image from Google, which is carrier agnostic.
Click to expand...
Click to collapse
ok well first i appreciate the reply
so basically the set up is i am running stock recovery with a locked boot loader.
if i use this Android N Preview 1 OTA zip. this will allow me access to the dev options which then i can boot up to check the bootloader box? then i can flash 6.0.1.
if that's right then awesome! i appreciate the help. so just so i don't fall back into this mistake. i have the AT&T version of the Nexus 6.
so if there is a specific Image i need, could you please point me to it?
I'd rather not have this happen again lol. the reason i ask is because the site i posted in my Original post has like 4 version of the 6.0.1 image that i can choose from. and since my track record of doing this hasn't panned out all that well so far i figured id just ask for specifics before attempting anything because clearly i messed up and have very little understanding of what im doing.
again. i really appreciate your advice

"Carrier agnostic" in my previous post means it doesn't matter what carrier you have. With Android 6.0.1, the system images no longer have carrier customization within them. The carrier-specific stuff is downloaded when the phone is set up with the SIM inserted.
As for your current setup, install the Android N preview OTA by sideloading it in recovery, boot into Android, enable developer options, and enable OEM unlock. From there, you need to make sure you have on the PC drivers for the Nexus installed, as well as Fastboot and ADB. Unlocking the bootloader as well as installing the Android 6.0.1 system image require it. If you need a walkthrough, there should be tutorials for both installing the Android N OTA as well as installing a system image in the General section of the Nexus 6 forums.

Strephon Alkhalikoi said:
"Carrier agnostic" in my previous post means it doesn't matter what carrier you have. With Android 6.0.1, the system images no longer have carrier customization within them. The carrier-specific stuff is downloaded when the phone is set up with the SIM inserted.
As for your current setup, install the Android N preview OTA by sideloading it in recovery, boot into Android, enable developer options, and enable OEM unlock. From there, you need to make sure you have on the PC drivers for the Nexus installed, as well as Fastboot and ADB. Unlocking the bootloader as well as installing the Android 6.0.1 system image require it. If you need a walkthrough, there should be tutorials for both installing the Android N OTA as well as installing a system image in the General section of the Nexus 6 forums.
Click to expand...
Click to collapse
well when using the adb devices command... my device wont show up. i can get it to show up when i reboot into bootloader and use fastboot devices, but it wont register in the recovery. could it be because i dont think i have ADB debugging checked? since i flashed new image on it and now i cant access the menus i cant chenc the debugging box either.

So where are you getting stuck? The OTA needs to be copied to internal storage and installed from there. You shouldn't need ADB or Fastboot until after you install the N preview.

Strephon Alkhalikoi said:
So where are you getting stuck? The OTA needs to be copied to internal storage and installed from there. You shouldn't need ADB or Fastboot until after you install the N preview.
Click to expand...
Click to collapse
ok so im lost now. i need to take the tgz file and put it on my phone then when i go to the recovery i need to sideload it?.. dont you do that by having it sideload the file from your PC? right? well my issue now is that i cant get it to show its storage on my PC. when booted into recovery the device wont even show up on my PC at all and when it boots into fastboot it regesters, but i cant do anything because the bootloader isnt unlocked i also cant unlock it via command because the OEM checkbox hasnt been checked. and i cant check the oem box via usb debugging because my device doesnt regester when in recovery.
so im not sure. where to go from here. is there a way to place the file on my phones storage via fastboot or usb debugging? preferably fastboot because ADB commands dont seem to regester to my phone at all.

You need to start reading, which I recommended if you needed a walkthrough.
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

Age135 said:
well when using the adb devices command... my device wont show up. i can get it to show up when i reboot into bootloader and use fastboot devices, but it wont register in the recovery. could it be because i dont think i have ADB debugging checked? since i flashed new image on it and now i cant access the menus i cant chenc the debugging box either.
Click to expand...
Click to collapse
you can only use fastboot, while you're in the bootloader, to do anything.. unlock it, flash a factory image, flash a custom recovery. adb will do nothing and see nothing.

simms22 said:
you can only use fastboot, while you're in the bootloader, to do anything.. unlock it, flash a factory image, flash a custom recovery. adb will do nothing and see nothing.
Click to expand...
Click to collapse
yeah thats what i was thinking. the other guy was saying to sideload using recovery, but tbh i wasnt sure how to sideload and i didnt wanna be rude and act like you guys were my personal helpers. so i googled how to just to get a general idea. the idea that i got was that you needed to sideload anything by downloading it to your PC then using adb to install it.
apparently i dont know as much as i think. hes helping me out alot, but im not sure how to pull a file onto a phone that wont boot. i thought maybe i could transfer it via adb,but i think that boat is gone. since it seems i can only use fastboot, but idk of a way to transfer a file onto my phone via fastboot.
i appreciate the help though. thanks

Strephon Alkhalikoi said:
You need to start reading, which I recommended if you needed a walkthrough.
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
ok. so all of these say i should download it to the phone so i can sideload it using the recovery.... well this is the issue. the phones storage wont register on my PC. so transferring a file normally isnt gonna be possible (unless im doing something wrong and theres a way to make it show up). is there a way i could transfer it onto the device via fastboot?
Edit:
after doing some reading. i have found out i may not have adb drivers installed... ive looking into how to install them, but the only option i found was through a downloader which seems to stop after a bit of the download saying its waiting for something... so im completely lost as to what to do from here.

Age135 said:
ok. so all of these say i should download it to the phone so i can sideload it using the recovery.... well this is the issue. the phones storage wont register on my PC. so transferring a file normally isnt gonna be possible (unless im doing something wrong and theres a way to make it show up). is there a way i could transfer it onto the device via fastboot?
Edit:
after doing some reading. i have found out i may not have adb drivers installed... ive looking into how to install them, but the only option i found was through a downloader which seems to stop after a bit of the download saying its waiting for something... so im completely lost as to what to do from here.
Click to expand...
Click to collapse
Try these drivers from Googles site.
https://developer.android.com/sdk/win-usb.html