Database Develop

Urgent: Help, brick my phone

I need help, fast. im freaking out.
ok so, i needed to unroot my phone so i could send it in to get it replaced.well i went to unroot, i had the proper flash files and drivers and everything wugfresh said needed. but i forgot to make a recovery file, mostly cuz it told me i didnt have enough space on my phone, anyways thinking it went fine, i decided to lock the bootloader, and then it started to bootloop TWRP, so trying the unroot thing again, that didnt work, so i tried to unlock bootloader again, that didnt work. So in a moment of panic and stupidity i tried reinstalling everything using the guide that it had, but it wouldnt install anything. It's still in bootloop and idk what to do. have i screwed up? i dont have money for a new phone or another phone to use. any help would be great..
thanks in advance..

1. Don't use toolkits unless you can replicate everything they do (or everything you plan to use them for) on the the command line. They are for convenience, not for doing something you don't know how to do.
2. Try to unlock the bootloader again...but...
3. There is no need to unroot a nexus to send it in for a hardware defect. Just factory reset, take your sim out and ship. Just ship it.

brizey said:
1. Don't use toolkits unless you can replicate everything they do (or everything you plan to use them for) on the the command line. They are for convenience, not for doing something you don't know how to do.
2. Try to unlock the bootloader again...but...
3. There is no need to unroot a nexus to send it in for a hardware defect. Just factory reset, take your sim out and ship. Just ship it.
Click to expand...
Click to collapse
:victory:
---------- Post added at 11:07 PM ---------- Previous post was at 11:05 PM ----------
undeadfreak said:
I need help, fast. im freaking out.
ok so, i needed to unroot my phone so i could send it in to get it replaced.well i went to unroot, i had the proper flash files and drivers and everything wugfresh said needed. but i forgot to make a recovery file, mostly cuz it told me i didnt have enough space on my phone, anyways thinking it went fine, i decided to lock the bootloader, and then it started to bootloop TWRP, so trying the unroot thing again, that didnt work, so i tried to unlock bootloader again, that didnt work. So in a moment of panic and stupidity i tried reinstalling everything using the guide that it had, but it wouldnt install anything. It's still in bootloop and idk what to do. have i screwed up? i dont have money for a new phone or another phone to use. any help would be great..
thanks in advance..
Click to expand...
Click to collapse
you can try fastboot formatting userdata and cache, but that generally only works if you still have twrp installed. other than that, theres really nothing else that you can do.

brizey said:
3. There is no need to unroot a nexus to send it in for a hardware defect. Just factory reset, take your sim out and ship. Just ship it.
Click to expand...
Click to collapse
When I had to get mine replaced Sprint gave me crap cause I had bootloader unlocked and twrp installed. I had to take it home flash factory images and relock before they would take it back (for a sim slot issue) always best to go stock to avoid any issues.
Sent from my Nexus 6 using XDA Free mobile app

undeadfreak said:
I need help, fast. im freaking out.
ok so, i needed to unroot my phone so i could send it in to get it replaced.well i went to unroot, i had the proper flash files and drivers and everything wugfresh said needed. but i forgot to make a recovery file, mostly cuz it told me i didnt have enough space on my phone, anyways thinking it went fine, i decided to lock the bootloader, and then it started to bootloop TWRP, so trying the unroot thing again, that didnt work, so i tried to unlock bootloader again, that didnt work. So in a moment of panic and stupidity i tried reinstalling everything using the guide that it had, but it wouldnt install anything. It's still in bootloop and idk what to do. have i screwed up? i dont have money for a new phone or another phone to use. any help would be great..
thanks in advance..
Click to expand...
Click to collapse
If you cannot unlock the bootloader, fastboot format userdata and cache. Boot into TWRP and copy any rom.zip to the sdcard using MTP.
Flash the rom, tick the "allow oem unlock"
Boot to bootloader, unlock it. Flash stock CHECK IT BOOTS before you lock the BL.

