Database Users

[RECOVERY][JALEBI][UNOFFICIAL] TWRP Recovery 3.0.2-0 For Yunique

Team Win Recovery Project 3.x, or Twrp for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Introduction :
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/
Source : TWRP.me
Flashing Method :
If you are already on existing TWRP just choose Install image -> navigate to downloaded recovery and choose it and install
Via Fastboot Mode :
fastboot flash recovery TWRP_3.0.2-0_Jalebi.img
Note : Make sure you are on unlocked bootloader if you are flashing custom recovery for first time
Status : Stable
Source : Github
Credits :
@charansai (Me) For Building
@Dees_Troy For TWRP
@amalappunni For Testing
@you For Using

Downlods And Changelog
TWRP 3.0.2-0
Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
Add Greek translation to some builds.
Click to expand...
Click to collapse
A Part From TWRP Changelog
Based On Latest Omni Source
Based On Latest Kernel Source (MM)
Fixed OTG
Click to expand...
Click to collapse
Download : TWRP 3.0.2-0_Jalebi

Reserved -2

Thnkx for ur work for jalebi

Mr. Ajay said:
Thnkx for ur work for jalebi
Click to expand...
Click to collapse
Want My Jalebi Updated So Updated Recovery

Root + Recovery + Android 7.1+ - Updated link to thread

Moved to:
https://forum.xda-developers.com/showthread.php?t=3609358
Hello
This is a place holder for the Device tree I'm about to submit for our device.
Currently, I'm in the middle of testing restore, but I totally did a cannibal install of 3.1.1 straight to my recovery partition, while I had Rootkernel 5.23 Boot.img TWRP 3.0.2 installed... and I had dual boot.
So I'm fairly confident, I have and can get the other versions of Android working for the E5823.
You all should just be able to pull the specific device branch, download the TWRP source, and then build using your prebuilt binary that Sony supplies, or use Flashtool to extract the ELF of the FOTA-Kernel.
I'll update this as the project progresses
Adios.
https://github.com/NeoBeum/XpeRicoverE5823
EDIT: Yep, just did a full restore. I will test encryption this week. I can go back and forth from the other boot image too. DRM Keys intact too, if you have your DK.ftf.
I'll get it working with Rootkernel & Magisk next.
Test Passed:
Complete Backup & Restore
Restore TA Partition to revert lost DRM Keys on Bootloader Unlock
Current issues:
Install from Zip/Image Permissions - 16/5/2017

Enlighten me please, what is this? Source code for recovery or rom?

MakeHav0 said:
Enlighten me please, what is this? Source code for recovery or rom?
Click to expand...
Click to collapse
TWRP Recovery Source for vanilla Sony AOSP. So no need for CM or Omnirom.
Team Win says they should be able to review the build in about a fortnight

[Aljeter] [03rd June 2019] TWRP 3.3.1-0 Moto G6 Play

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.​
PHP:
* Your warranty is now void.
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
Changelog For 3.3.1-0
Fix selinux issues during formatting - dianlujitao
Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
Add option to uninstall TWRP app from /system - Dees_Troy
Create digest for subpartitions - bigbiff
Install Guide:
For non rooted and rooted phones
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Brain
Download https:// drive .google.com/file/d/1-1MQqE42zIoLnqbYx-JTRQtVtnIV85Rt/view?usp=sharing (Remove space)
Put phone into fastboot mode (hold vol down + power button)
Connect phone to PC
Open a command prompt where you have fastboot and the TWRP image file located
Type the following in command prompt:
PHP:
fastboot flash recovery twrp-3.3.1-0-aljater.img
Note: For Windows 10 users who use the powershell and not cmd
The command will become:
PHP:
./ fastboot flash recovery recovery.img
Note: Test if it works in the JETER variant (I do not have that device, I have the ALJETER variant)
XDA: DevDB Information
twrp, Tool/Utility for the Moto G6 Play (Aljeter)
Contributors
TWRP Team
Me
Version Information
Status: Stable
Stable Release Date: 2019-06-03
Created 2019-06-03
Last Updated 2019-06-03

So this will allow flashing of A/B roms?

kwiksi1ver said:
So this will allow flashing of A/B roms?
Click to expand...
Click to collapse
I am not bad Moto G6 Play as the Moto G6 only have a / Vendor type A partition, you can also install custom rom (GSI) from an image file.
In the same way, I will try to compile a TWRP that supports the partition / vendor as a defect so that a custom roms GSI installation can be performed from a zip file.

Thread cleaned!
Kanged work must be addressed by developer himself using the report button or contacting any Mod. Future public posts will be cleaned again and users will be addressed.
Thank you

Will this TWRP be available on unofficialtwrp.com/
Do you know if there will ever be a official TWRP for Moto G6 Play?
I ask because I have enough experience to follow guides, but not enough to be security smart, which is ironic as I want a custom ROM to move away from Googles spying and bloat.

