[X]Assistant

[bauuuuuu]

Nubia Z9 Max (NX512J) - Official firmware
Snapdragon 615
Description | Discussion пїЅ | Purchase пїЅ | Z9 NX510J пїЅ | Nubia Z9 Max (NX512J) - Unofficial firmware пїЅ | Z9 mini NX511J - Unofficial firmware пїЅ | Official firmware (Snapdragon 615) пїЅ

Important information!

Disable firmware upgrade
Recommendations for the design of messages

Drivers and Utilities

ADB / Fastboot drivers
Nubia tool studio
Android SDK Tool

Official firmware

Rucommon

• V2.04
  
• V1.01
  
• v1.01 (restore from backup)

Z9 Max Youth Edition

• v9.5504/03/2018 Password: 7gsv MD5: C1E83F44C6825B88F8BF234EED72B7ACYandex
  
• v9.5310/31/2017 Password: cvoi MD5: D98E40CEE3498933DBEFD888F0637FDDYandex
  
• v9.2905/04/2017 Password: my9a MD5: 75901D075619CC590DB0B5DD4DDEBB90Yandex
  
• v9.2104/21/2016 Password: rc3z MD5: 58B029FDB5E05853030BE42393027C90C9Yandex
  
• v9.1504/21/2016 Password: v9wy MD5: F1FD5A8B986A4D2BDE17935E7380D1F9Yandex
  
• v9.0804/21/2016 Password: b7qh MD5: 8F050DDCE133024CC43556ED9BEC38A8Yandex

China Unicom operator

• v9.5604/03/2018 Password: t89u MD5: CC421F89DAE63B5BD063637C4A5DF47Cyandex
  
• v9.5410/31/2017 Password: 9otl MD5: A47D585C19466E5AF44DAEFA049F430Ayandex
  
• v9.2804.05.2017 Password: 2d5v MD5: E08E17633498572339F9C02844C7D278Yandex
  
• v9.2009/28/2016 Password: klzg MD5: DF8C38206BC8D31D0B7872D2458D0572Yandex
  
• v9.1407/06/2016 Password: 3sgk MD5: 27C65A0771BF10B04131EAA20FC4DEF5Yandex
  
• v9.0503/23/2016 Password: cmq4 MD5: B5A956D6F4ADF0BFDA84A68CC098162AYandex
  
• v4.0409/17/2015 Password: ikk4 MD5: 06BA5F9C2CE24771D0DE8F9E3D068E69https://yadi.sk/d/9vl4SCZH3UBrjp
  
• v2.1106/29/2015 Password: gus6 MD5: 8847AA117BE35DFC1279A3DEF87FAC3D
  
• v2.0905/07/2015 Password: mij7 MD5: A79D65791B340BCAD80D7A99AD0E6394

China Telecom operator

• v3.1807/23/2015 Password: 0ebw MD5: FAD9F6CD5EA41F34950C976876C9026B
  
• v3.0105/07/2015 Password: fa9i MD5: E14BBE7AD96D27ADD6A151A50A902F4F

Based on official

• Alterna_Mix_trackfromStuG75
  
• Z9 Max (NX512J) v 9.29 Bobrykfromsx_
  
• V 4.07frombauuuuuu
  
• V 4.05frombauuuuuu
  
• Z9 Max Youth Edition (NX512J) V9.21_cleanedfromproblem123
  
• Shorn ver. 9.21fromsx_
  
• Cleaning on the basis of. ver. 9.15fromsx_
  
• Translated by NubiaUI V9.05fromlouler
  
• Lightweight firmware 2.04fromsx_
  
• v 4.04from CUOCO92
  

Troubleshooting

This solves most of autoload and recovery problems. You should try this first.

Read this first.

Solving the problem with installing firmware

• Installation instructions for the NX512J native Chinese firmware CNCommon (9.21 and their ilk)
  
• Repair IMEI for NX512J
  
• Restore native IMEI in the absence of QCN backup
  
• If the Nubia emergency tool doesn't work and the phone is walled up
  
• Correct actions for Nubia 9.15 firmware
  
• Solving problems associated with recovery, stuck on the logo, etc.
  
• Switch from LightX V3.70 to regular firmware
  
• What to do if after installing 3.70 the phone does not turn on
  
• Solving problems with auto-rotate on RR and correct operation of Nubia Camera
  
• Instructions for installing firmware from Z9 mini and return to stock
  
• Bootloop, problems with Recovery, installing and restoring firmware stock
  
• Instructions for obtaining Root rights and running Recovery
  
• Restoration of GPS Cyanogenmod 13
  
