[Moto Maxx General] hpbrasil:
Resurrect the Moto Maxx after having upgraded from 4.4 to 5.0 over the air.

We were reluctant to do this tutorial and make available to all for a few reasons. First that the procedures require the minimum of knowledge and insight so that everything works without a problem. We also wanted to do it all 'automated' way, but we face the second difficulty which is exactly the difficulty of predicting and making a script 'universal', as each computer and / or cell reacts in a different way. Finally, it is difficult to conduct tests and provide 'prints' as none of our devices have been 'brick'.

So, please understand the difficulty in trying to explain something that is different for each phone / computer, and just try the procedures who really feel safe in it performs. Remembering that we are not responsible for any damage that may occur on your phone or PC.

INTRODUCTION

This tutorial deserves a light introduction for us to understand the likely reason for the brick and that the procedure is carried out exactly who is this particular problem, while there are a number of different bricks.

Our devices are divided into some partitions and to update it the system version, both the partition table (GPT.bin - which is a kind of map of partitions) and some partitions themselves are modified, especially the SYSTEM partition, and BOOT RADIO.

When updated, for example to version 6, you can no longer downgrade GPT.bin (map) or the partition BOOTLOADER previous versions, which does not prevent the downgrade of the other partitions, thus making the system downgrade without no problem.

It turns out that when we update the MAXX to version 6 and GPT.bin is updated, it disables any partitions that should not be necessary. So when the user makes the Pro downgrade 4.4, but can use the system normally when trying to update to 5.0.1 via OTA (Over The Air), the script of this update in an attempt to write about some non-existent or existing partitions in a different place to the map of the new GPT causes corrupt some essential partitions for operation.

So if you've been on 6.0.1, just doing pro downgrade 4.4 and without notice or unintentionally updated to 5.0.1 via OTA, this tutorial is for you.

BEFORE YOU BEGIN

We imagine that your mobile phone is with black screen and nothing appears when trying to connect and that was unlocked BOOTLOADER (since it took to the downgrade).

First thing you should do before you start is to download our KIT-unbrick (HERE) , plug the phone to PC, open Device Manager and verify that the phone is being recognized by the PC as QUSB-BULK.

https://drive.google.com/file/d/0Byh6WPFNFL3RbG9YSTg3Wk9yVms/view

* To open the Device Manager, click on START / RUN (WIN + R) and type: devmgmt.msc

* It is essential that the cell is recognized by the computer if it has not occurred, we suggest charging the phone, try with another USB cable into another computer's USB port (preferably USB 1.1 or 2.0) or even another computer.

Extract the downloaded file (kit-unbrick) in any folder on your PC.

Second step is to Disable Driver Signature verification for this open the folder with the extracted files and run AS ADMINISTRATOR file "DesabilitaAssinaturaDrivers.bat" which is inside the folder "1.Qualcomm_USB_Drivers"

Restart your PC and check appears on your wallpaper, the clock above the "TEST MODE"

* If the .bat file does not put your CPME test mode, follow the steps THIS SITE

https://translate.googleusercontent...s-8-1/&usg=ALkJrhgRkuu8EB5PX-5m0Tj82vD7Uk_q2Q

Return to 'Disposivos Manager, click the right button on the' QUSB-BULK 'and select UPDATE DRIVERS.

Select the folder that you extracted manually (WITH DISCO) as following pictures:

This last message is important, it means that you have disabled the signing of drivers properly.

If you are here and appeared "Qualcomm HS-USB QDLoader 9008 (COM xx)" or

"Relink HS-9008 USB", you can follow the tutorial.

Unbrick

As we said earlier, we wanted to automate the most of the process, why create another script inside the 2.Unbrick folder called "01.Unbrick.bat". You can run it and, if lucky, everything will work automatically and your phone is already risen.

However, from experience we have seen that each cell reacts in a different way at the moment, so we'll show you the manual way of doing the unbrick, see:

1. Within the 2.Unbrick folder, run the command PROMPT.

2. Type: blank-flash qboot and press enter

3. Your mobile phone should call in a generic BOOTLOADER WITHOUT GREEN ROBOT image

4. Your 'Device Manager' should no longer display the 'Qualcomm 9008' and should now display the 'Android Device / Motorola ADB Interface'

5. Return to the prompt and perform the following commands:

mfastboot flash partition gpt6s1.bin

mfastboot flash rpm rpm6s1.mbn

mfastboot flash SBL1 sbl16s1.mbn

mfastboot flash sdi sdi6s1.mbn

mfastboot flash tz tz6s1.mbn

mfastboot reboot-bootloader

6. Now your phone should already be with the right BOOTLOADER WITH GREEN ROBOT

* As we said, each cell reacts in different ways if you do not appear to you the green robot, unplug the PC phone, hold the power button for 20 seconds, replugue and return to step 1.

Ready! Now just reinstall any version of android. :fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::p

Credits: https://maxximizar.wordpress.com

Google Translate!!