Database Develop

Nexus one only going to the "Android system recovery <2e>" screen

When booting the Nexus One I get an Android with an explanation point, then I am able to toggle the volume key and power to get into "Android system recovery <2e>" screen which gives me the options
-reboot system now
-apply sdcard:update.zip
-wipe data/factory reset
-wipe cache partition
when it's in this screen I can NOT access it through fastboot or adb.
It looks like it is only allowing me to push "officially" signed update.zip files to it and nothing else.
I cannot get it in to hboot or anything else it ONLY boots into "Android system recovery <2e>"
Maybe someone has an official update.zip boot image they can send me to or some other idea it would be much appreciated since I cannot use the phone at all.
Thank you in advanced, Please help!!!

Did you try holding trackball and power button when the phone is turned off to bring you directly to fastboot?

irishrally said:
Did you try holding trackball and power button when the phone is turned off to bring you directly to fastboot?
Click to expand...
Click to collapse
Yes, with no luck, it just goes straight to the Android and explanation point

Are you rooted? Unlocked bootloader? What did you do to get you into this situation?
Not to worry you, but usually not being able to boot into fastboot is not a good thing.

hyperandy said:
Maybe someone has an official update.zip boot image they can send me to or some other idea it would be much appreciated since I cannot use the phone at all.
Thank you in advanced, Please help!!!
Click to expand...
Click to collapse
Heres a thread that contains the official 2.1 update1 zip.
http://forum.xda-developers.com/showthread.php?t=627823
Maybe the volume key or trackball is stuck/damaged?

irishrally said:
Are you rooted? Unlocked bootloader? What did you do to get you into this situation?
Not to worry you, but usually not being able to boot into fastboot is not a good thing.
Click to expand...
Click to collapse
ya at this point I was kinda figuring that but I am hopeful ...I unlocked the boot loader and everything was going great until I partitioned the sd in the recovery image, then I started getting a weird MISC error and couldn't boot up at all, only in recovery but fastboot and everything still worked. Then I saw a post about applying the original image to the device via fastboot, preformed that and ever since then I have had a $500 brink that lights up

I don't think you can brick the N1 by just flashing a ROM, usually this only happens when changing the radio or spl.
I would try taking out your sd card, copy all your files you your computer, format your sd card, copy your files back to your sd card and see what that does for you. Maybe some issue arose when you partitioned your sd card, although you said fastboot still worked until you flashed the ROM. Worth a shot though.
If you can access fastboot then, I would flash Amon Ra's custom recovery image via fastboot and take it from there.

well I actually tried a completely different sdcard and then none at all. No luck. If it's not letting me into hboot do you think it may have gotten corrupted or something

hyperandy said:
well I actually tried a completely different sdcard and then none at all. No luck. If it's not letting me into hboot do you think it may have gotten corrupted or something
Click to expand...
Click to collapse
Honetly, I don't know. Did you try copying the .zip in the link posted above to your sdcard and then applying that zip in recovery?
Hopefully someone that knows more than me will chime in and have some better ideas.

irishrally said:
Honetly, I don't know. Did you try copying the .zip in the link posted above to your sdcard and then applying that zip in recovery?
Hopefully someone that knows more than me will chime in and have some better ideas.
Click to expand...
Click to collapse
maybe it's because I just woke up but I am not clear what you are asking, can you rephrase that? The link above my SD card?

hyperandy said:
maybe it's because I just woke up but I am not clear what you are asking, can you rephrase that? The link above my SD card?
Click to expand...
Click to collapse
Did you try copying the .zip file in the link below to your sd card and trying to flash it in recovery?
http://forum.xda-developers.com/showthread.php?t=627823

Thank you, ya I didn't see the link the first time. duh. Yep I tried that and I get a build.prop error (although this update says installing for a second and i see a progress bar, I have tried that same file from a few download locations to make sure it wasn't a bad download too):
file_getprop: Failed to stat "/system/build.prop": No such file or directory
E:Error in /sdcard/update.zip
(status 7)
Installation aborted
Thank you for all your help!! but I am afraid this isn't looking to good.

I also tried creating that file just to see but since it wasn't officially signed it gave me an error about that