New 28k T-Mobile images not flashing

Anyone else having issues getting the new T-Mobile 28k update to work? I have downloaded it from the official Google images site. When I try to flash through nrt it will not boot after its flashed just sits at goolge on the device. I've also tried flashing each file individually through fastboot and still same issue. It's like there isn't a system image being flashed even though I flashed one.. Any suggestions? I'm puzzled
Sent from my Nexus 6 using XDA Free mobile app

I don't use the NRT, so can't comment on it.
When flashing using fastboot, what images did you flash? And were all successful? (If you flashed bootloader and/or radio, did you reboot bootloader after each of those?)
Did you flash cache.img? If not, flash the cache.img and see if that helps

beachbum40 said:
Anyone else having issues getting the new T-Mobile 28k update to work? I have downloaded it from the official Google images site. When I try to flash through nrt it will not boot after its flashed just sits at goolge on the device. I've also tried flashing each file individually through fastboot and still same issue. It's like there isn't a system image being flashed even though I flashed one.. Any suggestions? I'm puzzled
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I just finished flashing my phone to 28K with NRT. I was on 48M, unlocked it and flashed it to 28J and then flashed it to 28K using the image dowloaded from Google. I had the Force Flash option checked.

Sound more like you have a corrupted boot.img since it looping at the splash. Try fastboot a boot.img from a new or custom download. Have seen images corrupted on download.

jj14 said:
I don't use the NRT, so can't comment on it.
When flashing using fastboot, what images did you flash? And were all successful? (If you flashed bootloader and/or radio, did you reboot bootloader after each of those?)
Did you flash cache.img? If not, flash the cache.img and see if that helps
Click to expand...
Click to collapse
Yea I finally got it I don't know what is going on I used fastboot adb and manually flashed about 30 times and still bootloop. I gave up on nrt. I like the tool for time saving but like I said it refused to flash with nrt and manual fastboot then all the sudden it worked. I downloaded the 28K factory images about 30 times as well. If it was corrupted it just finally decided to work. I've never had an issue like this in the past.
Sent from my Nexus 6 using XDA Free mobile app

prdog1 said:
Sound more like you have a corrupted boot.img since it looping at the splash. Try fastboot a boot.img from a new or custom download. Have seen images corrupted on download.
Click to expand...
Click to collapse
Don't want to sound to ignorant but could you explain to me how these boot.img get corrupted? I'm sure that's what it was because when NRT was checking the images and it said to verify the hash mdn and I copied the mdn from Google's official site and pasted it in the dialog box on nrt it said match the first time when I tried to flashed 28K then it failed. Then I tried again and put the same mdn in the dialog box and nrt said mismatch. So I'm confused as hell.
Sent from my Nexus 6 using XDA Free mobile app

beachbum40 said:
Don't want to sound to ignorant but could you explain to me how these boot.img get corrupted? I'm sure that's what it was because when NRT was checking the images and it said to verify the hash mdn and I copied the mdn from Google's official site and pasted it in the dialog box on nrt it said match the first time when I tried to flashed 28K then it failed. Then I tried again and put the same mdn in the dialog box and nrt said mismatch. So I'm confused as hell.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Usually when get a bad download you can't unzip it. When they put these images inside the zip the zip is good but don't mean the image is good. That is why they give you an MD5 with the download. Under normal conditions such as rom download can pretty much tell if download is bad cause can't access the file with 7zip ect. It is different with the zipped images. Any one image can be corrupt. but zip is good. I have had downloads with either/or/and system.img or boot.img was bad and all the others worked. Hope this makes sense. Lol
---------- Post added at 12:07 AM ---------- Previous post was at 12:00 AM ----------
Skip the toolkits till understand how it works with manual fastboot. Will save a lot of head banging when you need to fastboot fix a toolkit fail. I have used toolkit to play with it. Had many fails and used fastboot to fix. If using toolkit never pick the lock bootloader option. Good way to brick the device.

