Database Info

[RECOVERY][THEA] TWRP 3.2.3-0 Touch Recovery [OFFICIAL]

Team Win Recovery Project 2.x, or twrp2 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.
DOWNLOAD : https://dl.twrp.me/thea/
BUGS:
If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY][THEA] TWRP 3.2.3-0 Touch Recovery [OFFICIAL], ROM for the Moto G 2014 LTE
Contributors
luca020400, LuK1337
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2016-02-07
Last Updated 2018-08-07

Reserved

Reserved
Source code : motog2014devteam
Source code : CyanogenMod

ok and how can we install it?

javierutxo said:
ok and how can we install it?
Click to expand...
Click to collapse
fastboot flash recovery file.img

LuK1337 said:
fastboot flash recovery file.img
Click to expand...
Click to collapse
aja, and what about unlock bootloader and rooting? the same process than moto g 2014?

javierutxo said:
aja, and what about unlock bootloader and rooting? the same process than moto g 2014?
Click to expand...
Click to collapse
Yes

javierutxo said:
ok and how can we install it?
Click to expand...
Click to collapse
Take the steps from here http://forum.xda-developers.com/moto-g-2015/general/rooting-moto-g-2015-lte-xt1078-t3086069
Just change the twrp.mg for the one in this post.
Good Luck!

Thank you!! Its worked for me on XT1072

Hello, It worked just fine on my XT1078
Thanks!

Is it possible to make this an "official" release ?

551790 said:
Is it possible to make this an "official" release ?
Click to expand...
Click to collapse
Yes , but I'm not going to do that

luca020400 said:
Yes , but I'm not going to do that
Click to expand...
Click to collapse
Hi Luca! Can you explain shortly how you built this image? Any manual that you can point me to?
I'm asking because I'd like to build it also for peregrine...

New build up
Download

idk whats happening. i unlocked my phone and installed this recovery and when i try to enter in recovery mode it shows and android with the exclamation sign and never continues to the actual recovery. it just stays there forever and then reboots by itself. can anyone tell me what is wrong?

Maledroid said:
idk whats happening. i unlocked my phone and installed this recovery and when i try to enter in recovery mode it shows and android with the exclamation sign and never continues to the actual recovery. it just stays there forever and then reboots by itself. can anyone tell me what is wrong?
Click to expand...
Click to collapse
You haven't flashed twrp
Reboot to bootloader
By pc
fastboot flash recovery twrp-thea.img
( with admin/sudo )
Then reboot to recovery

luca020400 said:
New build up
Download
Click to expand...
Click to collapse
Hi Luca, thank you very much for your hard work on this device.
About this new release of TWRP, I'd like to know, if possible, what are the main differences with the previuos one.

cgb.spender said:
Hi Luca, thank you very much for your hard work on this device.
About this new release of TWRP, I'd like to know, if possible, what are the main differences with the previuos one.
Click to expand...
Click to collapse
TWRP fixes
The TWRP version still 2.8.6 but it's 2.8.7

My encrypted TWRP nandroid backups fail with the following error message:
E:createTarFork() process ended with ERROR=255
Click to expand...
Click to collapse
This only happens when I use encryption, and it always happens right near the end of backing up the Data partition (the System partition backup completes successfully).
N.B. The percentage of files and MB processed do not increase in-step, like with an unencrypted backup. The MB percentage increases to 90%+ far quicker than the percentage of files processed. When the percentages come in-line with each other near the end of the Data partition backup, it fails, and the above error message is given.
I was using a Titan build of TWRP to create nandroid backups on my Thea device previously, and had no issues with encrypted backups.
This is an issue, as there are sensitive security details stored in the backup, which must be encrypted with a strong password.

