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

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

FRP locked and wiped data HELP!

Hi, I'm about hours to jump from my window.
I wanted to flash EMUI 9 official C432 firmware, but I did it with HuRU so the compilation number was bad. I tried again with the official EMUI 9 beta update "The TOOL", but at some point TWRP lost conection with my PC, so as a dumb guy, I reseted the Developer Options, and the "Unlock OEM" option was greyed out and couldn't enable it.
So I rebooted to TWRP and made a Factory wipe, but I kept having problems with my pc detecting my phone. (I tried changing usb cable and port, reinstalling drivers, erasing all USB devices, etc). So I dont know why I did a Wipe Data partition, but it took so long that I turned off my phone.
So now, here is my problem/s:
>Bootloader unlocked/FRP Locked
>Constant Bootloop, nor OS or recovery works
>As I wiped Data partition, OS and TWRP or any recovery is not available (maybe?)
>As I have FRP Locked, I can't install any recovery nor .img (when I try to flash anything it says: "FAILED (remote: Command not allowed)"
>Also I installed Magisk, so when I run command to LOCK bootloader, it says that there is root: "FAILED (remote: root type is risk)"
fastboot data, maybe could help:
PS C:\Users\Kev\Desktop\Nueva carpeta> fastboot flash ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (32768 KB)...
OKAY [ 0.887s]
writing 'ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.897s
PS C:\Users\Kev\Desktop\Nueva carpeta> fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 13.464s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 13.476s
PS C:\Users\Kev\Desktop\Nueva carpeta> fastboot oem get-build-number
...
(bootloader) :CLT-LGRP2-OVS 9.0.0.163
OKAY [ 0.007s]
finished. total time: 0.008s
PS C:\Users\Kev\Desktop\Nueva carpeta> fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.003s
PS C:\Users\Kev\Desktop\Nueva carpeta> fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.022s
PS C:\Users\Kev\Desktop\Nueva carpeta> fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :CLT-L29 8.1.0.156(C432)
OKAY [ 0.008s]
finished. total time: 0.009s
Any hopes for me or I should jump from my window?
Thanks

Only thing is to change motherboard..
You should go to huawei service.

If i were you i would try to find a way to downgrade to oreo using usb-otg method before going to hw service.
Many people report "activate oem unlock" being greyed out. I've noticed that too when i was on 9.0.163 and wiped my phone (it was active before factory reset) . It looks like this setting is simply inactive in pie. Downgrade to oreo is the only solution.

it is impossible to install anything - any firmware..

1. Have you ever tried installation with sd card (usb otg)?
2. Another thing is trying to contact funky huawei. People with similar problems got their devices fixed without having to switch mainboard.

forever_lol said:
1. Have you ever tried installation with sd card (usb otg)?
2. Another thing is trying to contact funky huawei. People with similar problems got their devices fixed without having to switch mainboard.
Click to expand...
Click to collapse
No, I havn't. Do I need to use a flash drive and connect it with an otg cable?
Yes I could contact FH but I don't have access even to recovery nor erecovery.
Also, If I choose to fix it with Huawei Service I can't because in my country there is not service for P20 PRO. So i'm dead.

polaco95 said:
No, I havn't. Do I need to use a flash drive and connect it with an otg cable?
Yes I could contact FH but I don't have access even to recovery nor erecovery.
Also, If I choose to fix it with Huawei Service I can't because in my country there is not service for P20 PRO. So i'm dead.
Click to expand...
Click to collapse
1) yes indeed. I use micro sd card and usb adapter for that purpose.
2) it's worth to ask anyway.

forever_lol said:
1) yes indeed. I use micro sd card and usb adapter for that purpose.
2) it's worth to ask anyway.
Click to expand...
Click to collapse
So I'll buy and OTG-USB cable so I can use this.
I recently requested for an FRP Unlock Code with this program: Huawe FRP Tool, and used it, but now phone keeps rebooting trying to get into recovery and doesn't even get into fastboot mode. I think this is the end.

polaco95 said:
So I'll buy and OTG-USB cable so I can use this.
I recently requested for an FRP Unlock Code with this program: Huawe FRP Tool, and used it, but now phone keeps rebooting trying to get into recovery and doesn't even get into fastboot mode. I think this is the end.
Click to expand...
Click to collapse
Sorry too hear that man. I hope you'll find a way to fix it.

forever_lol said:
Sorry too hear that man. I hope you'll find a way to fix it.
Click to expand...
Click to collapse
Trying to do everything fast I f*ked up. Anyway, I think I learned the lesson not to go that far and settle a little bit. Anyway, don't use FRP Unlock tool, at least if you are bricked.
I think the last solution is to switch mainboard, but anyway I can't get it in my country, so Idk

i also have this problem, have send it to service centre here in The Netherlands.
They could repair it, with replacing the motherboard for 450 euro.
I let them send it back unrepaired.

coolhead said:
i also have this problem, have send it to service centre here in The Netherlands.
They could repair it, with replacing the motherboard for 450 euro.
I let them send it back unrepaired.
Click to expand...
Click to collapse
Hello.
Registered to report a successful repair after a manual firmware upgrade to EMUI 9.
After the update, I made a reset and got a brick.
Bootloader and FRP after updating blocked. He reset the phone, got a brick.
In funkyhuawei [x] club, he paid $ 18.00 USD to restore the brick using the eRecovery method. This method did not work. I made a request for a refund, they did NOT return the money. I do not recommend to contact this organization.
The problem was solved by the official corporate service center of Huawei in Moscow. They restored the firmware in my device. Service cost $ 12USD.
took 1 hour of time.
There is no need to change the motherboard.
Thanks to all.

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

Question 'Flashing is not allowed in Lock State' error message on Fastboot, how to have that permission ?

So i'm trying to root my phone with magisk and adb, OEM is enabled btw and when i tried to flash magisk to my boot_a it says this :
Code:
Sending 'boot_a' (131072 KB) OKAY [ 4.356s]
Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
Click to expand...
Click to collapse
Do someone know how i can have that permission ?

Is your phone unlocked?

viktak said:
Is your phone unlocked?
Click to expand...
Click to collapse
well that's the thing i don't know how to unlock it on fastboot

First you need to enable unlocking it in the Developer settings. For that you'll need a Xiaomi account, then you need to request an "unlock code", then wait a week, then unlock it there first. Then you can continue in fastboot and the likes.
You need the "Mi Unlock Tool" to do all this.

viktak said:
First you need to enable unlocking it in the Developer settings. For that you'll need a Xiaomi account, then you need to request an "unlock code", then wait a week, then unlock it there first. Then you can continue in fastboot and the likes.
You need the "Mi Unlock Tool" to do all this.
Click to expand...
Click to collapse
thank you

An easy way to check is:
Code:
C:\>fastboot erase fishheads
If you are locked it will complain immediately.
If you are unlocked it will try to erase "fishheads", then say, "Hey, there's no partition named that."
Do not do this if you have a partition named "fishheads".