• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Does anyone know if the moto g LTE will be able to be rooted or have CyanogenMod?

If you are a moto G LTE owner or have any relevant information, please reply!

Let's get this discussion started, please!

The phone still needs TWRP and CWM to create custom recoveries that will work on it. The recoveries for the Moto G will not work. If anyone knows someone at either one of those groups, it would be greatly appreciated if you could mention to them that custom recoveries need to be created for the XT1045.
 
Upvote 0
Ok so i looked into this all cuz someone pm'd me.

Download these:

http://goo.im/devs/OpenRecovery/xt1032/openrecovery-twrp-2.7.1.1-xt1032.img
http://download.chainfire.eu/396/SuperSU (put this on yourphone)

Unlock your bootloader via moto site.

fastboot boot openrecovery-twrp-2.7.1.1-xt1032.img

Once in recovery flash the supersu zip and youll be rooted. credits for this info came from http://forum.xda-developers.com/showthread.php?p=53313307 where it came from originally i dont know.

This will give you root, but not recovery, chances are the dtb files are mismatched and prevents flashing, once you have root someone can dump recovery and then CWM/TWRP can be ported :)
 
Upvote 0
Ok so i looked into this all cuz someone pm'd me.

Download these:

Goo.im Downloads - Downloading openrecovery-twrp-2.7.1.1-xt1032.img
SuperSU Download (put this on yourphone)

Unlock your bootloader via moto site.

fastboot boot openrecovery-twrp-2.7.1.1-xt1032.img

Once in recovery flash the supersu zip and youll be rooted. credits for this info came from Moto G LTE Delayed? - Page 5 - xda-developers where it came from originally i dont know.

This will give you root, but not recovery, chances are the dtb files are mismatched and prevents flashing, once you have root someone can dump recovery and then CWM/TWRP can be ported :)

Thank you! Another Xda member also got root using this method! :thumbup:

[Q] Rooting Moto G LTE - Post #10 - XDA

Here is a dump of the stock recovery.

http://forum.xda-developers.com/showpost.php?p=53409014&postcount=1
 
  • Like
Reactions: USCanthony
Upvote 0
Ok so i looked into this all cuz someone pm'd me.

Download these:

Goo.im Downloads - Downloading openrecovery-twrp-2.7.1.1-xt1032.img
SuperSU Download (put this on yourphone)

Unlock your bootloader via moto site.

fastboot boot openrecovery-twrp-2.7.1.1-xt1032.img

Once in recovery flash the supersu zip and youll be rooted. credits for this info came from Moto G LTE Delayed? - Page 5 - xda-developers where it came from originally i dont know.

This will give you root, but not recovery, chances are the dtb files are mismatched and prevents flashing, once you have root someone can dump recovery and then CWM/TWRP can be ported :)

Thanks for the info Shabby. I have not tried this yet but have heard from several people that have and it did work. I have been told that you must do this from a Windows or Linux PC. Mac's will not work.

Just to clarify the instructions......

The "openrecovery-twrp-2.7.1.1-xt1032.img" file should either be in the same directory that fastboot resides in on your PC or in another directory that is in the path. If you do not understand what I mean by a directory being in the path, just put it in the same directory that fastboot is in.
 
Upvote 0
Just rooted my phone using the method Shabby listed above. It worked perfectly. Just keep in mind that this method simply installs the files needed for SU access and it does not replace the stock recovery. This should not be a big deal right now since there are not any custom ROM's for this phone yet and the ability to flash custom ROM's is what a custom recovery brings to the party. Having the phone rooted will give you many more options even if you can't flash a ROM yet. You can install the Xposed framework and then chose to do some really cool things with individual Xposed modules. You can install an app like Titanium Backup and sleep better at night knowing your phone is being backed up regularly. If you are an audio nut like me, you can install viper4android and once again your expensive earbuds will have a device that can serve up sound worthy of the price you paid for them (this alone is a "must root" reason). Remember to install Busybox from the Play Store as well. For those of you that want or need a little more command clarification, I am listing the commands I did from a command prompt on my Windows PC after I had attached my phone to the PC via it's USB cable (remember to have USB debugging checked in the developer options). The actual commands listed below that I entered at a command prompt are between the quotes " ". Do not include the quotes when you enter these commands on your computer.