I think at this point it is looking for a specific signed update.zip file, where I find that, I have no idea.
It almost seems like I need the whole update.zip officially signed by google and/or HTC and then it would flash. I highly doubt they are going to hand that over. I am half temped to see if I could send it in to them to be reflashed even for a fee if it means I can get this thing working again, but I don't even know if they would offer that. It's only 2 months old and I think the file I need maybe out there but damned if I have been able to find it anywhere.

hyperandy said:
I think at this point it is looking for a specific signed update.zip file, where I find that, I have no idea.
It almost seems like I need the whole update.zip officially signed by google and/or HTC and then it would flash. I highly doubt they are going to hand that over. I am half temped to see if I could send it in to them to be reflashed even for a fee if it means I can get this thing working again, but I don't even know if they would offer that. It's only 2 months old and I think the file I need maybe out there but damned if I have been able to find it anywhere.
Click to expand...
Click to collapse
I wouldn't give up yet. I'm sure there is someone out there that can tell you you are completely hosed, or help you fix the problem.
If you can't fix it, I have heard it will cost $196 for a new motherboard if you send it in to HTC. They could just reflash your phone but I heard they handle a case like this by charging you for a motherboard swap. Second hand information though.

irishrally said:
I wouldn't give up yet. I'm sure there is someone out there that can tell you you are completely hosed, or help you fix the problem.
If you can't fix it, I have heard it will cost $196 for a new motherboard if you send it in to HTC. They could just reflash your phone but I heard they handle a case like this by charging you for a motherboard swap. Second hand information though.
Click to expand...
Click to collapse
I believe that, I work in the field service industry and I see stuff like that all the time. Although I would rather pay the 196 instead of 560+ again. I am almost 100% certain this could be re-flashed with the right file. but I have so far spent 2 full days trying different things, I think I will give it until tomorrow and then send it in (by then I should be good an sick of searching). Unfortunately, I am in love with my Nexus. it's been a while since I had a phone I really enjoyed as much. If I knew another great phone was coming out in a week I would probably say the heck with it and just buy the next one but this is still an awesome device.

hyperandy said:
I believe that, I work in the field service industry and I see stuff like that all the time. Although I would rather pay the 196 instead of 560+ again. I am almost 100% certain this could be re-flashed with the right file. but I have so far spent 2 full days trying different things, I think I will give it until tomorrow and then send it in (by then I should be good an sick of searching). Unfortunately, I am in love with my Nexus. it's been a while since I had a phone I really enjoyed as much. If I knew another great phone was coming out in a week I would probably say the heck with it and just buy the next one but this is still an awesome device.
Click to expand...
Click to collapse
Have you tried every option in all the other "HELP BRICK" posts?? I don't really have time to search (and my nexus is working fine) but I know there has been plenty of threads like this before. Multiple options where tried, some successfully and some not. I would not give up unless it won't power on at all. Does ADB logcat work during a boot? Fastboot Devices? anything??????

martin0285 said:
Have you tried every option in all the other "HELP BRICK" posts?? I don't really have time to search (and my nexus is working fine) but I know there has been plenty of threads like this before. Multiple options where tried, some successfully and some not. I would not give up unless it won't power on at all. Does ADB logcat work during a boot? Fastboot Devices? anything??????
Click to expand...
Click to collapse
No haven't tried those checking the Help Brick post I will see what I can find. No adb and not fastboot devices, just says waiting for device if I try anything.

Since you have unlocked the bootloader have you tried a complete reload?
fastboot: flash boot, flash recovery
recovery: wipe everything, reset, install latest CM.

Did you ever figure this out?

HTC VIVID Super User Problems....

So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.

Have you checked with Root Checker Basic to see if you even have Root? If you didn't follow the Super Guide step by step your phone could have relocked after you turned your phone off/on.
If it still fails to update you could try SuperUser Update Fixer.

Yes I have check with root checker.
This may be a dumb question but how do I uninstall Superuser? When I go to the typical application management it does not give me the option. I have done an install again to overwrite the files and nothing changed there.
I followed the instructions step by step (though obviously I messed up somewhere...)
Sent from my HTC PH39100 using XDA App

