Related
This tool is for the conversion of meizu's bin formatted rom files to zip. I didn't make the tool, but I can't recall where I got it either.
link
I made the tool. There's a topic on meizume dedicated to it but feel free to discuss it here.
http://d-h.st/users/iSilver
It is quite bloated because of the Qt dlls (couldn't be arsed to recompile the whole beast statically) and that doesn't count the VC 2008 runtime. Oh well.
I have found it is essentially good for converting stock bins to zips, as the other way round won't be helpful for CN devices - a check in the Mz recovery has a special code path for HK devices (based on /proc/uboot_version), which accepts all stuff regardless of whether it's signed updates or not. That's why you could flash anything, prerooted ROM, or even a su package (no need to mess with TPsparky indeed).
OTH, the CN version:
- checks sig of what it flashes (thus only stock updates may be flashed)
- had a (RSA ?) checksum for each partition and thus cannot be written to freely (e.g. mod the recovery image)
- is the reason my next phone won't be a Mz
TwoPointZero said:
I made the tool. There's a topic on meizume dedicated to it but feel free to discuss it here.
http://d-h.st/users/iSilver
It is quite bloated because of the Qt dlls (couldn't be arsed to recompile the whole beast statically) and that doesn't count the VC 2008 runtime. Oh well.
I have found it is essentially good for converting stock bins to zips, as the other way round won't be helpful for CN devices - a check in the Mz recovery has a special code path for HK devices (based on /proc/uboot_version), which accepts all stuff regardless of whether it's signed updates or not. That's why you could flash anything, prerooted ROM, or even a su package (no need to mess with TPsparky indeed).
OTH, the CN version:
- checks sig of what it flashes (thus only stock updates may be flashed)
- had a (RSA ?) checksum for each partition and thus cannot be written to freely (e.g. mod the recovery image)
- is the reason my next phone won't be a Mz
Click to expand...
Click to collapse
I suppose I'm lucky to own a HK MX then. Honestly, they make the best phone that I've handled aside from an iPhone (don't get me wrong, I'm just referring to the build quality.) Thanks for the tool!
We need a kernel dev if your up for it as well. Custom recovery would be a lifesaver for this phone. I'll credit you in the thread as well!
How about this:
1/ Extract the contents of an stock recovery_uboot.img
you obtain a recovery-uboot.img-kernel.zImage and recovery-uboot.img-ramdisk.cpio.gz
2/ Flash recovery-uboot.img-kernel.zImage where kernel ("zImage" in update) for normal boot goes
/dev/block/mmcblk0p63/ Flash [(64-byte header)+recovery-uboot.img-ramdisk.cpio.gz] where ramdisk ("ramdisk-uboot.img" in update) for normal boot goes
/dev/block/mmcblk0p7
and try to boot normally. Do you think the recovery that's normally invoked via VolUp+Power would show up?
EDIT: I posted instructions for dismembering such an image @ http://www.meizume.com/showthread.php?p=158029
TwoPointZero said:
I made the tool. There's a topic on meizume dedicated to it but feel free to discuss it here.
It is quite bloated because of the Qt dlls (couldn't be arsed to recompile the whole beast statically) and that doesn't count the VC 2008 runtime. Oh well.
I have found it is essentially good for converting stock bins to zips, as the other way round won't be helpful for CN devices - a check in the Mz recovery has a special code path for HK devices (based on /proc/uboot_version), which accepts all stuff regardless of whether it's signed updates or not. That's why you could flash anything, prerooted ROM, or even a su package (no need to mess with TPsparky indeed).
OTH, the CN version:
- checks sig of what it flashes (thus only stock updates may be flashed)
- had a (RSA ?) checksum for each partition and thus cannot be written to freely (e.g. mod the recovery image)
- is the reason my next phone won't be a Mz
Click to expand...
Click to collapse
I use this tool, but a mistake in the walk around the process, the specific circumstances, see screenshot!Please improve this tool, it really is very practical, thanks! ! !
Screenshot
View attachment 1613097
I'm trying to use this tool to convert the Flyme 2.0.3 update.bin to a zip file so I can extract a boot.img file, and I'm getting an error. Has the format of the update.bin file changed?
MzCrypt-Gui v1.0.2 with support for MX2 update.bin.
MzCrypt-Gui v1.0.2 with support for MX2 update.bin.
Full package : http://d-h.st/ukl
exe only (no dlls) : http://d-h.st/WLC
TwoPointZero said:
MzCrypt-Gui v1.0.2 with support for MX2 update.bin.
Click to expand...
Click to collapse
This is a fantastic tool, I like it! Thank you very much for your work!
TwoPointZero said:
MzCrypt-Gui v1.0.2 with support for MX2 update.bin.
Full package : http://d-h.st/ukl
exe only (no dlls) : http://d-h.st/WLC
Click to expand...
Click to collapse
Mighty TwoPointZero mate, as MX3 CN version finally hits the market today, is there any chances renewing your tool so that I can get my hands on the new V3.0 update.bin for MX3? Thanks in advance and keep up the great work.
Hi PaulReminder,
MzCrypt-Gui v1.0.3 with support for MX3 update.bin.
Full package : http://d-h.st/nZs
exe only (no dlls) : http://d-h.st/O69
Thanks iSilver! I uploaded it to my new Meizu fan community if you don't mind: http://meizufans.eu/forum/showthread.php?tid=55
TwoPointZero said:
Hi PaulReminder,
MzCrypt-Gui v1.0.3 with support for MX3 update.bin.
Full package : http://d-h.st/nZs
exe only (no dlls) : http://d-h.st/O69
Click to expand...
Click to collapse
Thank you sooo much mate for the heads up! Now I can extract new flat icons extracted from MX3 OS to work with my own theme.
With edited icons my phone looks so FlymeOS 3ish now. @TwoPointZero mate, I salute you.
No problem HondaRacer
What's happened to meizume btw?
TwoPointZero said:
No problem HondaRacer
What's happened to meizume btw?
Click to expand...
Click to collapse
Tool works for Meizu MX4 pro?
Thank
Is this tool no longer available? When I click the "Download Now" link, it just brings up a new tab with a grey blank page.
If it's still available, can someone provide me a mirror link please?
This tool is available on the chinese forum http://bbs.flyme.cn/thread-20121-1-1.html
or russian 4pda forum http://4pda.ru/forum/index.php?showtopic=521028&st=21460
or spanish forum http://www.htcmania.com/showthread.php?t=881622
direct download link : Converter Bin-to-zip
after too many test i finally made a patch for porting ics stock roms from arc/s (and maybe other xperia 2011 devices) to pur lovely xperia play
it will install all the things that you need for fully working rom on xperia play and deletes the cybershot camera(because it not working on our device)
installation guide:
there are 2 ways for installing
1-if the rom has armo installer
2-if it doesnt have armo installer
if it has armo installer its very easy to use this
here is the instruction
1-open rom zip and ics rom porter.zip files with winrar
2-find the device section in rom zip file
3-drag all the files inside system folder in the ics rom porter.zip to lt28i(xperia arc) folder of rom zip
4-now simply flash the rom zip ans choose xperia arc as your device and everything will be fine
if the rom doesnt have armo installer
do the same thing as i said for the the roms with armo installer but instead of draging the files to lt28i folder drag them to system folder
bugs:
1-no touchpad. i need help for this part.
2-flashable.zip is broken. i need help for this one too
3-build.prob will be replaced with xperia z v5 by markphyton so you wont see the original tweaks after the port
4-some of the roms will give bootloop because they have more space than our system partition. if some one can repartiton a kernel with more system storage it will be great
to do list:
1-making an armo zip with all build.prob form popular roms and the requested roms
2-adding touchpad fix
tested on(working):
1-anzumi : by myself
2-4.1.b.1.13(arc version by jader) : by myself
tested on(not working):
xperia ray 4.1.b.1.13 (touchscreen had some problems)
download link:
http://d-h.st/eJv
thanks to:
1-markphyton : i have taken my files from his rom
2-all the developers of xperia arc :for making roms(that gived me the idea of this patch)
3- xda: all of us know why
4-dev host : i use it for uploading my files
5-xperia play users : for not giving up
reserved
please help me for fixing the bugs
i will start working on gb and jb patch as soon as i get time
waiting for reports now
that all i can do now
if you want to help for completing this patch i need help for these things
1- someone with good knowledge in making armo installer and update.zip files
2-someone for helping me in making build.prob files of requested roms
3-(the moost ipmortant) helping me for fixing touchpads
Smokerman is good in porting roms, you should ask him for touchpad fix
I have basic knowledge of aroma installer and build.prop editing, if i can, i'll help
touchpads
@smokerman
can you help me for fixing the touchpads?
i will release an update soon
things that i changed:
1-fixed the flashable zip
2-im using 4.0.4 ics build.prob instead of xperia z rom by markphyton
jb patch is being tested now
for now i only get bootloops
but im trying to solve the problem
i aslo wanted to make an gb patch but i saw that we will get a little problem in gamepad after porting gb roms from arc
(always open game pad. you cant use touchscreen for gaming anymore in ported gb roms.)
pedyvirus said:
@smokerman
can you help me for fixing the touchpads?
Click to expand...
Click to collapse
i can help for sure..what is the rom? send me the link..i will look into it on the weekend.
well im making a patch for all of the roms
i need to know the way so i can support all the roms that xperia play users want
do you use farenheith's patch for fixing the touchpad in stock based roms?
update coming in less than 30 minutes
im doing the final test
changelog:
1-you don't need to do anything yourself now. just flash the rom + the porter package and everything is finished
2-build.prob replaced with 4.1.b.1.13 for xperia play (made by myself)
3-updated most of the files
to do list:
1-building a 410mg system partition kernel.(i really need help or this one. i don't have enough experience)
2-fixing touchpads (i really dont know how to this because i never fixed touchpads for stock based ics roms. please help me )
also i saw project lard remover script
it can remover build.prob lines
if i can remove xperia arc lines and replace them with xperia play lines most of the bugs will be fixed
but my problem is with different build.prob lines like 4.1.b.1.13 or 4.1.b.0.631 and these things
for now i will add a guide about how to make the build.prob yourself for activating the build.prob tweaks of the rom after applying my patch(for better speed)
update: i got bootloop using the new zip although its working with the old way of porting (extracting the files to the system folder)
i will release it when i fix this problem
pedyvirus said:
update coming in less than 30 minutes
im doing the final test
changelog:
1-you don't need to do anything yourself now. just flash the rom + the porter package and everything is finished
2-build.prob replaced with 4.1.b.1.13 for xperia play (made by myself)
3-updated most of the files
to do list:
1-building a 410mg system partition kernel.(i really need help or this one. i don't have enough experience)
2-fixing touchpads (i really dont know how to this because i never fixed touchpads for stock based ics roms. please help me )
also i saw project lard remover script
it can remover build.prob lines
if i can remove xperia arc lines and replace them with xperia play lines most of the bugs will be fixed
but my problem is with different build.prob lines like 4.1.b.1.13 or 4.1.b.0.631 and these things
for now i will add a guide about how to make the build.prob yourself for activating the build.prob tweaks of the rom after applying my patch(for better speed)
update: i got bootloop using the new zip although its working with the old way of porting (extracting the files to the system folder)
i will release it when i fix this problem
Click to expand...
Click to collapse
is it possible to port ics stock rom of arc to our device(xperia miro) (2012) ?????
a help would be appreciated!!! and i know @pedyvirus you can help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DEPRECATED, NO MORE UP-TO-DATE, ONLY KEPT FOR ARCHIVE
Technical Specifications -
Model Number(s) -
XT1031: Boost Mobile8GB
XT1032: This Model Number is shared by International GSM Version and the Google Play Edition 8 GB/16 GB (Single SIM) EU & International GSM - 8GB/16GB. (Does not Support 1700 MHz AWS)
XT1033 : Brazil, India, Malaysia (BrightStar) - 8GB & 16GB(Brazil Colors Edition) (Both are Dual Sim) and also for Moto G (Music edition) (Dual Sim) (16GB Only), Malaysia 8GB & 16 GB are Dual Sim
XT1034: AT&T and T-Mobile - 8GB/16GB.
Frequencies / Bands:
AT&T and T-Mobile - HSDPA 850, 900, 1900, 2100 MHz; GSM 850, 900, 1800, 1900 MHz
Verizon and Sprint - CDMA:800, 1900 MHz, CDMA2000 1xEV-DO
Display Resolution: 720 x 1280 pixels Corning Gorilla Glass 3 (IPS LCD capacitive)
Screen Size: 4.5" 16 M Colors (329 PPi)
Bluetooth Enabled: Yes
Wi-Fi Enabled: Yes
Internal Memory: 8 GB (Actual Space for user data ~6 GB)
16 GB (Actual Space for user data ~12 GB)
External Memory: None
Size / Dimensions: 5.11 x 2.59 x 0.46 inches (129.9 x 65.9 x 11.6 mm)
Weight: 5.04 oz (143 g)
Battery Capacity: 2070 mAh (Not User Replaceable)
Camera: 5 MP (2592х1944 pixels) Camcorder: 720p (30fps), stereo sound rec., HDR Front-facing camera: 1.3 megapixels
Operating System: Android 4.4, 4.3
Keyboard: Touch Screen
GPS: Yes
Click to expand...
Click to collapse
Unique Features -
Motorola Assist
50 GB Google Drive Space Free
Dual Sim
FM Receiver
Click to expand...
Click to collapse
Moto G Review -
Moto G Review - Here's great thread with collated Reviews of this device. Thanks to @matmutant
Click to expand...
Click to collapse
List of Commonly used Terms -
All that is fine, but I don't know what this rooting, flashing, nandroid, Modding etc. mean? Yelp ?
Fear Not! Here's a little Cheat Sheet for you. Please thank @benjamingwynn for this. I took his original list for HTC and extended it for here. Given bellow is a Glossary of sorts for commonly used terms. Please let me know if I missed any and I will add it. Also please visit this Q & A thread. Its more than likely to answer most of your questions.
ADB - "Android Debug Bridge" a system that can be accessed using a computer where you can manage the device from. You need the Android SDK to use it.
AFAIK - "As far as I know"
AOSP - "Android open source project" a project by Google Inc. to give android to developers and manufactures for free (see open-source)
APK - "Android Package" an Android application
Binary - (sometimes called bin's) a group of executable files.
Brick - When the device refuses to boot at all, despite having a full battery is termed as Bricking. Most of the times, the devices gives some indication of problems such as blinking Red Led, but no other signs of life. It is also called Hard Brick. Also see Soft Brick.
Bootloader - Its a small piece of code that's embedded in the device. Its the first to be executed when the device is turned on.
CDMA/GSM - A type of network communication between phones and carriers. GSM phones normally are included with SIM Cards that authorize them onto the network. CDMA have this authorization built in and do not need a sim card.
CM - See CyanogenMod
CM10 - Cyanogenmod 10. A modified version of Jelly Bean release of Android 4.2.x as well as 4.3.x (see CynogenMod)
CM11 - Cyanogenmod 11. A modified version of Kitkat release of Android 4.4.x. (see CynogenMod)
Custom recovery - An unofficial recovery developed by other developers for your device. Its typically used to install unoffical ROMs. See CWM and TWRP.
CWM - ClockWorkMod, a project that makes Custom Recovery.
Cyanogenmod - A free open-source project based on the AOSP. It is a modded (see modded) version of the Android firmware
Dev - See developer.
Developer - A man or woman who has created (developed) software.
Deodexed - Where the two part ODEX files (see Odex) are moved into the actual APK (apk), thus making it one.
Execute - To "run" or "start" a binary
Firmware - a piece of software to make hardware function correctly. This can refer to Radio Firmware, but is normally used as another name for ROM. (See ROM)
Flash - The process of installing a software on your device.
Flashing - See Flash.
FOTA - "Firmware over the air" this normally refers to ROM's but can refer to radio firmware (see OTA)
Froyo - Android 2.2
GB - Could mean one of two things. 1. Gingerbread or 2. Great Britain
Gingerbread - Android 2.3
Governor - A system embedded into the kernel to automatically change the current working CPU frequency depending on the workload. It would only go up to what it is overclocked (or underclocked) to, this is called the maximum frequency. It would not drop bellow the (just as easily configurable) minimum frequency.
Honeycomb - Android 3.x. it was never released or ported to the wildfire s because it was built for tablets.
Ice cream sandwich/ICS - Android 4.0. The latest version of Android.
JDK - "Java Development Kit" an SDK for the java platform. It is needed to run the Android SDK.
JRE - "Java Runtime Environment" a collection of binarys and files to allow java software to execute.
KANG - The process of creating a code based of someone else's code.
Kernel - This is another term brought over from Linux World. A Kernel is a piece of software, that takes over from the Bootloader and then completes the booting of the device. It handles the CPU and other vital components. A modded kernel may be used for overclocking.
Library's/Libs - a set of instructions for applications to use to function. A functioning camera lib would allow the camera to be used.
Logcat - A logging system built into the ADB
Mod - A modification to a part of the phones software. It is also POSSIBLE to mod the phones hardware but is not recommended.
Modding - To perform a mod
Modded - to have included mods or condition after applying a mod.
Modification - see mod
Open-Source - (not to be confused with free) A piece of software that is free to edit, use, distribute and share with no charge.
OTA - "Over the air" a term used to indicate software that was sent to phones directly through the internet to their phones.
Radio - (not to be confused with Radio Firmware) A piece of hardware that allows communication. There are 3 main radios in your phone. Bluetooth, WiFi and GSM/CDMA.
Radio Firmware - (see firmware) a type of software that allows correct communication with the radio and the operating system. A newer firmware would normally improve battery life and call quality. The radio firmware only applies to the CDMA/GSM radio.
Overclock - (not to be confused with underclock) to exceed the default maximum CPU speed. This could make a phone more powerful but may cause damage. Although no damaged has been reported so far it could still drain battery life.
Nandroid - Its a process of taking a backup of most of the partitions in Android. This is usually performed in Recovery Console when OS is not running.
Partition - Similar to Linux, Android storage is divided into Partitions. These are akin to compartments that house specific part of the OS boot and operation.
RAM - Could be one of three meanings: 1. Memory for the CPU to process processes. 2. Random Access Memory, a place where information can be used, executed from, modified, or deleted. 3. A type of sheep.
Recovery - Its a dedicated Android partition, that has Recovery console installed. This is invisible during normal operation of the android device.
ROM - 1. A modified version of the Android operating system operating system. 2. Read Only Memory, a place where information is stored and can not be destroyed, modified or written to.
RUU - "ROM Update Utility" An automatic installer for Radio Firmware, ROM and HBOOT. (Predominantly used on HTC).
SD - Short term for MicroSD
SDK - "Software Development Kit" a set of tools used for software development.
Soft Brick - When the device refuses to boot despite a full battery, but shows some other signs of life, its considered as soft Bricked. Also see Brick
Stock - An unchanged version of something. Example: I just flashed stock Rom. Typically this term may be used to refer to Official firmware. But this is not the case always.
TWRP - Team Win Recovery Project. This also has a newer edition called TWRP 2.
Underclock - to change your phones maximum frequency to LOWER than the default to attempt to extend the phones lifespan and battery.
WFS - "Wildfire S" an armv6 device made by HTC in 2011.
WIP - "Work In Progress"
Zipalligned - This is something that makes a ROM faster. Best see this link for more.
Click to expand...
Click to collapse
Ok Now that you have a hang of your device, you probably want to explore your options and maybe install a Custom Rom. Well, the first thing you will need is to Root the Device.
So what really is a Root ? Why should I do it ? Would it break my Phone ? How about my Warranty ? All legitimate questions. To start off, here's an easy guide by Lifehacker. This whole concept may seem mystical to some of us. Let me try to make it pretty straightforward. Rooting is a process on Android that effectively grants you superuser access. Think of it as Administrator access on Windows. Android is a derivative of Linux. So those from Linux should have no difficulty with this concept.
There are certain operations that only a Superuser can do. Hence you'd want to root in order to so. For ex, remove any application that is installed as System application. Just like on on Windows, Root access does come with risk, so you need to use it with care. Just because you have Root access, does not mean your phone is broken. Typically making wrong changes to system with Root access, will result in affecting smooth operation of your phone. In extreme cases, the device may be Bricked if incorrect software (Rom, Mod or others) is flashed.
When it comes to Warranty, typically Root as such does not void your warranty. But if you end up flashing anything with a custom Recovery, then your Warranty may be voided.
Rooting -
Ok so, I got what Root is and I need to be responsible in what I do. How do I get the root ? Well the first and basic thing would be to install appropriate drivers for Windows.
Next in order to Root, please follow this thread by @paulobrien . As you will see, there are two ways to go about it. Both do require your Bootloader to be unlocked. However, neither method, applies to the Google Play Edition (XT1032) as there is no supporting Custom Recovery for this variant.
If you do not have or do not wish to unlock your bootloader then you can opt for @oasoas014 's method of bootloader downgrade. You may also visit @Cooptx's more detailed guide. Note, with the most recent recoveries, you do not need to downgrade your bootloader.
Note - Flashing a bootloader is inherently dangerous. You can possibly hardbrick your device if you flash incorrect bootloader. Always check the MD5 value of downloaded file.
Only In Case of Moto G Google Play Edition (XT1032), it is possible to unlock the Bootloader on your own. You do not need to pay to get an Unlock Code from Motorola. Instead, you can follow the same method as Nexus or other Google Play Devices. Here's a nice tutorial. For those technically minded, here's Android Source Documentation of the same process. Once unlocked, the bootloader cannot be re-locked unless you flash a signed system image, (which Motorola has not made available as of 01-22-2014).
One of the first things you should do upon Rooting is to backup your PDS Partition.
[SIZE=+1]How to backup / restore PDS partition and why?[/SIZE]On Motorola devices the 'pds' partition contains information specific to your machine: IMEI, MAC address, serial number, etc. This partition can be lost by accidental format or over time due to filesystem corruption. If you have made a backup, there is a good chance you can bring your handset back to life.
==> PDS backup will help to restore lost IMEI. It is a situation when the phone reports that the IMEI is unknown. ; This works like a vaccine, apply before having issue with IMEI, after it will be too late !
Instructions:
**Root Required**
Using ADB you can make a copy of the partition and move it to a safe place (Google Drive?):adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/pds of=/sdcard/pds.imgTo restore in the event of corruption or loss:adb shell
su
dd if=/sdcard/pds.img of=/dev/block/platform/msm_sdcc.1/by-name/pds(assuming you've pushed pds.img to internal SDcard storage first)
Click to expand...
Click to collapse
Once rooted, some of you may wish to stick with that and not proceed any further. With root, you will want to remove some of the apps that you don't need. I wish to suggest that you take a complete backup with a tool such as Titanium Backup. That way if you accidentally uninstall/remove something that's critical to android's operation, then you can restore it. For those of you, who wish to install custom Rom, read on.
The first step towards installing a custom Rom is to install a custom Recovery.
Please note, In order to flash any custom Recoveries, you need to have unlocked Bootloader. The viable options are either follow this guide or get an unlock code from Motorola.
Custom Recoveries -
A Custom Recovery is a unofficial Recovery Console that can be flashed to your device's Recovery Partition.
Typically unofficial recoveries offer several advantages over Stock or Official Recovery. Hence the unofficial recoveries are necessary in order to flash a Custom Rom. Apart from flashing a Rom, Kernel or any other firmware, unofficial Recoveries can also take Nandroids.
An unofficial Recovery is also commonly referred to as Custom Recovery. There are two major projects that contribute Custom recoveries. One is called CWM. The other is called TWRP. Given bellow is a list of Custom Recoveries available for your device.
Note - CWM and TWRP recoveries do not support the Google Play Edition variant (XT1032). You will need to wait for Motorola to release the Kernel source code before @a1Pha can support. However Philz Touch does support Google Play Edition.
CWM Recovery v 6.0.4.5 by @a1Pha -
This is the ClockWorkMod Recovery for the Moto G. Head over to the thread for more details.
(Thread as of 12-15-2013)
CWM 6.0.4.7 Swipe Recovery from CM11 thread
CWM 6.0.4.7 Swipe Recovery
TWRP Recovery v2.6.3.0 by @a1Pha -
This is TWRP 2 project brought over to Moto G by @a1Pha. Keeping with TWRP 2, its a Touch Recovery. Head over to the thread for more details.
(Thread updated as of 12-09-13)
Philz's Touch Recovery v2.6.3.0 by @Phil3759 -
This is CWM Advanced Edition Recovery for the Moto G. Head over to the Thread for more details. Other members have reported that this is compatible with the Google Play Edition of this phone.
ROMs for Moto G
ROMs -
Given bellow is a list of known Roms for Moto G. Most of the Custom Roms for Moto G require Unlocked Bootloader in order to flash via custom Recovery. Only in the case of Stock firmware or Stock based firmware, it will be possible to flash without unlocked bootloader.
If I miss on a Great Rom, let me know.
AOSP ROMs - [KITKAT 4.4.x]
Android Open Source Project, commonly known as AOSP is a repository of Official Google Codebase for Android. Any Rom built from this code will provide a true Android Experience.
CM 11 (Unofficial) - by @Dhacker29
Unofficial release of CynogenMod 11 (4.4.2) for the Moto G. It is released only for GSM variants only. International GSM and US domestic (AT&T and T-Mobile) are supported. Please head over to the thread for details.
Nexus G - by @xmattjus
This Rom offers a pure vanilla Nexus experience on your Moto G. As of 13-01014, Modem does not work for dual sim models. Please see the thread for details.
SlimKat Unofficial - by @SpaceKiller
Following on the Traditions of Slim Rom, this unofficial port provides the same experience on Motorola G. As of 01-18-14, the rom supports only GSM Variants for EU, International and US. Please see the thread for more details.
Paranoid Android Unofficial - by @Vocoderism
Unofficial Port of the Paranoid Android Rom for Moto G. This rom is intended only for EU and international GSM variants. Please see the thread for more details.
Beanstalk Unofficial - by @Cameron581
This Rom is based on the CM codebase as well as Slim Code. It has a lot of nice features. Please see the thread for more details.
AOSP ROMs - [JB 4.3]
None Listed as of 12-31-2013.
Stock based ROMs - [Kitkat 4.4]
Stock Firmware - [KITKAT 4.4.2] by @antiquezip
The OTA Update to Kitkat 4.4.2 is posted for the U. S. GSM version of this device. It is dubbed as U.S. GSM (UMTS Version with AWS)
Please see this thread for more details.
This note, it is possible to apply this update to other Non-US GSM Devices successfully. Please look for a Guide in Post 4.
Kitkat+ Rom - [Kitkat 4.4.2] by @anerik
This is a stock based Kitkat rom. It enhances the stock Kitkat firmware and hence the name. Please head over to the thread for details.
OTA Firmware (All variants) - [Kitkat 4.4.2] by @josalaito
The original 4.4.2 release for GSM version has been re-packed for all variants of this device. It now applies to US as well as international versions of the Moto G. Head over to the thread for details.
(Rom Thread as of 12-23-2013.)
Stock based ROMs - [JB 4.3]
List of Stock Firmwares by @Skrilax_CZ -
All the Stock unrooted firmwares are available over here. The process to flash this, has been linked in the Post 3.
INFUSION B2 Rom by @tillaz -
This is a modified stock based Rom. Please head over to the thread for more details. Or you could also visit Modaco Thread for Screenshots and more details.
(Rom Thread as of 12-23-2013)
KERNELS -
Given bellow is a list of kernels for Moto G. Please let me know if there's one I have missed.
AOSP Kernels -
Hybrid Kernel by @faux123 - [for JB 4.2]
Although based on Linux 3.4, this kernel incorporates some of the advanced features of Linux 3.8+. Head over to the thread for more details.
[ANYKERNEL] pink Kernel by @pinkflozd
This kernel offers a host of features. It does support ExFAT and NTFS. It is based on Linux 3.4.x. It is not Compatible with Stock Rom. Head over to the thread for more details.
Furnace Kernel by @Savoca
This Kernel offers a host of features and includes good collection of Governers and Schedulers. It is based on Linux 3.4.x. It is not Compatible with Stock Rom. Head over to the thread for more details.
Baseband/Modems -
We have a list of possible Modems / Basebands for the Moto G. Please see the thread by @lost101 for details. The thread is Work in progress as of 04-16-2014.
Guides, Tutorials, How To -
Streamlined Rooting International Variants - [Kitkat 4.4.2] by @nupi
This thread has a nice Guide for Non-US versions the Moto G. by This only applies to those who have updated to Kitkat. See the thread for details.
How to Flash OTA Update to Non-US GSM Devices - by @darkeingel
For the Stock OTA updates that are being rolled out, here is a nice Guide by @darkeingel.
GUIDE : APK Parsing Errors -
When uninstalling an app, you got an error message "APK not found" or something to that effect, you may want to follow this Guide.
Mods and Apps -
Calendar Mod - by @Shaftenberg
This mod lets you see Text view in the Calendar when looking at Month as a whole. Head over to the thread for more details.
Status Bar Mod - Remove Carrier Label - by @Shaftenberg
This mod helps you to remove the Carrier's name from the phone's status bar. See the thread for details.
Volume Button Mod - by @Shaftenberg
This mod allows you to long press volume button to skip to the next Track or to the previous track. See the thread for details.
[Xposed] Framework Mods for Moto G -
Xposed Framework is a new framework introduced to the AOSP world. It helps access and modify system settings on the fly that would have otherwise taken a lot of steps.
MotoGuide collection of Tweaks -
@Kameo has created MotoGuide, a collection of assorted appearance tweaks to modify Status bar and other changes. Please see the thread for more details.
Wakeup on Volume Up -
@dubidu has written a module to the framework that allows you to wake the phone by pressing the Volume Up button. See the thread for details. You do need the Framework installed as basic requirement. You may wish to also visit a list of all Xposed modules written. Note, not all of them will work with Moto G.
Modified Phone Apk displaying Caller photo - by @shaftenberg
This mod shows the full picture of the caller from your contacts instead of being cut off at top. See the thread for the screeshot and details.
Customizations - Themes, Bootanimations, Media -
Boot Animation - by@Cooptx
There's a great bootanimation created from one of the Moto G animation video files. Please see the thread for details.
Font Pack for Motorola G- by @gianton
We have universal Font Packs that are compatible with Moto G. These can be flashed from Custom Recovery. Please see the thread for details.
Specific to International Variants -
Thanks for this!
Enviado de meu XT1033 usando Tapatalk
leonardoroza said:
Thanks for this!
Click to expand...
Click to collapse
I am still building this. Presently working on my Moto X thread.
Update this with a new faux Kernel
This summary is very helpful thank you.
Sent from my XT1034 using XDA Premium 4 mobile app
root problem
Hello!
I have a Moto G with android 4.3, and I want to root, but I can't.
Can you help me please?
I installed the moto driver, the java jdk, and I not find the android jdk.
What I find 480 Mb and there is no install file. /on windows 7 X84/ :silly: :crying:
It would be great if you could add a link to the stock ROM images
robagp said:
Hello!
I have a Moto G with android 4.3, and I want to root, but I can't.
Can you help me please?
I installed the moto driver, the java jdk, and I not find the android jdk.
What I find 480 Mb and there is no install file. /on windows 7 X84/ :silly: :crying:
Click to expand...
Click to collapse
Please follow this thread.
Cooptx said:
It would be great if you could add a link to the stock ROM images
Click to expand...
Click to collapse
I intend to. I am working on building up. Its a work in progress.
Hello!
I have a new problem /the jdk is ok now/
I want to open the bootloader, and they write me the email is sent, but nothing. I not get email, not in spam too.
I used my gmail email, when I login the motorola site.
I made again, but same, no email.
robagp said:
Hello!
I have a new problem /the jdk is ok now/
I want to open the bootloader, and they write me the email is sent, but nothing. I not get email, not in spam too.
I used my gmail email, when I login the motorola site.
I made again, but same, no email.
Click to expand...
Click to collapse
It may take a day or so. Please wait 24 to 48 hours.
Hello!
I have again a problem.
I unlocked the bootloader, when it start shows the screen.
I want to root but nothing.
I downloaded the Superboot, and I do this:
OSs-MacBook-Pro:r2sr maverick$ chmod +x superboot-mac.sh
OSs-MacBook-Pro:r2sr maverick$ sudo ./superboot-mac.sh
Password:
downloading 'boot.img'...
OKAY [ 0.356s]
booting...
OKAY [ 0.251s]
finished. total time: 0.607s
OSs-MacBook-Pro:r2sr maverick$
But when restart nothing. I downloaded googleplay store the superSU , but it shows:
There is no SU binary installed, and SuperSU cannot install it.
:crying:
I do it with windows but not rooted too...
robagp said:
Hello!
I have again a problem.
I unlocked the bootloader, when it start shows the screen.
I want to root but nothing.
I downloaded the Superboot, and I do this:
OSs-MacBook-Pro:r2sr maverick$ chmod +x superboot-mac.sh
OSs-MacBook-Pro:r2sr maverick$ sudo ./superboot-mac.sh
Password:
downloading 'boot.img'...
OKAY [ 0.356s]
booting...
OKAY [ 0.251s]
finished. total time: 0.607s
OSs-MacBook-Pro:r2sr maverick$
But when restart nothing. I downloaded googleplay store the superSU , but it shows:
There is no SU binary installed, and SuperSU cannot install it.
:crying:
I do it with windows but not rooted too...
Click to expand...
Click to collapse
Please note that this is a resource guide, not a Q&A thread. I have written a guide that I think may help you. http://forum.xda-developers.com/showthread.php?t=2585755
Disregard, already corrected.
AFAIK touchless control and active notifications are for the X only, please correct the first post(or me if I'm wrong)
Sent from my phone
miklosbard said:
AFAIK touchless control and active notifications are for the X only, please correct the first post(or me if I'm wrong)
Sent from my phone
Click to expand...
Click to collapse
You are correct.
Edit: Moto Maker is also not available for the Moto G
More OP edits
CM9 - Cyanogenmod 9. A modified version of ICS. (see CynogenMod)
CM10 - Cyanogenmod 10. A modified version of ICS. (see CynogenMod)
Should be JB
CM11 - Cyanogenmod 11. A modified version of ICS. (see CynogenMod)
Should be KK
Not that it matters right now, because we don't have any CM
Also, CyanogenMod is spelt wrong at the end. And I am pretty sure that you can remove all preJB words
INFUSION B2 Rom by @tillaz -
This is a JB ROM
And there is no need to label JB as 4.1, 4.2 and 4.3 because we only have 4.3
Also, you should add the two root methods for KK
http://forum.xda-developers.com/showthread.php?t=2583652
http://forum.xda-developers.com/showthread.php?t=2585755
In OP special features have listed Active noti and Touchless controls ....
both are not features of G(they are of moto x)
Cooptx said:
You are correct.
Edit: Moto Maker is also not available for the Moto G
More OP edits
CM9 - Cyanogenmod 9. A modified version of ICS. (see CynogenMod)
CM10 - Cyanogenmod 10. A modified version of ICS. (see CynogenMod)
Should be JB
CM11 - Cyanogenmod 11. A modified version of ICS. (see CynogenMod)
Should be KK
Not that it matters right now, because we don't have any CM
Also, CyanogenMod is spelt wrong at the end. And I am pretty sure that you can remove all preJB words
INFUSION B2 Rom by @tillaz -
This is a JB ROM
And there is no need to label JB as 4.1, 4.2 and 4.3 because we only have 4.3
Also, you should add the two root methods for KK
http://forum.xda-developers.com/showthread.php?t=2583652
http://forum.xda-developers.com/showthread.php?t=2585755
Click to expand...
Click to collapse
Thanks for mentioning. I have made rest of the changes except for the 2 Root methods. Will add them to the Op. All changes are done.
Between the two methods you have mentioned, the basic premise of bootloader downgrade is pretty much the same right ? Your's seems more elaborate list of steps. Or am I missing something ?
Ankush menat said:
In OP special features have listed Active noti and Touchless controls ....
both are not features of G(they are of moto x)
Click to expand...
Click to collapse
Thanks for mentioning. This has been corrected.
Hello again:
Build B2G for ZTE Open (inari) is tricky. People who want to develop applications with firefox's app-manager extension need to wait for ZTE upgrades or build their own system, which involves some permission modifications in boot.img and some tweaking to recover the bootanimation (lost on custom builds) among other things.
But hey, I've build a production pre-release of firefox os 1.2, and so far so good , and I like to share it with you via a flashable .zip file. Remember this file can be installed ONLY from CWM recovery, cause its not signed
features:
Version 1.2-prerelease (user release):
Build with blobs from version 1.1.0B02 (also known as 1.1.0B06) for ZTE Open (EU version)
Multilanguage - upgradeable through B2G nightlies (for both gecko & gaia)
Compatible with firefox app-manager (firefox 26+)
Includes su & busybox binaries ( busybox is linked with clear, grep, head, less, lsmod, more, nohup, pidof, ping, printf, pstree, sysctl, tail, telnetd, tftpd, traceroute, uname & usleep, for debugging via adb)
No carrier branding, just official firefox os branding
Fastboot enabled | ADB rooted
does *NOT* overwrite your recovery partition (you won't loose CWM recovery )
known bugs: isn't a bug but a security feature: "ADB should not be allowed to connect when device is locked in production builds"
FAQ:
I'm on version 1.x.y of 'some-carrier' build, Will this zip work in my case: Yes, only and just only if you have CWM installed.
There are a lot of strange files inside .zip, why ? this is because ZTE provides upgrades with radio & bootloader firmware (incompatibles between versions) If I want to support this ROM I need to make sure everyone have the same version ( the version that matches with the blobs )
Of course, YOUR WARRANTY IS VOID, and if you brick your phone , this is NOT MY FAULT
the link to the zip file: ul.to/2jwkruhj
Feedback is welcome
paziusss said:
Hello again:
Build B2G for ZTE Open (inari) is tricky. People who want to develop applications with firefox's app-manager extension need to wait for ZTE upgrades or build their own system, which involves some permission modifications in boot.img and some tweaking to recover the bootanimation (lost on custom builds) among other things.
But hey, I've build a production pre-release of firefox os 1.2, and so far so good , and I like to share it with you via a flashable .zip file. Remember this file can be installed ONLY from CWM recovery, cause its not signed
...
Feedback is welcome
Click to expand...
Click to collapse
Runs great, I will use your build to test and mod some apps with the app-manager.
And please, stay at this good work (updates etc?!)
---edited:
Is your build a development build (of FFOS 1.2)? I cant't open certified apps with the app-manager (I have changed the pref "devtools.debugger.forbid-certified-apps" to false in my profile. But there is no certified app to see or to open in the app-manager. If not, can you - or somebody else - build this development build of FFOS 1.2?
ROM is pretty stable. I don't know if I'm the only one having this issue, but it looks like my data is connecting but then it isn't working. I'm connected to AT&T right now. When I pull down the notification bar, I see that I am getting an "H" (HSPA+) signal but if I try to open firefox and hit a site, it says I'm not connected to the internet.
I'm aware that this is in a prerelease state but do you know how I could fix this?
@martin_s5670: AFAIK there are three types of builds: engineer builds, userdebug builds and user builds. This is an user build, but you can also test privilegied (aka certified) apps on it. If you want to see your installed system apps I'm sorry but you can't do it in this way
@ryanolson7: could you please test your connection via a ping
adb shell
ping www.google.com
if you can't reach google, then I would appreciate if you paste somewhere your logcat in this way:
adb logcat | grep RIL > file.log
and just deactivate data, wait a few seconds, and activate it again.
---
I'll do some further tests on this branch (because some blobs may change from 1.0.1) but here in Spain both 3G & 2G data seems to works well, need to find a place with HSPA+.
Are you in the USA? I'm asking because this rom is based in open_eu release ( AFAIK they are the same except for radio capabilities )
Thanks for the feedback
Great Job!
Thanks! Tried and working. I have even received a update, and still working smooth!
can you tell me about the creating this ROM process?
I'm using US rom, I just want to use these blobs to make a custom builds, but flashing all the images bricked my phone. Can you explain me about the steps you did to package this ROM?
paziusss said:
...
Feedback is welcome
Click to expand...
Click to collapse
@ paziusss:
Maybe a littele bug: The app "calendar" starts everytime when your build will be booted - without open it separetly.
im new here
i want to know if i can use this in my nexus 4 multirom android 4 KK
Need FF OS 1.3
Can anyone please provide me zip file of FF OS 1.3?
Thanks
LinuxHolic said:
Can anyone please provide me zip file of FF OS 1.3?
Thanks
Click to expand...
Click to collapse
Not quite a zip, but, https://daylightpirates.org/b2g_inari_nightly_builds/
Bad Luck
Deathwish238 said:
Not quite a zip, but, https://daylightpirates.org/b2g_inari_nightly_builds/
Click to expand...
Click to collapse
I flashed the latest nightly build and everything went fine but my mobile is sitting on Fox now and restarts constantly
Look
LinuxHolic said:
I flashed the latest nightly build and everything went fine but my mobile is sitting on Fox now and restarts constantly
Click to expand...
Click to collapse
groups [dot] google [dot]com/d/msg/mozilla.dev.b2g/dENpc-7Fbi4/80t6EyS6bwIJ
is the included radio for european or american zte opens?
@hecatae:
blobs were pulled from 1.1.0B02 - UK but radio firmware should be the same for both UK and US versions
paziusss said:
Hello again:
Build B2G for ZTE Open (inari) is tricky.
Feedback is welcome
Click to expand...
Click to collapse
HI!
Can you build with added Russian keyboard?
I wanna use 1,2. Because it have RU locale, but have not keyboard.... (((
At 1.1. have not RU locale, but it have RU keyboard
FM radio doesn't work, no sound.
Japanese?
Could someone enable the Japanese keyboard and provide a ROM? I can explain how to do it, just can't build for it
thanks
thanks for your rom
Introduction
Recently, I have noticed about the multiple new roms that requires the boot 41.18+ and refuses to be installed over the 41.13 one, & that's why I had to "make" this script using various files from google, and other sites, and obviously a keyboard
I made a Spanish Version (wich has been tested many times) and now for xda, the english one
If you want something like this for another model, just provide correct bootloader, and let me see what can I do :fingers-crossed:
Supported devices:
xt1002, xt1003, xt1008, xt1028, xt1031, xt1032, xt1033, xt1034, xt1039, xt1040, xt1042, xt1045 :victory:
Download v1.29Old downloads | Bootloaders in zip mode.
First of all, you should read post 3 (FAQ) We don't want your device gets bricked
Requisites:
-Have the motorola drivers installed.
-Usb cable.
-For the moment you need to use Windows.
-I'll try to get this working on Linux and Mac. Something went wrong I got a Mac, trying to make it.
Hope you find it useful. :highfive:
Don't forget to hit thanks if helped you! :good:
XDA:DevDB Information
Bootloader Upgrader Tool, Tool/Utility for the Moto G
Contributors
Xyzko, lost101
Source Code: https://goo.gl/N6Mk47
Version Information
Status: Stable
Current Stable Version: v1.29
Stable Release Date: 2015-12-07
Current Beta Version: ---
Created 2015-05-24
Last Updated 2015-12-12
Current changelog -- 21/11/2015
[version] -Updated to 1.29.
[new] -Added support for upgrading xt1028 & xt1042 to 41.1A
[fix] -Fixed (or should be fixed) update script for xt1032-41.1A on English.
[fix] -Cleaned more code, more "double hit" deleted.
Old changelogs
Old changelog: -- 21/11/2015
[new] -Updated to v.1.22
[new] -Added support for upgrading xt1031 to 41.1A
[new] -Re-added Spanish support.
[fix] -Cleaned code to delete the need of "double hit enter" on some windows version.
[merge] -Now lang selector is again on the script.
[up] -Updated screenshots.
Old changelog: -- 11/10/2015
[new] -now using androidfilehost as server due to troubles with xda filesystem.
[new] -merged original and lite version
[new] -deleted spanish support (for now, will come back on the next update)
[new] -now can upgrade to 41.1A also these devices: xt032, xt1033, xt1034.
Old changelog: -- 13/09/2015
[new] -added lite version with only some rare variants.
[new] -added suport for the xt1002, xt1003 & xt1008 variants.
[fixed] -now the script also lets you to select a lang (instead of making two scripts)
[help] -if you wanna contribute with a translate to your lang, send me a PM
Old changelog: -- 19/07/2015
[new] -added suport for the xt1045 variant
[note] -Updated to v1.16a, some lines changed.
[note] -Some lang faults fixed.
old changelog: -- 22/06/2015
[new] -added suport for the xt1039 variant
[new] -added suport for the xt1040 variant
[note] -Updated to v1.12b, ther are the changes
Old changelog: -- 15/05/2015
[new] -redesigned all the scripts in a bigger one with support of xt1032,33 and 34
[new] -added multiple chooser to the script, it let's you to select what to do
[fix] -added some extra lines in the code to make it "safer"
[dev] -you can view the script and suggest, or find bugs here
Old changelog: -- 09/05/2015
[new] -made an specific one for the xt1034 variant
Old changelog: -- 02/05/2015
[new] -made an specific one for the xt1033 variant
[new] -made new script for those who wants the GPE 41.19 one
Old changelog: -- 27/04/2015
[new] translated to english and published on xda
Old changelog: -- 14/04/2015
-initial release.
Reserved for notes and FAQ.
Important note:
lost101 said:
It should be mentioned that flashing an incorrect Bootloader (motoboot.img) could result in an instant hard-brick. Upgrading Bootloader is not something that should be casually done with any motoboot.img.
For safety, each model should have a specific script that includes the correct Bootloader for that model.
Click to expand...
Click to collapse
And this works only on xt1028, xt1031, xt1032, xt1033, xt1034, xt1039, xt1040, xt1042 xt1045, xt1002, xt1003 & the xt1008 variants. I think those are all variants available, but... however.
For Moto G 4G users
After upgrading, you may lose signal. To fix it, just flash latest radio firmware available here. As always, thanks to @lost101
For all users
Don't flash random bootloaders on random device, It can gets bricked!
FAQ
Q: Can I flash it on a peregrine (4G)?
A: No. Congratulations, now you can
Q: I got an screen fllickering after updating the bootloader
A: Update your rom and kernel to one using latest sources.
Q: Can I flash it if I already have the 41.18 one?
A: Why are you planing to do it?
Q: Screenshot?
A: 4th post.
Q: Can I flash the xt1032 on a xt1040?
A: See up.
Q: Does the dodo flies?
A: Yeah, it flies if I can fly :v
Q: Can I downgrade from the 41.19 to the 41.18?
A: You can check this
Q: How to know if I have latest bootloader?
A: The chronological order is: 41.05 -> 41.13 -> 41.18 -> 41.19 -> 41.1A.
Screenshots.
Have a look before you try
Thank you.
P.D: I didn't test it but I appreciate your effort.
It should be mentioned that flashing an incorrect Bootloader (motoboot.img) could result in an instant hard-brick. Upgrading Bootloader is not something that should be casually done with any motoboot.img.
For safety, each model should have a specific script that includes the correct Bootloader for that model.
lost101 said:
It should be mentioned that flashing an incorrect Bootloader (motoboot.img) could result in an instant hard-brick. Upgrading Bootloader is not something that should be casually done with any motoboot.img.
For safety, each model should have a specific script that includes the correct Bootloader for that model.
Click to expand...
Click to collapse
At the start of the script it tells you that is only for xt1032 and 33, but thanks, I'll add it to the OP.
I flashed full 5.0.1 lollipop ROM.
& in bootloader menu i can see 41.18
Does that mean bootloader is updated??
Shouldn't this work on XT1031? The bootloader for it is 41.19
.:Addicted:. said:
I flashed full 5.0.1 lollipop ROM.
& in bootloader menu i can see 41.18
Does that mean bootloader is updated??
Click to expand...
Click to collapse
Yeah, that's the normal way to update bootloader
itslels said:
Shouldn't this work on XT1031? The bootloader for it is 41.19
Click to expand...
Click to collapse
I think no... As lost101 sayid,
lost101 said:
It should be mentioned that flashing an incorrect Bootloader (motoboot.img) could result in an instant hard-brick. Upgrading Bootloader is not something that should be casually done with any motoboot.img.
For safety, each model should have a specific script that includes the correct Bootloader for that model.
Click to expand...
Click to collapse
Ya , boot-loader is something that actually flashes files to ROM.
Bootloader makes it possible for chip to communicate through USB.
So if you flash incorrect file then you need to correct that by mannually opening chip & connecting may be through ISB or any other available for ARM processor
Updated
Thread updated, added xt1034 variant :victory: :fingers-crossed:
Current changelog 09/05/2015
[new] -made an specific one for the xt1034 variant
Click to expand...
Click to collapse
again, thanks to @lost101
@Xyzko
Can the 41.19 be installed on xt1033
FYI- Currently on 41.18
sjandroiddeveloper said:
@Xyzko
Can the 41.19 be installed on xt1033
FYI- Currently on 41.18
Click to expand...
Click to collapse
You should not be so trigger-happy with flashing Bootloaders - every time you do, you risk destroying your phone.
lost101 said:
You should not be so trigger-happy with flashing Bootloaders - every time you do, you risk destroying your phone.
Click to expand...
Click to collapse
I know sir, and I don't even plan to flash it
I was just asking
sjandroiddeveloper said:
I know sir, and I don't even plan to flash it
I was just asking
Click to expand...
Click to collapse
I have not read of any XT1033 user flashing it. I would personally not be comfortable flashing it if I owned an XT1033 - as it is in no way worth the risk.
The v41.19 Bootloader is intended for XT1032 / GPE - and came included with the GPE Android 5.1 Firmware. It appears to be only a very minor upgrade, with no obvious changes. However custom recoveries often need redevelopment to support new Bootloaders.
You flash at your own risk, and if it creates problems with recoveries you are stuck until they can be fixed.
In summary; you should probably only flash a newer Bootloader if absolutely necessary, or face unwanted consequences.
lost101 said:
I have not read of any XT1033 user flashing it. I would personally not be comfortable flashing it if I owned an XT1033 - as it is in no way worth the risk.
The v41.19 Bootloader intended for XT1032 / GPE - and came included with the GPE Android 5.1 Firmware. It appears to be only a very minor upgrade, with no obvious changes. However custom recoveries often need redevelopement to support new Bootloaders.
You flash at your own risk, and if it creates problems with recoveries you are stuck until they can be fixed.
In summary, you should probably only flash a newer Bootloader if absolutely necessary, or face unwanted consequences.
Click to expand...
Click to collapse
Thanks for the heads up, I will not flash it unless necessary
Q- Do you think the non gpe variants will get an official update to 5.1 because then only it may be necessary in the future to upgrade the bootloader (like it was from 41.13 to 41.18 )
sjandroiddeveloper said:
Q- Do you think the non gpe variants will get an official update to 5.1 because then only it may be necessary in the future to upgrade the bootloader (like it was from 41.13 to 41.18 )
Click to expand...
Click to collapse
I expect all variants will get 5.1 (more probably 5.1.1) - the GPE 5.1 firmware is essentially what the Stock Motorola ROMs will be. Much of the work is already done.
It's a matter of opinion how necessary upgrading to v41.18 is. I run GPE 5.1 with the v41.13 Bootloader.
lost101 said:
I expect all variants will get 5.1 (more probably 5.1.1) - the GPE 5.1 firmware is essentially what the Stock Motorola ROMs will be. Much of the work is already done.
It's a matter of opinion how necessary upgrading to v41.18 is. I run GPE 5.1 with the v41.13 Bootloader.
Click to expand...
Click to collapse
Maybe it will be necesary due to custom roms just like was been with the latest cyanogenmod and the Alberto's aosp.
The installer script refuses to be installed over the 41.13, and you need to upgrade it... or change the updater script