[TWRP] Moto Maxx Only - XT1225 - test builds only

respider

Senior Member
Sep 18, 2008
700
235
0
Sao Paulo
First of all, I'm not responsible for any damage to your phone if you use anything in this topic.

This is only for Moto Maxx xt1225 with unlocked bootloader.

It's not adviseable to use this version with Lollipop. Source

I'm warning you I'm not an android developer. I'm building TWRP for myself since we don't have any custom recovies for our phone yet.
These are just test builds, many things are broken, that's why I do not recommend flashing these recoveries. Specially Backup/Restore.

@Gundabolu SC has successfully booted via fastboot (fastboot boot recovery.img) and flashed Super SU, but that's all for now. Touch recognition is still buggy, backup is not functional, etc.

If you are one of those guys that don't read OP and warnings and end up bricking your phone, I'm sorry, you have only yourself to blame.
I haven't made any source changes, this is purely TWRP with some configurations to boot into our XT1225.

Apparently works:
- Flashing zips like supersu

Not working:
- Touch is not functional when you boot the recovery. Wait for screen timeout and then it might work.
- Backup is not working. Error:

- Everything else just in case

I would appreciate if any real developer starts supporting TWRP. Just let me know and I'll close this thread.

So here's the first build:
**removed**

Edit November 30th 2014:

I managed to fix the touch issue, now it's ok.
Apparently backing up is fine as well. OTG works too.

I personally havent tested restoring backups and still don't advise to, but looks like @Gundabolu SC has. Thanks for your help.

How to use:
- Extract attached zip file
- Boot your phone to booloader (adb reboot bootloader)
- Boot the extracted img file (fastboot boot file-name.img) or if you want to flash it (fastboot flash recovery file-name.img)
 

Attachments

Last edited:

respider

Senior Member
Sep 18, 2008
700
235
0
Sao Paulo
new build:

https://drive.google.com/file/d/0B9LJnNqd94eNUGNOMmJpLUVlV1E/view?usp=sharing

changes in this build were basically:


  • Changing paths in PRODUCT_COPY_FILES array to copy a lot of important(?) files to ramdisk's root, like fstab.qcom (device.mk)

  • Removed two flags from BoardConfig.mk:
    - TW_INTERNAL_STORAGE_PATH
    - TW_INTERNAL_STORAGE_MOUNT_POINT
    - these flags are usually used for devices with dual storages, not our case. Besides that, Moto X 2014 boardconfig doesnt have this flags as well.

  • Added some other flags:
    - BOARD_HAS_NO_SELECT_BUTTON := true
    - TARGET_USERIMAGES_USE_EXT4 := true
    - TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"
    - RECOVERY_SDCARD_ON_DATA := true
    - TW_DISABLE_TTF := true
    - TW_SCREEN_BLANK_ON_BOOT := true
    - TW_NO_EXFAT_FUSE := true
    - TW_EXCLUDE_ENCRYPTED_BACKUPS := true
 

Gundabolu SC

Senior Member
Sep 9, 2013
491
309
0
new build:

https://drive.google.com/file/d/0B9LJnNqd94eNUGNOMmJpLUVlV1E/view?usp=sharing

changes in this build were basically:


  • Changing paths in PRODUCT_COPY_FILES array to copy a lot of important(?) files to ramdisk's root, like fstab.qcom (device.mk)

  • Removed two flags from BoardConfig.mk:
    - TW_INTERNAL_STORAGE_PATH
    - TW_INTERNAL_STORAGE_MOUNT_POINT
    - these flags are usually used for devices with dual storages, not our case. Besides that, Moto X 2014 boardconfig doesnt have this flags as well.

  • Added some other flags:
    - BOARD_HAS_NO_SELECT_BUTTON := true
    - TARGET_USERIMAGES_USE_EXT4 := true
    - TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"
    - RECOVERY_SDCARD_ON_DATA := true
    - TW_DISABLE_TTF := true
    - TW_SCREEN_BLANK_ON_BOOT := true
    - TW_NO_EXFAT_FUSE := true
    - TW_EXCLUDE_ENCRYPTED_BACKUPS := true
