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 ?
Related
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.
STOCK BASED ROM 8.1.0-OREO (OPM2.029.A1, May 2018.)
System :
- Android 8.1.0 opm2.171019.029.a1,May. 2018)
- Stock kernel 3.10.73
- Easy installation through the Aroma
Installation:
- Reboot to recovery
- Take necessary backups
- Wipe system/data/cache
- Flash the appropriate vendor.img
- Flash Rom.zip
- Reboot to system
- Enjoy
What is working:
- Everything
Contributors:
- cile381
Credits:
- Google/AOSP
XDA: DevDB Information
SUPERXE AOSP ROM for the Nexus 6P
ROM OS Version: 8.1.0-Oreo
Kernel: Linux 3.10.73
ROM Vendor:8.1.0 (opm2.171019.029.a1)
Based On: Google/AOSP
Version Information:
Status: Stable
DOWNLOAD ROM 8.1.0-OPM2.171019.029.A1
MD5 [fc884c4e09fad95c27b79cf606ec9158
VENDOR IMAGE 8.1.0-OPM2.171019.029.A1
MD5 [ec5d30b20fb022df2fe26a5b4ef8a0d4
Created 2017-07-25
Last Updated 2018-05-14
DONATIONS
@Signal2Noise
@hawgguy
Bee venom collector
@Samuel Holland
CUSTOM BUILT ROM 8.1.0-OREO (android-8.1.0_r21)
System :
- Android 8.1.0_r21
- Kernel 3.10.73
Clean installation is required!
Installation:
- Reboot to recovery
- Take necessary backups
- Wipe system/data/cache
- Flash ROM
- Reboot to system
- Enjoy
What is working:
- Everything
Vendor is included in the ROM and does not need to be installed separately!
Do not install stock vendor on this ROM!
Contributors:
- cile381
Credits:
- Google/AOSP
XDA: DevDB Information
SUPERXE AOSP ROM for the Nexus 6P
ROM OS Version: android-8.1.0_r21
Kernel: Angler/Linux 3.10.73
ROM Vendor:8.1.0 (OPM3.019/custom)
Based On: Google/AOSP
Version Information:
Status: Stable
If you change the kernel or any part of the system and after that you have a problem, please do not post any questions in this thread.
DOWNLOAD ROM SUPERXE-8.1.0_r21
MD5 641d3bb35cbf4f3b0e457b3c52480fa3
Root - Magisk 16.3
Created 2017-10-03
Last Updated 2018-04-11
Welcome and thank you for the contribution will test this out
Android Rocks
Sent from my Nexus 6P using Tapatalk
SWEET
I think 1st 7.1 based custom ROM..
Thanks @cile381[emoji4]
Where is change log ?......
mukesh22584 said:
I think 1st 7.1 based custom ROM..
Thanks @cile381[emoji4]
Where is change log ?......
Click to expand...
Click to collapse
Uberstock is 7.1 as well it's based on pixel sources.... OP is this the same or is it based on dev preview? Also change log is in first post
Arzee08 said:
Uberstock is 7.1 as well it's based on pixel sources.... OP is this the same or is it based on dev preview?
Click to expand...
Click to collapse
Neither private sources was not used for building.
Rom is 100% synced and built from googlesource..
Gif support on keyboard with Messenger and Allo?
Can I go back to a MM custom rom after i've flashed this?
I've never tried 7.0 or 7.1 . I will stay on this rom if all my apps work and when the battery is good.
Yes.. thanks dev
Wouldn't you flash the vendor image after flashing the ROM in recovery? Rebooting into bootloader is just a extra step or am I wrong???
tarroyo said:
Wouldn't you flash the vendor image after flashing the ROM in recovery? Rebooting into bootloader is just a extra step or am I wrong???
Click to expand...
Click to collapse
Can twrp flash radio imgs?
Lawlrus said:
Can twrp flash radio imgs?
Click to expand...
Click to collapse
Not radio images but if someone makes a flashable zip of new radio and bootloader etc then you can
Sent from my Pixel XL using XDA-Developers mobile app
mickyw1980 said:
Not radio images but if someone makes a flashable zip of new radio and bootloader etc then you can
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Obviously. But that's why it says to boot into the bootloader.
Lawlrus said:
Obviously. But that's why it says to boot into the bootloader.
Click to expand...
Click to collapse
I don't see the point of your question then if you obviously know ?
Sent from my Pixel XL using XDA-Developers mobile app
mickyw1980 said:
I don't see the point of your question then if you obviously know ?
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
I wasn't 100% if twrp could now do radio images and bl's like it can vendor images now. And I'm not sure what that bit of numbers stands for after you typed know
The point of my question was to answer his question as to why the op says to boot into the bootloader in the op, he offers the BL and radio in IMG form, not flashible..
My stating obviously, was to your stating you can get flashables for twrp for the radio.
Lawlrus said:
I wasn't 100% if twrp could now do radio images and bl's like it can vendor images now. And I'm not sure what that bit of numbers stands for after you typed know
The point of my question was to answer his question as to why the op says to boot into the bootloader in the op, he offers the BL and radio in IMG form, not flashible..
My stating obviously, was to your stating you can get flashables for twrp for the radio.
Click to expand...
Click to collapse
You misunderstood me I was asking about the vendor image only.
Contains 3D touch?
tarroyo said:
You misunderstood me I was asking about the vendor image only.
Click to expand...
Click to collapse
Nope didn't misunderstand you, I answered why it specifically states in the op to go into the BL. Its under the assumption that you need to update all IMG files.
If you don't need to update your BL or radio using the files he provided. Then yes, you can flash just the vendor image however you want.
Introduction
Hello everyone, this is my build of LineageOS with full Substratum support. It supports the rootless operations of Substratum as well as all of its features (overlays, fonts, boot animations [only on decrypted devices, more below], and sounds). It will be stock Lineage (meaning NO modifications from me aside from the Substratum support) and as such, I will not be supporting issues not related to Substratum. I will build as often as I can, ETAs are inconsiderate of my time
Installation
NOTE: Because this is build straight from Lineage's trees, forced encryption IS enabled. If you have decrypted, be sure to flash a custom kernel with forced encryption disabled (I of course recommend mine but all the major kernels should have it disabled as well).
Clean flash (needed when coming from another ROM [including official LineageOS]):
Download latest build with md5sum (TWRP will automatically verify)
Download GApps
Boot TWRP
Wipe system, data, cache, and dalvik cache
Flash ROM zip
Flash GApps
Flash other zips (such as root and kernels)
Reboot
Dirty flash (when already on these builds):
Download latest build with md5sum (TWRP will automatically verify)
Boot TWRP
Wipe cache and dalvik cache
Flash ROM zip
Flash other zips (such as root and kernels)
Reboot
Frequently Asked Questions
1.1 Q: Can I dirty flash over from official LineageOS?
1.1 A: No, a clean flash is required as their builds are signed with private keys.
1.2 Q: Can you merge ABC feature from XYZ ROM?
1.2 A: No. This is stock Lineage with OMS support, that is it.
1.3 Q: I have XYZ bug, please fix!
1.3 A: I will only be fixing issues related to Substratum support; anything else will be handled by the Lineage team. You will need to clean flash over to their builds to do so, they will most likely not accept reports on unofficial builds (especially ones like mine with a heavily modified framework).
1.4 Q: Why did my device get force encrypted?
1.4 A: Because you didn't read.
1.5 Q: What root should I flash?
1.5 A: It's up to you, as root is only required for boot animations on encrypted devices. There are four options:
SuperSU
Magisk
phh's Superuser
Lineage's su
1.6 Q: How do I see what is new every release?
1.6 A: https://www.cmxlog.com/14.1/angler/ and https://github.com/LineageOMS
Downloads/links
ROM: https://www.androidfilehost.com/?w=files&flid=167286
Highly recommended GApps: https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Required vendor image: https://androidfilehost.com/?fid=529152257862725522
Special Thanks
The Lineage team: this is all their work, I only added the necessary hooks for OMS and exposures
The Substratum team: their dedication would not make this possible
Any other open source contributors: you guys are what make this wonderful hobby worth it :good:
Sources
ROM: https://github.com/LineageOS and https://github.com/LineageOMS
Device: https://github.com/LineageOS/android_device_huawei_angler
Kernel: https://github.com/LineageOS/android_kernel_huawei_angler
XDA:DevDB Information
Unofficial LineageOS with OMS support, ROM for the Huawei Nexus 6P
Contributors
The Flash
Source Code: http://github.com/LineageOMS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 14.1-20170705
Stable Release Date: 2017-05-04
Created 2017-03-31
Last Updated 2017-07-05
Reserved
Reserved
Wow. first one for N6P i think.
downloading. Thanks in advance )
Happy weekend
Thank you so much, @The Flash! Might give it a spin for a short while the next time I clean flash.
Really wish LOS merges your commits so that rootless Substratum becomes officially supported, since I don't see any progress with CMTE, at least anytime in the near future.
Great to see! Kudos
@The Flash, It's really incredible to see you doing so much for the community. Thank you
Sent from my SGP621 using Tapatalk
lineage-14.1-20170401-UNOFFICIAL-angler.zip
lineage-14.1-20170401-UNOFFICIAL-angler.zip.md5sum
The Flash said:
lineage-14.1-20170401-UNOFFICIAL-angler.zip
lineage-14.1-20170401-UNOFFICIAL-angler.zip.md5sum
Click to expand...
Click to collapse
Bro..... √√√√√
YOU'RE SMURFING AWESOME!!!! THANK YOU!!!!!!
Awesome
Thank you. Lineage is now perfect.
Thank you for this, just downloaded it and about to flash it... Do you have a PayPal so I can contribute to your work
Sent from my Nexus 6P using Tapatalk
tdg2k15 said:
Thank you for this, just downloaded it and about to flash it... Do you have a PayPal so I can contribute to your work
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Nope. I appreciate the thought but I don't take donations Especially since Lineage themselves don't currently take donations. Feel free to give to something like the Free Software Foundation or Open Source Initiative if you want to contribute to something good.
The Flash said:
lineage-14.1-20170401-UNOFFICIAL-angler.zip
lineage-14.1-20170401-UNOFFICIAL-angler.zip.md5sum
Click to expand...
Click to collapse
Hmm...To trust or not to trust the April Fool's build...That, is the question???
Thanks for sharing this @The Flash
Sent from my Nexus 6P using Tapatalk
bps119 said:
Hmm...To trust or not to trust the April Fool's build...That, is the question
Thanks for sharing this @The Flash
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This is the one I'd be wary of
lineage-14.1-20170403-UNOFFICIAL-angler.zip
lineage-14.1-20170403-UNOFFICIAL-angler.zip.md5sum
Does this support f2fs?
note3userr said:
Does this support f2fs?
Click to expand...
Click to collapse
You'll need a custom kernel like my own but yes, it does.
The Flash said:
You'll need a custom kernel like my own but yes, it does.
Click to expand...
Click to collapse
Been running it a day, didn't even change the kernel, running very well.
Great news!!! I'm on LOS and was waiting for this for a long time...
I have one question: if i make my own migration build with "repopick -f 156047 162144" , is it possible to dirty flash this ontop of my build? I have a lot of customised apps and don't want to config everything again...I would make my own build with OMS but i don't know how to pick all the OMS patches.
Thanks!!
Enviado desde mi Nexus 6P mediante Tapatalk
alexiuss said:
Great news!!! I'm on LOS and was waiting for this for a long time...
I have one question: if i make my own migration build with "repopick -f 156047 162144" , is it possible to dirty flash this ontop of my build? I have a lot of customised apps and don't want to config everything again...
Click to expand...
Click to collapse
No idea, possibly LOL?
alexiuss said:
I would make my own build with OMS but i don't know how to pick all the OMS patches.
Thanks!!
Enviado desde mi Nexus 6P mediante Tapatalk
Click to expand...
Click to collapse
Well you're in luck! https://forum.xda-developers.com/ne...ference-lineageos-substratum-support-t3580276
You can also use the merge script I provide. Just run it on a clean Lineage repo and you're good to go! https://forum.xda-developers.com/showthread.php?p=71660770
Awesome..
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?
After some effort I have rebased the twrp tree for merlin to twrp 3.6.2_11-0 and after some builds and revisions I have it fully working
Credits:
Me (rebased tree)
Val (built for me as I have potato pc)
Cane (tested for me I literally don't own merlin lol)
method to install:
fastboot flash recovery (insert path to downloaded twrp here)
Device tree:
GitHub - halal-beef/twrp_device_xiaomi_merlin
Contribute to halal-beef/twrp_device_xiaomi_merlin development by creating an account on GitHub.
github.com
areallydumbperson said:
After some effort I have rebased the twrp tree for merlin to twrp 3.6.2_11-0 and after some builds and revisions I have it fully working
Credits:
Me (rebased tree)
Val (built for me as I have potato pc)
Cane (tested for me I literally don't own merlin lol)
method to install:
fastboot flash recovery (insert path to downloaded twrp here)
Device tree:
GitHub - halal-beef/twrp_device_xiaomi_merlin
Contribute to halal-beef/twrp_device_xiaomi_merlin development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
hi i want to install shrp or twrp and I'm currently on miui 12.0.1 and android 10. Which ver. of shrp or twrp should I install.
Just for general knowledge can you tell me whether I should be concerned about the twrp and the android version on which I'm installing it?
For twrp you should be able to install this twrp and other twrp but shrp I'm not too sure of
My phone isnt detected in sideload, is that because of the TWRP or have I done something wrong?
TheEpicFlame said:
My phone isnt detected in sideload, is that because of the TWRP or have I done something wrong?
Click to expand...
Click to collapse
May be your drivers
areallydumbperson said:
May be your drivers
Click to expand...
Click to collapse
Used a twrp from the messenger group and it worked fine.
Does it work on the M2003J15SG model with the MIUI 12.5.5 RJOEUXM? (1st April 2022 Patch)
It has an unlocked bootloader and I'm trying to escape the MIUI.
Mineplayerminer said:
Does it work on the M2003J15SG model with the MIUI 12.5.5 RJOEUXM? (1st April 2022 Patch)
It has an unlocked bootloader and I'm trying to escape the MIUI.
Click to expand...
Click to collapse
you can try shrp its great download the latest version from their official site
Mineplayerminer said:
Does it work on the M2003J15SG model with the MIUI 12.5.5 RJOEUXM? (1st April 2022 Patch)
It has an unlocked bootloader and I'm trying to escape the MIUI.
Click to expand...
Click to collapse
Most likely yes
Manjotbenipal said:
you can try shrp its great download the latest version from their official site
Click to expand...
Click to collapse
Yeah, I saw this recovery earlier. Will it wipe my phone and internal storage after flashing this? What, if the flash fails or something happens during that? I've heard, that MediaTek phones are harder to unbrick. I just need a root to get rid of the MIUI apps. Unless there will be another daily driver ROM like the Project Elixir that is in the beta. The only thing I would miss will be the Redmi Buds 3 Pro pop-up message, or the Mi Band 5 proximity unlock. It's wonderful that someone is still trying to develop something better for that phone.
Edit: Ignore my broken grammar.
Mineplayerminer said:
Yeah, I saw this recovery earlier. Will it wipe my phone and internal storage after flashing this? What, if the flash fails or something happens during that? I've heard, that MediaTek phones are harder to unbrick. I just need a root to get rid of the MIUI apps. Unless there will be another daily driver ROM like the Project Elixir that is in the beta. The only thing I would miss will be the Redmi Buds 3 Pro pop-up message, or the Mi Band 5 proximity unlock. It's wonderful that someone is still trying to develop something better for that phone.
Edit: Ignore my broken grammar.
Click to expand...
Click to collapse
You can rest easy my friend i have used shrp for android 11 and it's great
It will not wipe your data
And my phone was rooted while flashing shrp
Just don't forget to disable avb before flashing both magisk patched boot.img and
shrp(fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
Coz I have faced the aftermath of not doing it which got me stuck in a bootloop.
It A12 supported ???
muerto_parao said:
It A12 supported ???
Click to expand...
Click to collapse
I don't know I'm kinda scared too as i have downgraded to android 10 and now finding it difficult to get a suitable version of twrp!
Manjotbenipal said:
I don't know I'm kinda scared too as i have downgraded to android 10 and now finding it difficult to get a suitable version of twrp!
Click to expand...
Click to collapse
It doesn't support A12, I flashed it already
muerto_parao said:
It doesn't support A12, I flashed it already
Click to expand...
Click to collapse
It'd take some effort for A12 support
areallydumbperson said:
It'd take some effort for A12 support
Click to expand...
Click to collapse
That's would be great , man
areallydumbperson said:
After some effort I have rebased the twrp tree for merlin to twrp 3.6.2_11-0 and after some builds and revisions I have it fully working
Credits:
Me (rebased tree)
Val (built for me as I have potato pc)
Cane (tested for me I literally don't own merlin lol)
method to install:
fastboot flash recovery (insert path to downloaded twrp here)
Device tree:
GitHub - halal-beef/twrp_device_xiaomi_merlin
Contribute to halal-beef/twrp_device_xiaomi_merlin development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Does this twrp support installation of custom roms and have close avb2.0 option?
Custom ROM installs should be supported but avb2.0 patching isn't included in the recovery as this is a clean unmodified twrp
doesn't boot from recovery.img not from fastboot boot either
whyem1x said:
doesn't boot from recovery.img not from fastboot boot either
Click to expand...
Click to collapse
worked after returning to android 10