yashsingh1/xdaforums huggingface dataset:
[Huawei Mediapad M3 Questions & Answers] sergio_sant:
It won't get Oreo just like the M2 never got Nougat.

I think it wouldn't be hard for Huawei to bring Oreo to the M3, since the M5 has it and the hardware has not changed that much. But they don't care at all.

On the other hand, I would be pleased if there were custom ROMs available, so at least we could have Oreo (and even Pie) unofficially, but Kirin processors have always been a problem for developers.
[Huawei Mediapad M3 Questions & Answers] gt_cruiser:
Exactly the reason why my next device will have a "mainstream" chipset. At this stage about how they treat end users, I am not going buy any Huawei devices in the future.
[Huawei Mediapad M3 Questions & Answers] Matt8504:
I've already bought mediapad m5 10'8. Its great and amazing and better device. I sold out the m3 for a good price and just gave 100 euro more to buy m5. M3 got june patch so it's not completely forgotten. The desktop mode on 10'8 is very useful. Otherwise it's not big difference between the OS in both tablets. Ive own p20 which is on oreo 8.1 and it act and looks completely different. I dont know why maybe because is a phone, or because p20 is on 8.1 instead of 8.0 on m5.
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
Introduction

This is the bootloader unlock from ZTE. It was provided to me in private email by a ZTE engineer.

Warning

This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.

Note

After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool's unlock are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot, which provides a way to flash a custom boot and recovery (among other things).

Flashing Instructions

Place axon_mini_unlock.zip on the root of your sdcard.

Reboot into recovery.

Select "Apply update from SD card".

Select axon_mini_unlock.zip.

Usage Instructions

After the package is flashed, you may boot into the bootloader:

adb reboot bootloader

Once in the bootloader, you will see an on-screen menu. Additionally, you may access the typical fastboot commands:

fastboot oem device-info

fastboot oem unlock

fastboot flash ...

... etc ...

Download

axon_mini_unlock.zip

md5: ea8f1a21c8a46b3045d00f17a37fe359
[ZTE Axon 7 Mini Guides, News, & Discussion] Deleted member 7646815:
So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
Yes, that is correct.
[ZTE Axon 7 Mini Guides, News, & Discussion] tprfd:
Is this something your contact mentioned or something that you believe based on your experience?

Any harm in trying it on verdandi/other versions without any risk of bricking?

Any way to confirm this is also the case with other versions as well?

Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
[ZTE Axon 7 Mini Guides, News, & Discussion] bromanbro:
Yeah...verdandi is stuck on Marshmellow. But since it has different hardware it could brick if this is tried.
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
The ZTE engineer is USA based, he is not on the China development team (read: probably a support engineer). He said: "I attached the unlock update zip package, please try it. It is based on B14 build."

Sorry, that's all I have to go by for "official" information.

I do not want to be responsible for anyone bricking their device, so I cannot claim that this bootloader will work with anything other than a tulip device running 7.1.1 b14.

If you want to try and report back, I'm sure others will appreciate it. But I can't be responsible for the results.
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
Oh, and here is some more information to help you decide...

The volume key combo to enter EDL is handled by aboot (bootloader, eg. the thing we are flashing). This means even if you aren't currently able to use the key combo, you should be able to use it with the new aboot here. And if you can get to EDL, you can never really brick the device.

The volume key combo is detected very early in the aboot code. Like, first thing after basic platform init. So even if this isn't compatible with your device, it's likely we could restore the old aboot (assuming you back it up first, of course).

I'm convinced that the tulip is not locked based on my investigation today. So I have no idea if this aboot is properly signed. If your device is locked and this aboot is not signed properly, the lower boot loader won't load it. I'm not quite sure if that kicks you into EDL or not.

Not sure if that makes the decision easier or harder... ;)
[ZTE Axon 7 Mini Guides, News, & Discussion] tprfd:
How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?

I will have a read about backing up aboot and see what I come up with concerning getting into edl.
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
So here's the deal...

I initially assumed the bootloader was locked because... well... it's supposed to be. So I found the place in aboot code where it checks the lock flag in the devinfo partition. I used the firehose to write unlocked to that flag. Then I built TWRP, flashed it and it booted. So I assumed everything was working just as I expected.