Internal Storage failure?
sunka1 said:
My encrypted TWRP nandroid backups fail with the following error message:
....
Click to expand...
Click to collapse
This happens to me all the time all of a sudden. I did not change anything at all, except for flashing a new CM version.
I also get a strange stat error, something with google.photo cache.
Yesterday, I have then flashed the new 2.8.6(7). from a few posts above and that gave my phone the rest. It might be because I flashed through TWRP itself into the recovery partition, but now additional to the backup error above when I want to erase dalvik cache, the recovery just hangs. I also can't restore a backup atm.
Now I have reflashed the real 2.8.6.0 recovery and it still hangs when I want to wipe dalvik... wtf is going on here?
And oh yea, my phone does not boot anymore either, it just loops at the flash screen...
UPDATE:
After I found some info on this thread about similar issues, I factory reset my phone with stock recovery (TWRP was not reliable anymore, even the 2.8.6.0 version that was running perfectly before) and then reflashed the latest CM on a wiped internal storage. Now I am up and running again with minimal loss of data due to my TB backups that are scheduled and save to the SD.
But this leaves a very weird feeling back, basically my phone was rendered useless out of nowhere (I was running the previous CM for 2 weeks already), making TWRP backups impossible and forcing me to wipe the internal storage with all media on it without giving me the chance to back it up (MTP in TWPR was also very flaky and died several times half in copy operations). Something is going very wrong with this phone, never ever had that on any of my 5 previous htc devices and the fact that the OnePlusOne users are among the main ones that reported similar issues, I have a feeling it is linked to cheap storage quality. Motorola is a Chinese company now after all... :-/

[Rom][Pixel Experience Android 9][Unofficial for Mi Pad 4 - Clover] [Magisk-Busybox]

Here is a Google Pixel Rom with Magisk,Busybox,Google Apps inside.
What is working:
Bluetooth
Wifi
Mobile Data
Sensors
What is not working:
Usb Connection
DT2W
Charging Led
Requirements:
Unlocked Bootloader Here
Twrp installed
Installation:
I install direct from Miui 10 Stable China Rom
Reboot into Twrp
Make a Backup from your Current Rom!!!You can go back with the Backup to 8.1 Miui10!
Wipe Data with "Yes"
Go back to Advanced Wipe and wipe Cache,Dalvik,Data and System,reboot again in Twrp
Flash the Rom
Do not Reboot,wipe Data with "Yes"
Reboot.
It booted 2-3 times on the first boot,no Panic in 3-5 min Boot into System.
If the icons are too big, you can set the DPI in the Developer Options​
Download Rom PE 9.0
MD5:93a78e98144915f94dae566ad088e7d6
Version Information:
ROM OS Version: 9.0 Pie
ROM Kernel: Linux
Based On: Pixel Experience
Status: Beta/Test
Created :27.November 2018
Last Updated :
SuperR. for the Kitchen
topjohnwu for Root Magisk
!Warning!
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,etc...
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​

Reseved

DT2W？

KuroNoSeiHai said:
DT2W？
Click to expand...
Click to collapse
No

Not support exFat ,and can't reboot back to twrp. but thank you for your work.

Great rom, thanks for support

Hi. What Device tree use for your rom build?

tom.android said:
Not support exFat ,and can't reboot back to twrp. but thank you for your work.
Click to expand...
Click to collapse
Mean Sd Card for Exfat Support?
I have Problems after First boot with SD Card,does't work.I copy all Files to Pc with Card Reader,format Sd Card and put in Mi Pad and the Card works.
Twrp works but longer Boot.I use Twrp from LR Team download in first Post.
Or boot into Twrp via Fastboot with ADB Command.I restore back to Miui v10 and install the Rom again,Twrp works 100 Percent.

SwipeIT said:
Hi. What Device tree use for your rom build?
Click to expand...
Click to collapse
This is a Treble Rom from Pixel Phone.The Original img works with the most newest Phones,Huawei Mate 10 Pro,Samsung Galaxy S8/9 etc.
Put this Rom here works only with Mi Pad 4 Clover!.If you install on other Devices abort the installation with Error 7 in Twrp.
I extract the Original img with the Rom Kitchen make the Rom for Mi Pad 4 Clover.

tom.android said:
Not support exFat ,and can't reboot back to twrp. but thank you for your work.
Click to expand...
Click to collapse
Power off the Pad
Press and hold Volume up and Power Button at same time.

im downloading ... thanks so much

letschky said:
What is not working:
Usb Connection
DT2W
Charging Led
Click to expand...
Click to collapse
Screen shutdown does not work with a smart cover too.
Is it possible to fix it?
Tanks

Any screenshots?

tim_dnepr said:
Screen shutdown does not work with a smart cover too.
Is it possible to fix it?
Tanks
Click to expand...
Click to collapse
Not at the Moment,i have not a Smart Cover!

