Using the newset build, unified falcon and falcon_gpe, version 6.19.3 and i get an error. My device is normal us global moto g, converted to the gpe edition with the official image using fastboot. So it must have the partition table of the gpe device and data sould be ext4. the new recovery should identify this and change the filesystem as it boots, but on my device i get the error that it cannot mount the data partition, as if i had used a moto g recovery to a moto g gpe phone. But the new version should not have this problem. Don't know if it is a known problem, or it has to do with the fact that mine is a converted gpe and not an original gpe. I have rolled back to the last gpe version until it is fixed.
thanks for an awesome recovery btw.
I am not using a custom gpe rom. I am using the official GPE factory image, flashed with fastboot. So i must have the binary you are describing. I don't know why it doesn't recognize it correctly as a gpe device.
Sure, for now i have reverted back to the older version that works fine. Hope someone with an original gpe device can give some more info.
Using Aroma FM and the latest 6.19.3, the screen becomes garbled. You can see the recovery wallpaper mixed with the aroma theme colour. It did not happen with previous versions....
Can someone help me I cannot wipe data/media on philz recovery and my phone is stuck on a boot loop
hi phil, may be you know what Im doing wrong, Im on stock 4.4.2 173.44.9.falcon_umts.movistar.en.CL, ROOTED and Ive tryed to upgrade to Blur_Version.172.44.4.falcon_umts.Retail.en.US from your recovery 6.13.9 - falcon with no success, operation aborted just after opening package, selected by flash zip from sdcard..of course my model is 1032, Any advice? TIA
Afaik, If you are trying to flash an official Moto package, it only will work using fastboot or Stock recovery...
No. I have flashed automatically last ota on my en.EU firmware with Philz recovery and stock system.img partition. There is no need to reflash stock recovery, you need only of a unmodded system partition with no root and no other change.
hi phil, may be you know what Im doing wrong, Im on stock 4.4.2 173.44.9.falcon_umts.movistar.en.CL, ROOTED and Ive tryed to upgrade to Blur_Version.172.44.4.falcon_umts.Retail.en.US from your recovery 6.13.9 - falcon with no success, operation aborted just after opening package, selected by flash zip from sdcard..of course my model is 1032, Any advice? TIA
No. I have flashed automatically last ota on my en.EU firmware with Philz recovery and stock system.img partition. There is no need to reflash stock recovery, you need only of a unmodded system partition with no root and no other change.
Correct me if I'm wrong, but I guess xnewuser is trying to make a full install of a new ROM version (Retail.en.US), not just upgrading the same he has installed (movistar.en.CL), so that's the reason he will need the Stock Recovery to make it.
Or if he's just upgrading Retail.en.US over movistar.en.CL it's normal it doesn't work...
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.