Database Develop

[Q] N6 is just DEAD,,, NOT OPERATING AT ALL(HELP!)

Hello, everyone.
So, about an week ago, I posted a thread to ask for your help regarding my broken N6. Since then, nothing has changed(but got worse, I guess...?). Here is what is happening with my N6 right now.
1) It powers up(thank god) but goes straight to the boot-loader screen(I believe this means that my device doesn't have system image file within the device)
2) On boot-loader menu(Start, Restart bootloader, Recovery mode, Power off, Factory, Barcodes, BP Tools, QCOM, Bootlaoder logs), only few are working(Restart bootlodaer, Power off, Barcodes). When I try to perform other than these, it just goes back to main boot-loader screen.
3) I tried to use both Nexus Root Tool kit and manual installation of each image but doesn't work for both of them(From this, I believe that my phone is just BROKEN)
With this happening, conclusion that I can think of is
1) There is no 'Recovery' available in my device(that's why I can't do anything to recover my device)
2) ADB is not functioning.
Only solution that I can think of from this point is that contact Motorola and replace my device(which is what I am currently doing but Motorola has huge problem with their customer service that I am waiting for their answer for about 2 weeks now)
If possible, would there other options that I can repair this device by myself?
I appreciate your attention.
Sincerely.

Adb has no impact on bootloader. What do you mean doesn't work when you fastboot the factory image?
Sent from my Nexus 6 using XDA Free mobile app

your problem is the use of toolkits. stay away from them, unless you know what you are doing!
your phone doesnt have any rom on it. you can.. 1. flash the factory img via fastboot, like you are supposed to do(not via a toolkit), or 2. unlock the bootloader, flash a custom recovery then while in the custom recovery adb push a rom, gapps, and supersu and flash them that way. what you did does not give you the right for a trade in.

The two previous posters are correct. You just need to fastboot flash the factory rom and factory recovery. It is fairly simple, if you take the time to read how to do it. There are posts all over XDA for beginners on how to do this. And I cannot stress how correct @simms22 is. Toolkits may seem to make things easy, but when there is a problem, you need to know how to manually fix it. I just personally stay away from toolkits. And I was in your shoes. I didn't know jack about flashing roms and such. Just reading XDA got me to where I am. (and i am still learning!)

Like the others have pointed out, you are fine. You have access to your bootloader screen, this is a Nexus. Take a deep breath. Take some time and read this site about flashing a factory image. Please do it the best way - manually with fastboot commands. If you get stuck come back here and someone will help. It really is easy. Please repeat after me "I will avoid all toolkits from now one".
Start with this and read lots.
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

Flashing the factory image should still work from boot loader with fast boot.
Follow the second link for manual flashing after downloading the zip from the first link.
https://developers.google.com/android/nexus/images
If you run into the missing system.img problem here is the link to fix it:
http://www.androidpolice.com/2014/11/12/running-into-the-dreaded-missing-system-img-error-flashing-android-5-0-factory-images-heres-how-to-get-around-it/
This way you can start from the beginning.