Kraizk said:
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Click to expand...
Click to collapse
Interesting... maybe your root didn't stick. We had a little trouble with that before but pirateghost fixed the CWM ROOT zip. You have a working CWM Recovery, correct?
In the superguide, I have a second option for root in case the first doesn't work. In your case, go ahead and try the second option. The one involving the supertool. That should get you perm root. If that doesn't even work, then we might have to put you back to stock and go at it again.
EDIT: BEFORE TRYING THE SUPERTOOL, try flashing the new CWM ROOT VER2 zip from CWM recovery and see if root sticks.

Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.

Kraizk said:
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Click to expand...
Click to collapse
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?

*Just a clarification*
You have to unroot your phone to get rid of it Idk why I put uninstall/reinstall earlier...still out there from last night I guess.

slapshot30 said:
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
Click to expand...
Click to collapse
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...

Kraizk said:
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Click to expand...
Click to collapse
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?

slapshot30 said:
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
Click to expand...
Click to collapse
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated

Kraizk said:
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Click to expand...
Click to collapse
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4

Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....

Kraizk said:
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Click to expand...
Click to collapse
It's no problem, this isn't a dumb question or easy issue by any means. If the method I directed to you doesn't work, let me know. There is another way to do it without all the code.

slapshot30 said:
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Click to expand...
Click to collapse
Worked perfectly. I flashed it back to stock using the thread you linked me to. Then I did the CWM Root method and so far so good. I appreciate all of your help

Nice, I'm glad you were able to get everything working.
Sent from my HTC PH39100 using xda premium

[Q] HTC M7 Dev Edition *Factory Rom Lost*

Hey everyone new poster to the forums here . Have a question about loosing the stock ROM for my HTC M7 Dev edition. I made the backup but I think when I formatted I formatted more then I should have because when I pull up TWRP recovery mode to restore a backup nothing is listed in the window. However when I go into the internal storage in windows on my computer with the phone connected and look inside HTC One\Internal storage\TWRP\BACKUPS I found a folder called HT34GW9xxxxx and a sub directory with a date on it and it looks like the date that I did the flash in the first place. That folder also has 13 files in it equaling out to 4.25GB in size. So basically what I'm getting at is how come I can see this folder here but not in recovery and even if I could see it in recovery this seems like it's not large enough to be HTC Sense 5.0 according to this thread and the downloads attached to it.
http://forum.xda-developers.com/showthread.php?t=2248997&highlight=nandroid
Also speaking of that thread considering the original M7 Dev rom is gone can I use that thread to restore my phone even though I am using TWRP and not clockwork. I'm not the greatest at these type of things, I don't want to brick my phone, and I never have enough time invest in this stuff. If I knew this was going to happy I probably wouldn't have done it in the first place lol.
Thank you in advance and sorry if this has already been talked about, I did a search but I must have skipped over it if it was already out there :\.

dont worry if u have htc one 64gb dev edition go to htcdev..com and download ruu file lock the bootloader and run ruu thats all

Follow up
ccpzcp said:
dont worry if u have htc one 64gb dev edition go to htcdev..com and download ruu file lock the bootloader and run ruu thats all
Click to expand...
Click to collapse
Thank you for the help. A follow up question would be is there a place to get someone's previous backup and download it like the link I put up in the previous posts user did. I really don't want to lock the boot loader and I would love to just be able to easily get Cyanogenmod back on the phone easily. Reason being is that right now the Cm camera just isn't up to pay with the Sense camera software and if I go to an event like I am tonight I would like to be able to swap back and fourth.

TWRP and CWM backups aren't compatible with each other. You'd have to flash the relevant recovery to use a corresponding backup.
You still have your backup though. You said as much in your OP. You just need to go into TWRP settings and specify the default location for your backups.
As mentioned above however, you can just flash the official RUU to return to stock

Thanks a ton!
Just wanna say thanks to the both of you for your help. I went with option 2 for now because I want to switch back to CM after the Cardinals MLB game tonight. I never lost the backup and you were right I just had to find the folder. It was weird I didn't see any button to search for a folder kinda odd how TWRP is layer out in that interface. Yet I found the backed up file and took about 10 minutes from start to finish. The device is still unlocked to so I can reflash CM when I'm ready.
A little off topic but does anyone know what the difference between the GSM Cyanogenmod ROMs and the AT&T ROMs are? I have the Dev version but flashed the AT&T version and it ran fine made calls and had no data transfer issues at all.

