Database Develop

[Q] Looking for help. Cant boot phone, recovery nor use adb commands.

Hej guys. I really hope that you can help me with my problem
Have been trying for 2 days and looking at post but haven't been able to get it fixed.
Here goes.
I have been playing around with custom roms on my htc one for a while now.
Then when i was about to install a new custom rom, i first wiped my phone.
I properly wiped something that should not be wiped, because i ended up with no os and no custom rom zip file that i could install in twrp.
I then tryed sideloading revolutions, and it seemed to work because it ended up booting on the phone and i could select what programs too install with it... but halfway through it stoped and rebooted.
now i cant even get into recovery anymore, and booting the phone only gets it to htc briliant logo. Then it restarts and tryes going into recovery, but it cant, and ends up just restarting over and over again.
Tryed flashing cwm and twrp again, but still cant get into recovery.
adb dont fint my device, and i have tryed all drivers i could find.
Tryed using a RUU, but it fails. Properly because its not the right one, but cant fint one that fits.
Sooo... i think im in a real pickle right now.
my radio is :4a.14.3250.13
hboot: 1.44.0000
Thinking about going back with my phone, but with the warranty gone i dont know if they'll even look at it.
Hoping for some advise, or some ideas on what to do.
-dealba

fastboot erase cache in terminal or with all in one toolkit

Arh thanks for your reply.
Cant belive i dident try that.
but it worked, im now able to get into twrp.
It says that i have 0 mb internal storage?
should i try to flash twrp again or what should my aproach be ?

dealba said:
Arh thanks for your reply.
Cant belive i dident try that.
but it worked, im now able to get into twrp.
It says that i have 0 mb internal storage?
should i try to flash twrp again or what should my aproach be ?
Click to expand...
Click to collapse
try reboot recovery if that doesnt work install cwm non touch. i love twrp but i had the same issue with it and i havent had it with cwm

skinsfanbdh said:
try reboot recovery if that doesnt work install cwm non touch. i love twrp but i had the same issue with it and i havent had it with cwm
Click to expand...
Click to collapse
Okay thanks
So i tryed installing cwm the non touch version. but it says the same thing as twrp.
And that is that it cant mount /sdcard/

dealba said:
Okay thanks
So i tryed installing cwm the non touch version. but it says the same thing as twrp.
And that is that it cant mount /sdcard/
Click to expand...
Click to collapse
i dont think that is a problem. im not absolutely sure about that but what is the next step you trying to accomplish

skinsfanbdh said:
i dont think that is a problem. im not absolutely sure about that but what is the next step you trying to accomplish
Click to expand...
Click to collapse
Well, im really just trying to get an os flashed back on the phone so i can boot it, either by another custom rom or a stock rom.
But since i cant use adb commands, how do i get a new rom on there?

dealba said:
Well, im really just trying to get an os flashed back on the phone so i can boot it, either by another custom rom or a stock rom.
But since i cant use adb commands, how do i get a new rom on there?
Click to expand...
Click to collapse
you on a windows computer?

dealba said:
Well, im really just trying to get an os flashed back on the phone so i can boot it, either by another custom rom or a stock rom.
But since i cant use adb commands, how do i get a new rom on there?
Click to expand...
Click to collapse
i have had the same problem. what i did is in twrp recovery go to wipe --- format data --- type yes (WARNING you will lose all your files)

skinsfanbdh said:
you on a windows computer?
Click to expand...
Click to collapse
Yes, im running windows

dealba said:
Yes, im running windows
Click to expand...
Click to collapse
download all in one toolkit if you havent already its easy to use and easier for me to tell you what to do. plus i dont know how well you know adb and fastboot commands

rambo12345 said:
i have had the same problem. what i did is in twrp recovery go to wipe --- format data --- type yes (WARNING you will lose all your files)
Click to expand...
Click to collapse
okay thanks, now i can see my sdcard.
But still wondering how to get a rom on it so i can flash from twrp..

dealba said:
okay thanks, now i can see my sdcard.
But still wondering how to get a rom on it so i can flash from twrp..
Click to expand...
Click to collapse
adb sideload
its an option in the all in one tool kit but its easier or you can type the command

