Database Users

WARNING - Do not use OTA to get Android N Beta Preview before reading this!

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.

Not receiving OTAs and can't side load 7.1.1 OTA

Hi all,
I enrolled into the Android Beta program when 7.0 stable was released so that I would receive the OTA earlier and as soon as I received it I un-enrolled. Since then I have not been receiving OTAs and my Security Patch level is August 2016. Checking for updates says my device is up to date. I decided to side load the 7.1.1 OTA to my device so that I would have the latest Android version and security patch and hopefully this would fix my OTA issue too.
I'm running macOS 10.12.1 and I downloaded the OTA file from Google's site and installed ADB for Mac using a Terminal command from xda. My phone is recognised in Terminal if I run adb devices when it is fully booted and in Photo Transfer mode, but when I put my phone in Recovery mode and select install from ADB and then run the command again my phone is no longer recognised. I try running adb sideload <OTA Filename.zip> but I get error: no devices found. USB debugging is enabled and my cable is high quality and supports data transfer, so it's neither of those things.
I don't want to do a factory reset because I don't want to lose my data, and I have wiped the partition cache too which also hasn't worked. I've looked for a long time but can't seem to find a solution but figured some clever being on here might be able to help me. Any suggestions?

nathanmiah said:
Hi all,
I enrolled into the Android Beta program when 7.0 stable was released so that I would receive the OTA earlier and as soon as I received it I un-enrolled. Since then I have not been receiving OTAs and my Security Patch level is August 2016. Checking for updates says my device is up to date. I decided to side load the 7.1.1 OTA to my device so that I would have the latest Android version and security patch and hopefully this would fix my OTA issue too.
I'm running macOS 10.12.1 and I downloaded the OTA file from Google's site and installed ADB for Mac using a Terminal command from xda. My phone is recognised in Terminal if I run adb devices when it is fully booted and in Photo Transfer mode, but when I put my phone in Recovery mode and select install from ADB and then run the command again my phone is no longer recognised. I try running adb sideload <OTA Filename.zip> but I get error: no devices found. USB debugging is enabled and my cable is high quality and supports data transfer, so it's neither of those things.
I don't want to do a factory reset because I don't want to lose my data, and I have wiped the partition cache too which also hasn't worked. I've looked for a long time but can't seem to find a solution but figured some clever being on here might be able to help me. Any suggestions?
Click to expand...
Click to collapse
I'm going to assume you are completely stock with no root or custom recovery. Have you tried re-enrolling in the Beta and rebooting? You may get a new OTA after enrolling. Sounds like you may also not have the correct drivers installed to properly use the LATEST version of ADB/Fastboot. Sorry I can't help you with a Mac, but there are also several toolkits for PC that automate this for you. NRT by Wugfresh, and Skipsoft to name two.

v12xke said:
I'm going to assume you are completely stock with no root or custom recovery. Have you tried re-enrolling in the Beta and rebooting? You may get a new OTA after enrolling. Sounds like you may also not have the correct drivers installed to properly use the LATEST version of ADB/Fastboot. Sorry I can't help you with a Mac, but there are also several toolkits for PC that automate this for you. NRT by Wugfresh, and Skipsoft to name two.
Click to expand...
Click to collapse
I contacted Google and they said the only solution was to perform a factory reset. I didn't want to do that so I just enrolled into the beta again, received the 7.1.1 update and then un-enrolled. Not sure if I'll have the same problem going forward but if I do then I guess I'll have to do a factory reset
Thanks for your help!

sideloading ota

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.

"Network unavailable" on manual System update attempt

Just got my Axon 7, shipped from DE to UK, thought I'd try manual software update.
Current version listed as ZTE A2017GV1.0.0B06
It times out with Network Unavailable despite the fact it is connected to WiFi and Chrome works fine as well as everything else needing internet connections.
I am on Three UK, haven't tried updating without a SIM ... is that worth trying? I did see at initial setup I was prompted to accept some sort of 3UK profile though I assumed this is just APN/MMS stuff.
Anyone else having similar problem trying to update?
I see talk of updating to B08 etc, from 2017G --- is 2017G same as 2017GV1... wouldn't want to assume anything this early on in my game
TIA for any tips/advice.
Am really liking this phone though, might be nice to get latest update for security mainly, not sure if many features are added?