Today, I flashed the aboot with fastboot support and ran "fastboot oem device-info". It said that my device was locked. So I went to look and, sure enough, my devinfo partition flag was still set. Hmm, that's odd.

So I wrote locked back to the flag. TWRP still booted. Now things are looking pretty suspicious.

But maybe the new aboot doesn't even support locking? So I flashed the original b14 version of aboot and TWRP still booted.

That's pretty hard evidence that aboot is ignoring the lock flag. I don't know what they did -- whether they just removed the code that reads the lock flag or introduced a bug or what.

This does not necessarily mean that the lower layers are unlocked. That is, the lower boot loader may still required a properly signed aboot. I don't know, and I'm not ready to brick my device trying to find out.
[ZTE Axon 7 Mini Guides, News, & Discussion] maestromony:
Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.

Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
Ah, yes, you have the euro model. See the "calling all mini owners" thread, posts #76 and #77.
[ZTE Axon 7 Mini Guides, News, & Discussion] yeshivabachur:
i get a message saying "cant update from sd card?"
[ZTE Axon 7 Mini Guides, News, & Discussion] Deleted member 7646815:
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.
[ZTE Axon 7 Mini Guides, News, & Discussion] Aries2010:
My battery was 80%+ mine still said can't update from sdcard
[ZTE Axon 7 Mini Guides, News, & Discussion] Deleted member 7646815:
Try turning on the OEM unlock setting in developer settings.
[ZTE Axon 7 Mini Guides, News, & Discussion] Aries2010:
Thank you so much that worked I appreciate the it :). Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware
[ZTE Axon 7 Mini Guides, News, & Discussion] Deleted member 7646815:
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.
[ZTE Axon 7 Mini Guides, News, & Discussion] Aries2010:
Thank you sir I appreciate it I shall try it tomorrow.
[ZTE Axon 7 Mini Guides, News, & Discussion] yeshivabachur:
here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
The "standard" (not Samsung) method of updating via OTA is to ship:

1. Full images of any firmware partitions (rpm, tz, aboot, etc.)

2. Full image of boot.

3. A delta (patch) to system.

Also note that custom recoveries generally do not work with vendor OTA's.

This means that if you wish to apply an OTA, you must first have stock recovery and a completely pristine, unmodified system partition. The rest doesn't matter.
[ZTE Axon 7 Mini Guides, News, & Discussion] :
deleted post
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
1. Please don't quote the entire OP. Nobody wants to read all of that again.

2. This is off-topic. You have a thread for K88, and I am active there.
[ZTE Axon 7 Mini Guides, News, & Discussion] :
sorry
[ZTE Axon 7 Mini Guides, News, & Discussion] blessed01101:
Im taking a big ole stab in the dark to suppose this also applies to "sd card" updates directly from ZTE? Anyone know if they have a flashing tool available for installing OEM updates?
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
Yes this also applies to sdcard updates.

I've packaged recovery flashable firmware and system/boot in another thread. Please give them a try.
[ZTE Axon 7 Mini Guides, News, & Discussion] lchichiarelli:
Hi,

I kinda of briked my Mini 7 in the process of rooting it.

Everything went smooth (TWRP etc) until I've installed SuperSu 2.82.

Now I've installed the stock bootimage, and the only option that I have is to boot in standard recovery and use ADB sideload.

I've tried to install the Axon Mini Unlock from

hxxp://code.nwwn.com/files/android/axon7mini/axon_mini_unlock.zip

but I receive the error as you can see in the image:

hxxps://imgur.com/9WpX6Aa

sorry for the fake links, but as a new user I cannot post links right now.

Please can someone help me sending me a working boot image to use with my device with adb sideload command?

thanks a lot
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
The error flashing the unlock package is because the unlock package only supports the US model. It checks your model before starting and will refuse to flash on EU models.

You didn't mention how you got from having TWRP installed to having stock recovery installed. If you read the OP in the tuliptool thread, it says to never flash both boot and recovery at the same time. If you always ensure that you can boot into TWRP before flashing boot, and you can boot into Android before flashing recovery, you should never be in this situation.