Ok so I actually started having issues after that last post. What was happening was I kept getting this HTC system update my guess the Camera software update but whatever. So I clicked on the update now and it downloaded like normal then reboot. After it reboot it booted into TWRP recovery well at that point I didn't know what to do so I just went a head and rebooted into System. Well here is where the issue started it said again system update avalible ok great install, same deal it just booted back into TWRP after the download. Back into system I went and again same thing.
At this point I desided to go into TWRP and do a system restore and I thought that worked cause it wasn't notifying me immediately after the launcher loaded to install the update. So I checked for it manually and of course there was one. Tapped on Install it downloaded and asked to reboot so I did...
SAME ISSUE AHHHHGGG! Lol
This will be the end of me haha.
Is there something I'm missing here? Can I not have root access or a a third party boot loader like TWRP or both modifying the system. What am I missing?
Ok thanks again, sorry for the multiple posts I'm just so frustrated at this point.
Sent from my HTC One using xda premium

This my very wild guess. Try flashing stock recovery first and then install the OTA update again. That's just my wild guess I'm not saying it will 100% work.

No luck
shadowboy23 said:
This my very wild guess. Try flashing stock recovery first and then install the OTA update again. That's just my wild guess I'm not saying it will 100% work.
Click to expand...
Click to collapse
Nope no luck

Hopefully this helps..
What I did find was this link here...http://forums.androidcentral.com/htc...ml#post2827047 that's where someone else is having the same issue but on Sprint I'm guessing. So that doesn't really apply to me. However a poster further down the thread gave another link to all these "nandroid?" files. I'm not really sure what a nandroid is haha I'm such a noob at this. Basically what they are saying is that unrooting it then i guess somehow putting this "nandroid" file on it somehow. Anyone have any idea on this. I'm terribly sorry for my noobishness but I'm trying to learn all this and it's really frustrating at first..
Here's the link to the nandroid files. http://forum.xda-developers.com/show....php?t=2207874 funny thing is that I actually found that link on Android Central website so that I could come back here and repost about it again heh. Anyways does that look like something that might fix the issue that I'm having?
Even if this file does help I have no idea what to do with it but that first link seemed to have some video's attached to it although I worry about following them because it's for Sprint and I really don't want to brick my phone. (another reason I am being so careful) You pay over 600 dollars for a device you tend to be super careful with anything you do with it.

Nvidiafanboy said:
Nope no luck
Click to expand...
Click to collapse
Sorry about that.

All fixed!!
Ok so I got it. I ended up finding this http://qbking77.com/development/how-to-unrootunbrick-the-htc-one-to-stock-2/
Worked great fixed everything. Linked to the RUU on HTC Dev website also so its official.:good:
So basically if Anyone need to restore to factory from a mess they have made follow this guide it works perfectly and he does an execelent job of describing how to do it in a video he posted step by step.

not really a noob, but still confused anyway... need a little help from my friends...

Project Fi Nexus 6 rooted here on 5.1.1 LVY48E
I keep getting a notice that a system update has been downloaded (29.1) megs..a tad annoying
Would like to run the update, but can't because of TWRP... Also would like to try 6.0 if it is out, just don't want to lose root, and or have to have my phone reset...
I have Wug's nexus root toolkit too
How do I update to the latest L and or/ M???
Looking for some friendly advice....
Thanks!

Forgot to mention that I have tried flashing the update manually to no avail..
Drumrjoe

You can't update your rooted phone with Ota update, only way is to flash the factory image, download latest Nexus 6 factory image from Google and flash it with the tool kit, if you don't know how to flash a factory image, you should see the main thread

And I believe , given the need for a modified boot when rooting Marshmallow, you lose the OTA anyway, no?

aiiee said:
And I believe , given the need for a modified boot when rooting Marshmallow, you lose the OTA anyway, no?
Click to expand...
Click to collapse
Thanks for the help! Been using the toolkit to try and flash stock + unroot...
It doesn't seem to be working for me... First tried to update to last version of lollipop.. runs the batch updater after downloading the factory image and extracting.. batch window closes after awhile I wait after no change to phone or toolkit and nothing has changed on phone... tried this with marshmallow too... same thing....
At a loss..

