[GUIDE] [Maxx XT1225] Install Lollipop OTA if you have Rooted - no Wipe necessary

Search This thread
By:
Advanced…
D

Darkcolt

Member
Jun 10, 2014
13
3
i cant locate this file in cache Blur_Version.XX.XX.X.quark_retbr.retbr.en.BR.zip..
i have root in my device but i cant locate
 
D

Darkcolt

Member
Jun 10, 2014
13
3
I just do not know I did root the device, and I'm wanting to put the retail but not locate this file.
 
B

BeSalecker

Member
Mar 8, 2013
40
18
New York
Christ whoever is posting these articles on the XDA homepage saying this will work for the Turbo has to stop. The Maxx and the Turbo are two separate devices. Someone please fix this it's annoying.
 
alexcreto

alexcreto

Senior Member
Jan 13, 2014
110
94
São Paulo
respider said:
as always I'm not responsible for any damage in your device (or lost files)
Always backup everything first - nandroid and titanium.

TL;DR for more experienced users: flash stock boot, stock recovery and stock system images (system via mfastboot since its chunks) and then install OTA zip file in the stock recovery (via sd or sideload)

If you have rooted your Moto Maxx and are trying to install the OTA for Lollipop, you are probably getting errors due to modifications on you system.

Simply removing SuperSU doesnt work, you have to restore your system to stock.

If you received the OTA notification, download it and don't install.

0- After downloading, grab the zip file from /cache/ and save it on your computer.
Filename will be something like Blur_Version.XX.XX.XX.quark_retbr.retbr.en.BR.zip

1- Download brazilian retbr full 4.4.4 firmware from here
http://xdaforums.com/droid-turbo/orig-development/retbrxt12254-4-4kxg21-50-9cid12subsidy-t2992444

Decompress it and you should see these files:

system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
system.img_sparsechunk.4
recovery.img
boot.img

2- Download mfastboot (google it) (I used both regular fastboot and mfastboot)


3- Decompress mfastboot and put all files in the decompressed folder above

All files should be in the same folder: mfastboot.exe, boot.img, recovery.img and all system sparsechunks.
Of course they can be in different folders if you know how to use paths in command :p

4- Unroot

Go to SuperSU app -> configurations -> uninstall root

I recommend uninstalling xposed, busybox etc (I didnt have those, not sure if they will mess with something)

5- Put your phone in bootloader mode

adb reboot bootloader

5- Flash stock kernel, recovery using regular fastboot:

fastboot flash recovery recovery.img
fastboot flash boot boot.img

6- flash stock system to fix install-recovery.sh bug/validation, using mfastboot:

Flashing stock boot and recovery was not enough for me. I was getting an error saying /system/etc/install-recovery.sh has unexpected contents.

To solve this, I flashed the stock system image by using mfastboot:

mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4

Code: 
C:\mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (259107 KB)...
OKAY [  8.130s]
writing 'system'...
OKAY [  4.122s]
finished. total time: 12.259s

C:\mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (254153 KB)...
OKAY [  7.958s]
writing 'system'...
OKAY [  3.282s]
finished. total time: 11.250s

C:\mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [  8.208s]
writing 'system'...
OKAY [  3.719s]
finished. total time: 11.937s

C:\mfastboot.exe flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (262142 KB)...
OKAY [  8.207s]
writing 'system'...
OKAY [  3.880s]
finished. total time: 12.098s

C:\mfastboot.exe flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (144756 KB)...
OKAY [  4.533s]
writing 'system'...
OKAY [  2.330s]
finished. total time: 6.871s

After this your system is back to stock.

All you have to do now is enter in stock recovery, go to "install zip from adb" and sideload the zip you saved in step 0.

1.2- Reboot your phone to stock recovery

You should see a broken android laying on the floor

in this screen, press Power+VOL UP together and hold for like 2 seconds and release.
A menu should appear. If it doesnt, try again many times - it can be tricky

2.2- Select install zip from ADB or something like that

Now you should be able to see your device in your computer via adb devices command

You should see your device ID and a sideload string when you type this. If you dont, you have incorrect drivers

3.2- Sideload the OTA zip file

In your command prompt find the OTA file you saved in step 0 and then
adb sideload filename.zip, exemple:

adb sideload Blur_Version.XX.XX.X.quark_retbr.retbr.en.BR.zip