If you have a EU model with stock recovery and you cannot boot into Android, you likely cannot access EDL. I would try flashing a full OTA for the EU model. I was given this one, for example:

http://code.nwwn.com/files/android/axon7mini/B2017G-EU-v1.2.0-b12-ota-full.zip
[ZTE Axon 7 Mini Guides, News, & Discussion] lchichiarelli:
tmd thanks for the reply.

Actually my Axon 7 Mini is a US model, what I've done is flashing with EU bootstack, stockrecovery and stocksystem from TWRP

I've done this because I need italian language and in the US system is not available.

Other users reported that this is possible:

hxxps://xdaforums.com/axon-7-mini/help/reflash-b2017g-model-to-european-stock-t3592268

At this point all I need is to be able to make the phone work again? You suggest that if I use the full OTA you linkedfrom ADB sideload it will work?

Thanks a lot
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
Ah, okay, thanks for the clarification.

If you are on the EU boot stack, then the linked OTA *should* get your phone working again. Once it's working, I would recommend flashing TWRP and keeping it. The stock recovery is very limiting and it's easy to get stuck like you are now.

I'm not sure exactly what is different between US and EU models. The hardware obviously has *some* differences but not many. So while this procedure may work, it's obviously not a supported configuration.

Ideally, the EU boot/system would work with the US boot stack. That would allow you to have the US modem and the US aboot. But I don't know if that works or not. If it doesn't, I would at least try using the US version of aboot. The reason is that it allows EDL mode with a key combo. This is very handy for situations like yours. You just need to flash TWRP using tuliptool to unbrick.
[ZTE Axon 7 Mini Guides, News, & Discussion] lchichiarelli:
I've tried to adb sideload the ROM you suggested but I receive the following error:

loading: 'c:\B2017G-EU-v1.2.0-b12-ota-full.zip'

* cannot read 'c:\B2017G-EU-v1.2.0-b12-ota-full.zip' *

I've tried to download it twice but I get the same error almost instantly after I run the command...

any ideas????

thanks in advance

---------- Post added at 11:01 PM ---------- Previous post was at 10:45 PM ----------

Ok I've figured out the cannot read error and fixed it using adb 64bit for Windows.

Anyway adb sideload command failed now:

(adbd status 1)

Installation aborted.

:crying: I'm stuck
[ZTE Axon 7 Mini Guides, News, & Discussion] k500zm:
[MENTION=8794984]lchichiarelli[/MENTION] - you are using the wrong file ! Inside the zip file named B2017G-EU-v1.2.0-b12-ota-full.zip there is a file you should extract called update.zip - This is the file you should be using ;)

Give it a go and it should work well
[ZTE Axon 7 Mini Guides, News, & Discussion] lchichiarelli:
[MENTION=5380232]k500zm[/MENTION] thanks for the info....I've extracted the B2017G-EU-v1.2.0-b12-ota-full.zip and here the content:

Directory di c:\B2017G-EU-v1.2.0-b12-ota-full

19/12/2017 00:19 <DIR> .

19/12/2017 00:19 <DIR> ..

08/03/2011 16:13 16.777.216 adspso.bin

08/03/2011 16:13 21.978.408 boot.img

08/03/2011 16:13 10.670 build.prop

08/03/2011 16:13 176.604 cmnlib.mbn

08/03/2011 16:13 0 ddr.mbn

08/03/2011 16:13 556.420 emmc_appsboot.mbn

08/03/2011 16:13 204.731 file_contexts.bin

08/03/2011 16:13 73.728 hyp.mbn

08/03/2011 16:13 177.596 keymaster.mbn

19/12/2017 00:19 <DIR> META-INF

08/03/2011 16:13 80.402.944 NON-HLOS.bin

08/03/2011 16:13 23.614.764 recovery.img

08/03/2011 16:13 167.084 rpm.mbn

08/03/2011 16:13 328.996 sbl1.mbn

08/03/2011 16:13 7.864.320 splash.img

08/03/2011 16:13 3.737.362.432 system.new.dat

08/03/2011 16:13 0 system.patch.dat

08/03/2011 16:13 156.082 system.transfer.list

08/03/2011 16:13 636.740 tz.mbn