Same issue here as it happens, though I'm currently trying to update WITHOUT a sim (didn't appreciate it was nano so new one on order!).
I was thinking it maybe needed one to be present to update, but clearly that's not the case.

nstirton said:
Same issue here as it happens, though I'm currently trying to update WITHOUT a sim (didn't appreciate it was nano so new one on order!).
I was thinking it maybe needed one to be present to update, but clearly that's not the case.
Click to expand...
Click to collapse
Can't speak to the EU version, but I was surprised when my A2017U would not complete initial setup (& update) without the SIM, although wifi was strong. All completed quickly as soon as I popped in the SIM.

Hi,
I have the same issue here.
I've just bought A2017G from Italy (Amazon) and I live in France. Can't have the upade to B08. There is always this message "No network" after a minute of searching. I tried with 4G and Wifi and there is the same issue!

Also can't connect
Same issue here. I am already on B.08 and have wifi/Sim in place.

Mysterious problem
I have tried many solutions but I wasn't able to update :
- used three different sim cards from 3 operators
- removed sim card and worked only on wifi
- used VPN
- tried to update via SD card form the update page and from recovery
... Unsuccessful !
Anyone have idea?

I'm also having the same problem. I live in Sweden and I just got the phone today. Would be nice if I could update sometime soon.

A2017g b06
Greenland here, I also have problems with the connectivity

Maybe ZTE is updating its servers so that the updates can finally deploy at the same time, the same version, for everyone.
Or, maybe... they are silently getting rid of Adups and moving to another kind of upload process, before **** hits the proverbial fan.
Also, Global Axon 7 here, brought via Amazon.es, sent from Germany and now used across Portugal/Spain. Running 0B08.

deoki said:
Maybe ZTE is updating its servers so that the updates can finally deploy at the same time, the same version, for everyone.
Or, maybe... they are silently getting rid of Adups and moving to another kind of upload process, before **** hits the proverbial fan.
Also, Global Axon 7 here, brought via Amazon.es, sent from Germany and now used across Portugal/Spain. Running 0B08.
Click to expand...
Click to collapse
I can understand that, but even if we put the B08 update file downloaded from ZTE support in SD card, the update can't be processed.

Hello, I had the same problem, I reinitialized the Axon 7, and I copied the file update.zip B09 on the phone, it recognized and installed the file (I was on the b08 before)

Hallo, i have the same problem with update, I have B06, somebody can give me a link to download the latest firmware and how to install it.

Yansin said:
I can understand that, but even if we put the B08 update file downloaded from ZTE support in SD card, the update can't be processed.
Click to expand...
Click to collapse
hmm I put a b09 in the sd card and it updated no problem

