Bricked Nexus 6 please help ASAP! - Nexus 6 Q&A, Help & Troubleshooting

I just bought a Nexus 6... Unlocked the bootloader and rooted the phone.... after realizing there were some issues with the phone I decided I would try and download the PURE rom for the phone... I installed TWRP recovery and tried to flash the image. When the phone booted back up it said that the data was corrupt, and to enter a password. Entering anything seemed to work and I would then reset the phone... but the same thing would come back up.
So I decided to try and wipe the phone again and re-install the ROM... after that it wouldn't load at all, came back with some kind of error.
Then I decided to do a full wipe of the phone and try and re-install the factory image... Problem is... I haven't tried to do anything with a phone in like 2 years and well... i'm having trouble on trying to figure out how I can restore the factory image. I have the SDK tools installed, the phone drivers are also obviously installed, but can someone help me try to reset to the factory image.
I only have like 3 hours to try and accomplish this from now because after this I have to get on a plane and won't be around and will also leave me without a phone... Can someone please help me as soon as possible? Thank you so much!! I could use somewhat detailed instructions but not crazy

http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

Try nexus toolkit by wugfresh can't go wrong. If you get error missing system.img while flashing go to options then flash then click force flash. The toolkit will download all needed steps and flash without a problem

dont use a toolkit. you are guaranteed to learn nothing, and doing it the right way is just as fast(and easy). plus, root toolkits mess up often. dong it right never messes anything up.

Nexus device can almost never be bricked, I say almost never because of the people variable, but if you can get it into bootloader mode it is easy to bring back. just follow the instructions above.
I agree that even though wugfresh tools is the best out there. I have used it before. You learn nothing about what needs to be completed.
I could never get the drivers to work for me in most cases. I use ubuntu and it always works running the manual commands.

Ok so I have tried to run the flash-all.bat file and it says in the command prompt it is an unrecognized command...
I'm assuming I must be missing part of the ADB tools? Ugh help!

jwleonhart said:
Ok so I have tried to run the flash-all.bat file and it says in the command prompt it is an unrecognized command...
I'm assuming I must be missing part of the ADB tools? Ugh help!
Click to expand...
Click to collapse
first thing to do in adb is run the command "adb devices" to make sure that adb sees your device, does adb see your device?

It says list of devices attached and then nothing....
Can someone give me a short step by step on what I need to do here? I'm really running low on time, this is really bad....

jwleonhart said:
It says list of devices attached and then nothing....
Can someone give me a short step by step on what I need to do here? I'm really running low on time, this is really bad....
Click to expand...
Click to collapse
wait.. you are flashing the factory img, you do not use adb for that. you boot into the bootloader then use fastboot for that. adb doesnt work in the bootloader anyways, use fastboot while youre in the bootloader, and type fastboot devices to make sure fastboot sees your device.

@simms22 is correct, tool kits make you learn nothing, and you get posts like this.
However if you are time contained. As much as it pains me to say this. Use the tool kit. And learn on a time when you can.
Download Wugs toolskit and flash back to stock images. And you'll be fine.

Update your SDK if u haven't already.
Unzip factory images and place in platform tools folder of SDK. (Unless you have environmental variables set correctly)
Open a command prompt from that directory (place cursor in empty space, hold shift and right click on mouse)
Boot into bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
Sent from my Nexus 6

simms22 said:
dont use a toolkit. you are guaranteed to learn nothing, and doing it the right way is just as fast(and easy). plus, root toolkits mess up often. dong it right never messes anything up.
Click to expand...
Click to collapse
Different strokes for different folks!!!!
Sent from my SM-T310 using XDA Premium 4 mobile app

doing the following command in command prompt:
fastboot devices
it shows the following device:
ZX1G2224G5
I'm assuming that is the nexus 6...
So whats next on the list then?
I unzipped the factory image and using the flash-all.bat script it says fastboot is not a recognied command.

dparrothead1 said:
Different strokes for different folks!!!!
Sent from my SM-T310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
not really.
if you know anything about what you are doing, its one thing, use a toolkit, enjoy yourself. if you have no idea what you are doing, the root toolkit is by far the wrong way to go. as you will still know absolutely nothing, and will learn nothing. and pretty soon, when you have some simple maintenance to do, and you have no idea how, you start thread about having your device bricked. and im sure that you personally have not helped out hundreds that have started threads about having their device "bricked" after using a root toolkit. i have.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
jwleonhart said:
doing the following command in command prompt:
fastboot devices
it shows the following device:
ZX1G2224G5
I'm assuming that is the nexus 6...
So whats next on the list then?
I unzipped the factory image and using the flash-all.bat script it says fastboot is not a recognied command.
Click to expand...
Click to collapse
you probably have to unzip it twice, if there is another zip within that one zip. and you can try not using the word fastboot, as i also have ran into fastboot programs where it wasnt needed.

