Database Develop

I need some help rooting my phone

I need some help like if someone could help me root my phone by conectiong to my computer to help me out that would be great. I have hacked many windows mobile phones and iphone and I still cant do this I think i got the bootloader to unlock and I think I have it rooted im just having a problem trying to put the recovery image on before i can put a new rom on some please help me out.
Yahoo messanger jasonolbrys

help>!
give more details about where you stand , how far your in on your phone.
JasonInWisconsin said:
I need some help like if someone could help me root my phone by conectiong to my computer to help me out that would be great. I have hacked many windows mobile phones and iphone and I still cant do this I think i got the bootloader to unlock and I think I have it rooted im just having a problem trying to put the recovery image on before i can put a new rom on some please help me out.
Yahoo messanger jasonolbrys
Click to expand...
Click to collapse

Im pretty sure its rooted but im having a hard time trying to get the recovery-RA-nexus-v1.7.0.img to run i have tryed it wit hthe termial and through windows and im having no luck

JasonInWisconsin said:
I need some help like if someone could help me root my phone by conectiong to my computer to help me out that would be great. I have hacked many windows mobile phones and iphone and I still cant do this I think i got the bootloader to unlock and I think I have it rooted im just having a problem trying to put the recovery image on before i can put a new rom on some please help me out.
Yahoo messanger jasonolbrys
Click to expand...
Click to collapse
What are you seeing when attempting to flash recovery?

So when you reboot your phone you see an unlocked lock under the colourful "X"? If you do, you have indeed unlocked your bootloader and have a proper fastboot setup.
Now you need to boot back into the bootloader [Trackball + Power]. Place the AmonRa recovery image into the "tools" folder of your sdk and rename it simply to "recovery.img". Then run the command
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
On the top right of your phone screen you will see a progress bar. Once it is complete, boot into the new recovery by fully powering down, thenholding [Volume Down + Power ], selecting "Recovery" from the list and tapping the power button to confirm selection.

Double post.

We are all jumping to conclusions here...let's start from the beginning.
OP - have you turned your phone on?
(I crack myself up)

Hahaha what the hell?

ok so i renamed the AmonRa recovery image to recovery.img and put it in the tools folder on my desktop and booted the phone in bootloader then tryed to run the command on the computer and I cant get it to work what am i suppost to type

I would try putting the recovery.img SDK\ dir, then using fastboot
fastboot flash recovery recovery.img
easiest way

wesbalmer said:
I would try putting the recovery.img SDK\ dir, then using fastboot
fastboot flash recovery recovery.img
easiest way
Click to expand...
Click to collapse
The tools folder is where fastboot lives so unless he puts the sdk\tools path in his global path, he will have to type tools\fastboot flash recovery recovery.img
OP - if you type fastboot devices, do you get an item list that displays your device?