drumrjoe said:
Thanks for the help! Been using the toolkit to try and flash stock + unroot...
It doesn't seem to be working for me... First tried to update to last version of lollipop.. runs the batch updater after downloading the factory image and extracting.. batch window closes after awhile I wait after no change to phone or toolkit and nothing has changed on phone... tried this with marshmallow too... same thing....
At a loss..
Click to expand...
Click to collapse
Just do it manually using fastboot. Or since you have TWRP, find a pre-rooted rom.zip you can flash from there.

Lately half the threads are about a toolkit not working. There should be a sticky about this: Don't use toolkits on Nexus phones! Those who don't feel secure enough to enter three lines in a command line/terminal really shouldn't use toolkits either. It gives a feeling of false security for a price of being totally at loss if anything goes wrong. And things do go wrong.

istperson said:
Lately half the threads are about a toolkit not working. There should be a sticky about this: Don't use toolkits on Nexus phones! Those who don't feel secure enough to enter three lines in a command line/terminal really shouldn't use toolkits either. It gives a feeling of false security for a price of being totally at loss if anything goes wrong. And things do go wrong.
Click to expand...
Click to collapse
We try to advise people not to use rootkits or kits of any kind. It does nothing but hinder their efforts if something goes wrong. In the end it is people being lazy and then bricks happen and they have no idea what to do.

zelendel said:
We try to advise people not to use rootkits or kits of any kind. It does nothing but hinder their efforts if something goes wrong. In the end it is people being lazy and then bricks happen and they have no idea what to do.
Click to expand...
Click to collapse
I think many of us here agree with that. To avoid bashing, we have to say "use them if you like, but learn to use fastboot manually first". But all the work we collectively put in to that as a majority is easily undone when just one person replies "use a toolkit". It almost always ends up in a debate that is so long that when it reaches it's conclusion, the OP ended up using a toolkit anyway.,

danarama said:
I think many of us here agree with that. To avoid bashing, we have to say "use them if you like, but learn to use fastboot manually first". But all the work we collectively put in to that as a majority is easily undone when just one person replies "use a toolkit". It almost always ends up in a debate that is so long that when it reaches it's conclusion, the OP ended up using a toolkit anyway.,
Click to expand...
Click to collapse
I know. All we can do is advise and the lazy will still be lazy and then end up with issues. This is why you will see people post about issues and then the min they mention they have used a root kit all replies stop. There are many of us that refuse to help people that have used a root kit. It shows they should not be messing around with their devices if they dont have the time to learn to do things properly.

Duly noted -
But seriously, thanks for the info.. will be figuring this out!
Best all
DJ

Update-
Sincere thanks to all that replied.. Did not know that the toolkit's were a nono-
I did use the command line to manually update and all is well. I am on LVY48I now and rooted.. Next is to reinstall the latest xposed for 5.1.1.
Also, tried finding a stock pre-rooted marshmallow, but didn't really have any luck with that... any pointers or links?
TIA

drumrjoe said:
Update-
Sincere thanks to all that replied.. Did not know that the toolkit's were a nono-
I did use the command line to manually update and all is well. I am on LVY48I now and rooted.. Next is to reinstall the latest xposed for 5.1.1.
Also, tried finding a stock pre-rooted marshmallow, but didn't really have any luck with that... any pointers or links?
TIA
Click to expand...
Click to collapse
Not 100% sure of this but I believe that Marshmallow will not achieve root without some modification. At least I couldn't

Issues after trying to Root : Bootloader Code 3 : Soft Bricked?