Problem with flashing factory image manually.
First, thanks everyone for helping me by providing useful information but there is a problem when I flash factory image manually.
Whenever I try to flash image(for example, 'boot.img', or other images, I always get the same error 'FAILED <remote failure>' and not installed on my device. From here, I have no idea what to do.

chg911225 said:
First, thanks everyone for helping me by providing useful information but there is a problem when I flash factory image manually.
Whenever I try to flash image(for example, 'boot.img', or other images, I always get the same error 'FAILED <remote failure>' and not installed on my device. From here, I have no idea what to do.
Click to expand...
Click to collapse
first off, does fastboot see your device?? you can check by typing.. fastboot devices
if it doesnt see your device, do you have the driver instslled?

simms22 said:
first off, does fastboot see your device?? you can check by typing.. fastboot devices
if it doesnt see your device, do you have the driver instslled?
Click to expand...
Click to collapse
fastboot detects my device. but when I tried to TWRP recovery, it shows following error.
sending 'recovery' <11668 KB>...
OKAY [ 0.375s]
writing 'recovery'...
<bootloader> Failed to erase partition
<bootloader> Failed to flash partition recovery
FAILED <remote failure>
finished. total. time: 6.133s

chg911225 said:
fastboot detects my device. but when I tried to TWRP recovery, it shows following error.
sending 'recovery' <11668 KB>...
OKAY [ 0.375s]
writing 'recovery'...
<bootloader> Failed to erase partition
<bootloader> Failed to flash partition recovery
FAILED <remote failure>
finished. total. time: 6.133s
Click to expand...
Click to collapse
look for the command to erase the recovery partition. youll have to google it as i dont know(or remember) it. i dont even own a computer :angel:
then youll have to reflash the recovery.

simms22 said:
look for the command to erase the recovery partition. youll have to google it as i dont know(or remember) it. i dont even own a computer :angel:
then youll have to reflash the recovery.
Click to expand...
Click to collapse
found the command "fastboot erase recovery" but not working with following error message.
fastboot erase recovery
erasing 'recovery'
<bootloader> Erase allowed in unlocked state
<bootloader> Failed to erase partition
FAILED <remote failure>
finished. total time: 5.763s
*my phone is unlocked for sure(I checked 'fastboot oem unlock' and it said
fastboot oem unlock
...
<bootloader> Device already unlocked!
FAILED<remote failure>
finished. total time: 0.003s

​
chg911225 said:
found the command "fastboot erase recovery" but not working with following error message.
fastboot erase recovery
erasing 'recovery'
<bootloader> Erase allowed in unlocked state
<bootloader> Failed to erase partition
FAILED <remote failure>
finished. total time: 5.763s
*my phone is unlocked for sure(I checked 'fastboot oem unlock' and it said
fastboot oem unlock
...
<bootloader> Device already unlocked!
FAILED<remote failure>
finished. total time: 0.003s
Click to expand...
Click to collapse
i have no idea, but this is a good thread to read and post questions about fastboot in http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500

RIP. What did you do to your N6?

OP how did you install your fastboot. I would assume you did it from within a toolkit. That is probably your problem. If that is the case, please do this. Go here and install the .exe: http://developer.android.com/sdk/index.html#Other
It's big I know it but just do it please.
Make sure everything (SDK) gets installed in a folder path like c:\android or something you will easily remember. This is very important because it is within this folder you will place the extracted factory image files (.img). Place all full unzipped .img files in this folder.
Please follow method #2 in this excellent guide:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

zetsumeikuro said:
RIP. What did you do to your N6?
Click to expand...
Click to collapse
One day it just shut down by itself and since then it's like this. I just contact Motorola and they are going to ship me new device with different color(idk y they are still having problem with their stocking their devices in because what I had was Cloud White 32Gb but only model that were present when I contact them was Midnight blue with 32Gb, other options are all out of stock. really wished they had a white color...)

This phone is a damn Nexus, it can't die. It's user error.
Sent from my Nexus 6

[Q] stuck after factory reset with "unfortunalty phone has stopped"

AT&T Nexus 6, not rooted, bootloader unlocked.
I flashed the latest Android build LMY47i . Everything seemed to go fine. When the phone booted the first time i got an error "Unfortunately NFC service has stopped." click OK then get "Unfortunately phone has stopped." click ok, rinse and repeat. I cannot get past that error in the setup. eventually It just keeps re-booting.
I booted to recovery and cleared cache. Same issue.
Factory reset from recovery. Same issue.
Booted to safemode. same issue.
USB debugging is not turned on so I cannot get my computer to talk to the phone via USB.
any help much appreciated!
Berk

Berk8520 said:
AT&T Nexus 6, not rooted, bootloader unlocked.
I flashed the latest Android build LMY47i . Everything seemed to go fine. When the phone booted the first time i got an error "Unfortunately NFC service has stopped." click OK then get "Unfortunately phone has stopped." click ok, rinse and repeat. I cannot get past that error in the setup. eventually It just keeps re-booting.
I booted to recovery and cleared cache. Same issue.
Factory reset from recovery. Same issue.
Booted to safemode. same issue.
USB debugging is not turned on so I cannot get my computer to talk to the phone via USB.
any help much appreciated!
Berk
Click to expand...
Click to collapse
Boot to bootloader. Use fastboot. fastboot format userdata and fastboot format cache.

Evolution_Freak said:
Boot to bootloader. Use fastboot. fastboot format userdata and fastboot format cache.
Click to expand...
Click to collapse
I am at the bootloader but when I send fastboot commands from the console (windows7) i get "waiting for device"? USB debugging is not turned on becuase I cannot get to the menu.

Berk8520 said:
I am at the bootloader but when I send fastboot commands from the console (windows7) i get "waiting for device"? USB debugging is not turned on becuase I cannot get to the menu.
Click to expand...
Click to collapse
What happens when you type fastboot devices?

Evolution_Freak said:
What happens when you type fastboot devices?
Click to expand...
Click to collapse
no devices are listed.

Berk8520 said:
no devices are listed.
Click to expand...
Click to collapse
rebooted computer. No fastboot sees the device. Going to try a cleaning the cache and user data now.

Berk8520 said:
no devices are listed.
Click to expand...
Click to collapse
You shouldn't need USB debugging from bootloader for fastboot to work. Try installing ADB and fastboot system wide with this:
http://forum.xda-developers.com/showthread.php?t=2588979

That seemed to work. I am now trying to flash the image again. The bootloader and radio go fine.
When I flash the sytem image I get the following error
(bootloader) Permission Denied
Failed (remote failure)

Berk8520 said:
That seemed to work. I am now trying to flash the image again. The bootloader and radio go fine.
When I flash the sytem image I get the following error
(bootloader) Permission Denied
Failed (remote failure)
Click to expand...
Click to collapse
Did you reboot to bootloader after flashing bootloader and radio?

Evolution_Freak said:
Did you reboot to bootloader after flashing bootloader and radio?
Click to expand...
Click to collapse
Yes I sent "fastboot reboot-bootloader" after loading bootloader and the radio.

Berk8520 said:
Yes I sent "fastboot reboot-bootloader" after loading bootloader and the radio.
Click to expand...
Click to collapse
Just try fastboot format cache and fastboot format userdata and try to reboot to system.

Still getting the same error and boot loop after clearing the cache and user data.

Berk8520 said:
Still getting the same error and boot loop after clearing the cache and user data.
Click to expand...
Click to collapse
You sure your bootloader is unlocked? Another silly question, you are trying to flash the images individually, right? Not using flash all?

device is UNLOCKED. Status code: 3
Still stuck in the same bootloop

Berk8520 said:
device is UNLOCKED. Status code: 3
Still stuck in the same bootloop
Click to expand...
Click to collapse
Flash TWRP recovery. Wipe and format in TWRP. Download and flash ROM.

locked the bootlaoder and rebooted. Now I have the android icon with the spinning belly.

Berk8520 said:
locked the bootlaoder and rebooted. Now I have the android icon with the spinning belly.
Click to expand...
Click to collapse
Please tell me you did NOT lock the bootloader.
@rootSU @simms22

now when i try to unlock I get failed error
(Bootloader) (remote failure) Check 'allow OEM unlock' in developer options
failed (remote failure)

Berk8520 said:
now when i try to unlock I get failed error
(Bootloader) (remote failure) Check 'allow OEM unlock' in developer options
failed (remote failure)
Click to expand...
Click to collapse
evidently that was a mistake

Berk8520 said:
now when i try to unlock I get failed error
(Bootloader) (remote failure) Check 'allow OEM unlock' in developer options
failed (remote failure)
Click to expand...
Click to collapse
Yes, you may have just bricked yourself.
You can now try this:
http://forum.xda-developers.com/showpost.php?p=60591217&postcount=266
@cam30era
---------- Post added at 07:17 PM ---------- Previous post was at 07:14 PM ----------
You absolutely should NOT have locked your bootloader. Worst thing to do.

Broke the Bootloader???

Long time lurker first time poster, but I need help!!!
Getting tired of waiting for my OTA 7.11 and after a long night at work decided rather than just manually flashing the file that I would use the NRT. I must've encountered an error as it left me in Fastboot so I try to manually flash everything with it being stuck on the "Google" pre-boot screen. I try again with the version that I was on prior to update (NBD91X) and still the same results. Looking at the log from my Command Prompt I notice upon flashing the bootloader I have this error:
sending 'bootloader' (4071 KB)...
OKAY [ 0.219s]
writing 'bootloader'...
(bootloader) Motoboot: invalid GPT
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.408s
I am only able to boot into Fastboot and unable to boot into Recovery. What are my options to getting my N6 back?
Thank you all for the help.

Hi. Download last adb + fastboot executables here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract the files somewhere.
Download Google factory image and extract it in the same folder you have the fastboot executable.
Boot in bootloader "power + volume down" and follow this guide:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I always choose the second option (manually flashing all files).
Good luck..!

5.1 said:
Hi. Download last adb + fastboot executables here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract the files somewhere.
Download Google factory image and extract it in the same folder you have the fastboot executable.
Boot in bootloader "power + volume down" and follow this guide:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I always choose the second option (manually flashing all files).
Good luck..!
Click to expand...
Click to collapse
Thanks for your reply. Even after getting a fresh download of adb/fastboot files I'm still encountering this error when trying to flash the bootloader;
c:\Users\matt\Downloads\platform-tools>fastboot devices
ZX1G3249HB fastboot
c:\Users\matt\Downloads\platform-tools>fastboot flash bootloader C:\Users\matt\D
ownloads\platform-tools\shamu-n6f26r\bootloader-shamu-moto-apq8084-72.01.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.134s]
writing 'bootloader'...
(bootloader) Motoboot: Preflash validation for aboot
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.433s
Any other suggestions?

bootloader is locked correct?

SynisterWolf said:
bootloader is locked correct?
Click to expand...
Click to collapse
The bootloader has been unlocked from the day I took it out of the box. I still have the little "unlocked" icon at the bottom of the "Google pre-boot" screen that it stays stuck at when I try to boot the phone.

Can you issue this command while in bootloader:
fastboot oem device-info
"Remote failure" sounds like as the bootloader is locked...
Also your problem sounds similar to this one:
https://forum.xda-developers.com/nexus-6/help/bricked-t3523844
I really don't know what you can do now sorry

5.1 said:
Can you issue this command while in bootloader:
fastboot oem device-info
"Remote failure" sounds like as the bootloader is locked...
Also your problem sounds similar to this one:
https://forum.xda-developers.com/nexus-6/help/bricked-t3523844
I really don't know what you can do now sorry
Click to expand...
Click to collapse
I just issued the command and got this back:
C:\Users\matt\Downloads\platform-tools>fastboot devices
ZX1G3249HB fastboot
C:\Users\matt\Downloads\platform-tools>fastboot oem device-info
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 'device-info' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.011s
I hope I'm not screwed like the thread you suggested. At this point if I could just get a fresh install I'd be happy with that. Otherwise I guess I could start looking for an N6 replacement...I've put my sim card in my old MotoX 2013 and boy is this phone smaller than I remember.
AGGHHHHH!!! Thanks for your help and please let me know if there is anything else you could suggest for me to try.

Try: fastboot getvar all
Paste the result. Just hide you imei...

5.1 said:
Try: fastboot getvar all
Click to expand...
Click to collapse

I'm not sure, but wasn't it possible to unbrick the n6 by flashing the 7.0 developer preview image????

coremania said:
I'm not sure, but wasn't it possible to unbrick the n6 by flashing the 7.0 developer preview image????
Click to expand...
Click to collapse
That's interesting. I'd be game for whatever weird ass technique there is to get it up and running.

the200sx said:
That's interesting. I'd be game for whatever weird ass technique there is to get it up and running.
Click to expand...
Click to collapse
But I can't find a download of any early preview, maybe a member here has made backup. If you get a copy, try to flash it step by step without inserted simcard
Edit: may najoor has the original file for you
https://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335

coremania said:
But I can't find a download of any early preview, maybe a member here has made backup. If you get a copy, try to flash it step by step without inserted simcard
Edit: may najoor has the original file for you
https://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335
Click to expand...
Click to collapse
I just read through the entire thread, while it sounds like method 2 would most likely be the option considering how I can't get into recovery, I wasn't able to find where anyone talked about it unbricking the phone. At this point I'm ready to try just about anything, but I had hoped there would be a method to keep data. It may have to wait until tomorrow so I can dedicate enough time to it. In the meantime, if anyone can point me into the direction of someone being stuck similarly to me and what they did to get out of it, I would be extremely grateful.
Thanks

Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...

5.1 said:
Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...
Click to expand...
Click to collapse
I'll give it a shot

the200sx said:
I just read through the entire thread, while it sounds like method 2 would most likely be the option considering how I can't get into recovery, I wasn't able to find where anyone talked about it unbricking the phone. At this point I'm ready to try just about anything, but I had hoped there would be a method to keep data. It may have to wait until tomorrow so I can dedicate enough time to it. In the meantime, if anyone can point me into the direction of someone being stuck similarly to me and what they did to get out of it, I would be extremely grateful.
Thanks
Click to expand...
Click to collapse
Ok, I didn't remember this right, the developer preview ota sideloading with adb was for fixing the Google ota update which bricked some devices as the n previews were released.
But you have nothing to loose, so you may try to do this. Here's a working download in the link, if you don't sideloading the userdata your data may stay intact. https://www.reddit.com/r/nexus6/comments/49txh3/bricked_nexus_6_after_android_n_ota_update_stock/

5.1 said:
Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...
Click to expand...
Click to collapse
It looks like it pushed the TWRP recovery but I still can't seem to get it to boot it into recovery. Only the main fastboot screen pops up trying to Power + Vol and when I VOL select it recovery, it will just reboot back to the main fastboot screen.

Damn... Try:
fastboot erase cache
And try to boot in twrp again?

5.1 said:
Damn... Try:
fastboot erase cache
And try to boot in twrp again?
Click to expand...
Click to collapse
That didn't work either. However it made it take a split-second longer to restart, which gave me a moment of hope. Hope Crushed!!!

Last question... When you power your phone, does it stay on Google logo, or boot animation forever? Or directly bootloader?
If one of the first two, is the phone detected on your computer device manager? If yes, how?

Soft Brick Nexus 6 with No Recovery and Bootloop

Hi everyone i got a Nexus 6 that is stuck in bootloop, its on 6.0.1 with january security patch, cant remember which version though. It boots to google and shuts off and boots back up to google, i have tried to reload the software on it by downloading it from google and and installing it, but it always gives me error that because the bootloader is locked it cannot install the s/w even if i choose the newest one. Since it does not go into recovery, i cannot adb sideload the software into it, does anyone have any suggestion on how i can get this phone back up and running again?
I also cannot flash the system img or boot or recovery into the phone because the bootloader is locked.
C:\Users\admin\Desktop\shamu-mob31s-factory-c73a35ef\shamu-mob31s\image-shamu-mob31s>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8901 KB)...
OKAY [ 0.278s]
writing 'recovery'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.297s
C:\Users\admin\Desktop\shamu-mob31s-factory-c73a35ef\shamu-mob31s\image-shamu-mob31s>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8183 KB)...
OKAY [ 0.269s]
writing 'boot'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.269s
thanks

You're screwed.
In situations where there is a locked bootloader and a soft brick like this, sideloading a Google OTA image using the stock recovery would have been able to restore the device to operating condition. Unfortunately you have no recovery, and thus no way to restore this device.

If you are stuck in boot loop and have no recovery, there is a way to fix your problem. If fastboot commands work then download Wugs Nexus Root Toolkit and use that to return to stock. There might be a way to unlock the bootloader first and then go from there. Have you tried to get the bootloader unlocked through fastboot commands then flash TWRP. Dude thinks this through. There is always a way to fix a soft brick. I hard bricked not long ago and was able to fix my device on low level systems code. Just don't give up

Regarding the locked bootloader, the only way that the OP can make changes to the device's system and recovery partitions is if he can unlock the bootloader. To unlock the bootloader a copy of Android must be in the system partition. He would need to enable Developer Options in Settings, then enter Developer Options to enable the OEM Unlock toggle hidden there.
Pretty standard stuff, right? The problem here is that the bootloop the OP encountered is not the typical one. In a normal bootloop, the device enters the boot animation and gets stuck. In this instance, the bootloop as described doesn't even present a boot animation, but immediately flashes the Google logo present in the bootloader repeatedly. This is due to there being no software in the system partition at all. Since there is no OS in the system partition, it's impossible for the OP to enter Developer Options to enable OEM Unlock, which he has to do in order to be able to unlock the bootloader with fastboot.
So, explain how a toolkit which leverages fastboot and ADB to do its work is supposed to help this poster when the naked software Google provides cannot.

Strephon Alkhalikoi said:
Regarding the locked bootloader, the only way that the OP can make changes to the device's system and recovery partitions is if he can unlock the bootloader. To unlock the bootloader a copy of Android must be in the system partition. He would need to enable Developer Options in Settings, then enter Developer Options to enable the OEM Unlock toggle hidden there.
Pretty standard stuff, right? The problem here is that the bootloop the OP encountered is not the typical one. In a normal bootloop, the device enters the boot animation and gets stuck. In this instance, the bootloop as described doesn't even present a boot animation, but immediately flashes the Google logo present in the bootloader repeatedly. This is due to there being no software in the system partition at all. Since there is no OS in the system partition, it's impossible for the OP to enter Developer Options to enable OEM Unlock, which he has to do in order to be able to unlock the bootloader with fastboot.
So, explain how a toolkit which leverages fastboot and ADB to do its work is supposed to help this poster when the naked software Google provides cannot.
Click to expand...
Click to collapse
I flashed a faulty bootloader image via fireflash app instantly bricked. I went through low level fastboot recovery options. I fixed my device. This is a mid level soft brick it can be fixed just needs some patience and perseverance. If fastboot commands are available then he can do a fastboot unlock command and fastboot a TWRP img. It might take some work but it isn't impossible. When I bricked it was a black screen, qhusb Qualcomm level I needed to restore my bootloader, I did it. This guy can fix his situation, I could do it for him if I had the device in hand.

Rondeau79 said:
If fastboot commands are available then he can do a fastboot unlock command and fastboot a TWRP img. It might take some work but it isn't impossible.
Click to expand...
Click to collapse
Look, we can go back and forth on this until blue in the face. The facts of the matter are as follows.
1. The bootloader is locked.
2. There is no OS in the system partition.
3. There is no stock recovery.
4. An OS in the system partition is required to be able to unlock the bootloader.
5. A stock recovery is required to sideload OTA images.
6. The original post does not mention whether the OP tried unlocking the bootloader.
You mentioned Fastboot. Everything you described in the quoted portion of your post works, but only if the bootloader can be unlocked. I'm assuming however the OP tried that already, failed, and went straight into flashing system images. If he didn't try it, he should, although I believe the attempt will fail.

Any help here. I have the exact same situation. Should I take my phone to Motorola/Google for repair? Anything else i can try?

@sumit.nathany: If you are in the same situation (locked bootloader, no OS, no recovery) you'll need to contact Motorola. But it won't hurt to try unlocking the bootloader before you do.
The only other option requires hardware hacking, and both the tools and methods can't be discussed here (against XDA rules).

Not that I know much about this, but what about the fastboot boot recovery.img command? If used with a Google recovery image, it might get around the bootloader lock?

Fastboot boot recovery.img doesn't work with a locked bootloader.
Think of the ramifications. If one could simply fastboot boot a TWRP image, it would be possible to root the device without unlocking the bootloader. That would mean every AT&T and Verizon device could be rooted as well as devices from Samsung, Huawei, and Lenovo, all of which lock their bootloaders. The carriers would not be happy, and the OEMs that lock their bootloaders won't be happy either.

Strephon Alkhalikoi said:
Fastboot boot recovery.img doesn't work with a locked bootloader.
Think of the ramifications. If one could simply fastboot boot a TWRP image, it would be possible to root the device without unlocking the bootloader. That would mean every AT&T and Verizon device could be rooted as well as devices from Samsung, Huawei, and Lenovo, all of which lock their bootloaders. The carriers would not be happy, and the OEMs that lock their bootloaders won't be happy either.
Click to expand...
Click to collapse
Making it work, but only with an original recovery from Google, would not open any opportunities.
BTW, do you, or anyone else have any theories why this happens? Hardware error?

It probably could be made to work, but then you'd run into an issue of people spoofing the stock recovery, which would still open up the whole can of worms. Better to simply block the ability completely unless the bootloader is unlocked.
As to how this happened I will not speculate. Reason being that any speculation would be useless without seeing the devices firsthand and examining them. Not to mention the people that would be throwing hissy fits thinking I accused them of something. All that really matters here is that a device in this state is not something that can be fixed without a trip to the repair center.

fix it
truwrxtacy said:
Hi everyone i got a Nexus 6 that is stuck in bootloop, its on 6.0.1 with january security patch, cant remember which version though. It boots to google and shuts off and boots back up to google, i have tried to reload the software on it by downloading it from google and and installing it, but it always gives me error that because the bootloader is locked it cannot install the s/w even if i choose the newest one. Since it does not go into recovery, i cannot adb sideload the software into it, does anyone have any suggestion on how i can get this phone back up and running again?
I also cannot flash the system img or boot or recovery into the phone because the bootloader is locked.
C:\Users\admin\Desktop\shamu-mob31s-factory-c73a35ef\shamu-mob31s\image-shamu-mob31s>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8901 KB)...
OKAY [ 0.278s]
writing 'recovery'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.297s
C:\Users\admin\Desktop\shamu-mob31s-factory-c73a35ef\shamu-mob31s\image-shamu-mob31s>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8183 KB)...
OKAY [ 0.269s]
writing 'boot'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.269s
thanks
Click to expand...
Click to collapse
I found a solution for this problem i know is late in the game but better late than never jijiji