prdog1 said:
Skip the toolkits till understand how it works with manual fastboot.
Click to expand...
Click to collapse
Allow me to add an argument.
Manual fastboot requires command line input and the 'speed' is controlled by yourself.
Toolkits use scripts and you won't be fast enough to stop when you choose the wrong option.

NLBeev said:
Allow me to add an argument.
Manual fastboot requires command line input and the 'speed' is controlled by yourself.
Toolkits use scripts and you won't be fast enough to stop when you choose the wrong option.
Click to expand...
Click to collapse
I only use tool kit as a time saver I do know my way around adb / fastboot. Thanks
Sent from my Nexus 6 using XDA Free mobile app

NLBeev said:
Allow me to add an argument.
Manual fastboot requires command line input and the 'speed' is controlled by yourself.
Toolkits use scripts and you won't be fast enough to stop when you choose the wrong option.
Click to expand...
Click to collapse
I use adb fastboot and have manually installed plenty times. Tool kits are convenience
Sent from my Nexus 6 using XDA Free mobile app

beachbum40 said:
I only use tool kit as a time saver I do know my way around adb / fastboot. Thanks
Click to expand...
Click to collapse
Same here. Nice to meet you.

beachbum40 said:
I only use tool kit as a time saver I do know my way around adb / fastboot. Thanks
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
timesaver toolkits are not, as things are quicker when done the right way. for example, it takes about 3 minutes to root your phone, if done the right way.

i tend to disagree on this one.
if the tool is made properly, all its doing is automating the commands and steps you would be using manually.
its not like its using a whole different method.
the tool could actually be better to use, if made properly, with Mfastboot. most users would use standard fastboot, instead of moto's fastboot, Mfastboot.

beachbum40 said:
I use adb fastboot and have manually installed plenty times. Tool kits are convenience
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Adb and fastboot are two completely different tools.
bweN diorD said:
i tend to disagree on this one.
if the tool is made properly, all its doing is automating the commands and steps you would be using manually.
its not like its using a whole different method.
the tool could actually be better to use, if made properly, with Mfastboot. most users would use standard fastboot, instead of moto's fastboot, Mfastboot.
Click to expand...
Click to collapse
Our point is using tool kits doesn't help the learning process. We mostly believe that people should use fastboot manually to ensure they have a good set up and get accustomed to the commands.. This way, when they get in trouble and we have to help fix it, we don't have to teach them to use fastboot and set up their computer, we can go straight to helping resolve whatever actual issue they have - because tool kits cannot always help them.

danarama said:
Adb and fastboot are two completely different tools.
Our point is using tool kits does help the learning process. We mostly believe that people should use fastboot manually to ensure they have a good set up and get accustomed to the commands.. This way, when they get in trouble and we have to help fix it, we don't have to teach them to use fastboot and set up their computer, we can go straight to helping resolve whatever actual issue they have - because tool kits cannot always help them.
Click to expand...
Click to collapse
All I was saying is I use both toolkit and fastboot. That's all. Thank you have a nice day?
Sent from my Nexus 6 using XDA Free mobile app

beachbum40 said:
All I was saying is I use both toolkit and fastboot. That's all. Thank you have a nice day?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I was just correcting you when you said "adb fastboot" as if it was one thing, not two unrelated things.

danarama said:
Adb and fastboot are two completely different tools.
Our point is using tool kits does help the learning process. We mostly believe that people should use fastboot manually to ensure they have a good set up and get accustomed to the commands.. This way, when they get in trouble and we have to help fix it, we don't have to teach them to use fastboot and set up their computer, we can go straight to helping resolve whatever actual issue they have - because tool kits cannot always help them.
Click to expand...
Click to collapse
i should have quoted simms last post.
i dont disagree with what you are saying, but do with the inference that toolkits use some inferior method, which isnt the case.