After installing the first boot, I ask for it
passwords. What password?

letschky said:
Not at the Moment,i have not a Smart Cover!
Click to expand...
Click to collapse
You might be able to test it with any magnet.

awesome great work!
---------- Post added at 07:58 AM ---------- Previous post was at 07:50 AM ----------
if the rom support pad4 plus ?

Can you post sources? Kernel, device tree?

it's impossible to connect to the hidden wifi networks.
I have tested with 2.4 and 5
EDIT:
Solution for hidden WiFi problem
When you are saving a new network, open Advanced options dropdown, and set the Hidden network to Yes. This way your phone will connect to hidden WiFi.
source

Hi guys!
I must have been doing something wrong.
I installed it and in the first boot it asks for my password, which I guess is the one associated with my MI Account. I enter the password and I get the following message:
DECRYPTION UNSUCCESSFUL
The password you entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.
And a button saying: RESET PHONE that takes me to the TWRP recovery.
I get this message even before the OS loads.
ANY IDEAS on how to solve this, please?

OP6 after FULLROM Flash i lost the TWRP-Recovery

Hello Android community ....
I have a problem with my rooted OP6.
I always use my devices with root but since model OP6 I'm too stupid for that or have not found any suitable instructions?
I root and install the TWRP on the OP6
then I install the original FULLROM followed by the current and matching MAGISK to get root
and it boots perfectly including root and everything is great!
but the TWRP is always gone ...
that makes me totally crazy
What am I doing wrong or what can/must do differently so that the TWRP recovery stays on for the next time?
Does anyone have a tip for me?
Many Thanks
VG
Z.

This is how you do it from twrp.
Flash rom (DON'T REBOOT)
Flash twrp (now reboot to recovery)
Flash magisk and boot = done.
Full roms will write over partitions.

whizeguy said:
This is how you do it from twrp.
Flash rom (DON'T REBOOT)
Flash twrp (now reboot to recovery)
Flash magisk and boot = done.
Full roms will write over partitions.
Click to expand...
Click to collapse
Thanks - maybe this also helps to resolve one of my confusions: will this now also work with Standard (not BluSpark) TWRP and Android Pie - there's all kinds of mixed statements online. Best

CoffeeMachineSwitch said:
Thanks - maybe this also helps to resolve one of my confusions: will this now also work with Standard (not BluSpark) TWRP and Android Pie - there's all kinds of mixed statements online. Best
Click to expand...
Click to collapse
I always use blu-spark. Always work

whizeguy said:
I always use blu-spark. Always work
Click to expand...
Click to collapse
thanks - but isn't that another source of complexity and error, as another party (bluSpark developer) is involved on top of TWRP team? And Magisk. Seems like many cooks throwing in ingredients to root, while the Android system itself keeps updating and changing....

People need to learn to READ

Problems with TWRP

I was running OOS 9.3.5 on my GM1917 and using version 3.3.1-2 of TWRP. Everything worked flawlessly. But since updating Oxygen OS to 10.0.2 I can't get anything to mount in TWRP (not working on any newer version of TWRP either). It also no longer asks for my pin to decrypt the data and reads as 0mb on the internal storage. I've already tried the usual formatting data and switching from ext4 to ext2 and back, and this also always leads back to 0mb. Is there something different with the data encryption on OOS 10? Or have I just flashed something wrong. I really need TWRP (or any recovery for that matter) because I really don't want to have to factory reset every time an update rolls around. I'm new to this so bear with me. If anyone could point me in the right direction, I'd highly appreciate it!

jwbritt01 said:
I was running OOS 9.3.5 on my GM1917 and using version 3.3.1-2 of TWRP. Everything worked flawlessly. But since updating Oxygen OS to 10.0.2 I can't get anything to mount in TWRP (not working on any newer version of TWRP either). It also no longer asks for my pin to decrypt the data and reads as 0mb on the internal storage. I've already tried the usual formatting data and switching from ext4 to ext2 and back, and this also always leads back to 0mb. Is there something different with the data encryption on OOS 10? Or have I just flashed something wrong. I really need TWRP (or any recovery for that matter) because I really don't want to have to factory reset every time an update rolls around. I'm new to this so bear with me. If anyone could point me in the right direction, I'd highly appreciate it!
Click to expand...
Click to collapse
Try to change your slot. Means if you are on a change to b or b to a from twrp reboot section

rohitg347 said:
Try to change your slot. Means if you are on a change to b or b to a from twrp reboot section
Click to expand...
Click to collapse
This was initial thought too, but TWRP won't allow me to switch slots because it is "unable to mount storage"

Since you moved over to Android 10 , use the latest TWRP, fastboot flash it, or flash it as a module in Magisk.
The older versions of TWRP do not work well with Android 10.

@soka said:
Since you moved over to Android 10 , use the latest TWRP, fastboot flash it, or flash it as a module in Magisk.
The older versions of TWRP do not work well with Android 10.
Click to expand...
Click to collapse
Also tried this with no luck, but thanks anyway

jwbritt01 said:
I was running OOS 9.3.5 on my GM1917 and using version 3.3.1-2 of TWRP. Everything worked flawlessly. But since updating Oxygen OS to 10.0.2 I can't get anything to mount in TWRP (not working on any newer version of TWRP either). It also no longer asks for my pin to decrypt the data and reads as 0mb on the internal storage. I've already tried the usual formatting data and switching from ext4 to ext2 and back, and this also always leads back to 0mb. Is there something different with the data encryption on OOS 10? Or have I just flashed something wrong. I really need TWRP (or any recovery for that matter) because I really don't want to have to factory reset every time an update rolls around. I'm new to this so bear with me. If anyone could point me in the right direction, I'd highly appreciate it!
Click to expand...
Click to collapse
Use version -70.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3932943

hallo dare said:
Use version -70.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3932943
Click to expand...
Click to collapse
Is this really the solution? Flashing this TWRP will make the storage mount and decrypt the device every time the recovery starts?

jwbritt01 said:
Is this really the solution? Flashing this TWRP will make the storage mount and decrypt the device every time the recovery starts?
Click to expand...
Click to collapse
Never had an issue using this version on android 10

jwbritt01 said:
Is this really the solution? Flashing this TWRP will make the storage mount and decrypt the device every time the recovery starts?
Click to expand...
Click to collapse
Did the -70 version worked for you?

jwbritt01 said:
This was initial thought too, but TWRP won't allow me to switch slots because it is "unable to mount storage"
Click to expand...
Click to collapse
Hi, have you tried to use the fastboot command to change slot? I had the same problem after I tried to flash the latest beta without flashing magisk and twrp after, luckily the other slot was working .
Change slot via fastboot and then restart to recovery.
The command should be "fastboot --set-active=b" (or a, depeding on which slot is working)

Question [HELP] I keep failing trying to flash a custom Android 12 ROM on the Redmi Note 11 Pro (veux). Can someone help me figure out what I'm doing wrong?

I've owned Samsung, Lenovo and Moto phones before, and I never had any problems unlocking them and flashing custom recoveries and ROMs. This is my 2nd Xiaomi phone and like the 1st I keep bricking and unbricking it. The only thing I can manage to do is sometimes get TWRP on it, or the normal ROM.
- Version: European version of the Redmi Note 11 Pro, codename veux.
- TWRP: https://forum.xda-developers.com/t/twrp-3-7-0_12-for-veux-peux.4520689/
- ROM: https://forum.xda-developers.com/t/rom-13-veux-peux-official-evolution-x-11-09-22.4497785/
___
1st attempt:
1 - After unlocking the bootloader it reinstalled a clean ROM. I then forgot to turn USB debugging on so that was my fault. Because after that I went into fastboot and flashed this TWRP with fastboot flash boot name.img
2 - On this first try I then rebooted to recovery, but it sent me to the normal one instead. In essence I bricked it so I followed this guide to reset it
___
2nd attempt:
1 - I enable USB debugging
2 - go into fastboot: fastboot flash boot name.img
3 - reboot to recovery
4 - in TWRP I try to flash the ROM from the internal storage. It fails after around 33% or something. Errors about not being able to mount certain folders
___
3rd attempt:
1 - reboot to recovery
2 - try and sideload the ROM from my laptop with the command adb sideload name.zip
3 - fails around 40% with similar errors
___
4th attempt:
1 - reboot to bootloader
2 - try instead fastboot boot name.zip to flash the ROM. It gives me the error: requested download size is more than max allowed fastboot
___
In between these tries TWRP sometimes loses touchscreen functionality. I notice when I flash OrangeFox and then TWRP again, I get touchscreen functionality back. I know this is a well known issue but it's interesting I can back TWRP working again when doing the above.
Another interesting is that when I flash OrangeFox and reboot to recovery, it's still TWRP.

When you flash a new ROM, you need to format the userdata and the cache partitions.
EDIT:
Btw, i'm curious to know where you found your OrangeFox build. ^^

Sneilas said:
When you flash a new ROM, you need to format the userdata and the cache partitions.
EDIT:
Btw, i'm curious to know where you found your OrangeFox build. ^^
Click to expand...
Click to collapse
I believe I did format data, cache and dalvik cache as usual. Hm, will check again.
I forgot where I got the OrangeFox from. Might be nothing though.

kerelberel said:
I believe I did format data, cache and dalvik cache as usual. Hm, will check again.
I forgot where I got the OrangeFox from. Might be nothing though.
Click to expand...
Click to collapse
Btw, i do not recommand to flash unofficial images if the maintainer not released it's device tree on GitHub and not linked it on his thread.
We can't know what's inside the recovery.
The recovery can be infected by a malicious code.

Sneilas said:
When you flash a new ROM, you need to format the userdata and the cache partitions.
EDIT:
Btw, i'm curious to know where you found your OrangeFox build. ^^
Click to expand...
Click to collapse
So I made sure to format everything this time. But because I am stoopid I then accidentally sideloaded a MIUI ROM instead of Evolution. I copy/pasted the wrong file name in the cmd window, lol. I was surprised to see the Evolution logo after rebooting, so I got the ROM I wanted by accidentally flashing the other one.
Do I have MIUI on one partition and Evolution on the other? Is that even possible?

kerelberel said:
So I made sure to format everything this time. But because I am stoopid I then accidentally sideloaded a MIUI ROM instead of Evolution. I copy/pasted the wrong file name in the cmd window, lol. I was surprised to see the Evolution logo after rebooting, so I got the ROM I wanted by accidentally flashing the other one.
Do I have MIUI on one partition and Evolution on the other? Is that even possible?
Click to expand...
Click to collapse
From here, i recommand you to ask the maintainer of the Evolution X ROM of your device.
Send him your device infos (code name, processor, etc...).
If you can't access to these info on from phone, contact the reseller of your phone.
Maybe your specific device is not compatible with the ROM.
I'm not enough experienced to help you more.

I don't know if twrp works on veux.
I flashed the boot.img and vendor_boot.img provided by the custom ROM.
The custom ROM was updated using the sideload in recovery mode.
It must be unlocked. USB debug doesn't matter.

Sneilas said:
From here, i recommand you to ask the maintainer of the Evolution X ROM of your device.
Send him your device infos (code name, processor, etc...).
If you can't access to these info on from phone, contact the reseller of your phone.
Maybe your specific device is not compatible with the ROM.
I'm not enough experienced to help you more.
Click to expand...
Click to collapse
I'm fine now, the ROM works, afterwards I also installed Magisk successfully so TWRP works as expected too.
osebee said:
I don't know if twrp works on veux.
I flashed the boot.img and vendor_boot.img provided by the custom ROM.
The custom ROM was updated using the sideload in recovery mode.
It must be unlocked. USB debug doesn't matter.
Click to expand...
Click to collapse
It does, the one I linked in my first post is the one from this specific subforum.
If you need help you can PM me.

Seems like you've managed to fix the problem, and USB debugging only works when you're booted inside the rom, it doesn't do anything in recovery/fastboot.

kerelberel said:
I'm fine now, the ROM works, afterwards I also installed Magisk successfully so TWRP works as expected too.
It does, the one I linked in my first post is the one from this specific subforum.
If you need help you can PM me.
Click to expand...
Click to collapse
Oh ok, i thought you still had problems. ^^

Ritik17 said:
Seems like you've managed to fix the problem, and USB debugging only works when you're booted inside the rom, it doesn't do anything in recovery/fastboot.
Click to expand...
Click to collapse
USB debugging works in some stock/custom recoveries, but in stock recoveries it is limited to sideloading updates signed by the device manufacturer.