Did you try unlocking the device with?
Code:
fastboot oem unlock

Zombie

Rezz577 said:
fix it
I found a solution for this problem i know is late in the game but better late than never jijiji
Click to expand...
Click to collapse
Hi sir.
Can you tell me the solution, please?
I am in yhe same situation, no recovery and bootloader locked, and bootloop
i wait for your answer

[GUIDE] Temporary unlock bootloader to flash partitions on Nougat

This guide won't work with OFFICIAL Oreo. I've also made a batch script for this so you don't have to type though
This is the new guide for TWRP without the need of OST. I'll cover the other thread later
What you need:
-Service bootloader which is in the attachment, just delete the .zip extension
-ADB: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Nokia driver, available when you plug in the phone
Tutorial:
-Install Nokia driver and ADB first in which way you feel the most convenient
-Plug in your phone after allowing USB Debugging
-Type these commands, each one at a time
Boot your phone to download mode
adb reboot bootloader
Click to expand...
Click to collapse
Get the product ID
fastboot getvar productid
Click to expand...
Click to collapse
It will throw back a string begin with D1A. Copy that string and generate its MD5. I use this service https://md5.gromweb.com
Unlock the bootloader
fastboot oem dm-verity <your MD5 here>
Click to expand...
Click to collapse
When it says failed, your MD5 might be wrong
Flash the service bootloader
fastboot flash aboot <path to mbn file>
Click to expand...
Click to collapse
BE CAREFUL AS CORRUPTED ABOOT MIGHT BRICK YOUR PHONE
If it says OK, proceed to the flashing part, else dm-verity again
Reboot bootloader again
fastboot reboot-bootloader
Click to expand...
Click to collapse
Re-unlock your bootloader
fastboot oem dm-verity <your MD5 here>
Click to expand...
Click to collapse
Congrats! Now you can flash anything you want, shoutout to anyone who provided OST
Note
-Again, special thanks to @heineken78 and @the_laser for their discussion, and anyone involved with the great tool called OST
-The command is found within the file named AdbCmdDll.dll. You can just crack open it with IDA or whatever to find the command yourself
-After flashing, log is in C:\LogData\OUT or OST. Just find the txt file which is about 15KB in size, thanks @hikari_calyx