skinsfanbdh said:
download all in one toolkit if you havent already its easy to use and easier for me to tell you what to do. plus i dont know how well you know adb and fastboot commands
Click to expand...
Click to collapse
I got the toolkit now
got a 5 min post restriction so little slow on replying

dealba said:
I got the toolkit now
got a 5 min post restriction so little slow on replying
Click to expand...
Click to collapse
i think it it will be over after 3 more posts. plug your phone in. then open all in one toolkit and select adb sideload then just follow the on screen instructions

skinsfanbdh said:
i think it it will be over after 3 more posts. plug your phone in. then open all in one toolkit and select adb sideload then just follow the on screen instructions
Click to expand...
Click to collapse
Okay, did the side loader, and used android revolutions rom. It installed and and after staying on boot animation a few minnuts it started.
Thank you so much for your help, really appreciate it

dealba said:
Okay, did the side loader, and used android revolutions rom. It installed and and after staying on boot animation a few minnuts it started.
Thank you so much for your help, really appreciate it
Click to expand...
Click to collapse
no problem. have fun:victory:

skinsfanbdh said:
fastboot erase cache in terminal or with all in one toolkit
Click to expand...
Click to collapse
So I'll try here first. I am having the same issue, I can't get the device to boot into recovery, no matter if I clear the cache, or flash either one of twrp or CWM.
I unlocked the bootloader, I think used the all in one toolkit to flash the recovery. When that didn't work, I erased the cache and manually flashed the recovery, and it said it pushed successfully.
I am at a loss, I have no idea what to try next, any help would be appreciated.
******Finally got it, I had to disable Fast Boot in the Power options in Settings******

