[Firmware] Xiaomi Mi Max 3 [nitrogen] [Auto updated daily!]

yshalsager · Dec 29, 2018 at 8:25 AM

MIUI 10 8.12.27 Global/China Beta ROM Firmware

Telegram Channels: https://t.me/XiaomiFirmwareUpdater | https://t.me/MIUIUpdatesTracker

Download Links are available on our site

You can download form OSDN or GitHub.
Downloads:

Developer ROMs Firmware

Firmware without ARB

For whyred, nitrogen, sakura and wayne
OSDN:

Developer ROMs Firmware

Firmware-less ROMs

For whyred, nitrogen, sakura and wayne
OSDN:

Developer Firmware-less ROMs

Donation:
A donation was never necessary, but It's making life easier for me and guarantees paying server costs, as you know, both of my XiaomiFirmwareUpdater and MIUIUpdatesTracker scripts are automated, running on a Linux server. If you want these projects to continue and provide the best services to Xiaomi users, you can help me by buying me a Pizza here: https://paypal.me/yshalsager

yshalsager · Dec 29, 2018 at 8:26 AM

Deleted

ZanaGB · Oct 3, 2015 21 1 0

Here's a question.

For a Max 3 purchased last week that has yet to arrive, and i assume will come with an ARB-enabled firmware, will anything happen if i flash the non arb firmware file? or am i locked to use only the ARB-Enabled firmwares?

yshalsager · Jan 2, 2019 at 8:52 AM

ZanaGB said:
Here's a question.

For a Max 3 purchased last week that has yet to arrive, and i assume will come with an ARB-enabled firmware, will anything happen if i flash the non arb firmware file? or am i locked to use only the ARB-Enabled firmwares?

Nothing will happen and there's no use of doing this.
stick to newer versions of firmware and don't flash old with lower arb

ZanaGB · Oct 3, 2015 21 1 0

yshalsager said:
Nothing will happen and there's no use of doing this.
stick to newer versions of firmware and don't flash old with lower arb

I guess it's better than recklessly bricking the device.

palmdude · Jan 4, 2019 at 8:01 PM

Thanks for this. I am new to the Xiaomi world, and this topic was always a mystery to me ... But now I got it

I tried to flash fw-less_nitrogen_miui_MIMAX3_8.12.13_4c12517959_9.0.zip with two different TWRP versions (https://forum.xda-developers.com/mi-max-3/development/recovery-twrp-3-2-3-1-nitrogen-t3866084). But I only get a "Zip file is corrupt!" message. I verified the zip file and the file is ok (there is no download corruption etc)..

I am able other flash recovery ROMs without any issues (for example xiaomi.eu).

Any idea what could be wrong?

nijel8 · Jan 4, 2019 at 10:04 PM

palmdude said:
Thanks for this. I am new to the Xiaomi world, and this topic was always a mystery to me ... But now I got it

I tried to flash fw-less_nitrogen_miui_MIMAX3_8.12.13_4c12517959_9.0.zip with two different TWRP versions (https://forum.xda-developers.com/mi-max-3/development/recovery-twrp-3-2-3-1-nitrogen-t3866084). But I only get a "Zip file is corrupt!" message. I verified the zip file and the file is ok (there is no download corruption etc)..

I am able other flash recovery ROMs without any issues (for example xiaomi.eu).

Any idea what could be wrong?

recovery log???

palmdude · Jan 5, 2019 at 6:14 AM

nijel8 said:
recovery log???

The log file does not seem to contain any useful info regarding this issue, but I sent it to you via PM.

I also used the "create_flashable_firmware" tool to create a zip file (fw-less_nitrogen_miui_MIMAX3_8.12.27_f1e1988397_9.0), but TWRP was not able to flash that either.

Thanks for looking into this.

nijel8 · Jan 5, 2019 at 6:58 AM

palmdude said:
The log file does not seem to contain any useful info regarding this issue, but I sent it to you via PM.

I also used the "create_flashable_firmware" tool to create a zip file (fw-less_nitrogen_miui_MIMAX3_8.12.27_f1e1988397_9.0), but TWRP was not able to flash that either.

Thanks for looking into this.

It was helpful, pointed me to the exact location in twrp code and it shows that the standard c++ zip library cannot open your zip.
Check your PM and don't use fishy tools. 7z is all you need, doesn't break zips. Definitely some non-standart zip is created...

palmdude · Jan 5, 2019 at 7:20 AM

nijel8 said:
Check your PM and don't use fishy tools. ... Definitely some non-standart zip is created...

Just to clarify, I did not use any fishy tools. I just downloaded the zip file provided by @yshalsager. Having said that, I agree that some "non-standard" zip (zip64?) is by created by "create_flashable_firmware" tool. That is also the reason why I posted my "bug" report in this topic and not your TWRP topic

Hope that makes sense. But thanks for confirming the issue

Hope @yshalsager will comment on this.

TL;DR TWRP does not seem to be able to handle zip64?

yshalsager · Jan 5, 2019 at 7:56 AM

palmdude said:
Just to clarify, I did not use any fishy tools. I just downloaded the zip file provided by @yshalsager. Having said that, I agree that some "non-standard" zip (zip64?) is by created by "create_flashable_firmware" tool. That is also the reason why I posted my "bug" report in this topic and not your TWRP topic Hope that makes sense. But thanks for confirming the issue Hope @yshalsager will comment on this.

TL;DR TWRP does not seem to be able to handle zip64?

Well, the generated zip file should be very standard.
Tbh it's the first time to see such issue among all devices.
If it was the first message above only, I'd say courrpted upload or download. But seems the issue is still present if you created your own zip files.
Can you try the normal firmware version?
It's made with the same tool as you know.
And BTW @nijel8 nice to see you again

palmdude · Jan 5, 2019 at 8:03 AM

yshalsager said:
Well, the generated zip file should be very standard.
Tbh it's the first time to see such issue among all devices.
If it was the first message above only, I'd say courrpted upload or download. But seems the issue is still present if you created your own zip files.
Can you try the normal firmware version?
It's made with the same tool as you know.

Thanks for your response. I think the issue is that the firmware creator uses the zip64 format which is not understood by TWRP (at least the versions I tried). If you re-zip the archive from zip64 to zip, then TWRP (@nijel8) is able to flash the archive.

I guess you are implying that TWRP (@nijel8) should be able to understand the zip64 format, right?

yshalsager · Jan 5, 2019 at 9:37 AM

palmdude said:
Thanks for your response. I think the issue is that the firmware creator uses the zip64 format which is not understood by TWRP (at least the versions I tried). If you re-zip the archive from zip64 to zip, then TWRP (@nijel8) is able to flash the archive.

I guess you are implying that TWRP (@nijel8) should be able to understand the zip64 format, right?

If the problem can be fixed from recovery side that would be okay.
If not I can try to stop using zip64

nijel8 · Jan 5, 2019

yshalsager said:
If the problem can be fixed from recovery side that would be okay.
If not I can try to stop using zip64

I am not familiar in details of the zip library twrp source uses but now that I know the culprit I 'see if I can do something about it. BTW twrp compiles that library from android tree it is build with(omnirom, lineage, aosp etc).

EDIT: Investigating python make_archive function it creates zip64 archives only when resulting zip file is > 2gb. I tested your script with simple test zip which only prints to twrp console and had no problem. Just for info twrp has no problems with miui zips > 2gb so the problem lies in the python's internal way of creating large zips. I can fix that probably in twrp but what about other recovery variants? Your zips > 2gp will still have comparability problems with them. So I think you should find better way of creating your zips ensuring comparability across the board IMO...