You mean if I use this option to OEM unlock the boot loader is still locked

Note, doesnt work after Oreo update

heineken78 said:
Note, doesnt work after Oreo update
Click to expand...
Click to collapse
Do you have IDA on your PC?

wolfyapl said:
Do you have IDA on your PC?
Click to expand...
Click to collapse
Yes I have.
Tools "must have":
Beyond Compare, IDA Pro, WinHex.

heineken78 said:
Yes I have.
Tools "must have":
Beyond Compare, IDA Pro, WinHex.
Click to expand...
Click to collapse
Hey, can you patch the exe of OST 6.0.4? Thanks!

wolfyapl said:
Hey, can you patch the exe of OST 6.0.4? Thanks!
Click to expand...
Click to collapse
look here https://forum.xda-developers.com/showpost.php?p=75486360&postcount=64

heineken78 said:
look here https://forum.xda-developers.com/showpost.php?p=75486360&postcount=64
Click to expand...
Click to collapse
Do you know the password of the mbn zip?

Does it work after oreo update... Is there is any way to root oreo

Birbal said:
Does it work after oreo update... Is there is any way to root oreo
Click to expand...
Click to collapse
If you're talking about official Oreo, I'm afraid not

wolfyapl said:
If you're talking about official Oreo, I'm afraid not
Click to expand...
Click to collapse
Thanks bro for the info i am running official oreo btw

