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

Random bootloop. Need help.

So, I was BROWSING REDDIT, and an app starts downloading in the background. Which somehow caused google play services to crash, along with everything running on my phone. Then bootloop. Completely unprompted. Still at a loss here.
My nexus 6 is unlocked, no custom kernel or xposed installed, just running AOSiP 3.3 android 6.0.1. havent flashed anything other than that, which i flashed more than a month ago.
So, my troubleshooting thus far.
./fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s
device still says UNLOCKED STATUS CODE 3
next i tried:
./fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (12004 KB)...
OKAY [ 0.378s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.382s
and lastly, I tried:
./fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8196 KB)...
OKAY [ 0.259s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.264s
So, i'm kinda at a loss here. Recovery is failing to mount to storage, etc. Again, I was BROWSING REDDIT and this happened. I'd like to save my data at all costs. if anyone has any ideas, please, I am desperate. thank you.

Sorry but why open a new thread on the same issue? Did you think you would get a different answer than what you were getting in your original thread?

alryder said:
Sorry but why open a new thread on the same issue? Did you think you would get a different answer than what you were getting in your original thread?
Click to expand...
Click to collapse
to condense, summarize and make clear what i have already tried, and to seek further troubleshooting to my issue. there must be someone with an idea of how to fix this. if not, does it really hurt the forum? i am a person with a problem, seeking advice.

While I agree it's good to summarize the issue and layout what you've tried to resolve it, it could have been done as a post in your original thread to avoid the clutter of having two threads about the same issue. I also think you got the correct answer in the original thread that, however it happened, your bootloader has somehow became locked and in all likelihood the device is beyond repair. Sorry to say so but that's the way I see it.

alryder said:
While I agree it's good to summarize the issue and layout what you've tried to resolve it, it could have been done as a post in your original thread to avoid the clutter of having two threads about the same issue. I also think you got the correct answer in the original thread that, however it happened, your bootloader has somehow became locked and in all likelihood the device is beyond repair. Sorry to say so but that's the way I see it.
Click to expand...
Click to collapse
how is that even possible?

I'm super curious on what downloaded in the background...
Sent from my Nexus 6 using Tapatalk

MrBlob69 said:
I'm super curious on what downloaded in the background...
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
automatic update of some sort. it crashed my phone as soon as it was finished updating. didnt know a background app update could relock my bootloader and brick my phone. not sure why some are suggesting the bootloader is locked when it still displays status code 3 device is unlocked.

Post a screenshot of the bootloader screen
Sent from my Nexus 6 using XDA Free mobile app

The only thing that I can think of is you could try formatting /system and /boot separately and then try again flashing the system and boot images???
Sent from my Nexus 6 using Tapatalk

MrBlob69 said:
The only thing that I can think of is you could try formatting /system and /boot separately and then try again flashing the system and boot images???
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This won't work as if the bootloader is locked, you cannot wipe/flash img files to the phone.
To answer your question OP, we can't tell you how this happened, or what the download was that happened in the background, we simply weren't there and don't know what you have installed to your phone. This line indicates that "Allow OEM Unlocking" is not enabled in Developer Options:
Code:
(bootloader) [B]Check 'Allow OEM Unlock' in Developer Options.[/B]
FAILED (remote failure)
finished. total time: 0.002s
With that not enabled, you cannot issue:
Code:
fastboot oem unlock
You also cannot flash factory images to the device, or wipe the device either. I'm afraid that this device is bricked since it appears your bootloader is locked.

scottshebs said:
So, I was BROWSING REDDIT, and an app starts downloading in the background. Which somehow caused google play services to crash, along with everything running on my phone. Then bootloop. Completely unprompted. Still at a loss here.
My nexus 6 is unlocked, no custom kernel or xposed installed, just running AOSiP 3.3 android 6.0.1. havent flashed anything other than that, which i flashed more than a month ago.
So, my troubleshooting thus far.
./fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s
device still says UNLOCKED STATUS CODE 3
next i tried:
./fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (12004 KB)...
OKAY [ 0.378s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.382s
and lastly, I tried:
./fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8196 KB)...
OKAY [ 0.259s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.264s
So, i'm kinda at a loss here. Recovery is failing to mount to storage, etc. Again, I was BROWSING REDDIT and this happened. I'd like to save my data at all costs. if anyone has any ideas, please, I am desperate. thank you.
Click to expand...
Click to collapse
i guess all the time i devoted to you yesterday means absolutely nothing to you, and you learned nothing.. thanks

RMarkwald said:
This won't work as if the bootloader is locked, you cannot wipe/flash img files to the phone.
To answer your question OP, we can't tell you how this happened, or what the download was that happened in the background, we simply weren't there and don't know what you have installed to your phone. This line indicates that "Allow OEM Unlocking" is not enabled in Developer Options:
Code:
(bootloader) [B]Check 'Allow OEM Unlock' in Developer Options.[/B]
FAILED (remote failure)
finished. total time: 0.002s
With that not enabled, you cannot issue:
Code:
fastboot oem unlock
You also cannot flash factory images to the device, or wipe the device either. I'm afraid that this device is bricked since it appears your bootloader is locked.
Click to expand...
Click to collapse
forgive me, but how can the phones bootloader lock itself? this is the fastboot screen still saying code 3 unlocked. sorry if i am stubborn, just refusing to believe my 300 dollar device bricked itsself while i literally did nothing. never seen anything like this.

31ken31 said:
Post a screenshot of the bootloader screen
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
just posted, still status code 3.

Thread closed.
Not sure why the OP started 2 similar threads (like THIS) and ignored the help provided already....

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...

Data recover from a dead ALE-L21 P8Lite

Hello guys. Thanks for tacking a look at this thread.
I have a P8Lite ALE-L21 that some time ago I seat my ass on it and screen broke and even bend a bit the frame. I have lots of pictures from a trip that I´m desperate thinking that maybe I will lose them.
First of all I brought a new frame with new screen. Replace the good looking board to new frame. Tried to turn on the phone and starts to loop trying to boot but never boots. I have read that this is an usual issue with this phones.
Now I´m stuck at the fastboot & rescue mode not knowing what to do next.
Is it possible to restore the phone to factory settings and after that try to recover the pictures? If it´s possible to restore it can someone give me some instruction on how to do it?
I will apriciate all the help from you guys.
Thanks

tcolaco said:
Hello guys. Thanks for tacking a look at this thread.
I have a P8Lite ALE-L21 that some time ago I seat my ass on it and screen broke and even bend a bit the frame. I have lots of pictures from a trip that I´m desperate thinking that maybe I will lose them.
First of all I brought a new frame with new screen. Replace the good looking board to new frame. Tried to turn on the phone and starts to loop trying to boot but never boots. I have read that this is an usual issue with this phones.
Now I´m stuck at the fastboot & rescue mode not knowing what to do next.
Is it possible to restore the phone to factory settings and after that try to recover the pictures? If it´s possible to restore it can someone give me some instruction on how to do it?
I will apriciate all the help from you guys.
Thanks
Click to expand...
Click to collapse
Hmm, if you have twrp dirty flash personas mod. If you don't, try t flash twrp, and after flash the mod. That won't delete your files, only make your phone to boot. Hopefully you had Android 6 already.

tcolaco said:
Hello guys. Thanks for tacking a look at this thread.
I have a P8Lite ALE-L21 that some time ago I seat my ass on it and screen broke and even bend a bit the frame. I have lots of pictures from a trip that I´m desperate thinking that maybe I will lose them.
First of all I brought a new frame with new screen. Replace the good looking board to new frame. Tried to turn on the phone and starts to loop trying to boot but never boots. I have read that this is an usual issue with this phones.
Now I´m stuck at the fastboot & rescue mode not knowing what to do next.
Is it possible to restore the phone to factory settings and after that try to recover the pictures? If it´s possible to restore it can someone give me some instruction on how to do it?
I will apriciate all the help from you guys.
Thanks
Click to expand...
Click to collapse
flash twrp, if your internal storage isnt encrypted then put a microsd card into your phone and copy your data.
Sent from my LG-K220 using XDA Labs

D1stRU3T0R said:
Hmm, if you have twrp dirty flash personas mod. If you don't, try t flash twrp, and after flash the mod. That won't delete your files, only make your phone to boot. Hopefully you had Android 6 already.
Click to expand...
Click to collapse
In the fastboot & rescue mode it the bottom it says in green "PHONE Locked". This might be a problem to flash ?
I run adb and my device is detected if I use "fastboot devices". When I try to run "fastboot flash recovery" it gives me the message below;
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (26000 KB)...
OKAY [ 0.621s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.627s

tcolaco said:
In the fastboot & rescue mode it the bottom it says in green "PHONE Locked". This might be a problem to flash ?
I run adb and my device is detected if I use "fastboot devices". When I try to run "fastboot flash recovery" it gives me the message below;
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (26000 KB)...
OKAY [ 0.621s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.627s
Click to expand...
Click to collapse
Unlock your bootloader... Get the unlock code, unlock it, and than repeat.

D1stRU3T0R said:
Unlock your bootloader... Get the unlock code, unlock it, and than repeat.
Click to expand...
Click to collapse
How do I get the codes ?? can you please clarify me.
Thanks

tcolaco said:
How do I get the codes ?? can you please clarify me.
Thanks
Click to expand...
Click to collapse
Search in the megathread and you will find it

Can't properly re lock bootloader

Hello guys.
So, I recently bought a new phone and thought "let's try rooting my old one" and tried it on my G7+. I ended up not liking out it turned out (Netflix DRM, Vanced didn't work properly, etc).
So I reflashed the stock ROM and put the comand fastboot oem lock.
The thing is, after I boot the device again, all the messages still appear, like Your device has loaded a different operating system" and below that "ID: " (blank) and I also get "Verity mode is set to disable".
The thing is, every tutorial I come across to relock the bootloader(regular G7, G7 Power, G6, etc), says that when you enter the command "fastboot oem lock" two times, the message that you should only flash signed images, does not appear. I instantly get the state flashing_locked, and I can't continue flashing the stock firmware like every other tutorial shows.
In short, once you enter the command "fastboot oem lock", it's locked for good, and you can't do anything unless you unlock it again, starting the whole process again.
The problem is, even with the bootloader locked again, my device still shows as "insecure", Netflix is nowhere to be found on the app store, and the state of my device is not certified.
I wouldn't have unlocked If I knew it was going to be this difficult to get it back. Selling it now would be next to impossible.
Here are some examples of the errors I'm getting:
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) ***************************************
(bootloader) WARNING: This command erases user data!
(bootloader) Please re-run this command to confirm.
(bootloader) ***************************************
OKAY [ 0.022s]
finished. total time: 0.024s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) Bootloader is now locked
OKAY [ 0.045s]
finished. total time: 0.046s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) Already locked
OKAY [ 0.012s]
finished. total time: 0.014s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23537 KB)...
OKAY [ 0.618s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.678s
Click to expand...
Click to collapse
Does anyone know how to fix this?

Did you ever get this sorted ? I have the same problem on my G7 Plus. I unlocked, then loaded Lineagos, but then decided to go back to stock, I used LMSA to rescue the phone, but still got the warning and boot time "Your phone has loaded a different OS" and I can't use GPay. I tried the fastboot OEM lock (worked) and fastboot flashing lock, but I still get the warning and I can't use GPay.
I think in my case the LMSA rescue didn't work because I was originally on Android 9 and the rescue took me straing to Android 10

Elrom said:
Hello guys.
So, I recently bought a new phone and thought "let's try rooting my old one" and tried it on my G7+. I ended up not liking out it turned out (Netflix DRM, Vanced didn't work properly, etc).
So I reflashed the stock ROM and put the comand fastboot oem lock.
The thing is, after I boot the device again, all the messages still appear, like Your device has loaded a different operating system" and below that "ID: " (blank) and I also get "Verity mode is set to disable".
The thing is, every tutorial I come across to relock the bootloader(regular G7, G7 Power, G6, etc), says that when you enter the command "fastboot oem lock" two times, the message that you should only flash signed images, does not appear. I instantly get the state flashing_locked, and I can't continue flashing the stock firmware like every other tutorial shows.
In short, once you enter the command "fastboot oem lock", it's locked for good, and you can't do anything unless you unlock it again, starting the whole process again.
The problem is, even with the bootloader locked again, my device still shows as "insecure", Netflix is nowhere to be found on the app store, and the state of my device is not certified.
I wouldn't have unlocked If I knew it was going to be this difficult to get it back. Selling it now would be next to impossible.
Here are some examples of the errors I'm getting:
Does anyone know how to fix this?
Click to expand...
Click to collapse
You can try downloading each versions from your region (RETUS, RETEU, etc) and retry the relock process until you find the correction version.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com