danarama said:
Adb and fastboot are two completely different tools.
Our point is using tool kits does help the learning process. We mostly believe that people should use fastboot manually to ensure they have a good set up and get accustomed to the commands.. This way, when they get in trouble and we have to help fix it, we don't have to teach them to use fastboot and set up their computer, we can go straight to helping resolve whatever actual issue they have - because tool kits cannot always help them.
Click to expand...
Click to collapse
your first line. toolkits does help the learning process. with that i disagree 1000000%. why? because the tool kits dont go through and explain each process to the user. they tend not to explain anything actually.
---------- Post added at 03:47 PM ---------- Previous post was at 03:42 PM ----------
ok, toolkits.. they do work usually(every once in a while they do mess up). problem is with new users. toolkits dont teach them anything, not even basics, in case they mess up(and they do). by going through the rooting process the first time, properly, instead of toolkit, the user gets to learn the basics of every android process. by knowing thise basics, the yser can fix 99.99% of issues that pop up. with a toolkit, you dont get to learn the basics. so i tell everyone that toolkits are fine, just do thd rooting one time manually, then use the toolkit whenever you want after that.

simms22 said:
your first line. toolkits does help the learning process. with that i disagree 1000000%. why? because the tool kits dont go through and explain each process to the user. they tend not to explain anything actually.
---------- Post added at 03:47 PM ---------- Previous post was at 03:42 PM ----------
ok, toolkits.. they do work usually(every once in a while they do mess up). problem is with new users. toolkits dont teach them anything, not even basics, in case they mess up(and they do). by going through the rooting process the first time, properly, instead of toolkit, the user gets to learn the basics of every android process. by knowing thise basics, the yser can fix 99.99% of issues that pop up. with a toolkit, you dont get to learn the basics. so i tell everyone that toolkits are fine, just do thd rooting one time manually, then use the toolkit whenever you want after that.
Click to expand...
Click to collapse
problem is, as long as there is a toolkit, 99% of people wont listen to you and will use the toolkit. there simply lazy and will never really appreciate any mods they do, because they did nothing more than click a few buttons...

bweN diorD said:
problem is, as long as there is a toolkit, 99% of people wont listen to you and will use the toolkit. there simply lazy and will never really appreciate any mods they do, because they did nothing more than click a few buttons...
Click to expand...
Click to collapse
thats ok, as long as at least one person listens then im not wasting my time. and i know that at the very least that at least one person has listened to my advice
the other 99%, some will think that their phone is bricked, some will go back and learn, some will be successfull with toolkits. and some just wont ever learn a thing

Bricked Nexus 6

Hi guys -
I'm somewhat a newbie here. I think I have bricked my Nexus 6. I had root and an unlocked bootloader. I had Chroma riom installed and was trying to go back to stock rom, unrooted with locked bootloader and through TWRP i deleted everything, including the OS I believe. So now my phone is locked on the Google startup screen (unlocked bootloader) . Suggestions?
Thanks -
John

if your bootloader is unlocked you should be able to fastboot clear cache and user data , then flash a rom from twrp. I would refrain from ever locking the bootloader back up since the update where you have to enable unlock bootloader in Dev Options.

droidstyle said:
if your bootloader is unlocked you should be able to fastboot clear cache and user data , then flash a rom from twrp. I would refrain from ever locking the bootloader back up since the update where you have to enable unlock bootloader in Dev Options.
Click to expand...
Click to collapse
me too I'm have Nexus 6 5.1.1 no recovery...except the bootloader that's locked Code: 2 , i can't unlock it, any solution !!?

hadifreestyler said:
me too I'm have Nexus 6 5.1.1 no recovery...except the bootloader that's locked Code: 2 , i can't unlock it, any solution !!?
Click to expand...
Click to collapse
no you are bricked unfortunately. the unlock bootlader option in dev options really seems to have caused more issues then good.
I am wondering if Jtag will fix these devices?

