Database Develop

Nexus 7 2012 hspa soft brick on 4.4 ota need my files accessed

Hey everyone, so tonight I got the 4.4 ota on my N7, I am unlocked and rooted but stock everything including recovery.
After updating, my N7 keeps going to stalk recovery and that's it.
I know I can just reflash everything but I have a few very important files. Is there a way to reflash 4.3 without losing data or accessing the data partition while soft bricked so I can recovery my files?

I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.

chrisinsocalif said:
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
Click to expand...
Click to collapse
I'm not sure. I'd like to have this confirmed before I do anything. It's not urgent as the due date on my prgect isn't for another couple of weeks. But thanks. I'll look at that as a last resort.

Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.

chrisinsocalif said:
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
Click to expand...
Click to collapse
ADB or Wugs root kit don't see my Nexus 7 as it keeps rebooting to the dead droid and I know I don't have it set for debugging. Guess I'm screwed.

When you say "dead droid", you're referring to fastboot mode, right? (Android icon with a bunch of text below it, starting with "Fastboot Mode" in red.)
If you have fastboot, you can flash TWRP Recovery 2.6.3.0. Download it from Team Win's site (Google it). Then:
fastboot flash recovery openrecovery-twrp-2.6.3.0-grouper.img
fastboot reboot-bootloader
Use the Volume keys to select "Recovery Mode" and hit Power. Once you see the TWRP menu, you should have adb root access automatically. Connect tablet to USB, and use adb pull to download the contents of /sdcard:
adb pull /sdcard /dumphere
Replace "dumphere" with whatever directory you want to dump to. I'm sure there's better guides and explanations for this, but this is the quick version.
I guess you could reflash stock recovery afterwards, but I can't think of a reason why you'd want to. It's not like it's that useful.
As a rule of thumb, you should at least know how to get around a command line, and use adb and fastboot before mucking around with your tablet.
-XCN-
P.S. I could be mistaken, but I don't think internal storage (which is /sdcard, or /data/media) is overwritten when you flash a ROM. Obviously, backup first before trying.

[Q] "adb server out of date" along with many other problems.

