Related
[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
Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle down any time soon. The thread is still usable so I will leave it open for discussion.
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections,
* thermonuclear war, or you getting fired because the alarms failed and you
* could not call in.
*
* Please ensure you have an advanced understanding of this device before
* flashing it! YOU are choosing to make these modifications or your own free will.
Thread Notes:
I cannot stress this enough--Please READ EVERY STEP FULLY to be sure of what you need to do.
Some steps listed in this process WILL wipe your userdata. If you have anything you need to save back it up first. While flashing via bootloader you should see it say "(bootloader) Image not signed or corrupt" - (and can show "bad key" or "N/A" while booting) this is normal expected behaviour as the image is no longer properly signed by motorola (I had to repack as our dtb's are compressed inside the boot image)
This thread is not about custom roms - You may be able to run them using the boot images provided, but this thread does NOT cover that
This guide assumes your are on COMPLETELY STOCK (FACTORY) FIRMWARE. If you have previously flashed *any* other firmware, system images, kernels, or anything else I cannot say for sure that this guide will work for you
This WILL affect your ability to get OTA's if/when they come. This thread does not cover getting back to stock. It's up to you to figure out how to get back to stock if you want the update. You're best bet to avoid issues (boot-loops, non-booting, failed updates, etc) is to go completely back to stock first!
Android GSI's - For the record, I have booted GSI's made (Aonly-32bit) however there are some issues I've noticed regarding sounds while using them. Again, this thread is NOT the place to discuss problems with this.
TWRP - We can now use official twrp! Please click this link to see details. I have edited the first post to reflect the current state of our twrp images. If you see an error or run across an issue please let me know and I"ll see about fixing it. I have linked an unofficial build I made in the official thread to fix some issues with the official build. When I get a chance to properly verify the new test-build (made by the twrp gerrit) I will see about having the official one updated.
PIE - These instructions were made using Oreo, not Pie. There are differences in the boot images at the very least (you may not need a modified boot image for Magisk). I have not flashed Pie yet to test things. If you want to test, please let me know how things work out for you.
Working Images:
The variant models below have been verified working using one of the firmware versions listed.
XT1925-2, XT1925-3, XT1925-4, XT1925-5, XT1925-6, XT1925-13
OPS27.82-19-4 (Build Date: Fri Mar 9 11:04:39 CST 2018)
OPS27.82-41 (Build Date: Sat Mar 24 01:37:45 CDT 2018)
OPS27.82-72 (Build Date: Sun May 27 02:13:41 CDT 2018)
OPS27.82-87 (Build Date: Mon Jul 16 14:54:23 CDT 2018).
OPSS27.82.87-3 (Build Date: September 2018 Security Update)
OPSS27.82-87-6 *Provided by @Jleeblanch
OPS27.104-15-10 (Build Date: Wed Mar 28 21:13:40 CDT 2018)
OPSS27.104-15-10-4 (Build Date: July 2018 Security Update) *Provided by @Jleeblanch
OPS27.104-92 (Build Date: September 2018 Security Update)
OPSS27.104-92-2 (Build Date: November 2018 Security Update) *Provided by @Jleeblanch
*
*Waiting for confirmation:
*OPS27.82-57
*
Prerequisites:
Unlocked bootloader.
ADB/Fastboot installed on your machine ( https://developer.android.com/studio/releases/platform-tools ) If you have issues with commands make sure you have a current build of ADB and fastboot.
At least some knowledge of how to use ADB and fastboot, this guide does not cover that.
Some knowledge of how TWRP/custom recoveries work.
Finally, the guide:
Step 1) Downloading TWRP and modified boot image
Download TWRP and a modified boot image that matches your factory firmware version to the ADB/Fastboot folder on your computer. The boot image downloads are based on the premise of the firmware you are running. If yours is not listed please back up (next step) and provide a link for me to edit.
Official TWRP Thread: please read the thread for more information regarding this build. The download link is in that thread.
Unofficial TWRP, this link is just like official but added a vendor image mount for testing vendor operations: [AFH] twrp-v3.2.3-ali.img
BOOT Image Links - [AFH] No-verity edited boot images link
Reboot to your bootloader. You can do this by turning on your device while holding the power and volume down buttons at the same time. Once the device reboots to the bootloader connect your phone to your computer.
Step 2) Backing up your stock boot and recovery images and fstab.qcom file--if you have these already you can safely skip to step 3.
Open a terminal/command prompt on your computer and type the following to boot into TWRP (If your filename is different, please replace the filename below with yours):
Code:
fastboot boot twrp-v3.2.3-ali.img
Once TWRP boots (it may take a bit to boot because it is trying to decrypt your userdata. It will fail as TWRP--at least for now--needs to be flashed to decrypt properly. Swipe to allow modifications if you want if asked), type the following in your computer's terminal/command prompt to back up your boot and recovery images:
Code:
adb pull /dev/block/bootdevice/by-name/boot stockboot.img
Code:
adb pull /dev/block/bootdevice/by-name/recovery stockrecovery.img
If you intend to remove encryption you'll want a backup of your fstab.qcom file:
To back up your fstab.qcom file (modified in a later step) we need to mount Vendor in TWRP first if it's not already mounted. From TWRP's main menu press 'Mount'. You can see if the vendor partition is mounted (check mark next to the word 'Vendor') . If it isn't mounted just press 'Vendor' and it should mount. Next type the following:
Code:
adb pull /vendor/etc/fstab.qcom factory-fstab.qcom
Reboot to the bootloader.
Step 3) Installing TWRP and modified boot images
Run the following command from your computer's terminal/command prompt to install the TWRP image to your device (If your filename is different, please replace the filename below with yours).
Code:
fastboot flash recovery twrp-v3.2.3-ali.img
Run the following command from your computer's terminal/command prompt to install the boot image to your device.
usage:
Code:
fastboot flash boot <insert-boot-image-name-here>.img
example:
Code:
fastboot flash boot OPS27.104-92_no-verity_boot.img
Step 4) Wiping your data on your phone to remove the current encryption. Ensure you have a backup beforehand if you want it.
This step is only needed if you intend to remove your current encryption, if you don't want to do this please skip to the next step
Boot into TWRP by using the volume keys on your phone to select "recovery mode" and then press the power button and TWRP will boot up (it may take a bit to boot because it is trying to decrypt your userdata or if you have a screen lock it may ask for it--enter it and proceed. Please read the thread linked above for help if you enter it incorrectly.)
Swipe to allow system partition modifications if you want and are asked. If you wish to backup your data and restore it after formatting then do so now. Next click the "Wipe" button in TWRP and then "Swipe to Factory Reset". This step should have formatted data as it was encrypted (removing internal storage ) however if it didn't and data is still not mountable in TWRP you can use the "Format Data" button above "Swipe to Factory Reset", this will format data and remove EVERYTHING from the internal storage as well. You may need to format data again and reboot into TWRP. DON'T REBOOT TO SYSTEM YET.
Step 5) Removing forced-encryption upon first boot (you may still choose to encrypt after booting--Moto's firmware defaults to saying it's encrypted, at least on mine, in the security tab of settings but it's not and the option to encrypt still exists within that menu)
This step is only needed if you intend to remove forced encryption, if you don't want to do this please skip to the next step
**THIS STEP DOES NOT REMOVE CURRENT ENCRYPTION--IT ONLY REMOVES FORCED ENCRYPTION DURING THE FIRST BOOT: YOU MUST HAVE COMPLETED STEP 4 ABOVE TO REMOVE CURRENTLY ENCRYPTED DATA**
This file has been verified working on Oreo and may not function correctly on Pie, please be aware of this: see HueyT's Post.
Download the force-encryption disabler zip to your ADB/Fastboot folder: [AFH] Force_Encryption_Disabler_For_ALI_Oreo_v2.zip
Now push that zip file to your phone. The example uses the /tmp directory. From your computer's terminal/command prompt type the following into your command prompt/terminal from your adb/fastboot folder:
Code:
adb push Force_Encryption_Disabler_For_ALI_Oreo_v2.zip /tmp
Flash the zip you just pushed by pressing the Install button in the TWRP main menu, select the folder where you pushed the zip to and install it. We can verify it flashed by mounting vendor manually if it's not mounted and using the following command from your computer's terminal/command prompt and checking the line that mounts /data says "encryptable" instead of "forceencrypted":
Code:
adb shell "cat /vendor/etc/fstab.qcom"
The result should include this line:
/dev/block/bootdevice/by-name/userdata /data f2fs rw,discard,nosuid,nodev,noatime,nodiratime,nobarrier,inline_xattr,inline_data wait,check,formattable,encryptable=/dev/block/bootdevice/by-name/metadata
Click to expand...
Click to collapse
Note where it says "encryptable". That means we now have the choice to do so vs. being forced to. If for whatever reason it still says "forceencrypted" mount vendor manually and try again.
Step 6) Rooting via Magisk
This step is only needed if you intend to have root access, if you don't want to do this or wish to do this later please skip to the next step
To be safe, you may need to reboot back into TWRP to make sure it sees the data partition mounted correctly and again swipe to allow system partition modifications if you want. (I've seen Magisk say forced-encryption was still detected even though it actually wasn't if I didn't reboot)
Download Magisk from the linked thread to your ADB/Fastboot folder: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Run the following command to push the Magisk zip to your device (v17.3 (beta) is current as of the last edit of this post, if it changes please put your version number instead).
The example uses the /tmp folder:
Code:
adb push Magisk-v17.3.zip /tmp
Flash the Magisk zip from TWRP by pressing the Install button in the main menu and navigate to the /tmp (or wherever you pushed it) folder to select and install it. Magisk should show success without any mention of verity or encryption. If it does, something hasn't gone right and you may need to start again.
Step 7) Almost finished!
Reboot your device. If you installed Magisk it will say "N/A" in the top corner of your device for a few seconds (otherwise it should say "bad key"). This is normal. It may look like it bootloops that screen, just let it go and and it should boot the Motorola boot screen and you can setup your device as a new phone.
Once booted, if you installed Magisk, verify Magisk Manager is installed and the root functionality works.
Step 8) ???
Step 9) Profit
Credits:
@kwiksi1ver - getting things going for us, work with twrp and verity and allowing me to use his thread as base for this guide.
@CodyF86 and his Moto E5 thread for clues as to what it would take to turn off DM-Verity (per kwik)
@Dadud - testing and constantly nuking said device
@AngryManMLS - testing and communications
@Vache - Provided us the fix for sdcards in TWRP.
@Xennet's thread regarding verity and encryption and the disabler zip and everyone there: Disable [DM-Verity]/[Force Encryption] [OnePlus 3T/3] for [Oreo] Oxygen OS
@likemiketoo - Having had TWRP built for us for testing purposes
@Jleeblanch - Helping provide various no-verity images and other help/advice like....everywhere
Everyone else who I am forgetting because let's be honest, I'm sure I have. If you feel like mention is owed please let me know and I'll be happy to add.
Extras:
THE BOOT IMAGE LINKS IN THIS POST HAVE BEEN REMOVED TO AVOID CONFUSION: THEY WERE OLD DOWNLOADS WITH IMPROPERLY LABELED NAMES.
The following is provided for backup purposes only in case you forgot to back up. When pulled from the phone, the images are the full partition size, not actual size.
XT1925-6 (OPS27.104-15-10) Factory pulled files
These files will get you back to stock as far as this guide is concerned. Remember though, 'bad key' will be displayed as they were pulled from a device instead of being provided by Motorola
Factory boot image - *link removed*
Factory recovery image - *link removed*
Factory fstab.qcom file - factory-fstab.qcom - You can push this file to /vendor/etc/ to go back to stock vendor parition if you need. You'll need to rename it to 'fstab.qcom' to make it work right. Factory boot images will probably have an issue booting without vendor being completely stock.
The following images have been provided by other XDA members:
XT1925-2
Factory boot image - *link removed*
XT1925-4
Factory boot image - *link removed*
XT1925-5
Factory boot image - *link removed*
Notes regarding editing the boot images
First off, this is not going to be a "guide" like the first post. Different devices may have different needs, and at this time I am not changing this thread to answer questions about the editing process. Maybe that'll change in the future.
It took me a minute to realize that the G6 (ALI) dtb's are compressed and this is why directly hex editing the boot images (like the G6 Play (jeter)) initially resulted in non-booting. I'd think anyone could decompress the lz4 archive and edit the necessary info, recompress (I used max compression) and then repack the boot image and it should boot. Before that realization I had at one time built the kernel from source code (OPS27-104.15.10) with verity support disabled there so I could get around verity.
Story time!
I'll keep it shorter than it really was so be happy!
So the last time I was into building roms and such was several years ago. If the dtb's existed then, I didn't remember them I started off with some of the various "kitchens" unpacking the boot image I pulled and was getting no where. Even simply unpacking and repacking seemed like it was causing issues. I saw the results kwiksi1ver was having with the G6 Play and asked for advice: Hex edits, don't unpack..
Not sure where to go from there I searched around for posts regarding verity and at some point came across Xennet's thread: Disable [DM-Verity]/[Force Encryption] [OnePlus 3T/3] for [Oreo] Oxygen OS. Within that thread there was a link for another post in that thread that spoke a more in detail about what needed to change (post #3). Please read up on that if you want to know more.
Details:
Basically, if we're not rebuilding from source, etc etc, then we need to hex edit the dtb file (ours is actually I believe 6 dtb files combined into one, other devices can vary). On some devices these files are not-compressed and we can just edit them and go. For ours, I found the need to unpack them with a kitchen (AIK). Once there, I decompress the dtb archive (it's in 'lz4' format, max compression) and make the edits. The lines we are looking for contain "wait,verify". Under normal circumstances these will mount the system and vendor partitions with verity enabled (verify) to be sure they aren't modified. We need to REPLACE the ",verify" portion of the "wait,verify" with zeros. We can't just delete them, replace with zeros so we don't change the overall file size. We have to make sure we get all references to ",verify" replaced. It'll just say "wait" now. After I've edited the dtb file I recompress in 'lz4' format with max compression and then repack the boot image. After that, we should be good to go!
Please reference Xennet's thread if you want more details of how the lines actually look in code, just be aware ours may not be 100% the same. I may add or change stuff here later.
Great guide!
thanks, can't try it yet but i will soon.
Excellent work broski, sweet guide. Really looking forward to testing some stuff out, I'm off for the next two days... so gotta get to a computer [I know pathetic, I don't have one] ... Jeez you couldn't make a one click solution for all this? ?
For real though, super big thanks to all of you for
enduring the grueling task of cracking this bad boy
How bout some donate links? ... and @kwiksi1ver, I'm not sure if you're into developing ROMs or Kernels, but I say more is always better, so there's still good cause for you to get a G6.
dejello said:
Extras:
The following is provided for backup purposes only in case you forgot to back up. When pulled from the phone, the images are the full partition size, not actual size.
Moto G6 (Ali - OPS27.104-15-10) Factory pulled files
Factory boot image - MotoG6-ali-factory-boot.img
Factory recovery image - MotoG6-ali-factory-recovery.img
Factory fstab.qcom file - factory-fstab.qcom
Click to expand...
Click to collapse
it serves for XTI 1925-4?
OPS 27.82-72
Enviado desde mi moto g(6) mediante Tapatalk
dejello said:
Extras:
The following is provided for backup purposes only in case you forgot to back up. When pulled from the phone, the images are the full partition size, not actual size.
Moto G6 (Ali - OPS27.104-15-10) Factory pulled files
Factory boot image - MotoG6-ali-factory-boot.img
Factory recovery image - MotoG6-ali-factory-recovery.img
Factory fstab.qcom file - factory-fstab.qcom
Click to expand...
Click to collapse
First off thank you for the work, this is incredible and I would love to donate.
And second, I am running the RetBr firmware as I softbricked my retus version, do you know how or where I could get the us firmware?
stifmaster81 said:
it serves for XTI 1925-4?
OPS 27.82-72
Enviado desde mi moto g(6) mediante Tapatalk
Click to expand...
Click to collapse
This is for the US version xt1925-6, but seems that it may work for you depending on the files
bird412 said:
First off thank you for the work, this is incredible and I would love to donate.
And second, I am running the RetBr firmware as I softbricked my retus version, do you know how or where I could get the us firmware?
This is for the US version xt1925-6, but seems that it may work for you depending on the files
Click to expand...
Click to collapse
I just want to install magic, I do not want to decrypt it at the moment, what I'm scared if it's boot.img will be useful for me, anyway if it goes wrong, installing the factory image
Enviado desde mi moto g(6) mediante Tapatalk
---------- Post added at 04:37 PM ---------- Previous post was at 04:35 PM ----------
anyway if something goes wrong, installing the factory image by adb is solved everything not?
Enviado desde mi moto g(6) mediante Tapatalk
stifmaster81 said:
I just want to install magic, I do not want to decrypt it at the moment, what I'm scared if it's boot.img will be useful for me, anyway if it goes wrong, installing the factory image
Enviado desde mi moto g(6) mediante Tapatalk
---------- Post added at 04:37 PM ---------- Previous post was at 04:35 PM ----------
anyway if something goes wrong, installing the factory image by adb is solved everything not?
Enviado desde mi moto g(6) mediante Tapatalk
Click to expand...
Click to collapse
I believe you are correct, that if you fastboot the original boot img it should fix any issues. Of course you should back up your data in the case that you need to completely reflash
someone could do this same but for the version OPS27.82-72 XTI 1925-4 ??
This did not work for me, I had to reinstall everything again, I would be very grateful
Same here
It didnt work for XT1925-2
Thanks anyway
But could anyone help us to do the same with the other varients pls :b as it seems it depends on it (and the boot img) (i had ALI_OPS27.82-72_cid50 in mine)
Btw thanks you again, all of you did a great job giving us a working TWRP, Root and magisk
(Just we need make it work for everyone )
Josio67 said:
Same here
It didnt work for XT1925-2
Thanks anyway
But could anyone help us to do the same with the other varients pls :b as it seems it depends on it (and the boot img) (i had ALI_OPS27.82-72_cid50 in mine)
Btw thanks you again, all of you did a great job giving us a working TWRP, Root and magisk
(Just we need make it work for everyone [emoji14] )
Click to expand...
Click to collapse
+1
Enviado desde mi moto g(6) mediante Tapatalk
---------- Post added at 07:40 PM ---------- Previous post was at 07:39 PM ----------
stifmaster81 said:
someone could do this same but for the version OPS27.82-72 XTI 1925-4 ??
This did not work for me, I had to reinstall everything again, I would be very grateful
Click to expand...
Click to collapse
Help us please
Enviado desde mi moto g(6) mediante Tapatalk
bird412 said:
First off thank you for the work, this is incredible and I would love to donate.
And second, I am running the RetBr firmware as I softbricked my retus version, do you know how or where I could get the us firmware?
Click to expand...
Click to collapse
@bird412 I do not currently. I have yet to see them posted anywhere. @Dadud had a similar (same?) issue and is now on a different bootloader as a result. If you give us a bit we can see about getting links for what you need (minus the bootloader) to see if we can get you mostly back to stock. I will not post pulled bootloader files at this time as I have zero clue if it could brick your device *permenantly* and I just don't want that on my conscience Can you let me know what all files you flashed?
For everyone else on different variants
Looks like we're going to have to do what @kwiksi1ver has done on G6 Play boot images, just slightly different. It will take a tiny bit more time per device.... Plus I'm about to go out for a bit so yeah, it'll still be a minute.
Firstly, does the TWRP image boot for you?
Secondly, if TWRP boots for you, I'd like for you to get me a couple of things:
A) I need you to pull the boot image following the steps in the first post and post a link here (along with your model number ie XT1925-#). I will see what I can do and try to find what's actually different so maybe we can avoid having to do this in the future.
B) If someone could pull the config.gz from the phone while booted in TWRP and post the model number you're using (XT1925-#) that may help.
Code:
adb pull /proc/config.gz
dejello said:
@bird412 I do not currently. I have yet to see them posted anywhere. @Dadud had a similar (same?) issue and is now on a different bootloader as a result. If you give us a bit we can see about getting links for what you need (minus the bootloader) to see if we can get you mostly back to stock. I will not post pulled bootloader files at this time as I have zero clue if it could brick your device *permenantly* and I just don't want that on my conscience [emoji14] Can you let me know what all files you flashed?
For everyone else on different variants
Looks like we're going to have to do what @kwiksi1ver has done on G6 Play boot images, just slightly different. It will take a tiny bit more time per device.... Plus I'm about to go out for a bit so yeah, it'll still be a minute.
Firstly, does the TWRP image boot for you?
Secondly, if TWRP boots for you, I'd like for you to get me a couple of things:
A) I need you to pull the boot image following the steps in the first post and post a link here (along with your model number ie XT1925-#). I will see what I can do and try to find what's actually different so maybe we can avoid having to do this in the future.
B) If someone could pull the config.gz from the phone while booted in TWRP and post the model number you're using (XT1925-#) that may help.
Code:
adb pull /proc/config.gz
Click to expand...
Click to collapse
If you tell me the steps that I have to do I will try to take mine out of my variant XTI 1925-4
Enviado desde mi moto g(6) mediante Tapatalk
---------- Post added at 08:21 PM ---------- Previous post was at 08:14 PM ----------
stifmaster81 said:
If you tell me the steps that I have to do I will try to take mine out of my variant XTI 1925-4
Enviado desde mi moto g(6) mediante Tapatalk
Click to expand...
Click to collapse
Tell me the steps to remove from the phone the configuration you are asking me please
Enviado desde mi moto g(6) mediante Tapatalk
dejello said:
@bird412 I do not currently. I have yet to see them posted anywhere. @Dadud had a similar (same?) issue and is now on a different bootloader as a result. If you give us a bit we can see about getting links for what you need (minus the bootloader) to see if we can get you mostly back to stock. I will not post pulled bootloader files at this time as I have zero clue if it could brick your device *permenantly* and I just don't want that on my conscience Can you let me know what all files you flashed?
For everyone else on different variants
Looks like we're going to have to do what @kwiksi1ver has done on G6 Play boot images, just slightly different. It will take a tiny bit more time per device.... Plus I'm about to go out for a bit so yeah, it'll still be a minute.
Firstly, does the TWRP image boot for you?
Secondly, if TWRP boots for you, I'd like for you to get me a couple of things:
A) I need you to pull the boot image following the steps in the first post and post a link here (along with your model number ie XT1925-#). I will see what I can do and try to find what's actually different so maybe we can avoid having to do this in the future.
B) If someone could pull the config.gz from the phone while booted in TWRP and post the model number you're using (XT1925-#) that may help.
Code:
adb pull /proc/config.gz
Click to expand...
Click to collapse
thank You for your help, I am gonna try to find out what @kwiksi1ver did to modify the boot.img.
But in every case here are the files for XT1925-5
dejello said:
@bird412 I do not currently. I have yet to see them posted anywhere. @Dadud had a similar (same?) issue and is now on a different bootloader as a result. If you give us a bit we can see about getting links for what you need (minus the bootloader) to see if we can get you mostly back to stock. I will not post pulled bootloader files at this time as I have zero clue if it could brick your device *permenantly* and I just don't want that on my conscience Can you let me know what all files you flashed?
Click to expand...
Click to collapse
I downloaded the firmware from this and flashed it using the code provided in the op. Later in the thread someone uploaded some files from their RetUS phone but I could not get past their encryption passwords
nightmw said:
thank You for your help, I am gonna try to find out what @kwiksi1ver did to modify the boot.img.
But in every case here are the files for XT1925-5
Click to expand...
Click to collapse
Can you help me make mine? What steps do I have to do, thanks
Enviado desde mi moto g(6) mediante Tapatalk
nightmw said:
thank You for your help, I am gonna try to find out what @kwiksi1ver did to modify the boot.img.
But in every case here are the files for XT1925-5
Click to expand...
Click to collapse
Thanks for doing this...Stifmaster hold on buddy, it's going to be okay, breath.
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
what to put who ... by-name / boot adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
what to put who . ... by-name/boot para el motog6 ali xti 1925-4
[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.
Disclaimer :
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
If you point the finger at me for messing up your device, I will laugh at you. Hard. A lot
Warranty will be VOID
UNLOCK BOOTLOADER AND ROOT ASUS ZENFONE MAX PLUS M2
<Device will be formatted, so keep a backup >
Requirements :
Asus Zenfone Max Plus M2
Windows
Instructions :
//unlocking
Phone:
- Go to Setting > System > About Phone and tap on the build number until developer option appears
- Go back to Settings > System > Developer options and enable usb debugging ( If you had already enabled usb debugging, ignore this step)
Windows:
- Download "unlocker" and extract the files
- Install ADB and necessary drivers
- Connect the device to PC on a USB 2.0 port
- Go to "unlock" folder and open an Elevated command promt there and enter :
Code:
adb devices
( Allow usb debugging box will appear, check "always allow debugging from this computer" and click OK ) and again enter
Code:
adb devices
(Device should be listed)
Code:
adb reboot bootloader
(Device will now enter fastboot )
Code:
fastboot devices
(Device should be listed )
Now execute unlocker.cmd
Thats it, Bootloader is unlocked
You can check the bootloader status by
Code:
fastboot oem device-info
Credits
@legacy07
Downloads:
Unlocker
Thanks Brazilian Team in telegrama group: Matheus Vinicius and Mago Implacável
Hi,
Do i need to be on android 9 for this to work ?
Thanks.
arcane07 said:
Hi,
Do i need to be on android 9 for this to work ?
Thanks.
Click to expand...
Click to collapse
Not necessarily
legacy07 said:
Not necessarily
Click to expand...
Click to collapse
some one... already test?
Thanks
Worked fine on ZenFone Max plus m2 :good:
will this work with zb633kl?
pococount said:
will this work with zb633kl?
Click to expand...
Click to collapse
You can try the tool of zb631kl under yourown risk:good:
Can someone make a tool for the Max Plus M1 (WW version). I have the official unlock tool but doesn't seem to work anymore as ASUS official site removed the download page for the apk. Can someone tweak the insides of the apk tool to just unlock the phone's bootloader without tapping into ASUS?
Yes please, can you make unlock tool for asus max plus m1
CleanBoot Project Galaxy A20
Code:
/*
* Your warranty is now void.
* I am not responsible for any damages, you do everything at your own risk
*/
Here you will find files .tar containing the param file for variants of the Galaxy A20 mobile, this modified param file is free of all warning messages about "unlocked bootloader" and "unofficial software", all files come from One UI 3.1, if your model is missing, wait I'll add them all over time
Installation process
- Download the correct file for your model
- Open Odin on your computer, you can download it here
- Put the modified bootlogo, which you downloaded, to AP
- Press "start", the mobile should restart to recovery itself with the modifed bootlogo
Download links for different models
SM-A202F
SM-A205F
SM-A205U
Awesome work. I just installed on SM-A202F and worked perfectly! Thanks a ton man.
Installed on A202F and worked with no problems! rep
for A20S?
rejpr-dev said:
CleanBoot Project Galaxy A20
Code:
/*
* Your warranty is now void.
* I am not responsible for any damages, you do everything at your own risk
*/
Here you will find files .tar containing the param file for variants of the Galaxy A20 mobile, this modified param file is free of all warning messages about "unlocked bootloader" and "unofficial software", all files come from One UI 3.1, if your model is missing, wait I'll add them all over time
Installation process
- Download the correct file for your model
- Open Odin on your computer, you can download it here
- Put the modified bootlogo, which you downloaded, to AP
- Press "start", the mobile should restart to recovery itself with the modifed bootlogo
Download links for different models
SM-A202F
SM-A205F
SM-A205U
Click to expand...
Click to collapse
this file suport for a205f -binary B or not sir ?