Doesnt boot anymore! :( Stuck at Motorola screen! b4 it used to stay blank...
 

respider

Senior Member
Sep 18, 2008
700
235
0
Sao Paulo
  • Like
Reactions: [email protected]

Gundabolu SC

Senior Member
Sep 9, 2013
491
309
0
this one is more similar with the first one that booted, I'm just copying fstab.qcom and removing those INTERNAL_STORAGE flags

https://drive.google.com/file/d/0B9LJnNqd94eNQ0ZnZ1ZvS1h6SGM/view?usp=sharing

if you are gonna try this and it didnt boot, let me know if there's a /tmp/recovery.log file
This boots, but guess you removed the "TW_SCREEN_BLANK_ON_BOOT := true" flag as well so touch doesn't work!! And the error:13 Failed to create backup folder is still there.. At this point in time probably its better to add one flag at a time and test it...

Try just these flags.....
TW_SCREEN_BLANK_ON_BOOT := true
RECOVERY_SDCARD_ON_DATA := true
BOARD_HAS_NO_REAL_SDCARD := true
 
Last edited:

respider

Senior Member
Sep 18, 2008
700
235
0
Sao Paulo
This boots, but guess you removed the "TW_SCREEN_BLANK_ON_BOOT := true" flag as well so touch doesn't work!! And the error:13 Failed to create backup folder is still there.. At this point in time probably its better to add one flag at a time and test it...

Try just these flags.....
TW_SCREEN_BLANK_ON_BOOT := true
RECOVERY_SDCARD_ON_DATA := true
BOARD_HAS_NO_REAL_SDCARD := true
when do you get the error?
when click BACKUP in the main menu or when SWIPE to backup?
 

respider

Senior Member
Sep 18, 2008
700
235
0
Sao Paulo
Swipe to backup....

---------- Post added at 05:34 PM ---------- Previous post was at 05:25 PM ----------


You still want the recovery log file?
nope that's ok
I've just unlocked my bootloader and I'm testing myself

I've fixed the touch and trying to figure out backup error
it's a permission problem as you said earlier, no idea why yet. It's mounted correctly, we can see the /sdcard files from recovery but can't write

Code:
/sdcard # echo a > b
echo a > b
/sbin/sh: can't create b: Permission denied
/sdcard #
fstab looks fine though :confused:

I have successfully backed up to a OTG partition using a flash drive :good:
internal sd is the problem :eek:
 

Gundabolu SC

Senior Member
Sep 9, 2013
491
309
0
nope that's ok
I've just unlocked my bootloader and I'm testing myself

I've fixed the touch and trying to figure out backup error
it's a permission problem as you said earlier, no idea why yet. It's mounted correctly, we can see the /sdcard files from recovery but can't write

Code:
/sdcard # echo a > b
echo a > b
/sbin/sh: can't create b: Permission denied
/sdcard #
fstab looks fine though :confused:

I have successfully backed up to a OTG partition using a flash drive :good:
internal sd is the problem :eek:
Ohhh... Thats awesome! Yeah even i checked the fstab.... It looks almost identical to the Moto X 2014... Maybe we should take a look at Nexus 6's recovery once?

I:Set page: 'backup'
I:Set page: 'backup_run'
Updating partition details...
I:Data backup size is 1726MB, free: 17419MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done

I:Backup Name is: '2014-11-28--22-19-29 KXG21.50-9'
I:Full_Backup_Path is: '/data/media/0/TWRP/BACKUPS/XXXXXXXX/2014-11-28--22-19-29 KXG21.50-9/'
I:Calculating backup details...
* Total number of partitions to back up: 1
* Total size of all data: 16MB
* Available space: 17419MB

Why is it just mounting the USB and not the data partition?
 
Last edited:

Gundabolu SC

Senior Member
Sep 9, 2013
491
309
0
it was mounting data correctly you can check under advanced filemanager, you'll probably see your files.

I believe the problem was enforcing should be set to permissive

I just managed to backup to internal sd card but I'm not willing to test recover hahaha

I *think* it's fixed :)

https://docs.google.com/file/d/0B9LJnNqd94eNQmlsWmJGMTYxNkE/edit?usp=docslist_api
It is perfect now!!! Backup restore, flashing zips, touch and everything works!!! :) :) :)
Time to update the OP with this link...
 
  • Like
Reactions: judaxxx