[X]Assistant

[mainbord]

Motorola Droid Ultra / Maxx / Mini - Firmware (OS 4.X)
Droid Mini, XT1030, obake m, Droid Ultra, XT1080, obake, Droid Maxx, XT1080M
Droid Mini: Description | Discussion пїЅ | FAQ | Purchase пїЅ | Firmware пїЅ
Droid Ultra / Maxx: Description | Discussion пїЅ | FAQ | Purchase пїЅ | Firmware пїЅ

Attention!

The material provided by the authors is unofficial; in the event of unsuccessful firmware or loss of the device, the author of the software and the administration of the resource are not responsible!
Before flashing - check!

All actions are performed at your own risk! If everything suits you in your current firmware, or you don’t know why you need to change it, then you don’t need to change the firmware. Anyone who is scary do not go to the topic! Anyone who wants to leave without hemorrhoids, read above.

Before any actions, even if you are 100% sure that you are doing the right thing, make a backup copy of the firmware (program) and copy this backup copy to the computer. Copy everything you have on your phone: photos, data, files from the sdcard section to your computer. Remember and write down the version of your firmware. Before asking a question, read the topic header, FAQ, and use the search on the topic. Performing these points will greatly help you with any actions with the firmware, even if something goes wrong, tested by numerous user experiencessavagemessiahzine.com.

If your bootloader is closed, you cannot roll back to the previous firmware!

On firmware with Android version<5.x and installed GravityBox, ART does not turn on! The same applies to other applications that do not support ART, when you turn on ART, the OS checks if all applications support it, if not all, dalvik is turned on.

The firmware for Droid Ultra / Maxx / Mini is exactly the same. Upgrades by air and firmware are 100% compatible with one reservation. Fastboot xml firmware for Ultra Mini and Maxx are different. The boot section differs according to the checksum, pay attention to it. So far no consequences of the firmware of the wrong boot partition have been found, but you can always be the first.

Drivers and Utilities

MotorolaDeviceManager_2.4.3.exe
MotorolaDeviceManager_2.5.4.exe(32.65 MB)

RSDLite6.1.5.msi
RSDLite_6.2.4.zip(7.13 MB)

Android SDK Tools

Official firmware

Before flashing via RSD, it is necessary to delete the line from the firmware:
<step operation = "getvar" var = "max-download-size" />
If there is one. And the line is available on all official Verizon device firmware files.

How to flash the official firmware or fastboot-xml file?

https://firmware.center/firmware/Motorola/- official firmware can be downloaded here. The site contains firmware with two indices: CFC and 1FF, the sizes of the sections in them and the checksums are the same, only the firmware file differs:
1) 1FF - file to update, it does not erase files from the phone.
2) CFC - zero firmware file, erases everything from the phone, and even what is in the sdcard section and reinstalls it.

Also firmware can be downloaded here:https://yadi.sk/d/MCli…/DROID.MINI.ULTRA.MAXX
Another mirror with official firmware:http://motorolka.org.ua/stock-firmware-motorola
https: //www.androidfil...&manufacturer=Motorola
Firmware on the official website:https: // motorola-globa ... loader / recovery-images

What has changed in the new firmware can be read here:
https: //motorola-global-portal.custhelp.com.../p/30,6720,8697

You can install official firmware from Moto X, including Android 5.X based firmware, but only on devices with an unlocked bootloader.
Installation instructions for Moto x 1st Gen firmware

SU6-7.7 (Blur 24.21.7)- Android 4.4.4
SU6-7.3 (Blur 24.13.3)- Android 4.4.4, radio 23255.132.81.01R, ota, it is impossible to get a root, but if there is a previous firmware with a root, you can upgrade to save the root, also read about the spoiler "Questions and Answers, Instructions," about Russification same
SU6-7.2 (Blur 24.13.2)- Android 4.4.4, radio 23255.132.81.00R,otaIt is impossible to get a root, but if there is a previous firmware with root, you can upgrade with saving the root, also read about the root spoiler "Questions and Answers, Instructions", read about Russification there
SU6-7 (Blur 24.3.7)- Android 4.4.4, radio 23255.132.81.00R,otaIt is impossible to get a root, but if there is a previous firmware with root, you can upgrade with saving the root, also read about the root spoiler "Questions and Answers, Instructions", read about Russification there
SU5-24 (Blur 23.3.24.)- Android 4.4.4, radio 23255.127.76.00R,ota, fastboot XML, it is impossible to get a root, but if the previous firmware is worth a root, you can upgrade with saving the root
SU4.21 (Blur 11/21/21)- Android 4.4.4, radio 232.55.52.00R,ota, fastboot XML, crack 1, crack 2, it is impossible to get a root, but if the previous firmware is installed, you can upgrade with saving the root
SU2-3.3 (Blur 19.6.3)- Android 4.4.0, radio 2323.031.111.00.R,ota, crack number 1, crack number 2, it is possible to roll back to the previous firmware and get root
SU2-3 (Blur 19.5.3)- Android 4.4.0, radio 2323.026.100.00.R,ota, there is an opportunity to get root
SU1-15-3 (blur 12-15-15)- Android 4.2.2, radio 2323.026.100.00.R,ota, deodex, crackthere is an opportunity to get root
12.9.0Q2.X (blur 12-7-7)- Android 4.2.2, ota,system / app, there is an opportunity to get root

Unofficial firmware

Modifications of the official firmware