DulfaGreyny said:
Will this TWRP be available on unofficialtwrp.com/
Do you know if there will ever be a official TWRP for Moto G6 Play?
I ask because I have enough experience to follow guides, but not enough to be security smart, which is ironic as I want a custom ROM to move away from Googles spying and bloat.
Click to expand...
Click to collapse
To install a Custom ROM you do not need an build official TWRP , because in my opinion the cell phone should go better with the 64bit architecture and thus the device would be more useful, but since currently there is no support for the device itself, you can try installing a GSI ROM, apparently everything works, in LineageOS 16 Moto Actions do not work.

Don't use this.. yes it works, because the developer made sure of it, but this isn't the developer,
This guy was kindly helped by the developer and then stole that developers work. Then turned around and posted it here, risking all of your devices since he has no clue about it, just for a little attention.
Nice guy right?

If it seems like he's talking gibberish, it's cause he is. He has no clue how any of this works. But yes an official is in the works. In the meantime, thank god this guys an idiot and didn't erase his footsteps, suck it Allan

Alan1231999 said:
To install a Custom ROM you do not need an build official TWRP , because in my opinion the cell phone should go better with the 64bit architecture and thus the device would be more useful, but since currently there is no support for the device itself, you can try installing a GSI ROM, apparently everything works, in LineageOS 16 Moto Actions do not work.
Click to expand...
Click to collapse
I have installed custom roms before and as starkiller2 pointed out you make no sense. My question was about the security and quality control of what you have offered -which for all I know could be invasive or broken. Hence I was seeking some kind of verification of legitimacy; which you have given me albeit the opposite of what you may have intended.
It appears that some concern is shared by starkiller2 -thanks

I maintain my stance that Allan can choke on it

Give a link to twrp 3.3.1 I can not download

bronislav808 said:
Give a link to twrp 3.3.1 I can not download
Click to expand...
Click to collapse
That's because it was stolen work bud.

Why is this thread even up? @mods

Kuntitled said:
Why is this thread even up? @mods
Click to expand...
Click to collapse
When I tried taking my first guide thread down a mod told me they don't remove posts for archival purposes or something like that. Might be different though for the situation involved with this thread though

Kuntitled said:
Why is this thread even up? @mods
Click to expand...
Click to collapse
The mods were supposedly "investigating" it but never did anything. And Allan's ***** ass disappeared

[Recovery][Pitchblack-Recovery][Platina] Fork of TWRP for Mi 8 Lite

I have nothing to do with this project at all. I was simply introduced to it today from a helpful user. The fact that all the versions we have of TWRP are flawed in some way, it is nice there is yet another recovery choice that seems to be up to date and full of features. It does not appear to be backwards compatible with TWRP so you cannot restore TWRP backups with this.
EDIT: I have discovered if you rename your TWRP folder to PBRP, Pitchblack will see it just fine. I have NOT attempted to restore a TWRP backup using this., but it is promising it may work.
As I have nothing to do with this project I will not provide any support for issues you may have while using this recovery. I have so far not had any problems using it. Good luck!
Project Homepage
https://pbrp.ml/#home
Pitchblack-Recovery for Mi 8 Lite Platina Downloads
https://sourceforge.net/projects/pitchblack-twrp/files/platina/

Just got around to testing the restore function. It worked.....unlike TWRP. Thankfully! TWRP never has been able to.

I have discovered if you rename your TWRP folder to PBRP, Pitchblack will see it just fine. I have NOT attempted to restore a TWRP backup using this., but it is promising it may work.

can it be installed in miui 12.0.3 and android 10?
my device is mi 8 lite (platina)

Axon 7 Can access TWRP but cannot get into bootloader menu

So my current phone recently broke. So I decided to dust of my old Axon 7 which was still using Android 6.0.1. A bit old for these days since a lot of apps won't work. The best thing I could think of was to install a different rom. After a lot of work I finally managed to unlock the bootloader and install TWRP. Then I tried to flash a rom but to no avail. I have tried many things and now I can access only TWRP and EDL through ADB. I cannot access the Bootloader menu anymore. Does anyone know what to do next? How can I fix this and try to flash something again?
Edit: Forgot to mention that I currently have the most recent version of TWRP installed. And the flashing error I get is Error 7, Googled that and tried every "fix" but none of them worked. Another strange thing is that my phone used to be A2017G, but now when I connect it to my pc it shows up as A2017U, Is this a driver issue or did I change something unintended?