simms22 said:
not really.
if you know anything about what you are doing, its one thing, use a toolkit, enjoy yourself. if you have no idea what you are doing, the root toolkit is by far the wrong way to go. as you will still know absolutely nothing, and will learn nothing. and pretty soon, when you have some simple maintenance to do, and you have no idea how, you start thread about having your device bricked. and im sure that you personally have not helped out hundreds that have started threads about having their device "bricked" after using a root toolkit. i have.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
you probably have to unzip it twice, if there is another zip within that one zip. and you can try not using the word fastboot, as i also have ran into fastboot programs where it wasnt needed.
Click to expand...
Click to collapse
Friend, I'm way too old to get into an internet pissing contest!!! I realize I don't have 27,000+ post, but if you look at my thanks total, you will see that I've helped my share of members!!!! So don't tell me that I dont try to share my knowledge......have a good day and please don't respond to any more of my post!!!! Peace out!!
Sent from my SM-T310 using XDA Premium 4 mobile app

dparrothead1 said:
Friend, I'm way too old to get into an internet pissing contest!!! I realize I don't have 27,000+ post, but if you look at my thanks total, you will see that I've helped my share of members!!!! So don't tell me that I dont try to share my knowledge......have a good day and please don't respond to any more of my post!!!! Peace out!!
Sent from my SM-T310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
with a silly post like "Different strokes for different folks!!!!" you definitely arent posting like someone your age, as thats what a child would say. im not young myself. anywho, you can not tell me not to respond, lol. ill respond to anyone who posts as silly as you. i have nothing against you, nor are trying to get at you, im simply responding to your silliness.

OP... The password was a numerical representation of your pattern unlock since you were still encrypted. The key is in the first post of the TWRP thread.
Now...extract the factory image until you have boot.img radio.img system.img and recovery.img if there is a bootloader img flash that first.
Flash bootloader with fastboot flash bootloader bootloader.img
Reboot with fastboot reboot-bootloader
Flash boot system and radio respectively with fastboot flash boot/radio/system boot.img/radio.img/system.img one at a time.
Finish with fastboot reboot and you sgould be all set.

op got it flashed, and ended up flashing his rom as well. so, he was successful

I hope saying use a toolkit didn't start an argument, only said to use it because he had a time restraint..

jiv101 said:
I hope saying use a toolkit didn't start an argument, only said to use it because he had a time restraint..
Click to expand...
Click to collapse
no, it didnt start an argument. but he ended up doing it the right way, then flashed his rom. then flashed a different rom because his rom was so so. but really, even if theres a time restraint, if your driver is installed properly, it takes about 3-4 minutes to flash the boot.img

Related

Problem when rooting Custom Rom