deprecate said:
The tools folder is where fastboot lives so unless he puts the sdk\tools path in his global path, he will have to type tools\fastboot flash recovery recovery.img
OP - if you type fastboot devices, do you get an item list that displays your device?
Click to expand...
Click to collapse
True, forgot how difficult it was to root the N1 :-(

ok i got it but now i flashed a new rom and it wont come off the start up screen this is nuts.

JasonInWisconsin said:
ok i got it but now i flashed a new rom and it wont come off the start up screen this is nuts.
Click to expand...
Click to collapse
go back to recovery, wipe everything (except your sd card). Flash your rom and if needed, the g-apps package (cyanogen rom additional step). Tell it to reboot and wait for it to boot up.
Sounds like you didn't wipe and got it stuck in a bootloop.

All is well thanks a lot guys

It's not hard to root the Nexus at all. I had adb and fastboot all set up for my Dream. It only took me maybe 2 minutes from when I unboxed my Nexus to having unlocked the bootloader. But he got it working now so it's good.

[Q] Htc One BRICKED.

After only four day of having this phone i managed to brick it. I would really like to know if its fixable or if i have a really nice paper weight. Im stuck on a boot loop, I was half way through flashing a rom when it suddenly shut off. Now it will not boot up. I can load into the bootlader but when i try to go into recovery it just sends me to fastboot. When i restart the phone i can see the old recovery (TWRP)for just an instant but then the screen goes completely black. If i plug in to my pc, nothing happens my computer detects it but it says y device is damaged nd it cant identify it. PLEASE HELP Am i out of luck?
Ive looked around but i couldnt seem to find anyone with the same problem as me (Sprint Variant)

Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help

There's a Sprint One forum as well, so hopefully you found a ROM on there!
http://forum.xda-developers.com/forumdisplay.php?f=2215

jaythenut said:
Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help
Click to expand...
Click to collapse
I really hope so because on a college budget i cant afford another phone D:

Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.

wnp_79 said:
Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.
Click to expand...
Click to collapse
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!

i suggest you contact with HTC customservices to repair this problem.

Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock

Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.

DynamicRam said:
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock
Click to expand...
Click to collapse
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.

Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
dont give up
Sent from my HTC One

Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
Edit: Just got done typing the stuff below and saw you can't connect to your device in fastboot? What do you mean by re-installed driver?
Don’t worry, as long as you can still get into hboot your phone is not completely bricked!
The fastboot commands I referred to need to be carried out on your laptop/pc when you phone is connected in fastboot.
Can I assume that as you have already unlocked bootloader and flashed a custom recovery you are already familiar with this and have your computer set up for fastboot commands?
(Apologies if you already know some of this, best not to skip parts out though!)
I’d start with downloading a fresh version of your chosen recovery, and place it in your fastboot directory ready. I’d also do the same with your ROM.
Like you have already done, boot into fastboot. Connect your phone to your pc, and the red text should change to ‘Fastboot USB’.
Then open up command prompt and get to your fastboot directory. (On Windows 7 you just find that folder in Explorer, hold shift and right-click, then choose ‘Open command window here’.)
To check your pc is talking to your phone, type ‘fastboot devices’. You should get a device serial number back if all is well.
Then type ‘fastboot erase cache’ and hit enter.
Then type ‘fastboot erase recovery’ and hit enter.
Then type ‘fastboot flash recovery [name of recovery].img’ and hit enter.
Then type ‘fastboot reboot recovery’ and hit enter.
Hope fully you should successfully boot into recovery now. Once in recovery, mount USB storage and copy over your fresh ROM. Choose to do a full wipe including cache and dalvik, then reflash your ROM.
Reboot.
Let me know how this goes.

cronus101 said:
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.
Click to expand...
Click to collapse
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:

Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app

Muquita said:
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:
Click to expand...
Click to collapse
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html

Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck

wnp_79 said:
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html
Click to expand...
Click to collapse
(Win8 but the procces is identical.) All my drivers are up to date. Still no love.

On the dev forum is a thread that includes all the latest drivers (including an app to remove older drivers.)
Find that thread, download the drivers and bmp and driver removal tool. Remove drivers with tool, install the new drivers, reboot, connect phone and see if 'adb devices' finds anything.
Also make sure you're using the latest adb.
Sent from my HTC One using xda app-developers app

thneed said:
Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app
Click to expand...
Click to collapse
This actually sounds really similar to my situation.. Would you care to be a little more specific on the procedure? noob here.

Tabtoub said:
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck
Click to expand...
Click to collapse
My pc will not recognize my phone. The drivers are up to date but when i plug it in it says something malfunctioned ?

Is it possible to access files / pics via fastboot only?

Hello All,
I have following issue and hope that - if possible - someone can help me. I also would like to mention that I am not an
Android expert but did read a lot of articles here in the forum to find out - or better - to get an idea how things are working.
My Z3C had a water damage. Now I only get fastboot mode. Display is broken and does not show anything. I installed Android-SDK
to get ADB and Fastboot. I installed also drivers.
When I connect the device while pushing the "volume down" button the device manager show me a somc flash device with the "volume up" button I see an Android ADB Interface device. However ADB is not working (no device found) only Fastboot does.
I flashed the "Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img" with Flashtool via fastboot in the hope that I can somehow access
to "sdcard" by blindly navigating to "mount storage" but nothing seem to work.
On my linux device I see that the usb device is recognized but that it is not an mtp device.
Before I continue to spent hours without really knowing what I am doing I thought that if there is a solution I would find it here.
So if there is any way to get access to my files / pics on the device I would be really glad if someone can let me know how or
at least bring me to the right direction.
Thanks a lot in advance!

Is your bootloader unlocked?

clouds5 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Thanks for your reply clouds5.
I followed the process to unlock the bootloader (got code from sony side and unlocked via fastboot with
"fastboot.exe -i 0x0fce oem unlock 0xKEY").
In Flashtool, when I click on the "BLU" Icon I get a window with with my IMEI and my Unlock Code and a
Relock Button. So I assume that the bootloader is unlocked.
If there is another way to verify please let me know and I will do.

no you cannot access files via fastboot only. but isn't it possible to flash custom recovery img file and boot into recovery and access files?

evildog1 said:
no you cannot access files via fastboot only. but isn't it possible to flash custom recovery img file and boot into recovery and access files?
Click to expand...
Click to collapse
I flashed "Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img" from doomlord.xperia-files.com/download.php?dlid=WjNjX0Rvb01Mb1JEX0FkdlN0a0tlcm5lbF92MDFfRlctMTA1 with
fastboot flash boot Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img
in the hope that it is possible but after rebooting it immediately goes into fastboot again. As I do not have
a screen I can not see anything - so I can not really confirm if it works or not - and in windows I do not see
anything either..

Galbasib said:
I flashed "Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img" from doomlord.xperia-files.com/download.php?dlid=WjNjX0Rvb01Mb1JEX0FkdlN0a0tlcm5lbF92MDFfRlctMTA1 with
fastboot flash boot Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img
in the hope that it is possible but after rebooting it immediately goes into fastboot again. As I do not have
a screen I can not see anything - so I can not really confirm if it works or not - and in windows I do not see
anything either..
Click to expand...
Click to collapse
hmm you better send it to repair.

evildog1 said:
hmm you better send it to repair.
Click to expand...
Click to collapse
That's unfortunately not an option as I had to disassemble the device

evildog1 said:
no you cannot access files via fastboot only. but isn't it possible to flash custom recovery img file and boot into recovery and access files?
Click to expand...
Click to collapse
Should sdcard appear automatically when booting into recovery or are there any specific steps I would need to complete?

[HELP]Making ADB work with Moto G 2014

Hi,
My friends Moto G just died and now it is just bootlooping. He asked me to try get contacts through ADB but it is not finding phone.
I installed Motorola Device Manager and it seems that it found phone and successfully used command "get variable", but when I use ADB via CMD it don't even finding phone.
How can I fix this?

Tenderenden said:
Hi,
My friends Moto G just died and now it is just bootlooping. He asked me to try get contacts through ADB but it is not finding phone.
I installed Motorola Device Manager and it seems that it found phone and successfully used command "get variable", but when I use ADB via CMD it don't even finding phone.
How can I fix this?
Click to expand...
Click to collapse
at first learn what ADB is.
at second - fastboot it the proper place to begin with.

PsyClip-R said:
at first learn what ADB is.
at second - fastboot it the proper place to begin with.
Click to expand...
Click to collapse
Well, fastboot don't want to work neither so that answer didn't help at all

Tenderenden said:
How can I fix this?
Click to expand...
Click to collapse
ADB can only be used from a fully booted device (you have to be past the login screen. It's a security measure so no one can mess with your data without approval). You can use fastboot commands though.
Try this
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
XXXXXXXXXXfastboot
Now do your thing, like flashing stock ROM. Multiple tutorials exist for that.

doppelhelix said:
ADB can only be used from a fully booted device (you have to be past the login screen. It's a security measure so no one can mess with your data without approval). You can use fastboot commands though.
Try this
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
XXXXXXXXXXfastboot
Now do your thing, like flashing stock ROM. Multiple tutorials exist for that.
Click to expand...
Click to collapse
That is the answer that I needed!
Can I somehow pull data from this phone using fastboot? Because I think that flashing stock ROM will erase any personal data, but I really need to get it.

Tenderenden said:
That is the answer that I needed!
Can I somehow pull data from this phone using fastboot?
Click to expand...
Click to collapse
No. That would defeat the lock screen. Just imagine someone steals your phone and can access your data just by booting into fastboot.

doppelhelix said:
No. That would defeat the lock screen. Just imagine someone steals your phone and can access your data just by booting into fastboot.
Click to expand...
Click to collapse
Okay, I got it. Now, have you got any suggestions how to get contacts and (hopefully) SMS back?

Tenderenden said:
how to get contacts and (hopefully) SMS back?
Click to expand...
Click to collapse
Contacts are synchronised with your Google account (unless you choosed not to). Can't say the same about SMS.

doppelhelix said:
No. That would defeat the lock screen. Just imagine someone steals your phone and can access your data just by booting into fastboot.
Click to expand...
Click to collapse
Loading custom recovery via
fastboot boot TWRP.img should do the job.
than one can can make a full backup, which might be extracted on pc as a regular archive.

PsyClip-R said:
Loading custom recovery via
fastboot boot TWRP.img should do the job.
Click to expand...
Click to collapse
Does this work with locked bootloader? That would be really messed up.

Tenderenden said:
Hi,
My friends Moto G just died and now it is just bootlooping. He asked me to try get contacts through ADB but it is not finding phone.
I installed Motorola Device Manager and it seems that it found phone and successfully used command "get variable", but when I use ADB via CMD it don't even finding phone.
How can I fix this?
Click to expand...
Click to collapse
Is your bootloader locked?
Can you try fastboot oem partition dump userdata (using mfastboot, not Google's fastboot)?

PsyClip-R said:
Loading custom recovery via
fastboot boot TWRP.img should do the job.
than one can can make a full backup, which might be extracted on pc as a regular archive.
Click to expand...
Click to collapse
I will try that. Firstly my friend want to message the seller to get his phone repaired. So I can not touch anything in software until he is done.
doppelhelix said:
Contacts are synchronised with your Google account (unless you choosed not to). Can't say the same about SMS.
Click to expand...
Click to collapse
Unfortunately in this case contacts weren't synchronised.
LuK1337 said:
Is your bootloader locked?
Can you try fastboot oem partition dump userdata (using mfastboot, not Google's fastboot)?
Click to expand...
Click to collapse
Well, it seems that I have to read something more about what you said here firstly xD
And the bootloader is locked.
But I appreciate any new idea that may lead to solving this problem.

Tenderenden said:
I will try that. Firstly my friend want to message the seller to get his phone repaired. So I can not touch anything in software until he is done.
Unfortunately in this case contacts weren't synchronised.
Well, it seems that I have to read something more about what you said here firstly xD
And the bootloader is locked.
But I appreciate any new idea that may lead to solving this problem.
Click to expand...
Click to collapse
fastboot oem partition dump userdata may work with locked BL and it'd be great to know if it does...

LuK1337 said:
fastboot oem partition dump userdata may work with locked BL and it'd be great to know if it does...
Click to expand...
Click to collapse
I will try it as fast as I can. Thanks

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)