This is my version of TWRP built for the 2015 Moto X Play. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, turn off your device, hold PWR and VolDn for 3 seconds, then let go.
Differences between upstream TWRP and my fork:
My original green theme
No SuperSU
No TWRP app
No HTC Dumlock cruft
Updated pigz compressor (slightly faster and more tolerant of corruption)
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is up on the downloads tab.
XDA:DevDB Information
TWRP, Tool/Utility for the Moto X Play
Contributors
vache, squid2
Source Code: https://github.com/sultanqasim/android_device_motorola_lux
Version Information
Status: Stable
Current Stable Version: 3.2.3-r1
Stable Release Date: 2018-08-16
Created 2015-09-05
Last Updated 2018-08-16
Reserved
2015-09-17 :
-Fix flashing custom zips
Gr8!!
Is this actually built for X Play? I know it sounds silly but there's no kernel source yet is there? Or do we not need that to build recovery?
Sent from my Vodafone Smart ultra 6 using Tapatalk
Yes it's build for X Play, based on G 2015 device tree. I'm using MSM8916 generic kernel from Motorola, modded by @squid2 (https://github.com/sultanqasim/android_kernel_motorola_msm8916)
Ahh that's great. Thanks for this my device should be delivered tomorrow so I'll be definitely using this.
We will still need kernel source for cm12 etc though surely?
Sent from my Vodafone Smart ultra 6 using Tapatalk
TWRP working fine here on XT1562
I'm making a stock TWRP Backup + some partition dump
Next move will be starting playing with CM12.1
ephumuris said:
Ahh that's great. Thanks for this my device should be delivered tomorrow so I'll be definitely using this.
We will still need kernel source for cm12 etc though surely?
Sent from my Vodafone Smart ultra 6 using Tapatalk
Click to expand...
Click to collapse
Yes i think we'll have to wait for kernel sources to get a working custom.
Already build one (SOKP) but cannot get it to boot (with stock kernel or msm8916 kernel)
Shreps said:
TWRP working fine here on XT1562
I'm making a stock TWRP Backup + some partition dump
Next move will be starting playing with CM12.1
Click to expand...
Click to collapse
can you please upload your dumps and backups if there are ready for it?
i have a broken XT1562 without a nandroid or other backups...
thanks
Thanks for this Vache! However, just to let you know this is still showing as Moto G 2015 when plugged into my PC whilst in recovery - not sure if that's normal or not?
skdubg said:
can you please upload your dumps and backups if there are ready for it?
i have a broken XT1562 without a nandroid or other backups...
thanks
Click to expand...
Click to collapse
Hi,
check this : http://moto.shreps.fr/?dir=Moto X Play (lux)/rom/stock_XT1562_EMEA-retfr/ZY2223RWB8
Shreps said:
Hi,
check this : http://moto.shreps.fr/?dir=Moto X Play (lux)/rom/stock_XT1562_EMEA-retfr/ZY2223RWB8
Click to expand...
Click to collapse
Hopefully they have a XT1563 full backup soon as well. Cheers.
Vibration and screen brightness are not working
Btw the stock firmware is out : http://www.filefactory.com/file/4ivu9kooeesf/?code=275
this one is for xt1563 CA
XMoDuLeSx said:
Vibration and screen brightness are not working
Btw the stock firmware is out : http://www.filefactory.com/file/4ivu9kooeesf/?code=275
this one is for xt1563 CA
Click to expand...
Click to collapse
@vache
Try adding these to the defconfig: https://github.com/sultanqasim/andr..._twrp2/arch/arm/configs/ext_config/lux.config
EDIT: I made a dedicated defconfig that you can try for this recovery: https://github.com/sultanqasim/andr...p2/arch/arm/configs/msm8916-minilux_defconfig
Wow thanks for your great work. Soon, we'll be able to get custom kernel to go with the stock firmware. We will probably get better performance with a properly tuned CPU governor. I'd also love to see CM12 being ported but the Moto firmware is already really good. In fact, I'm not sure if I could live without the added feature like Moto Voice and Moto Assist.
squid2 said:
@vache
Try adding these to the defconfig: https://github.com/sultanqasim/andr..._twrp2/arch/arm/configs/ext_config/lux.config
EDIT: I made a dedicated defconfig that you can try for this recovery: https://github.com/sultanqasim/andr...p2/arch/arm/configs/msm8916-minilux_defconfig
Click to expand...
Click to collapse
@squid2 Did you used the lux_defconfig in ext_defconfig ?
Already tried with those addition, the phone boot but i have no RIL. (Stock ROM)
Ill post a new reco with this kernel.
EDIT : Published a new version, with the new kernel config, that fix brightness and vibration.
Shreps said:
Hi,
check this : http://moto.shreps.fr/?dir=Moto X Play (lux)/rom/stock_XT1562_EMEA-retfr/ZY2223RWB8
Click to expand...
Click to collapse
So flashing this restores functionality on a XT1562?
And another thing, if your TWRP version is working when I fastboot boot it, is it guaranteed that it'll work when I fastboot flash it? And another thing: Is there a possibility to backup stock recovery, just in case TWRP doesn't work properly? I tried booting your TWRP version and backing it up but that didn't work (duh.)
Best wishes
derelektrischemoench
derelektrischemoench said:
So flashing this restores functionality on a XT1562?
And another thing, if your TWRP version is working when I fastboot boot it, is it guaranteed that it'll work when I fastboot flash it? And another thing: Is there a possibility to backup stock recovery, just in case TWRP doesn't work properly? I tried booting your TWRP version and backing it up but that didn't work (duh.)
Best wishes
derelektrischemoench
Click to expand...
Click to collapse
Stock Recovery is also available on my backup.
And yes, if TWRP is working while booting it, should work also fine when flashing it.
Be sure to use the latest version by @vache
Ok thx.
And another thing, I made a backup of my recovery partition via ls -al /dev/block/platform/7824900.sdhci/by-name
followed by
dd if=/dev/block/mmcblk0p32 (the partition that had the name "recovery"assigned in the output of the first command)
and got a nice recovery.img written to my sdcard.
Now from my understanding, in case something goes wrong with TWRP i should be able to restore my stock recovery via fastboot flash recovery nameoftheimagethatidumped.img, is that correct?
Greetz DeM
squid2 said:
@vache
Try adding these to the defconfig: https://github.com/sultanqasim/andr..._twrp2/arch/arm/configs/ext_config/lux.config
EDIT: I made a dedicated defconfig that you can try for this recovery: https://github.com/sultanqasim/andr...p2/arch/arm/configs/msm8916-minilux_defconfig
Click to expand...
Click to collapse
Got it booting, my repack method was wrong. All seems to work fine now.
Now trying to build a custom ROM.
Related
Just for fun, I compiled an optimized version of stock kernel for Marshmallow 6.0
It works with stock ROM for Moto X Pure XT1575, not tested with anything else.
Current features:
Compiled with O3
Uber toolchain
misc gcc optimization flags
KCAL
TCP congestions
Source code:
https://github.com/vadimtk/moto-x-kernel-6.0
Based on source
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/MMI-MPH24.49-18
Download link
V5:
Changes:
Updated to Kernel 3.10.94, thanks to https://github.com/Nimrodsv
XT1575:
https://www.androidfilehost.com/?fid=24345424848487596
XT1572:
https://www.androidfilehost.com/?fid=24345424848487595
V3:
Changes:
Couple SSD/flash related optimizations
XT1575:
https://www.androidfilehost.com/?fid=24343351889232014
XT1572:
https://www.androidfilehost.com/?fid=24343351889232056
V2:
https://www.androidfilehost.com/?fid=24341993505161414
How to use:
1. Download and unpack
2. Reboot to bootloader:
Code:
adb reboot bootloader
3. Boot temporary with new kernel (active till next reboot):
Code:
fastboot boot v4tk-opt-V2.img
or flash permanently:
Code:
fastboot flash boot v4tk-opt-V2.img
XDA:DevDB Information
V4TK Kernel, Kernel for the Moto X Style (Pure)
Contributors
VadimTk
Kernel Special Features:
Version Information
Status: Beta
Created 2015-12-24
Last Updated 2015-12-23
Damn that was fast okay I'm installing it now. I'll be the test dummy for TruPureX users. Thanks for your hardwork its very appreciated
also OT. woot 123 posts
---------- Post added at 02:09 AM ---------- Previous post was at 02:02 AM ----------
Works great on TruPureX it's just very bare bones at the moment. Still great job! I can not wait to see more from you tanks again for being awesome
Thank you for this!
sweet! vadim is back will flash later
patt2k said:
sweet! vadim is back will flash later
Click to expand...
Click to collapse
If your running TruPureX your going to be happy by the speed up
I tried flashing this in TWRP and get a failed message. md5 checks out. Any suggestions?
btafoya said:
I tried flashing this in TWRP and get a failed message. md5 checks out. Any suggestions?
Click to expand...
Click to collapse
Its not a flashable zip. You need to extract it before flashing. Flash as an image file in TWRP and select boot
^^^ yes, and/or try using flashify or rashr after unzipping
I have the traditional root using rooted boot and super SU in system. Is this boot.img pre rooted?
countryfolk07 said:
I have the traditional root using rooted boot and super SU in system. Is this boot.img pre rooted?
Click to expand...
Click to collapse
the boot.img does not control root. The only thing that would effect this for would maybe be the SR build as that hooks into the kernal. traditional dosent hook into the kernal. He is reverting to traditional soon.
WelcomeToTheSkye said:
If your running TruPureX your going to be happy by the speed up
Click to expand...
Click to collapse
I had it,using Sabissimos rom and so far so good.
Sent from my XT1575 using Tapatalk
I flashed this on a rooted, deodoxed 6.0 and dang.. My phone is so snappy now. Thank you!
WelcomeToTheSkye said:
the boot.img does not control root. The only thing that would effect this for would maybe be the SR build as that hooks into the kernal. traditional dosent hook into the kernal. He is reverting to traditional soon.
Click to expand...
Click to collapse
If the boot partition isn't flashed as rooted you will bootloop if superSU is installed. When I first took OTA I had to flash a rooted boot.img to get root without bootlooping. I can remember off hand who created the image, but this is why I ask.
VadimTk said:
Source code:
https://github.com/vadimtk/moto-x-kernel-6.0
Click to expand...
Click to collapse
Very nice Vadim
Please remove the "http://" on the url part for this link.
Might be a good idea to note that in the OP @VadimTk. Thanks!
Sent from my XT1575 using Tapatalk
Sir can i install this kernel on non rooted pure style
@VadimTk
please make an xt1572 version compatible, this version don't work on style, every app FC at start.
thanks
happy xmas
fdc77 said:
@VadimTk
please make an xt1572 version compatible, this version don't work on style, every app FC at start.
thanks
happy xmas
Click to expand...
Click to collapse
Did you wipe dalvik/cache?if it truly didn't work on the xt1572 either WiFi or RIL would be broken.
yes, wiped cache and dalvik but no luck, wifi and ril seems to be broken but i don't know for certain because phone was unusable
fdc77 said:
yes, wiped cache and dalvik but no luck, wifi and ril seems to be broken but i don't know for certain because phone was unusable
Click to expand...
Click to collapse
Ah okay then yes it is incompatible lol sorry for doubting
At the moment we have rather dfficult situation because custom ROMs based on AOSP (such as my AD which is not yet public) require previous OOS LP firmware, while OOS 3.0 includes new MM firmware which breaks both older recoveries and custom ROMs.
As I need to switch between OOS 3.0 and my AD quite frequently, I created two helpful flashable zips so I can do that easily, and because it's useful for me, perhaps it'll be useful for you too.
Download: MM | LP
Instructions:
- Download the firmware you want (or both, if you want easy switching)
- Unpack downloaded zip, you'll find firmware-update.zip and recovery.img inside
- Put both of those files on your phone, in appropriately named directory such as "firmware-LP" or "firmware-MM"
- When you will need to do a switch, simply firstly flash firmware-update.zip, then flash recovery.img as recovery image via "flash image" option in TWRP
- Reboot to load new firmware
That's it, this way you firstly flash chosen firmware version, and then TWRP recovery that works with it.
So if you have two TWRP backups - one of OOS 3.0 and one of CM13.0, make sure that you have proper firmware (and recovery) after restoring backup - LP for CM13.0, and MM for OOS 3.0.
Situation should soon improve (when OnePlus pushes kernel sources, and MM-based ROMs will rebase), but until then it's wise to keep both of those firmware + recovery combos on your sd card, so you can do a switch without any problem on as-needed basis.
Hope it helps. Try to be careful with those, if you mix up wrong recovery with wrong firmware you'll need to flash proper recovery.img variant via fastboot. You can't hard brick anything by using those files, in worst case soft-brick if both your recovery and your ROM will be for wrong firmware you have.
Have fun.
We are waiting for AD release. At least a beta?
mido25 said:
We are waiting for AD release. At least a beta?
Click to expand...
Click to collapse
Don't you know how to use the JustArchi's github?
Wow, really helps. I wish I have my OnePlus2 now.
Guihardrock said:
Don't you know how to use the JustArchi's github?
Click to expand...
Click to collapse
No sir. I do not know. Once I tried downloading a build from the below location and tried flashing it but recovery didn't allow me to flash it.
https://t.co/96EZIl6dJJ
I don't know why is it failed. My knowledge about github and making builds are limited.
mido25 said:
No sir. I do not know. Once I tried downloading a build from the below location and tried flashing it but recovery didn't allow me to flash it.
https://t.co/96EZIl6dJJ
I don't know why is it failed. My knowledge about github and making builds are limited.
Click to expand...
Click to collapse
ok so i will explain you when you download that file you have to unzip it and then you will have a folder with another folder (if you choosed unzip in archidreoid etc.zip so inside that folder you will have the necesary files (view the attached screenshot) you will have to pack them in a zip file
hope it helps but try to download the latest file to do that cause last time i tried the oneplus2 archidroid there were things that dint work such as ad filter
Guihardrock said:
ok so i will explain you when you download that file you have to unzip it and then you will have a folder with another folder (if you choosed unzip in archidreoid etc.zip so inside that folder you will have the necesary files (view the attached screenshot) you will have to pack them in a zip file
hope it helps but try to download the latest file to do that cause last time i tried the oneplus2 archidroid there were things that dint work such as ad filter
Click to expand...
Click to collapse
Thanks a lot for your guidance. Appreciate if you can give a link to his latest build.
Sent from my ONE A2003 using Tapatalk
mido25 said:
Thanks a lot for your guidance. Appreciate if you can give a link to his latest build.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Here you go https://github.com/ArchiDroid/ArchiDroid/archive/oneplus2-cm-experimental.zip but its experimental so you can expect bugs
Lost recovery
Hi sir,
I have flashed MM using the TWRP recovery as normal. But now I have lost my recovery. I am not able to boot into any recovery. Pls help.
JustArchi said:
At the moment we have rather dfficult situation because custom ROMs based on AOSP (such as my AD which is not yet public) require previous OOS LP firmware, while OOS 3.0 includes new MM firmware which breaks both older recoveries and custom ROMs.
As I need to switch between OOS 3.0 and my AD quite frequently, I created two helpful flashable zips so I can do that easily, and because it's useful for me, perhaps it'll be useful for you too.
Download: MM | LP
Instructions:
- Download the firmware you want (or both, if you want easy switching)
- Unpack downloaded zip, you'll find firmware-update.zip and recovery.img inside
- Put both of those files on your phone, in appropriately named directory such as "firmware-LP" or "firmware-MM"
- When you will need to do a switch, simply firstly flash firmware-update.zip, then flash recovery.img as recovery image via "flash image" option in TWRP
- Reboot to load new firmware
That's it, this way you firstly flash chosen firmware version, and then TWRP recovery that works with it.
So if you have two TWRP backups - one of OOS 3.0 and one of CM13.0, make sure that you have proper firmware (and recovery) after restoring backup - LP for CM13.0, and MM for OOS 3.0.
Situation should soon improve (when OnePlus pushes kernel sources, and MM-based ROMs will rebase), but until then it's wise to keep both of those firmware + recovery combos on your sd card, so you can do a switch without any problem on as-needed basis.
Hope it helps. Try to be careful with those, if you mix up wrong recovery with wrong firmware you'll need to flash proper recovery.img variant via fastboot. You can't hard brick anything by using those files, in worst case soft-brick if both your recovery and your ROM will be for wrong firmware you have.
Have fun.
Click to expand...
Click to collapse
Your ll recovery is in chinese. How to change it?
EDIT: Forget it. I found where to change the language! Thanks.
eswa1068 said:
Hi sir,
I have flashed MM using the TWRP recovery as normal. But now I have lost my recovery. I am not able to boot into any recovery. Pls help.
Click to expand...
Click to collapse
Use fastboot to flash the recovery
Guihardrock said:
Here you go https://github.com/ArchiDroid/ArchiDroid/archive/oneplus2-cm-experimental.zip but its experimental so you can expect bugs
Click to expand...
Click to collapse
Thank you Sir
Tierri said:
Your ll recovery is in chinese. How to change it?
EDIT: Forget it. I found where to change the language! Thanks.
Click to expand...
Click to collapse
Hi,
Can u let me know where to change the language of twrp ?
Sent from my ONE A2003 using Tapatalk
amit_sen said:
Hi,
Can u let me know where to change the language of twrp ?
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Yes. See the images to help you.
Guihardrock said:
Here you go https://github.com/ArchiDroid/ArchiDroid/archive/oneplus2-cm-experimental.zip but its experimental so you can expect bugs
Click to expand...
Click to collapse
It's around 900 mb zip..?
And did anyone try that build..?
Mohit31 said:
It's around 900 mb zip..?
And did anyone try that build..?
Click to expand...
Click to collapse
Its because of the aroma you can choose the gapps of your choice...
Guihardrock said:
Its because of the aroma you can choose the gapps of your choice...
Click to expand...
Click to collapse
OK... Thanks
Btw Are you on this build..
A quick feedback on the ROM would be great
This thing should be STICKY
Finally was able to install CM13 properly using this recovery without Google Services crashing.
Mohit31 said:
OK... Thanks
Btw Are you on this build..
A quick feedback on the ROM would be great
Click to expand...
Click to collapse
Now i am in oos3 but when justarchi release archidroid i wont use any other rom, i had so great experience with this on my s3
Edit: i am gonna try it :3 yo made me do it
Mohit31 said:
OK... Thanks
Btw Are you on this build..
A quick feedback on the ROM would be great
Click to expand...
Click to collapse
rom is smooth as h*ll and battery is better than in normal cm13 but as i said the backed dont work yet :3 and aroma is not fully functional with the bootanimation and root (but the rom has the cm superuser)
I patched the kernel for 7.1.1 on Qualcomm Moto E4 Plus. This is useful to get Magisk fully working with modules and settings that can be saved.
I compiled the fix from the released kernel source: MMI-NPR26.58-25
Here are the unsigned boot.img and zImage, use whichever one suits your fancy to patch the kernel.
Download boot.img
Download zImage
Edit: I've uploaded a build for the regular Qualcomm Moto E4 here.
Installation:
You should backup your Boot in TWRP before installing, that way you can restore if something goes wrong.
If you have Magisk installed, you'll want to patch the boot.img using Magisk Manager. Just tap install, and patch boot rom image. Then copy the patched file back to your computer to flash it.
Easiest way is to flash the boot.img while in fastboot:
Code:
>fastboot flash boot /path/to/downloaded/boot.img
Did not work, phone would not boot after flash, had to restore stock kernel.
TheJAYpoop said:
Did not work, phone would not boot after flash, had to restore stock kernel.
Click to expand...
Click to collapse
Hmm, having tried it myself, I see that without patching the image with magisk from inside magisk manager, it seems the rebuilt boot image does not work. But it does work after it's been patched in magisk, so you can try that.
Here's a link that's already been patched with Magisk 14.6 beta: https://drive.google.com/open?id=13vaUgq22fNnVnWqq5ai9kGC1KsO3ZEmJ
SeanStar said:
Hmm, having tried it myself, I see that without patching the image with magisk from inside magisk manager, it seems the rebuilt boot image does not work. But it does work after it's been patched in magisk, so you can try that.
Here's a link that's already been patched with Magisk 14.6 beta: https://drive.google.com/open?id=13vaUgq22fNnVnWqq5ai9kGC1KsO3ZEmJ
Click to expand...
Click to collapse
That worked perfectly, awesome!
TheJAYpoop said:
That worked perfectly, awesome!
Click to expand...
Click to collapse
Merry Christmas! Enjoy the full Magisk experience, it was really bothering me when I got this phone about half a week ago.
Nice, I was planning on doing this after Christmas. Saved me the trouble. Merry Christmas to you too! It worked fine just flashing the patched img with TWRP. Want to save me the trouble of doing one for the regular E⁴ also?
GetOffMyLawn&!+¢#{$ said:
Nice, I was planning on doing this after Christmas. Saved me the trouble. Merry Christmas to you too! It worked fine just flashing the patched img with TWRP. Want to save me the trouble of doing one for the regular E⁴ also?
Click to expand...
Click to collapse
If you point me to the kernel source you specifically want patched, I can make it. You'll have to test it for me though, as I don't own the regular E^4.
SeanStar said:
If you point me to the kernel source you specifically want patched, I can make it. You'll have to test it for me though, as I don't own the regular E^4.
Click to expand...
Click to collapse
That would be great. I'll pm you a link since I can't post links yet. I've been spending all my spare time trying to get data working properly on both devices. I have no problem testing it.
Sent from my Moto E (4) Plus using XDA Labs
Qualcomm Moto E4 f2fs fix for perry 7.1.1 (Built and patched from NCQ26.69-48 source) kernel boot image for anyone that wants it is linked below. Thanks to GetOffMyLawn&!+¢#{$ for testing. See the OP for installation instructions, and please remember to make backups of your stock Boot.
Download:
unsigned boot.img
zImage
SeanStar said:
Qualcomm Moto E4 f2fs fix for perry 7.1.1 (Built and patched from NCQ26.69-48 source) kernel boot image for anyone that wants it is linked below. Thanks to GetOffMyLawn&!+¢#{$ for testing. See the OP for installation instructions, and please remember to make backups of your stock Boot.
Download:
unsigned boot.img
zImage
Click to expand...
Click to collapse
Thank you very much for taking the time to do this! Especially today. Just to point out how I installed the kernel, I simply flashed it as an img with TWRP, flashed the no dmverity/forceencrypt zip, then flashed Magisk V15.0 that was just released. It stayed on the n/a screen a minute then bootlooped a couple times, but it eventually booted just fine, so be patient with it. I had the latest Boost firmware installed and Magisk v14.6 at the time. Enjoy!
Sent from my Moto E (4) Plus using XDA Labs
Thanks @SeanStar for the regular e4 boot.img. you rock bro. Works great. Tested, successful
@SeanStar would you mind uploading the source to your kernel, like maybe on a GitHub repo or something? I'm working with a friend who has the owens and I'm trying to see if we can get a more functioning Lineage 14.1 on here
jasonmerc said:
@SeanStar would you mind uploading the source to your kernel, like maybe on a GitHub repo or something? I'm working with a friend who has the owens and I'm trying to see if we can get a more functioning Lineage 14.1 on here
Click to expand...
Click to collapse
Though the kernel I am currently working on is slightly modified more than what is provided here, the OP only has the fix for the f2fs loopback issue, as described here: https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
You can download the stock kernel build source from Motorola's own repository here: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPR26.58-25
Also, I admit that I'm currently in the process of porting Lineage 14.1 to this phone, but it may take more time than I had originally planned for. It's not a priority for me at the moment, especially considering how much I like the stock rom.
SeanStar said:
Though the kernel I am currently working on is slightly modified more than what is provided here, the OP only has the fix for the f2fs loopback issue, as described here: https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
You can download the stock kernel build source from Motorola's own repository here: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPR26.58-25
Also, I admit that I'm currently in the process of porting Lineage 14.1 to this phone, but it may take more time than I had originally planned for. It's not a priority for me at the moment, especially considering how much I like the stock rom.
Click to expand...
Click to collapse
Well dang, I'm working on porting lineage 14.1 to this thing too. Maybe we should join forces.
And moto's source is in a zip file, I was hoping I could get one that was unzipped and in a github repo already, for easy syncing when trying to build Lineage 14.1
Thank you for your work. I agree that stock isn't too bad with root magisk and Xposed working fine. But lineage is pretty tasty! I will shoot you both a PM if I can assist in any way
@SeanStar check out these screenies everyone:
Sent from my Moto E (4) Plus using XDA Labs
GetOffMyLawn&!+¢#{$ said:
@SeanStar check out these screenies everyone:
Click to expand...
Click to collapse
I'm not sure if they're still doing updates for this phone from what I've heard, but if they do this would be very nice.
SeanStar said:
I'm not sure if they're still doing updates for this phone from what I've heard, but if they do this would be very nice.
Click to expand...
Click to collapse
That sucks to hear, but although I do actually like stock on this device, that's why I build custom ROMs. Budget Motorola's never get updated more then a few times. Hopefully it will get added for future devices and ones that don't get abandoned at least.
Sent from my Moto E (4) Plus using XDA Labs
SeanStar said:
Qualcomm Moto E4 f2fs fix for perry 7.1.1 (Built and patched from NCQ26.69-48 source) kernel boot image for anyone that wants it is linked below. Thanks to GetOffMyLawn&!+¢#{$ for testing. See the OP for installation instructions, and please remember to make backups of your stock Boot.
Download:
unsigned boot.img
zImage
Click to expand...
Click to collapse
Hey @SeanStar would it be possible for you to do this on the latest update for the kernel on the E4 Perry please?? The reason being is this one can't be used on the latest update of the firmware, it fails to boot all the way up.
EDIT: The latest is NCQ26.69-56
PimpMy5Ton said:
Hey @SeanStar would it be possible for you to do this on the latest update for the kernel on the E4 Perry please?? The reason being is this one can't be used on the latest update of the firmware, it fails to boot all the way up.
EDIT: The latest is NCQ26.69-56
Click to expand...
Click to collapse
Considering there is no kernel source for NCQ26.69-56 on MotorolaMobilityLLC github, you're SOL, there's no easy way to patch it without the source. Sorry bud.
EDIT: I wouldn't try to downgrade either, I'm sure they updated the baseband. You'll probably knockout your service if you even try.
Download:
https://github.com/JarlPenguin/releases/releases/download/twrp3.3.1-3-cedric/twrp-3.3.1-3-cedric.img
Known issues:
Encrypted backups don't work
You tell me
Special thanks to:
@squid2 and @Akipe for their hard work on the montana & msm8937-common device tree
OmniROM and TWRP team
All other open source devs/teams I may have missed!
Sources:
Device Tree:
https://github.com/JarlPenguin/android_device_motorola_cedric-soham/tree/twrp-9.0
Kernel: https://github.com/Sohamlad7/android_kernel_motorola_msm8937/tree/twrp-treble
TWRP (Treble) for the Moto G5 (cedric).
XDA:DevDB Information
Unofficial TeamWin Recovery Project for Moto G5, Tool/Utility for the Moto G5
Contributors
JarlPenguin, Akipe, squid2
Source Code: [url]https://github.com/TeamWin[/URL]
Version Information
Status: Stable
Current Stable Version: 3.3.1-3
Stable Release Date: 2019-07-28
Created 2019-07-28
Last Updated 2019-07-28
Is this version of treble recovery allows us to flash Android Q treble version without any problems or not ?
basem bebarse said:
Is this version of treble recovery allows us to flash Android Q treble version without any problems or not ?
Click to expand...
Click to collapse
I haven't tested it. It should work fine
These are the commits I made for encryption on the official twrp
I haven't gone through your source in detail but you may find it useful for comparison of files
Github TWRP Encryption Commits
TheFixItMan said:
These are the commits I made for encryption on the official twrp
I haven't gone through your source in detail but you may find it useful for comparison of files
Github TWRP Encryption Commits
Click to expand...
Click to collapse
Yes, this TWRP is based off of squid2's trees (will fix history soon) with Nougat arm64 crypto blobs
one small question: is this the version for future LOS 16 builds? for 64bit builds?
kare_meesner said:
one small question: is this the version for future LOS 16 builds? for 64bit builds?
Click to expand...
Click to collapse
It's for both 32 and 64 bit builds.
what trebel rom we can install ?
If you try please share
Does this also work in Stock Rom?
TheBlob11 said:
Does this also work in Stock Rom?
Click to expand...
Click to collapse
This is a recovery image so you can flash it regardless of what rom you are using (you can flash 32 or 64bit roms with it)
However as you are on stock rom I would recommend sticking with my official twrp recovery especially if you use encryption due to encryption bug in this recovery
I wanted to use this to Switch to a 64bit Rom Rom for the first time. I have always been afraid, because i wouldn't be able to restore my stock backup. Would this be possible With this Recovery?
TheBlob11 said:
I wanted to use this to Switch to a 64bit Rom Rom for the first time. I have always been afraid, because i wouldn't be able to restore my stock backup. Would this be possible With this Recovery?
Click to expand...
Click to collapse
If you want to restore stock flash stock firmware via fastboot and then restore your backup using the twrp which created the backup
You can probably just restore the backup using the twrp that created it without flashing stock firmware first but just in case the custom rom alters anything that isn't restored with the backup
Make sure you backup efs partition just in case of a loss of imei
TheBlob11 said:
Does this also work in Stock Rom?
Click to expand...
Click to collapse
you need to unlock your bootloader and flash this TWRP for treble to work. i believe you then need to flash a rom which supports treble before you can flash your desired GSI
walidham said:
what trebel rom we can install ?
Click to expand...
Click to collapse
You need to install a treble-enabled ROM. Currently it seems like there are none on XDA.
@JarlPenguin It's cool to have an updated TWRP for 64 bit but please fix encryption.
Sent from my cedric using XDA Labs
nift4 said:
@JarlPenguin It's cool to have an updated TWRP for 64 bit but please fix encryption.
Sent from my cedric using XDA Labs
Click to expand...
Click to collapse
Encryption doesn't work on which ROMs?
No idea, I only read the OP + Thread history. The OP says that backup with encryption does not work and the thread history has no fixed or somewhat.
Sent from my cedric using XDA Labs
P.S.: This isn't meant as a "INSTANTLY DO THAT I WANT IT!", I can try to help but I have zero experience at Android internals (and Android recoverys).
I have currently no encryption, is it save to use it for backups?
@JarlPenguin ?
TWRP 3.5.2_9 FOR GALAXY J5 (2016)
DISCLAIMER : I AM NOT RESPONSIBLE VOIDING YOUR WARRANTY OR ANY DAMAGE CAUSED TO YOUR DEVICE
FEATURES
-Standard TWRP 3.5.2 features
**-Nano and bash removed for now
-Built with Android 9.0 sources
-Backup/restore/format/mount:
-IMEI 1, IMEI 2, FRP PARTITION, EFS, APNHLOS, RPM, MODEM, HIDDEN, QSEE, QHEE, PERSDATA, USB OTG
-Android 11 compatible
-Encryption
-J510H support dropped due to lack of feedback from users
BUGS/KNOWN ISSUES
-None so far
***Backup and restore info***
Some have reported having issues backing up and restoring beginning with Android 10, where upon restoring, a bootloop/stalled boot up occurs. A root fix flashable zip was referenced as the fix to this.
The official solution to this, per TWRP managerial staff, is when backing up the system partition, use the system image instead of system. Its more reliable and efficient.
INSTALLATION
1. Download TWRP image to your device
2. Reboot to Recovery
3. Install
-a. via TWRP by selecting Install, Install Image, then select the image.-b. via OrangeFox as a normal install.4. Reboot to recovery.
5. Enjoy!
DOWNLOAD
J5XNLTE/J5XLTE
https://twrp.me/samsung/j5xnlte.html
J5XLTECMCC
https://twrp.me/samsung/j5xltecmcc.html
Credits
TWRP Team
Zakaryan2004 for his assistance
Sources
TWRP source: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
Device and Kernel trees: https://github.com/teamwin
XDA:DevDB Information
[RECOVERY] TWRP 3.5.2_9 for Galaxy J5 (2016), Tool/Utility for the Samsung Galaxy J5
Contributors
palmbeach05
Version Information
Status: Stable
Current Stable Version: 3.5.2_9
Stable Release Date: 2021-04-19
Created 2019-10-01
Last Updated 2021-04-19
When might it be available?
Awesome! I will install it when available.
shreejalm said:
When might it be available?
Click to expand...
Click to collapse
I'm guessing later on today. I submitted the markdown about 3 hrs ago. Just waiting on word from the twrp team to say its uploaded
Wooow thanks so much!
Thank you so much
nice to see twrp official.
Ota install doesn't work..
Bogdans29 said:
Ota install doesn't work..
Click to expand...
Click to collapse
If i'm not mistaken, i tried coordinating with zakaryan2004 and he said ofox had the same issue. However jens 3.2.3 did have that feature. I have been unable to replicate his success on this or the 2015 version. Best advice, download the rom normally, and update that way until i can track down a patch to implement.
palmbeach05 said:
If i'm not mistaken, i tried coordinating with zakaryan2004 and he said ofox had the same issue. However jens 3.2.3 did have that feature. I have been unable to replicate his success on this or the 2015 version. Best advice, download the rom normally, and update that way until i can track down a patch to implement.
Click to expand...
Click to collapse
You are right...Jenslody i think know solution since he make 3.2.3 that work for ota.. Not a big problem for me at all.. Just want you to know and don't know for others. Thank you for TWRP and for your help.
Bogdans29 said:
You are right...Jenslody i think know solution since he make 3.2.3 that work for ota.. Not a big problem for me at all.. Just want you to know and don't know for others. Thank you for TWRP and for your help.
Click to expand...
Click to collapse
Np. Not sure how much he talks, i'm wrapped up in pre-10 implementations and stuff (or at least trying to get the damn thing to work), but if you can get info on that, i'll push it to both the 2015 and 2016 builds and re-release with that update
Amazing to see official TWRP for our device! Thank you so much!
Sent from my j5xnlte using XDA Labs
palmbeach05 said:
Np. Not sure how much he talks, i'm wrapped up in pre-10 implementations and stuff (or at least trying to get the damn thing to work), but if you can get info on that, i'll push it to both the 2015 and 2016 builds and re-release with that update
Click to expand...
Click to collapse
I will try..
i asked for the issue on the twrp github.maybe they have a hint for fixing
J510H?
TWRP 3.3 has some flashing problems with some zips like the Camera fix for Pie just doesn't replace anything...
NecromancerViper said:
TWRP 3.3 has some flashing problems with some zips like the Camera fix for Pie just doesn't replace anything...
Click to expand...
Click to collapse
provide logs
Have you got any recovery for J510H? The version is not important but to be able to download android P&Q roms only
Bogdans29 said:
provide logs
Click to expand...
Click to collapse
+1
Zaid Koudmani said:
Have you got any recovery for J510H? The version is not important but to be able to download android P&Q roms only
Click to expand...
Click to collapse
I have some free time over the next few days to look into things. Can you tell me if there are any pie roms for the j510h? I'm not sure or can't exactly tell if that is supported?