Using this guy's guide for the Nexus 5 I had no issues, bought a N6 today and was giddy to flash on Cataclysm for N6 and figured might as well use same person's guide for next phone up.
http://www.androidrootz.com/2014/12/how-to-root-nexus-6-windowsmaclinuxubun.html
Was able to unlock bootloader, then installed TWRP but now am getting the 'corrupt phone' message, however unlike others like I have read on XDA, am unable to boot up by just letting it sit. Screen turns off and that's that. Before beginning entire process I enabled "enable/allow oem unlocking". I'm assuming that when the phone factory resets after the bootloader unlock I need to go back in and recheck 'allow oem unlock' in dev options, but I didn't as I assume/ed that it wasn't necessary and the guide doesn't tell you to.
Tried relocking the bootloader to maybe get phone to open up, but terminal tells me that I need to have 'allow oem unlock' checked. Nice Catch-22 http://puu.sh/moOUf/d0f8fa9050.png
Tried formatting data from within TWRP and factory resetting/wiping everything but it tells me that it is unable to mount '/data'
Have since tried WugsToolkit and flashing to stock with 'softbricked' option enabled the shamu-mmb29k-fact....tgz image that I downloaded and imported myself into Wugs (was taking 10 minutes to dl 1%). That seemed to work and told me it was a success, however when I then went back to re-enable the bootloader via wugs it fails and reboots with the lock sign still open and boots again onto 'corruption' screen that then flashes off and turns phone off, left it for 30 minutes at one point and didn't boot so don't think I'm lucky enough to be able to sit if through like others who had that issue
Where to go from here? Really hoping I didn't brick this phone less that 3 hours after getting it. I can still boot and see the Google screen and can get onto the bootloader and used to be able to get into recovery (since wugs have been getting the android with red triangle)
Been rooting/rom'ing since day one that I've had androids. Had a Samsung Apollo with CM on it, same for the Nexus S, then the Galaxy Nexus, then the N5 and looks like my chain of no issues ended tonight
Anything you can do for guys would be greatly appreciated. No clue where to go from here....

So from what I gathered, I think you are in luck. It sounds like your bootloader is unlocked. This is a very good thing. Under no circumstances do you want to try to re lock it right now or do you ever when stuck not being able to boot or any issues like that. If you lock it while stuck, thats when you are soft bricked. If I remember correctly, I got myself in the same situation , although maybe with out a custom recovery installed. None of that matters though. The way to fix this is to reflash the the factory image. Here are the guides for that.
https://www.youtube.com/watch?v=K_m6bYNKrXQ
This is the video I used the first time. A bit rough but, It did the job.
https://www.youtube.com/watch?v=2hao_Yf-gaw
Here is a bit of a nicer one. I used it the second time around.
and lastly here is an xda post http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I would recommend reading and watching all of these and maybe doing more research so you really knows whats going on. The flash-all script is not going to work from what I've read and I've always done it manual so go with that. It may also be a good idea to keep the custom recovery, so look into to keeping that. Maybe it is as simple as not erasing the recovery partition and not flashing the recovery image. This is what should save your nexus.
Now, I am fairly new to the Rooting and ROMming, really only started 2 months ago, so I would really appreciate if any of the more experienced guys on XDA can confirm what I said. Please don't try any of this without confirmation from another member here, I do not want to be responsible for sending your device past the point of no return. I recently had to order a new Nexus 6 as the screen is dead, so I know it's frustrating to have that loss. In your case, as long as that boot loader is unlocked, you should be safe. Best of luck to you.