You can also boot to EDL from TWRP in terminal (reboot edl) and dfu/edl mode by pressing vol up+vol down and power button.
If your phone boot in dfu mode, use EDL Tool by djkuz.
Don't worry if it show up as A2017U - you won't lose any bands.
You didn't wrote much so I won't help.
Axon 7 scene is a little messed up. I'm getting lost in it myself. We've probably got 3 or 4 different twrp recoveries for different roms.
- official twrp from twrp.me website, compiled with marshmallow zte kernel for ailsa_ii - for stock roms, up to nougat.
- unofficial for ailsa_ii - for custom roms, up to nougat
Then, I don't know when, but device codename was changed from ailsa_ii to axon7.
- unofficial nfound/oki lab compiled with oreo zte kernel for axon7 - for oreo stock roms
- unofficial oki lab/twrp 3.2.3 for axon7 - for oreo/pie custom roms
Don't use twrp for oreo/pie roms on nougat bootstack.
There are two 3.2.3 twrp recoveries. One with vendor support, which isn't available anymore in LOS 16.0 thread, I attached it.
Other one without vendor support - from LOS 15.1 thread.
It doesn't change much. You will just gain an option to mount vendor partition in twrp.
Oki lab twrp for custom roms has a party tool for creating vendor partiton.
You can also use Party v0.5 script, to create vendor partition in twrp 3.2.3.
512MB vendor - for LOS and most custom roms
800MB vendor - for some old custom roms made by nfound

klałn said:
You can also boot to EDL from TWRP in terminal (reboot edl) and dfu/edl mode by pressing vol up+vol down and power button.
If your phone boot in dfu mode, use EDL Tool by djkuz.
Don't worry if it show up as A2017U - you won't lose any bands.
You didn't wrote much so I won't help.
Axon 7 scene is a little messed up. I'm getting lost in it myself. We've probably got 3 or 4 different twrp recoveries for different roms.
- official twrp from twrp.me website, compiled with marshmallow zte kernel for ailsa_ii - for stock roms, up to nougat.
- unofficial for ailsa_ii - for custom roms, up to nougat
Then, I don't know when, but device codename was changed from ailsa_ii to axon7.
- unofficial nfound/oki lab compiled with oreo zte kernel for axon7 - for oreo stock roms
- unofficial oki lab/twrp 3.2.3 for axon7 - for oreo/pie custom roms
Don't use twrp for oreo/pie roms on nougat bootstack.
There are two 3.2.3 twrp recoveries. One with vendor support, which isn't available anymore in LOS 16.0 thread, I attached it.
Other one without vendor support - from LOS 15.1 thread.
It doesn't change much. You will just gain an option to mount vendor partition in twrp.
Oki lab twrp for custom roms has a party tool for creating vendor partiton.
You can also use Party v0.5 script, to create vendor partition in twrp 3.2.3.
512MB vendor - for LOS and most custom roms
800MB vendor - for some old custom roms made by nfound
Click to expand...
Click to collapse
Thanks for the reply! I was a bit ahead of you and managed to create a vendor partition using the Party v0.5 script, now I can flash ROMs just fine but the system won't boot (blinking red light, black screen)
I am using the most recent TWRP version for Axon 7 (3.5.2_9-0), I am not sure if this is part of the problem
I've found some possible fixes related to my original question for getting into the bootloader menu, but I have no idea on what to change to regain access to it. I do remember that it said the device name was ailsa_ii as you mentioned, and that the bootloader version was not specified (it was just blank)
Edit: never mind the bootloader menu issue, I managed to get back into it. But the system still won't load.

On which bootstack you are right now?
Which rom you want to try?
Custom roms won't work on stock bootstacks.
First, I would recommend to backup persist/efs partition, before futher changes.
Second, I would recommend upgrade stock marshmallow to nougat, then nougat to oreo and after that, flash universal v2 oreo bootstack.
Bootloader/fastboot was locked by zte on most stock roms.
For what for you need fastboot mode? EDL mode isn't enough?
If you really need fastboot, you may try this aboot on oreo bootstack. Didn't try it with universal v2.

I have no idea what bootstack I am on right now to be honest. How can I check this?
I want to install LineageOS 17.1.
The bootloader is unlocked, I am sure of that.
Sorry for my ignorance, I know I am in way over my head but I am dedicated to make this work.

So you probably on stock marshmallow bootstack.
I still recommend to upgrade system step by step. From 6.0.1 to 7.0, then to 8.0 B02 and applying A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX.zip.
Why this way? Most of a7 users did that at beginning and official updates may do some changes to persist partition.
Some people complained about 50% battery bug, which came out of nowhere.
If you want take a risk, you can flash DrakenFX bootstack straight away or flash A2017G_B02_OREO_FULL_EDL in edl mode and then DrakenFX bootstack. At least - please - do efs partition backup using EDL Tool by djkuz, before doing such a jump.
I don't know if this gonna work. If you brick your device, you will have to download full edl packages, which may take even more time, than official way to upgrade.

Well, that didn't work. Guess it is bricked now because I cannot access recovery anymore, and my pc can no longer find it. Thanks for your help but I think it is time to buy a new one.

DNYO31 said:
Well, that didn't work. Guess it is bricked now because I cannot access recovery anymore, and my pc can no longer find it. Thanks for your help but I think it is time to buy a new one.
Click to expand...
Click to collapse
Have you tried booting phone to edl mode by holding vol-up + vol-down and pressing power button?
ZTE logo might not appear, but you should enter to dfu/edl mode by pressing those buttons.
It's really hard to make a brick of Axon 7.
In 2016-2017, I had to ground test points on the motherboard to leave DFU mode, but it's not necessary anymore.