I neglected to flash vendor.img when installing the M preview and did "fastboot reboot" after flashing everything else manually. Now whenever my N9 boots, it only shows the Google logo. I've tried going into Recovery and wiping/factory reset with no success.
Is there any way I can a) flash the remaining vendor.img; or b) return my N9 back to 5.1.1?
shaiwon said:
I neglected to flash vendor.img when installing the M preview and did "fastboot reboot" after flashing everything else manually. Now whenever my N9 boots, it only shows the Google logo. I've tried going into Recovery and wiping/factory reset with no success.
Is there any way I can a) flash the remaining vendor.img; or b) return my N9 back to 5.1.1?
Click to expand...
Click to collapse
Boot back into your bootloader, and "fastboot flash vendor vendor.img"
That's what I'm trying to do but I don't know how to connect the tablet with my Mac to run the command in fastboot. When I type "adb devices", it no longer lists my device as attached. Would appreciate instructions in how to connect again through USB to flash the vendor image.
shaiwon said:
That's what I'm trying to do but I don't know how to connect the tablet with my Mac to run the command in fastboot. When I type "adb devices", it no longer lists my device as attached. Would appreciate instructions in how to connect again through USB to flash the vendor image.
Click to expand...
Click to collapse
There's not enough information here to help you.
So if I understand well, you previously were able use ADB and fastboot on this computer?
Does your computer recognize your N9? Can you see the N9's SDcard from your Mac?
If yes, then is "USB debugging" enabled in Developer Options?
When you try ADB devices, did you click the "always allow/trust connection with this computer" popup on your N9's screen?
cam30era said:
There's not enough information here to help you.
So if I understand well, you previously were able use ADB and fastboot on this computer?
Does your computer recognize your N9? Can you see the N9's SDcard from your Mac?
If yes, then is "USB debugging" enabled in Developer Options?
When you try ADB devices, did you click the "always allow/trust connection with this computer" popup on your N9's screen?
Click to expand...
Click to collapse
Before flashing the preview image using fastboot, I had USB debugging enabled. When rebooting after flashing all the files (except vendor.img), the tablet would power on and show only the "Google" logo and go no further. So I tried booting into fastboot and recovery, but when I plug in the tablet to my Mac and try "adb devices", it doesn't recognize it being connected.
Since I cannot turn the N9 on fully to go into Developer Options and enable USB debugging again, how do I connect it to my Mac again so I can flash the remaining file and complete the setup?
In the same boat here. Enabled USB debugging, OEM unlocked, flashed the device manually (build failed, did the .img's sequentially), now the device gets stuck on the Google logo at boot. Attempted recovery and reset, no joy. Gets stuck on the Google logo. When back in the Fastboot menu, meanwhile, my Mac - previously able to see the device via adb - lists no connected devices so I can't reflash.
I assume I'm going to have to go the RMA route?
sogrady said:
In the same boat here. Enabled USB debugging, OEM unlocked, flashed the device manually (build failed, did the .img's sequentially), now the device gets stuck on the Google logo at boot. Attempted recovery and reset, no joy. Gets stuck on the Google logo. When back in the Fastboot menu, meanwhile, my Mac - previously able to see the device via adb - lists no connected devices so I can't reflash.
I assume I'm going to have to go the RMA route?
Click to expand...
Click to collapse
Hi, sogrady...
You don't need ADB to flash anything... All you need is FASTBOOT and a working connection to your PC/Mac.
----
ADB debugging is irrelevant when it comes to running fastboot flash commands. ADB is only meaningful when running a fully booted version of Android OR when running a Recovery... Stock or Custom.
Providing your Nexus 9 bootloader is unlocked, you should be able to run fastboot flash commands without problem.
To confirm you have a working fastboot connection, and with the device booted into it's bootloader, type...
Code:
fastboot devices
This should return your N9s unique device id... If it doesn't, you likely have a driver/connectivity issue... but it has nothing to do with ADB debugging - On or Off.
Rgrds,
Ged.
sogrady said:
In the same boat here. Enabled USB debugging, OEM unlocked, flashed the device manually (build failed, did the .img's sequentially), now the device gets stuck on the Google logo at boot. Attempted recovery and reset, no joy. Gets stuck on the Google logo. When back in the Fastboot menu, meanwhile, my Mac - previously able to see the device via adb - lists no connected devices so I can't reflash.
I assume I'm going to have to go the RMA route?
Click to expand...
Click to collapse
I thought so too, but I found a solution.
Check out my post here: http://forum.xda-developers.com/nexus-9/help/help-boot-loop-os-n-t3122167#post61051773
Hopefully, it helps.
Unfortunately, fastboot can't see the device either:
Code:
ferro$ fastboot devices
ferro$
This is with the Nexus 9 connected and in fastboot mode. As for it being a driver issue, everything that I've seen suggests that specific to Windows, and I'm on Mac. Is that accurate, or are there drivers I need to install on a Mac?
GedBlake said:
Hi, sogrady...
To confirm you have a working fastboot connection, and with the device booted into it's bootloader, type...
Code:
fastboot devices
This should return your N9s unique device id... If it doesn't, you likely have a driver/connectivity issue... but it has nothing to do with ADB debugging - On or Off.
Rgrds,
Ged.
Click to expand...
Click to collapse
sogrady said:
Unfortunately, fastboot can't see the device either:
Code:
ferro$ fastboot devices
ferro$
This is with the Nexus 9 connected and in fastboot mode. As for it being a driver issue, everything that I've seen suggests that specific to Windows, and I'm on Mac. Is that accurate, or are there drivers I need to install on a Mac?
Click to expand...
Click to collapse
No drivers on a Mac. And the command should be "./fastboot devices". You need the "period" and "backslash" before the command.
cam30era said:
No drivers on a Mac.
Click to expand...
Click to collapse
So assuming fastboot doesn't see the device, then, I'm out of options and looking at an RMA?
cam30era said:
And the command should be "./fastboot devices". You need the "period" and "backslash" before the command.
Click to expand...
Click to collapse
Why would this be? I've placed both adb and fastboot both in the machine's PATH, so executing them with the ./ prefix is unnecessary. Certainly worked just fine the first time around without them.
sogrady said:
So assuming fastboot doesn't see the device, then, I'm out of options and looking at an RMA?
Why would this be? I've placed both adb and fastboot both in the machine's PATH, so executing them without the ./ preference is unnecessary. Certainly worked just fine the first time around without them.
Click to expand...
Click to collapse
Hi, again sogrady....
Don't give up so easily...
When you say "I'm out of options", what options have you tried exactly?
Another computer? Another USB cable? A different USB port on a computer?? There could be several variables causing problems for you.
One other point, are you certain your Nexus 9 is fully booted into fastboot mode, and not just the HBOOT bootloader...
You should see something like my attached screenshot...
If you see this, then all things being equal, fastboot commands should work without problems.
Hope this helps...
Rgrds,
Ged.
sogrady said:
Why would this be? I've placed both adb and fastboot both in the machine's PATH, so executing them with the ./ prefix is unnecessary. Certainly worked just fine the first time around without them.
Click to expand...
Click to collapse
Update the binaries, they may be outdated.
You can use my script for this: http://forum.xda-developers.com/android/general/adb-fastboot-binaries-os-x-inclusive-t2941205
Happy to report success - well, partial success anyway. Per @GedBlake, I swapped in a new machine and cable, and per @simmac I made sure my binaries were updated. As it turns out, this was unnecessary: my mistake, after looking at @GedBlake's screenshot was that I was not down in fastboot, I was in hboot. As soon as dropped down into fastboot, voila:
Code:
Macintosh-3:volantis-MPZ44Q sogrady$ fastboot devices
HT4CRJT01274 fastboot
So, problem solved I figured. I re-downloaded the M image to my new machine, checked the MD5 and attempted to flash all. As with the previous iteration, it failed due to a new (to me) set of errors:
Code:
error: cannot load 'system.img'
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
ERROR: usb_write failed with status e00002ed
ERROR: usb_write failed with status e000404f
sending 'vendor' (147127 KB)...
ERROR: usb_write failed with status e000404f
FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
ERROR: could not get pipe properties
ERROR: could not get pipe properties
rebooting...
ERROR: usb_write failed with status e0004061
finished. total time: 0.000s
Macintosh-3:volantis-MPZ44Q sogrady$ fastboot reboot
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting...
ERROR: usb_write failed with status e00002ed
At which point I figured that I would simply load the *.img's manually, one by one. But fastboot had by this point become squirrelly about even seeing the machine.
Code:
Macintosh-3:volantis-MPZ44Q sogrady$ fastboot devices
ERROR: could not get pipe properties
ERROR: could not get pipe properties
???????????? fastboot
At which point I decided to simply see if I could go back and load 5.1.1 and deal with M later. While that flash-all.sh script failed as well, I was able to put 5.1.1 back on via the following manually:
Code:
fastboot flash bootloader bootloader-flounder-3.44.1.0123.img
fastboot reboot-bootloader
unzip image-volantis-lmy47x.zip
cd image-volantis-lmy47x
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
fastboot reboot
At which point the device booted back up into 5.1.1. So big thanks folks for helping me restore an otherwise bricked machine! Much appreciated. Hope the steps help anyone else caught in a bricking cycle.
And if anyone has any idea why my M load failed, I'd be all ears because I would like to load that up at some point. For now, though, I'm just happy to have a working machine again.
Update: Ok, strike the above. Re-ran that process for the Android M build and it went off without a hitch this time, although the setup wizard failed so the build itself looks to be buggy. That at least is not related to the flashing process, however, so proceed to flash M onto the device if you're willing to try and get past those issues.
Hello, i have my phone Huawei P20 Lite wich is bricked with Phone Locked and FRP lock. I tried to write recovery with fastboot but always receive 'Command not allowed'. It's because my bootloader isn't unlocked...
when i want to power on it's stuck on 'Attention! Please install the update again'
If anyone know how to solve that, please leave an answer there!
orpheum123 said:
Hello, i have my phone Huawei P20 Lite wich is bricked with Phone Locked and FRP lock. I tried to write recovery with fastboot but always receive 'Command not allowed'. It's because my bootloader isn't unlocked...
when i want to power on it's stuck on 'Attention! Please install the update again'
If anyone know how to solve that, please leave an answer there!
Click to expand...
Click to collapse
Hi there
Have you tried to go to eRecovery through power on and Volume+ buttons?
Yes
ars_chelsea said:
Hi there
Have you tried to go to eRecovery through power on and Volume+ buttons?
Click to expand...
Click to collapse
yes, but is stucked on Huawei logo..
orpheum123 said:
yes, but is stucked on Huawei logo..
Click to expand...
Click to collapse
Hallo there
Ok! So you can't really have an unlock code? Cause that would help a lot more... Anyway as for now from all cases I have seen you are telling me this is the hardest one. Altough there is one more chance that you should try.
If you have the stock recovery .img or a TWRP recovery .img you might be able to boot to it and do a hard reset which fixes your issue.
First download the adb tools from here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Then extract it to a random folder.
After you have the stock or TWRP recovery .img just copy it to this folder and open it.
If you don't have the stock recovery, I have a link to it here:
https://mega.nz/#!SR9RzKST!dhXS0yC-p_SvWu-SYYLaop1aRFzSulLVrnSXCVVJiGI
Then press shift + right click on the mouse, it should show an option called "Open a Powershell Window here in case you have Windows 10, or "Open a CMD window here" (on windows 8 and below) click that and a window will appear.
Next, if you are on windows 10 and the window says Windows Powershell type ".\fastboot boot imagenamehere.img" if not and you are on Windows 8 or below type "fastboot boot imagenamehere.img".
Where "imagenamehere" is your image name such as recovery.img or twrp.img or usually on this stock recovery recovery_ramdisk.img.
It should boot into recovery
That way you can factory reset if on stock recovery of course.
Either way you gotta lose all your data right now, there's just no way around it without losing data.
Cheers and best of hopes,
AS
ars_chelsea said:
Hallo there
Ok! So you can't really have an unlock code? Cause that would help a lot more... Anyway as for now from all cases I have seen you are telling me this is the hardest one. Altough there is one more chance that you should try.
If you have the stock recovery .img or a TWRP recovery .img you might be able to boot to it and do a hard reset which fixes your issue.
First download the adb tools from here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Then extract it to a random folder.
After you have the stock or TWRP recovery .img just copy it to this folder and open it.
If you don't have the stock recovery, I have a link to it here:
https://mega.nz/#!SR9RzKST!dhXS0yC-p_SvWu-SYYLaop1aRFzSulLVrnSXCVVJiGI
Then press shift + right click on the mouse, it should show an option called "Open a Powershell Window here in case you have Windows 10, or "Open a CMD window here" (on windows 8 and below) click that and a window will appear.
Next, if you are on windows 10 and the window says Windows Powershell type ".\fastboot boot imagenamehere.img" if not and you are on Windows 8 or below type "fastboot boot imagenamehere.img".
Where "imagenamehere" is your image name such as recovery.img or twrp.img or usually on this stock recovery recovery_ramdisk.img.
It should boot into recovery
That way you can factory reset if on stock recovery of course.
Either way you gotta lose all your data right now, there's just no way around it without losing data.
Cheers and best of hopes,
AS
Click to expand...
Click to collapse
will not work, because:
"downloading 'boot.img'...
OKAY [ 0.487s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.510s"
bootloader are locked, cant do anything!!
Arnys said:
will not work, because:
"downloading 'boot.img'...
OKAY [ 0.487s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.510s"
bootloader are locked, cant do anything!!
Click to expand...
Click to collapse
Yeah you are right, my bad :/
I have a simple one, have you tried "fastboot reboot recovery" via the same command line as well? I know it's obvious but that should work for you...
If it doesn't please send me the error code.
Cheers,
AS
I'm also having almost the same issue. My p20 lite is locked to Japan AU network and frp lock but it's not bricked. I want to use it here in Philippines that's why I'm planning to install a stock rom which will work here. Can you help me?
Hello, I have the exact same problem the guy above has, and I tried "Fastboot reboot recovery" and it still didn't work, I believe because of my cellphone. Do you have any more advice?
contact me i will try help
Hi kikson112!
If You are able to help in such problem I would like to ask You for help as well.
My case look similar.
My P20 lite with no reason (nothing I know) got locked . the screen is black and when I try to unlock it shows only time and weather in uper right corner. It looks like it would stuck in flipcover mode but I never had one.
I tried to reset it , reboot it but nothing help.
I tried to connect by Hisuite to download My data but it is not in debugg mode so I cannot connect.
During reset it looks like it is not loading the system.
When I connect my bluetooth headset it connects.
It is playing the alarm in the morning.
But I cannot do anything. The screen does not respond.
Any ideas what could I try to get My data would be apprieciate.
Hi kikson112!
If You are able to help in such problem I would like to ask You for help as well.
My case look similar.
My P20 lite with no reason (nothing I know) got locked . the screen is black and when I try to unlock it shows only time and weather in uper right corner. It looks like it would stuck in flipcover mode but I never had one.
I tried to reset it , reboot it but nothing help.
I tried to connect by Hisuite to download My data but it is not in debugg mode so I cannot connect.
During reset it looks like it is not loading the system.
When I connect my bluetooth headset it connects.
It is playing the alarm in the morning.
But I cannot do anything. The screen does not respond.
Any ideas what could I try to get My data would be apprieciate.
Click to expand...
Click to collapse
hi, for rescue data use converter to connect a mouse in usb port should work, in this case posible digitizer can be just broken, try download software math to ur phone and write it over sd card by 3 buttons (vol - vol + pwr) and post here if any changes
Umm, you can try to get Huawei to do it or youcan buy an unlock key to flash the stuff.
I think there is a special Huawei Flash mode but I don't remember how to access it anymore because I was a Huawei employee and I knew how before but I forgot. Sorry!
hi all, i have the same problem...Huawei logo...
I connect the mobile phone to the PC, press volume - and power and enter "Fastboot & Rescue Mode".
Phone locked
FRP lock
I try to give the command from the terminal, fastboot boot recovery_ramdisk.img, and I have the following messages:
F: \ P20 \ platform-tools_r29.0.5-windows \ platform-tools> fastboot boot recovery_ramd
isk.img
<waiting for any device>
Sending 'boot.img' (32768 KB) OKAY [0.963s]
Booting FAILED (remote: 'Command not
allowed ')
fastboot: error: Command failed
Then try Volume+ buttons, but it restarts showing the initial logo, without going to eRecovery
hi all, i have the same problem...Huawei logo...
I connect the mobile phone to the PC, press volume - and power and enter "Fastboot & Rescue Mode".
Phone locked
FRP lock
I try to give the command from the terminal, fastboot boot recovery_ramdisk.img, and I have the following messages:
F: \ P20 \ platform-tools_r29.0.5-windows \ platform-tools> fastboot boot recovery_ramd
isk.img
<waiting for any device>
Sending 'boot.img' (32768 KB) OKAY [0.963s]
Booting FAILED (remote: 'Command not
allowed ')
fastboot: error: Command failed
Then try Volume+ buttons, but it restarts showing the initial logo, without going to eRecovery
Click to expand...
Click to collapse
is fastboot working and upgrade mode ?
After doing a flash for new pixel experience PixelExperience_Plus_beryllium-11.0-20210823-0645-OFFICIAL, phone restarted and then no other option for access. Boots into twrp logo and stuck.
adb devices in command prompt show device and recovery.
When I do bootloader into fast boot,
fastboot devices shows
??????? fast boot
then disconnects. (after this it doesnt progress any further and disconnects from pc).
cant fastboot any files as it has error, my boot loader is unlocked and was on pixel experience 10 prior.
what are my next steps?
the teamwin recovery is 3.2.3-0
kmkzboi said:
After doing a flash for new pixel experience PixelExperience_Plus_beryllium-11.0-20210823-0645-OFFICIAL, phone restarted and then no other option for access. Boots into twrp logo and stuck.
adb devices in command prompt show device and recovery.
When I do bootloader into fast boot,
fastboot devices shows
??????? fast boot
then disconnects. (after this it doesnt progress any further and disconnects from pc).
cant fastboot any files as it has error, my boot loader is unlocked and was on pixel experience 10 prior.
what are my next steps?
the teamwin recovery is 3.2.3-0
Click to expand...
Click to collapse
Use the latest Official TWRP since the one you have now is outdated and do clean install according the guide at POCO F1 Ultimate Collection & Guides. (You need to format data not just wipe) You can find everything you need there.
first time i turned on phone today, i was able to to do command fastboot devices and it actually showed the device id, then when i tried to flash it stopped and then everytime i connect it wont even show fastboot devices without showing ???????? and shutting down again.
ive tried installing uninstalling the drivers and boot loader drivers, i believe its something to do with that, otherwise it has unlock symbol when it gets stuck on twrp logo, then when i put into fastboot it doesnt have unlock symbol before fastboot splash, what could it be? (im unable to flash anything without getting
1. running fastboot flash/boot/ any command really
Sending 'recovery' (1551913 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
2. running command then connecting phone already in fastboot
< waiting for any device >
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
kmkzboi said:
first time i turned on phone today, i was able to to do command fastboot devices and it actually showed the device id, then when i tried to flash it stopped and then everytime i connect it wont even show fastboot devices without showing ???????? and shutting down again.
ive tried installing uninstalling the drivers and boot loader drivers, i believe its something to do with that, otherwise it has unlock symbol when it gets stuck on twrp logo, then when i put into fastboot it doesnt have unlock symbol before fastboot splash, what could it be? (im unable to flash anything without getting
1. running fastboot flash/boot/ any command really
Sending 'recovery' (1551913 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
2. running command then connecting phone already in fastboot
< waiting for any device >
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Click to expand...
Click to collapse
Check AMD Ryzen Fastboot Fix at the thread I posted above. If you have Intel system just install the Fastboot Drivers which is there (at the thread) and check.