How do you copy update.zip from external to internal SD?
Sorry if it's a total no-brainer, but how do I manually copy a recovery zip to the internal update.zip? Can I do this from my phone (which is stuck in a bootloop: see below)? Or do I have to use ADB with my computer?
Turbojugend said:
So I'll try here first. I am having the same issue, I can't get the device to boot into recovery, no matter if I clear the cache, or flash either one of twrp or CWM.
I unlocked the bootloader, I think used the all in one toolkit to flash the recovery. When that didn't work, I erased the cache and manually flashed the recovery, and it said it pushed successfully.
I am at a loss, I have no idea what to try next, any help would be appreciated.
******Finally got it, I had to disable Fast Boot in the Power options in Settings******
Click to expand...
Click to collapse
My situation:
Using Open Recovery I tried to install CM7 with custom kernel on my XT720
It gave an error: "assert failed: write_raw_image... Status 7" As I was looking that up, my phone blackscreened. After a while I pulled the battery.
Then on startup it went into a bootloop after a picture of a broken screen saying "2ndboot kernel restart in progress." (Presumably the kernel wasn't properly applied?)
Trying to boot into bootloader says battery is too low.
Phone will only turn on when plugged into outlet.
What I think I need to do:
- Copy a good update from my external SD over the bad update.zip on the internal SD, and apply the update to reset the kernel, etc.
- Open Recovery could do this, if I could load it.
- I could load Openrecovery if I could get the bootloader to run,
- I could get the bootloader to run if my battery would charge

Doesn't go into recovery

I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?

It is most likely you did something wrong when you flashed the recovery img, just follow the tuto again and make sure to follow each step.
Here is a guide made by mike: http://forum.xda-developers.com/showthread.php?t=2265618

I have done that. Tried a few times. I am fairly "in the know" with rooting ect, but I just can't figure this out.

Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta

Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.

samflorin said:
Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Tried that.
TarekElsakka said:
Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.
Click to expand...
Click to collapse
Tried that to.
When I press perm root, it just reboots normal like recovery doesn't even exist.

Have you tried flashing stock recovery and trying to boot in it? I know that doesn't fix anything, I am just curious if your device will actually boot into any recovery state at all. I have read on XDA about some devices not being able to boot into recovery for some reason.
Here's the stock recovery, just in case: http://forum.xda-developers.com/showthread.php?p=38504123

Okay give me a shot at that.
I noticed after flashing recovery, mine doesn't tampered like it should?

The stock recovery says it's not available anymore.

If it doesn't say TAMPERED then the recovery must have not been flashed to begin with and that is why it's not booting into it. Which recovery are you trying to install? I use TWRP 2.5.0 and I flashed it with fastboot then restarted and it booted fine. My device is S-ON, by the way, and running Trickdroid 7.5.
US Developer Edition Recovery: http://d-h.st/b5g
T-Mobile Recovery: https://www.dropbox.com/s/hvs38223dfrzsny/recovery_tmobile.img
I am not sure if either one will work with your device since I am guessing it's international? But they might be worth a shot.
Never mind, I found the stock international recovery for you: https://dl.dropboxusercontent.com/u/22045273/htc1-stock-recovery.img it was on page 4 of the thread. Give it a go.

I flashed the stock recovery and it still boots like there is no recovery there. and it doesn't say "tampered"
This is crap
EDIT: Yeah I figured it's not being flashed since it's not tampered, but no matter what I try it won't flash.
I'm navigating to the folder: CD C:\One_All-In-One_Kit_v\Data\Recoveries then typing fastboot flash recovery recovery.img and it doesn't work.
It says it's flashed ect, but doesn't boot into it, nore show tampered.

This is very weird and unfortunately I do not know the solution to that. I do not use the All-In-One-Kit, actually, but just a mini-SDK with fastboot files inside. I use shift + right click and "open command prompt window here" rather than navigate to the location, it's just much easier that way. Can you try flashing the latest TWRP recovery?

aussiesausage said:
I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?
Click to expand...
Click to collapse
Are you under s-off ?

tash2013 said:
Are you under s-off ?
Click to expand...
Click to collapse
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.

Would ADB be any better?

Ugh man that's horrible. I honestly do feel your frustration because I have faced similar situations with my HTC devices (One X and One) countless times, and it sucks because you know the correct steps yet it's not working. I sure hope someone knowledgeable about this can come in and help you. Best of luck.
EDIT: I have only used ADB to sideload a ROM but I don't know about flashing recoveries. If you know how to do it, then why not? It's worth a shot for sure.
EDIT #2: And if you're not familiar with ADB, this article should get you started: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Make sure you follow all the steps to the word and also install HTC Sync Manager for the proper drivers to be loaded.

I know right, driving me nuts.
I've never done adb to flash a recovery before but don't know if I would want to be the pidgeon to try lol

aussiesausage said:
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.
Click to expand...
Click to collapse
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again

tash2013 said:
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again
Click to expand...
Click to collapse
Tried that, no go.
Also checked the drivers, re-installed no go.
I am quite up there with adb, but not with flashing recovery with a HTC device lol.

There seems to be another method for flashing recoveries besides fastboot.
http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html
This is an HTC Evo section but it could work for the One as well, although I am not sure of it. I have done some Googling and I did not come across any articles/threads saying that it is possible to flash a recovery using ADB, so that might not be possible.

[Q] Help: Can't get to recovery or system?!?!?

Hi, Gang... Please be patient as I'm not normally playing at this level...
I recently had a kid kill my TF700 so I bought at TF701 as a replacement. I immediately unlocked it, forgetting to take the latest Asus update OTA beforehand. Anyways, I manually downloaded v11.4..1.17 and put it on a blank microSD and stuck it into the tablet where the update was recognized as available and I set the update in motion... Something went sideways after I walked away to let the update run and now I can't get back into the system and I can't get into recovery.
I have the bootloader up (1.00e as released by 10.14.1.47) and I can communicate with the device via fastboot. Can someone help me wipe and get a recovery.img and/or a full stock image onto this thing. Right now it just keeps rebooting unless I manually force it to the bootloader.
I'm hoping someone more knowledgeable can chastise me for being a moron an point me in the right direction. Ultimately, I was tying to get to the latest ASUS ROM to the the bootloader that goes with it and then move onto a custom ROM.
Many thanx.

Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
---------- Post added at 08:27 PM ---------- Previous post was at 08:19 PM ----------
I wouldnt flash a recovery/bootloader especially the new ones til you can verify an older recovery works. Try booting this one https://www.dropbox.com/s/il2m4rtxlmzjfz9/recovery.img but dont flash til someone else takes a look at this. This is an old philz touch without touch.

Still nothing...
YayYouFixedIt said:
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
I'm really starting to get frustrated... (understatement)
I've got a copy of the 4.4.2 OTA image (zip and recovery.img). Should I not be able to use ADB to copy the image to the device and then boot the recovery.img? I can get the tablet to respond to fastboot but I can't get it to be recognized by ADB.
I've never had issues with custom ROMs before. This time I'm wading into unfamiliar waters. I'm note even sure how the initial update failed. Is there a way for me to update the bootloader, then add a CWM recovery, then load the ROM?
Again sorry to have to ask but any help would greatly be appreciated.
Click to expand...
Click to collapse

kartman_canada said:
YayYouFixedIt said:
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
I'm really starting to get frustrated... (understatement)
I've got a copy of the 4.4.2 OTA image (zip and recovery.img). Should I not be able to use ADB to copy the image to the device and then boot the recovery.img? I can get the tablet to respond to fastboot but I can't get it to be recognized by ADB.
I've never had issues with custom ROMs before. This time I'm wading into unfamiliar waters. I'm note even sure how the initial update failed. Is there a way for me to update the bootloader, then add a CWM recovery, then load the ROM?
Again sorry to have to ask but any help would greatly be appreciated.
Click to expand...
Click to collapse
Where did you get the full firmware update you tried to flash?
I can't find a recovery that is compatible with that old bootloader, so your best bet would be to update via Asus firmware.
What happens if you choose RCK in the bootloader menu? Is the stock recovery still working?
What's your SKU?
If the manual stock update doesn't work you may have to flash the system blob in fastboot, but answer above questions first and then we'll see.
If you're getting frustrated, stop and come back to it later. Don't do anything desperate! No reason for it yet.
Click to expand...
Click to collapse

kartman_canada said:
YayYouFixedIt said:
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
I'm really starting to get frustrated... (understatement)
I've got a copy of the 4.4.2 OTA image (zip and recovery.img). Should I not be able to use ADB to copy the image to the device and then boot the recovery.img? I can get the tablet to respond to fastboot but I can't get it to be recognized by ADB.
I've never had issues with custom ROMs before. This time I'm wading into unfamiliar waters. I'm note even sure how the initial update failed. Is there a way for me to update the bootloader, then add a CWM recovery, then load the ROM?
Again sorry to have to ask but any help would greatly be appreciated.
Click to expand...
Click to collapse
https://www.dropbox.com/s/il2m4rtxlmzjfz9/recovery.img
download this recovery(which is an older one compatable with that bootloader and try fastboot boot recovery.img from your older bootloader.
It should work. If you can determine that it works and all your partitions are intact. The command is" fastboot flash recovery recovery.img" I would think if you can simply get this one to boot it will be ok to flash and you should be able to flash whatever you want. Namely you will want to flash the new bootloader and recovery from the flashable zip that sbdags provides from his optimized asus stock.
If you have to adb sideload a rom from within the recovery. Then download just use the cm11 rom for now because the asus stock is over a gig and and might not sideload. the asus stock sbdags provides in this forum.
Otherwise you might be able to flash things from the microsd card.
Than if you decide to go the cm11 route. just download the asus stock from this forum from inside the rom. Be careful.
Click to expand...
Click to collapse

Fixed!
YayYouFixedIt said:
kartman_canada said:
download this recovery(which is an older one compatable with that bootloader and try fastboot boot recovery.img from your older bootloader.
It should work. If you can determine that it works and all your partitions are intact. The command is" fastboot flash recovery recovery.img" I would think if you can simply get this one to boot it will be ok to flash and you should be able to flash whatever you want. Namely you will want to flash the new bootloader and recovery from the flashable zip that sbdags provides from his optimized asus stock.
If you have to adb sideload a rom from within the recovery. Then download just use the cm11 rom for now because the asus stock is over a gig and and might not sideload. the asus stock sbdags provides in this forum.
Otherwise you might be able to flash things from the microsd card.
Than if you decide to go the cm11 route. just download the asus stock from this forum from inside the rom. Be careful.
Click to expand...
Click to collapse
Managed to fastboot to the older recovery.img. As per instructions, I then flashed the latest bootloader and recovery from sbdags. I'm now good to go with whatever ROM I want. Many thanx! I'd still like to know how the upgrade to the latest Asus update screwed up. I wasn't watching it after setting the update in motion so it's a mystery. All I know is that the unit was plugged in so it wouldn't run out of juice and when I came back to check it, it wouldn't boot to Android, I couldn't get to recovery, and it would just keep rebooting in a loop.
Lucky for me it was unlocked and I had fastboot access to the (albeit out-of-date) bootloader.
All good now. Cheers.
Click to expand...
Click to collapse

kartman_canada said:
YayYouFixedIt said:
Managed to fastboot to the older recovery.img. As per instructions, I then flashed the latest bootloader and recovery from sbdags. I'm now good to go with whatever ROM I want. Many thanx! I'd still like to know how the upgrade to the latest Asus update screwed up. I wasn't watching it after setting the update in motion so it's a mystery. All I know is that the unit was plugged in so it wouldn't run out of juice and when I came back to check it, it wouldn't boot to Android, I couldn't get to recovery, and it would just keep rebooting in a loop.
Lucky for me it was unlocked and I had fastboot access to the (albeit out-of-date) bootloader.
All good now. Cheers.
Click to expand...
Click to collapse
Good to hear. For the Asus updates you just put them in /sdcard and reboot dont you? Its fairly automatic wasnt it? Then unlock after being updated? What went wrong in your case, Hard for me to say i guess because I and others unlocked at or before 4.3.
Click to expand...
Click to collapse

[Q] After flashing TWRP, XT1063 only boots to the unlocked warning screen

My apologies if this has already been posted. I've been looking all morning but haven't seen anyone with the same issue.
Unlock bootloader: no problem.
Flash TWRP: I downloaded from http://teamw.in/project/twrp2/275, and I got an error about partition size mismatch, but that's ok, right?
But when I try to enter recovery, all I get is the warning screen that my phone is unlocked. The drivers are certainly installed correctly, and fastboot is working fine. I just can't get into recovery to flash a ROM!

Restoring to 4.4.4 stock worked like a charm.
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I've re-enabled USB debugging. Do I dare try to flash a custom recovery again?

Pandae said:
Do I dare try to flash a custom recovery again?
Click to expand...
Click to collapse
You can use Flashify to make a backup of your current recovery and to flash TWRP.img. should work like a charm.

But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.

Pandae said:
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Click to expand...
Click to collapse
You're right. Latest motorola driver and [TOOL]Minimal ADB and Fastboot will do the trick.

Sorry, I should have clarified that when flashing TWRP, I've already been using fastboot.exe from a command line (and administrator level), with the drivers correctly installed. That's how I was able to unlock in the first place.
I did try it with the version of Fastboot you linked to (what I have works peachy for my Nexus 7), still the same thing. I can't boot into recovery and only get stuck at the Motorola unlocked warning.

Pandae said:
I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Click to expand...
Click to collapse
Oh. Sorry. Can you post the output (terminal & device) of
Code:
fastboot devices
fastboot flash recovery NAME_OF_RECOVERY.img

I'd done "fastboot devices" already to verify, and it returns the serial number, though as I said it's clearly working since I was able to unlock as well as flash recovery. I'm flashing "TWRP2801-titan-motog-2014.img" that I downloaded from the TWRP site, and fastboot gives the standard messages about size and success (and my phone gives the size mismatch error).
It's so strange to me. I've flashed a custom recovery dozens of times on both generations of my Nexus 7s, but I've never seen this.

Pandae said:
It's so strange to me.
Click to expand...
Click to collapse
Yeah......have to meditate about that problem....... is your battery low? Fastboot mode of the device gives me all sorts of problems if it detects low battery

I had been using fastboot at 100% (literally finished a full charge) and 84%, but thanks for the continued attempts at explanation.

Oh, did you check the md5 checksum of your download?

Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?

Pandae said:
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Click to expand...
Click to collapse
If you are willing to risk it, try a fresh download and try again. I've flashed TWRP more than 20 times by now and never recieved an error whatsoever. It basically the easiest thing to do.
Incase you are stuck again, don't reflash the entire stock rom. Just flash the recovery.img from the stock rom files.
OR
Try this:
HOW TO ROOT MOTO G 2014 with Temporary Custom Recovery
Cheers

I've flashed a custom recovery many a time and have helped people through it, though on Nexus 7s.
Now shall I compound the mystery? I didn't think yet to use ADB to make my phone reboot to recovery. I had assumed recovery wasn't working. So here we go, after booting into Android:
adb reboot devices: my phone's there.
adb reboot recovery: TWRP's working?! And now root is complete!
It doesn't make sense to me why I can't get into recovery from the bootloader, but I can get into it with the simple ADB command. But I appreciate all the help, thanks!

Pandae said:
It doesn't make sense to me why I can't get into recovery from the bootloader
Click to expand...
Click to collapse
A little workaround:
Install Android Terminal Emulator
Add "Term shortcut" widget.
In "Arguments" enter
Code:
su -c reboot recovery

bootloop. & bootloader is locked. And I do not have usb debugging enabled

bootloop. & bootloader is locked. And I do not have usb debugging enabled. Any way to get around this?

Depends... You're quite sparse with information about what you've done to get to where you are and about your setup.
A few options come to mind. If you have TWRP you can try flashing a custom rom zip and that could fix it. You could also try the special N preview OTA that google provided to fix phones that got screwed up by an N OTA. http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660

Yeah sorry about that. While updating to 6.0 the phone died. And is now stuck in a bootloop (stuck at the google logo screen). I was trying to use nexus root toolkit to flash stuck android back onto it, however my bootloader is locked. And I did not have usb debugging enabled either. So I am trying to find a way to unlock my bootloader. If that makes any sense

Use the second method I suggested. Should work.

Can you get in bootloader or recovery mode?
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660
Try to sideload shamu-ota-npc91k-201dd8d1.zip. (This upgrades to Android N Preview.)

Since the OTA is a complete image, it should restore the device to working condition. Then you should be able to enable USB debugging and OEM unlock so the bootloader can be unlocked through fastboot.

Sorry for the late replies. I am attempting the second method & I am able to boot into recovery mode. However I keep getting "adb server is out of date" so I am trying to work it out at the moment

This worked for me! Locked bootloader, no usb debugging, no custom recovery, stuck in bootloop due to software issues.

Bootloader showing engineering
Hi,
I-ve attempted to do the manual upgrade from Android 5.0 to 6.0.1, when running the restart on my Motorola Nexus 6. the screen is showing Bootloader status> Engineering mode.
Somebody told me I would not be able to update this phone because is a prototype or something like that, I need help with this.... thank you!!

Warhammer143 said:
Hi,
I-ve attempted to do the manual upgrade from Android 5.0 to 6.0.1, when running the restart on my Motorola Nexus 6. the screen is showing Bootloader status> Engineering mode.
Somebody told me I would not be able to update this phone because is a prototype or something like that, I need help with this.... thank you!!
Click to expand...
Click to collapse
have you tried manually flashing/updating your bootloader, via fastboot or flashable zip?

simms22 said:
have you tried manually flashing/updating your bootloader, via fastboot or flashable zip?
Click to expand...
Click to collapse
tried many things but not sure..
Is there any thread where I can find the instructions???

Warhammer143 said:
tried many things but not sure..
Is there any thread where I can find the instructions???
Click to expand...
Click to collapse
well, instructions, probably not. if its a flashable zip, that means that you can use twrp recovery to flash it. fastboot flashing has to be done while youre in the bootloader, using fastboot. the command is.. fastboot flash bootloader zipname.img

right now am using nexus root toolkit V 2.1.6.....
look. I am really a noob on this topic .... don't know what to do....

Warhammer143 said:
right now am using nexus root toolkit V 2.1.6.....
look. I am really a noob on this topic .... don't know what to do....
Click to expand...
Click to collapse
well, being a noobie, use google to find out about twrp recovery and about fastboot flashing. fastboot flashing would be more important to you, as twrp recovery use is simple when you already have it installed. unfortunately, im at work at the moment, so cant really help out to much.

simms22 said:
well, being a noobie, use google to find out about twrp recovery and about fastboot flashing. fastboot flashing would be more important to you, as twrp recovery use is simple when you already have it installed. unfortunately, im at work at the moment, so cant really help out to much.
Click to expand...
Click to collapse
Well, I will be searching on google, but thanks a lot!