• Gapps correctly working on CM13
  
• Return from Z9 mini firmware
  
• Patches for the correct operation of the auto-rotation on the firmware from Z9 mini
  
• The utility for restoration of restoration of bricks (port 9008)

Recovery / Root

Flash TWRP & Stock recovery
TWRP 3.0.2
Stock recovery JD v1.01
"Utility for obtaining Root rights and installing Recovery (works only for android 5.0)

miscellanea

пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅ ZTE Nubia Z9 max download

On our device fit firmware fromZ9 miniOf the critical bugs seen: the orientation of the screen in the auto-rotate mode is broken; incorrect operation of the communication module (seen personally in St. Petersburg, MTS / Megaphone operators in the zone with unstable 3G / 2G reception, no communication /
Updated repository with Cyanogenmod firmware and TWRP recovery

Survey Screenshots

07-11-2016

Post has been editeddraiv88 - 18.04.19, 16:43

Reason for editing: 9.55, 9.56

[kynpuc]

Instructions for getting Root and Starting Recovery

1. Download and install on computerThese Drivers
2. Download and unpack to the root of the C: \ driveArchive with Utility
3. Download native for our deviceTWRP RecoveryArchive file with extensionZIP and throw the archive on the flash drive, or in the internal memory of the phone.
4. We connect the device with a USB cable to the computer, if it is better to connect the BB stationary to the ports located directly on the motherboard, in the developer’s settings we enable USB debugging “Settings (Settings)” - “About Phone (About Phone)” (build number) 8 times, go back to "Settings" - "More (More Option)" - "Developer Options", turn on "USB Debugging Mode"
5. In the folder with the downloaded and unpacked utility, we find and run the file "ThemePush.bat".
6. In the window that opens on the screen, 7 options will be offered:
-Install Driver - install the driver;
-Install English TWRP 2.8.6.0 - install English TWRP 2.8.6.0;
-Install Original Recovery - install the original recovery;
-Temporarily use English TWRP - download TWRP once;
-One-Click Root (superuser version) - Ruth in one click SuperSU;
-One-Click Root (kinguser version) - Ruth in one click KingUser.
-Finish to Exit- Finish and exit.
We are interested in points 4 and 5, with the help of point 5 we get Root, and with the help of 4We start !!!recovery
7. After running Recovery from the utility, run (go) in it inInstal, find previously downloaded to the phone TWRP Recovery and install it.
8. In the case of correct actions, we get a device with custom Recovery and Root rights.

P.S. Proposals for making amendments to the instructions are written in koumiss, there we also appeal in case of problems. Successful customization !!!

Post has been editedkynpuc - 26.01.16, 10:53

[Kirux0]

Hello!
At night looking I think to flash my MAX firmware from a mini, namely 3.70 lightX. She is on my mini and very happy.

Has anyone already walked on such a rake? Will there be difficulties, will it start at all, will the connection fall off?

[kynpuc]

Kirux0 @ 01/06/2016, 20:52

Has anyone already walked on such a rake? Will there be difficulties, will it start at all, will the connection fall off?

Cap-Miscellaneous in brief described his observations. There will be something to add, write!

[rdiamond1984]

Glitches seen on the off-firmware:
Sometimes the keyboard stops working on pop-ups (quick answer viber, what's up)
The sound disappears on incoming calls, it is treated by reboot
The subscriber becomes unavailable, when the phone is turned on, a reboot helps, but here it may be a buggy, not sure.
The camera, compared to the mini, is very sad.

Post has been editedrdiamond1984 - 06.01.16, 21:49

[kynpuc]

rdiamond1984
off from mini, or for ours?

[rdiamond1984]

Off from jd for z9 max 2gb. I have a mini phone and firmware light and mod.

[pumbaster]

rdiamond1984 @ 01/06/2016, 21:42

The camera, compared to the mini, is very sad.

And the front and back cameras on the mini and 512 max are identical? And what is the beauty of the camera on the mini? You can try to get a HAL camera from mini to cyan for max, if there really is any difference.

[alexdoux25]

[email protected], 00:17

And the front and back cameras on the mini and 512 max are identical?

Iron is the same.
As for the CM 13, the camera shoots there worse than on the drain. I tried various applications (open camera, FX camera, F5 camera, MX camera), the amount of noise, especially in low light, exceeds the limit. On the stock, too, it's not a fountain, but it seems it was better.

Post has been editedalexdoux25 - 07.01.16, 00:42

[slavar72]

rdiamond1984 @ 01/06/2016, 23:42

Glitches seen on the off-firmware: Sometimes the keyboard stops working on pop-up windows (quick response viber, what's up) The sound disappears when there are incoming calls, it is treated with reboot The subscriber becomes unavailable, when the phone is turned on, it helps reboot, but here Simka is buggy, not sure. , compared to the mini, very sad.

Thanks for the answer. Smart since November. The only thing I put on the office. The firmware is another launcher (my own is generally inconvenient for me). Now the answer for glitches (for me personally):
The keyboard always works, the sound of calls has not disappeared even once. The camera is probably not ideal, but far from the worst (I don’t know about the mini. In any case, it’s not difficult to pull it out and put it on the office). Maybe the wife something crooked set or removed from this glitches? Mine, too, this sin sometimes)))

