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

MRA58R Unable to relock bootloader

Hey all. I'm coming back from a custom ROM/kernel and I've successfully flashed the latest factory image. However, fastboot is spitting out an error when I go to relock the bootloader. Here's the output:
C:\Users\***>fastboot flashing lock
...
OKAY [ 0.002s]
finished. total time: 0.003s
After I issue the command my N6's screen goes unresponsive for a few minutes, after which I can still use the volume keys to navigate the bootloader. However, after a reboot, the device is still unlocked.
Has anyone else encountered this issue?

Try using "fastboot OEM lock". Fastboot flashing lock is only for the 5X/6P from what I understand.

pmikec said:
Hey all. I'm coming back from a custom ROM/kernel and I've successfully flashed the latest factory image. However, fastboot is spitting out an error when I go to relock the bootloader. Here's the output:
C:\Users\***>fastboot flashing lock
...
OKAY [ 0.002s]
finished. total time: 0.003s
After I issue the command my N6's screen goes unresponsive for a few minutes, after which I can still use the volume keys to navigate the bootloader. However, after a reboot, the device is still unlocked.
Has anyone else encountered this issue?
Click to expand...
Click to collapse
I don't know why it refuses to relock but another question: why do you want it to be relocked? It is adviced to only relock a bootloader when it is absolutely needed (warranty case, resale...)

Face_Plant said:
Try using "fastboot OEM lock". Fastboot flashing lock is only for the 5X/6P from what I understand.
Click to expand...
Click to collapse
This did the trick. I'm not sure why I didn't just try the old command myself before asking. Thanks!

Bootloader unlocked but failing fastboot of recovery

I have a review phone of the P9 (the 09 version). I'm trying to put a nougat beta on it. Bootloader came unlocked- see attached photo. When i go into bootloader fastboot devices sees it no worries. I ran the bat file to check and yes the bootloader is unlocked according to it.
Problem is that when I try to flash TWRP i get:
Code:
fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery" (22368 KB)...OKAY [ 0.655s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.667s
I am not a noob to hacking android etc that is for sure but this is doing my head in. Is there an issue with the bootloader unlock? I've sent an email to Huawei support people as well. I had issues getting a bootloader unlock code anyway as being in Australia it doesn't allow be to do anything in Huawei ID, so i cannot get the code. I also tried using the beta app but even when using a VPN it was geoblocked.
ideas on what is going wrong?
thanks

Make sure OEM unlock is enabled in developer settings. If you have an app called "Phone Finder" or any other phone tracker app, disable it. If that doesn't work, you can try restoring phone to factory settings and enable OEM unlock again then try again.

I tried the above stuff mate- unfortunately it did not work. only phone finder is android device manager and it is turned off (phone is basically stock). OEM unlock is enabled correctly etc. even factory reset and did it all over again. oh well. i give up for now. i would love root on this too...

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

Bootloop after flashing kernel

To start, I have no knowledge on rooting other than simply using ODIN on one of my older Samsung devices.
I had got a Moto E5 Play the other day and decided to root it today. It was difficult finding a tutorial, but I found this one (https://www.rootingtutorials.com/android-rooting/root-moto-e5-play/)
I downloaded the Minimal ADB and Fastboot tool, and flashed the custom ROM that the post recommended me to do. Then downloaded Magisk and I couldn't install it directly as noted in the guide and after some research found out I had to flash it manually, but I only had the stock recovery for some reason. Found another tutorial from this website (https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323)
I flashed the no-verity kernel and now my phone is in a boot loop. I freaked out and wiped the data and factory reset it. Now when I turn on my phone it says "bad key" in the top left corner and then it goes to the screen before the boot animations and stays there (motorola logo and powered by android at the bottom)
I am an idiot and shouldn't have done this. Is there anything I can do to fix it?

j256 said:
To start, I have no knowledge on rooting other than simply using ODIN on one of my older Samsung devices.
I had got a Moto E5 Play the other day and decided to root it today. It was difficult finding a tutorial, but I found this one (https://www.rootingtutorials.com/android-rooting/root-moto-e5-play/)
I downloaded the Minimal ADB and Fastboot tool, and flashed the custom ROM that the post recommended me to do. Then downloaded Magisk and I couldn't install it directly as noted in the guide and after some research found out I had to flash it manually, but I only had the stock recovery for some reason. Found another tutorial from this website (https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323)
I flashed the no-verity kernel and now my phone is in a boot loop. I freaked out and wiped the data and factory reset it. Now when I turn on my phone it says "bad key" in the top left corner and then it goes to the screen before the boot animations and stays there (motorola logo and powered by android at the bottom)
I am an idiot and shouldn't have done this. Is there anything I can do to fix it?
Click to expand...
Click to collapse
Restore the stock firmware using the instructions here: https://forum.xda-developers.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901

konradsa said:
Restore the stock firmware using the instructions here: https://forum.xda-developers.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901
Click to expand...
Click to collapse
Thanks for replying.
I can't do this because I hard reset the phone and USB debugging is no longer on. "adb devices" recalls back nothing and inputting something like "adb reboot recovery" comes back with "no devices/emulators found".
Tried to input "fastboot flash partition gpt.bin" and get back:
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.047s
What can I do?

j256 said:
Thanks for replying.
I can't do this because I hard reset the phone and USB debugging is no longer on. "adb devices" recalls back nothing and inputting something like "adb reboot recovery" comes back with "no devices/emulators found".
Tried to input "fastboot flash partition gpt.bin" and get back:
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.047s
What can I do?
Click to expand...
Click to collapse
Did you boot the phone into fastboot mode? You don't need debugging on for fastboot.
The ,"bad key" is normal.

Looks like the wrong firmware or your bootloader is still locked

j256 said:
To start, I have no knowledge on rooting other than simply using ODIN on one of my older Samsung devices.
I had got a Moto E5 Play the other day and decided to root it today. It was difficult finding a tutorial, but I found this one (https://www.rootingtutorials.com/android-rooting/root-moto-e5-play/)
I downloaded the Minimal ADB and Fastboot tool, and flashed the custom ROM that the post recommended me to do. Then downloaded Magisk and I couldn't install it directly as noted in the guide and after some research found out I had to flash it manually, but I only had the stock recovery for some reason. Found another tutorial from this website (https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323)
I flashed the no-verity kernel and now my phone is in a boot loop. I freaked out and wiped the data and factory reset it. Now when I turn on my phone it says "bad key" in the top left corner and then it goes to the screen before the boot animations and stays there (motorola logo and powered by android at the bottom)
I am an idiot and shouldn't have done this. Is there anything I can do to fix it?
Click to expand...
Click to collapse
you need to download 'lenovo moto smart assistant. when you opened the application you need to go to the rescue page. then click on moto phone and select your model. once the download is completed you need to click on rescue and the rescue will begin. after the rescue is completed you can boot your phone like it usually does.

This thread is one and half years old.
Sent from my jerry_cheets using XDA Labs