1- "adb devices" (Use this command to ensure your phone is being properly recognized by the computer. It should return something like TA95000WAX device. If it says unauthorized instead of device, look at your phones screen. There should be a popup asking if you want to authorize that computer.

2- "adb reboot bootloader" (this command will reboot your phone into bootloader mode and you will see the stock recovery displayed on your phones screen)

3 - "fastboot boot openrecovery-twrp-2.7.1.1-xt1032.img" (this command will load the TWRP recovery as if it is actually running on your phone and you will see TWRP's recovery displayed on your phones screen.

Those are the commands you need to enter at your PC's command prompt. Once the TWRP recovery is displayed on your phones screen, you can then select install and browse to where you had copied Shabby's Update-SuperSU zip file on your phone and then flash that file. Once the file flashes successfully you can then select the reboot to system option from TWRP and disconnect your phone from your computer. That is it....you are now rooted.

- Anthony
 
Upvote 0
Thank you! Another Xda member also got root using this method! :thumbup:

[Q] Rooting Moto G LTE - Post #10 - XDA

Here is a dump of the stock recovery.

[Q] [REQ] Is anyone able to port a custom recovery for Moto G LTE (xt1045)? - Post #1 - XDA

thats a bad copy, its not unpacking.

adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img

that will give me a recovery i should be able to work my magic with and get a basic cwm working and go from there. dhacker was the one pushing for all the moto devices but it seems he is busy on the nokia x and moto e. seems this device has fallen through the cracks :p
 
Upvote 0
thats a bad copy, its not unpacking.

adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img

that will give me a recovery i should be able to work my magic with and get a basic cwm working and go from there. dhacker was the one pushing for all the moto devices but it seems he is busy on the nokia x and moto e. seems this device has fallen through the cracks :p

Shabby,

I just pulled a copy of the stock recovery off of my phone and put it up in my Dropbox at the link below. See if you have better luck with this copy.

https://dl.dropboxusercontent.com/u/47843318/recovery.img
 
  • Like
Reactions: Tesla5
Upvote 0
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KXB21.14-L1.23-4
ro.build.display.id=KXB21.14-L1.23-4
ro.build.version.incremental=1
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.3
ro.build.date=Fri May 23 16:31:23 CDT 2014
ro.build.date.utc=1400880683
ro.build.type=user
ro.build.user=hudsoncm
ro.build.host=ilclbld31
ro.build.tags=release-keys
ro.product.model=XT1045
ro.product.brand=motorola
ro.product.name=peregrine_retus
ro.product.device=peregrine
ro.product.board=MSM8226
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8226
# ro.build.product is obsolete; use ro.product.device
ro.build.product=peregrine
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=peregrine_retus-user 4.4.3 KXB21.14-L1.23-4 1 release-keys
ro.build.fingerprint=motorola/peregrine_retus/peregrine:4.4.3/KXB21.14-L1.23-4/1:user/release-keys
ro.build.characteristics=default
# end build properties
#
# from device/moto/peregrine/system.prop
#
#
# system.prop for msm8226
#

# Use reference RIL for initial bringup
#rild.libpath=/system/lib/libreference-ril.so
rild.libpath=/vendor/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
persist.radio.msgtunnel.start=false

#
# system props for the cne module
#
persist.cne.feature=0


# Skip /sys/power/wait_for_fb_* nodes and
# force FB to be always on
debug.sf.fb_always_on=1

debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=c2d
persist.hwc.mdpcomp.enable=true
debug.mdpcomp.logs=0
dalvik.vm.heapsize=36m
dev.pm.dyn_samplingrate=1

persist.demo.hdmirotationlock=false
ro.hdmi.enable=true
tunnel.decode=false
tunnel.audiovideo.decode=false
lpa.decode=true
lpa.use-stagefright=true

#system props for the MM modules

media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
#9273 is decimal sum of supported codecs in AAL
#codecs:(PARSER_)AVI AC3 ASF AAC QCP DTS 3G2 MP2TS
mm.enable.qcom_parser=37491

# VIDC: debug_levels
# 1:ERROR 2:HIGH 4:LOW 0:NOlogs 7:AllLogs
vidc.debug.level=1
#
# system props for the data modules
#
ro.use_data_netmgrd=true

#system props for time-services
persist.timed.enable=true

#
# system prop for opengles version
#
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608

#
# System props for telephony
# System prop to turn on CdmaLTEPhone always
telephony.lteOnCdmaDevice=0

# simulate sdcard on /data/media
#
persist.fuse_sdcard=true
ro.crypto.fuse_sdcard=true

#
#snapdragon value add features
#
# System props for audio
ro.qc.sdk.audio.ssr=false
##fluencetype can be "fluence" or "fluencepro" or "none"
persist.audio.fluence.mode=endfire
persist.audio.handset.mic=digital
ro.config.vc_call_vol_steps=7
# FM maximum volume be between 0 and 8192 (0dB)
ro.audio.fm_max_volume=4096

#need rotation info in audio-land
ro.audio.monitorRotation=1

# Enable/disable cabl
ro.qualcomm.cabl=0

# system prop for NFC DT
ro.nfc.port=I2C

#
# system property for Bluetooth hci transport
#
ro.qualcomm.bt.hci_transport=smd

#
# system property for Bluetooth HFP version
#
ro.bluetooth.hfp.ver=1.6

#
# system property for Bluetooth SAP support
# Motorola disabled SAP
#
ro.qualcomm.bluetooth.sap=false

# Bluetooth LE power class
qcom.bt.le_dev_pwr_class=1

##property to choose between virtual/external wfd display
persist.sys.wfd.virtual=0
# Motorola, ams087, 09/24/2013, IKJBMR2-6432 : disable tunnel audio encode
#tunnel.audio.encode = true

# Enable SSR
persist.sys.ssr.restart_level=3
persist.sys.qc.sub.rdump.on=1

# For TCMD debug level
persist.tcmd.log.limit=0

# Disable QCOM net early sockets feature
net.early.sockets=0

# Radio RIL properties
persist.radio.no_wait_for_card=1
persist.radio.call_type=1
persist.radio.apm_sim_not_pwdn=1
persist.radio.dfr_mode_set=1
persist.radio.relay_oprt_change=1

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.build.version.full=Blur_Version.21.23.4.peregrine_retus.retus.en.US
ro.mot.build.customerid=retus
ro.mot.build.version.sdk_int=19
ro.product.display=Moto G
ro.build.version.qcom=AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1.04.04.02.048.020
ro.carrier=retus
ro.fsg-id=retusa_glb
telephony.lteOnCdmaDevice=0
ro.telephony.default_network=9
ro.mot.hw.uaprof=http://uaprof.motorola.com/phoneconfig/motomb886/Profile/motomb886.rdf
ro.com.android.dataroaming=false
ro.config.ringtone=Moto.ogg
ro.config.notification_sound=Moto.ogg
ro.config.alarm_alert=Oxygen.ogg
ro.MAX_HIDDEN_APPS=12
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
persist.sys.logkit.ctrlcode=0
ro.vendor.extension_library=/vendor/lib/libqc-opt.so
persist.radio.apm_sim_not_pwdn=1
ro.usb.mtp=0x2e82
ro.usb.mtp_adb=0x2e76
ro.usb.ptp=0x2e83
ro.usb.ptp_adb=0x2e84
ro.usb.bpt=0x2e28
ro.usb.bpt_adb=0x2e29
ro.usb.bpteth=0x2e2a
ro.usb.bpteth_adb=0x2e2b
persist.audio.calfile0=/etc/Bluetooth_cal.acdb
persist.audio.calfile1=/etc/General_cal.acdb
persist.audio.calfile2=/etc/Global_cal.acdb
persist.audio.calfile3=/etc/Handset_cal.acdb
persist.audio.calfile4=/etc/Hdmi_cal.acdb
persist.audio.calfile5=/etc/Headset_cal.acdb
persist.audio.calfile6=/etc/Speaker_cal.acdb
ro.bug2go.magickeys=24,26
persist.sys.qc.sub.rdump.max=0
ro.adb.secure=1
ro.sf.lcd_density=320
keyguard.no_require_sim=true
ro.zygote.capsuid=0
mdc_initial_max_retry=10
persist.radio.apn_delay=5000
drm.service.enabled=true
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.ms=android-motorola
ro.com.google.clientidbase.am=android-motorola
ro.com.google.clientidbase.gmm=android-motorola
ro.com.google.clientidbase.yt=android-motorola
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.4.3_r1
ro.media.enc.aud.fileformat=amr
ro.media.enc.aud.codec=amrnb
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.qc.sdk.izat.premium_enabled=1
ro.qc.sdk.izat.service_mask=0x5
persist.gps.qc_nlp_in_use=1
persist.loc.nlp_name=com.qualcomm.services.location
ro.gps.agps_provider=1

worked ;)
 
  • Like
Reactions: Tesla5
Upvote 0
Thanks :)

ill try twrp here in a few more tests, they have cwm working on the nonlte while twrp requires a lot more work and can have all sorts of issues clear out of teh blue. the last moto phone i had was a tegra 2 2.3 device so im not up to date on all how they work etc so it may take a bunch of tries :p

obviously would be a lot faster if some of the dudes who had the original g and did the work, but for now all you got is me :p

the good thing is with sdcard slot you guys can get a unbrick image and never really brick :p
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones