Related
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
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).
oppili said:
If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).
Click to expand...
Click to collapse
Yes, im sure. On bootloader mode is in red color - Phone unlocked, but i not using Linux, im on Windows 7 and this not help me....
Try fastboot oem unlock - command again.
If still not works, try fastboot erase of that *.img file before flashing that new img file.
oppili said:
Try fastboot oem unlock - command again.
When i try this command...
c:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.004s]
finished. total time: 0.006s
If still not works, try fastboot erase of that *.img file before flashing that new img file.
Click to expand...
Click to collapse
I know about this but im above when i try erase all after this fastboot send me "Failed..." and i will be have dead phone, tell me - when i try erase command for all partitions - will be phone work wit fastboot after this??
THX
Are you the only user in pc ? Do you have admin rights ?
or
try any other pc
or
use Ubuntu OS
Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked
thilak devraj said:
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked
Click to expand...
Click to collapse
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
then you should take it to the service center. the only best thing you can do now..
Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
erase cache command is blocked by huawei in fastboot irrespective of locked or unlocked state. somewhere i read unlock lost permissions after update. if you have not tried unlock after update try it. driver can also be an issue, install hisuite it comes with drivers.
Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down
shady143 said:
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down
Click to expand...
Click to collapse
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.
zzztidurvirus said:
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.
Click to expand...
Click to collapse
First...many thanks for your interest!
Look, about bootloader, on boot mode is in red PHONE UNLOCKED, i try this command in fastboot:
C:\Minimal ADB and Fastboot>adb reboot bootloader
C:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Minimal ADB and Fastboot>fastboot oem backdoor info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ -0.000s]
finished. total time: -0.000s
so what is FB Lockstate??Is my bootloader unlocked or locked??
Here is another command which i try....
C:\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
Cant derermine partition type - is this problem?
I also try this....
C:\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 524288000 bytes
sending 'recovery' (25034 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 1.033s]
finished. total time: 1.831s
C:\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
It seems that fastboot write recovery (with your help i need use admin rights now this work) but i still cant boot to recovery no matter how...
I can also flash and backup boot and recovery via Flashify or Rashr and when i open backup with HEX editor it seems that i succesfully upload TWRP but still cannot acess TWRP recovery....
This is all what i try in this time, of course i read your help words about Huawei extractor etc. but not try at this time, i hope i explain more detailed my problem. Look im not a newbie, i allready flash etc. my Lenovo and P9 lite what i have here but not understand where can be problem in this Honor 4x, it seems like corrupted recovery partition or can be problem in read only/write partition - i play with this option before....
anyway - run as admin - this help me a lot i think, THX and wait your answer.
EDIT: one thing, you think that when i try flash stock recovery (i can, no problem of course) it will be work?
Update: Big success, i just try flash stock recovery B064b and now im in stock recovery menu, im surprised but what now? I want update to Marshmallow 6.0....?
But in stock recovery is: phone and the data cannot be recovered. Continue?
Oh sorry, this is about "not sd card inserted" problem
What will now progress? I have inside B130 firmware and want Marshmallow, also TWRP recovery must i flash now especially for B130 firmware for work?
Update: Yes, all working now, factory reset, recovery etc. you help me a lot, only if you can tell me what number of firmware must i upload for Marshmallow, thx
Last update: So finally, coz im too hurry and dont want wait for your answer :angel:, i just upload from local update first Android 5.1.1. after this 6.0 and all is perfect and working!
My big thanks and kisses goes to you zzztidurvirus, im lucky and still cant beleive that all works, again thx!!
I did once on Win to revert back to Stock from CM12.1 by using img from update.app file. For my case, it's the MM update.app not working, I couldn't flash img files into phone, then I tried to flash files from LP, it worked. I boot into LP ROM and update from there to MM.
Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?
Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
I had faced same issue but get back by using the that method.
Sumea said:
Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?
Click to expand...
Click to collapse
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...
Lulu_568 said:
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...
Click to expand...
Click to collapse
Sadly not, as I tried both running ADB fastboot as admin from administrator command line and I tried three different recovery images from huawei, 6.0 (because the flash went bad during attempt to flash a 4.1EMUI with 6.0 B506 ROM for CHE2-L11) - And it keeps denying the write attempt with the same message. More info on the flash: I tried to TWRP flash from 5.1 rom to the EMUI4.1 6.0 ROM following guide someone made with updateappflasher.zip or something, during the flash the phone just crashed 60% in the bar and after that the phone is boot looping into recovery but it can't do anything. Like said any attempt to flash a stock rom even if a recovery seems to exist when booting VOL+ & POWER at the same time, but it will fail if attempting to do wipe data/factory reset in 40% mark. Forced updater can also be accessed but again, thanks to the firmware situation the phone is in it does not flash anything beyond 5% without crashing and being stuck or just giving an error message outright.
Only thing I might have not have is the right kind of ADB drivers but googling about CHE2-L11 I really cannot find a ADB drivers for this phone for life of me and dealing with windows 10 these days makes it worse. At least it used to be that I was with windows 7, back when I myself unlocked the bootloader of the phone and rooted it myself, I have some memory of that being harsh to deal with too, as I had hard time getting drivers that worked right with the phone etc.
I will check into this... At this point my friend bought a new phone already but I still will try to fix the phone for him since I feel personally pretty bad for pretty big mess I made.
I will also try this with a windows XP machine I have still, it is meant entirely for different things but at times like these it is somewhat nice to have a XP around. At least the darn driver problems are not a problem.
UPDATES:
I unbricked the phone. The stock recovery was intact enough for just a normal dload install of a update.app from huawei - why it did not initially work was probably the USB connection to computer and/or 64gig microSD card my friend had, not being compatible with Huawei's recovery updater. I myself had a 8gig card around which worked and I restored the phone ultimately to a 6.0 official ROM. I also went ahead to root it - and final find really was that the reason why recovery etc. would not flash, was because I wrote "fastboot flash RECOVERY twrp.img" - instead of "fastboot flash recovery twrp.img" - the latter works, and the all caps for "RECOVERY" results in illegal command error - and it was no bigger than that.
Meanwhile even after sorting this all out my friend already ended up buying a new phone so it hurts but I hope some other people find some info here useful.
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?
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
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.