Solution found!
I’ve already found the solution for the manual upadate from SD card and it’s easy to do.
Theses instructions are not mine and I’m not responsible of what you do with your phone. I found them inside the update file that I Downloaded then I unzipped.
You will find a PDF document called “ZTE A2017G Upgrade Guide (through an SD Card).pdf”. You can use it to do the upgrade step by step.
Till now, all was OKEY: backup is very quickly with Zte app. The update take about 5 minutes, than the phone restarts automatically.
If you cannot find the B08 update file, try to download it from here: http://www.ztedevice.com/support/detail?id=98CEB24F9FFD433EA99EC424163149A6
Here are the steps (exactly as mentioned in ZTE Upgrade Guide)
ZTE V7 Upgrade Guide (Through an SD Card)
​1. Backing Up the Data
1) Download the upgrade package.
Open http://www.ztedevice.com.cn/support and download the upgrade package (update.zip) that matches your phone model. If the downloaded package is not update.zip, unzip the package to obtain update.zip.
Ensure that your micro SD card is at least 3GB.
2) Remove the SIM card before the upgrade. Back up the data and APPs in your phone by using the built-in Backup function. To enable the built-in Backup function of your phone (an SD card must be inserted), select
Backup and Restore from the main menu。
3) Perform data backup.
Note:
You should not remove the SD card during the backup process. To avoid data lost, it is not recommended to cancel the backup process.
4) Verify that the update.zip file in the root directory of the SD card
matches the model of the phone. Do not modify the file name and extension name of the files in the upgrade package.
5) Verify that your phone has enough (at least 30%) power. Charge the phone if required. To avoid data lost or upgrade failure, it is not recommended to upgrade your phone through an SD card when the phone is being charged.
Note:
You should not perform any other operation on the phone during the upgrade process. To avoid upgrade failure, do not forcibly remove the battery.
A normal upgrade should be completed in 2-3 minutes. If the phone does not reboot or show any response in three minutes, you should perform the upgrade process again. If the phone cannot be started, perform a forced upgrade. If the forced upgrade does not work, you should contact an after-sale service agent for support.
2. Upgrade Description
There are two upgrade methods: normal upgrade and forced upgrade.
If the phone cannot be started properly, for example, the phone cannot be started, or the phone does not enter stand-by state, perform a forced upgrade. If the phone can be started properly and the Settings menu can be selected, perform a normal upgrade.
3. Upgrade Steps
A. Normal upgrade (the primary upgrade method)
1) Download the upgrade package that matches the phone model from ZTE official website (http://www.ztedevice.com.cn/support/), extract update.zip from the package, and copy update.zip to the root directory of the SD card (the file name must be update.zip
2) Select System Manager > File Manager> SD Card from the main menu, and verify that the update.zip file in the root directory of the SD card is proper.
3) Tap the main screen is displayed. Tap and select SETTINGS >All setting > Updates>,
4) Click INSTALL, The phone automatically powers off and reboots. the SD
card upgrade screen is displayed,
After the phone is upgraded, it is rebooted again. After the phone starts properly, it is recommended to manually restore the phone to its original factory default settings. The phone is upgraded properly and can be used.
B. Forced upgrade (for the phones that cannot be started or the phones that cannot enter standby state)
1) For a powered-off phone, press and hold both the volume key + and power
key to enter into Recovery mode.
2) Press the volume key - to select apply update from sdcard, and press the power key to confirm it.
3) Press the volume key - to select the update.zip file, and press the power key to confirm it. The phone completes the upgrade process in about three minutes.
4) On the Upgrade Complete screen, select reboot system now and press the power key to confirm it.
4. (Optional) Restoring the Data
If you have backed up data before upgrading your phone, restore the data.
1) Backup and Restore important user information.
2) Perform data restoration.
Note:
Do not remove the SD card during the restoration process. To avoid data lost, it is not recommended to cancel the restoration process.
An interesting thread: http://forum.xda-developers.com/axon-7/how-to/manual-updating-a2017g-t3519104 !

Thanks, but i tryed to install this update but I get an error that it is not for my phone, i have ZTE A2017G_1817 buildnr. ZTE A2017GV1.1.0B06
Have I don anything wrong or do I need an other file
Regards

Same problem on my axon 7 a2017g - updated via updater from b06 to b08 - network unavailable trying to check update to b09

Same white me, then I tryed it with the downloaded updat.zip from B08 and he start the update bute later stopt whit the message this file is not for my phone ??
Where can I download the B09 update.

keesvl55 said:
Same white me, then I tryed it with the downloaded updat.zip from B08 and he start the update bute later stopt whit the message this file is not for my phone ??
Where can I download the B09 update.
Click to expand...
Click to collapse
The file is on ztedevice (link in thread) but i think (as some of other users) that this patch is only for Spain - don't know that for 100% but most ppl that can upadate it with OTA are located in Spain. Also I still get "network unavailable" when I trying to check update (location Poland, phone from UK). But you should can update from B06 to B08 as I can without any doubts via OTA.

MrMD69 said:
The file is on ztedevice (link in thread) but i think (as some of other users) that this patch is only for Spain - don't know that for 100% but most ppl that can upadate it with OTA are located in Spain. Also I still get "network unavailable" when I trying to check update (location Poland, phone from UK). But you should can update from B06 to B08 as I can without any doubts via OTA.
Click to expand...
Click to collapse
Here the problem is solved, this morning the ota update worked en now he is installing B08.
I downloaded B09 en wanted to go install it and than the give me the original B08 update in the screen, let see how it works.

As for 1.01.2017 update check start working for me - no more "network unavailable" just "up to date" at B08 a2017g.

Recovery bricked after Nougat update?

