this is the first Ive heard of this.... Is this true? what should a person do? buy GPE or unlocked version? or is there hope?
Buy GPE I'd say.
Sent from my XT1033 using Tapatalk
this is the first Ive heard of this.... Is this true? what should a person do? buy GPE or unlocked version? or is there hope?
Unless a dev finds's a way to manually unlock. There is a keygen thread going on where someone is trying to figure out the algorithm. Boost Mobile is also a CDMA version of the Moto G, but does allow unlock.this is the first Ive heard of this.... Is this true? what should a person do? buy GPE or unlocked version? or is there hope?
Update 6.13.3 - One recovery for all devices: migrate to common device
falcon: compatible with xt1028, xt1031, xt1032, xt1033, xt1034
@Phil3759
may i include your recovery in my MotoTool, i'm developing a new version, and i like to know if you give me permission to add your recovery to my tool... what do you think?
This recovery is truly amazing but pleeeease add the google play edition. It is working but the /sdcard won't mount
Gesendet von meinem XT1032 mit Tapatalk
So what's the recommended way to install this on an unlocked bootloader with stock recovery?
This works?
Or unzip the file and use fastboot flash recovery recovery.img ?
Couldn't get an answer. I see lots of people in here using this CWM, but not one can be bothered to tell what is the recommended way to install it.
And what do you expect it to do, on a non USB mass storage device?
That's what I keep telling to people!
They think they have just found a bug while it's simple hardware limitation.
It's about time for them to learn that the moto g can not mount emulated storage. No device does that.
Enviado de meu XT1033 usando Tapatalk
I've been added on to this post as a contributor, so now you can direct blame my way. (Oh yeah, I'm @Hachamacha on this board.) All credits to Phil3759 and the guys the made CM11 happen.
Just added the 6.58.7 build (see main thread) and has a number of enhancements and is likely the final build for months: You can download from the usual spot in either .img or .zip format. Keep in mind that on this device I'm just a builder and don't have any of the "moto g" devices myself so all testing is in your hands.
Update v6.57.8 / CWM 6.0.5.1 / libtouch_gui 1.41
- fix for ROM OTA updates generating two install scripts (openrecovery + extendedcommands)
- merge CWM updates to selinux permissions for init services
- fix adb for 3.10 kernel
6.57.5
- Update SuperSU
- merge a few SR/CWM changes and bug fixes
- fix aroma file manager issue with some slow mount/unmount devices
6.55.0
-add option to disable md5 from edify restore_rom command line
- this fixes restore of custom roms
6.54.9 - libtouch_gui 1.40
- support faster transfers through USB storage for voldmanaged devices
- fix compiling for devices with custom recovery key or ui files
-- This version adds many enhancements in the code to better support storage volumes
-- USB mount should have now good transfer speeds for vold volumes if you add needed entries in extra.fstab
Notes regarding 6.50.6:
- fix potential failure for TWRP backups (cause scan_mouned_volumes() not called)
- loki_recovery code clean up
- fix potential failure to reboot when checking config file
- never confirm wipe in ors scripts
- always show text in sideload mode
- support wipe_cache and clear_display edify script commands
Notes regarding 6.41.6:
- update exfat to dorimanx 1.2.9 latest sources
- fix compile error when enabling BOARD_RECOVERY_USE_BBTAR
- repo sync latest sources
- Galaxy Tab Pro 8.4 WiFi SM-T320 (mondrianwifi)
- HTC M7 variants: use new cm kernel with exfat sources
- HTC M8 variants: use new unified recovery
6.41.5 - Stable
- libtouch_gui 1.21: auto detect BRIGHTNESS_SYS_FILE path if it is not set during compile
* search for the file in most common locations
* if found, save it to recovery settings ini file to be called on next recovery starts
* else, disable adjust brightness function to avoid error logs on recovery start
- fix various compiler warnings and errors
- enhance pre-compile setup
- dedupe: merge clean up code from @xiaolu
- merge: fix restorecon_from_file potential crash from @xiaolu (only for BOARD_RECOVERY_USE_BBTAR)
- fix 240x320 images
- merge "cwm: Honor recovery variant "
- merge "cwm: Remove hardcoded paths"
- merge "Keep 'show log' on screen until user dismisses it"
- create /data/media directory after internal storage is wiped
prevents denial to read/write from internal storage under some circumstances
- open source touch_gui library
- update licence files
Moto G (falcon)
- Unified device for xt1028, xt1031, xt1032, xt1033, xt1034, Google Play Edition: falcon
Build Links:6.58.7: Img: http://d-h.st/DEw : Zip: http://d-h.st/Dbh
Build links: 6.57.9 : Img : http://d-h.st/kgN : Zip : http://d-h.st/Unh
Build links: 6.57.8 : Img : http://d-h.st/FLK : Zip : http://d-h.st/vzql
Build links: 6.57.5 : Img : http://d-h.st/lTD : Zip : http://d-h.st/D8y
Build links: 6.55.0 : Img : http://d-h.st/ljR : Zip : http://d-h.st/Seu
Build links: 6.54.9 : Img : http://d-h.st/3GH : Zip : http://d-h.st/N6G
Build links: 6.50.6 : Img : http://d-h.st/Lwx : Zip : http://d-h.st/F8Y
Build links: 6.41.6 : Img : http://d-h.st/LmY : Zip : http://d-h.st/KUS
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
I've found similar results. I don't understand how "Philz" manages to keep updating his ROM without ever fixing any of this ****. I tried complaining in the main Philz thread but didn't get anywhere.