So, I have spent the last 4 hours trying to find information and trying to fix things and I have yet to get nowhere.
I tried to install SkyDragon (http://forum.xda-developers.com/showthread.php?t=2400161) on my HTC One. Having gotten an insurance replacement in the last month, I forgot that I hadn't gotten around to getting S-OFF on this replacement device. (I had S-OFF on my old one). Due to this, everything got messed up.
It was trying to boot, went to HTC screen, then tried to reboot to recovery. Clockwork mod would boot, but as soon as any graphics came on the screen, it would reboot back to the HTC screen. This looped.
I managed to flash TWRP on it, but the same thing was happening.
After using fastboot to clear the cache, I got into TWRP. Awesome. Now I just need to get a ROM on this sucker.
adb keeps telling me "adb server is out of date. killing..." In regards to this, I have gone to the Android SDK and installed the latest version. I also tried updating to the latest drivers on my computer as well.
To my understanding, you can't push whole .zip files with fastboot, but I tried to use the "fastboot update rom.zip" command, which won't work due to "archive does not contain 'android-info.txt'" and "archive does not contain 'android-product.txt'".
I tried to go into TWRP and mount the storage, but lo-and-behold it crashes and doesn't mount crap so I can't copy this rom over to flash it with TWRP.
Please. Does anyone have any suggestions? I am not the MOST android savvy, but I have tried everything I could think of. One last resort is I'm gonna try to flash clockwork and see if I can get it to mount. Please help me?
EDIT: Clockwork didn't work, and sideload won't work because "adb server is out of date. killing..."
EDIT 2: I've got an M7_UL with S-ON, HBOOT 1.44.0000. Fastboot works like a charm, adb tries to connect but fails every time.

What is your PC Operating system?
You may wish to try a Linux Live CD.

BenPope said:
What is your PC Operating system?
You may wish to try a Linux Live CD.
Click to expand...
Click to collapse
Both of my PCs are running Windows 7.

Using my roommates computer, I downloaded the Android SDK and I am now able to adb push. Here's to hoping just pushing a ROM and booting into recovery to flash it will work.

starlitjessi said:
Using my roommates computer, I downloaded the Android SDK and I am now able to adb push. Here's to hoping just pushing a ROM and booting into recovery to flash it will work.
Click to expand...
Click to collapse
It works now. I was able to push a stable ROM from my roommate's computer and got it running just fine. Thanks anyway!

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.

I need some help unbricking my fire...

Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA!

Do you know if you had amazon FireOS version 5.0.1 or 5.1.1?
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
drillster said:
I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
Click to expand...
Click to collapse
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.

Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740

hAtE NeVeR dIeS said:
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
Click to expand...
Click to collapse
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36

blueberry.sky said:
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
Click to expand...
Click to collapse
I have 5.1.1... yeah, thanks.

blueberry.sky said:
Do you know if you had amazon FireOS ve wrsion 5.0.1 or 5.1.1?
Click to expand...
Click to collapse
I have 5.1.1.
blueberry.sky said:
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
Click to expand...
Click to collapse
Yeah I selected apply update from adb, adb devices was blank, didn't work.
blueberry.sky said:
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Click to expand...
Click to collapse
I went into fastboot mode, installed twrp, and nothing happened because yes, its 5.1.1.

I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..

blueberry.sky said:
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
Click to expand...
Click to collapse
Do you have any ideas on how to do this? I would greatly appreciate it.
Thank you!

Since I haven't read anyone try it before, there would be some risk. I suppose you are already bricked, seemingly without a way to fix it, but you could brick it harder. You might be able to get adb working. I may not have any ideas on how to get adb working for you, but someone else might know. If you try flashing the stock OS via fastboot, there is a chance you could brick it in a different way.
The command would be
Code:
fastboot update <filename-of-stock-firmware.zip>
But we don't have a .zip stock firmware file. In twrp recovery you can just rename the .bin file to .zip & it works. Not sure if that will also work for fastboot. My guess is it won't work & might brick you.
Also be aware, on Fires that self-updated to FireOS 5.1.1 (or came with 5.1.1 new) you must only flash 5.1.1. Attempting to flash 5.0.1 will brick it 100% of the time & it's unrecoverable.

drillster said:
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
. . .
Click to expand...
Click to collapse
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.

I have same issue.
[QUOTE=drillster;64617577]Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA![/QUOTE]
I did the same thing. Slim worked great, tried to flashfire CM12, ot bricked. Can get fastboot, but nothing else. Afraid to try update from fastboot.

I just want to say thanks to everybody who contributed, I'm really appreciative of the support, especially because I didn't expect it, haha! Listening to blueberry.sky I'm going to try the flashboot update, because it's either that or a bricked device. School just started so I got busy with that.
DoLooper said:
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
Click to expand...
Click to collapse
So when I have it in adb mode, the fire doesn't seem to show up anywhere in any of my devices, and I can only find it when it's in fastboot mode. So when it's in that mode, I've tried Android ADB Interface, Android ADB Composite Interface, and when I go back to adb sideload, it's just not there in device manager. I don't know what this means, so any speculation? But no matter what mode I'm in or what driver I'm using, I can't seem to get it to show up in adb when in sideload mode.
Again, thanks everybody, and I hope anybody else in the future with this issue can refer to this thread for a lead!

So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I didn't rename the Slim and this is what I get:
C:\path\to\SuperTool>fastboot update Slim-ford-5.1.1.build.2.2b-20151210.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!

drillster said:
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
Click to expand...
Click to collapse
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?

thekrakah said:
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
Click to expand...
Click to collapse
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip

drillster said:
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
Click to expand...
Click to collapse
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.

thekrakah said:
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
Click to expand...
Click to collapse
On my device, I can get fastboot, but not adb. if I reboot from fastboot, I only get the
CM logo and it sticks there permanently until I power off. When I boot to fastboot, the screen is blank but my Windows PC can see the device and return the SN. I can issue the command to reboot to bootloader, but reboots to fastboot with "fastboot" in small letters at the bottom of the screen. What else can I try? Thanks for all the help offered so far.

What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.

blueberry.sky said:
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
Click to expand...
Click to collapse
When I try to get into recovery, it boots with a blank screen. At that point, I can connect to my PC, type fastboot devices, and it will show me device. Then I try to reboot-bootloader, and it reboots to fastboot, but this time it says fastboot on the screen. I can't seem to get to recovery

watch this video to see if it helps.
https://www.youtube.com/watch?v=RQLoH-ahjy4

Connection issues between computer and Nexus6

I bought a Nexus6 about a month ago. I wasn't planning on rooting it, but I have rooted a number of devices in the past so am reasonably comfortable doing that. I bought the phone from Amazon but I am on T-mobile's network.
After I fired up the phone and used it for a while, I got a message asking me to update to software version 5.1. When I go to the about on my phone, it says it has 5.1.1 but it says the build number is LRX22C which when I looked that up indicates that it is actually running 5.0. I told the phone to update, but it fails every time (android guy with the red exclamation mark over his belly). I did a factory reset and repartition and still the same thing. At this point, I figured I would just root and and force it to 6.0.
After installing drivers, ADB-tools, etc. my computer recognizes the phone. When I connect by a USB cable and the phone is on, it shows under devices. However, when I boot into fastboot mode, my laptop no longer recognizes the Nexus. The fastboot screen shows that the phone is unlocked, and it recognizes that it is getting power from the laptop. However, it says to connect via usb. Running the command prompt and using SDK-Windows, when I type fastboot devices it shows nothing.
Interestingly, I see that Superuser is on the phone and working. I don't think I rooted my phone at any point in the process of trying a lot of different things, although anything is possible. I have been thrashing around a bit trying to get this to get the phone on 6.0 so might have rooted accidentally although I doubt it. My suspicion is that I was given a previously used phone that someone rooted and returned.
Any suggestions/help out there?

When in Fastboot Mode, what does Device Manager show? Does it see the device correctly, or is it showing a yellow triangle w/ exclamation point over the device?

RMarkwald said:
When in Fastboot Mode, what does Device Manager show? Does it see the device correctly, or is it showing a yellow triangle w/ exclamation point over the device?
Click to expand...
Click to collapse
It shows Other Devices > Fastboot Shamu S with the yellow triangle and exclamation point. I have motorolla device manager installed and I thought that had my drivers covered but perhaps not?

These devices do have driver issues. Try downloading the correct drivers and it should fix it, a lot of people have had similar issues.

@LSquared
Download Wugfresh Nexus Root Toolkit. It has a long button on the top right "Install and test drivers" - a really helpful guide in clearing out any old drivers and installing and testing the new ones.
It can also perform many other functions, but after a lot of persuasion(!) in these forums I decided that learning to do everything manually is not only simple but safer, because you know at exactly which point an error occurs. The driver setup part of NRT is a brilliant help in setting your PC up once to get you started.
If you don't have anything valuable on your device yet, install the MMB29S factory image, then TWRP, and from there install SuperSU v2.66, and you're as up to date as you can possibly be.

Spend a few hours doing research and you will be fine. Just stay away from root kits. They only make things worse and lessen the experience of owning a nexus. As well as stops any help you may get in the forums as no one will help those that use the root kits.

Thanks for all the help/suggestions. After a lot of poking around, I realized that I had the right driver hiding in a folder (inside SDK I think) and had to just manually point to them and that got rid of the connection issue. Now I seem to be stuck on flashing the latest stock OS. I have been trying to flash via Minimal ADB and Fastboot but it isn't pushing the image there correctly. I don't want a custom rom, just stock 6.0.

LSquared said:
Thanks for all the help/suggestions. After a lot of poking around, I realized that I had the right driver hiding in a folder (inside SDK I think) and had to just manually point to them and that got rid of the connection issue. Now I seem to be stuck on flashing the latest stock OS. I have been trying to flash via Minimal ADB and Fastboot but it isn't pushing the image there correctly. I don't want a custom rom, just stock 6.0.
Click to expand...
Click to collapse
How are you trying to push the files, I assume Fastboot, are you getting an error? Is your Android SDK up-to-date?

LSquared said:
I have been trying to flash via Minimal ADB and Fastboot but it isn't pushing the image there correctly. I don't want a custom rom, just stock 6.0.
Click to expand...
Click to collapse
Google updated fastboot a little over a year ago to allow flashing the very large system.img files. Minimal ADB & Fastboot does not have this update (I believe). Download the latest Android SDK and you'll be good to go.

cam30era said:
Google updated fastboot a little over a year ago to allow flashing the very large system.img files. Minimal ADB & Fastboot does not have this update (I believe). Download the latest Android SDK and you'll be good to go.
Click to expand...
Click to collapse
I just downloaded Android SDK so it has the latest files (I believe). Android SDK doesn't connect to the phone, it just keeps an updated set of firmwear, right? If I am not using minimal ADB and fastboot to push files from my computer to the phone, what program should I be using? It seemed a lot easier on my older phones that had a micro SD card because I could just drop the new Rom on there and install that from the bootloader.

LSquared said:
If I am not using minimal ADB and fastboot to push files from my computer to the phone, what program should I be using?
Click to expand...
Click to collapse
Use the ADB and fastboot that are included with the Android SDK that you downloaded. They are in the Platform-Tools folder.

cam30era said:
Use the ADB and fastboot that are included with the Android SDK that you downloaded. They are in the Platform-Tools folder.
Click to expand...
Click to collapse
If I click on either of those to run the application, it flashes a box for a split second and then nothing. I guess I am missing a step?

LSquared said:
If I click on either of those to run the application, it flashes a box for a split second and then nothing. I guess I am missing a step?
Click to expand...
Click to collapse
I would suggest reading and following this guide >http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot

cam30era said:
I would suggest reading and following this guide >http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot
Click to expand...
Click to collapse
That guide is great and helped me get the bootloader unlocked and the phone rooted. I downloaded the image file just fine, but when I go to run root-windows.bat I get the message "fastboot is not recognized as an internal or external command." I am guessing I don't have some file in the right location?

LSquared said:
That guide is great and helped me get the bootloader unlocked and the phone rooted. I downloaded the image file just fine, but when I go to run root-windows.bat I get the message "fastboot is not recognized as an internal or external command." I am guessing I don't have some file in the right location?
Click to expand...
Click to collapse
The flash_all scripts don't work. Flash each img file individually, after you've extracted them all from the ,zip.

Yup, flash the .img files individually, the batch command doesn't work.

Here's the guide I always use: How to manually flash img files to your Nexus device
Basically, with phone connected to computer and booted to the bootloader, open Command Prompt window, change directories to where your sdk/platform-tools directory is with your Shamu files, then:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Code:
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
Code:
fastboot flash radio "name of radio"
fastboot reboot-bootloader
NOTE: You'll have to extract the files from the image-shamu-mmb29s.zip file in this case to flash MMB29S.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Code:
fastboot reboot
I'm aware, it may be overkill, but I've never had any issues performing all of these steps to get back to 100% stock so if it "isn't broken, don't fix it". Also this will wipe your internal SD area, so any files you want to save you should save them prior to starting this.

Good summary!
RMarkwald said:
Also this will wipe your internal SD area, so any files you want to save you should save them prior to starting this.
Click to expand...
Click to collapse
To avoid wiping your internal user storage, just skip the step that flashes userdata img (and the step at the beginning that erases usedata)