First excuse me for opening an other thread like this, i think i have read all other threats regarding my problem, but none have the same situation
My Huawei M3 Wifi (BTV-W09) seems semi bricked after installation of Nougat Update.
The Installation (Force Install with dload) gave me an error and also while boot i got the error message: "Your device has failed verification and may not work properly."
I have the option to press "Powerbutton" and the device will boot up. I checked the Version and it showed android 7 + EMUI 5. The only problem was that almost every system app was missing, like keyboard, calendar etc. (playstore was there)
So i tried to do the rollback with:
HUAWEI MediaPad M3 8 Rollback Package%28BTV-W09 %2CC900B300%2C EMUI5.0%2BAndroid7.0 rollback to EMUI4.1%2BAndroid 6.0%29
The Installtion (force update) gets stuck at 5% and after like 3-5 minutes the tablet will boot up showing the same boot error that can be skipped with pressing powerbutton. I checked sytem and it still showed "android 7 + EMUI 5" but built : BTV-W09C900B300
I think this is the one i "need" to be able to install the "HUAWEI MediaPad M3 8 Firmware %28BTV-W09 %2CC100B006%2C EMUI4.1%2BAndroid 6.0%29"
Problem is regardless which "update.app" i try to force install will get stuck at 5% and give me same error. I have ADB/Fastboot installed and tried some different things like flashing/unbricking it with "Huawei Multitool" where you can extract like boot.img or recovery.img and try to flash it.
Also getting an error. I can access eRecovery witout problems, the option to fix it by itself by wifi doesn`t work. I can´t access "normal" recovery and i think there is the problem (may got bricked while flashing Nougat?) I think its recovery problem, cause when i boot it up to the "half-installed" Android and go into setting "hard-reset" option i know it would boot up intoi recovery and would erease everything, while bootup it shows error "reset failed".
In fastbootmode i see bootloader: unlocked FRM: unlocked
I tried to install TWRP recovery with adb but get error: adb remote command not allowed
I downloaded like 15 different Android Versions 6+7 Emui 4.1+5 to try with force update but none worked, may i have to flash special version of recovery first?
I just want a normal version of android 6 or 7 i dont mind but at the moment with half working 7 "without" systemapps its a hardtime.
I hope someone can help me.
This isnt my first android device and im not a total noob i unlocked bootloader and flashed kernels on many other phones but with the W-09 where i did nothing special i dont get why "recovery got broken"
Thanks in advance

You haven't read other threads too well: more times people reported that the bootloader got locked after an update still declaring itself unlocked!
Second thing you have not found: the Nougat update consist of 2 packages and the second must be installed from TWRP.

nicolap8 said:
You haven't read other threads too well: more times people reported that the bootloader got locked after an update still declaring itself unlocked!
Second thing you have not found: the Nougat update consist of 2 packages and the second must be installed from TWRP.
Click to expand...
Click to collapse
thanks for your anwser, i read that so i also tried unlocking it "again" and it quotet it is also unlocked in adb. I also know that there are 2 packages. That you need TWRP i didnt know thanks so i am a bit smater now. I think i ll try "relock" and unlock it again might be the right way, thanks for the tip.

kivi90 said:
I think i ll try "relock" and unlock it again might be the right way, thanks for the tip.
Click to expand...
Click to collapse
This is nonsense. Unlock, install the right TWRP then install the second zip package.

nicolap8 said:
This is nonsense. Unlock, install the right TWRP then install the second zip package.
Click to expand...
Click to collapse
i cant unlock cause i dont have the code, on the huawei page i try do make an account and get the code by providing the necessary information.
I just uploaded a picture, i choose "before EMUI5" cause this is the only option i can choose "tablets". --> i choose "tablet wifi" , enter product model "BTV-W09" then the serialnumber i can see in setting: 28D6R17316XXXXXX but then i have the problem to input product id, it say i can get it through "Dialer" app (which i dont have in wifi model ) or the calculator. Problem is in my damaged installation there is no huawei calc, other calcs from store dont work (read that problem in other threats) I tried many apps from appstore to get a product ID but huawei site keeps saying wrong product ID =/
With the program DC Unlocker i am able to see a MEID i dont know if its the right one, i tried my luck with the Product ID Generator from Huawei but it doenst work. (device not supported)

It's very strange that it says bootloader unlocked if you have never unlocked...
And was very stupid to try to installl a beta release without before unlocking and taking a backup.
Exhange your device for a Nokia 3110!

nicolap8 said:
It's very strange that it says bootloader unlocked if you have never unlocked...
And was very stupid to try to installl a beta release without before unlocking and taking a backup.
Exhange your device for a Nokia 3110!
Click to expand...
Click to collapse
yeah at this device i never touched bootloader, i didnt think it would become such a big deal , i didnt want unlocked bootloader or other recovery just newest android. Never had any problems with the "force update function" to come back to stock. I tried DC Unlocker but cant get further cause device need to get into manufature mode (thorugh dialer or calculator which i both dont have) i hope maybe i find one more way.

Did you ever find a fix
Did you ever find a way to fix this. I'm in the same situation. I even did a VPN on my router to give me a Hong Kong address for erecovery and that still didn't work. I have the exact same product. Like you I tried to various attempts to download a new recovery, but nothing works. Nice hardware, but some of the worst software/firmware I have ever dealt with since starting with the first release of Android on the HTC Hero.

kivi90 said:
yeah at this device i never touched bootloader, i didnt think it would become such a big deal , i didnt want unlocked bootloader or other recovery just newest android. Never had any problems with the "force update function" to come back to stock. I tried DC Unlocker but cant get further cause device need to get into manufature mode (thorugh dialer or calculator which i both dont have) i hope maybe i find one more way.
Click to expand...
Click to collapse
I had mostly the same problem. I rolled back to 4.1 using the rollback and the actual 4.1 update.app. I think that puts you on C100 if I remember right. Tablet I have is C128 (USA) but no problem for this step. Get the Product ID from the calculator. Allow OEM unlock in the settings, then unlock it using the unlock code. Email yourself the unlock code because who knows if their website will even be functional next time. Alternatively you can extract the stock calculator from the update_data_usa.zip or whatever and try to use DC with 5.0. That second update zip does not install properly via the dload method, so a bunch of stock apps don't get installed. You can kind of hack it and flash it via TWRP but I didn't do it that way.
Or...you can use firmware finder to force an OTA from 4.1 right up to 5.0 (350), then take that last partial OTA to 351 after as well. The way to do that is via DNS in firmware finder. Find the Full OTA in firmware finder you want, send it to the updater by changing your DNS the way it tells you to, and when it does the OTA, everything will be properly installed basically the official way. Good as new. Flash TWRP to recovery2 and replace the erecovery. Keep the stock recovery as is. Install magisk. Golden.
---------- Post added at 03:36 AM ---------- Previous post was at 03:26 AM ----------
kivi90 said:
So i tried to do the rollback with:
HUAWEI MediaPad M3 8 Rollback Package%28BTV-W09 %2CC900B300%2C EMUI5.0%2BAndroid7.0 rollback to EMUI4.1%2BAndroid 6.0%29
The Installtion (force update) gets stuck at 5% and after like 3-5 minutes the tablet will boot up showing the same boot error that can be skipped with pressing powerbutton. I checked sytem and it still showed "android 7 + EMUI 5" but built : BTV-W09C900B300
I think this is the one i "need" to be able to install the "HUAWEI MediaPad M3 8 Firmware %28BTV-W09 %2CC100B006%2C EMUI4.1%2BAndroid 6.0%29"
Problem is regardless which "update.app" i try to force install will get stuck at 5% and give me same error.
Click to expand...
Click to collapse
Also, as far as the rollback, you need to do the first one (the C900 which is just a compatibility fix to allow rollback, previously used by beta testers I believe). Then you need to do the second one, the C100. If it is getting stuck, try downloading it again and be sure you don't have anything else in the /dload directory on either internal or the sd card. I had one on both at one point so maybe that happened to you. The C900 should be very quick but the C100 will slowly progress after 5% all the way around in several minutes.
When you get to updating back to 5.0, you can choose whichever region you want as long as it is a full OTA. C128 is USA and that's what I bought so that's what I picked. That gets you back in the right OTA update channel after that.

Hi guys,
I started as a novice and have learnt the hard way.
Has anyone tried rollback to EMUI 4.1 EU version on a US device (W09) and are there any problems I should be aware of?
I have had the exact same problem shared in this thread and have gone through the pain of finding a solution. My last resort is to rollback to 4.1 and restart the whole process.
@deV14nt: you suggested that when updating back to EMUI 5.0, I can choose the region even if my EMUI4.1 is EU version. How does this work?
Thanks in advance for your help.