Database Info

[RC-FAQ] >> Frequently Asked Questions for Motorola Moto G [Updated : 2015/09/23]

[RC-FAQ] >> Frequently Asked Questions for Motorola Moto G [Updated : 2015/09/23]
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2] Motorola Moto G
{
"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"
}
[/SIZE]
Read Before Asking Please​
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
To Browse quickly the FAQ and find what you need, Ctrl+F is the key feature
You may search in Motorola help topics too​
Table of content :
FAQ part 1
General advices about debugging
Unlocking Bootloader
Rooting your device :
- Option 1, using SuperBoot [external thread, on MoDaCo]
- Option 2, using a customized recovery [external thread, on MoDaCo]
- Option 3, for 4.4.2 using SuperSU [external thread, on swedroid.se]
Useful Links
build.prop collection
Refer to :
@Perseus71 Ressource Guide for tech specifications, ROMs, Kernels, Root ...
@Mr hOaX Tips and Tricks thread for more Up-To-Date informations
@72off Android related terms and abreviations
@pinguijxy FAQ, for CM11 related issues.
THIS FAQ IS MADE FOR Moto G 'old' editions (NOT FOR 4G/LTE MODEL or 2d Gen [aka 2014])

FAQ​
[SIZE=+1]Q1: What are Moto G tech specs ?[/SIZE]The Motorola Moto G is named XT1032/XT1033/XT1034/XT1035/... aka Falcon
XT1028: Verizon US CDMA - 8GB/16GB
XT1031: Boost US CDMA - 8GB/16GB
XT1032: EU/Global GSM/GPe - 8GB/16GB. (GPe = Google Play edition)
XT1033: Brazil - 8GB/16GB (Colors Edition) (Dual Sim) + Moto G (Music edition) (Dual Sim) (16GB Only)
XT1034: US GSM - 8GB/16GB.
XT1035: Brazil - 8GB/16GB (Colors Edition) (Unconfirmed)
Moto G 4G/LTE aka peregrine : ==> /!\ Roms made for standard edition (non-4G) are not compatible with these devices!
XT1045: Moto 4G - 8GB
XT1039: Moto 4G - 8GB UK/EU
XT1040: Moto 4G - 8GB Brazil
Complete specifications available in @Perseus71 Guide or @Mr hOaX Tips and Tricks thread​
[SIZE=+1]Q2: What is the .................................................. .................................................. ....?[/SIZE][...]​
[SIZE=+1]Q3: Why doesn't the LED work ?[/SIZE]maybe you disabled LED on you older device (or it didn't even have one) setting up you google account disabled the LED on you new Motot G use Notification Light Widget From Motorola to fix this issue (more info)​
[SIZE=+1]Q4: How to access Fastboot?[/SIZE]Hold PowerButton and VolDown during boot.​
[SIZE=+1]Q5: How to unlock Bootloader?[/SIZE]Boot to Fastboot and follow this guide
or Motorola guide on Motorola's website​
[SIZE=+1]Q6: How do i get adb and fastboot drivers ?[/SIZE]For windows, follow this guide or this one
although, it seems Motorola Device Manager works ok for win7x86-32 (but not for win7x64-64?) i cannot answer this i'm under linux
other USB drivers if first method failed, source
For Linux, get fastboot files here also, adb and fastboot can be installed using repos for ubuntu-based distros packages needed are : android-tools-adb and android-tools-fastboot (android-tools-fsutils may be useful too)
eg:
Code:
sudo apt-get install android-tools-fastboot
[SIZE=+1]Q7: How to flash Stock Firmware?[/SIZE]For windows, follow this guide or this video
The above is for non-4G devices, for Moto G 4G version refer to this thread​
[SIZE=+1]Q8: How to Root my device ?[/SIZE]Until now,you first need to unkock your bootloader,
Option 1 : then follow this guide [original thread - on MoDaCo]
Option 2 : via a customized recovery [original thread, on MoDaCo]
paulobrien said:
The first method is recommended as it doesn't mess with the recovery. But the second is there as a backup.
Click to expand...
Click to collapse
==> Option 1 seems not to work properly for some users, in that case : Try Both.
After you get root, please read Q19​
[SIZE=+1]Q9: Why dosen't my .apk get installed manually?[/SIZE]
Until i get a better solution, here are some workaround :
Check you've enabled Unknown sources (settings>security>unknown sources)
If you did so, there are some workaround :
At the phone first set-up (you may need to factory-reset to get that) - When Motorola assistant asks for data safety (just before the Google accounts question comes up), don't click accept, but tap on "data safety guidelines" and tick both settings to off. Then accept.
Use adb :
Code:
adb install packagename.apk
Use google drive to download the app (gdrive has an antivirus scanner that checks the app, since then it is considered as "safe" for the device and is correctly installed
other workaround
[SIZE=+1]Q10: Where can i find a Custom recovery ?[/SIZE]
TWRP Recovery ported by @a1Pha
CWM recovery ported by @a1Pha
CWM Advanced Edition PhilZ Touch by @Phil3759
TWRP 2.7.1.0 by @TeamMex
[SIZE=+1]Q11: How to access bootloader?[/SIZE]- Via ADB :
Code:
adb reboot bootloader
- The hard(ware) way :
With the phone powered off, press the VOL DOWN KEY for 2-3 seconds then POWER key then release.
The device will display different BOOT OPTIONS
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
[SIZE=+1]Q12: How to access recovery?[/SIZE]
using terminal, if the device is already rooted
Code:
su
reboot recovery
via adb
Code:
adb reboot recovery
via bootloader
boot to bootloader (see Q11) and select recovery (use Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select)
via external app
[SIZE=+1]Q13: How to force reboot my frozen device?[/SIZE]
Press and hold the Power button for 10 - 20 seconds, the device will restart and go through the boot-up sequence [source]
(VOL DOWN hold + a quick tap on POWER should force reboot when in bootloader) [source]
[SIZE=+1]Q14: How to charge my device and extend battery life?[/SIZE]Follow Motorola tips:
How do I properly charge my device?
How can I extend my battery life?
[SIZE=+1]Q15: Does rooting/unlocking your phone invalidate its warranty? (In EU)[/SIZE]In short: No. Just the fact that you modified or changed the software of your device, is not a sufficient reason to void your statutory warranty. As long as you have bought the device as a consumer in the European Union.
[source]​
[SIZE=+1]Q16: What to do if my battery is fully discharged and not re-charging?[/SIZE]
Motorola said:
If your battery is completely discharged, it may take several minutes for the device to begin charging. The battery needs to charge to a minimum voltage before the system can boot up, and this may take a few moments to achieve.
Click to expand...
Click to collapse
You may have experienced the 'sudden battery drop' : go to Q25 [source]
Also refer to Moto G will not power up (Q28)​
[SIZE=+1]Q17: OMG i really bricked my device... Any chance getting it back to life ?[/SIZE]If your device is apparently dead, and does not look like a phone when connected to PC, then have a look at this guide by @Boss442​
[SIZE=+1]Q18: How to flash Stock Radio (aka Baseband) / Kernel and why?[/SIZE]Flashing the latest Radio may help if you have problems with poor signal or wifi coverage. Flashing the SS (Single Sim) radio on a Dual Sim device may cause one or both Sims to stop working. Likewise, flashing the radio from a non-CDMA device to a CDMA one, is a very bad idea.
Flashing a newer / different Radio or Kernel may improve battery-life and general performance
ClockWorkMod Recovery or TWRP is required to flash these images.
http://forum.xda-developers.com/showthread.php?t=2649763​
[SIZE=+1]Q19: Lost IMEI ? : 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.img​
To 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)
If for some reason this doesn't work, maybe your IMEI isn't destroyed but only not "readable" by system (file system issue? misread cluster reading frame ? no idea), in that case you may read the following story : http://forum.xda-developers.com/showthread.php?p=52648789
​
[SIZE=+1]Q20: HOw to disable/enable auto On/Off screen with Flip Shell?[/SIZE]
for stock rom : (disabling, since it's enabled by default)
install Xposed framework (and reboot)
install and enable MotoMagnetOff (and reboot)
for CM11: (enabling, since it doesn't work by default)
Follow this FAQ​
[SIZE=+1]Q21: how to remove the 'unlocked warning' message?[/SIZE]Follow @ffosilva method and default Motorola logo will be back ​
[SIZE=+1]Q22: Why and How convert Moto G GPe to non-GPe ?[/SIZE]GPe uses EXT4 for it's 'userdata' filesystem, non-GPe uses f2fs. The GPe kernel expects an EXT4 partition and gives an encryption error if there isn't one. So just flashing a custom ROM won't work on GPe.​
Converting a GPe MOTO G to a non-GPe Moto G:
(we would need someone to approve this method, and if you made it a different way, please, tell us)
1) Fastboot flash retail US XT1032 stock firmware found here:
http://sbf.droid-developers.org/phone.php?device=14​
2) This will wipe the device, replace GPe kernel and radio with stock non-GPe versions and create a new partition table with f2fs filesystem for 'userdata.'
3) Custom ROMs will now work and as will all Motorola Moto G apps.​
[SIZE=+1]Q23: How to reboot into 'safe mode'?[/SIZE]
Press power button, on the pop up, either keep pressing 'shut down' [stock] or 'reboot' [AOSP based]
more infos about this feature​
[SIZE=+1]Q24: How to keep backups on my 8GB device without loosing space?[/SIZE]
To backup :
Use a micro USB-OTG adapter and a USB-storage
boot to recovery
go to backup and storage > backup to /storage/usbdisk
wait (it is really slower than when done to /sdcard ==> especially when generating md5sum!)
reboot your system
To restore your backup :
Use a micro USB-OTG adapter and the USB-storage where the backup is located
boot to recovery
go to backup and storage > restore from /storage/usbdisk
wait (it is really slower than when done to /sdcard)
reboot your system
Enjoy !
You now have a way to keep all your backups, without over flooding your device's storage ! (make sure you won't loose the external storage and keep it safe!)​
[SIZE=+1]Q25: Abrupt Drop Battery Issue (Battery suddenly drops to 0%)[/SIZE]
Description: This issue appears to affect all versions of Moto G; while some people never experience it, others have it frequently. Most likely to occur when tethering / using USB cable. Android versions 4.3 and 4.4.2 are vulnerable.
Solution: Issue fixed in Android 4.4.3.
Kirk Stromberg said:
If anyone else experiences this abrupt drop on your Moto G *after* updating to 4.4.3, we'll need your serial number/IMEI for further investigation and may need to be in more direct contact. Please send an email to:
[email protected]
- with the title "Abrupt Drop" and
-include your serial number (Settings>About Phone>Status) and
- note to please forward to me (Kirk Stromberg).
We'll obviously keep working this here in the forums as well but want to isolate anyone still having this on 4.4.3, especially if it is repeats with some frequency. I know it is reproducible fairly reliably for some of you (tethering/USB cable).
Click to expand...
Click to collapse
https://forums.motorola.com/comment/785885​
[SIZE=+1]Q26: Isssues with MMS on boost mobile with Moto G ?[/SIZE]
Apply the following changes :
apns-config.xml
Code:
<apn carrier="Boost Mobile" mcc="311" mnc="870" apn="n.boost.ispsn"
mmsproxy="68.28.31.7" mmsport="80" mmsc="http://mm.myboostmobile.com"
type="default,supl,mms,fota,dun" carrier_enabled="false" protocol="IPV4V6"
roaming_protocol="IPV4V6" bearer="13" />
build.prop
Code:
ro.cdma.home.operator.numeric=311870
ro.cdma.home.operator.alpha=Boost Mobile
ro.telephony.default_network=13
telephony.slteOnCdmaDevice=1
get more here​
[SIZE=+1]Q27: Miracast / TV Screen-mirroring / DNLA app not working?[/SIZE]
Description: Android 4.4.2 added a 'Settings > Display > Cast screen' (Miracast) option, but it does not function - missing settings menu.
Solution: (Root Required)
This feature now works correctly with Android 4.4.3. However, you still need to enable the 'Cast screen' settings menu by adding the following line (if not already present) to /system/build.prop:
persist.debug.wfd.enable=1​
For quick access to the feature, install: Miracast Widget.
Additionally, 4.4.3 improves compatibility with Allcast and BubbleUPnP, along with other DNLA apps that did not operate correctly in 4.4.2
Simultaneous Internet connection and Screen-mirroring is not possible in Stock Motorola Firmware 4.4.3 or 4.4.4. This may change with a future update or with the release of Android 'L.' Most Custom ROMs do however support this ability.
The utility SecondScreen (root required) allows Moto G's screen resolution to be easily changed when Screen-mirroring - e.g. 720p or 1080p. The app has several additional features such as turning the phone's screen off and disabling haptic feedback in order to save battery usage while Screen-mirroring.​
[SIZE=+1]Q28: Moto G will not power up (addition to Q16 and Q25)[/SIZE]
Plug it into the charger
Hold the VOL DOWN key
While still holding the VOL DOWN key, press and hold the POWER key
Hold both keys down for over 120 seconds. This is more than two minutes and will seem like a long time. You might want to time yourself to make sure you hold it longer than two minutes.
After holding the keys down for more than two minutes, release them.
The Flash Boot screen will display, and the Normal Reboot option will be highlighted
Press the VOL UP key and the device will start a normal reboot.
If you have tried the above and it didn't work, try this:
Plug in the phone for 15 minutes.
Proceed to Step 2 above.
Source: https://forums.motorola.com/posts/3d5eadc25d​
[SIZE=+1]Q29: 4.4.3 / 4.4.4 update issues[/SIZE]If after getting the update to 4.4.3 / 4.4.4 you encounter some problem, there are several options:
App-specific issues: Some apps may simply not be compatible with the latest version of Android and you have to wait until they are. You could always mention it to the App developer via Google Play.
Anything else: Could be solved be doing a Factory reset: (Back up anything important!)
Setting > Backup & reset > Factory data reset (erase all data on phone)​
The best and cleanest way to get to 4.4.4 from a previous version of Android; is to Fastboot flash a Motorola Stock Factory Firmware Image. This can avoid any potential issues that may arise when upgrading via an Over the Air (OTA) update. Also see: "Q7: How to flash Stock Firmware?" in this FAQ.
Stock Factory Firmware Images are available here:
http://sbf.droid-developers.org/phone.php?device=14​
When new images are available they are announced here:
http://forum.xda-developers.com/showthread.php?t=2546251​
[SIZE=+1]Q30: i encounter '(bootloader) Preflash validation failed' error message when flashing Firmware Image[/SIZE]You may have updated to Android 4.4.4 via firmware image or OTA update. In this case you now also have the latest version of the Bootloader. That is why you get the above output when attempting to flash a 4.4.2 firmware image. ==> simply flash 4.4.4 images instead.
If the error still occurs, even with a 4.4.4 firmware image, then unlocking bootloader will be necessary.​
[SIZE=+1]Q31: Various way to fine tune your Moto[/SIZE]Greenify : prevent unwanted apps from awaking device or runing in background (works on both rooted and not devices, but best performances are with rooted+Xposed.
MinFree settings : if you think the moto G (4.4.4) is too aggressive about killing apps to free memory so that you can't switch between two large apps without it killing one app and restarting it. then try tuning MinFree settings, rooted devices only.​
[SIZE=+1]Q32: What can i do with my Notification LED?[/SIZE]Actually your device has 2 LEDs [source] and here is how to play with it : http://forum.xda-developers.com/moto-g/development/led-moto-g-led-custom-controls-t2951463
it can be used as a eMMC activity monitoring, or for charging or USB connected!​
[SIZE=+1]Q33: Spare space needed? using /cache partition[/SIZE]Moving /data/dalvik-cache to /cache/dalvik-cache to use the 600MB of /cache for something useful
==> only using Dalvik.
==> http://forum.xda-developers.com/moto-g/general/mod-save-data-space-cache-partition-t2942765 (by @Bert98)​
[SIZE=+1]Q34: How can I add init.d Support to Stock ROM without using a Custom Kernel?[/SIZE]This can be done by adding the following to: /system/etc/init.qcom.post_boot.sh
Code:
# init.d support
busybox run-parts /system/etc/init.d/
Busybox also required. (Don't know what it is? search a little, it won't hurt you ​
[SIZE=+1]Q35: I reduced brightness to 0 and got stuck with a black screen?[/SIZE]This appears to be a bug in 'Adaptive brightness.' Turning it off and on should stop this happening.
If you are in this situation, try shining a torch light on the screen at an angle to make out the very dim display. You can also try swiping down the 'quick toggle' notification menu and changing brightness via the sliding bar. [Source]​
[SIZE=+1]Q36: I flashed a ROM and GPS has stopped working?[/SIZE]
Flash this 'no-GPS' fix zip via custom recovery.
Alternatively, enter Fastboot mode and type the following commands:
Code:
fastboot erase modemst1
fastboot erase modemst2
[SIZE=+1]Q37: How can i update my bootloader ?[/SIZE]Understand the risks and simply choose between an automated process (for Windows users only) or the step by step one (for Linux users mainly) here​
[SIZE=+1]Q35: [?][/SIZE][...]​
[SIZE=+1]Q35: [?][/SIZE][...]​
[SIZE=+1]Q35: [?][/SIZE][...]​ *​
Forum Rules | New Users Guide | XDA Tour | Report Posts​
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.​ A special thanks to everyone who contributed to the production of this FAQ​

Reserved for part 2

Stock firmware links for a bunch of Moto devices :
http://goo.gl/Qa5WRW

some usefull lines of commands for any user wanting to know what's going on:
requirements :
On Windows : install Moto G drivers and
On Linux : set your rules following that guide (3. Set up your system to detect your device.) : add to /etc/udev/rules.d/51-android.rules the following code
Code:
#motog normal mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e82″, MODE="0666"
#motog debug mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e76″, MODE="0666"
#motog fastboot mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e80″, MODE="0666"
For specific access by one group of users, add GROUP="[groupname]"
______________________________
______________________________
______________________________​
Let's start ! :
in terminal, just type the lines,
in ADB, add "adb" before the commands
if you want not to display the output in terminal, specify the path :
Code:
command > /where_you_want_your_output_to_be_stored/name_you_want_for_the_log
to know if KSM is really turned on : KSM means Kernel Samepage Merging, may not exist on Moto G stock or custom roms
Code:
cat /sys/kernel/mm/ksm/run
to know what modules are running :
Code:
lsmod
install an app from terminal :
Code:
pm install /sdcard/app1.apk
from adb :
Code:
adb install /home/user/app1.apk
(if your .apk is located there )
your kernel crashed?
Code:
cat /proc/last_kmsg
ex : from adb, and stored in /home/user/last_kmsg1
Code:
adb cat /proc/last_kmsg > /home/user/last_kmsg1
an app crashed, you want to know why?
Code:
logcat
ex : from adb and stored in /home/user/myfirstlogever
Code:
adb logcat > /home/user/myfirstlogever
don't have an USB cable ?or adb "other the air" :
connect to your home wifi network (both device and pc)
in settings/dev options/ enable adb on TCP/IP
Code:
adb connect xxx.xxx.xxx.xxx:5555
(the IP is the one displayed in the option you choose previously
and then, since it is connected, catch the log :
Code:
adb logcat > /home/user/myfirstlogever
All commands and syntax used for ADB can be found here
__________________
More is coming
enjoy !

Unlocking Bootloader
Rusty! said:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
>>> Unlocking Bootloader will overwrite any data stored on your device, backup your files before proceeding <<<
For 4.4.2, an updated guide is available here
For real GPe devices (not ones with a GPe ROM added on it after the purchase), NO code is needed, simply skip to "3. Unlock"
1- Register to Motorola website
2- get your Device ID
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure fastboot is in your $PATH)
At the prompt, type
Code:
$ fastboot oem get_unlock_data
The returned string will be used to retrieve your unlock key.
Example: On a Windows Desktop, the returned string format would be
Code:
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
On a Mac OS Desktop, the returned string format would be
Code:
INFO0A40040192024205#4C4D3556313230
INFO30373731363031303332323239#BD00
INFO8A672BA4746C2CE02328A2AC0C39F95
INFO1A3E5#1F53280002000000000000000
INFO0000000
Paste together the 5 lines of output into one continuous string without (bootloader) or ‘INFO’ or white spaces. Your string needs to look like this:
Code:
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
3- Unlock
Check if your device can be unlocked by pasting this string in the pecific field on the Motorola website, and clicking “Can my device be unlocked?”
NOTE: If your device is unlockable, a "REQUEST UNLOCK KEY" button will now appear at the bottom of that page.
after you got the code type the following :
Code:
fastboot oem unlock <code>
or for GPe devices :
Code:
fastboot oem unlock
and wait your device to reboot !
4- Enjoy
5- to relock, (pointless, isn't it?)
First you'll need a stock firmware for your specific device [make sure the device number is the right one at least...]
Then follow these steps:
Open the zip
Find 'flashfile.xml'
Make sure to check integrity of EACH img/bin files in the stock firmware zip before proceeding (to do that, look at the flashfile.xml)
e.g.:
Code:
<step MD5="daae9a555a3789558ee44f9e1fddc8c5" filename="gpt.bin" operation="flash" partition="partition"/>
check that gpt.bin MD5 is really daae9a555a3789558ee44f9e1fddc8c5 and has not been corrupted during download/unpacking
Prepare your device (boot to fastboot) and start relocking:
Code:
fastboot oem lock begin
Flash in the order:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0 // note that you may have more or less sparsechunks, FLASH THEM ALL
mfastboot.exe flash system system.img_sparsechunk.1 // alternatively the files could be named system.img_sparsechunk[1-3] instead
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Finish relocking:
Code:
mfastboot oem lock
Done!

having all this, do you know of anyone who is already working on cyanogenmod and other custom roms and kernels?

toby913 said:
having all this, do you know of anyone who is already working on cyanogenmod and other custom roms and kernels?
Click to expand...
Click to collapse
i don't know, but if the community is cool, calm, willing to work and contribute, thankful and "not flaming people that try to build something" then maybe there will be some devs coming for some work around here

matmutant said:
i don't know, but if the community is cool, calm, willing to work and contribute, thankful and "not flaming people that try to build something" then maybe there will be some devs coming for some work around here
Click to expand...
Click to collapse
well then i'll ask differently do you think that the device needs something like a custom-rom or kernel?
what do you think generally about it?

toby913 said:
well then i'll ask differently do you think that the device needs something like a custom-rom or kernel?
what do you think generally about it?
Click to expand...
Click to collapse
With custom kernels (they generaly are better optimised than stock) we'll get overclock (some extra performance but mostly useless) ; Undervolt (extremely efficient for getting higher battery life when the device is idle ie: nearly no drain in deep sleep contrary to non undervolted device) ; other IO shedulers (that can give better perf in IO : i made some work about this on my old device see here and here and many otehr cool features.
With Custom roms like CM, PA, AOKP, PAC ... we'll get many features as personalizations, theming, performances settings... and many things you could get on stock rooted rom + Xposed, but that's better when things are in the code
But at first, i mean when a kernel/rom is young we'll get instabilities, crashes, maybe some soft bricks : That's the price for cool and fully working Customs
All is based on what you want :
stability (mostly) and simpleness = stay on stock
performance, long lasting battery, fully optimised kernel, extra features, BUT instabilities or littles crashes/drawback = go on Customs

So are you already cooking a kernel for the moto g
Sent from my LG-E610 using xda app-developers app

toby913 said:
So are you already cooking a kernel for the moto g
Sent from my LG-E610 using xda app-developers app
Click to expand...
Click to collapse
No, because i am neither a cooker, nor a developer... Only a Contributor

Code:
adb install packagename.apk
Is going to be easier than using package manager via adb shell.

Rusty! said:
Code:
adb install packagename.apk
Is going to be easier than using package manager via adb shell.
Click to expand...
Click to collapse
thx,
is that full syntax ? no path for app name ?

I'm summing adb in the same location as the apk, or (as I have it) in the path.
Also unlocking your bootloader does still void your warranty, it's only the developer versions that it doesn't.

Rusty! said:
I'm summing adb in the same location as the apk, or (as I have it) in the path.
Also unlocking your bootloader does still void your warranty, it's only the developer versions that it doesn't.
Click to expand...
Click to collapse
ok thx,
i'll correct this.

matmutant said:
ok thx,
i'll correct this.
Click to expand...
Click to collapse
you should remove that part its confusing and unneeded.
also what is falcon_umts
can you or anyone with the device pull the build.prop and post it here.

Dark Passenger said:
you should remove that part its confusing and unneeded.
also what is falcon_umts
can you or anyone with the device pull the build.prop and post it here.
Click to expand...
Click to collapse
Ok, removed.
about falcon_umts : i don't know, but Falcon was one of Motorola's series (i1 was part of the Falson series) but Moto G is part of the XT series ... maybe a codename ; and UMTS is a network system based on GSM
is that what you wanted ?
edit : regarding the build.prop, Falcon is MotoG codename

matmutant said:
Ok, removed.
about falcon_umts : i don't know, but Falcon was one of Motorola's series (i1 was part of the Falson series) but Moto G is part of the XT series ... maybe a codename ; and UMTS is a network system based on GSM
is that what you wanted ?
Click to expand...
Click to collapse
kind of though it would be awesome if you could attach your build.prop here
adb pull

No need for image dumps, the factory images are available here: http://sbf.droid-developers.org/falcon/list.php

[OTA][FASTBOOT][ROM] Official Stock Fastboot image (V10.0.10.0.PDHMIXM, Android P)

Attention: To be able to flash, the bootloader needs to be unlocked (https://en.miui.com/unlock/). Please be warned though: Xiaomi changed something in the method of unlocking the device from May 2018 security update onwards. Now all data will be flushed if you unlock a previously locked device. So please be warned and check the .bat/ .sh scripts for "lock" and "unlock" commands and remove these lines if unsure. If you don't want to unlock your device, you can use everything without the need of editing anything.
Side note: Before everyone is complaining about that kind of change, it makes sense from security point of view: Say, someone steals your phone and he could just unlock the bootloader, he has any possibility to get to your most private data. Just some technical background, but I am not related to Xiaomi or anything, just applying logic.
Introduction:
XIAOMI offers for their official releases also fastboot images including easy to use shell/ batch scripts for flashing.
Luckily, this is also the case for our Mi A1, delivering us a very neat way to easy flash or even emergency rescue our phone via fastboot.
The included shell scripts (*.sh) are meant to be used on Mac/ Linux,
the included batch files (*.bat) are for the Windows users.
Prerequisite:
adb & fastboot have to be installed for the scripts and the flashing to work properly. Please ensure, that your versions are up2date, if you should run into any issues.
Warning: Do not use the flash_factory.bat or .sh file, as it deletes your IMEI.
Android Pie Fastboot Link (official): http://c.mi.com//miuidownload/detail?device=1700333
Version: V10.0.10.0.PDHMIXM (Android P)
Size: 1166M
md5:
Code:
n.a.
No Fastboot image found (yet) --> Please use V10.0.9.0 available here under "Previous versions" and update via OTA
V10.0.10.0.PDHMIXM for Mi A1 Changelog
Code:
[LIST=2]
[*] June 2019 Security patch
[/LIST]
Previous versions:
Version: V10.0.9.0.PDHMIXM (Android P)
Size: 1616M
md5:
Code:
3ded3e7b82097f27ddf176e0399fceba
https://bigota.d.miui.com/V10.0.9.0...0.PDHMIXM_20190514.0000.00_9.0_3ded3e7b82.tgz
V10.0.9.0.PDHMIXM for Mi A1 Changelog
Code:
[LIST=2]
[*] Max 2019 Security Patch
[/LIST]
Version: V10.0.4.0.PDHMIXM (Android P)
Size: 1616M
md5:
Code:
2cee840c96cdb6e0a9b14fc3c3105ff7
https://bigota.d.miui.com/V10.0.4.0...0.PDHMIXM_20190104.0000.00_9.0_2cee840c96.tgz
V10.0.4.0.PDHMIXM for Mi A1 Changelog
Code:
[LIST=2]
[*] FM Radio Adaptive battery and brightness
[*] Simpler ways to navigate your phone
[*] Recommended apps and actions based on your context
[/LIST]
Version: V9.6.8.0.ODHMIFE (Android O, 8.1)
Size: 1616M
md5:
Code:
9ea450fe98fbf4883439a934847f9f5d
https://bigota.d.miui.com/V9.6.8.0....0.ODHMIFE_20181031.0000.00_8.0_9ea450fe98.tgz
V9.6.8.0.ODHMIFE for Mi A1 Changelog
Code:
[LIST=2]
[*] Fortify your Android One phone with the November 2018 security update from Google, which improves security and fixes bugs.
[*] This update improves the stability of your device and optimizes its performance.
[/LIST]
Version: V9.6.7.0.ODHMIFE (Android O, 8.1)
Size: 1615M
md5:
Code:
47d6fd23c7ca5aa538258782aceb3bd2
https://bigota.d.miui.com/V9.6.7.0....0.ODHMIFE_20181015.0000.00_8.0_47d6fd23c7.tgz
V9.6.7.0.ODHMIFE for Mi A1 Changelog
Code:
[LIST=2]
[*] Fortify your Android One phone with the October 2018 security update from Google, which improves security and fixes bugs.
[*] This update improves the stability of your device and optimizes its performance.
[/LIST]
[*] [B]Version: V9.6.4.0.ODHMIFE (Android O, 8.1)[/B]
Size: 1559M
md5: [CODE]735823083fba68350ba27f418114f388
https://bigota.d.miui.com/V9.6.4.0....0.ODHMIFE_20180712.0000.00_8.0_735823083f.tgz
V9.6.4.0.ODHMIFE for Mi A1 Changelog
Code:
[LIST=2]
[*] Fortify your Android One phone with the July 2018 security update from Google, which improves security and fixes bugs.
[*] This update improves the stability of your device and optimizes its performance.
[/LIST]
Version: V9.5.11.0.ODHMIFA (Android O, 8.0)
Size: 1462M
md5:
Code:
1a04581058dc7f27ca18cf8fd74f9413
https://bigota.d.miui.com/V9.5.11.0...0.ODHMIFA_20180504.0000.00_8.0_1a04581058.tgz
V9.5.11.0.ODHMIFA for Mi A1 Changelog
Code:
[LIST=2]
[*] Update June Security Patch
[/LIST]
Version: 9.5.10.0.ODHMIFA (Android O)
Size: 1462M
md5:
Code:
b9e697ed56b49f3657fa13229241519a
https://bigota.d.miui.com/V.9.5.10....0.ODHMIFA_20180405.0000.00_8.0_b9e697ed56.tgz
V9.5.10.0.ODHMIFA for Mi A1 Changelog
Code:
[LIST=2]
[*] Update April Security Patch
[/LIST]
Version: 9.5.9.0.ODHMIFA (Android O)
Size: 1422M
md5:
Code:
5773957dcda9a89495e1d0bfa84ab220
https://bigota.d.miui.com/V9.5.9.0....0.ODHMIFA_20180316.0000.00_8.0_f8cd1b4e8e.tgz
OPR1.170623.026.V9.5.9.0.ODHMIFA for Mi A1 Changelog
Code:
[LIST=2]
[*] Update Mar Security Patch
[*] Fix “couldn’t flash ROM in 9008 mode”
[*] Fix “[IN_User Feedback][Reboot][Mi A1]Random reboot while using the device on V9.5.4.0.ODHMIFA”
[/LIST]
Version: V9.5.4.0.ODHMIFA (Android O)
Size: 1422M
md5:
Code:
5773957dcda9a89495e1d0bfa84ab220
https://bigota.d.miui.com/V9.5.4.0....0.ODHMIFA_20180226.0000.00_8.0_5773957dcd.tgz
OPR1.170623.026.V9.5.4.0.ODHMIFA for Mi A1 Changelog
Code:
[LIST=2]
[*] Update Feb Security Patch
[*] Fix “received call recognized as missed call”
[*] Fix rebooting issue
[*] Update E-label for India
[/LIST]
Version: Android 8.0.0 [OPR1.170623.026.8.1.10]
Size: 1407M
md5:
Code:
8ea503201bb0b594e02e5ed2bf6dea09
https://bigota.d.miui.com/8.1.10/tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b.tgz
OPR1.170623.026.8.1.10 ROM for Mi A1 Changelog
Code:
[LIST=2]
[*] Optimize audio parameters.
[*] Remove the “quick charge” on the lockscreen when charging.
[*] Integrate the performance optimization of MIUI.
[*] Fix “bluetooth power consumption issue”.
[*] Add Korean input method.
[*] Fix “the dialer icon is missing after the upgrade”.
[*] Fix “camera cannot connect sometimes”.
[*] Fix“couldn’t connect to network sometimes”.
[*] Update the Feedback APP.
[*] Fix “fingerprint unlocking speed is slow ”.
[/LIST]
Version: N2G47H.7.12.29 (Android O)
Size: 1084M
md5:
Code:
c9a6ea979b58b9a2fa4dc9e81d70796e
https://bigota.d.miui.com/7.12.29/tissot_images_7.12.29_20171228.0000.00_8.0_c9a6ea979b.tgz
no changelog found
Version: N2G47H.7.12.19
Size: 1396M
md5:
Code:
d39fa89aafcaaaa2203324313c964706
https://bigota.d.miui.com/7.12.19/tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
N2G47H.7.12.19 ROM for Mi A1 Changelog:
Code:
[LIST=2]
[*] D2Acontinuous annoying sharp Sound problem in A1
[*] D2A is transferred to 112 when the local emergency number is called in the Czech Republic
[*] Transition version for Android Oreo
[/LIST]
Short Flashing Guide:
Choices for flashing/ Which script to run?
flash_all = Full flash, like factory reset, bootloader stays unlocked
flash_all_except_storage = Keep your data, bootloader gets re-locked
flash_all_lock = Full flash, like factory reset, bootloader gets re-locked
(*.bat for Windows/ *.sh for Linux & Mac)
Download and extract the *.tgz archive
Shutdown your Mi A1 and start it in fastboot mode (Vol- + Power)
Connect it to your computer/ mac via usb cable
Open a terminal, shell or command line prompt depending on your OS; make sure you are in the same folder as all the just extracted files, if in doubt use the "cd" command
Run the script of your choice to start the flashing process (e.g.: "flash_all.bat" or "./flash_all.sh")
Wait for the script to complete and enjoy your official version of AndroidOne for Mi A1
Hints:
You need to have an up-to-date version of adb and fastboot to be installed properly on your system. For that please just follow the guide here
To get the device in fastboot mode, turn it off, hold VOL(-) & the power button
To check for successful connection type in shell/ terminal "fastboot devices" after device is connected via USB in fastboot mode
If you want/ need to have an unlocked bootloader, you can still use any of the above described scripts and just when finished flashing, reboot again into fastboot mode and run the terminal/ shell/ cmd command "fastboot oem unlock" (locking and unlocking does not mess with your user data)
Just to be clear, inspite of the URL containing "miui" in its name, it is official Android One for Mi A1 (tissot)
Please do not attempt to do downgrades, without factory reset
If you are feeling unfamiliar and/ or unsafe, please use the Mi Flash Tool for Windows instead to install (Guide for Mi Flash Tool; if you had a previous version of Mi Flash tool installed it needs to be uninstalled first)
If you want to force, that you get OTA updates when they become available and you check in system settings manually for them, please ensure that you are using the Google Play Beta Services
Everything seems so complicated, isn't there a tool to assist me? --> I did some research and there seems to be one: https://toolaio.tk/
{
"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"
}
All credits for this tool go to its creator mauronofrio

Hi , thank you for the update because I find only bin files on the official site.
The script .bat don't work on my laptop so I flashed manually all the images files.
I didn't succeed by flashing dummy, fs_image.tar.gz and persist image files. I'm pretty sure it's because there weren't on my version of the OS so if someone could help me by telling me how to push these images files, where and thanks which command, it could be great! ^^

lelozerien said:
Hi , thank you for the update because I find only bin files on the official site.
The script .bat don't work on my laptop so I flashed manually all the images files.
I didn't succeed by flashing dummy, fs_image.tar.gz and persist image files. I'm pretty sure it's because there weren't on my version of the OS so if someone could help me by telling me how to push these images files, where and thanks which command, it could be great! ^^
Click to expand...
Click to collapse
Hi, what error message do you get, when trying to run the batch script? Did you try via command line (cmd) or via powershell (Win10)?
The things you tried to flash without succeeding seem to be not necessary. Please find here all fastboot commands used by "flash_all_except_storage":
Code:
fastboot oem unlock
fastboot flash modem_a /images/modem.img
fastboot flash modem_b /images/modem.img
fastboot flash sbl1 /images/sbl1.img
fastboot flash sbl1bak /images/sbl1.img
fastboot flash rpm /images/rpm.img
fastboot flash rpmbak /images/rpm.img
fastboot flash tz /images/tz.img
fastboot flash tzbak /images/tz.img
fastboot flash devcfg /images/devcfg.img
fastboot flash devcfgbak /images/devcfg.img
fastboot flash dsp /images/adspso.bin
fastboot flash sec /images/sec.dat
fastboot flash splash /images/splash.img
fastboot flash aboot /images/emmc_appsboot.mbn
fastboot flash abootbak /images/emmc_appsboot.mbn
fastboot flash boot_a /images/boot.img
fastboot flash boot_b /images/boot.img
fastboot flash system_a /images/system.img
fastboot flash system_b /images/system.img
fastboot flash lksecapp /images/lksecapp.img
fastboot flash lksecappbak /images/lksecapp.img
fastboot flash cmnlib /images/cmnlib.img
fastboot flash cmnlibbak /images/cmnlib.img
fastboot flash cmnlib64 /images/cmnlib64.img
fastboot flash cmnlib64bak /images/cmnlib64.img
fastboot flash keymaster /images/keymaster.img
fastboot flash keymasterbak /images/keymaster.img
fastboot reboot bootloader
fastboot set_active a
fastboot oem lock
fastboot reboot

majamee said:
Hi, what error message do you get, when trying to run the batch script? Did you try via command line (cmd) or via powershell (Win10)?
The things you tried to flash without succeeding seem to be not necessary. Please find here all fastboot commands used by "flash_all_except_storage":
Click to expand...
Click to collapse
great! I will study which steps are missing! thank you!
Edit: I'm on Win 8 and I'm not able to read the error message because it disappears very quickly! I tried by double clik on the .bat.

lelozerien said:
great! I will study which steps are missing! thank you!
Edit: I'm on Win 8 and I'm not able to read the error message because it disappears very quickly! I tried by double clik on the .bat.
Click to expand...
Click to collapse
Ok, that info should be already enough to help you First press the Windows button and enter "cmd" to start the command line. Once there you have to "cd" (change directory) into the extracted directory (the one where also the *.bat/ *.sh files are in).
Once there you should be able to verify that you are correct by entering "dir" which lists you all the files in the current folder.
After that you just need to call the batch script you want to run by entering its full name and press enter. Then you can sit back and enjoy the show
Edit: Of course you have to have your phone already connected in fastboot mode

Xiaomi just released the full fastboot image for Oreo, which they labeled stable. I disagree, but for everyone who wants to enjoy Oreo already it is the best option we have so far. In comparison to the manual update to Oreo you can also close your bootloader and don't end up in a bootloop, so that is... something!

The flash all command will not relock the bootloader ??? Or will all three choices relock the bootloader ?

Is this same patch level "December 1"?

coremania said:
The flash all command will not relock the bootloader ??? Or will all three choices relock the bootloader ?
Click to expand...
Click to collapse
flash_all does not lock the bootloader.
If you are in doubt and want to keep an unlocked bootloader, I would recommend to choose the script which matches the best what you are looking for.
Then afterwards let your phone reboot, once completed turn it off and start it again in fastboot mode (Volume- + Power) and run in command line/ terminal/shell the following command:
Code:
fastboot oem unlock

Pezmet said:
Is this same patch level "December 1"?
Click to expand...
Click to collapse
Yes

Pezmet said:
Is this same patch level "December 1"?
Click to expand...
Click to collapse
It is, but for instance the slow camera opening bug is gone for me. So I consider it worth the effort so far.

majamee said:
flash_all does not lock the bootloader.
If you are in doubt and want to keep an unlocked bootloader, I would recommend to choose the script which matches the best what you are looking for.
Then afterwards let your phone reboot, once completed turn it off and start it again in fastboot mode (Volume- + Power) and run in command line/ terminal/shell the following command:
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Thanks,
I don't like to relock my bootloader ever,
until selling the device.
Flashing and a locked bootloader never were or will be friends
I do a flash all and restore my data with TWRP.

coremania said:
Thanks,
I don't like to relock my bootloader ever,
until selling the device.
Flashing and a locked bootloader never were or will be friends
I do a flash all and restore my data with TWRP.
Click to expand...
Click to collapse
Alternatively, you could also use flash_all_except_storage, when opening it as a text file first, by removing the line which includes the "oem lock" command. Start looking from the very end of the script file, it is one of the last commands

Hey
I downloaded rom from official site
But when i extracted .tgz file i got payload.bin file
I did not get any .img or any scripts

majamee said:
It is, but for instance the slow camera opening bug is gone for me. So I consider it worth the effort so far.
Click to expand...
Click to collapse
Still slow camera here, are you clean stock ? Or on TWRP and magisk like me ?
Edit: that's funny camera gets fast after opening a few times

how about battery drain fixed or not any test ?

¿ Have The Same bugs that oreo [OTA] ?
-Slow open Camera.
-Bluetooth Drain Battery.
-Some Apps Crashed Like Whatsapp

there is an another .bat file named flash factory.bat..
dont flash this "flash_factory.bat"
i did it and my phone is screwed up..
it fails and doesnt boot..
i dont think this is for our phone..

Blackheart151 said:
dont flash this "flash_factory.bat"
i did it and my phone is screwed up..
it fails and doesnt boot..
i dont think this is for our phone..
Click to expand...
Click to collapse
Sad, to hear that, but just to be clear this one I did not even mention in my guide/ OP. Hope you find a way to recover from it though.

coremania said:
Still slow camera here, are you clean stock ? Or on TWRP and magisk like me ?
Click to expand...
Click to collapse
Clean stock and it got way better for me.

[Guide] [XT16XX] [Solve] G4+ Baseband/Network/Volte issue, Lost 1 IMEI & fingerprint

[Guide] [XT16XX] [Solve] G4+ Baseband/Network/Volte issue, Lost 1 IMEI & fingerprint
Important:
If you have IMEI=0, then this is the wrong thead. Follow this: [Guide] [XT16XX] [Solve] Moto G4/Plus IMEI=0 issue
This method is only tested on Nougat for now, for Oreo, new files will be needed.
Code:
#include <disclaimer.h>
/*
* Your warranty is now.......(wait a minute)........still valid?
*
* I am not responsible for bricked devices.
* YOU are choosing to make these modifications, and if you point
* your finger at me for messing up your device, I will laugh at you.
*/
This thread addresses the following problems:
Baseband version changed to some other country
Sim card getting detected, but no network
Both sims having a network but VoLTE doesn't work
G4 Plus turned to G4, i.e phone just shows one IMEI and no fingerprint
This method is only for the retail models of Moto G4/Plus, it may or may not work on any other models.
All of these issues have a common reason,
The modem files for your device has been corrupted/has some issue or have been changed to some other country.
Voltes isn't working since your baseband is of some other country and not Indian. If you have Indian baseband and still Volte doesn't work, then your modem files have been corrupted/ have some issues.
You have to push the modem, hw, fsg files for your own device.
We already had a thread addressing this issue, but it didn't have modem files for all baseband.
Finally, thanx to our fellow Moto G4 Plus users, for providing these files, we now have hw, modem, fsg files for all the five basebands i.e BRAZIL, LATAM, EMEA, INDIAN, and RETUSA.
Link to the files:
XT1640 [BRAZIL]:
Link: https://www.androidfilehost.com/?fid=11410963190603873179
md5: 8db666f13700e3d12b01051989e3f068
XT1641 [LATAM]:
Link: https://www.androidfilehost.com/?fid=11410963190603873829
md5: cab09417be82e508d0c54f54aac56498
XT1642 [EMEA]:
Link: https://www.androidfilehost.com/?fid=11410963190603873183
md5: e046d911b23c76cb88d5ccd7967d621f
XT1643 [INDIA]:
Link: https://www.androidfilehost.com/?fid=11410963190603873250
md5: d509c5a26305cc5261e707bdf91268e9
XT1644 [RETUSA]:
Link: https://www.androidfilehost.com/?fid=11410963190603873181
md5: 598191e577db1137df62ae996055f5da
Download modem, fsg, hw files according to your original baseband/device model.
Code:
Model Number Baseband
XT1640 BRAZIL
XT1641 LATAM
XT1642 EMEA
XT1643 INDIA
XT1644 RETUSA
Note: These files are extracted from the dual-SIM variant of Moto G4 Plus, so if you flash these on your Moto G4, these will work, but your device name will be changed to Moto G4 Plus (everything will still work fine, just your device will be treated as Moto G4 Plus by all apps) and if you flash these images on single SIM Moto G4 Plus, it will still work.
Pre-requisites:
You must be on Stock Nougat 7.0 (latest version preferred)
You must be rooted (install Elemental-X kernel first and then flash Magisk otherwise you will have boot issues)
Terminal app or adb drivers in PC/Laptop (I wouldn't recommend TWRP (official or unofficial as it has issues flashing hw.img)
Step 1: Download files
Download and place these files in your /sdcard directory.
/sdcard is the same as the Internal storage directory. Do not confuse it with micro Sdcard as it has its directory named as /external_sd
Step 2: Flash the files
Note: The below commands are to be typed in a terminal app or adb shell.
Q) How to type in adb shell?
A) Open command prompt in the folder where you have adb and fastboot installed and type:
Code:
adb shell
So lets start now!
Code:
su
This command it to get root access for the terminal/shell. Grant the root access and you will see that the $ symbol is replaced with # symbol which means that root access has been granted.
Code:
dd if=/sdcard/modem.img of=/dev/block/bootdevice/by-name/modem
dd if=/sdcard/fsg.img of=/dev/block/bootdevice/by-name/fsg
dd if=/sdcard/hw.img of=/dev/block/bootdevice/by-name/hw
Step 3: Flash the latest Stock ROM (April 2018)
That's it. After flashing, reboot and check your baseband. You would be on the baseband which you flashed in step 2.
Indian users, you will see INDIAN baseband if you flashed the files for it, and Volte would work.
Flash the latest Stock ROM from here: Stock N Firmware [Apr 01 Security Patch][fastboot]
Contributors:
@djumie and Erick Lima (for providing BRAZILIAN modem files)
@Nacoro and @Deivid_21 (for providing LATAM modem files)
@echo92 (for providing EMEA modem files)
@checksamir (for providing INDIAN modem files)
@Jleeblanch (for providing RETUSA modem files)
@Pranav (for testing the files)
@Heeth21 (and lastly, myself)
Also all the others who helped during the process

Complete Backup Zip/Script (All partitions)
Now since you have faced this issue, make sure to take a complete backup of all the partitions so that if you ever face an issue like this in future, you will always have your partitions with you to restore your device.
Here is the link to the thread to take complete backup of all partitions: [Guide] [XT16XX] Moto G4/Plus Complete Partition Backup/Restore Zip/Script
The above thread can backup/restore using TWRP flashable zip files for convenience.

reserved

Thank you for this guide, but unfortunately it didn't work. When I pushed the hw image my phone stop responding and I have to force a reboot with the power buttom. I will give up on this issue for now on. Thank you again.
I attached a logcat in case you can find something that could give an anwser about what happens after i push the hw img

Do I have to be on stock ROM for this to work? Can't it work when I'm on a custom ROM?
What happened was I flashed the latest arrow os build, which was faulty. I then clean flashed crdroid. After reboot, sim isn't working, and imei isn't showing anything. I restored my persist partition, with no result.
Any help?

Wow after Restoring Indian Baseband Volte works now.
Thanks Sir.

sxbino said:
Thank you for this guide, but unfortunately it didn't work. When I pushed the hw image my phone stop responding and I have to force a reboot with the power buttom. I will give up on this issue for now on. Thank you again.
I attached a logcat in case you can find something that could give an anwser about what happens after i push the hw img
Click to expand...
Click to collapse
There are a few more ways to make this work, so its too early to give up.
Are you on the latest Stock ROM (April 2018)? You need to be on the latest stock firmware for this to work as the files are extracted from the latest stock firmware.
1. Flash Stock ROM (latest version - April 2018) once again.
2. Flash official TWRP (I repeat official TWRP only).
3. Then go in Terminal of TWRP (Settings>Terminal), and then repeat step 2, but this time no need to type "su" command.
Edit: @sxbino, now that I have learnt a little to read logs, it appears that the logs doesn't contain anything about flashing those files.
Please collect logs from adb using the command:
Code:
adb logcat>log.log
This will start collecting and saving logs in a file named "log" which will be saved in the same folder where you have adb.
If you are using PC/Laptop to push the files, you can open 2 terminal/command prompt windows, one to collect logs and other to flash the files.

But is missing Brazil baseband.
I'm from Brazil and change mine for LATAM.
Does anyone have this files?

edjalmo said:
But is missing Brazil baseband.
I'm from Brazil and change mine for LATAM.
Does anyone have this files?
Click to expand...
Click to collapse
Right now, we haven't been able to get modem files for BRAZILIAN baseband. Will add them in the Google Drive link once they are available from fellow Brazilian users.
Edit: @edjalmo, BRAZILIAN modem files are now available.

CMKdaGreatest said:
Do I have to be on stock ROM for this to work? Can't it work when I'm on a custom ROM?
What happened was I flashed the latest arrow os build, which was faulty. I then clean flashed crdroid. After reboot, sim isn't working, and imei isn't showing anything. I restored my persist partition, with no result.
Any help?
Click to expand...
Click to collapse
You may try if you'd like to. It just didn't work for me(flashing/pushing those files on custom ROM) so I am asking to be on stock ROM.
All of the 64-bit Pie ROMs are causing this error. The developers are working hard to fix it.
I would recommend flash stock ROM. No need to worry about losing IMEI after flashing stock as now it is recoverable, the only condition is you should not try to restore somebody else's persist or efs partitions.

Heeth21 said:
You may try if you'd like to. It just didn't work for me so I am asking to be on stock ROM.
ArrowOS is causing some problem with efs partition. The developer Lyuu is working hard to fix it.
I would recommend flash sSock ROM. No need to worry about losing IMEI after flashing stock as now it is recoverable, the only condition is you should not try to restore somebody else's persist or efs partitions.
Click to expand...
Click to collapse
Somehow, I clean flashed crdroid again, this time restoring the efs partition right after ROM flash. Now my sim is working. Silly me

Update: BRAZLIAN modem files are now available and have been added to the drive link. OP has been updated.

Heeth21 said:
Right now, we haven't been able to get modem files for BRAZILIAN baseband. Will add them in the Google Drive link once they are available from fellow Brazilian users.
Edit: @edjalmo, BRAZILIAN modem files are now available.
Click to expand...
Click to collapse
Thank you very much

edjalmo said:
Thank you very much
Click to expand...
Click to collapse
@edjalmo, Please report back whether they worked or not. I have 2 pairs of modem files. If this one didn't work, I will upload the second pair of files.

Heeth21 said:
@edjalmo, Please report back whether they worked or not. I have 2 pairs of modem files. If this one didn't work, I will upload the second pair of files.
Click to expand...
Click to collapse
Yes! I tested and it worked! My model is XT1640.

Heeth21 said:
You may try if you'd like to. It just didn't work for me so I am asking to be on stock ROM.
ArrowOS is causing some problem with efs partition. The developer Lyuu is working hard to fix it.
I would recommend flash sSock ROM. No need to worry about losing IMEI after flashing stock as now it is recoverable, the only condition is you should not try to restore somebody else's persist or efs partitions.
Click to expand...
Click to collapse
The ArrowOS also broke the imei of my smartphone, I have tried everything but nothing, I hope that the developer of ArrowOS get a solution!

Heeth21 said:
Code:
#include <disclaimer.h>
/*
* Your warranty is now.......(wait a minute)........still valid?
*
* I am not responsible for bricked devices.
* YOU are choosing to make these modifications, and if you point
* your finger at me for messing up your device, I will laugh at you.
*/
This thread addresses the following problems:
Baseband version changed to some other country
Sim card getting detected, but no network
Both sims having a network but Volte doesn't work
G4 Plus turned to G4, i.e phone just shows one IMEI and no fingerprint
This method is only for the retail models of Moto G4/Plus, it may or may not work on any other models.
All of these issues have a common reason,
The modem files for your device has been corrupted/has some issue or have been changed to some other country.
Voltes isn't working since your baseband is of some other country and not Indian. If you have Indian baseband and still Volte doesn't work, then your modem files have been corrupted/ have some issues.
You have to push the modem, hw, fsg files for your own device.
We already had a thread addressing this issue, but it didn't have modem files for all baseband.
Finally, thanx to our fellow Moto G4 Plus users, for providing these files, we now have hw, modem, fsg files for all four basebands i.e LATAM, EMEA, BRAZIL, and INDIAN.
Here is the link to the files: https://drive.google.com/open?id=1NtOTKgmJIP_Ys26CYd9KBdwhWdGfbCqH
Download modem, fsg, hw files according to your baseband.
Note: These files are extracted from the dual-SIM variant of Moto G4 Plus, so if you flash these on your Moto G4, these will work, but your device name will be changed to Moto G4 Plus (everything will still work fine, just your device will be treated as Moto G4 Plus by all apps) or if you flash these images on single SIM Moto G4 Plus, it will still work.
Pre-requisites:
You must be on Stock Nougat 7.0
You must be rooted (install Elemental-X kernel first and then flash Magisk otherwise you will have boot issues)
Terminal app or adb drivers in PC/Laptop (I wouldn't recommend TWRP (official or unofficial as it has issues flashing hw.img)
Step 1: Download files
Download and place these files in your /sdcard directory.
/sdcard is the same as the Internal storage directory. Do not confuse it with micro Sdcard as it has its directory named as /external_sd
Step 2: Flash the files
Note: The below commands are to be typed in a terminal app or adb shell.
Q) How to type in adb shell?
A) Open command prompt in the folder where you have adb and fastboot installed and type:
Code:
adb shell
So lets start now!
Code:
su
This command it to get root access for the terminal/shell. Grant the root access and you will see that the $ symbol is replaced with # symbol which means that root access has been granted.
Code:
dd if=/sdcard/modem.img of=/dev/block/mmcblk0p1
dd if=/sdcard/fsg.img of=/dev/block/mmcblk0p16
dd if=/sdcard/hw.img of=/dev/block/mmcblk0p43
Step 3: Flash the latest Stock ROM (April 2018)
That's it. After flashing, reboot and check your baseband. You would be on the baseband which you flashed in step 2.
Indian users, you will see INDIAN baseband if you flashed the files for it, and Volte would work.
Contributors:
@echo92 (for providing EMEA modem files)
@checksamir (for providing INDIAN modem files)
@Nacoro and @Deivid_21 (for providing LATAM modem files)
@djumie and Erick Lima(for providing BRAZILIAN modem files)
@Pranav (for testing the files)
@Heeth21 (and lastly, myself)
Also all the others who helped during the process
Click to expand...
Click to collapse
I do not understand where to enter the commands, can you explain more detailed? does this also work for IMEI = 0?

luis dambrowski said:
I do not understand where to enter the commands, can you explain more detailed? does this also work for IMEI = 0?
Click to expand...
Click to collapse
Nope, if you have IMEI=0, go to this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068
If there is any problems like baseband/network after restoring IMEI, come to this thread.

Update: RETUSA modem files are now available and have been added to the drive link. OP has been updated.

I just installed the files of the Brazilian version, they worked perfectly in the g4 xt1626, only the part of tv does not appear because my model is the version no plus, but the baseband is now correct, brazilian version. I just have to thank Heeth21, his job in keeping a baseband database and etc is phenomenal, will help a lot of people.

[ROM][STOCK][PIE 9.0] Install stock Android Pie without unlocked bootloader

Hello everybody, I'm sharing this tutorial to how to force Android Pie installation on retail moto x4.
Warning: read all the steps carefully. I'm not responsible for your actions and you're on your own on this..
What you need to do this
At first, follow the commandments to change the firmware of a mobile phone:
You will need an SD card (minimum 2gb of memory) !!! IMPORTANT !!! - See step 3.1 if you don't have a SD Card
Check if the battery is above 80%
Make sure you have ADB + Fastboot drivers installed AND YOU CAN ACCESS IT FROM YOUR COMMAND PROMPT
Make sure you have the latest Motorola Drivers installed on your computer.
Tested on:
- XT1900-1 - Ok
- XT1900-4 - Ok
- XR1900-5 w/ Android 8.0 - Ok
- XT1900-6 w/ Android 8.1 - Ok
- XT1900-7 w/ Android 8.0 - Ok
Not working for:
- XT1900-2 Indian Variant
Let's do this.
Step 1
Understand that this Pie update zip does not work on devices running Android One (google_fi) or Amazon (AMZ), only Retail phones. No matter if you have already installed other systems on it, you have to be in a retail (better with locked bt).
If you are not in retail, I picked up the latest retail firmware to install. Flash it on your device before proceeding.
Warning: note If your actual version number (OPWS 99.999.99-99) is lower than you will download below. If your current version number is higher, the procedure will not work and you will have to abandon this tutorial unless you unlock your bootloader, and I do not recommend doing this since rollback can cause brick your device permanently.
For Retail Android 8.1
Firmware: https://moto.netlib.re/payton/PAYTON_OPWS28.46-21-16_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
For Retail Android 8.0 devices (devices which never updated to 8.1) -- thanks to Comby_sk
Firmware: https://moto.netlib.re/payton/PAYTON_OPWS27.57-40-25_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Android Pie Firmware: https://moto.netlib.re/payton/OTAs/ab_delta-Blur_Version.27.301.32-29.11.36.payton.retail.en.US.zip (don't download the step 2's file if you're downloading this. THIS IS ONLY FOR ANDROID 8.0 NOT 8.1)
-------
You will need this file too. Copy all text, create a notepad file with it's content and name it "Flash-all.bat".
Flash-all.bat: https://pastebin.com/pZ9ZteGX
Step 2
Skip to step 3.1 if you don't have a SD Card
After installing the Android 8.1 firmware on your device, download this ROM and place it at the root of your SD card.
Android Pie Firmware: https://moto.netlib.re/payton/OTAs/ab_delta-Blur_Version.28.271.24-29.11.36.payton.retail.en.US.zip
Step 3
Reboot your device to Fastboot, and start it on recovery mode (hold power button and press volume + -- don't hold both buttons simultaneously). When done, select "Apply update from SD card" and select the update package. The update is slow and it took more than 1 hour with me. Then sit back and relax while it's installed.
Step 3.1
If you don't have a SD Card, you should upload the file with a ADB command.
Download the file from Step 2 and put the file in the same directory where your adb is installed.
Restart your payton to recovery mode (hold power button and press volume + -- don't hold both buttons simultaneously). When done, select "Apply update from ADB" and them run this command from CMD:
HTML:
adb sideload path_to_your_file
this command can take about 40 to 60 minutes for the speed of uploading and installing the update.
Note: path_to_your_file should be the full file name where your downloaded zip are.
Step 4
To work everything perfect and with no bug after the upgrade:
I) Go to settings -> System -> Advanced -> Reset options -> Factory reset the device
II) If the phone stucks on motorola boot screen, soft reset it. (hold power button for ~15 seconds)
III) Do all the initial setup procedures, then update the all the pending Play Store apps, and restart the device.
After that, your device will be with the stock Android Pie installed. Congratulations.

Have you tried it with the bootloader blocked?

Just did it on my XT1900-6, working fine but i had to install the update via adb.

[XT1900-7][STOCK][PIE] Install stock Android Pie without unlocked bootloader
It looks that guide from OP can be used for installing stock Pie on XT1900-7 reteu model.
Step 1.
Install OPWS27.57-40-25 fastboot package (Blur_Version.27.301.32.payton.retail.en.US with october 2018 security patch) instead from OP
Step 2.
Install PPW29.69-26 OTA (Blur_Version.29.11.36.payton.retail.en.US) instead from OP
Will try tonight.

al3al3al3jandr0 said:
Have you tried it with the bootloader blocked?
Click to expand...
Click to collapse
this tutorial is for locked/blocked bootloader

-
Sorry i was wrong.

SebastKae said:
@Comby_sk The last one is linked to the same file than the OP?
Click to expand...
Click to collapse
No, it is different. OP file is "28.xx.xx" to "29.xx.xx". My file is "27.xx.xx" to "29.xx.xx".
27 = 8.0
28 = 8.1
29 = 9.0
XT1900-7 never had 8.1, only 8.0. For XT1900-7 upgrade from 27 to 29 is needed.

What is the process for xt1900-2? I am on latest october patch OPWS 27.57-40-3-15

Prinjal Dave said:
What is the process for xt1900-2? I am on latest october patch OPWS 27.57-40-3-15
Click to expand...
Click to collapse
No one, your blur version "27.306.16" hasn´t Pie OTA yet.

Comby_sk said:
No one, your blur version "27.306.16" hasn´t Pie OTA yet.
Click to expand...
Click to collapse
So i can't update to pie yet.... Right?

Prinjal Dave said:
What is the process for xt1900-2? I am on latest october patch OPWS 27.57-40-3-15
Click to expand...
Click to collapse
I've updated the thread with Android 8.0 options.

CypherPotato said:
I've updated the thread with Android 8.0 options.
Click to expand...
Click to collapse
Thanks

CypherPotato said:
I've updated the thread with Android 8.0 options.
Click to expand...
Click to collapse
I have XT1900-2 OPWS27.57-40-3-15
How to flash/update PIE using these files? both files through SD Card or manually using fastboot method?
Code:
For Retail Android 8.0 devices (devices which never updated to 8.1) -- thanks to Comby_sk
Firmware: https://moto.netlib.re/payton/PAYTON...LT_CFC.xml.zip
Android Pie Firmware: https://moto.netlib.re/payton/OTAs/a...tail.en.US.zip (don't download the step 2's file if you're downloading this. THIS IS ONLY FOR ANDROID 8.0 NOT 8.1)

Prinjal Dave said:
So i can't update to pie yet.... Right?
Click to expand...
Click to collapse
Right

zlebors said:
I have XT1900-2 OPWS27.57-40-3-15
How to flash/update PIE using these files? both files through SD Card or manually using fastboot method?
Code:
For Retail Android 8.0 devices (devices which never updated to 8.1) -- thanks to Comby_sk
Firmware: https://moto.netlib.re/payton/PAYTON...LT_CFC.xml.zip
Android Pie Firmware: https://moto.netlib.re/payton/OTAs/a...tail.en.US.zip (don't download the step 2's file if you're downloading this. THIS IS ONLY FOR ANDROID 8.0 NOT 8.1)
Click to expand...
Click to collapse
Same thing as the post says. Flash Firmware using fastboot and flash Android Pie Firmware from recovery

CypherPotato said:
I've updated the thread with Android 8.0 options.
Click to expand...
Click to collapse
I think, it won't work on all 8.0 versions. E.g. XT1900-2 OPWS 27.57-40-3-15 has different blur version "27.306.16", but Pie OTA needs "27.301.32".

Is this for xt19-1 or what

boonemeat said:
Is this for xt19-1 or what
Click to expand...
Click to collapse
for all devices

This doesn't work with large SD cards since recovery mode can't mount the external sd card. I tried with a 128gb one and it failed, luckily I had a 4GB one lying around.

Comby_sk said:
I think, it won't work on all 8.0 versions. E.g. XT1900-2 OPWS 27.57-40-3-15 has different blur version "27.306.16", but Pie OTA needs "27.301.32".
Click to expand...
Click to collapse
CypherPotato said:
for all devices
Click to expand...
Click to collapse
any suggestions?

[FIRMWARE][GUIDE] Topelotek Meteor (T07D) Stock Firmware/Installation Guide

TOPELOTEK METEOR T07D
7" ANDROID TABLET
Product: astar_733Q1
Board Platform: Allwinner-A33
CPU: Quad-Core Cortex-A7 (ARMv7l)
CPU Clock: 200 MHz - 1.2 GHz
[Overclock Up To 1.51 GHz]
GPU: Mali-400MP2
RAM: 1 GB
Bluetooth: 4.0
Internal Storage: 8 GB (eMMC)
External Storage: microSD Slot (Up to 128GB)
USB OTG Support
OEM Unlocked
Display: 7" IPS
Screen Resolution: 800 x 1280
Screen Density: 190 DPI (mdpi)
Battery: 2850 mAh Li-Ion
Cameras: 2.0 MP Main; 0.3 MP Front
OVERVIEW:
The Topelotek Meteor (T07D) is a very affordable, very basic, low-spec 7" Android tablet. As reflected by the above hardware specs, this tablet is by no means spectacular with regard to performance potential. Nonetheless, for the pricetag (typically about $25 or less), the Meteor T07D is not a bad deal. Like many Chinese tablets of its kind, stock firmware can be very difficult -- if not impossible -- to locate. However, this device does ship with a couple of extraordinary features: an unlocked bootloader and insecure boot image support (ro.secure=0) out of the box. As such, rooting and customizing this tablet are fairly simple tasks, as is pulling firmware images from the device's partitions. This firmware package is constructed from unmodified stock partition images (/system, /boot, /bootloader, /recovery), which can be installed using a few rudimentary fastboot commands, and can be beneficial in restoring a device that is soft bricked, stuck in a bootloop, etc. Installing this firmware package per the instructions below will restore your Topelotek Meteor to a stock factory state.
FIRMWARE BUILD INFO:
Android Version: 6.0.1 Marshmallow
Build ID: MOB30R
Firmware Version: v6.0rc3
Build No.: A33-1+8-0312+2145-1280x800-6.0-733Q1-8703-180601
Kernel Version: 3.4.39
Build Date: May 30, 2018
Security Patch Level: April 1, 2018
Insecure Boot Image (ro.secure=0)
DISCLAIMER: By proceeding further, your warranty can be rendered null & void. (However, because the device ships OEM unlocked, out of the box, your warranty may or may not be affected. You will need to make this determination on your own.) As with any other system-level procedure, installing this firmware invokes the possibility that your device could be damaged or rendered completely inoperable. While I have thoroughly tested this firmware on my own device, I will not be held liable for anything that goes wrong during your installation of this firmware. By proceeding, you are taking sole responsibility for the integrity and operability of your device.
PREREQUISITES:
For this installation, you will need a PC or Mac with the latest Android platform tools or the latest Minimal ADB & Fastboot utilities installed. Visit this thread for download links and instructions: https://forum.xda-developers.com/showthread.php?t=2317790 Please give @shimp208 a tap on the THANKS button if you use his work. This is a link to the July, 2019 Minimal ADB & Fastboot thread by @K3V1991. https://forum.xda-developers.com/an...g/tool-mini-adb-fastboot-2019-06-30-t3944288. Again, please give thanks if you use the developer's work.
Also, you will need to install the correct ADB and USB device drivers for this tablet.. A simple Google search for "Allwinner-A33 ADB & USB drivers" will provide links to these files, as well as guidance for proper installation of the drivers. As mentioned supra, this tablet ships with an unlocked bootloader. Nevertheless, you will need to go to SETTINGS>ABOUT TABLET and tap Build Number 7 or 8 times until Developer Options are enabled. Then, you will need to check the box called OEM Unlocking. Once this is done, your device bootloader is unlocked for all intents and purposes.
INSTRUCTIONS:
1. Download the firmware package from the below link and extract the contents of the archive to your ADB & Fastboot directory on your PC;
2. Boot your device into fastboot mode. One way to do this is by connecting your device to your PC with a quality micro USB to USB syncing/charging cable. Boot your device up, ensure USB Debugging is enabled, and open a command prompt on your PC in the path of your ADB/Fastboot directory. Execute this command:
adb devices
If properly connected, the command window will return with an alphanumeric string that represents your device serial number. If you do not see confirmation of a proper connection, check your driver installations, your sync cable, and/or try another USB port.
(In the event your device will not boot into the Android OS (soft brick, boot loop, etc.), you can boot directly into recovery mode/fastboot mode by using hardware key combinations. However, I am not familiar with the hardware key method, so you will need to research the proper procedure.);
3. Once properly connected, execute the following command:
adb reboot bootloader
Your tablet will now boot into fastboot mode. Your device screen will simply display the white Topelotek logo lettering amidst a pale blue screen. Open a command window once again in your ADB/Fastboot directory;
4. Execute this command:
fastboot devices
Once again, if properly connected, the word "fastboot," or your device serial number will be displayed in the command window;
5. Once fastboot communication has been established, execute the following command set:
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase userdata
fastboot erase cache
fastboot reboot
(Please note that system.img is a large file. Fastboot will automatically parse this image into a series of sparsechunks and systematically flash them to your device. This process can take up to 5 or more minutes, so just be patient. To avoid any possible issues, it is imperative to be using a current version of either the Android platform tools or the Minimal ADB and Fastboot utilities.)
Upon reboot, your device should be restored to a factory stock state and be running on the latest available firmware version.
DOWNLOAD LINK:
Firmware v6.0rc3: https://drive.google.com/file/d/1-0UciSFgTwqN-n_TyL255oZcOVZMqjso/view?usp=drivesdk