jpl81905 said:
Suggestions?
Click to expand...
Click to collapse
Stop.
Read.
A lot.
You have an unlocked nexus with custom recovery installed, and you don't know what to do? You shouldn't be messing with this stuff. You lack VERY basic understanding. Read the stickies.
https://developers.google.com/android/nexus/images?hl=en
Factory images. Follow their directions.

scryan said:
Stop.
Read.
A lot.
You have an unlocked nexus with custom recovery installed, and you don't know what to do? You shouldn't be messing with this stuff. You lack VERY basic understanding. Read the stickies.
https://developers.google.com/android/nexus/images?hl=en
Factory images. Follow their directions.
Click to expand...
Click to collapse
Thank you. I think.

jpl81905 said:
Hi guys -
I'm somewhat a newbie here. I think I have bricked my Nexus 6. I had root and an unlocked bootloader. I had Chroma riom installed and was trying to go back to stock rom, unrooted with locked bootloader and through TWRP i deleted everything, including the OS I believe. So now my phone is locked on the Google startup screen (unlocked bootloader) . Suggestions?
Thanks -
John
Click to expand...
Click to collapse
The easiest way if you are not familiar with ADB is to download the nexus tool kit located on these forums from WUGFRESH. That tool will walk you through a step by step process on how to flash stock back. You are far from bricked. I have deleted my entire phone many a times and just re flashed stock back easily. As long as your boot loader is unlocked you are fine
Link to toolkit: http://www.wugfresh.com/nrt/
The option you are going to want to use is on the front of the toolkit called flash stock + un-root. You can watch some videos on his website as well for flashing stock. That is all you need to do .
Any questions let me know, send me a PM

backdown00 said:
The easiest way if you are not familiar with ADB is to download the nexus tool kit located on these forums from WUGFRESH. That tool will walk you through a step by step process on how to flash stock back. You are far from bricked. I have deleted my entire phone many a times and just re flashed stock back easily. As long as your boot loader is unlocked you are fine
Link to toolkit: http://www.wugfresh.com/nrt/
The option you are going to want to use is on the front of the toolkit called flash stock + un-root. You can watch some videos on his website as well for flashing stock. That is all you need to do .
Any questions let me know, send me a PM
Click to expand...
Click to collapse
It is not the easiest option. The easiest option is plug the USB cable in, boot to TWRP, enable MTP mode and copy a rom to the sdcard.
Also, many senior members here will discourage the use of toolkits for those who are not familiar with adb or fastboot. It is best to learn these and use them at least once before starting to use toolkits. Toolkits do not "walk you through". They take you through without explaining anything.

danarama said:
It is not the easiest option. The easiest option is plug the USB cable in, boot to TWRP, enable MTP mode and copy a rom to the sdcard.
Also, many senior members here will discourage the use of toolkits for those who are not familiar with adb or fastboot. It is best to learn these and use them at least once before starting to use toolkits. Toolkits do not "walk you through". They take you through without explaining anything.
Click to expand...
Click to collapse
In a perfect world, I am sure we would all love to dive in and discover everything and be experts in all fields as time would not be a factor. I do not disagree it is helpful to learn ADB and fastboot commands and understand what they do. At this point in time though, the end goal here is to get his phone back up and running as fast as possible and then he can do the post-mortem to figure out what he did wrong and how to fix it .
I am guessing hes not very familiar with TWRP since he wound up in this situation. The toolkit alleviates the need for knowledge and gets the job done. I'm sure after this, the OP will research how to use his phone before trying to do anything next.

