Related
UPDATE: Solution below!
There is a chance the OTA will fail, as this have happened to some users already:
http://forum.xda-developers.com/nexus-9/general/nexus-9-android-n-preview-t3332715
You might be able to recover if you have USB Debugging turned on PRIOR to performing the OTA update. (Will need to flash factory image).
The problem is the factory image will require you to unlock the bootloader to flash it. To unlock the bootloader, you need to enable USB Debugging. BUT if the OTA fails, you can't boot into the OS to enable USB Debugging. You will end up with a brick.
Here's my experience:
I enrolled my Nexus 9 in the Android N Beta Preview program, and a minute later I got a notification that I have a system update. I went through with the update like any other update. I got to the part where you see an Android laying on it's back and it says "updating system" (or something to that effect) and it has a progress bar. After a few minutes, I see the same Android on it's back, but with an exclamation mark and the words "ERROR!". It would then reboot itself after a few minutes later, but get stuck at the Google logo.
If you leave everything stock, unrooted, and bootloader locked (like a good user), don't try to get the preview via OTA without enabling USB Debugging first! This way, you can at least be able to flash the factory image if the OTA takes a dive.
Since I bought the tablet on Amazon, Google is washing their hands from tech support. Instead, they gave me HTC's support line (which is currently closed). I don't know what I will have to face tomorrow morning when I call.
UPDATE: Google posted signed OTA zips that can be used to recover from this situation. You can now use adb sideload to side load the full OS in OTA form. Go to https://developer.android.com/preview/download-ota.html to download.
Will I be able to recover if this happens by unlocking the bootloader and enabling USB debugging then install Android N preview? I'm feel for you. Good luck.
kalinskym said:
Will I be able to recover if this happens by unlocking the bootloader and enabling USB debugging then install Android N preview? I'm feel for you. Good luck.
Click to expand...
Click to collapse
If you unlock the bootloader and enable USB debugging prior to installing the Android N preview (via OTA), you should be fine. You're essentially leaving yourself a backdoor to flash the factory image should the OTA fails.
Yes, I wish I know this earlier, and now I have a bricked Nexus 9 with me. :sad
Ouch, had that issue and went here looking for help. Should have waited before I tried it ?
THIS IS CRAZY! OTA should work :-\
So crazy to hear that you are all having the same issue with the Android N Developer Preview on Nexus 9!
I have had exactly the same experience today when I enrolled my device for the OTA. It downloaded and started to install fine, but got stuck with the android on his back with the red exclamation mark. It then rebooted and is now stuck on the Google logo. I have tried using adb to push files, factory reset/wipe cache & nexus root toolkit. However, I had NEVER set the OEM unlock option and that seems to have left me stuck!
I'm hoping someone will figure out an amazing fix! Just in case no one does, I called Google and as I purchased it from the play store they have offered me a replacement. Sadly I'm living in Thailand and they can only arrange it to my home country, Australia. So sorry they wouldn't help you Naddie
I didn't unlock the bootloader and I'm also facing exact same issue, my tablet is now almost bricked .
I can go to "recovery" mode, so I tried to do "adb sideload" with OTA image for MMB29V from MMB29R (got from gist.github.com/jduck/744a6c8a9042e9c792b7), but my device is already at MMB29V so it complains with below error:
"system partition has unexpected contents"
Will I be able to flash OTA image through recovery once we get it for MMB29V to AndroidN_version? And where should I get it from?
What other option do I have to recover the device?
sashinde said:
I didn't unlock the bootloader and I'm also facing exact same issue, my tablet is now almost bricked .
I can go to "recovery" mode, so I tried to do "adb sideload" with OTA image for MMB29V from MMB29R (got from gist.github.com/jduck/744a6c8a9042e9c792b7), but my device is already at MMB29V so it complains with below error:
"system partition has unexpected contents"
Will I be able to flash OTA image through recovery once we get it for MMB29V to AndroidN_version? And where should I get it from?
What other option do I have to recover the device?
Click to expand...
Click to collapse
Gee, I hope we're still on MMB29V... But since the OTA seemed to have failed during the update, the system partition may be partially whatever build this Android N preview is and partially MMB29V - which is to say ... It's completely borked for ANY OTA update to fix it via side loading.
Does anyone even have the OTA zip for MMB29V to N preview for we poor souls to try?
Sent from my iPad using Tapatalk
Hello. Sorry for my english. The same from here. I called Google and they offered me a replacement. I said yes. Waiting for a new Nexus 9. I hope you will find the solution.
Enviado desde mi Nexus 6P mediante Tapatalk
Naddie, have you contacted HTC or Google yet about getting a replacement?
My update failed too and I cannot boot. I did not have the OEM unlock switch flipped, so I can't unlock my bootloader. I chatted with Google last night and since I didn't buy it from the Google Store, they wouldn't replace it. They gave me the HTC phone number instead. I haven't tried calling them yet.
I tried updating via the beta program, but there was an error and now my Nexus 9 is softbricked. I can get to fastboot and recovery, but can't boot into Android. And, worst of all, I don't have USB debugging enabled, so I can't do an ADB flash or even OEM unlock.
Can anyone help me out?
naddie said:
There is a chance the OTA will fail, as this have happened to some users already:
http://forum.xda-developers.com/nexus-9/general/nexus-9-android-n-preview-t3332715
You might be able to recover if you have USB Debugging turned on PRIOR to performing the OTA update. (Will need to flash factory image).
The problem is the factory image will require you to unlock the bootloader to flash it. To unlock the bootloader, you need to enable USB Debugging. BUT if the OTA fails, you can't boot into the OS to enable USB Debugging. You will end up with a brick.
Here's my experience:
I enrolled my Nexus 9 in the Android N Beta Preview program, and a minute later I got a notification that I have a system update. I went through with the update like any other update. I got to the part where you see an Android laying on it's back and it says "updating system" (or something to that effect) and it has a progress bar. After a few minutes, I see the same Android on it's back, but with an exclamation mark and the words "ERROR!". It would then reboot itself after a few minutes later, but get stuck at the Google logo.
If you leave everything stock, unrooted, and bootloader locked (like a good user), don't try to get the preview via OTA without enabling USB Debugging first! This way, you can at least be able to flash the factory image if the OTA takes a dive.
Since I bought the tablet on Amazon, Google is washing their hands from tech support. Instead, they gave me HTC's support line (which is currently closed). I don't know what I will have to face tomorrow morning when I call.
Click to expand...
Click to collapse
Nexus 9 is FAMOUS for OTA's failing and leaving you with a "brick".
The good news is that the sky IS NOT falling, even with the bootloader locked and debugging OFF, you can still recover it. All you need to do is reboot into recovery, and "adb sideload" the update.zip again.
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
greiland said:
My update failed too and I cannot boot. I did not have the OEM unlock switch flipped, so I can't unlock my bootloader. I chatted with Google last night and since I didn't buy it from the Google Store, they wouldn't replace it. They gave me the HTC phone number instead. I haven't tried calling them yet.
Click to expand...
Click to collapse
The switch unflips every reboot anyway, so that wouldn't have helped you to begin with.
What "Update" would I sideload? I did my original update via OTA.
Fixed Brick on Nexus 9 OTA Android N update
I had the same problem yesterday with a failed OTA update.
I solved it by booting into Fastboot ( hold down volume up and power button until you see Fastboot options). Then choose recovery. The Nexus 9 should try to reinstall the update.
For me this worked and I now have a working Nexus 9 on Android N beta.
Hope this works for you folks !
Good to know. I just signed up for the beta program. My bootloader is unlocked from day one because I always flash the stock image of the security updates. The USB debugging is on
Sent from my Nexus 6 using Tapatalk
inthelandofnod said:
I had the same problem yesterday with a failed OTA update.
I solved it by booting into Fastboot ( hold down volume up and power button until you see Fastboot options). Then choose recovery. The Nexus 9 should try to reinstall the update.
For me this worked and I now have a working Nexus 9 on Android N beta.
Hope this works for you folks !
Click to expand...
Click to collapse
Can you please explain more detailed? Are you sure it's volume up because recovery is volume down. And what to do then in recovery?
Please, give us more info!!!!
Enviado desde mi Nexus 6P mediante Tapatalk
I am on MMB29V with unlocked bootloader, TWRP recovery, rooted. I opted in for OTA. It downloaded and seemed to install. After restart it booted to recovery and nothing else happened. When I restarted to system I was still on 6.0.1. No errors, nothing! Any clue?
So this might be resolvable if someone has found the Android N OTA...
srideep said:
I am on MMB29V with unlocked bootloader, TWRP recovery, rooted. I opted in for OTA. It downloaded and seemed to install. After restart it booted to recovery and nothing else happened. When I restarted to system I was still on 6.0.1. No errors, nothing! Any clue?
Click to expand...
Click to collapse
OTAs won't apply if you don't have stock recovery.
Hi I have an unrooted 6p I have never messed with the software but I am on the dp program I usually get the updates within hours of it being announced. But for some reason I have not gotten the 7.1.1 stable with December security patch which is odd but anyway I tried side loading the OTA and it gets to 40% and then says installation aborted. I have the and setup right and all that I can reboot into bootloader does anyone know why it would be doing this? When I was at work today I thought maybe if I disable the allow seamless update option in developer options maybe that will allow it. Any thoughts?
Ok I feel like an idiot. I tried again when I got home from work and it seems that the file I am trying to flash is from November 1 which I already have installed. It is the last one one the Google OTA page. So is it not out yet for the 6p? I'm confused can anyone help me out please
I believe you'll need to unenroll from the beta program first before attempting to sideload the OTA image. The latest OTA image is NMF26F, which includes the December security patch. And make sure you boot into recovery, and not the bootloader to install the update using adb.
redduc900 said:
I believe you'll need to unenroll from the beta program first before attempting to sideload the OTA image. The latest OTA image is NMF26F, which includes the December security patch. And make sure you boot into recovery, and not the bootloader to install the update using adb.
Click to expand...
Click to collapse
Ok if I unenrolled from the dp program I should just get the OTA then I won't have to side load is what I'm guessing. It seems that Google had the stable build done before they released the last dp because the file says November 1 build and I got mine on November 5 that is why it won't allow it.
Hey Guys,
I tried updating my tablet from 4.1 to 5.0 and now i am having some issues. I have no keyboard and my fingerprint sensor doesn't work anymore. So i have no way of doing anything. When I try to bring up the keyboard i get the google voice window.Build number shows BTV-W09C128B350. Trying to understand the steps i need to do to get my tablet back and running normally. Do I need to go back to 4.1? Any help would be greatly appreciated.
Thanks
Erik
lamstang94 said:
Hey Guys,
I tried updating my tablet from 4.1 to 5.0 and now i am having some issues. I have no keyboard and my fingerprint sensor doesn't work anymore. So i have no way of doing anything. When I try to bring up the keyboard i get the google voice window.Build number shows BTV-W09C128B350. Trying to understand the steps i need to do to get my tablet back and running normally. Do I need to go back to 4.1? Any help would be greatly appreciated.
Click to expand...
Click to collapse
How did you do the update? Did you use Firmware Finder and it's DNS update or did you use the dload folder method? I used the Firmware Finder method and everything went smoothly even with an unlocked bootloader, You might try to use that method to reinstall Nougat, but you will need a keyboard to change your DNS settings to the one Firmware Finder needs and for that I suggest you try a USB keyboard connected through an OTG cable.
I will say that once you get Nougat working, the 5Ghz radio goes back to not working and the file that needs to be updated to enable it seems to have changed. So far, I can not find the correct file/setting to change to enable it. For me it is more annoying that I can't get it working than necessary because I am getting between 20 and 40 Mbs with the 2.4Ghz radio and that is plenty fast for what I ask this tablet to do.
johje said:
How did you do the update? Did you use Firmware Finder and it's DNS update or did you use the dload folder method? I used the Firmware Finder method and everything went smoothly even with an unlocked bootloader, You might try to use that method to reinstall Nougat, but you will need a keyboard to change your DNS settings to the one Firmware Finder needs and for that I suggest you try a USB keyboard connected through an OTG cable.
I will say that once you get Nougat working, the 5Ghz radio goes back to not working and the file that needs to be updated to enable it seems to have changed. So far, I can not find the correct file/setting to change to enable it. For me it is more annoying that I can't get it working than necessary because I am getting between 20 and 40 Mbs with the 2.4Ghz radio and that is plenty fast for what I ask this tablet to do.
Click to expand...
Click to collapse
i Johje,
I was able to rollback to Android 6.0 and 4.1. Do you have instructions on how you did the Firmware finder update?
Thanks again for your help
Erik
I used Firmware Finder to update to the most recent Full Update for the US version. After Selecting the firmware choose "Get an update through DNS" and follow the instructions. This will install the beta Nougat and restore your recovery partitions even if you have an unlocked bootloader. Once the tablet has Nougat installed, root by installing TWRP to the Recovery2 partition which will replace eRecovery and leave your main recovery in place. Use TWRP to Flash Magisk and PHH Superuser to root the tablet because from my experience SuperSU does not work for Nougat on this table. Once rooted you can enable the 5Ghz radio by finding the "cfg_btv_hisi.ini" file in the "cust_spec\vendor\etc" directory and then just change "band_5g_enable=0" option to "band_5g_enable=1" , after rebooting the 5Ghz wireless will be enabled.
Hope this helps
johje said:
I used Firmware Finder to update to the most recent Full Update for the US version. After Selecting the firmware choose "Get an update through DNS" and follow the instructions. This will install the beta Nougat and restore your recovery partitions even if you have an unlocked bootloader. Once the tablet has Nougat installed, root by installing TWRP to the Recovery2 partition which will replace eRecovery and leave your main recovery in place. Use TWRP to Flash Magisk and PHH Superuser to root the tablet because from my experience SuperSU does not work for Nougat on this table. Once rooted you can enable the 5Ghz radio by finding the "cfg_btv_hisi.ini" file in the "cust_spec\vendor\etc" directory and then just change "band_5g_enable=0" option to "band_5g_enable=1" , after rebooting the 5Ghz wireless will be enabled.
Hope this helps
Click to expand...
Click to collapse
I have also tried to update to 5.0. Everything seemed fine, but there is no keyboard, calc, file manager, etc. The "full..hw.." update seems to go really fast and it says it's done but there is no difference in what is on the tablet. Now I'm stuck at the point where it's A7.0, but I cannot do anything. Try getting google voice type to enter a complex email password
Any help on the second phase of the update is appreciated.
USA
C128
B350
used dload method to load.
nostep said:
I have also tried to update to 5.0. Everything seemed fine, but there is no keyboard, calc, file manager, etc. The "full..hw.." update seems to go really fast and it says it's done but there is no difference in what is on the tablet. Now I'm stuck at the point where it's A7.0, but I cannot do anything. Try getting google voice type to enter a complex email password
Any help on the second phase of the update is appreciated.
USA
C128
B350
used dload method to load.
Click to expand...
Click to collapse
Can you use Firmware Finder in your tablet's current state? If so, try updating using Firmware FInder's DNS method. You will need to be able to update your network DNS settings, though. Have you tried using a corded keyboard connected through an OTG cable or a bluetooth keyboard?
I did not try using the dload method because earlier attempts an updating Marshmallow to a more recent build always failed because of my unlocked bootloader.
johje said:
Can you use Firmware Finder in your tablet's current state? If so, try updating using Firmware FInder's DNS method. You will need to be able to update your network DNS settings, though. Have you tried using a corded keyboard connected through an OTG cable or a bluetooth keyboard?
I did not try using the dload method because earlier attempts an updating Marshmallow to a more recent build always failed because of my unlocked bootloader.
Click to expand...
Click to collapse
Unfortunately I could not fgure out how to do anything with it in that state (no keyboard, no internet, etc.). I tried to find a quality rollback for USA, but was not sure of what was out there that was correct. I ended up installing a EU version so at least it's working again (with old Android). I also realized the next day that my USB cord was bad and that's why I could not ADB or Fastboot anything. I'll try an upgrade again in the near future. Thx.
nostep said:
Unfortunately I could not fgure out how to do anything with it in that state (no keyboard, no internet, etc.). I tried to find a quality rollback for USA, but was not sure of what was out there that was correct. I ended up installing a EU version so at least it's working again (with old Android). I also realized the next day that my USB cord was bad and that's why I could not ADB or Fastboot anything. I'll try an upgrade again in the near future. Thx.
Click to expand...
Click to collapse
How did you install the EU old version? do you have link to the ROM?
Is anyone having problems with Bluetooth on their device? Just need to enable it on mine because I used 2FA with my Google account, & have a security token.
Model Number: BTV-W09
Build Number: NRD90M test-keys
EMUI Version: 5.0
Android Version: 7.0
Everything else seems to be working, at least so far. Still only seeing 2.4 GHz frequency with WiFi, but getting 5.0 GHz working is something I can work on later.
My Bluetooth seems to be working fine. I am on EMUI 5 / Android 7.
the second update file likely did not install correctly when attempting the dload method correct? the solution is to install the second update file as a zip from twrp. that fixes the problem, and updates your system version to the correct btv-w09c128b350 (if your using us version) if you don't have the second update file you can download it using firmware finder app, be sure its the full ota version, as the others do not work with this method.
tomchism said:
the second update file likely did not install correctly when attempting the dload method correct? the solution is to install the second update file as a zip from twrp. that fixes the problem, and updates your system version to the correct btv-w09c128b350 (if your using us version) if you don't have the second update file you can download it using firmware finder app, be sure its the full ota version, as the others do not work with this method.
Click to expand...
Click to collapse
I love how people here use abbreviations so frivilously. TWRP?? I googled that and it seems to be a root method. Rooting the tablet isn't a solution to this and we need bluetooth and 5ghz working for US. I had an EU update installed before this, then I hear the US update is out and I hoped it fixed the bluetooth issue. But now I have a USA version with a disabled bluetooth and no 5ghz wifi radio. This tablet is becoming more of a pain than anything....
When it comes to Android, your best solution is not a Google search but a search of the forums here at XDA, TWRP, is a recovery system that can be installed on the device. Once installed it can be used to perform system backups and restores, install firmware install root, wipe a device, do all sorts of nifty things.
To install TWRP you need to unlock your device, the instructions for doing that are in a different forum. Once unlocked you will need to set up adb which instructions can be found in the install TWRP forum, each version of TWRP is device specific, so you have to get the right one. If you really want to dig into figuring out how to do this, you will need to spend several hours reading the forums about this device, or find a friend who knows how to do this that you can trust not to brick your device.
tomchism said:
When it comes to Android, your best solution is not a Google search but a search of the forums here at XDA, TWRP, is a recovery system that can be installed on the device. Once installed it can be used to perform system backups and restores, install firmware install root, wipe a device, do all sorts of nifty things.
To install TWRP you need to unlock your device, the instructions for doing that are in a different forum. Once unlocked you will need to set up adb which instructions can be found in the install TWRP forum, each version of TWRP is device specific, so you have to get the right one. If you really want to dig into figuring out how to do this, you will need to spend several hours reading the forums about this device, or find a friend who knows how to do this that you can trust not to brick your device.
Click to expand...
Click to collapse
does the above mentioned operation void my guarantee for the tablet ?
That's a difficult question to answer. The device comes with two recovery systems built in. There are not many scenarios where you can hard brick the device and are unable to restore it back to factory settings, locked unrooted and like new. Any warranty issue are likely to be hardware not software.
Hmm. I am in the process of using the dc-unlocker client to unlock my bootloader. When the client reads my phone, it shows the build number as NRD90M test-keys, but when I look at device info on the phone, it shows a normal build number. Does anybody know what this means?
Hi all,
Recently we find a way to go back to 8.1.0 from Android P DP1 with Verizon locked bootloader on the Android Beta Program community. Thanks Ziauddin Sameer for try it.
All you need is:
1- Google Pixel or Pixel XL with locked bootloader (Don't know if it work on Pixel 2 or Pixel 2 XL but it may work)
2- Android P DP1 installed on your device
3- Full April 2018 OTA link here https://developers.google.com/android/ota
4- ADB/FASTBOOT drivers link here https://forum.xda-developers.com/showthread.php?t=2588979
Now that you have all that and the drivers intalled let's do this:
You'll lose all your data after this, so backup before continue
1- Install the drivers
2- Put the Full April OTA zip on the adb folder located on C:/
3- Turn you Pixel off and go to recovery mode
4- Select "Apply update from ADB"
5- Plug in your Pixel via USB to the computer
6- Inside the adb folder Hold "Shift" and right click, select Open Powershell/CMD here"
7- Inside the Powershell/CMD type
Code:
abd sideload filename.zip
8- When its done your Pixel will try to boot and since it has the Android P data (cause sideloads dont erase data) it would said that the data is corrupted and it will suggest you to factory reset.
9- Select factory resert and it will boot on Android 8.1.0
Psdt: Sorry for my bad english.
You can confirm it in here https://plus.google.com/101606265756083327418/posts/cshGmedy5ZX
I can confirm that this does work! THANKS! I am happily back to 8.1! Don't get me wrong "P" is awesome and stable, but having the WiFi Calling feature broke in "P" is a deal breaker for me. I will just have to wait until DP2 to see if it gets sorted out.
EDIT do not use the May 2018 file, use April, this one is transferring now, below error is because of MAY file.
I tried this after going to Android P beta. It did not work for me.
I followed the steps and when I ran adb sideload xxx.zip I received this...
verifying update package
E:footer is wrong
update package verification took 0.2 s (result 1)
E:Signature verification failed
E:error: 21
Installation aborted.
Any help would be greatly appreciated, basically I opted into beta and then opted out but never received the image to go back and apps are not working for me...gear s3, libby and some others.
whreed said:
EDIT do not use the May 2018 file, use April, this one is transferring now, below error is because of MAY file.
.
Click to expand...
Click to collapse
So for downgrading from Android P DP2 we need to use 8.1 April OTA, right?
I ultimately did get the push of the image to my device to pass but the image didn't work for me... When I wiped and rebooted and after initial setup up I received the message to go back to Oreo from Google....I was previously in the beta but opted out.
Does not work for me even for April OTA. It says package being updated is older than the currently installed. I'm on Android P May patch.
Is it possible that I can downgrade when the June OTA is out because of the timestamp?
caloysilva said:
Does not work for me even for April OTA. It says package being updated is older than the currently installed. I'm on Android P May patch.
Is it possible that I can downgrade when the June OTA is out because of the timestamp?
Click to expand...
Click to collapse
Just opt out of the beta and an OTA will appear to go back to Oreo
It doesn't seem this method will work to downgrade the OTA 9.0 update? My phone has been completely unusable since the 9.0 update applied (the radio modem has worked all of about 2 days since the update). I've tried everything and have been on the phone with google many times over this. When I try to place a call, I'll either get the message "Radio off" or " Cannot place calls in Airplane mode" errors. Rebooting, cycling data and airplane modes have no effect, resetting networking does nothing, even factory resetting does nothing. My phone is completely useless without mobile data. I'll never purchase anything from Verizon again, with their opting to lock the bootloader on their phones!
I was also curious if this method would work for an OTA 9.0 device ?