DO NOT RELOCK THE BOOTLOADER!!!!! I cannot emphasize how critical it is that you do not relock the bootloader, given the position you are in. If you somehow manage to relock the bootloader and "enable OEM unlock" is toggled off and Android will not boot (even after attempting a factory reset), then you are 100% bricked with no way to fix your phone. Personally, I leave my bootloader unlocked 100% of the time so that I can fix anything that may go wrong with my phone. Additionally, I (as well as many other users on here) will always advise against using Wug's or any other toolkit in order to do stuff to your phone. While they do provide a nice GUI as well as an easy way to install the necessary drivers, using the regular platform-tools command line method isn't all that hard to figure out, and it allows you to know exactly what you have done to your phone. With Wug's and the like, you never really know what commands that they are running and exactly at what point in the process a flash may fail. Right now, I would advise you to read up on using the platform-tools method to flash stock images. After you have all of the necessary drivers, platform-tools, etc. working properly on your computer, I would strongly advise that you download MMB29S (the latest official update) from the Google Developer page and flash it using the platform-tools method, NOT with Wug's. And whatever you do, I repeat, DO NOT LOCK YOUR BOOTLOADER!
---------- Post added at 07:03 AM ---------- Previous post was at 06:51 AM ----------
triguyrn said:
So from what I gathered, I think you are in luck. It sounds like your bootloader is unlocked. This is a very good thing. Under no circumstances do you want to try to re lock it right now or do you ever when stuck not being able to boot or any issues like that. If you lock it while stuck, thats when you are soft bricked. If I remember correctly, I got myself in the same situation , although maybe with out a custom recovery installed. None of that matters though. The way to fix this is to reflash the the factory image. Here are the guides for that.
https://www.youtube.com/watch?v=K_m6bYNKrXQ
This is the video I used the first time. A bit rough but, It did the job.
https://www.youtube.com/watch?v=2hao_Yf-gaw
Here is a bit of a nicer one. I used it the second time around.
and lastly here is an xda post http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I would recommend reading and watching all of these and maybe doing more research so you really knows whats going on. The flash-all script is not going to work from what I've read and I've always done it manual so go with that. It may also be a good idea to keep the custom recovery, so look into to keeping that. Maybe it is as simple as not erasing the recovery partition and not flashing the recovery image. This is what should save your nexus.
Now, I am fairly new to the Rooting and ROMming, really only started 2 months ago, so I would really appreciate if any of the more experienced guys on XDA can confirm what I said. Please don't try any of this without confirmation from another member here, I do not want to be responsible for sending your device past the point of no return. I recently had to order a new Nexus 6 as the screen is dead, so I know it's frustrating to have that loss. In your case, as long as that boot loader is unlocked, you should be safe. Best of luck to you.
Click to expand...
Click to collapse
Regarding the flash-all script, my friend and I just used the script included with MMB29S and it worked fine. In addition, I was able to use the one with MMB29K, MRA58K and MRA58R, all of which worked fine. I'm not sure if these scripts always work for some users and never work for others, but I always recommend that people who are new to flashing simply try them, as they are quite convenient when they work. In addition, I have only been in the rooting and ROMing scene for about a month or two as well, but I would consider myself pretty seasoned by now considering all the different ROMs, rooting methods, etc. that I have tried. All the advice that you gave to the OP is excellent and I agree with it all.

matthew2926 said:
Regarding the flash-all script, my friend and I just used the script included with MMB29S and it worked fine. In addition, I was able to use the one with MMB29K, MRA58K and MRA58R, all of which worked fine. I'm not sure if these scripts always work for some users and never work for others, but I always recommend that people who are new to flashing simply try them, as they are quite convenient when they work. In addition, I have only been in the rooting and ROMing scene for about a month or two as well, but I would consider myself pretty seasoned by now considering all the different ROMs, rooting methods, etc. that I have tried. All the advice that you gave to the OP is excellent and I agree with it all.
Click to expand...
Click to collapse
Thank you. I always wanted to try the flash-all script but, I ahve read a few places it wouldn't work and haven't had the chance to give it a try lately. When my new device arrives in a day or two, I'll give it a shot. Thanks for the confirmation, makes me feel good knowing I'm starting to get the hang of this stuff

triguyrn said:
Thank you. I always wanted to try the flash-all script but, I ahve read a few places it wouldn't work and haven't had the chance to give it a try lately. When my new device arrives in a day or two, I'll give it a shot. Thanks for the confirmation, makes me feel good knowing I'm starting to get the hang of this stuff
Click to expand...
Click to collapse
No problem! It's too bad to hear about your device but at least you got a new one on the way. There is really no harm to at least trying the flash-all script. It will either work and save you time or fail halfway through and force you to flash everything manually.

triguyrn said:
Thank you. I always wanted to try the flash-all script but, I ahve read a few places it wouldn't work and haven't had the chance to give it a try lately. When my new device arrives in a day or two, I'll give it a shot. Thanks for the confirmation, makes me feel good knowing I'm starting to get the hang of this stuff
Click to expand...
Click to collapse
Flash-all script is still broken, flash the img files individualy in fastboot.

gee2012 said:
Flash-all script is still broken, flash the img files individualy in fastboot.
Click to expand...
Click to collapse
You guys are life savers, thank you so much
Got it to work after I was getting ready to phone it in and bring it to a repair shop and eat whatever the charge might've been