backdown00 said:
In a perfect world, I am sure we would all love to dive in and discover everything and be experts in all fields as time would not be a factor. I do not disagree it is helpful to learn ADB and fastboot commands and understand what they do. At this point in time though, the end goal here is to get his phone back up and running as fast as possible and then he can do the post-mortem to figure out what he did wrong and how to fix it .
I am guessing hes not very familiar with TWRP since he wound up in this situation. The toolkit alleviates the need for knowledge and gets the job done. I'm sure after this, the OP will research how to use his phone before trying to do anything next.
Click to expand...
Click to collapse
..but even so, your method is overkill. It is really simple to boot into TWRP and look in the menu for the "Enable MTP" option. Once that is done, the phone appears in "Computer" as an MTP device, just like when you boot into android. Then, simply dragging and dropping a ROM onto that device then flashing it via recovery will get him back up and running. There is nothing simpler or quicker than this.
Sorry, I do not intend to be confrontational here.

Nexus 6 bootloop when updating to android 5.1

Hey everyone I'm looking here as my last resort before sending my phone back to Motorola.
Bought a Nexus 6 from motorola uk which was delivered yesterday, switched phone on and all the Google apps on the phone updated, then had a notification OTA to download and install android 5.1 which I did, towards the end of the install process I had an error with the green android and a red exclamation mark.
I powered the device off with the power button and it turned back on and ever since it says "Android is starting" "Optimizing app 1 of 125" once it goes through all the apps it gets to the android boot screen then just goes back to the "Android is starting" "Optimizing app 1 of 125" over and over and over. (Infinite bootloop)
Pointers: The phone is not unlocked or rooted as I'm a noob its just fresh out the box, also I never opened/unlocked the developer options.
I have tried various recovery mode fixes, wiping cache and wiping all data and then rebooting the device with no luck.
Is there anyway I can hook my N6 up to my computer and fix this with a tool kit etc? I'm willing to try but I'd need basic instructions and reassurance it wouldn't muck up my warranty if it didn't work as my only other option is to exchange for a new device.
I'm a noob so I need detailed basic step by step instructions.
Any help, advice etc would be hugely appreciated. Thanks

Just send it back, no point messing about with it if it brand new could down to a fault with the hardware itself.

ixon2001 said:
Just send it back, no point messing about with it if it brand new could down to a fault with the hardware itself.
Click to expand...
Click to collapse
Iv'e heard this is a common problem with the N6 whilst trying to update the OTA 5.1 I had no other apps on the phone it was fresh, I did nothing wrong, I know someone who has been through 4 devices with the same bloody issues! In the end he had to sideload 6.0 and I'm not confident in being able to do that.

Well best bet is to download wugfresh toolkit 2.10 i think is the latest version, follow the instructions carefully because first you need to unlock the bootloader then flash 6.0.1 which has just come out.
Using Wugfresh is the best way to go if your new to flashing & you can't really go wrong with it.

ixon2001 said:
Well best bet is to download wugfresh toolkit 2.10 i think is the latest version, follow the instructions carefully because first you need to unlock the bootloader then flash 6.0.1 which has just come out.
Using Wugfresh is the best way to go if your new to flashing & you can't really go wrong with it.
Click to expand...
Click to collapse
I`am sure most xperienced users (me included) will not agree with you The best way to unlock, flash and root is still adb/fastboot. Especialy for lesser xperienced users that are lost is something goes wrong while using the toolkit, wich happens frequently btw. Just check the help threads.

gee2012 said:
I`am sure most xperienced users (me included) will not agree with you The best way to unlock, flash and root is still adb/fastboot. Especialy for lesser xperienced users that are lost is something goes wrong while using the toolkit, wich happens frequently btw. Just check the help threads.
Click to expand...
Click to collapse
Lol it's not rocket science using adb, been doing that way for years but for somebody that never flashed, rooted ect I still think the toolkit best way to go at first because everything is done for you at a click of a button.
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.

ixon2001 said:
Lol it's not rocket science using adb, been doing that way for years but for somebody that never flashed, rooted ect I still think the toolkit best way to go at first because everything is done for you at a click of a button.
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
Click to expand...
Click to collapse
Lets agree to disagree

OK