If everything goes ok, just wait and relax, if could take a while for the first boot.
Phone will hang on a blank screen with motorola Logo for a while. Dont panic.

Obviously you will lose root by doing this.
Click to expand...
Click to collapse
Great work, man!
I'd try it out but I'll hold till @rovo89 gives us his Lollipop ready child.
 
D

danger2u

Senior Member
Jan 24, 2010
1,085
239
some good news here
Lollipop instaled on Moto Maxx
root working

Screenshot_2015_02_13_02_21_16.png


Screenshot_2015_02_13_01_59_25.png
 
  • Like
Reactions: ruledrbrt1, Gundabolu SC, hidea and 1 other person
T

TachyonGun

Creative Director
Dec 31, 2014
24
28
Minneapolis
BeSalecker said:
Christ whoever is posting these articles on the XDA homepage saying this will work for the Turbo has to stop. The Maxx and the Turbo are two separate devices. Someone please fix this it's annoying.
Click to expand...
Click to collapse

I edited it as requested. We are sorry for the inconvenience. I posted the link and I had mistaken both devices as one with different localization names, and given this was featured under the Droid Turbo forum I intuitively (and mistakenly) reassured that notion so I accidentally mistook them for synonyms. It won't happen again and please do not think less of us, we have to be aware or review almost every new mod entry for every device that has a forum (well, I try to do that to possible extents), so someone is bound to make a mistake every now and then... and sadly this time it was me. It's on me guys, sorry about the misunderstanding, and I hope no phones were hurt because of this :( Well, given it can only be triggered if you get the Maxx-specific OTA I am sure nobody got problems, but still, very sorry!
 
Last edited:
  • Like
Reactions: zenaufa, clydei, BeSalecker and 3 others
D

danger2u

Senior Member
Jan 24, 2010
1,085
239
yes i am in MFN but i didn t receive the OTA from there
pm me and i will give u the link
 
You must log in or register to reply here.

Similar threads

alexcreto
[ROOT] Guide for the Moto Maxx XT 1225
Replies
267
Views
106K
alexcreto
alexcreto
Jaocagomez
[All Quark][Official] Stock Firmware Moto Maxx Droid Turbo Moto Turbo
Replies
521
Views
178K
L
lovelydilip
ChazzMatt
UPDATED GUIDE: How to unlock your MOTO MAXX/MOTO TURBO bootloader/install TWRP/root
Replies
112
Views
27K
ChazzMatt
ChazzMatt
ChazzMatt
Moto Maxx - Moto Turbo XT1225 factory images (Mexico | Puerto Rico | India | Brazil)
Replies
107
Views
35K
S
sourav92
D
Guide:install Lollipop OTA and root ur Moto Maxx
Replies
127
Views
26K
G
gauravahluwalia

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 12
    respider
    respider
    as always I'm not responsible for any damage in your device (or lost files)
    Always backup everything first - nandroid and titanium.

    TL;DR for more experienced users: flash stock boot, stock recovery and stock system images (system via mfastboot since its chunks) and then install OTA zip file in the stock recovery (via sd or sideload)

    If you have rooted your Moto Maxx and are trying to install the OTA for Lollipop, you are probably getting errors due to modifications on you system.

    Simply removing SuperSU doesnt work, you have to restore your system to stock.

    If you received the OTA notification, download it and don't install.

    0- After downloading, grab the zip file from /cache/ and save it on your computer.
    Filename will be something like Blur_Version.XX.XX.XX.quark_retbr.retbr.en.BR.zip

    1- Download brazilian retbr full 4.4.4 firmware from here
    http://xdaforums.com/droid-turbo/orig-development/retbrxt12254-4-4kxg21-50-9cid12subsidy-t2992444

    Decompress it and you should see these files:

    system.img_sparsechunk.0
    system.img_sparsechunk.1
    system.img_sparsechunk.2
    system.img_sparsechunk.3
    system.img_sparsechunk.4
    recovery.img
    boot.img

    2- Download mfastboot (google it) (I used both regular fastboot and mfastboot)


    3- Decompress mfastboot and put all files in the decompressed folder above

    All files should be in the same folder: mfastboot.exe, boot.img, recovery.img and all system sparsechunks.
    Of course they can be in different folders if you know how to use paths in command :p

    4- Unroot

    Go to SuperSU app -> configurations -> uninstall root

    I recommend uninstalling xposed, busybox etc (I didnt have those, not sure if they will mess with something)

    5- Put your phone in bootloader mode

    adb reboot bootloader

    5- Flash stock kernel, recovery using regular fastboot:

    fastboot flash recovery recovery.img
    fastboot flash boot boot.img

    6- flash stock system to fix install-recovery.sh bug/validation, using mfastboot:

    Flashing stock boot and recovery was not enough for me. I was getting an error saying /system/etc/install-recovery.sh has unexpected contents.

    To solve this, I flashed the stock system image by using mfastboot:

    mfastboot.exe flash system system.img_sparsechunk.0
    mfastboot.exe flash system system.img_sparsechunk.1
    mfastboot.exe flash system system.img_sparsechunk.2
    mfastboot.exe flash system system.img_sparsechunk.3
    mfastboot.exe flash system system.img_sparsechunk.4

    Code: 
    C:\mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (259107 KB)...
OKAY [  8.130s]
writing 'system'...
OKAY [  4.122s]
finished. total time: 12.259s

C:\mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (254153 KB)...
OKAY [  7.958s]
writing 'system'...
OKAY [  3.282s]
finished. total time: 11.250s

C:\mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [  8.208s]
writing 'system'...
OKAY [  3.719s]
finished. total time: 11.937s

C:\mfastboot.exe flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (262142 KB)...
OKAY [  8.207s]
writing 'system'...
OKAY [  3.880s]
finished. total time: 12.098s

C:\mfastboot.exe flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (144756 KB)...
OKAY [  4.533s]
writing 'system'...
OKAY [  2.330s]
finished. total time: 6.871s

    After this your system is back to stock.

    All you have to do now is enter in stock recovery, go to "install zip from adb" and sideload the zip you saved in step 0.

    1.2- Reboot your phone to stock recovery

    You should see a broken android laying on the floor

    in this screen, press Power+VOL UP together and hold for like 2 seconds and release.
    A menu should appear. If it doesnt, try again many times - it can be tricky

    2.2- Select install zip from ADB or something like that

    Now you should be able to see your device in your computer via adb devices command

    You should see your device ID and a sideload string when you type this. If you dont, you have incorrect drivers

    3.2- Sideload the OTA zip file

    In your command prompt find the OTA file you saved in step 0 and then
    adb sideload filename.zip, exemple:

    adb sideload Blur_Version.XX.XX.X.quark_retbr.retbr.en.BR.zip

    If everything goes ok, just wait and relax, if could take a while for the first boot.
    Phone will hang on a blank screen with motorola Logo for a while. Dont panic.

    Obviously you will lose root by doing this.
    View
    6
    T
    TachyonGun
    BeSalecker said:
    Christ whoever is posting these articles on the XDA homepage saying this will work for the Turbo has to stop. The Maxx and the Turbo are two separate devices. Someone please fix this it's annoying.
    Click to expand...
    Click to collapse

    I edited it as requested. We are sorry for the inconvenience. I posted the link and I had mistaken both devices as one with different localization names, and given this was featured under the Droid Turbo forum I intuitively (and mistakenly) reassured that notion so I accidentally mistook them for synonyms. It won't happen again and please do not think less of us, we have to be aware or review almost every new mod entry for every device that has a forum (well, I try to do that to possible extents), so someone is bound to make a mistake every now and then... and sadly this time it was me. It's on me guys, sorry about the misunderstanding, and I hope no phones were hurt because of this :( Well, given it can only be triggered if you get the Maxx-specific OTA I am sure nobody got problems, but still, very sorry!
    View
    4
    D
    danger2u
    some good news here
    Lollipop instaled on Moto Maxx
    root working

    Screenshot_2015_02_13_02_21_16.png


    Screenshot_2015_02_13_01_59_25.png
    View
    2
    D
    Darkcolt
    [MOD EDIT:]SHAME SHAME SHAME. Signing an NDA means you're agreeing to not share details of the special program you are in.

    This has been removed at the request of Motorola due to your negligence in violating the terms of your agreement.
    View
    2
    D
    danger2u
    i m having the Puerto Rico version of Moto maxx. i flashed the Retail Brasil 4.4.4 then install the ota zip.
    View

New posts