I've accidentally tried to do this with the mbn file of Nokia 5 TWRP link of this tread:
https://forum.xda-developers.com/nokia-5/development/root-twrp-nokia-5-t3703423
When I tried to reboot the bootloader, the phone started acting like it's dead and Windows couldn't recognize it anymore. Do you know how I can fix this?

LInk doesn't work
Can someone upload the TWRP link as the above one doesn't work. Thank you!

pls help
after entering "fastboot oem dm-verity e9fcead1112f39bf19a83fc753b4bc1d" it says OK but nothing happens
here:
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot devices
D1AGAD1781632534 fastboot
PS C:\adb> fastboot oem dm-verity e9fcead1112f39bf19a83fc753b4bc1d
...
OKAY [ 0.008s]
finished. total time: 0.010s
PS C:\adb> fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.031s

It shows "Waiting for device"
It shows "Waiting for device"
When i type 2nd command line.
My phone is in download mode after i typed first line.
Please help me , I need to change my imei . So i have to root. But i am not having any proccess. I googled a lot but cant unlock the bootloader.
Even when i tried flashing twrp ,that said the same thing waiting for device in adb command line. :crying:

black screen
my device is on screen deny and windows does not recognize it, nor does it enter download mode with buttons volume up and power

thankyou ... its work for TA-1053

Besides the effort you made to place this into the forum; I disregard having to make click in a Website in Chinese.
Perhaps you know Chinese. Well.. Imagine all the users clicking blindly... Is that safe? Even though you've tested it; it is still pretty uncertain that users will not end with malware.
Or end up with anti privacy on their devices or receiving millions of ads. I honestly find this thread offensive and unsafe to everyone.
If you are the author; a mirror would be nice. Some information regarding TWRP; indicating that the TWRP itself wont be in Chinese.
Therefore i disregard this thread.

wolfyapl said:
It will throw back a string begin with D1A. Copy that string and generate its MD5. I use this service
When it says failed, your MD5 might be wrong
Click to expand...
Click to collapse
Do we need to copy that string in capital or lowercase ?

after the command "fastboot getvar productid", i'm stuck at [waiting for device]... please help me solve this