Hi guys!
I received my Nexus yesterday en immediately rooted and unlocked the device. No problems so far.
I want to install a the cyanogen custom rom on my nexus but get stuck in the recovery step.
I have used the tutorial from Theunlockr . com (unfortunately I cant insert a link here because Im a new member)
Because I already rooted and unlocked my Nexus I started with ''III. Flash the Custom ROM''. I managed to start up the bootloader and click on 'Recovery'. Here the problems start, after clicking on 'recovery' a screen with a yellow exclamation shows up. (see attachment for screenshot)
Can somebody help me with flashing my Nexus with a custom rom? Thanks in advance!
Try to run "fastboot boot recovery.img" and see if that works. (Something like that anyway)
This was what I did for all my time using Amon's 1.5.3 recovery. Now that I'm on 1.6.0, I can use the normal recovery. That worked perfectly for me anyway. I also would always boot to that screen when attempting the normal recovery via the phone.
Do you have small tutorial or how-to how I can run 'flashboot boot recovery.img'' on my Mac?
I am quite an android-noob.
Stinosss_31 said:
Do you have small tutorial or how-to how I can run 'flashboot boot recovery.img'' ?
I am quite an android-noob.
Click to expand...
Click to collapse
So am I
To run fastboot, you should simply go find the Android SDK download. Once you've downloaded that, make your way to the tools folder. Place the recovery image in that folder and then Shift+Right Click in the window. You click the option to bring up a command prompt.
In that Command prompt, type flashboot devices and verify the PC sees your phone. If so, then you can do the Flashboot command. Though you may need USB drivers. If you do need them, they're somewhere in this forum, but I've completely lost track of them.
P.S. if my initial command doesn't work... You might need to try "fastboot boot recovery recovery.img"
(Note... Don't try "Flashboot".. That was a typo )
Stinosss_31 said:
Do you have small tutorial or how-to how I can run 'flashboot boot recovery.img'' ?
I am quite an android-noob.
Click to expand...
Click to collapse
got this info from the same site you posted, you just skipped the step before you started to flash the rom altogether.
II. Flash a Custom Recovery Image
1. Download the Nexus One Amon Ra Recovery Image below:
Nexus One Recovery Image (Link under Download in the first Post)
2. Save the recovery image file inside the superboot folder you used to root the phone.
3. Turn the phone off and then plug it in via USB cable.
4. Turn it on by holding down Power and the Trackball to get into fastboot mode.
5. Open a command prompt and type the following with hitting enter at the end of each line:
cd\
cd c:\superboot
fastboot-windows devices
*this is to check that the computer can see the phone (a serial should pop up if it can)
6. Then type:
fastboot-windows flash recovery recovery-RA-nexus-v1.5.3.img
7. This should flash the recovery image onto the phone.
Click to expand...
Click to collapse
The recovery img is in this thread
http://forum.xda-developers.com/showthread.php?t=611829
Click to expand...
Click to collapse
Also, you don't really need the android sdk for flashing the recovery img, but it's a good idea to download it for future use.
Can ANYONE just stop answering threads that are in wrong sections?
lazinase said:
Can ANYONE just stop answering threads that are in wrong sections?
Click to expand...
Click to collapse
Why? So that it gets moved and answered anyway? The sooner the guy gets helped out... The sooner the post gets buried.
A mod will be by to do their duty later. As the community, we may as well help in the mean time.
Man, oh man. Niceness has really lost some popularity in the virtual world, hasn't it...
Stinosss_31 said:
Do you have small tutorial or how-to how I can run 'flashboot boot recovery.img'' on my Mac?
I am quite an android-noob.
Click to expand...
Click to collapse
If you use a Mac, you don't deserve help. Bootcamp Windows and we'll talk.
grainysand said:
If you use a Mac, you don't deserve help. Bootcamp Windows and we'll talk.
Click to expand...
Click to collapse
great help!
for a mac just use ./fastboot-mac in the terminal
Like they said, sounds like you are missing recovery. Just do the step two, you skipped it. Why flame people? He is new, might as well help, instead of making this thread longer by telling him to post in right section.
Besides, he did find tutorials and followed them, he didn't come here completely unprepared and expecting people to walk him through. We all make mistakes sometimes, specially when dealing with something we are new to, he simply skipped a step.
MOD EDIT - Thread moved to Q&A

[Q] Bricked phone?

I think I may have bricked my phone. It's a rooted htc hero cdma. I'm running cyogenmod on it and it was working fine, until using metamorph to apply some changes to the theme.
I went to reboot, and it now it won't load past the htc screen. Even when i try the key combination to put it into recover mode. I didn't install a nandroid backup, and i'd be fine with just completely wiping my phone. can someone please help me?
Have you tried flashing the ROM back over itself without wiping? Try that first, and if that won't work, do a full format and reflash the ROM and you should be good to go.
And just an FYI, you really can't fully brick your phone by flashing a ROM or theme. You can always get it back.
Do what ranger suggested.
To elaborate, I *think* as long as your phone turns on, it is not bricked. Specifically, as long as you can boot to recovery you can do whatever you need to do, be it make fixes or start from scratch again. (I think even if you can't boot to recovery, but it turns on, you can run the RUU ). The only way to brick is to flash a wrong/corrupt radio or anything below the radio level.
Wipe then reboot and wait. When you change the framework, initial boot takes longer.
Sent from my HERO200 using XDA Premium App
I can't even get to the recovery mode screen. it'll only take me to where i can select hboot, fastboot, or wipe. nothing else will load up past that.
What key combination are you using? Hold home then depress end key/power key until phone vibrates.
Sent from my HERO200 using XDA Premium App
Load the fast boot ruu flash
Done
zbach said:
I can't even get to the recovery mode screen. it'll only take me to where i can select hboot, fastboot, or wipe. nothing else will load up past that.
Click to expand...
Click to collapse
Sent from my HTC Hero CDMA using XDA App
mahalocat said:
Load the fast boot ruu flash
Done
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
I can't select that option. Sorry for being kind of new at this, it just loads a bunch of green letters down really quick, telling me it can't find HERCIMG.zip/HERCDIAG.zip files. under that, it says no image or wrong image?
zbach said:
I can't select that option. Sorry for being kind of new at this, it just loads a bunch of green letters down really quick, telling me it can't find HERCIMG.zip/HERCDIAG.zip files. under that, it says no image or wrong image?
Click to expand...
Click to collapse
I am guessing you're not s-off, try this:
http://forum.xda-developers.com/showthread.php?t=958968
il Duce said:
I am guessing you're not s-off, try this:
http://forum.xda-developers.com/showthread.php?t=958968
Click to expand...
Click to collapse
I don't see the command to run "fastboot oem rebootRUU"
zbach said:
I don't see the command to run "fastboot oem rebootRUU"
Click to expand...
Click to collapse
It's a cmd prompt for windows. Open your command prompt from windows, with the phone plugged in usb, and then follow the steps in the OP of that thread.
il Duce said:
It's a cmd prompt for windows. Open your command prompt from windows, with the phone plugged in usb, and then follow the steps in the OP of that thread.
Click to expand...
Click to collapse
it keeps telling me fastboot is an unrecognized command. i have to be doing something wrong here.
zbach said:
it keeps telling me fastboot is an unrecognized command. i have to be doing something wrong here.
Click to expand...
Click to collapse
did you do the adb command first, like it says?
il Duce said:
did you do the adb command first, like it says?
Click to expand...
Click to collapse
yeah, it won't recognize that either. i'm selecting the right path to my C drive too. the driver just isnt recognized :/
You have to go further than just the C drive you have to specify the path all the way to the android-sdk-windows directory. If your on Vista, find the folder, hold the shift key and right click. Then select open a command line here.
EDIT: Yeah you need the drivers installed as well.
I had this happen to me a week ago. Luckily the phone rebooted and I was able to re-flash another recovery using the terminal emulator.
wild1z said:
You have to go further than just the C drive you have to specify the path all the way to the android-sdk-windows directory. If your on Vista, find the folder, hold the shift key and right click. Then select open a command line here.
EDIT: Yeah you need the drivers installed as well.
I had this happen to me a week ago. Luckily the phone rebooted and I was able to re-flash another recovery using the terminal emulator.
Click to expand...
Click to collapse
okay, i'm in now. i'm on the rebootRUU black and silver screen on my phone, but when i go to flash another .zip file, it says can't upload. do i need to download one from somewhere, or place it in a different folder?
I'm on my computer working through my command prompt by the way.
zbach said:
okay, i'm in now. i'm on the rebootRUU black and silver screen on my phone, but when i go to flash another .zip file, it says can't upload. do i need to download one from somewhere, or place it in a different folder?
I'm on my computer working through my command prompt by the way.
Click to expand...
Click to collapse
I've never actually done this fyi, but I think you need the RUU from htc.com, it would probably be under support, then hero cdma? DL that, and input the command "fastboot flash zip correctnameofhtcRUU.zip" in your cmd.
okay, i found and am currently downloading the file. so i should just have to root it to my SD, then flash it, right?
I'm really hoping this works.
il Duce said:
I've never actually done this fyi, but I think you need the RUU from htc.com, it would probably be under support, then hero cdma? DL that, and input the command "fastboot flash zip correctnameofhtcRUU.zip" in your cmd.
Click to expand...
Click to collapse
still nothing. it only tells me its and error, and cannot load the .zip file.
zbach said:
still nothing. it only tells me its and error, and cannot load the .zip file.
Click to expand...
Click to collapse
I don't know where the file should be located, but your posts in the other thread will yield better answers, jason knows the way better than me, given he started the thread. Wait for his response. I assume the error has something to do with where you have the ruu and what path you need to specify in the cmd. Wish I could be of more help. Once you fix it and get back to rooted and such, I HIGHLY recommend you get s-off, its basically like idiot-proofing your phone (no offense) so you can fix anything.
sent from a series of tubes.

[Q] Cant browse root

My current situation.
Streak 7 boots after factory reset, asks for a password. there never was one. after numerous attempts i just decided to install another rom.
i have all the files etc and know how to flash it with clockwork, but i cant get it onto the internal sd. only the external. meaning clockwork cant detect it. im kinda stuck here....
I had this issue once, I wiped again from recovery, cache and dalvic as well and it cleared up. Also I use fastboot to install everything for roms.
Sent from a Hacked, Modded and customized Streak 7
sadly ive tried that repeatedly :L
Did you use fastboot to reinstall the system, boot, and recovery files? This or Nvflash will be your only way to get out of it then.
Sent from a Hacked, Modded and customized Streak 7
i could, if you have a solution to why it hangs at "starting fastboot usb download protocall"
and thanks for the help by the way. this has caused me too much stress lol
EDIT: And if you could help me with the fastboot commands afterwards that would be great. i know how to flash recovery and thats about it.
Its suppose to say that on your device.
Now plug it into the computer, install the fastboot drivers, grab a copy of fastboot.exe, and flash the images.
giveen said:
Its suppose to say that on your device.
Now plug it into the computer, install the fastboot drivers, grab a copy of fastboot.exe, and flash the images.
Click to expand...
Click to collapse
Giveen, I am trying to help fill in for those that have been around longer than those of us that are new. I have to agree with the new people that it is difficult to find the knowledge on this site sometimes and the list of commands that are needed to get going. I know I have spent many hours on google, XDA, TabletRoms and WIKI looking for answers. I do get that it is frustrating for you as a developer as well. Sit back and relax and some of us newer noobs will try to assist.
Sent from a Hacked, Modded and customized Streak 7
---------- Post added at 11:14 AM ---------- Previous post was at 11:09 AM ----------
Meanc20 said:
i could, if you have a solution to why it hangs at "starting fastboot usb download protocall"
and thanks for the help by the way. this has caused me too much stress lol
EDIT: And if you could help me with the fastboot commands afterwards that would be great. i know how to flash recovery and thats about it.
Click to expand...
Click to collapse
You need to do more reading here, yea I know it's hard to find info sometimes. Google every way you can think of for your problem and an answer will be found. You don't have a brick yet but you need to know what your doing before diving into this stuff. I spent a week researching before I dived into this just to make sure I knew what I was doing. YouTube video search, flashing Dell streak 7, at least I think that is close enough. It is a for part series on how to flash a custom ROM from Nvflash but you need to read and find the fastboot commands and drivers. They are here.
Sent from a Hacked, Modded and customized Streak 7
i have everything ready but fastboot commands dont work because the device is still stuck "starting the protocall"
i have the correct drivers etc installed but still nothing
Meanc20 said:
i have everything ready but fastboot commands dont work because the device is still stuck "starting the protocall"
i have the correct drivers etc installed but still nothing
Click to expand...
Click to collapse
That's what it's supposed to show till commands are sent from your PC. Do you have "still" have a yellow "?" mark in your device manager?
A quick function test is to type: fastboot reboot and your S7 should reboot.
And this is why I plan on making a fastboot video.

[Q] Flash back to Stock

Hi guys, I'll just start things off with saying that I am far from being anywhere near as technologically advanced as the majority of you so I would like your help if possible.
I had wanted to flash back to Stock and unroot my Moto X but for some reason I had gone into TWRP and decided to delete everything. Now every time I try to reboot from TWRP, it'll just say that the phone does not have an OS Installed and therefore if I reboot it, it will just stay on the 'Warning Bootloader Unlocked" screen.
I've read quite a few threads on various forums but I am unable to get my laptop to recognise the device in fastboot. That's my only problem so far as I've downloaded the Motorola Device Manager and all those other things but still cannot get my laptop to show the device for me to put the files into. When I plug it in, I am able to hear the sound and the device recognizes that it's been plugged in but I can't see it on my laptop.
Any and all help is GREATLY appreciated. Thanks guys and forgive my ignorance.
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
Hi guys, I'll just start things off with saying that I am far from being anywhere near as technologically advanced as the majority of you so I would like your help if possible.
I had wanted to flash back to Stock and unroot my Moto X but for some reason I had gone into TWRP and decided to delete everything. Now every time I try to reboot from TWRP, it'll just say that the phone does not have an OS Installed and therefore if I reboot it, it will just stay on the 'Warning Bootloader Unlocked" screen.
I've read quite a few threads on various forums but I am unable to get my laptop to recognise the device in fastboot. That's my only problem so far as I've downloaded the Motorola Device Manager and all those other things but still cannot get my laptop to show the device for me to put the files into. When I plug it in, I am able to hear the sound and the device recognizes that it's been plugged in but I can't see it on my laptop.
Any and all help is GREATLY appreciated. Thanks guys and forgive my ignorance.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
You don't put files on the phone and you don't use twrp. Follow the instructions in the return to 100% stock thread.
samwathegreat said:
You don't put files on the phone and you don't use twrp. Follow the instructions in the return to 100% stock thread.
Click to expand...
Click to collapse
I've tried following the steps but I was unsure of step 3 where it says to download and install the proper firmware for the device but still unsure on how to install it. RSD Lite won't pick up the device nor will it show up when I type 'adb devices' in CMD. And finally, how do I go about turning on USB debugging when it won't boot up past the bootloader unlock screen?
Appreciate the help
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
I've tried following the steps but I was unsure of step 3 where it says to download and install the proper firmware for the device but still unsure on how to install it. RSD Lite won't pick up the device nor will it show up when I type 'adb devices' in CMD. And finally, how do I go about turning on USB debugging when it won't boot up past the bootloader unlock screen?
Appreciate the help
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Turn the phone off. Unplug it. Hold down VOL DOWN, and press power. The phone will boot into the bootloader. This is how you flash with rsd lite.
Adb does not work in bootloader, and isn't used for this. Once in bootloader (ap fastboot mode), rsd lite should recognize the device.
Make absolutely sure you do not downgrade to a previous version (you will brick), and make sure you flash the correct firmware for YOUR device/carrier.
You can only flash the same version or higher than what you were on before you erased everything.
samwathegreat said:
Turn the phone off. Unplug it. Hold down VOL DOWN, and press power. The phone will boot into the bootloader. This is how you flash with rsd lite.
Adb does not work in bootloader, and isn't used for this. Once in bootloader (ap fastboot mode), rsd lite should recognize the device.
Make absolutely sure you do not downgrade to a previous version (you will brick), and make sure you flash the correct firmware for YOUR device/carrier.
You can only flash the same version or higher than what you were on before you erased everything.
Click to expand...
Click to collapse
Thanks for the help! Unfortunately RSD Lite doesn't recognise the device in bootloader. Am I supposed to put the files into a certain place for things to start working properly and is it also because I'm using windows 8.1? I've already installed the Motorola Device Manager as well.
Really sorry for all the questions - complete newbie right here
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
Thanks for the help! Unfortunately RSD Lite doesn't recognise the device in bootloader. Am I supposed to put the files into a certain place for things to start working properly and is it also because I'm using windows 8.1? I've already installed the Motorola Device Manager as well.
Really sorry for all the questions - complete newbie right here
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
You said you downloaded moto device manager... Did you install it? If so you are one of the unlucky ones and will have to use the manual method with fastboot and mfastboot. Take it slow and follow the instructions. Leave out the config carrier line.
To make sure fastboot is working, type fastboot devices while in bootloader mode.
samwathegreat said:
You said you downloaded moto device manager... Did you install it? If so you are one of the unlucky ones and will have to use the manual method with fastboot and mfastboot. Take it slow and follow the instructions. Leave out the config carrier line.
To make sure fastboot is working, type fastboot devices while in bootloader mode.
Click to expand...
Click to collapse
Oh okay that makes sense. Yeah I had installed but still nothing. Okay, I'll try the manual method, thanks heaps!
I've typed it fastboot devices in CMD and it came up with T017500PDP fastboot. I assume that's good? Haha
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
Oh okay that makes sense. Yeah I had installed but still nothing. Okay, I'll try the manual method, thanks heaps!
I've typed it fastboot devices in CMD and it came up with T017500PDP fastboot. I assume that's good? Haha
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Yes perfect.
Run one command at a time - copy/paste them.
Remember to use mfastboot for system.img - regular fastboot will NOT work. Also remember to skip the config carrier command.
samwathegreat said:
Yes perfect.
Run one command at a time - copy/paste them.
Remember to use mfastboot for system.img - regular fastboot will NOT work. Also remember to skip the config carrier command.
Click to expand...
Click to collapse
You my friend are a legend. Last round (hopefully) of questions though: where the code says to type in fastboot flash .... .gpt.bin and all those other things, am I supposed to put the files somewhere in particular? Because just regularly typing them into CMD comes up with (bootloader) Variable not supported! Then error: cannot open 'gtp.bin' or cannot open 'recovery.img' and so on but on the phone it says getvar partition-type:recovery or boot and so on.
Also the when the instructions say to use mfastboot, CMD says that it is not recognized as an internal or external command. Thanks!
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
You my friend are a legend. Last round (hopefully) of questions though: where the code says to type in fastboot flash .... .gpt.bin and all those other things, am I supposed to put the files somewhere in particular? Because just regularly typing them into CMD comes up with (bootloader) Variable not supported! Then error: cannot open 'gtp.bin' or cannot open 'recovery.img' and so on but on the phone it says getvar partition-type:recovery or boot and so on.
Also the when the instructions say to use mfastboot, CMD says that it is not recognized as an internal or external command. Thanks!
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
First: yes, you have to put those files in the same folder as you are running the commands from. If your command prompt shows C:\users\jimmy\
Then that is where the files should be! You should have extracted the zip file you downloaded to the same folder you are running the commands from.
Second, you obviously have not download mfastboot.exe (it is linked in the return to stock thread) OR you didn't put it in the same folder as the rest of the files.
The "variable not supported" messages are normal. The error cannot open.... errors are NOT.
I'm attaching mfastboot.exe (it's zipped - extract it to the same folder as everything else) to this post so you don't have to go looking for it.
DON'T move on if the first command doesn't work. Make sure each one gives success before you move on.
Awesome!
samwathegreat said:
First: yes, you have to put those files in the same folder as you are running the commands from. If your command prompt shows C:\users\jimmy\
Then that is where the files should be! You should have extracted the zip file you downloaded to the same folder you are running the commands from.
Second, you obviously have not download mfastboot.exe (it is linked in the return to stock thread) OR you didn't put it in the same folder as the rest of the files.
The "variable not supported" messages are normal. The error cannot open.... errors are NOT.
I'm attaching mfastboot.exe (it's zipped - extract it to the same folder as everything else) to this post so you don't have to go looking for it.
DON'T move on if the first command doesn't work. Make sure each one gives success before you move on.
Click to expand...
Click to collapse
Thanks so much, it worked great! The colours are a bit out of wack though (the blues are now orange and so on) and the bot animation is messed but still better than nothing. Thanks so much for your help!
boss. said:
Thanks so much, it worked great! The colours are a bit out of wack though (the blues are now orange and so on) and the bot animation is messed but still better than nothing. Thanks so much for your help!
Click to expand...
Click to collapse
You're welcome....but that isn't normal. I suggest doing it again from the beginning. A full SBF to stock re-writes all the partitions and there shouldn't be anything "out of wack". Sounds like something went wrong....OR your device has physical damage?
Anyways, please consider hitting the "THANKS" button under any and all posts that help you. :good:
samwathegreat said:
You're welcome....but that isn't normal. I suggest doing it again from the beginning. A full SBF to stock re-writes all the partitions and there shouldn't be anything "out of wack". Sounds like something went wrong....OR your device has physical damage?
Anyways, please consider hitting the "THANKS" button under any and all posts that help you. :good:
Click to expand...
Click to collapse
Re-did the whole thing from scratch again and now all problems are solved. Really appreciate the help my friend!
Sent from my SM-N9005 using XDA Free mobile app

