Technical Specifications -
Model Number(s) -
T-Mobile (Developer Edition GSM) - XT1053
AT&T, Rogers, Vivo & Claro (Brazil, Puerto Rico), Oi & TIM (Brazil), Movistar & Claro (Chile) - XT1058
Verizon - XT1060
Sprint - XT1056
US Cellular - XT1055
Republic Wireless - XT1049
US Regional (NVC,Inland Cellular, Illinois Valley Cellular) - XT1050
Europe, India - XT1052
Frequencies / Bands:
AT&T and T-Mobile - UMTS 850, 900, 1700/2100, 1900 MHz; GSM 850, 900, 1800 MHz AWS 1900, 2100 MHz
Verizon - GSM/GPRS/EDGE 850/900/1800/1900 MHz
UMTS bands 850/900/1900/2100 MHz with HSPA+ up to 42 Mbps
CDMA EVDO Rev. A: 850/1900 MHz
LTE bands 750 MHz
Sprint - Quadband GSM (850/900/1800/1900)
Tri Band UMTS (850/1900/2100)DC HSPA+
Display Resolution: 720 x 1280 pixels AMOLED
Screen Size: 4.7" 16M Color
Bluetooth Enabled: Yes
Wi-Fi Enabled: Yes
Internal Memory: 16 GB (Actual Space for user data 12 GB)
32GB (Actual Space for user data ~28 GB)
External Memory: None
Size / Dimensions: 5.09 x 2.57 x 0.41 inches (129.3 x 65.3 x 10.4 mm)
Weight: 4.59 oz (130 g)
Battery Life: 2200 mAh (Not User Replaceable)
Camera: 10 MP Camcorder: 1920x1080 (1080p HD) (60 fps) Front-facing camera: 2 megapixels
Operating System: Android 4.4, 4.3, 4.2.2
Keyboard: Touch Screen
GPS: Yes
Click to expand...
Click to collapse
Unique Features -
Motorola Assist
Active Notifications
Touchless Control
Moto Maker
Click to expand...
Click to collapse
Moto X Review -
Moto X Review - Engadget - reviewed on September 2013
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.
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
CM9 - Cyanogenmod 9. A modified version of ICS release of Android 4.0.x. (see CynogenMod)
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.
RSD - Remote software download.
RUU - "ROM Update Utility" An automatic installer for Radio Firmware, ROM and HBOOT. (Predominantly used on HTC).
SBF - A file extension used for RSDLite files.
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 the thread to install PwnMyMoto by @jcase. If you have received the Camera update, then you will need RockMyMoto to patch PwnMyMoto. are on Kitkat, then you will need SlapMyMoto. There's a nice Tutorial by @Tha TechnoCrat as well for you. There could be additional questions or specific questions about bootloader downgrade or otherwise. If so you may wish to review a reference thread by @dray_jr
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. Barring the open Bounty, the only viable option right now is to get an unlock code from Motorola. Do know that according to this blog, unlocking the Bootloader of a Developer Edition device will NOT VOID WARRANTY!
If you do not wish to unlock your Bootloader, you may also wish to explore Safe Strap. It is a Bootstrap / Recovery for locked bootloader phones. Its aim is to avoid making changes to the main system partition and only flash or make large changes to the Data Partition in general, /sdcard in particular. When SafeStrap is installed, you should see a menu at boot, with a choice to enter recovery. As of now, the recovery of Safestrap is based on TWRP 2.6.3.0. If you wish to proceed down this path, please see this thread for more details.
Reference - Moto X Forum Thread.
ROOTING WITH LOLLIPOP UPDATE -
With the Lollipop update, rooting process is different. You may wish to review [HOW TO] How to Root 5.1 with (unlocked bootloader) if you have already unlocked the bootloader. If not, you might want to do so, preferably before the update.
For those with AT&T or Verizon version of Moto X, there is another option to Root. Please review Moto X Root AT&T/VZW [KXA21.12-L1.26] for more details on this. Do note, it does require specific firmware version.
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.
The internal Storage of Moto X does support F2FS, a file system developed by Samsung engineers. The custom recoveries too do support the same.
TWRP 2 Recovery v2.7.1.1 - Official
[HIDE/] Please visit TWRP 2 Project Official website for the latest version.[/HIDE]
TWRP Recovery v2.6.3.1 by @Hashcode -
TWRP 2 Project Recovery for Android KitKat (Android v4.4). As with TWRP 2, this is a touch Recovery. Head over to the Thread for more details.
(Thread updated as of 11-19-2013)
TWRP Recovery v2.6.3 by @dhacker29 -
This is TWRP 2 project brought over to Moto X by @dhacker29. Keeping with TWRP 2, its a Touch Recovery. It does have F2FS support. Head over to the thread for more details.
(Thread updated as of 11-25-13)
CWM Recovery Touch v 6.0.4.8 by @scoobaspeaz -
Touch enabled version for XT 1060 alone. Please visit the thread for details.
(Thread as of 14th April 2014)
Philz Touch Recovery v 6.4.1.5 by @Phil3759 -
This Recovery is for all XT10xx devices. Although Philz is based on CWM, it adds a host of advanced features that are not available in CWM. Please visit the thread for more details.
(Thread as of 15th January 2014)
CWM Recovery v 6.0.4.5 by @dhacker29 -
This is an unofficial Port of the ClockWorkMod Recovery to Moto X. It does have support for F2FS. Head over to the thread for more details.
(Thread as of 12-16-2013)
Open Recovery v 2.09 by @Skrilax_CZ -
One of the big difference Open Recovery has over TWRP and CWM is that, it can backup and restore modem firmware. In particular, it can backup the following partitions.
Code:
boot, cache, data, fsg, logo, modem, modemst1, modemst2, system.
It has F2FS support, however, after Motorola released 4.4 image, f2fs has been broken. Those of you, who are using it, can chime in on any issues.
It was designed for Droid MAXX but works well for Moto X. Head over to the thread for more details.
(Thread as of 12-02-2013)
Back to Stock -
Just like rooting and using custom Roms, there will be a time when some of us might decide that they want to start over. For any reason, should you wish to restore the phone to the condition that it was in when it arrived, that's certainly possible to do. This is collectively called Return to Stock. Your best places to review are the excellent guides. You can go with
[GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash). by @TechSavvy2.
It is possible that you only wish to go to stock so that you receive Android updates such as Lollipop, in which case, you don't have to go to stock Recovery. If so, please review [REF][How To] Return to STOCK Recovery (IF rooted) and sideload OTA by @KidJoe.
ROMs for Moto X
ROMs -
Given bellow is a list of known Roms for Moto X. 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 by @dhacker -
The Rom has been posted by @scoobaspeaz on behalf of @dhacker. This is a Unified build that is confirmed to work on both the 4.3 and 4.4 bootloaders.Please visit the thread for more details.
(Rom Posted as of 16th April 2014)
TRUMOTOX Rom by @ZeROMCreator -
This CM 11 based Rom is only for the Verizon Variant XT 1060. It includes some very interesting features such as Audio Mods, Performance improvements Ad Blocking and a host of other features. Please visit the thread for more details.
(Rom Thread as of 24th December 2013)
AOSPA ROM by @ayysir -
This is an interesting AOSP Rom based on Google Codebase. The developer does not have this device but the build has been working fine for other users.
(Rom thread as of 21st March 2014)
UNOFFICIAL PARANOID ANDROID ROM BY @jabza -
We now have the famed Paranoid Android Code and its cutting edge features for the Moto X. To those who are not aware, Paranoid Android Team started as a Kang of the AOSP Codebase and have deloped new code and heavily modified existing code. It has been very popular with Android users. Please see the thread for more details of the Rom.
(Rom thread as of 14th April 2014)
CMB Rom by @nycbjr -
A CM 11 based rom offering a jet black Halo theme experience. It does remove some of the features that are preceived not helpful. Please see the thread for more details.
(Rom thread as of 7th May 2014)
UNOFFICIAL SLIMKAT ROM BY @darkspadez
This is an unofficial Release of the Slim Bean Rom for Moto X. There are some really nice features that are distinctive marks of Slim Rom. Please see the thread for more details.
(Rom thread as of 10th February 2014)
PAC MAN ROM BY @skiwong20 -
PAC Stands for PA, AOKP and CM. It takes the best features from all three code bases. This is a unified Build of the PAC Man Rom for Moto X. Please see the thread for more details.
(Rom thread as of 30th October 2013)
AOSP ROM by @dhacker -
This Rom is for Developer Edition Devices only. It is not compatible with safestrap.
Reference Thread
For Verizon
For Non-US GSM
Google Apps for both.
(Rom Posted as of 11-05-2013)
Unofficial CM 11 by @dhacker -
This Rom is only for AT&T and Verizon users only. Head over to the thread for more details.
Verizon - Rom Here.
AT&T - Rom Here.
(Rom updated as of 11-26-2013)
Open Source Evolution (OSE) Rom [Verizon Only] by @timpohladthomas -
This Kitkat Rom is more or less AOSPish. Its based on CM code. It also has some of the AOKP features. Over all sounds an interesting combination of features. Head over to the thread for details.
(The Rom is updated as of 12-08-2013)
KangKat Rom by @iB4STiD -
Although it is De-Odexed, this Rom is oriented towards Performance. It comes with a bunch of nice addons. Head over to the Rom thread for more Details.
(Rom as of 12-21-2013).
AOSP ROMs - [Jelly Bean 4.1, 4.2 & 4.3]
Unofficial CM 10.2 by @dhacker29 -
This is unofficial Release of CynogenMod for Android 4.3. Its discussion has been fragmented.
For Verizon Users - Unfortunately the discussion is split. Its in this thread and that one.
(Rom as of 12-16-2013)
Official PAC MAN Rom [JB 4.3.x] by @skiwong20 -
This is official PAC MAN Rom with Jellybean 4.3.x nightlies and Stable versions. As is the tradition with P.A.C. Roms, it has the best features of PA, AOKP and CM Roms.
According to its OP, the Rom is intended for AT&T as well as T-Mobile devices.
(Rom thread as of 10-30-2013)
Unofficial PAC Rom [JB 4.3.1] by @skiwong20 -
This is an unofficial release of the PAC Rom.
This Rom is for Verizon (Dev Edition), AT&T (Unlocked Bootloader only), T-Mobile (Developer Edition), T-Mobile (Developer Ed.), Sprint. The Rom thread is over here.
(Rom as of 10-28-2013)
AOKP for Moto X -
Android Open Kang Project (AOKP) is a project that is always introducing a lot of new features all the time. It is ubiquitously represented by the Unicorn.
Kang is another word for Copy in the Android world. In this case, the AOKP project has made a copy of the original Google Code. However, since then they have significantly modified with several features. Give it a try and see for yourself.
AOKP for T-Mobile - JB 4.3 milestone (JB-MR2) Rom here. Get the Gapps here.
AOKP for Verizon (Developer Ed) - JB 4.3 Milestone (JB-MR2) Rom here. Get the Gapps here.
Stock based ROMs - [Lollipop 5.1]
STOCK FIRMWARE -
A Listing of Lollipop firmwares as they are available is maintained by @tazlooney89 in [OFFICIAL] Collection Full Firmwares (FXZ/SBF) Lollipop 5.1.
Stock based ROMs - [Kitkat 4.4]
STOCK BASED DEODEXED ROM FOR XT1052 BY @janjan
As the name states, this Rom is only for the Variant XT 1052. It has been de-odexed making it easy to theme or do other changes. Please see the thread for more details.
(Rom thread as of 7th February 2014)
REPUBLIC WIRELESS & C-SPIRE Variant ROM BY @iKrYpToNiTe
This Rom as the name suggest is specific for the Variant XT 1049. You need to be rooted on 4.2.2 or 4.4 with Safestrap installed. You also need to have disabled write protection. Please visit the thread for more details.
(Rom thread as of 18th May 2014)
KRYPTON ROM BY @iKrYpToNiTe
This Rom is intended for Unlocked Devices with SafeStrap.Please visit the thread for more details.
(Rom Thread as of 13th April 2014)
ECLIPSE ROM BY @nitroglycerine33 -
This Kitkat Rom is based on MotoBlur framework. Its only for the Verizon devices alone. You will have to be running latest OTA update before flashing this Rom. Head over to the Rom thread for more details.
(Rom as of 12-21-2013)
Stock Firmware for Sprint Version only by @gokart2
We have two versions of the Stock Rom on the Sprint Moto X.
Version 139.14.1
Version 139.44.8
Both versions are available in Stock unrooted as well as de-odexed Rooted format. Head over to the thread for details. (Rom as of 12-20-2013).
NOOB Rom by @abiezer
This is a modified version of the Stock OTA Release of KitKat for the Sprint version alone. It requires unlocked bootloader and a custom recovery. Please head over to the thread for details.
(Rom as of 12-20-2013)
Stock based ROMs - [JB 4.1, 4.2, 4.3]
Rooted Stock Rom by @Ctrl-Freak -
For AT&T Users
-Version 139.12.54 Ghost Rom Thread by @AI936. (Rom as of 10-16-2013).
-Version 140.44.3 Ghost Rom Thread. (Rom as of 11-26-2013)
-Version 140.44.5 Rom Thread (Rom as of 11-27-2013)
For T-Mobile Users - Android 4.3 Rom Thread by @TheOrangeRemix. Packaged thread by @dhacker(Rom as of 11-15-2013)
For Rogers (Canada) users
Version 139.12.36 Ghost Unrooted Rom Thread by @AI936
For Verizon users
Version 139.15.1 Ghost Unrooted Rom thread by @AI936
Version 139.12.57 (Off of T-Mo version) Rom thread by @doobie711
Stock Firmwares for all variants by @Skrilax_CZ -
Thanks to @Skrilax_CZ, we have a single place where all the stock firmwares for this device are located. One may also wish to review [INFO/TIP] Web sites for official and LEAKED roms.
Kernels -
Given bellow is a list of known Kernels for Moto X. If I miss on a good one, let me know.
AOSP Kernels - [Kitkat 4.4]
Enhanced Kernel by @rob43 -
This Kernel is based on the Source. It offers variety of advanced features such as Swipe2Sleep and Fast Charge. It also allows undervolting and oveclocking. It is compatible with all Verizon, AT&T and T-Mobile devices. Some have tested it successfully with Sprint version as well. Head over to the thread for more details. Unlocked Device required.
arrrghhh's kernel! by @arrrghhh -
This kernel is based on CM Source. It also offers stock based versions. It offers a lot of choices in Governors as well as Schedulers. Ideal for you if you prefer to tinker with Governor settings for Battery or Performance. Head over to the thread for more details.There is no explicit supported device listed. That makes me think its supports all versions of the Moto X.
Stock based Kernels - [Kitkat 4.4]
Enhanced Kernel by @rob43 -
This kernel has been enhanced significantly to add some pretty cool features such as Sweep2Sleep and Fast Charge. Please see the thread for more details.
Hybrid Kernel by @faux123 -
Although it still has the 3.4.0 kernel label, it has incorporated many advanced features available only on Linux 3.8+ and beyond. I have backported many of those advanced features for Linux 3.4, hence the name hybrid. Please visit the thread for more details.
AOSP Kernels - [JB 4.1, 4.2, 4.3]
arrrghhh's kernel! by @arrrghhh -
This kernel is based on CM Source. It also offers stock based versions. It offers a lot of choices in Governors as well as Schedulers. Ideal for you if you prefer to tinker with Governor settings for Battery or Performance. Head over to the thread for more details. There is no explicit supported device listed. That makes me think its supports all versions of the Moto X.
Stock based Kernels - [JB 4.1, 4.2, 4.3]
Rooted Stock Kernel by @rob43 -
This Kernel is based on the Stock Kernel for AT&T and Rogers (Canada). It roots the device and installs SuperSU on Boot. Head over to the thread for more details.
Basebands/Radios/Modems -
For the Verizon Edition of Moto X, we now have 4.2.2 Modems/Radios. Please thank @aviwdoowks and see his thread.
Mods & Tools-
Given Bellow is a list of some of the common Mods for the users. This is not a complete list by any means. It is not intended to be one. The intent is on collating easy to use mods for new users.
Moto X Toolkit -
A tool to Backup or Restore User Apps/Data or flash BootAnimation/Recovery etc. Please see the thread for details.
MotoWPNoMo Remove Write Protect-
This tool will remount your System Partition as Read-Write so you don't have to reboot to Recovery. See the thread for details.
MotoX FXZ Back to Stock - [Linux, Mac]
This tool allows you to flash your Moto X back to Stock. Please see the thread for details. Although the current version works, it is no longer supported.
NFC Unlock Tag Creator - (For Non Developer Ed. Devices)
Typically this feature is available on the Developer Edition devices. However, we have an app that'd allow you to do so on Non-Developer Edition devices. Please see the thread for details.
Enable Native Tether -
This mod enables, native tether even when your Data plan is not enabled for the same. Please see the thread for details. This works for Sprint, Verizon and AT&T.
Remove Unsafe Volume Warning -
This mod allows you to get rid of the warning message "Raise Volume above Safe Level ?". Please see the thread for details.
Customizations - Themes, Bootanimations, Wallpapers -
Xposed Mods for Moto X -
Xposed Framework is a system level framework. By itself it does not change anything. However, others have written modules that make use of this framework to do some nice mods. Bellow are a couple developed for Moto X. You can check this thread for a bigger list.
Remove Navigation Bar - As the name says. See the thread for details.
Status Bar Mods - Another Xposed Mod that makes few changes to Status bar appearance. See the thread for details.
Statusbar changes -
As the name says, this mod for Verizon will reduce the size of carrier Data signal icon. For AT&T, you may want to see this other mod. If you like Kitkat AOSP statusbar, try this mod instead.
Bootanimations and Media -
At boot, typically you see two different animations. First one is called a Boot Logo and is controlled by your Kernel. The second one is called the boot animation. Its specific to the Rom you are using.
If you wish, you can try some nice Boot Logos from this thread. This thread on the other hand, has some nice custom bootanimations and other media. This other thread has Google Play Edition Animation. This one has a Moto X Animation in Google Play Edition Style.
You also have a choice of a complete theme by @bytethegroove as well.
Themed Keyboards -
As the name states, this mod offers color themed Google Keyboards.
Reserved
Exactly and everything I needed. Thanks! :good:
Smitelight said:
Exactly and everything I needed. Thanks! :good:
Click to expand...
Click to collapse
I am still building this. Long ways to go before I am complete.
Looks like there's a kernel for you to put in here now.
Sent from my XT1056 using Tapatalk
MichaelMcEntire said:
Looks like there's a kernel for you to put in here now.
Click to expand...
Click to collapse
Guess I do... As I said haven't gotten there though.
Edit - Completed building. Let me know if I am still missing any Rom or Kernel.
The unit does not meet the expectations of the screen as in the expansion of the budget in 2012. Complete failure.
To each their own I guess.
So.... Is the download for VZW also for the Sprint Moto X?
Sent from my XT1056 using Tapatalk
dmonleo said:
So.... Is the download for VZW also for the Sprint Moto X?
Click to expand...
Click to collapse
It is on Case by Case basis. Best confirm on the individual threads.
Perseus71 said:
It is on Case by Case basis. Best confirm on the individual threads.
Click to expand...
Click to collapse
Yeah... That's what I'm trying to determine. The OEM site has info... but saw only AT&T and VZW. I still have 12 days to return it...lol...
Update:
Well... I'm still on stock, not rooted.... guess I'm procrastinating.
Sent from my XT1056 using Tapatalk
Moto X Developer Edition
Just got the Moto X Developer Edition GSM version last night. Is this already rooted? Or do I still follow the instructions in other posts to root it ? If so which APK do I use ? I am using a SIM card from TMobile. Thanks in advance.
The bootloader would be unlocked or user unlockable. You will have to root on your own.
Sub'ed.
Perseus71 said:
The bootloader would be unlocked or user unlockable. You will have to root on your own.
Click to expand...
Click to collapse
Yes you need to root, after unlocking your boot loader flash twrp recovery and it will ask if you want you system to be rooted
Sent on my Gummy running Lenoto X
Original post needs changing. It looks like AT&T and T-Mobile versions are using the same frequencies, which is only correct for
GSM/GPRS/EDGE.
======
4G LTE bands for T-Mo (which is the same as Developer Edition for GSM networks, 1053): 700/AWS/1900MHz (B17/B4/B2)
3G UMTS bands for T-Mo (which is the same as Developer Edition for GSM networks, 1053): 850/900/ AWS/1900/2100 MHz with HSPA+ up to 42 Mbps (B5/B8/B4/B2/B1)
Source: http://www.motorola.com/us/Moto-X-Developer-Edition-GSM-Networks/moto-x-developer-edition.html#product-specs
=======
4G LTE bands for AT&T: Bands 2, 4, 5 and 17
4G HSPA+ with enhanced backhaul
3G UMTS bands for AT&T: 850/900/1900/2100MHz
Source: http://www.att.com/shop/wireless/devices/motorola/moto-x-white.html
=========
As you can see comparing with AT&T T-Mobile is lacking LTE Band 5. I read that AT&T is not using it in USA at the time, so not sure of how important it is.
[Not sure] On the other hand, for 3G UMTS T-Mobile version has AWS which AT&T doesn't. Unless 4G HSPA+ with enhanced backhaul for AT&T is the same as AWS in T-Mobile.
By stating, "AT&T and T-Mo", I had indicted that they both have same GSM frequency. Op has never stated that the two have different set of frequencies. Both carriers indeed do have a different implementation of HSPA+ protocol with T-Mo's speeds supposedly higher due to compression. Since ATT had rolled out 4G LTE ahead of T-Mo, they didn't focus on H+ like T-mo.
Related
The Complete Wildfire Index (Root/S-OFF Guides/ROMs/Kernels/Radios/RUU/Recoveries/Themes)
This thread has 2 Posts, and is categorized as following. You can scroll down to the Point you are looking for.
Post 1:
Getting Root / S-OFF to your Wildfire. A Short overview and Guide
Custom ROM List
Post 2:
Custom Kernels List
Radio (Baseband) List
RUU List (ROM Update Utility - Getting back to stock)
Custom Recoveries (ClockWorkMod)
Themes List
Misc tweaks / hacks
1: Rooting / S-OFF'ing your Wildfire
-- Rooting your phone is essential if you wish to install Custom ROM's, Custom Apps2SD Scripts, Overclock, install Root only apps etc. Note: Rooting will void your warranty, but, you can use an RUU (Refer Pt 5) to restore back to your stock ROM. Rooting essentially consists of 2 parts - Pushing a custom Recovery like Clockworkmod (Essential), and, installing the SuperUser app.
AlphaRev X Public Beta is now available. You can now get S-OFF and root, on all the newer HBoots as well. Means, now, irrespective on which Wildfire you are on, you can get S-OFF and root!Link HERE
UPDATE (03/08/2011) - AlphaRev X is now called Revolutionary. The Process stated below remains the same, only the website and the name has changed. The new Website can be accessed HERE
A Short FAQ and Guide for AlphaRev X (Revolutionary):Q: First and foremost, what is S-OFF?
A: It's the disabling of the SecuFlag, a security implementation by HTC. When your phone is S-OFF, you essentially have "complete control" over it. Advatages stated below.
Q: I am rooted already. Do I need S-OFF?
A: Depends. Advantages of S-OFF are writable /system partition, so you can perform many modifications directly on your Wildfire, without using ADB. Also, you can change your Splash screen. (It is the White screen with Green HTC Text which comes immediately after power on). Another major advantage is enabling of Fastboot (On AlphaRev X only). However, it is not "essential" that you got to have S-OFF.
Q: Is the warranty void?
A: Yes, as is the case with rooting and installing Custom ROMs, Warranty IS void. But, there are ways to get back to a stock configuration. Refer the next question.
Q: How do I revert back to S-ON?
A: It's now possible! You will require Fastboot, and the Stock HBoot (a nb0 file) from an RUU. The guide for the same can be found HERE
Q: Ok, I am interested! How to I go about it?
A: Visit the website HERE. Download for your respective platform. Short How - To below:
Q: Which HBoot version do I have? Which versions does AlphaRev X support?
A: To get your version, Power off your phone. Then hold Vol Down + Power Key, this will open HBoot menu, and your version will be written on the first line. AlphaRev X only supports HBoot 1.01.x at this point of time, and not 0.80x. So, if you are on 0.80, you will have to flash an official Froyo RUU (Point 5 of this thread), and continue from there. Pre - Requisites:- A phone on one of the newer HBoots 1.01.0001 or 1.01.0002. HBoot 1.01.0002 is no longer supported, and you will have to downgrade to 1.01.0001. Guide here
- ADB Drivers. Download HTC Sync, Install it and Uninstall it after that. We just need the drivers.
- Hacked HBoot Drivers. Guide Here
- Your Wildfire's Serial Number. (Printed on the Box and below the battery. It is a 12 digit Alphanumeric number, which normally (not necessarily) begins with HT0 (That's a Zero))
- USB Debugging ON. (Settings > Applications > Development > USB Debugging)
- When you connect your Wildfire to your PC, make sure it is in "Charge only" mode. The Actual Process:- The actual process is pretty much self explanatory. After you download the program, simply run it. It will detect your Wildfire, along with its HBoot version, (If drivers are installed properly. This process doesn't take time at all), and perform the patching of the HBoot. The entire process takes about 1 minute at most. If it gets stuck there is some problem somewhere. If it states Success at the end, that's it. Your phone is patched and is now S-OFF.
- Here's a video tutorial on how to get S-OFF and install a Custom recovery using Revolutionary. (Courtesy theunlockr)
http://theunlockr.com/2011/08/02/ho...android-phone-using-the-revolutionary-method/ - WARNING - Some reports by members suggest that after S-OFF'ing with AlphaRev, they encounter various issues, on the Stock / HTC Sense based ROMs. You will lose the ability to use HTC Setup, HTC Wallpapers and HTC Scenes. Everything else works as intended though.
- UPDATE - There is a Fix for it. Head over here: Fix for Sense 2.2.1 after S-OFFPotential Problems:- Stuck at Detecting Device - Drivers are not installed properly. Refer the Pre-Requisites section.
- Stuck at Booting at Fastboot or Process 2 - You are possibly on HBoot 1.01.0002. There are some versions of the latest HBoot which is not supported by AlphaRev X, and you will have to downgrade it. IEF of the AlphaRev X team has written a great guide for the same, which can be accessed here
- Unknown command - Similar to above. You are probably on HBoot 1.01.0002 and will need to downgrade.
- Wrong Beta Key - Just what it says, you are reading it wrong. Majorly, there is confusion between I (Capital I) and l (small L). Re-read your beta key. Also, make sure the values you have entered into the website are correct, especially your Serial number. Another way to rectify this is redownloading the executable from the website, which fixed it for many users. (Your key should still be correct though)
- Stuck after Beta Key successful - Uninstall HTC Sync. This seemed to fix the issue for me personally.
- Anything else - First, Downgrade to HBoot 1.01.0001, if not already done so. Guide here. If it still doesn't work, I am at the end of my limited knowledge. Contact the AlphaRev X team, they will put you on the right track. Link Here (IRC Link)
What after S-OFF?
Great, your phone is now S-OFF, meaning with a completely unlocked bootloader. However, before you get to flashing a Custom ROM or modding, you will have to install a Custom Recovery (like Clockworkmod). Get your needed version of Clockworkmod from the second post, and follow one of the methods to install it.1) Via Revolutionary Itself - Revolutionary now asks you after S-OFF'ing your device whether you would want to install a Custom Recovery or not. If you select Yes, it will automatically download the latest Clockworkmod Recovery and install it on your Wildfire. It's definitely the easiest way with absolutely no hassles. But, if it fails for you, the 2 alternatives are stated below.
2) Via Terminal Emulator - Guide Here. If you get an error "flash_image: Not Found", follow Steps 1-5 from Here, then, back to the original (first) link. Pushing of flash_image is a 1 time process. You need not repeat it everytime.
3) Via Fastboot (Needs AlphaRev / Revolutionary S-OFF) - Guide Here. Refer the part called "To install Clockworkmod after Revolutionary". Can't understand Step 6? Screenshot here: (My fastboot .exe is in D:\Android\android-sdk-windows). Link to Image
4) Via Unrevoked (No Pre-Requisites. Works on S-ON / S-OFF devices) - Guide Here
I want to install <Insert ROM Name here> What next?- After you have performed all of the above steps, Refer this thread by 42turkey's for a very detailed explanation on what to do to install Custom ROMs. Link Here
(NOTE -Follow that Guide from Part 3 onwards. Part 1 and 2 are already performed in the above steps. Thus, you do not need to use Unrevoked) =================================================
Root Guides:
Only applicable if you are on HBoot 0.80x (i.e. Android 2.1 Eclair)
[GUIDE] Turkeys' Ultimate Guide to Root Wildfire v42.1.2 (Root ROM A2SD & Unoot!)
==================================================
2: ROM List: (Sorted by Last Update Date)
Short Primer on Wildfire ROMs:
AOSP stands for Android Open Source Project. AOSP ROM's are essentially pure (or bare) Android ROM's - The way Android was originally developed, and "intended" to be experienced.
Sense ROM's are the ones which are based on the HTC Sense UI. The Sense UI adds various functionalities like a smart dialer and contacts app, better social network integration, HTC Widgets etc.
There is no ROM which is "best". ROM choice is extremely subjective, and, what is the current favourite, may not appeal to you. Hence, use your discretion, read the threads, and test a few before settling on your personal favourite.
ProTip - If you are modding your "significant other's" (colleagues, girls, wifes, mother-in-laws etc) Wildfire, (Or anyone, who isn't much inclined to tech / smartphones in general) , it is recommended to stick with Stock / Sense based ROMs
******************************
1: Android 4.0 Ice Cream Sandwich ROMs
******************************
WARNING - Please read the thread carefully before flashing it, so you know what works and what doesn't. These are Test ROMs, and, may not be suitable for daily usage yet.
A) AOSP Based "Original Development" / Source Built ROMs:
2012-09-20 - CyanogenMod 9.0.0 Unofficial Test Builds by arco68 / ErwinP
B) AOSP Based Derivative / "Based-On" ROMs:
2012-11-11 - MiniCM9 v1 by jordfaz
2012-10-29 - MIUI V4 2.10.26 Beta by tathanhlam66
2012-10-16 - ICS LiGux v4.1 byelia222
2012-10-16 - Paranoid Android 2.1 by elia222
2012-10-14 - HTC Hero CyanogenMod 9 4.0.4 Port by Damag3
2012-10-08 - Xperia Lovin Ice Cream v1.1 by tathanhlam66
2012-10-05 - MIUI V4 2.9.21 Unofficial SnapSeries by Steriod™
2012-09-30 - KoolMIUI 2.6.8 V1.1 by KoolSavas95
2012-09-27 - MIUI V4 1.0 by Pator57
2012-07-13 - AOKP Milstone 6 Port by tathanhlam66
2012-03-04 - MIUI V4 2.3.2 Beta 1 by stelios97
2012-02-25 - SplashICS v0.6 by jamal2367
******************************
2: Android 2.3 Gingerbread ROMs
******************************A) AOSP Based "Original Development" / Source Built ROMs:
2012-11-10 - CyanMobileX Build 1 by keyur2maru
2012-06-16 - CyanogenMod 7.2 Final(GWK74/2.3.7) byarco68 / HCDR.Jacob
2012-03-15 - CyanogenMod-7 Nightly Builds (GWK74/2.3.7) by arco68 / HCDR.Jacob (Local Builds byErwinP / cobje)
2012-01-25 - Abtekk's Custom ROM v3 (2.3.7) by abtekk
2011-12-21 - DevNull (GRJ90/2.3.5) and Oxygen 2.3.2 (GWK74/2.3.7) Test Builds by schiznik
2011-11-11 - Stock AOSP 2.3.7r1 GWK74 with 2.6.35.14-nFinity by xdbg
2011-10-10 - CyanogenMod-7.1.0.1 for Wildfire by arco68 / HCDR.Jacob
2011-07-22 - Wild Ginger GB 2.3.4 by h4oxer
2011-05-28 - Whisper by ben1066
B) AOSP Based Derivative / "Based-On" ROMs:
2012-11-15 - MIUI GB V3 by jordfaz
2012-11-12 - MiniCM7 v1 by jordfaz
2012-11-07 - COSG3 v.30SC by nino90
2012-11-05 - CZRom by Rydlis
2012-09-05 - 3v1lut10n by Damag3
2012-08-17 - LeWaOS v14 by elia222
2012-08-12 - Lovin Ice Cream 1.0 by tathanhlam66
2012-08-10 - Lezo Buzz 1.8.3 by tathanhlam66
2012-07-26 - LiGux v8.1 Final by elia222
2012-07-24 - KoolSony HD v2.1 by KoolSavas95
2012-07-07 - MokeeOS v2 by slymobi
2012-06-28 - Kool-Elia-JoyOS v3.0 by Various Devs
2012-06-19 - ShenduOS by tathanhlam66
2012-05-16 - MIUI Buzz Beta 7 by hacktrix2006
2012-05-12 - Lezo for HTC Wildfire by tathanhlam66
2012-04-29 - Galaxy Nexus (ICS Style Mod) by josemaesra
2012-03-06 - SplashMOD v2.0 - (2.3.7) by jamal2367
2012-02-23 - High-Voltage Three by george1234567890
2011-11-30 - ZeroROM v1.0! by revan1993
2011-11-19 - IceCreamBread™ v1.1 - (2.3.7) by mrweqa
2011-10-23 - LotusMod S 1.0 Final by kaassaus
2011-08-13 - JokerGEN 1.0 Beta by emiliano7
2011-07-29 - LotusMod V1.3 Beta 2.0 (2.3.4)(A2SD+)(HCDR.Kernel) by jonas2295
2011-06-22 - Wild Eye 1.0 by migueldemon / anonimo95
2011-06-01 - Ruymanca V7.1 Pain Ass by ruymanca / anonimo95
2011-05-11 - Ginger Yoshi 1.1 (2.3.4) by stevendeb25
C) Sense Based:
NOTE - All ROM's below are experimental. Please read the thread carefully before flashing it, so you know what works and what doesn't.
2012-06-13 - KoolSense v1.7.3 (Sense 2.1 on Gingerbread 2.3.3) by KoolSavas95
2012-06-03 - buSyBuZz v1.0 (Sense 3.5 on Gingerbread 2.3.7) by benjamingwynn
2012-03-25 - Sense 3.5 Beta 1 by Various Devs
2011-10-19 - SenseOnFire v0.4b (Sense 2.1 on Gingerbread 2.3.3) by VigiDroid
2011-06-08 - SFM 1.1 based on Salsa (Sense 2.1 on Gingerbread 2.3.3) by evilisto
*******************************
3: Android 2.2 FroYo ROMs
*******************************
- Any 2.2 (or below) ROMs will need Clockworkmod 2.x to flash it. Attempting to flash it in Clockworkmod 3.x will give you an error that Amend Scripting is deprecated by Google in Cupcake and is no longer supported.
- To rectify this, you may "permanently" go back to Clockworkmod 2.x by using Unrevoked / Fastboot
- Or, as a "temporary" solution, Download ROM Manager > Open it > Select Install Clockworkmod Recovery > Then Select Reboot into Recovery within ROM Manager. This will open 2.5.0.7, allowing you to flash 2.2 ROMs. This version is over and above your existing 3.x/4.x version
- Or, another temporary fix is to download the attachment, flash it, and proceed. Repeat everytime you need Clockworkmod 2.xA) AOSP Based:
2011-07-05 - WildMix 1.0 by anonimo95
2010-12-12 - CyanogenMod 6.1.0 (Stable) for HTC Buzz (Wildfire) by HCDR.Jacob
2010-12-06 - UtmostROM_2.0.8a by UtmostMick0
B) Sense Based:
2012-10-19 - kwbr Wildfire 4.3.1 by kwbr
2012-09-26 - RemPuzzleRom 2.81 by kylon
2012-08-24 - Arsenal 1.1 by ontheflames
2011-03-21 - DK Custom Froyo v4.7 by Deep-Knight
2011-08-23 - Steam v1.0 (Supports Arabic) by trippinz
2011-08-18 - AeroFire_v0.5 (ROM/Theme) by JoeyDelp
2011-06-11 - JokerDroid 4.2 by emiliano7
2011-03-23 - Android Freedom Wildfire 2.2.1 (Arabic sense) by moni69
2011-03-21 - InsertCoin v0.2 by baadnewz
2011-02-06 - DS Version 7.a by daddyspud
2011-01-23 - Leaf r3 by doomed151
2011-01-07 - SUnAaBh v1.1 by warriorvibhu
2010-12-30 - WildPuzzleROM 2.2.1 v0.6 Light (Remake) by jan27t
2010-12-22 - Blazing Yoghurt 1.0 bynobloat
2010-12-10 - 2.22.405.1 r1 - MoDaCo Custom ROM with Online Kitchen by paulobrien
2010-12-xx - WildPuzzle 2.2.1 v0.6 by danne_jo
C) Hybrids:
-- Hybrid ROM's are, at their core, Sense ROM's, with various Sense Features / Apps removed and replaced with AOSP ROM's.
2012-02-04 - StockMOD 1.0 by saranhai
2011-03-09 - ImPrOS v1.2 by h4xoer
2011-02-22 - Stock Froyo + HTC Hybrid V6 by HewGBalls
2: ROM List (Contd..)
*******************************
4: Android 2.1 Eclair ROMs
*******************************A) AOSP Based:
-- None
B) Sense Based:
2010-11-16 - 1.37.405.1 r1 – HTC Wildfire Stock ROM with Online Kitchen by paulobrien
2010-09-19 - VIBES v1.6 by warriorvibhu
C) Hybrid:
2010-09-20 - Vibes LITE v2.0(Most Bloat Removed) by warriorvibhu
*******************************
4: Experimental ROMs
*******************************
-- Warning - These are experimental ports, with many non working functions. It is recommended to read the entire post carefully and perform a complete system backup before you attempt to flash these ROM's.
2012-10-31 - CyanogenMod 10 Build 1 (Android 4.1 - Jellybean Source Build) by jordfaz
2012-07-24 - CyanogenMod 10 RC0 (Android 4.1 - Jellybean Source Build) by danibosev
2011-02-28 - Honeyfire Alpha 2 (Android 3.0 - Honeycomb SDK Port) by ben1066
==================================================
3: Kernel List: (Sorted by Last Update Date)
-- In it's very basic terms, allows the software to communicate with hardware
-- A custom kernel is a must if you intend to overclock. The stock kernel's don't allow it.
2012-05-03 - [GB/ICS] Sympfinity Beta 4 [SIO-V/R-BFQ3][SavagedZen-LagFree-SmartAssV2] by Sympnotic
2011-11-21 - InfinityPLAY for CM7/AOSP by KeiranFTW
2011-10-14 - [No WiFi N][Default 518][Fix Hotspot] Kernel based on Arco's nFinity & HCDRJacob's by johnseen99
2011-09-07 - nFinity 2.6.35 (Kernel included by default in CM7 - Do NOT use on the Stock ROM) by arco68
2011-06-18 - nFinity 2.6.32 by arco68
2011-05-23 - [CIFS][WiFi Sleep Fix][Multicast][NFS][AOE]Kernel based on HCDRJacob's/Arco's nFinity kernel source by s7mx1
2011-01-29 - [KERNEL][OC/UV][BFQ][AUFS][FTW][GPL] HCDR.Kernel v4.2 || Flash to any ROM by HCDR.Jacob
==================================================
4: Radio List:
-- Radio is the lowest software layer of any phone which controls its GSM Functionality, BT, WiFi, GPS etc.
-- These only work with Clockworkmod 2.5.x. To get Clockworkmod 2.x when you have a newer version, refer the note under Android 2.2 (FroYo) ROMs.
-- Make sure you have sufficient battery charge and do not interrupt the flashing process.
-- Warning: - Do NOT Flash any of these Radio's if your Wildfire is not a standard GSM HTC Wildfire A3333, or, it uses any special frequency bands. (eg: 850 MHz). You will lose that particular frequency then,
Radio_13.55.55.24H_3.35.20.10
Radio_13.53.55.24H_3.35.19.25
Radio_13.53.55.24H_3.35.15.31
==================================================
5: RUUs:
-- RUU Stands for ROM Update Utility. You use a RUU whenever you wish to get back to a completely Stock ROM, as it was out of the box.
-- Normally EXE Files, some RUUs which update the bootloader and prevent rooting have been now distributed as a Flashable ZIP. So, you do not lose the ability to root, and, still can get back to Stock ROM's.
A) Safe Flash ZIP Files:
2010-12-18 - Safe Buzz_Froyo_HTC_WWE_2.22.405.1 | No Hboot | No Radio | No Rooted & Rooted by McSpee
2010-11-28 - Repack of the chinese RUU, Android 2.2 Froyo Rooted Chinese apps removed by Andrey765
B) EXE's
Shipped ROM's
HTC Wildfire Shipped / Stock ROMs Collection
-- All RUU's are well over 100MB. Make sure you get the complete file.
-- Get a Customer Error ID 131? You need a Goldcard. Guides can be Googled.
==================================================
6: Custom Recoveries:
-- The stock custom recovery obtained after rooting with Unrevoked is 2.5.0.1, and, the one obtained after using Revolutionary (Provided you selected Yes to installing Custom Recovery) is v4.0.1.4
-- To get rid of the offmode charging bug (Which prevents the phone from being switched on normally when charged in a switched off condition), you will need Clockworkmod 3.1.0.2 or newer.
-- Warning - Installing CWM 3.x/4.x will prevent the installation of Radio's and Sense based ROM's (Amend Scripting not supported). Use CWM from within ROM Manager to rectify this. Or, reinstall v2.5.0.7 from the link given below, Or, flash the attached file (update1.zip from the previous post). Also, Amon RA's Recovery is not officially supported. It's experimental.
How to Install a new Clockworkmod Recovery Image?
There are 4 basic ways:
1) Via Terminal Emulator (Needs S-OFF) - Guide Here. If you get an error "flash_image: Not Found", follow Steps 1-5 from Here, then, back to the original (first) link. Pushing of flash_image is a 1 time process. You need not repeat it everytime.
2) Via Fastboot (Needs AlphaRev / Revolutionary S-OFF or HTC DEV Unlocked Bootloader) - Guide Here. Refer the part called "To install Clockworkmod after Revolutionary"
3) Via PC49IMG.zip Process (Needs S-OFF) - Download anyone of the PC49IMG ZIP file of the recovery you wish to install, place on your SDcard, and reboot into HBoot Mode (Power Off, then Vol Down + Power Simultaneously). It will detect the file, and ask to install. Simply select Yes. If you wish to install another version which isn't present below, simply get the IMG file of the recovery version you wish to install,and replace in an existing ZIP. (Without Unzipping)
4) Via Unrevoked (No Pre-Requisites. Works on S-ON / S-OFF devices) - Guide Here
A) Clockworkmod 6.x
ClockWorkMod v6.0.1.4 + Aroma Installerhttp://forum.xda-developers.com/showthread.php?t=1014498
B) Clockworkmod 5.x
ClockWorkMod v5.0.2.8
ClockWorkMod v5.0.2.7
ClockWorkMod v5.0.2.0 - Click Here for PC49IMG ZIP
C) Clockworkmod 4.x
ClockWorkMod v4.0.1.4
D) Clockworkmod 3.x
ClockWorkMod v3.2.0.0
E) Clockworkmod 2.x
ClockWorkMod v2.5.0.7 - Click Here for PC49IMG ZIP
F) Others
Amon RA 2.0.0
==================================================
7: Themes:
-- There is already a thread created by BodenM for this purpose. Includes Sense based, CM6 (Admittedly few) and a few CM7 ROMs. Refer the link below:
Complete Theme List for Wildfire
-- Here is another Theme List for the Theme Chooser App included in many Gingerbread AOSP ROMs like Cyanogenmod 7, Ginger Yoshi, Ruymanca etc. MDPI and MDPI/HDPI Themes will work pretty good on the Wildfire, and, HDPI Themes may work, so its a hit or miss. Check this awesome post by maxpower47 here:
Theme Chooser Themes
==================================================
8: Misc:
[Script][A2SD]Darktremor 2.7.5.3 Beta 04 [Buzz] (01/29/2011)
-- True Apps2SD that makes use of an EXT Partition on your SD Card to move apps completely to it.
HTC IME for Tattoo/Wildfire (Working with Froyo and Gingerbread)
-- Miss the HTC keyboard on AOSP ROMs? The one posted here works perfectly, including the different versions that HTC offers - Compact QWERTY, QWERTY and Phone Keypad
[RLZ][v7.2.2] Patched Market (latest v.2.2.11 / Froyo & Gingerbread)
-- Allows non compatible devices on the Android Market to be seen and downloaded. (No, Paid apps will remain paid). The latest update can be found here
Reverse Tethering Wildfire --> Internet Pass Through
-- Allows you to use your computers / laptops internet on your mobile via USB. Does not work on Android Market out of the box though.
Custom MTD Partitions for the Wildfire (Increase Internal Memory Size)
-- Reallocate memory from your internal ROM in such a way to as to increase your internal memory size for installing apps to upto 320MB. This removes the needs for Apps2SD Scripts and gives you a potentially more stable device. Needs S-OFF using Revolutionary
AGPS Patch for the Wildfire v3.1 and 3.2
-- This is a patch developed by XDA user crypted for various devices. The benefits claimed are a much improved lock on time, and a connection to a greater number of satellites than before.
Dual Booting on the HTC Wildfire
-- Just what it says. This guide teaches you how to have multiple ROMs on your Wildfire and dual boot between them using an app called Boot Manager
This thread is alot better than the last one. The big red Rom type is really helpful. Thanks for taking the responsibility of continuing such a great thread.
@3xeno...Nice work this is a great and useful thread!
You should list both arco68 and HCDRJacob as the devs for CM7. Both are official maintainers. Looks odd with Arne on the nightlies and Jacob on the RC thread.
Edit: Oh and you might want to change all the "ROM's" to "ROMs", looks odd Same for ZIP's and maybe RUU's
Otherwise nice thread. Might want to make the HBOOT warning bigger and red.
one of the useful threads related to wildfire. keep up the work
Yeah, the other thread was great, but this is awesome!
Thank you for your work!
can we expect here, the froyo RUU for UK H3G .
can we use any other above mentioned froyo RUUs for wildfire with UK H3G network.
bharatgaddameedi said:
can we expect here, the froyo RUU for UK H3G .
can we use any other above mentioned froyo RUUs for wildfire with UK H3G network.
Click to expand...
Click to collapse
Why would you want to use a Froyo RUU? Anyway, this thread is supposed to serve as an index. If anything is available, it will be listed.
That said, Shipped ROMs does have the Froyo Update ZIP and Eclair RUU for H3G UK. Have a look.
RUU_Buzz_H3G_UK_1.16.771.2_Radio_13.45.55.24_3.35.15.31_release_131501_signed.exe
OTA_Buzz_Froyo_H3G_UK_2.33.771.1-1.26.771.1_release_163490jq8do89dc3y83p6w.zip
I have a question, I'm selling my wifes Wildfire. And the buyer wants a stock, rooted rom. No i found RUU_Buzz_Froyrange_ES_2.34.75.1_Radio_13.55.55.24H_3.35.20.10_release_163758_signed_rooted-dannejo
Can I use this for my Wildfire?
Sandertenty said:
I have a question, I'm selling my wifes Wildfire. And the buyer wants a stock, rooted rom. No i found RUU_Buzz_Froyrange_ES_2.34.75.1_Radio_13.55.55.24H_3.35.20.10_release_163758_signed_rooted-dannejo
Can I use this for my Wildfire?
Click to expand...
Click to collapse
Of Course. BTW, there are other rooted Stock ROM's also, like the 2.22.405 WWE one, which I have linked above. So you can use that as well. The Orange ROM has some Generic Orange Stuff I think, so you would be better off using a WWE ROM.
Thank you very much!
Acros Kernel is not added ?
ShyamSasi said:
Acros Kernel is not added ?
Click to expand...
Click to collapse
Doesn't it break some functionalities in Sense ROMs? Atleast that's what I read when someone asked it.
Anyway, I'll recheck, and if it works fine across all ROMs, I'll add it. Need to find it's download link though.
3xeno said:
Doesn't it break some functionalities in Sense ROMs? Atleast that's what I read when someone asked it.
Anyway, I'll recheck, and if it works fine across all ROMs, I'll add it. Need to find it's download link though.
Click to expand...
Click to collapse
Yeah, it isn't compatible with anything outside of the later CM7 nightlies / RC4 / stable. It breaks USB functionality in anything else.
Similarly, only that kernel and its derivatives work with CM7 builds. Using the HDCR.Jacob kernel family likewise break USB functions.
The Wildpuzzle 2.3.3 is working right now*
it will be ready for download soon!
melvinchng said:
The Wildpuzzle 2.3.3 is working right now*
it will be ready for download soon!
Click to expand...
Click to collapse
Wildpuzzle 2.3.3??? Cool! Where to download it?
thunderskain said:
Wildpuzzle 2.3.3??? Cool! Where to download it?
Click to expand...
Click to collapse
I have listed it under the Gingerbread Sense ROMs list. You can find the relevant details to make it boot starting from Page 17, if I am not mistaken.
CM 7.0.3 Stable is out, is it good to upgrade from 7.0.2 ? whats r the changes in 7.0.3 ? 3xeno , you haven't upgraded yet right?
iNCEPTiON2010 said:
CM 7.0.3 Stable is out, is it good to upgrade from 7.0.2 ? whats r the changes in 7.0.3 ? 3xeno , you haven't upgraded yet right?
Click to expand...
Click to collapse
Nope, still on 7.0.2. Actually, I am waiting for 7.1 Bit lazy to upgrade ROMs on a regular basis, and more so, because I always believe in fully wiping my device before flashing a new one.
If you are looking to upgrade, look at the newer nightlies rather than 7.0.3, because they use the latest Gingerbread build and a newer kernel.
The official changelog is:
This update contains a bug fix for our update notification system, as well as an important security fix. It is recommended that all users running a version of CyanogenMod prior to 7.0.3 update to this release. You should not install this update if you are already running a recent nightly build, only if you are coming from 7.0, 7.0.2, or 7.0.2.1.
{
"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.
All developments are carried out thanks to donations on Purchase of these or other devices
thank
Please do not copy files to other file shares
the project is under constant development and refinement
Project name [ROM] Moto X L!te FW LPA23.12-15.5.EU.ML
Tagline Faster Lighter Economical
for XT1052/1053/1058 - 2G/3G/LTE
and only GSM XT1049/1050/1056/1060/ - 2G/3G/LTE (for CDMA use menu *#*#4636#*#*)
SYSTEM Firmware LPA23.12-15.5.EU.ML Multilingual
- firmware Deodex - allowing resources using modifiers such GravityBox apply all when firmware odex, it sometimes limited customization or going awry
- Launcher -4*5, no searche bar
- tzdata 2015f
- icudt53l last
- return "the gesture of the Jedi" (after installing the firmware of the old sensor /*** it does not threaten the phone)
- delete more apps FaceLock, MotoServices, Google Drive & Docs, Permissions and etc
- replaced by sound WirelessChargingStarted
- uppdate apps LatinIME, Migrate, Calendar, AudioMonitor, Moto, MotCamera, MotGallery
- Stagefright Fix
- removed a lot of the background services collect and send data on the type of phone DropBox, MotoCare, MotoConntect, Drive, FaceLock ... etc.
- add apps VendorApp ESFileManager, CCleaner
- added Russian, Ukrainian language
for Unloked Device
Install for Custom Recovery
Root not PreInstalled
Download there https://yadi.sk/d/jp8ykQqFindY8/MotoX/5.1.0
for Loked Device
5.1.0 for locked phones ready to be sewn LONG !!! 5.1.0 1.5 GB used by all, no matter what the new system weighs only 900MB ... the old system to be erased
Install for QDLoad9008
Root, BusyBox is PreInstalled
- Root SuperSU v2.46
- BusyBox v1.32.2
DISCLAIMER
Author is not responsible for totally bricked devices, broken arms, legs, plane crashes and your wife's cheating.
All actions taken is your own risk.
Instructions to install
You:
- shouldn't be afraid of Qualcomm HS-USB QDLoader 9008;
- do not change any files, pathes;
- can install drivers manually;
- need to install python-2.7.9 and pyserial-2.7.win32;
- unzipp _Rus_5_1_0_LPA23_12.XX.7_BL_V30.BE.rar to Cython27;
Method is dangerous, however gives results.
you must have firmware SU6-7 receiving is not in the form of an update (OTA) and stitched through the RSD Lite.
00 Flash *******_5.1.0-LPA23.12-XX.7_CFC.xml firmware
01 Unzipp everything to Cython27.
02 Run BLBROKE.bat.
03 After you got Qualcomm HS-USB QDLoader 9008, install drivers manually
04 Run RUN_Rus_Part**.bat. Parts 250 of system.
*** You can also run a file if you are sure that your phone can work 6-7 hours with the screen RUN_Rus_***_Full.bat
then repeat this step X times (the number of times equal to 6)
while (found next part) do
***
>> fastboot to hold 10 minutes that would have been charged a little phone
>> Run BLBROKE.bat.
>> Run RUN_Rus_***_Part**.bat. Parts 250 of system.
***
end
99 Turn device on. Now you have SU DEODEX PreRooted
Drivers, Soft there -> https://yadi.sk/d/p458Cy0XineRC
Scripts, ROM there -> https://yadi.sk/d/kxbxpTnziSg35/Moto X/5.1.0
Please do not copy files to other file shares
the project is under constant development and refinement
XDA:DevDB Information
[ROM] Moto X L!te FW LPA23.12-15.5.EU.ML, ROM for the Moto X
Contributors
CrashXXL
ROM OS Version: 5.1.x Lollipop
ROM Firmware Required: Android 5.1.0 LPA23.12-15.5
Version Information
Status: Stable
Current Stable Version: 1.00
Stable Release Date: 2015-10-19
Current Beta Version: 0.01
Beta Release Date: 2015-09-28
Created 2015-10-12
Last Updated 2015-10-21
So can I assume this is a stock based rom that has been debloated, optimized, and such but is fully functional as a stock Rom? I've been waiting to update the wife's X on account of all the reported troubles with the official lollipop update.
This firmware is the most clean and fast
It based on the stock, and includes all updates and patches
Hi!
First of all, thank you very much for your rom, the "jedi" gesture is back!
I checked the stagefright detector and it seems to be vulnereble to the "CVE-2015-6602" I asume is a new vulnerability and motorola haven´t patched yet.
I have installed the rom an hour ago and everything works as expected, so nothing else to report, if I find anything strange i will tell you.
Thanks again!
Iktor said:
Hi!
First of all, thank you very much for your rom, the "jedi" gesture is back!
I checked the stagefright detector and it seems to be vulnereble to the "CVE-2015-6602" I asume is a new vulnerability and motorola haven´t patched yet.
I have installed the rom an hour ago and everything works as expected, so nothing else to report, if I find anything strange i will tell you.
Thanks again!
Click to expand...
Click to collapse
stagefright was fixed in last update, so I would certainly expect this ROM to have that patch. also, I believe that this thread should be moved to the Development section, not in general. you may need a mod to help out.
"and only GSM XT1049/1050/1056/1060/ - 2G/3G/LTE (for CDMA use menu *#*#4636#*#*)"
So this could work on the Sprint network with a 1056?
please link to another server
Enviado desde mi Moto X mediante Tapatalk
May I know how often will you update?
What about the very serious glitch-bug on YouTube ? Is it fixed ?
Sent from my XT1052 using Tapatalk
the project will be updated as long as I have moto phone x1
applications such as YouTube, Chrome, and others I can not fix, maybe, I do not have the source code of the product
YES 1056 will work
Xposed?
wildblade64 said:
Xposed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed
CrashXXL said:
the project will be updated as long as I have moto phone x1
applications such as YouTube, Chrome, and others I can not fix, maybe, I do not have the source code of the product
Click to expand...
Click to collapse
Thank you for reply.
jco23 said:
stagefright was fixed in last update, so I would certainly expect this ROM to have that patch. also, I believe that this thread should be moved to the Development section, not in general. you may need a mod to help out.
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/ota-xt1052-firmware-update-5-1-10-10-t3221898
Above thread has screenshots of XT1052 with update and shows that the above vulnerability is not fixed yet. It's the only one thats not fixed.
---------- Post added at 07:05 PM ---------- Previous post was at 07:02 PM ----------
CrashXXL said:
the project will be updated as long as I have moto phone x1
applications such as YouTube, Chrome, and others I can not fix, maybe, I do not have the source code of the product
Click to expand...
Click to collapse
I'm sorry... I dont understand... Do these apps not work right now???
I want to try this ROM to get back to stock... I do not have a system to flash the stock files...
Please help me understand.
XT1049 on C Spire?
Do you think this ROM will work on XT1049 from C Spire? I also would like to use a stock based ROM.
I do not change third-party applications, such as YouTube, Chrome, and other Google search, wait for the update application from the developers (Google)
Sorry, I meant to say if this rom will have xposed built in. Thank you so much crash by the way, I'm assuming this will eventually work for xt1058 with locked bootloaders?
what is that?
the gesture of the Jedi
what is that?
On kitkat you could have your hand in front of the screen and it would display moto display, since the lolipop update, you have to hold your hand directly over the light sensor for a few seconds.
Hi! This is an index and guide about the Samsung Galaxy S4 mini plus i9195i
Rooting guide:
I downloaded Kingroot and rooted it there (even though it said not supported, it still worked). I then downloaded Super me and let it do it's magic (delete Kingroot apps and install SuperSU apps). It takes about 10 minutes. After 10 minutes, you can get your refund from the Play Store.
Xposed guide:
I downloaded the Xposed installer, went to install/update, and it all went smoothly for me. Other users reported boot loop, but my phone was fine, so don't blame me if you get boot loop.
Custom Roms:
KitKat ROMS:
CyanogenMod 11
Lollipop ROMS:
CyanogenMod 12.1
Marshmallow ROMS:
CyanogenMod 13
Nougat ROMS:
LineageOS 14.1
Oreo ROMS:
LineageOS 15.1
dotOS 2.4
Resurrection Remix 6.0.0
Pie ROMS:
LineageOS 16
Pixel Experience
Credits to @Danil_e71 for the development on our device
As far as my testing went, all these ROM's are pretty stable and that includes LOS 16. This device is not my primary device though, so I don't test as well as I used to. LOS 16 doesn't seem to have any major bugs. (I didn't even find minor bugs either, but again, I don't test properly.). You need the latest TWRP to flash it though.
Custom Kernels:
Custom kernel by alexax66 for stock ROM 4.4
.zip file (v 0.1.7)(Flash via recovery)
.tar file(v 0.1.7)(Flash via odin)
(v 0.1.7) Disc image file
Source
It works well, normal features work and it seems to make the phone work faster. I found that all kernel features do work, while there are a few bugs (I've come across 2: the alarm clock doesn't work and I can't search for mobile networks/ put new apns in). To make sweep2sleep work, you must insert
Code:
su
echo 1 > /sys/sweep2sleep/sweep2sleep
into the terminal after adding code to the build prop (this worked for me, but after a reboot it stopped). I installed first via TWRP official and then via Odin. I'm not sure if you have to do it that way, but I can assure you that if you do do it that way, it will work.
I would not recommend this kernel, due to its instability, although I did used to use it daily.
Custom kernel for stock ROM 4.4 by Danil_e71
https://forum.xda-developers.com/attachment.php?attachmentid=3778847&d=1465586157
I could not get WiFi working on this kernel.
Custom kernel for CM 11 by Danil_e71
https://forum.xda-developers.com/attachment.php?attachmentid=3778501&d=1465562842
Overclocks to 1.4 Ghz, and works well.
Custom Recoveries:
I am only listing the most recent versions:
CWM
flash via recovery (v 6.0.5.1) by @alexax66
flash via odin (v 6.0.5.1) by @alexax66
Disc image file (v 6.0.5.1) by @alexax66
Philz
flash via odin (v 6.59.0) by @alexax66
flash via recovery (v 6.59.0) by @alexax66
Source
TWRP
flash via recovery (v 3.1.0-0) by @Danil_e71
Stock ROM:
Here
Stock Kernel:
Latest stock kernel (Disc image file)
Stock Recovery:
Stock recovery (Disc image file)
Anyone else tryed this metod and can confirm that them devices is rooted ?
Zakariasz said:
Anyone else tryed this metod and can confirm that them devices is rooted ?
Click to expand...
Click to collapse
yeah I just rooted my device by installing the linked KingRoot apk. It failed the first try but I tried a second time and now it works
I don't have custom recovery, nor kernel nor Xposed framework yet though.
Stagefright-Official Rom
Hello,
just to say that I upgrade (odin flash) to last Official rom yesterday, find on sammobile:
Model GT-I9195I
Model name GALAXY S4 mini LTE
Country Netherlands
Version Android 4.4.4
Changelist 5332500
Build date Mon, 11 Jan 2016 11:42:16 +0000
Product code PHN
PDA I9195IXXU1APA1
CSC I9195IPHN1APA1
good news : all Stagefright detector are green !
exzemat said:
good news : all Stagefright detector are green !
Click to expand...
Click to collapse
What is Stagefright?
LoScienzo said:
What is Stagefright?
Click to expand...
Click to collapse
wikipêdia:
Stagefright is the collective name for a group of software bugs (or more specifically backdoors), that affect versions 2.2 ("Froyo") and newer of the Android operating system, allowing an attacker to perform arbitrary operations on the victim device through remote code execution and privilege escalation.[1] Security researchers demonstrate the bugs with a proof of concept that sends specially crafted MMS messages to the victim device and in most cases requires no end-user actions upon message reception to succeed, while using the phone number as the only target information.[2][3][4][5]
Sorry, but I have a stupid question:
Can I use the Netherlands-version also on devices that are used in other countries / with other carriers?
Bibabuzzel said:
Sorry, but I have a stupid question:
Can I use the Netherlands-version also on devices that are used in other countries / with other carriers?
Click to expand...
Click to collapse
Yes, you can, but I think if you wait, your country might come. They just (50 minutes ago) released one for region TPD here. I think I'm going to wait.
I use method described in the first post but with Super Sume v 9.1.9 and xposed installer from the first post and everything work like charm for the moment.
I've done it via same route, it was bit of a hassle for trying to find information about this exact phone. Nice compilation here. Thumbs up.
exzemat said:
Hello,
just to say that I upgrade (odin flash) to last Official rom yesterday, find on sammobile:
Model GT-I9195I
Model name GALAXY S4 mini LTE
Country Netherlands
Version Android 4.4.4
Changelist 5332500
Build date Mon, 11 Jan 2016 11:42:16 +0000
Product code PHN
PDA I9195IXXU1APA1
CSC I9195IPHN1APA1
good news : all Stagefright detector are green !
Click to expand...
Click to collapse
Are there any noticable differences in this update?
no other than more recent kernel build (11/01/2016) : more secure ...
I added a bunch of disc images of kernels and recoveries (no new releases ) I also added the newest stock kernel if anyone needs it. (Released 11 Jan 2016) Also, TWRP 3.0.0-0 is out for our device, links are there. Is anyone working on CM by the way?
Anyone flashed any of the stock firmware in the original post?
Mine came with the stock firmware from another country, and I would like to flash the one for my country to see if the cell phone signal is any better.
Should I bother?
BTW, will doing that trip the knox meter?
I tried to change Kingroot with SuperSUMe but can't do this, course can't brake Knox. I try to install SuperSU it also can't brake Knox. Wtf?
I need custom kernel without bugs for our i9195i.
I also can mention that the Rom for each country has special BB (baseband - drivers for radio module). But there is no any Rom for my country... So i have unstable signal...
---------- Post added at 05:02 PM ---------- Previous post was at 05:02 PM ----------
How to disable Knox?
There's a new official TWRP release (3.0.0-2) here , enjoy
Sent from my GT-I9195I
Update: Got a custom ROM fully working (with small bus where and there). Check the first post
DroidKing18 said:
Update: Got a custom ROM fully working (with small bus where and there). Check the first post
Click to expand...
Click to collapse
You've got a interesting thread here to stay up-to-date on info about our phone, but shouldn't you mention some credits to the guy(s) that found the cm11?
I think it's Chrisled2 talking about it on cyanogenmod-forum (i see he's active here also by the name of chrisled):
https://forum.cyanogenmod.org/topic/110203-gt-i9195i-supported/?page=2#comment-591554
There are mentions about problems with play store, and playing video files in browser.
But thanks again for keeping us up-to-date!
Could you maybe try and test the infrared-functions with the custom rom? I use it for my television and decoder.
bartiest said:
You've got a interesting thread here to stay up-to-date on info about our phone, but shouldn't you mention some credits to the guy(s) that found the cm11?
I think it's Chrisled2 talking about it on cyanogenmod-forum (i see he's active here also by the name of chrisled):
https://forum.cyanogenmod.org/topic/110203-gt-i9195i-supported/?page=2#comment-591554
There are mentions about problems with play store, and playing video files in browser.
But thanks again for keeping us up-to-date!
Could you maybe try and test the infrared-functions with the custom rom? I use it for my television and decoder.
Click to expand...
Click to collapse
I thought OyyO found it first but I wasn't sure. I would've given creds to the devs but they don't seem to be on this site, if they are, tell me, but I've only seen them on 4pda, a Russian site. The truth is that I didn't test it enough to notice all the bugs. I lost a lot of interest when I found that I couldn't put Xposed on
Sent from my GT-I9195I using XDA-Developers mobile app
Btw, there is a also TWRP 3.0.2 now so your links to the official builds are outdated - you may want to link directly to https://dl.twrp.me/serranoveltexx/
Hi,
So as many of you already knew - I'm working on porting CM13 onto my NU3001.
I has it on my desk table, so I could work on it during my days. (I have another NR3001 installed in my car)
I already made some work for our unit SW. This is quick screenshots. Sources based on xdAuto and CM13. This is a very BETA and many things not working for now.on.
Why? : When I realize than CyanogenMod 13 (6.0.1) works on my Motorola XT1080 better than stock - I start thinking of porting CM13 to our device. And when I have spare set - I start porting.
How? : I took easiest way - try to do not modify kernel a lot, instead adopt bionic and other libraries for out 3.0.36+ kernel.
Currently working staff (it is very beginning):
1. Recovery TWRP 3.0.2
2. CM13 (LineAge OS) booting.
3. Graphics working (there is some blinking present).
4. Wifi working
5. Android audio working
6. Bonovo Radio working
4. Most of the rest is on the way (GPS, BT, rest of Bonovo apps)
UPDATE_1:
I decide to do not stuck with CM 13 and switch to AOSP N release (7.0) (mostly because on my daily job - we also going to Android N, so it should be more familiar to me now)
Currently working staff:
1. Recovery TWRP 3.0.2
2. SELinux needs to be carefully ported (kernel part), cause starting from 7.0 is can not be disabled (as I did for CM13 to easy port)
During this port I will try to minimize inpact to AOSP release, so any future updates should be much more easier.
For you to understanding of amount of needed work - kernel already has 100+ patches on top of xdauto release. Approximate left about 250-300 patches to revise/port.
Android 7.0 port abandoned because of bigger and bigger amount of work need to be done to port SELinux on top of our outdated kernel.
UPDATE2:
I setup review build environment, so who want to look at NOT-FULLY-WORKING CM13 could download sources and binaries. I do not provide instructions how to flash it, because who wants to look and contribute already know hot to flash, and who doesn't probably don't really want this NOT-FULLY-WORKING CM13
UPDATE3:
So I finally managed to get functional networking. So now Wifi working, internet working, display working.
I starting to port all necessary items. No more 'hard' showstoppers so far.
New build (I believe it is build number 5) should be ready in an our on build server, so I could test it more fully.
UPDATE4:
Cause CyanogenMod is no more maintained - switched to it's successor Lineage OS 13.0, starting from build 8
UPDATE5:
Build number 15 has working audio + radio
UPDATE6:
Most of Bonovo changes ported, new build 20 ready.
This build contains zip file which should be flashable via twrp, but I not test it this way.
Issues remaining so far(most noticeable to me):
1. Display flickering (my suspect is to vsync/fence mechanism slightly changed in Android 6.0, need to investigate)
2. HW Volume buttons not working on device
3. No audio In
UPDATE 7:
Starting from build 23 following images available:
cm_rk3188-ota-XX.zip - update to use via TWRP
nu3001-la-cm13-XX-userdebug.tar.gz - build image for flash via command line rkflashtool under linux (full or partial flash)
rkflash_nu3001-la-cm13-XX-userdebug.zip - Full image to be flashed via PC GUI RK Batch Tool.
kernel_nu3001-la-cm13-XX-userdebug.tar.gz - just kernel with debug symbols for debugging purposes.
To just download sources:
repo init -u https://gerrit.nc.org.ua/manifest -b nu3001_cm13
If you plan to contribute - login to Gerrit with GMail, push your SSH public key, choose login name and then do:
repo init -u ssh://<user>@gerrit.nc.org.ua:29418/manifest -b nu3001_cm13
Builds will be available on Jenkins build server (login also via GMail, PM for access grant on current project stage):
https://jenkins.nc.org.ua/
1.5 GB folder on MEGA
4 files
mega.nz
Please do not spoof this thread with questions like "When?", I will try to post updates regularly in this message.
This thread created is mostly to exchange experience with this build once it is published (issues, TODOs, etc)
**Reserved **
First!
Second! Lol
I'm not a developer so unfortunately I can't contribute, but hopefully those who can will.
At the very least I can beta test when its a little more complete.
Android port system less complicated than the application Bonovo.app and MCU. Good luck and patience.
Black're a legend !!
Your project is great !!! see Android 6.0 on Carpad would be great.
Thanks for the great effort you make for all
Woooow great !!
Good luck
nice one, i hope a very important feature:
"that can be use apps, which require android +4.4.4, like lollipop"
I say that because android auto "stand alone" coming soon, so if will be possible install this app in the radio, we have android auto pure, ( not automate that is awesome but is not the same like original ), and maybe mp3 stuttering from usb can be solved in this rom.
keep up work!
Thanks for the sneak peak, looks promising. I'll gladly help sponsor a new device if you happen to brick yours. I love this headunit and how far the community has gotten in supporting it.
I want to buy NU3001 now, is there any way to get it?
vivacious said:
I want to buy NU3001 now, is there any way to get it?
Click to expand...
Click to collapse
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
---------- Post added at 01:48 AM ---------- Previous post was at 01:43 AM ----------
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
vivacious said:
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
Click to expand...
Click to collapse
I just put NU3001 to aliexpress search bar and found a lot of propositions, I think there should be available one.
Hi VBlack,
it's nice to know you're making progress on the new ROM CM13. All are rooting for you !! Your work would be wonderful !!
I have only one question:
With the ROM of XDAuto I found an annoying problem that occurs when i turn off and then relight the Carpad.
When the power back very often the Carpad car remains with black screen until i touch it with my finger.
I think the problem is somehow related to the USB ports.
Even with your ROM does this happen ?? When you turn on the car, the Carpad remains ever with black screen ??
Thank you!!
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Zaphod-Beeblebrox said:
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Click to expand...
Click to collapse
Nice to hear from you. Sure I will share. Current situation is next:
CM13 - no wifi (looks like netfilter from userspace not match netfilter from our outdated kernel), no selinux (completely disabled), and increased system partition to be able to add opengapps, twrp - works.
AOSP 7 - it is strongly rely on selinux, so i could not just disable it, and now I'm trying to merge new selinux with our old kernel...
So, i will upload CM13 in current state, and continue on aosp 7, if i fail with aosp 7 i will back to cm13. This is current plan.
Sent from my DROID MAXX using Tapatalk
Zaphod-Beeblebrox said:
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Click to expand...
Click to collapse
I update first post with sources and build information
@VBlack, you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
shatteredsilicon said:
@VBlack, you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
Click to expand...
Click to collapse
No, we have kernel sources, but our kernel version 3.0.36 and looks like nobody release Android kernel 3.14 or 3.18 for rk3188. 3.14 and 3.18 mostly used in Android M and N. So combining Android M or N with such outdated kernel is not a trivial task. Because of this incompatibility we currently have all networks issue on this CM13 project.
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
shatteredsilicon said:
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
Click to expand...
Click to collapse
You'd be surprised how many phones in the market use old kernels (3.0 is not too old for Android - it is about 2-3years off from active development).. But true is that Android kernel despite it's version less vulnerable than Desktop one, and has many fixes included (it is does not increase kernel version, like mainline kernel). Because of this it is generally hard to say which security issue will be there for sure. But on the other hand Android N and Android M has SELinux enabled, and Android N could not have it disabled. It is dramatically increase overall security of the system. But for the most of traditional Android user kernel exploits does not produce many harm - it is not a corporate server with sensitive information. And many of them used to obtain root on bootloader locked systems.
So generally for what I have in mind:
1. If succeeded just with CM13 - I have disable SELinux there - it is will be not less secure than original 4.x release - just system/google components will be upgraded, which allow us use modern UI features from Android M, and also adds more compatibility with new applications revisions.
2. If succeeded with AOSP 7.0 - SELinux will be enabled there, so we will have security addition on top of old kernel, which actually will increase security alongside allowing UI features from Android N.
So in any case it is very nice to have.