ixon2001 said:
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
Click to expand...
Click to collapse
No, but because toolkits are always behind at least one version with marshmallow. People kept bricking their devices with toolkits when marshmallow came out and they thought they could root it. As 6.0.1 came out they'll do something else wrong.
Toolkits are not help. It's the lazy way if everything is already working and up to date.
Also what can a toolkit do if this phone doesn't even have developer options turned on? If it's in boot loop, as the OP said, then the Enable OEM unlocking was never set, then the only solution is to send it back. Unless there's a toolkit magic we don't know about.
Sent from my Nexus 6 running cyosp using Tapatalk

istperson said:
N
Also what can a toolkit do if this phone doesn't even have developer options turned on? If it's in boot loop, as the OP said, then the Enable OEM unlocking was never set, then the only solution is to send it back. Unless there's a toolkit magic we don't know about.
Click to expand...
Click to collapse
I think op created another thread http://forum.xda-developers.com/nexus-6/help/nexus-6-stuck-bootloop-trying-to-update-t3266100 for this issue - and was somehow able to unlock the bootloader (not sure how that worked if OEM unlock was never set)

jj14 said:
(not sure how that worked if OEM unlock was never set)
Click to expand...
Click to collapse
It was said that some of the first Nexus 6s with the original 5.0 came out with a bootloader that didn't check for this switch.

I need some help. I'm bricked.

Okay. so after hours of searching and reading about unbricking my nexus 6. I am lost, and very desperate.
So, I unlocked my bootloader, and rooted my phone today using chainfire cf auto root. and all went well. The primary reason I did this was to edit the build.prop file to enable wifi tethering, and this is where my problems started. Using root explorer I added
HTML:
net.tethering.noprovisioning=true
to the end of the build.prop file. I rebooted and now I'm stuck in a bootloop on the google screen.
I did not have a custom recovery installed, so flashing a new rom isn't that easy. I have looked into flashing twrp or cwm from the stock recovery adb sideload feature, but I haven't gotten this figured out either.
So that brings me to where I am at now. I still have an unlocked bootloader, which I guess is leaving me some options, but I just don't know where to go to find information which isn't going to further muck this situation up.
Help, please. I don't have a backup phone. And I am getting desperate.
Thanks in advance

Reboot to the bootloader, flash stock system.img
Sent from my Nexus 6 using Tapatalk

very first off.. http://forum.xda-developers.com/nexus-6/general/attention-questions-t3228454
meaning, you wont get help if tou do ont post it in the right place.
secondly, you have two choices, flash twrp then flash a rom, or flash the factory image(just system.img). what your pro lem is tgat you used a toolkit, instead of learning thd very easy proper way. now you dont know how to do things. its rwally easy to flash twrp via fastboot, and its very easy to flash a factory image using fastboot as well. now ill ask a mod to move your thread into the correct area..

thanks
simms22 said:
very first off.. http://forum.xda-developers.com/nexus-6/general/attention-questions-t3228454
meaning, you wont get help if tou do ont post it in the right place.
secondly, you have two choices, flash twrp then flash a rom, or flash the factory image(just system.img). what your pro lem is tgat you used a toolkit, instead of learning thd very easy proper way. now you dont know how to do things. its rwally easy to flash twrp via fastboot, and its very easy to flash a factory image using fastboot as well. now ill ask a mod to move your thread into the correct area..
Click to expand...
Click to collapse
I am mainly a reader here and don't normally post as I can figure things out on my own normally. So, sorry for posting in the wrong forum.
Help is appreciated..
Thanks.

acscot2 said:
I am mainly a reader here and don't normally post as I can figure things out on my own normally. So, sorry for posting in the wrong forum.
Help is appreciated..
Thanks.
Click to expand...
Click to collapse
i just saw, it was your first post. i didnt mean to sound rude, for that im sorry.
but you have your answer(s). your phone isnt bricked, its just without os. and the os can be flashed, even using a toolkit.