Deleted the whole os

I recently formatted everything on my nexus 6 and I mean everything, the OS too. And I can't fix it, there was nothing on the forums or threads about this and how to fix it. Could you please help me?
Boot into the boatloader and flash the fastboot image.
Sent from my DROID Turbo 2
I have Ben an apple guy for 5 years just bought the nexus, I know how to get in to the boot loader but how do I flash the image? I tried downloading the image from the Google developers website but it said it failed ins
talling it!
Big-Blunt said:
I have Ben an apple guy for 5 years just bought the nexus, I know how to get in to the boot loader but how do I flash the image? I tried downloading the image from the Google developers website but it said it failed ins
talling it!
Click to expand...
Click to collapse
you cant use the flash-all, you need to flash each part separately. ynzip the file, then flash each .img file sepately. btw, ive deleted the whole os before. if you already have twrp installed, it wouls be a much easier fix using twrp instead.
How do I unzip the file in the boot loader?
Big-Blunt said:
How do I unzip the file in the boot loader?
Click to expand...
Click to collapse
i dont remember the program i used on my laptop, maybe 7zip.
The file downloaded from Google has a second zip inside. Unzip twice with 7 zip. The system image is inside the embedded zip file.
I assume you have the SDK from Google... Place all image files in the platform tools folder. I rename the images boot, radio, system, etc. to simplify typing the commands when actually flashing the images. DO NOT add the, " .IMG" when renaming.
Then:
Fastboot flash bootloader bootloader.IMG
Fastboot reboot-boitloader
Then same for system, radio, data and cache with out the reboot line.
When all files are flashed then fastboot reboot and enjoy
My brains are exploding rn, idk what or how to do anything, maybe u will think I'm dumb but I don't know what u guys are saying, could anyone post full instructions on how I would do it
The ONLY thing that you need to revive your device is alive bootloader. Every OS has its bootloader, and it determines what to load before system loaded.
I guess you did that foolish things on recovery. Then it won't kill itself of bootloader for sure.
Then there's always a chance. Try to boot into bootloader and switch it to fastboot mode.
Just flash stock rom image provided by google as described above.
You need to do some googling about fastboot and/or look for the beginners guide posted in the forums. You could use wugsfresh toolkit as well. I'm not being a douche not linking them,I'm to stoned
Google anything you don't understand
Sent from my Nexus 6 using Tapatalk
Do you know if your bootloader is unlocked?
You say you're an Apple guy - are you using a Mac? If you have access to a Windows machine I suggest you install Wugfresh's Nexus Root Toolkit and use the "Install & test drivers" button to set up the required drivers to connect your Nexus 6 to the computer. The walkthrough is comprehensive and extraordinarily simple - brilliant piece of programming. There is no Mac version.
Download the factory image (https://developers.google.com/android/nexus/images?hl=en#shamu image MMB29K).
Find the Fastboot/ADB programs on the web (I may have used the Minimal ADB & Fastboot tool, I can't remember exactly) and create a directory containing both programs plus their associated bits and pieces. I recommend making the path as simple as possible - e.g. C:\ADB for ease of navigation ( see below).
(While reading up on this, I came across this, which you may find useful - http://www.android.gs/install-set-up-adb-mac-os-x-linux/).
Unzip everything in the factory image, including the zip inside the zip as Larzzzz82 said, then copy the unzipped *.img files into the ADB Fastboot directory.
Boot your N6 into bootloader.
Open a CMD window and navigate to the ADB directory.
To check that you're connected, type (you don't need caps, this is just to make it clearer) FASTBOOT DEVICES. You should see something like "djdgkdjhgkdfj device" in response; if it's blank you're not connected - go through the driver setup again to see what you've missed.
Once you're successfully connected, you can install your new image following the instructions in this thread:
http://forum.xda-developers.com/google-nexus-5/help/stuck-launching-flashstock-bat-t3244470
I did ask for an expert to run a more experienced eye over them to correct any errors or to remove any pointless reboot commands, but nobody did either, so I guess they're ok. It's what I did and it worked for me. I've just noticed that it includes a line "fastboot flash recovery twrp.img" which you can ignore for the moment - though you may want to do this later when you have a working device.
Come back if you want any clarifications.
Happy new year (and, I hope, device...)
I tried I guess flashing the image through the recovery mode in the mount section but it said it failed,
Big-Blunt said:
I tried I guess flashing the image through the recovery mode in the mount section but it said it failed,
Click to expand...
Click to collapse
No no no you do not flash images through the recovery
Use Wugfresh's Nexus root and toolkit to restore it. Pretty easy.
@wolfen69 - duck and take cover...
I was going to suggest exactly that, since I'm a big fan of Wugfresh's NRT, but recommending it doesn't half bring down the flak... that's why I recommended using it initially at least to get the PC set up properly to connect and then get on with learning how to do it manually.
Personally in this situation using the NRT is exactly what I'd do myself. But now I'm retiring to my bunker for a while.
dahawthorne said:
@wolfen69 - duck and take cover...
I was going to suggest exactly that, since I'm a big fan of Wugfresh's NRT, but recommending it doesn't half bring down the flak... that's why I recommended using it initially at least to get the PC set up properly to connect and then get on with learning how to do it manually.
Personally in this situation using the NRT is exactly what I'd do myself. But now I'm retiring to my bunker for a while.
Click to expand...
Click to collapse
That's OK if people disagree with my recommendation. People are entitled to their opinions.
I tried for hours to do it the manual way and could never get it to work. And I'm a person who is VERY tech savvy. I had a computer repair business and have written advanced linux tutorials. I gave up and started using wugfresh. Has worked great for me. Others are free to do what works for them.
If you dont flash the images through the recovery mode then how do you flash it? I cant flash through command because the phone dosent have usb debugging enabled and its not in developer mode. I tried the nexus root toolkit as well and that didnt work either. Plz i need help!
So how much of my instruction did you follow? What exactly have you tried? Step by step. If you're vague then we can't help you. Error messages?
How did you delete the OS if your phone isn't unlocked?
Sent from my DROID Turbo 2
So i put it in recovery mode and when i tried resetting to factory i accidentally clicked advanced wipe and deleted everything so now its stuck in the boot loop. What i have tried was i downloaded the img file 6.0 shamu from googles site and drag and dropped on internal memory with my pc. Then in recovery mode i went mount and selected the img and it said error.

Categories

Resources