PS: I remembered, I rebooted myself once. True, I don’t know a single smart who sometimes wouldn’t go on their own reboot)

Post has been editedslavar72 - 07.01.16, 00:59

[kynpuc]

We have the collector from source codes, maybe the portable firmware has gotten Max? Cyan is good, but why not screw something worthwhile, at least for a change

[camypau666]

In the old theme there is a link to the black theme for the settings menu, the dialer, etc.
It is written to put through the application "Themes", so, does anyone have such an application? I'm not here. Or how else to change the design of the menu without changing the firmware for example?

Post has been editedcamypau666 - 07.01.16, 01:36

[rdiamond1984]

If the sensor is repaired, then it will be possible to sew mini firmware, and there are already a lot of them for taste and color)

[kynpuc]

camypau666,
There are themes in 4.04 from unicom, this item is missing in the firmware from the Jews ...

Added 01/07/2016 3:05 AM:

rdiamond1984
Different control algorithms, or commands, an enthusiast who understands need

[Solarwareare]

As promised, I figured out the orientation sensor.
My opinion is that the sensor chip itself is soldered differently on the boards, this is why the readings are turned. Well, either the sensors themselves are different ...
And I also tried to find the sensor driver (so as not to edit the framework, I thought maybe the original library could be enough to put it in place) and could not find it. The only place where the sensor is mentioned is the NON-HLOS.bin file - the sensor driver is sitting in it. Although I have always believed that this is a "modem" firmware ...
By the way, even now the thought has arisen - the NON-HLOS.bin file is a disk image with FAT16 and can be easily disassembled. I just looked, in it there are 3 files in which the accelerometer sensor is mentioned: adsp.b12, adsp.b14 and adsp.mbn
Maybe if it is them from the original firmware that they return to their place in the mini firmware, then the orientation will be restored by itself. But honestly, I absolutely do not know if it is possible to modify NON-HLOS.bin (maybe it has a checksum or a signature - hz) - this is true, thoughts are heard ... If there are experts, tell me.

Returning to the topic - I made a patch, tested it on my phone - everything works.
Now I can either put the module for Xposed, or throw off your (well, in the sense of not native but from mini) framework.jar file - I will correct it.

[kynpuc]

SolarWarez,
If Non-Hlos is related to the connection, maybe the rest of the files can be changed in order for the device to work as a telephone?

[An @ dmin]

Solarwareare
I disassembled non-hlos.bin from runoff 1.01 - there are no files specified by you.
In general, of course, the easiest way is to take solid firmware from a mini, for example, MIUI, and to insert the necessary files (including non-hlos) into the substitution. I hope in a week I will have a body - I will have to try.
Ps. If at least someone put custom firmware from the mini, just like it is, without changing, kernels, etc. - please tell about it. Has the device turned off?

Post has been editedAn @ dmin - 07.01.16, 22:07

[rdiamond1984]

IMHO it is better not to edit the Framework, but to do it with the help of the module.
I would also like to understand how to properly backup current firmware? Through tvrp? Will he recover later? I read that there were problems, I could be wrong. Or standard backup backup?

[alexdoux25]

SolarWarez @ 01/07/2016, 19:27

Returning to the topic - I made a patch, tested it on my phone - everything works.
Now I can either put the module for Xposed, or throw off your (well, in the sense of not native but from mini) framework.jar file - I will correct it.

Is this patch not universal, in the sense of any mini firmware? If you understand correctly, then this file "NON-HLOS.bin" is the same in all mini firmware. Then just make one patch, which is suitable for any firmware?
Now I’ll download some mini firmware and lay out framework.jar

[alexdoux25]

Well, here it is from the miui_5.0_z9mini_v6.6.6.0_bobN firmware, which is praised on the Z9 mini branch:framework.jar(5.54 MB)

[rdiamond1984]

I do not know who and what praises there))) I have light 3.70, I am completely satisfied;)