Related
Ok so I think I've bricked my Nexus One. Everything was working perfect until I re-rooted it (to have SetCPU to work). I am now stuck at the loading animation screen (Google Nexus One "X"). It just keeps going and going and going. I've even tried loading my Nandroid backup and still does the same and won't work. Also I've wiped to factory default settings and tried to reinstall Modaco's 1.3 rom.
Someone please help me out...
Flash bacon add-on on top
bye!
So reinstall Modaco's 1.3, then install Bacon Add-On, and then reboot?
Yep That's the solution for some users
ok cool I'll give it a shot right now... I really appreciate it
ok at this moment it's still stuck on the animated screen... now I really don't know what to do...
Try flashing the stock rom
if u have the sdk installed, the run ddms. power on the phone usb connected to pc and see the log in ddms, paste-bin here
I have no idea on how to do that... I'm pretty much stuck at this point
try not flashing Modaco's Rom,
just flash CM's bacon
i think there is a confusion because Modaco's rom is in the rooting threat (made me believe you HAVE to use Modaco's superboot and then go to CM's bacon.
reality is you don't need modaco's superboot. after bootloader unlocking and flashing Amon Ra's recovery image you can go straight flashing CM's Makin' Bacon.
It seems people have been successful with CM's
maybe just go straight back to the start, check that bootloader is unlocked, flash amon ra's recovery, then flash Makin' Bacon
good luck
shmigao said:
try not flashing Modaco's Rom,
just flash CM's bacon
i think there is a confusion because Modaco's rom is in the rooting threat (made me believe you HAVE to use Modaco's superboot and then go to CM's bacon.
reality is you don't need modaco's superboot. after bootloader unlocking and flashing Amon Ra's recovery image you can go straight flashing CM's Makin' Bacon.
It seems people have been successful with CM's
maybe just go straight back to the start, check that bootloader is unlocked, flash amon ra's recovery, then flash Makin' Bacon
good luck
Click to expand...
Click to collapse
WOW, I really appreciate it and that just worked for me. Thank you to the both of you guys!
if you can get into bootloader mode (this is the lowest level mode you can boot into), you can not brick. Even more so if you can get into recovery (which is usually always possible if you can get to bootloader)
Good you found a way to get out of your situation.
Like i said in Android 101, you CAN NOT brick the phone unless you are updating SPL and Radio. All other stuff is just a minor inconvenience.
risterdid said:
WOW, I really appreciate it and that just worked for me. Thank you to the both of you guys!
Click to expand...
Click to collapse
haha, i am glad it worked! I don't even have my Nexus One in my hands (my biz trip to the States has been delayed again ), but i spend the waiting time doing my research... it's a bit like the Holiday Season, just that the gift giving day gets pushed out further and further...
glad it worked and it confirmed my research - so i can go at it with ease once i can
This is good news. OP, you should update your thread titled with the prefix [SOLVED].
ahh how'd I miss that 101 sticky... thanks for the heads up again guys.
Edited title =)
Am I bricked?
Ok, my issue is that I cant boot into bootloader or recovery (I tried booting with rollerball pushed in, booting with down volume, abd-mac reboot recovery, abd-mac reboot bootloader) and it just goes right into my OS which is crashing every few minutes, and my radio wont work. Any suggestions? If I am bricked, can I send it to HTC even though its rooted and bootloader is unlocked? I dont care if I have to pay for fixing it.
DrBlast33 said:
Ok, my issue is that I cant boot into bootloader or recovery (I tried booting with rollerball pushed in, booting with down volume, abd-mac reboot recovery, abd-mac reboot bootloader) and it just goes right into my OS which is crashing every few minutes, and my radio wont work. Any suggestions? If I am bricked, can I send it to HTC even though its rooted and bootloader is unlocked? I dont care if I have to pay for fixing it.
Click to expand...
Click to collapse
First of all, if your phone boots at all, it isn't bricked. A brick is a paperweight - it doesn't do anything. Second, this thread of 5 months old. Third, people have talked A TON about sending phones in to HTC with an unlocked bootloader, do a bit of searching.
And finally, it is very peculiar that your phone doesn't boot into bootloader or recovery. Try plugging your phone into your computer, opening your command prompt, navigate to your adb install direction, typing "adb wait-for-device reboot bootloader", and turning on your phone. Best of luck!
People should be banned for bumping 5 month old threads with posts not even related to the OP's post. Ridiculous.
@rcxquake: thanks for your suggestion. That didnt work, it just rebooted the OS. Ill keep searching for my solution and how to send to HTC if I cant find the solution.
@GldRush98: Sorry for ruining your day. I put in a google search for what I was experiencing and this was one of the top result of anyone remotely close to my issue. Yes, this is an old post, but maybe someone had this issue months ago, and had a solution I wasnt aware of.
And like I said, I found this post, although not exactly my same issue, was as related as Ive been able to find. I didn't find it so ridiculous.
If you can find my same issue on another post, then please help by pointing me to it so I can find my solution. I didn't mean to cause any issues.
Thanks
I for one am glad you posted. I don't know whether this is a solution for you or not, but I'm sometimes only able to get to the bootloader after I've had the phone off the charges, with the battery out, for some time. It varies for me between a few minutes and many minutes. It is hard to say because when I try and it doesn't work, I don't know if I've reset the time by having tried.
Anyhow, I found this thread because I'm having trouble with an N1, and one of the earlier posts may help me. Thanks for bumping the thread for my benefit.
Before you tell me to 'Google it' (which I have, and leads me to 1000 posts of people telling other people with the same problem to 'Google it'), please read.
I will PayPal anyone $20 with working instructions of how to resolve this
Phone: HTC Hero w/ chin
Carrier: Alltel
Story:
Switched from WM6 Palm Treo Pro to HTC Hero. Came with 2.1 and needed apps2sd. Want CM7 stable.
-Rooted using AndRoot.
-Installed SuperUser and Root Checker. Root Checker said I was good to go. SuperUser would not show any apps in the list this whole time.
-Installed Titanium Backup which said I needed BusyBox, but it would fail to install. Tried to install busybox and it said I was not rooted. Alright...
-Installed ClockworkMod and flashed recovery. Tried to reboot into clockwork recovery, but when I clicked it, it did nothing. When I clicked rom from sd card, and clicked the CM7, it said 'going to reboot now' but again, nothing happened.
I booted into recovery manually, but it was still in Android system recovery. Apparently there was some sort of rooting problem, so I tried z4root. Permanent root was stuck on 'rebooting', and temporary root said successful, but something was still wrong as BusyBox installer would say I was not rooted, and SuperUser app didn't show any programs to allow permissions.
I turned the phone off, and back on. It goes to the white 'HTC' screen, reboots, and then comes to a black page with a picture of a Hero and a red triangle and exclamation mark. I hold home and hit power, and it takes me into the Android system recovery. I wiped data and cleared cache, rebooted, and it does the same thing.
- - -
Now i've done many hours of research, and found nothing to help me. I guess i'm a bit confused on what the SDK does and how to use it, because it won't connect to my phone since I can't even boot my phone into the OS. I tried to download the RUU and rename it update.zip, but it says signature verification failed or not found in android recovery. I've done the clear data method by holding home, back, and power, but still nothing.
I need a clearcut answer for getting back to a stock Alltel 2.1 OS on my phone. I am more advanced than a basic user, and have flashed many roms on Windows Mobile, but remember I might not exactly understand everything.
I'm a silent browser on these forums but now I come to you guys for help. I hope to grow into a dev and hopefully help someone in the future in my position.
I read somewhere to wipe EXT2, but still confused on that process as it seems I don't know how to get into adb command line on my computer.
Try reflashing the cwm recovery. Sounds like you have no recovery image.
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
Dumb question...did you flash a ROM? Maybe I missed it in your post, but I see you installed Clockwork, SuperUser and all that, but don't see that you flashed a ROM. *EDIT* I see you did...
So...worst case scenario, if you can't even boot your phone, just start over from scratch...
Download the original AllTel ROM from here.
If you don't have HTC Sync set up and can't restore from your computer, use this method to flash it...your phone should now boot...
Then try to reroot, using this (preferred) or this.
Download ROM Manager from the Market and install ClockworkMod Recovery
Boot to recovery (hold home and power at the same time).
Once in recovery, wipe cache, system, data and boot (make sure you don't wipe your sd card! Do it twice for good measure)
Select install .zip from SD card, select zip and you should be good to go with a rooted phone and a new ROM.
I think that should cover it...
Ok, on your first link to flash my phone, the step says:
"With phone powered on, do "adb reboot bootloader" to enter fastboot."
How do I get the command prompt on my computer to communicate with the phone? That was my biggest problem when reading other people's posts. I guess i'm a bit lost. I installed the r10 android sdk which I believe is the first step? And when my phone is connected to the computer to enter these commands, is it okay if it is sitting at that screen with the red triangle?
Thanks for your help btw your steps sound simple, and simple is nice. One step closer!
Do you have HTC Sync set up? If you do, you should be able to restore from that to get you back to official AllTel...That's going to be the easiest way to get you back to stock I think.
And...I am on a Mac So, helping someone on a PC is not my forte with ADB
I'd try setting up HTC Sync and get yourself back to stock that way.
EDIT - To get it to communicate, you need to set up ADB and all that. Then just use command prompts...Try this thread for help/instructions.
I actually got it to load that rom with vol down + power but eventually got to 'CID incorrect! Update fail!', so i'll try connecting to sync.
damienisxcore said:
I actually got it to load that rom with vol down + power but eventually got to 'CID incorrect! Update fail!', so i'll try connecting to sync.
Click to expand...
Click to collapse
What ROM? The AllTel one?
I have to take off until about 8:30 or so...get yourself set up with HTC Sync and get the USB drivers and all that set up, first thing you need to do is get your computer to talk to your phone...download the official AllTel RUU and restore to stock. That's task 1
Then we'll get ya rooted
I think I found a rom that worked. Currently rebooting. I can follow the rest and if I need anymore help, I'll give you a hollar. I should have had it right the first time, but I was following about 5 sets of different directions and mixing them around to avoid certain programs. I like yours though.
Send me a PM with your paypal e-mail and I can send it over. Least I could do.
OP, glad you got it. What rom?
Ranger, nice!
sent from a series of tubes.
il Duce said:
OP, glad you got it. What rom?
Ranger, nice!
sent from a series of tubes.
Click to expand...
Click to collapse
He flashed CM7. Gotta get him on aospCMod
damienisxcore said:
I think I found a rom that worked. Currently rebooting. I can follow the rest and if I need anymore help, I'll give you a hollar. I should have had it right the first time, but I was following about 5 sets of different directions and mixing them around to avoid certain programs. I like yours though.
Send me a PM with your paypal e-mail and I can send it over. Least I could do.
Click to expand...
Click to collapse
It's tough sometimes to follow things...and as much as we always tell people to search, ya know, the search kinda sucks I searched for all the threads I linked for you, but I knew what I was looking for. If you don't know what to look for, searching is kinda tough. Glad you got it!
Now...if you want a real ROM, I'll just toss this one out there In all actuality, CM7 and aospCMod are quite similar, I am just partial to aosp's builds.
Let me know if you need any more help.
I had a great working rom of CG7. Everything was working great. Then I installed the Battery Icon mod 1.0
I rooted my phone with Z4root, and used the rom manager from clockworks to apply the CyanogenMod 7 rom.
I have ADB installed, but I can never get it to connect to my phone. I was about to give up when I found Z4root. The use of z4root and rom manager made it so simple.
I had it all working great, loving it.....
Then I mess it up with a battery widget.
I performed a backup of my stock rom from within rom manager, and it is saved on the sd card. I can't access it because of being stuck in a loop.
If I pull the card, and use an adapter I can read it on my laptop most likely. But what to read it with, to apply it back to the phone?
I have superoneclick installed, but don't see how to use it either...
But since it appears I half to use ADB and I have been having no luck with it, is there any other options for me to try?
I thought I could use some key command such as home plus power to bring up the commands to read my recovery, wipe data and restore but am not figuring it out.
Maybe I'm just freaking out since I'm going on no sleep, but can anyone please help an eager to learn noob out?
I'd really appreciate it. Apologies ahead of time if this is the wrong sub-forum, but it looked the closest for this topic.
Thanks,
-Joe
dude first of all read the forum rules and watch your language no ones going to help u with that attitude. seconnd if u had bothered to look around first you would realize that there are about 50 threads on how to fix a boot loop.
Sorry for any bad language. I edited it out, sorry.
I had bothered to look around for about an hour, and all threads kept pointing me back to using ADB push commands which I haven't been having much luck with.
Do you know of a better way to fix a boot looping hero? Or can at least point me in the right direction, I can and am willing to learn more, but just keep running into the same answers.
Again, sorry about any language, but if you can spare a link in the right direction, I'd really appreciate it.
Have you tried pulling the battery and then restarting the phone by holding down the volume key ( down) and the power Burton at the same time? This will put you in the boot loader and if you push the" home" Burton that should put you into recovery. From there, wipe data, cache, system and either restore a backup ( IF you did a nandroid), or flash a new Rom.
Then, reboot.
You need to do lot more reading of different threads because you will see that bootloops are a common occurrence. Just because something is hero cdma does not mean it will work with your particular Rom. Battery mods are built for that specific Rom and that specific build ( like 5/23 aosp/cm7); a battery mod from April probably won't work.
Flashing IS a gateway drug!
Reflash cm7 and don't try the batt mod anymore.
-----
Sent from my CDMA Hero. I got some hot Ginger-on-Hero action here!
As far as your adb issue. If you tap on my avatar you can find my thread on how to install adb on windows it might help you as you might just be having problem with the htc drivers. Also if you need help with installing it just pm me. And if you haven't figured out your bootloop problem hit me with a pm and if I can help I will. Good luck.
#Root/Hack-Mod_Always*
*hooray*
"holding down the volume key and the power Burton at the same time"
This did the trick this time, phew
This was the menu I was looking for. I reflashed my stock rom and all is well.
Then I just reflashed CM7 and will be avoiding the battery app. Lost all my settings because I hadn't backed up my CM7 rom (doh, live and learn)
Yes I can see that flashing IS a gateway drug! Once you get more comfortable and start understanding it, it is addictive to keep going further and further lol.
I'll keep messing with ADB, as I did get it to see the phone, just it has been 15 years since my days of messing with basically MS-DOS for all my command lines.
I was able to see the phone at one point but keep having trouble getting to the tools directory to start via DOS.
I'm hoping as I read more that maybe there is a better GUI for rooting and modifying other than ADB.
Thanks for the help, now I feel a little better equipped to go further.
Howdy all,
My phone broke, so I'm back on the hero. I forget any and all stuff of how to's on this phone so bear with me. Basically, I'm a noob for the hero now.
So, recently, I followed the Cyanogenmod Full Update wiki guide, rooting it with the rageagainstthecage exploit. However, after my first time, my phone would eventually be so slow that it would seem to freeze. It's just so so so so slow. It's unusable. The lockscreen would come up, and i would touch the lock icon, which would vibrate. I would slide to unlock, but the screen doesn't react. at all. then it would vibrate, indicating an unlock, but the screen doesn't change at all. Occasionally, I'm able to accidentally enter an app, but I cannot read texts, answer calls, or reply to texts. Or do anything else.
Occasionally, I'll get a "app is unresponsive" message, but I can't force close/wait.
Oh, btw, when this happens, I can't get into my recovery (CWM 3.0.0.5). Also, I don't see the boot animation.
I have done an RUU stock reset, which fixed it once. The problem occurred again while on CM7, and I did another RUU reset, but the problem is now consistent throughout the stock sense. Omigawd what do i do?
Since I am now on stock that has usb debugging disabled, I can no longer access adb.
I am currently on absolute stock (fresh-out-of-the-box like), not rooted, and have S-OFF.
I am fairly well versed in fastboot and adb commands. When I try to access the recovery, I am sent to a black screen. When I plug in while in recovery and do "adb devices," I get my model number with the message "offline."
I AM OUT OF IDEAS! Someone. Please helpppp.
Thank you for reading. Thank you for helping.
Try a re-root with regaws rooter (the old version if you can get it) i swear by it. or Z4 root. once you have reestablished root, get Rom manager and flash the 2.4.0.7 recovery. then in rom manager go to downloads and get the cyanogen mod download of your choice( myself i prefer 7.0.3) and flash. you should be good to go from there.
as far as your adb it looks like your pc either isnt recocnizing your phone or you dont have the proper drivers installed.
Bout all i can tell ya ,one noob to another,,,
BTW, if you want to start completly from scratch, since your s-off,you can get a HERCIMG.img i think in the development sectin of this forum that is flashable from fastboot,,,try that ,,,Later man and good luck
Luckily you are S-Off. Can you put a HERCIMG.zip on the root of your sd card with a recovery (even CWM 2.5.0.7 will do) and then maybe try downloading another rom. Maybe you have a bad download. I am a big fan of Jaybob's TeamHeroc Rom which is a great CM7ish type of rom. Make sure that you format boot, cache, data, and system (I do it 3 times for each to make sure that it is really wiped) before you flash whatever rom you choose. You might have some leftover stuff that is causing some issues. Just wiping data and cache might not be enough. Here is a HERCIMG with a 4.0.1.4 recovery that you can load from H-Boot. I'm pretty sure that it's the Orange Recovery that I use.
hugabu said:
Howdy all,
My phone broke, so I'm back on the hero. I forget any and all stuff of how to's on this phone so bear with me. Basically, I'm a noob for the hero now.
So, recently, I followed the Cyanogenmod Full Update wiki guide, rooting it with the rageagainstthecage exploit. However, after my first time, my phone would eventually be so slow that it would seem to freeze. It's just so so so so slow. It's unusable. The lockscreen would come up, and i would touch the lock icon, which would vibrate. I would slide to unlock, but the screen doesn't react. at all. then it would vibrate, indicating an unlock, but the screen doesn't change at all. Occasionally, I'm able to accidentally enter an app, but I cannot read texts, answer calls, or reply to texts. Or do anything else.
Occasionally, I'll get a "app is unresponsive" message, but I can't force close/wait.
Oh, btw, when this happens, I can't get into my recovery (CWM 3.0.0.5). Also, I don't see the boot animation.
I have done an RUU stock reset, which fixed it once. The problem occurred again while on CM7, and I did another RUU reset, but the problem is now consistent throughout the stock sense. Omigawd what do i do?
Since I am now on stock that has usb debugging disabled, I can no longer access adb.
I am currently on absolute stock (fresh-out-of-the-box like), not rooted, and have S-OFF.
I am fairly well versed in fastboot and adb commands. When I try to access the recovery, I am sent to a black screen. When I plug in while in recovery and do "adb devices," I get my model number with the message "offline."
I AM OUT OF IDEAS! Someone. Please helpppp.
Thank you for reading. Thank you for helping.
Click to expand...
Click to collapse
I like Regaw's for rooting too. I used it the last time I did an RUU.
Isnt that what I said just before you ??? Lol
BTW Pilot, Where have you been? One of the most active members of the Heroc forum and all of a sudden ,poof, gone like a fart in the wind ! And then as if by magic, Poof, your back.I knew youd return, they always always return to the ol reliable Heroc. Good to see you around again bud, Later man,,,
Sent from my HERO200 using xda premium
hey guys just got back from vacation. Thanks for all your feedback. I switched phones to a temporary one now. I don't really feel like switching back to the hero cuz it costs money to activate phones. Also, I talked to an app developer about my problems. He told me that 1. the phone is way to old to be running gingerbread. Some nasty software probably carried over from my last flash onto the stock RUU flash. and that 2. whenever the problem occurs, I should let the battery drain before I do anything. Turns out, whenever the problem happens nowadays, I just let the battery drain and its all fixed. OKAY WTF. But all smiles now. Its my ipod-touch-like device now. I used regaws root.
THANKS GUYS SO MUCH.
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