Firmware from the authorCrash] [:
Droid L! Te FW 6-7.3 ML
Multilanguage firmware for locked FW L! Te SU6-7-3
Droid L! Te FW 6-7.2 ML RC2
Droid L! Te FW 4-21 ML SU4-21.ML

DroidMAXX +from the authorserg_gangubas
Moto_Lite_5.24_En_Deodex
SU5.24_ (Blur 23.3.24) _En_Deodex
Backup firmware SU2-3.3 (Blur 19.6.3) - Android 4.4.0
Backup copy of rutted russified cleaned firmware for custom recovery (Safestrap, etc.)
Snake's venom

Firmware based on source code LineageOS (Cyanogenmod)

All unofficial firmware based on the source code LineageOS (Cyanogenmod), only for devices with unlocked bootloader.

If the firmware does not have a google account, google play (market) and any google applications in general, install the ZIP installer for your firmware:Google application
Google Apps for Andriod 5.0
http: //forum.xda-devel...p=59691695&postcount=3
If you install firmware based on unofficial source code for Moto X, in order for the hardware buttons and sound to work on Droid mini, you need to install a fix:http: //forum.xda-devel...ly-cm11-ghost-t2911626
To work on the droid mini LED, you need to use the driver
Motorola Droid Ultra / Maxx / Mini - Firmware (OS 4.X) (Post KBN # 47599226)

CyanogenMod 12, 12 Official, 13 Unofficial- Droid support (obake, obake m, obake mini) was launched again in a separate branch in January 2015. For firmware, you must use the new recoveryMotorola Droid Ultra / Maxx / Mini - Firmware (OS 4.X) (Post # 30044336). After the firmware, enter the command "fastboot oem config carrier gsm". If after the firmware does not work GPS, execute the following two commands in the fastboot.
fastboot erase modemst1
fastboot erase modemst2
Download the firmware by the link -http://download.cyanogenmod.org/?device=obake.
See the list of changes here -http://www.cmxlog.com/12.1/obake.
Sources of firmware can be found here -https://github.com/Cya…_device_motorola_obake
P.A.C-MAN
Gummy
Liquidsmooth- discussion onxda
Exodus- discussion onxda

You can also take all the firmware for Moto X, based on the source code of cyan, that is, unified MSM8960dt
http://forum.xda-developers.com/moto-x

Questions and answers, instructions

How to flash img via fastboot?
How to flash the official firmware or fastboot-xml file?- go into the firmware mode from the off state with the volume down button held down - enable.
How to Russify the phone?
CWM and TWRP recovery- Put only these recovery, only from this message and only these versions, others, even if they are flashed and opened, then they definitely work with errors, it is checked!
How to change the boot image?
Boot images
How to flash intertelecom number into the device?same thing only from moto ex themeMotorola X - Firmware (OS 4.x) (Post # 30183833)
script that blocks motohlamaauthorTRANZIOR
Step-by-step installation instructions for xt1080 (xt1030) with a locked boot and without rots Multilingual firmware for locked boot FW L! Te SU6-7-3 by Crash] [- author of instructions08sv80
MINI FAQ MOTOX // DROID MINI / ULTRA / MAXX- from Crash] [
Instructions for firmware L! Te LPA23.12-15.5 1052.EU from Moto X [from the authorNoigel
Step-by-step installation instructions for xt1080 (xt1030) with a blocked boot Multi-language firmware for locked DroidMAXX + with root without write permission to the system partition - from the author serg_gangubas (modification instructions from 08sv80)

Getting Root Rights
SU6-7.2 (Blur 24.13.2) - full root cannot be obtained. In the section of unofficial firmware, you will find the firmware from the crash, in which there is a root of rights without the possibility of making changes to the system section. Firmware can be delivered with a locked bootloader without root. Firmware translated into Russian, contain root rights, but do not have write rights to the system partition, cleaned of trash, xposed works.
SU6-7 (Blur 24.3.7) - full root cannot be obtained. In the section of unofficial firmware, you will find the firmware from the crash, in which there is a root of rights without the possibility of making changes to the system section. Firmware can be delivered with a locked bootloader without root. Firmware translated into Russian, contain root rights, but do not have write access to the system partition, are cleaned of junk, xposed works. saving the root
SU4.21 (Blur 21.11.21) - it is impossible to get a root, but if the previous firmware is installed, you can upgrade with saving the root
SU2-3.3 (Blur 19.6.3) - it is possible to roll back to the previous firmware and get the root
SU2-3 (Blur 19.5.3) - you can get a root
SU1-15-3 (blur 12-15-15) - there is an opportunity to get root
12.9.0Q2.X (blur 12-7-7) - you can get root
If you have an unlocked bootloader or you can unlock it, you can get a root. After unlocking, the root can be obtained on any firmware even after an official update via RSD or over the air.
How to get root rights?
How to upgrade to the latest russified and custom firmwareAndroid 4.4.4 SU5.24_ (Blur 23.3.24) _Ru_Deodexfrom the authorilia3367
The algorithm for updating the firmware with saving root

Bootloader unlocking
In a nutshell:
The version of the bootloader V30.B6 and below - the only condition for unlocking throughSunshine. The firmware version is not important. Loader V30.B7 and higher - not unlockable by anything, in general, and perhaps never.

V30.22 / V30.50 / V30.70 / V30.71 / V30.90 / V30.B0 / V30.B2 - YOU CAN UNLOCK THE DOWNLOADER
V30.B4 / V30.B6 - NOT ON ALL PHONES, BUT YOU CAN ALWAYS UNLOCK THE DOWNLOADER!
V30.B7 / V30.B9 / V30.BA / V30.BC / V30.BE- DO NOT unlock the bootloader

Only owners of Droid Maxx developer edition, ultra and mini in the version for developers are not allowed to officially unlock the bootloader. For everyone else there is an unofficial paid unlock. Paid unlocking works either on devices manufactured in 2013, or on devices with root, costs 1000-2000r.
How to unlock the bootloader?- official boot loader unlock only for the version of droid maxx developer edition, on other devices you can not unlock the bootloader, if you do not believe, try to unlock your device by the link. When you unlock, data is reset and all files are deleted from the internal memory, that's all!
Unlocking the bootloader on the consumer version of Moto X (Verizon, AT & T) and Droid Maxx, Ultra Mini- Unlock paid. When you unlock, data is reset and all files are deleted from the internal memory, that's all! Only for the unit produced in 2013. (Apparently the service does not work anymore)
Motorola Droid Ultra / Maxx / Mini - Firmware (OS 4.X) (Post # 34447516)- Paid unlocking bootloader for all devices with root. The cost is approximately 1000r, data reset with this unlocking is not done. Works on firmware SU4.21 and earlier.

How to roll back to the previous version of the firmware?
1) Unlock bootloader
2) Sew throughfastbootboot, motoboot and system of the desired firmware.
3) Do not update after this by air, only via fastboot or RSD.

To flash the firmware on the unlocked bootloader, at least you need to flash the following sections:

$ fastboot flash motoboot motoboot.img
$ fastboot flash boot boot.img
$ fastboot flash system system.img

Update Information
https: //motorola-global-portal.custhelp.com.../p/30,6720,8697

Modified native desktop
Motorola Droid Ultra / Maxx / Mini - Firmware (OS 4.X) (Post # 35793473)
Motorola Droid Ultra / Maxx / Mini - Firmware (OS 4.X) (Post # 34840869)
Motorola Droid Ultra / Maxx / Mini - Firmware (OS 4.X) (Post # 34714800)

Modified Circle Widget 3D widget
Motorola Droid Ultra / Maxx / Mini - Firmware (OS 4.X) (Post # 34819877)

safestrap
http://rootzwiki.com/topic/104161-recovery...-recovery-v36x/
http://downloads.crackflasher.com/?dir=Dev...0-vzw/safestrap
safestrap for XT1080M, XT1080, XT1060 and XT1030
When the safestrap is installed, the update by air will not rise!

To get rid of the error:
Sticky bit factory_fastboot
You need to connect the device to the computer in fastboot mode and execute the following commands:

fastboot oem fb_mode_clear
fastboot reboot-bootloader
fastboot reboot

files from
Dhacker29http://downloads.crackflasher.com/?dir=Devs/Dhacker29
Hashcode0fhttp://downloads.crackflasher.com/?dir=Devs/Hashcode0f

github (source) cyan
https://github.com/razrqcom-dev-team

The logo has three logos: one for normal, one for charging, one for unlocked.

The partition structure is taken from the gpt.bin file,

mmcblk0pN: offset: name: size
mmcblk0p0: 0x000000000000: partitions: 6144
mmcblk0p1: 0x000000020000: modem: 104857600
mmcblk0p2: 0x000006420000: sbl1: 1536000
mmcblk0p3: 0x000006597000: sbl2: 1536000
mmcblk0p4: 0x00000670e000: sbl3: 526336
mmcblk0p5: 0x00000690e000: aboot: 524288
mmcblk0p6: 0x000006a85000: rpm: 145408
mmcblk0p7: 0x000006b02000: tz: 215040
mmcblk0p8: 0x000006b7f000: utags: 524288
mmcblk0p9: 0x000006bff000: logs: 1048576
mmcblk0p10: 0x000006cff000: padA: 3149824
mmcblk0p11: 0x000007000000: sbl2Backup: 1536000
mmcblk0p12: 0x000007177000: sbl3Backup: 2097152
mmcblk0p13: 0x000007377000: abootBackup: 1536000
mmcblk0p14: 0x0000074ee000: rpmBackup: 512000
mmcblk0p15: 0x00000756b000: tzBackup: 512000
mmcblk0p16: 0x0000075e8000: utagsBackup: 524288
mmcblk0p17: 0x000007668000: padB: 1671168
mmcblk0p18: 0x000007800000: modemst1: 3145728
mmcblk0p19 0x000007b00000: modemst2: 3145728
mmcblk0p20: 0x000007e00000: mbl: 2097152
mmcblk0p21: 0x000008000000: hob: 655360
mmcblk0p22: 0x0000080a0000: dhob: 8192
mmcblk0p23: 0x0000080c0000: persist: 8388608
mmcblk0p24: 0x0000088c0000: ssd: 8192
mmcblk0p25: 0x0000088c2000: fsg: 3145728
mmcblk0p26: 0x000008bc2000: sp: 1048576
mmcblk0p27: 0x000008cc2000: misc: 524288
mmcblk0p28: 0x000008d42000: pds: 3145728
mmcblk0p29: 0x000009042000: cid: 131072
mmcblk0p30: 0x000009062000: logo: 4194304
mmcblk0p31: 0x000009462000: clogo: 4194304
mmcblk0p32: 0x000009862000: devtree: 1048576
mmcblk0p33: 0x000009980000: boot: 10485760
mmcblk0p34: 0x00000a380000: recovery: 10485760
mmcblk0p35: 0x00000ad80000: kpan: 8388608
mmcblk0p36: 0x00000b580000: cache: 1469579264
mmcblk0p37: 0x000062f00000: padC: 1048576
mmcblk0p38: 0x000063000000: system: 2214592512
mmcblk0p39: 0x0000e7000000: customize: 16777216
mmcblk0p40: 0x0000e8000000: userdata: 0

Radio module firmware

Radio in the official firmware is in the files NON-HLOS.bin and fsg fsg.mbn
Stitch as follows:

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot

We are stitching this way, because it is stitched in the instructions for the official firmware. Files from Verizon moto x XT1060 are suitable.

23255.132.81.01R.zip(23.69 MB)
23255.132.81.00R.rar(21.24 MB)
232.55.52.00r.zip(24.25 MB)
2323.038.123.00r.zip(24.09 MB)
2323.031.111.00r.zip(24.07 MB)
2323.026.100.00.R.

Mirror
Motorola Droid Ultra / Maxx / Mini - Firmware (OS 4.X) (Post Crash] [# 40995900)

Polls

Closed 12/26/16

Post has been editedmainbord - 20.04.17, 09:30

[4Adun]

[email protected], 18:24

2) We start CMD and we learn IP devices in system

adb shell getprop dhcp.wlan0.ipaddress

Must get something Tipo
adb server is out of date. killing ...
* daemon started successfully *
10.0.0.8

This will work only if the device is connected to an existing network (along with a PC).
If there is no opportunity to stir up a normal network (like mine’s an old laptop that cannot act as a router), do this:
1) Turn on the access point on the ruled device.
2) Connect from the laptop to the device, as to the router.
3) In the connection settings, we look at the IP address of the “main gateway” - this is the IP address of the device (my default was 192.168.43.1).
4) Next - all according to the instructions. After the reboot of the device, do not forget to restore the connection (include the access point).

[sansara]

With the update, flashing through the RSD, root and safstrap any questions everything is fine.
But now it’s problematic to switch the body to NV_ONLY mode, who was able to flash cdma?

[yurok82]

sansara
I haven’t found such an opportunity yet, I tried all the radio, which is for the line up to the Moto Ha even! Flies! Even from Drod Razr HD 4.0.4 tried, does not fly, but there is no connection: D
It is necessary to try to open the modem somehow, but I haven’t found such a possibility yet.

[sansara]

[email protected], 19:11

I haven’t found such an opportunity yet, I tried all the radio, which is for the line up to the Moto Ha even! Flies! Even from Drod Razr HD 4.0.4 tried, does not fly, but there is no connection
It is necessary to try to open the modem somehow, but I haven’t found such a possibility yet.

I also tried to sew on HD
radio stitched, writes an unknown version of the radio
therefore I can not log in through dfs firmware mode
I will now return back the radio from the drain
I will try to stick a people stick or Inter, although it is unlikely of course but still. I know that droid bionic oddly enough worked from both NV and RUIM, although this is the only case known to me

Posted on 12/01/2013 21:02 PM:

yurok82
But how about an hour with an attempt to flash what thread in the second rum?
I put the cyan in the second activated slot in the safestrap but the body did not start

Post has been editedsansara - 01.12.13, 21:01

[yurok82]

sansara
Unsubscribed, that Ruim swallows normally. I do not suffer with custom bridges, this Tsian and all other under-firmwares have already outgrown, I use the stock deodex + doped crack.

[sansara]

[email protected], 20:12

Unsubscribed, that Ruim swallows normally. I do not suffer with custom bridges, this Tsian and all other under-firmwares have already outgrown, I use the stock deodex + doped crack.

aha i also checked ruim
voice works
evdo now looking for adding APN or replacing XML file
you like evdo

And the question is, what does the doped Russian mean? it is freely available

[yurok82]

sansara
I did not start it myself, because I am using a bundle of FSM + SDMA (the second one is only for the Internet), so for now I'm sitting like that.

[email protected], 20:38

And the question is, what does the doped Russian mean? it is freely available

The topic of the 926th is all described, not yet freely available.

[sansara]

[email protected], 20:41

I did not start it myself, because I am using a bundle of FSM + SDMA (the second one is only for the Internet), so for now I'm sitting like that.

are you sitting on 926 models now?
there in the subject I'm aware of the gradation of admission to 926 localizers.
I thought it was about the crack to 1030

[mainbord]

[email protected], 22:02

But how about an hour with an attempt to flash what thread in the second rum?
I put the cyan in the second activated slot in the safestrap but the body did not start

I answered in the topic of discussion, I will also duplicate here, since the theme of the firmware is still here. You can try as many times as you like, just run the firmware on the same core, that is, you can run a maximum modification of the firmware, or build a cyan on the core.

[email protected], 22:47

I thought it was about the crack to 1030

Read the information in the author's profile, rusik for mini max and ultras are the same.

[sansara]

[email protected], 21:18

I answered in the topic of discussion, I will duplicate here,

I will also duplicate the question

Is it here?http://skrilax.droid-developers.org/cm10.2...oose_device.php
firmware is not on the corresponding core?

[yurok82]

[email protected], 20:47

You are now sitting on the model 926? There in the subject I am aware of the gradation of admission to 926 drivers. I thought it was about the crack to 1030

Yes, I'm stuck on the 926th and am not going to leave, while everyone is happy.
In about Russifier

[email protected], 21:18

Read the information in the author's profile, rusik for mini max and ultras are the same.

Maxim is absolutely right, it was written repeatedly and it was confirmed that the firmware is the same and that you can only flash on one core with a drain!

[email protected], 21:24

Is it here?

Link to nowhere

File not found.

Post has been editedyurok82 - 01.12.13, 22:26

[sansara]

this one opens

http://skrilax.droid-developers.org/cm10.2...oose_device.php

Post has been editedsansara - 01.12.13, 22:36

[sansara]

pahazzz
You have faith that you have a path 192.168.0.101

I have 14-7 as the root did not go
but after the update at 15.15 everything came together

so try to upgrade

Posted on 12/01/2013 22:43:

[email protected], 19:31

Must get something Tipo
adb server is out of date. killing ...
* daemon started successfully *
10.0.0.8

maybe someone will not understand, I want to clarify that the aipishnik can be different from me for example С”to 192,168,1,9

[yurok82]

sansara
There can be any important thing to be on the same network.

[sansara]

[email protected], 21:50

There can be any important thing to be on the same network.

Yes, I wrote the type, literally, that can be different

[yurok82]

sansara
Well, yes, and I approving the answer - confirmed it)

[1806]

Yurok82 @ 12/02/2013, 01:12

I use the stock deodex + doped crack

I was pleased with the presence of Russian letters on the keyboard of my native dialer, and you can do only Russian letters and Russian search in a diler and a notebook, without russification of other applications?

[ku5ma]

yurok82dear comrade, can you give more detailed information about the plans for the Russification of the current droid family? Do you expect to be freely available? when to expect? how to thank)

[yurok82]

ku5ma,
Crack is ready for the entire line of Droids, Moto Ha and Ge in the plans, if someone does not do it before. Of course you can wait, I’m not going to tell you in time, everything else is presented in a personal.

1806,
At 4.2, the notebook is already in Russian, which greatly simplified life if you are talking about the scroll bar. According to the buttons for the caller with the search t9, then only on deodex it is possible to implement this feature.

[Audist]

yurok82
How can I put Rus. on Motorola Droid Ultra (XT1080) developer edition (the one with the red stripe)?