:confused: cannot see the update.zip
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
Note that [MENTION=5380232]k500zm[/MENTION] is incorrect. The OTA file is the proper zip. It is named update.zip when you download it as an OTA file. I renamed it for clarity.

I don't know what the adbd status 1 is all about. Perhaps you ran sideload before selecting the sideload item in recovery?

If you cannot sideload it, you can put it on the root of an sdcard and name it update.zip, then choose install from sdcard in recovery.
[ZTE Axon 7 Mini Guides, News, & Discussion] k500zm:
[MENTION=4126377]tdm[/MENTION] [MENTION=8794984]lchichiarelli[/MENTION] Try renaming the file " update.zip " and try it :)
[ZTE Axon 7 Mini Guides, News, & Discussion] lchichiarelli:
[MENTION=4126377]tdm[/MENTION] quick update...I've downloaded the B2017G-US-v1.2.0-b12-ota-full.zip and with this file if I run the adb sideload command it move forward, reaches around 50% and then throw an error:

Opening update package...

Verifying update package...

Update package verification took 488.7 s (result 0).

Installing update...

assert failed: getprop("ro.product.name") == "P8852A12"

E:Error in /sideload/package.zip

(Status 8)

Installation aborted.

Seems like it doesn't like the product name, infact my Adroid recovery says ZTE/P852A11/tulip

Regarding the sd card, I just need a microsd in FAT32?

Please tell me my phone is not bricked...

---------- Post added at 11:51 PM ---------- Previous post was at 11:48 PM ----------

[MENTION=5380232]k500zm[/MENTION]

tried that with the EU zip file with no luck (fail instantly):

(adbd status 1)

Installation aborted.
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
That is correct, the US file will fail because it expects a US device (or more specifically a US recovery, as the recovery is responsible for setting ro.product.name). You must use the EU file.

I would try putting the EU zip file on the root of the sdcard (named update.zip). Any standard microsd should work.
[ZTE Axon 7 Mini Guides, News, & Discussion] lchichiarelli:
[MENTION=4126377]tdm[/MENTION] thanks for your help but no luck with sd card

once I tap the option Apply update from SD card I receive the error:

Supported API: 3

Sorry, you can't sdcard upgrade

I'm lost at this point...

The strange thing is that with adb sideload the EU ota gives error instantly instead the US one takes few minutes before sending the error.
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
Hmm, so they disabled sdcard install? That's not very nice.

I have no clue why the EU zip would fail instantly. But then again, I've never used it... I just posted the file that I was given, as it seemed legit.

Your device is definitely not permanently bricked, but the only way out I can see is to find a valid working full OTA for an EU model. Maybe you can search around the ZTE support site or the ZTE forums...?
[ZTE Axon 7 Mini Guides, News, & Discussion] :
It originally wouldn't let me update from SD card the first try, but enabling the OEM unlock setting fixed that.
[ZTE Axon 7 Mini Guides, News, & Discussion] lchichiarelli:
[MENTION=7646815]JoeGatto[/MENTION]

How can I enable OEM unlock if the only option I have is to boot into standard recovery?

Also SD update seems disabled so my only way I can see is going with adb sideload.

[MENTION=4126377]tdm[/MENTION]

I've googled around and found 2 full ota update.zip packages for the B2017G EU one in a russian website and one on a Spanish one.

Both of them fails instantly via adb sideload like the EU file you provided.

At the moment the only zip that begins the installation is the US full ota that we both know will not work anymore.

There is some way to edit the US full ota package and change the P852A12 with P852A11 so that the installation can continue without errors?

Can't believe I bricked my wife's device in such a stupid way...

Hope someone can point me in the right direction if any...

Thanks
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
[MENTION=8794984]lchichiarelli[/MENTION] ...

You cannot enable OEM unlock. But that's fine, sideload seems to be functional for you. The issue is just finding an OTA that recovery will accept.

I can poke around from here, but I need to know what recovery you are running.... preferably a link to where you got it, if it's not from my web server. The EU OTA package on my web server that includes a recovery. I can flash that to troubleshoot.
[ZTE Axon 7 Mini Guides, News, & Discussion] lchichiarelli:
[MENTION=4126377]tdm[/MENTION]

thanks for your effort helping me...here all the steps I've take to reach this point:

My phone is a B2017G US Model. It was on B14 release

I've used all file from your web space hxxp://code.nwwn.com/files/android/axon7mini/

I've installed tuliptool and twrp

From TWRP recovery I've installed SuperSU latest version 2.82 and from that moment the phone stopped booting (ZTE logo only)

TWRP was still working and from there I've flashed EU bootstack, bootrecovery and bootsystem from your site.

Since that I'm only able to boot in standard recovery as showed in this picture: hxxps://imgur.com/9WpX6Aa

let me know if you need any more info...
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
Okay, thanks for the explanation. It seems like your phone stopped booting because you modified the system partition but didn't flash the noverity boot image. That's not a problem, you could have easily recovered. But then flashing the EU boot stack killed EDL and the EU recovery killed TWRP.

I've flashed the EU recovery on my phone and tried to sideload the EU OTA. It looks like adb is refusing to load the file because it's too large (more than 2gb). This should be fixable. What OS are you running, and where did you get adb?
[ZTE Axon 7 Mini Guides, News, & Discussion] lchichiarelli:
Yes, I faced the same problem, you just need to use adb 64bit from here:

https://www.asus.com/zentalk/thread-119788-1-1.html

I'm running Windows 10 64bit

Thanks

---------- Post added at 09:07 PM ---------- Previous post was at 08:53 PM ----------

I just tried also with the lates adb from here:

https://www.xda-developers.com/install-adb-windows-macos-linux/

still no luck.

Trying to flash your file B2017G-EU-v1.2.0-b12-stocksystem.zip throw a different error:

E:Signature verification failed

E:Error: 21

Installation aborted
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
Well, if you have a 64-bit adb already, then I'm not sure that this is going to work. The device side may also have a 32-bit limitation. But I can continue to try.

The ideal situation would be to find a EU OTA file that is less than 2gb. But I don't know if there is one available.

Edit:

I've looked through the ZTE support site and found several different regional models. But unfortunately the install file exceeds 2gb for all of them. So if you still cannot get the sdcard method to work, the only hope is that the device sideload code is 64-bit clean.

I'm running Linux and I fixed one 32-bit error, now I am seeing another. I'll let you know how it goes.
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
I've verified everything looks good from the host side now. Unfortunately, it looks like the device's sideload code is not taking files over 2gb. The recovery log says this:

file has too many blocks (4294935212)

That is a result of wrap-around due to a signed 32-bit value.

So I'm out of ideas. Sorry. :(
[ZTE Axon 7 Mini Guides, News, & Discussion] lchichiarelli:
[MENTION=4126377]tdm[/MENTION]

damn, I've found an official ZTE recovery zip here: http://www.ztedevice.com/support/detail?id=6CCC18CC9451416C8A01BED5174B5762#software

but it's not clear which region it is. Anyway I got the same error.

So you are saying that the only way would be find a recovery for EU region smaller than 2GB and using adb 32bit?

it will be ok also android 6 based?

Also why with the US recovery file the process start with adb 64bit?
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
What you have found is an OTA package. The ZTE support site has OTA packages for many different models. Any of the EU packages should work on your phone with the EU recovery.

However, due to a limitation in the sideload code, you will not be able to sideload any of them that exceed 2gb in size. And, unfortunately, all the current images are just over 2gb.

If you can find a full OTA package for any of the EU models which is less than 2gb in size, it should work. Even if it's android 6. But I don't know if such a package even exists.

Another possible route is to look into ZTE tools that can work with DFU mode. I have no experience with these but they may be able to restore your phone.
[ZTE Axon 7 Mini Guides, News, & Discussion] lchichiarelli:
[MENTION=4126377]tdm[/MENTION]

you mean a tool like this?

http://flashtool.org/8/download-ZTE-flash-tool.html
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
I have no idea... I never used anything but the standard Qualcomm tools.
[ZTE Axon 7 Mini Guides, News, & Discussion] lchichiarelli:
mmm thanks anyway...but just in case what I have to flash with the tool in DFU mode? the full recovery image US or EU?
[ZTE Axon 7 Mini Guides, News, & Discussion] tdm:
I don't know .. if you get that far, try one and then the other.