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.
Code:
#include <std_disclaimer.h>
/*
*
* 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.
*
*/
Features:
- Decrypt works
- Mtp works
- Adb works
- Android 12/13 support with system_ext (like Evolution X, LineageOS and CrDroid)
Download:
TWRP 3.6.2-12.1 Unofficial by LuMorningStarr
https://sourceforge.net/projects/dippertests/files/recovery/TWRP_3.6.2-12.1_dipper_system-ext.img/download
TWRP 3.7.0-12.1 Unofficial by LuMorningStarr
https://sourceforge.net/projects/di...WRP_3.7.0-12.1_dipper_system-ext.img/download
TWRP 3.7.0-12.1 V2 Unofficial by LuMorningStarr
(Fix for error1 when flash CrDroid/LoS/Evolution X A13)
https://sourceforge.net/projects/di..._3.7.0-12.1_dipper_system-ext_V2.img/download
Source code:
https://github.com/LucyfMorning/twrp_device_xiaomi_dipper
Donations:
Pay Matheus Vinícius Nunes da Costa using PayPal.Me
Go to paypal.me/LucyfMorning and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
www.paypal.me
Credits:
@REIGNZ3
Created 2022-09-09
Updated 2022-10-22
Reserved
It's fully functional in LineageOS and probably most ROMs with to his bases, like CrDroid (tested).
Not work on Pixel Experience and most ROMs who uses Pixel Experience tree's (Evolution, PixelPlusUI and others more).
I assume this provides decryption support for Android 12?
UnNamedChronos said:
only for Lineage Bases custom ROMs)
Click to expand...
Click to collapse
abtekk said:
I assume this provides decryption support for Android 12?
Click to expand...
Click to collapse
Look at this point
I used in LineageOS and really work. But in pixel experience not work
UnNamedChronos said:
Look at this point
I used in LineageOS and really work. But in pixel experience not work
Click to expand...
Click to collapse
Don't worry.
Thanks.
So has anybody tested it and confirms decryption works with Android 12 (Lineage 19.1) ? Is this still under active development, maybe we should rebase on new twrp sources
milouk said:
So has anybody tested it and confirms decryption works with Android 12 (Lineage 19.1) ? Is this still under active development, maybe we should rebase on new twrp sources
Click to expand...
Click to collapse
Works for me. It seems to me that the decryption process is quite slower than it used to be on LOS18.1, but at least it works.
milouk said:
So has anybody tested it and confirms decryption works with Android 12 (Lineage 19.1) ? Is this still under active development, maybe we should rebase on new twrp sources
Click to expand...
Click to collapse
Work in LineageOS 19.1 and in CrDroid 8.x but only in this ROMs at last
And update is Available for A13 ROM's
Now fixed flash for CrDroid and evolution X A13 ROM
Thank you very much for this TWRP version. I've installed LineageOS 19.1 official 11/03/2022 version a few days ago using your TWRP version and this worked fine.
Not sure if its normal behaviour, but before I formatted my data I updated TWRP "3.5.x" to "3.7.0-12.1 V2 Unofficial by LuMorningStarr". After this I was not able to decrypt my phone (running LineageOS 18.1).
After formatting/wiping the phone I was able to install LineageOS 19.1 with MindTheGapps and everything went well. I have tried to reboot into TWRP after installing LineageOS 19.1 and I was able to decrypt my phone. Will have to see if updating the rom will also work, but seems promising.
tharonny said:
Thank you very much for this TWRP version. I've installed LineageOS 19.1 official 11/03/2022 version a few days ago using your TWRP version and this worked fine.
Not sure if its normal behaviour, but before I formatted my data I updated TWRP "3.5.x" to "3.7.0-12.1 V2 Unofficial by LuMorningStarr". After this I was not able to decrypt my phone (running LineageOS 18.1).
After formatting/wiping the phone I was able to install LineageOS 19.1 with MindTheGapps and everything went well. I have tried to reboot into TWRP after installing LineageOS 19.1 and I was able to decrypt my phone. Will have to see if updating the rom will also work, but seems promising.
Click to expand...
Click to collapse
Version 3.7 v2 is for the most current ones that use a change in boot mode, the official version should be more beneficial over using older versions like Android 11 and below.
The one I created is for 12 and above that uses system ext and the new boot mode
Hi guys,
please help me out. I try to install los 20 with twrp decryption.
Here is what I try:
Bootloader is unlocked, I used los 19 before.
Flash stock rom dipper global V12.0.3.0.QEAMIXM.
Enable ADB USB debugging.
Reboot into Fastboot.
fastboot flash recovery TWRP_3.7.0-12.1_dipper_system-ext_V2.img
Reboot into Recovery.
Wipe > Format Data.
Wipe > Advanced Wipe > Dalvik + Data + System.
Reboot into Recovery, because Data is not there(?).
=> Decryption gone: All folders in /sdcard/ have cryptic names.
I'm sure, I do something stupid, please help me.
I'm not into en/decryption in Android at all. Maybe I can not use encryption at all? Or is this not good?
haxnhaxn said:
Hi guys,
please help me out. I try to install los 20 with twrp encryption.
Here is what I try:
Flash stock rom dipper global V12.0.3.0.QEAMIXM.
Enable ADB USB debugging.
Reboot into Fastboot.
fastboot flash recovery TWRP_3.7.0-12.1_dipper_system-ext_V2.img
Reboot into Recovery.
Wipe > Format Data.
Wipe > Advanced Wipe > Dalvik + Data + System.
Reboot into Recovery, because Data is not there(?).
=> Encryption gone. All folders in /sdcard/ have cryptic names.
I'm sure, I do something stupid, please help me.
Click to expand...
Click to collapse
Yeah... Ask in Lineage thread
Thank you for your answer, sorry if I bothered you.
Its working now.
Insead of the wiping in your recovery I used lineageos recovery (Factory Reset, then Format data / factory reset), then switched back to your recovery for installing rom.
UnNamedChronos said:
Version 3.7 v2 is for the most current ones that use a change in boot mode, the official version should be more beneficial over using older versions like Android 11 and below.
The one I created is for 12 and above that uses system ext and the new boot mode
Click to expand...
Click to collapse
And which 3.7.0-12.1 should I pick (V1 or V2) when I want to Update from LOS 18.1 to LOS 19.1?
I have already installed TWRP 3.7.0_9-0.
I don't want to wipe my whole phone like @tharonny just to get LOS 19.1 running.
G A S T said:
And which 3.7.0-12.1 should I pick (V1 or V2) when I want to Update from LOS 18.1 to LOS 19.1?
I have already installed TWRP 3.7.0_9-0.
I don't want to wipe my whole phone like @tharonny just to get LOS 19.1 running.
Click to expand...
Click to collapse
It's impossible update android 11 to 12 without loose your data... Better make and backup of your files and make the upgrade... Always
V2 work for both
On the contrary, I've dirty flash updated from 10 to 12 without problems. With the minor hiccup that the 3.7.0-12.1 twrp was no longer able to decrypt the old A-10 partition. But after installing and booting A-12, encryption was upgraded and twrp worked again.
(pays off to have an usb-c connectable usb stick ready in case of decrypt issues)
urigg said:
On the contrary, I've dirty flash updated from 10 to 12 without problems. With the minor hiccup that the 3.7.0-12.1 twrp was no longer able to decrypt the old A-10 partition. But after installing and booting A-12, encryption was upgraded and twrp worked again.
(pays off to have an usb-c connectable usb stick ready in case of decrypt issues)
Click to expand...
Click to collapse
So you flashed the new ROM with the old TWRP and flashed the TWRP from here right after the A12-Update via your USB-connectable Stick?
Related
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.
TWRP 3.2.1 Changelog: https://twrp.me/site/update/2017/12/09/twrp-3.2.1-0-released.html
Installation instructions: Use the official TWRP app (requires root), available here and here. If you already have TWRP installed, you can also download the latest available img and flash it from recovery.
DOWNLOAD: https://dl.twrp.me/armani/
More info: https://twrp.me/devices/xiaomiredmi1s.html
Device source: https://github.com/TeamWin/android_device_xiaomi_armani
Kernel source: https://github.com/LineageOS/android_kernel_xiaomi_armani
XDA:DevDB Information
Team Win Recovery Project, Tool/Utility for the Xiaomi Redmi 1S
Contributors
fefifofum, Dees_Troy, bigbiff
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2016-11-27
Last Updated 2017-12-11
New build released
TWRP 3.0.2-1 was just released for armani, with updates needed for cm-14.1 nightlies to work properly. You can download from here and install (as an image) from twrp itself.
wow , great OP
I still can not access adopted storage.
Sent from my HM 1SW using Tapatalk
fefifofum said:
TWRP 3.0.2-1 was just released for armani, with updates needed for cm-14.1 nightlies to work properly. You can download from here and install (as an image) from twrp itself.
Click to expand...
Click to collapse
Thanks, but I don't see the changelog for twrp-3.0.2-1?
I got no touch screen on the recovery upon flashing this similar to the problem i have on flashing new roms
Twrp
in twrp 3.0.2 i flashed cm rom's via otg bt in twrp 3.0.2.1 i cant
is the problem only with me or everyone has it
New build released
TWRP 3.1.0 has been released. Please check post 1 for more info.
HI @fefifofum, the touch screen issue is back for TWRP 3.1.0 and would not work again.
before installing twrp 3.1, I was on twrp 3.0.2. I have set SD card as internal storage. And in 3.0.2 it displayed only root folder it happens randomly (previously it displayed internal and shared SD, also at the time of installing nightlies). After installing 3.1 it showed both internal and shared. How to solve?
mobaddict said:
HI @fefifofum, the touch screen issue is back for TWRP 3.1.0 and would not work again.
Click to expand...
Click to collapse
No issue's on my device installed few ROMs took backup's and restored ROM's
hafeez90 said:
No issue's on my device installed few ROMs took backup's and restored ROM's
Click to expand...
Click to collapse
I think this is the same issue as the previous issue for phones with replacement touchscreen modules.
Bug report.. When i want to reboot recovery or bootloader , it will reboot to system, anyone can confirm this?
#problem solved, reflashing recovery again.. Sorry
No response from Touch Screen
hafeez90 said:
No issue's on my device installed few ROMs took backup's and restored ROM's
Click to expand...
Click to collapse
I am also having the same issue. It takes time to get into twrp but once it is in twrp I cant press any buttons and no touch screen responce any solution? or its is bug?
Me too experience "No response from Touch Screen"
I was also having touch screen problem but after reflashing the twrp IMG its gone
twrp home get stuck while boot into recovery with usb otg connected .
PowerOff causes reboot to system
indraian said:
Bug report.. When i want to reboot recovery or bootloader , it will reboot to system, anyone can confirm this?
#problem solved, reflashing recovery again.. Sorry
Click to expand...
Click to collapse
I tried reflashing but it doesnt work.. PowerOff reboots to system!
vbvn said:
I tried reflashing but it doesnt work.. PowerOff reboots to system!
Click to expand...
Click to collapse
Try to instal a rom.. It happen when you wipe everythig but not yet instal a rom.
Due to encrypted on internal storage by new version rom zui oreo, and still unable to decrypted by latest official TWRP 3.2.1-0, so now i release ported TWRP 3.2.1-0 the one from official to be unofficial version in order to decrypted and accessed internal storage in rom zui oreo from recovery side.
Features:
Multilanguages
Support aroma installer
Otg
WARNING
Don't try to flash on other device accept for ZUK Z2 Plus
Use with your own risk
I don't responsible if your device damage or bricked
Link: unofficial-twrp-3.2.1-0-zuk-z2-plus- by- hendi-2nd-rev
https://mega.nz/#!DdhVED4R!kso7PCRo5Wqg87FVlA22xKvk1feCVklbEcbtGSx7asI
Thanks to and all credits go to TWRP teams
Is it working good? Any issues?
is it valid for any rom 8.0 ??
Thank you very much
Enviado desde mi Z2 Plus mediante Tapatalk
Aroma doesn't work and is inverted
spandu500 said:
Aroma doesn't work and is inverted
Click to expand...
Click to collapse
Soon in 2nd revision aroma will be reverted and working
how do i flash it ? its an img file not zip ... Pls help
adil786ali63 said:
how do i flash it ? its an img file not zip ... Pls help
Click to expand...
Click to collapse
Twrp install on the bottom install image
Wysłane z mojego ZUK Z2132 przy użyciu Tapatalka
is the 2nd revision of this twrp working good? any problems anywhere?
I wanted to go back to the my AICP nougat after seeing how horrible the battery life became in 3.5.243ST_Deodex. To my nightmare, I got the fix encryption msg on first boot. So, thinking its clearly with hendi's TWRP alone, I flashed the TWRP 3.2.1-0 from TWRP website but all my stuff disappeared (encrypted perhaps). Had to format everything. So those who want to ONLY use 3.5.243 deodex and not to jump roms afterwards, this recovery is good. It's included by default in the rom so it gets overwritten anyway if u are flashing 3.5.243_ST Deodexed. Just a warning for others so that they don't suffer as me.
dark_prince said:
I wanted to go back to the my AICP nougat after seeing how horrible the battery life became in 3.5.243ST_Deodex. To my nightmare, I got the fix encryption msg on first boot. So, thinking its clearly with hendi's TWRP alone, I flashed the TWRP 3.2.1-0 from TWRP website but all my stuff disappeared (encrypted perhaps). Had to format everything. So those who want to ONLY use 3.5.243 deodex and not to jump roms afterwards, this recovery is good. It's included by default in the rom so it gets overwritten anyway if u are flashing 3.5.243_ST Deodexed. Just a warning for others so that they don't suffer as me.
Click to expand...
Click to collapse
As i mention before dearest brother, if you read first post, zui oreo by default will encrypted and not allow you to access internal storage from recovery for security reason, if you using or flashing with official TWRP,
not because zui oreo deodexed,
if you want switch back to custom rom first
keep stay in unofficial twrp don't hurry to flash official twrp because you internal storage in state encrypted by zui oreo,
next wipe data/art catche, cache, and system, then you can flash custom rom,
after rebooting you can change to any twrp as you like, so your data still intact
Happy flashing
Can it also be used for the ZUK Edge?
hendibudi said:
Due to encrypted on internal storage by new version rom zui oreo, and still unable to decrypted by latest official TWRP 3.2.1-0, so now i release ported TWRP 3.2.1-0 the one from official to be unofficial version in order to decrypted and accessed internal storage in rom zui oreo from recovery side.
Features:
Multilanguages
Support aroma installer
Otg
WARNING
Don't try to flash on other device accept for ZUK Z2 Plus
Use with your own risk
I don't responsible if your device damage or bricked
Link: unofficial-twrp-3.2.1-0-zuk-z2-plus- by- hendi-2nd-rev
https://mega.nz/#!DdhVED4R!kso7PCRo5Wqg87FVlA22xKvk1feCVklbEcbtGSx7asI
Thanks to and all credits go to TWRP teams
Click to expand...
Click to collapse
Bro.. Can we have an updated version of TWRP with treble support? The developer of AOSP extended has uploaded TWRP with treble support but I'm not sure if it encrypts the device or not ... So would love to see it with your version of TWRP.. Thanks
Thank you! You are a lifesaver! I needed TWRP to solve bootloop issues coused by magisk and your TWRP solved the issue.
so if i flash this i will be able to access internal data on twrp ? i am zui 3.5.321
sanjay.2704 said:
so if i flash this i will be able to access internal data on twrp ? i am zui 3.5.321
Click to expand...
Click to collapse
Yes you can
shafa.musraf said:
Yes you can
Click to expand...
Click to collapse
Can I flash this via ADB coz if I understand right once I boot to twrp to flash this I will again loose internal memory.. flashing via ADB should avoid that.. right??
sanjay.2704 said:
Can I flash this via ADB coz if I understand right once I boot to twrp to flash this I will again loose internal memory.. flashing via ADB should avoid that.. right??
Click to expand...
Click to collapse
Yes you can flash via ADB
It is the 2nd or 1st version
adil786ali63 said:
Bro.. Can we have an updated version of TWRP with treble support? The developer of AOSP extended has uploaded TWRP with treble support but I'm not sure if it encrypts the device or not ... So would love to see it with your version of TWRP.. Thanks
Click to expand...
Click to collapse
+1 that that just like a magic!Ahhh
Flashing AEX wouldnt encrypt ur device but some treble ROM indeed.
But u can flash the universal decrypting patches after flashing a data-encrypted ROM in a treble-supported TWRP instead.
Can you please update the link, can't download the file with MEGA link,
Here's my situation, I can't flash anything with TWRP cause it can't mount Data & internal storage,
I can use OTG though, But, I can boot into my phone normally, IF I connect a charger while it's at White ZUK logo, but if I unplug the charger and try to play PUBGM (or any power hungry tasks), it shuts down immediately, I'm on deodexed ZUI 4 BTW. I can use the phone as long as it's connected to the charger without any issues, Just can't figure out if it's a software issue, or is it with my battery.
aaaaand it booted!
I just flashed Resurrection Remix GSI by phhusson and it works. With EMUI 8 beta you can now flash a treble ROM. Still, this requires further testing so be careful. I'm not responsible for bricked phones. Here are the steps:
1. Make sure your device is on EMUI 8 beta with unlocked bootloader (guide: https://forum.xda-developers.com/honor-6x/development/hwota7-hwota8-honor-6x-t3792601)
2. Download GSI from this thread https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688 and move it to the folder where you installed ADB
Note: Honor 6x doesn't support seamless update so you want the A-only image, not the A/B one. Just in case you don't know already, Honor 6x has arm64 architecture.
3. Open cmd and navigate to your ADB folder
4. Reboot your phone to fastboot mode and type 'fastboot flash system name-of-the-image.img' where name-of-the-image.img is your downloaded GSI.
5. Hit enter and wait for it to finish installing
6. Famous words: "Reboot and pray"
Problems:
1. Since we don't have a treble-compatable TWRP build yet, there is no way to install gapps for now. I will try to find an image that includes them.
2. All the problems present on the actual ROM (check ROM thread)
3. There are likely others. (There always are some)
I'd like it if others tried to flash this and share their experiences here.
Thanks to @phhusson, @vovan1982, @HassanMirza01, Huawei, RR team and everybody else I forgot to mention.
How's the battery life?
Amirk365 said:
How's the battery life?
Click to expand...
Click to collapse
I'm flashing AOSP right now. It has gapps preloaded so I'll update when I've tested enough.
TheParallelOne said:
I'm flashing AOSP right now. It has gapps preloaded so I'll update when I've tested enough.
Click to expand...
Click to collapse
Thanks,in the mean time I'm looking for a proper cable to root my phone lol
UPDATE:
I flashed AOSP GSI and it boots normally as well. Has gapps and root as well, but you'll need the og supersu (phh's). Chainfire's su doesn't work. Also, you can't give adb root access via dev options so you cant pull boot image to patch it with magisk right away. I'm also unable to get stock camera to work but will experiment with that in the future. Battery life seems a bit better than on nougat roms but then again I'm running pure AOSP with no major battery consumer app on it for now. That's it for now.
@TheParallelOne
Did you try to use stock camera app from there?
https://forum.xda-developers.com/project-treble/trebleenabled-device-development/huawei-stock-camera-app-treble-roms-t3735169
Cool that you already tried to flash a GSI image :good:
TheParallelOne said:
aaaaand it booted!
I just flashed Resurrection Remix GSI by phhusson and it works. With EMUI 8 beta you can now flash a treble ROM. Still, this requires further testing so be careful. I'm not responsible for bricked phones. Here are the steps:
1. Make sure your device is on EMUI 8 beta with unlocked bootloader (guide: https://forum.xda-developers.com/honor-6x/development/hwota7-hwota8-honor-6x-t3792601)
2. Download GSI from this thread https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688 and move it to the folder where you installed ADB
Note: Honor 6x doesn't support seamless update so you want the A-only image, not the A/B one. Just in case you don't know already, Honor 6x has arm64 architecture.
3. Open cmd and navigate to your ADB folder
4. Reboot your phone to fastboot mode and type 'fastboot flash system name-of-the-image.img' where name-of-the-image.img is your downloaded GSI.
5. Hit enter and wait for it to finish installing
6. Famous words: "Reboot and pray"
Problems:
1. Since we don't have a treble-compatable TWRP build yet, there is no way to install gapps for now. I will try to find an image that includes them.
2. All the problems present on the actual ROM (check ROM thread)
3. There are likely others. (There always are some)
I'd like it if others tried to flash this and share their experiences here.
Thanks to @phhusson, @vovan1982, @HassanMirza01, Huawei, RR team and everybody else I forgot to mention.
Click to expand...
Click to collapse
Bro do complete research first. we have fully working twrp. use twrp on elemental Rom. and installation procedure is also completely wrong. first flash twrp from fastboot using command fastboot flash recovery_ramdisk RECOVERY V2.img then check the recovery and reboot to boot loader then flash system image then reboot to recovery do formats data then install gapps then again reboot to boot loader then flash stockrecovery from dot os thread which is also treble rom then reboot to stock recovery do factory reset now device will boot fine.
Also there are some bugs like mtp,battery drain,heating issues on normal usage and slow charging in some rims. I have tried 4 roms and decided go back to elemental Rom. but these treble roms much better than nougat custom roms comparing to them these can be used as daily driver. pure Android 8.1 roms with all latest features.
Can you provide screenshots please
That's great news. TFS bro.
Edwin Davis said:
Can you provide screenshots please
Click to expand...
Click to collapse
mtp working on some roms and battery drain is not that much compared to emui 8 stock now im gonna try more roms.
Treble roms are much faster and more stable you can't find any bugs. even I was surprised honor 6x can run stock android with this much stability.
Battery drain comparison
on stock emui 5 5% drain for hour while watching movie in mx player no apps running in background all freezed.
on emui 8/treble roms 7-8% while watching movie on mx player but didn't freezed any apps only apps running telegram and whatsapp.
conclusion if u r in emui8 go for treble roms for complete pixel experience
4G VoLTE
it got volte?
What about the volte and gcam ?
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.
Code:
[I]#include <std_disclaimer.h>
/*
* Your warranty is not 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 recovery
* 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.
*
*/[/I]
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
Note: Please be aware that you cannot install this without a kernel with LZMA compression support, I believe most ROMs have included my commit for this so you should be good for all custom ROMs and kernels (Not Android 10), if not please file a request to the maintainer.
To follow up, please be aware that TWRP is currently not compatible with Android 10. If you would like to use TWRP you will need to go back to Android 9. If you would like more information you can read at the link here.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. Use ADB or MTP to transfer the zip onto your device.
Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Changelog:
[BETA]
3.3.1-0: Initial release for Pixel 3A devices
3.3.1-1: Fixed having to manually change slots before rebooting.
3.3.1-2: Updated to July blobs!
3.3.1-3: Can now install TWRP to boot image. ADB, MTP, LOGD, Repack Tools and Logcat have all been removed to save the necessary space for this to work. You can grab stuff while in the OS, then flash it in TWRP (Keep in mind I have only tested this on stock as of now, feel free to test it on whatever ROM you use. It should work, but let me know if it doesn't).
3.3.1-4: Changed back to LZMA compression, also added back all the features besides ADB/Logcat. As long as your kernel supports LZMA you will be able to take advantage of installing it permanently without having to worry about space restrictions.
3.3.1-5:
Add persist entry to fstab
* To allow TWRP to store a backup settings file on /persist
and also to be used as QCOM time fix source during early boot.
Revert "Don't include logcat."
Revert "Don't include repack tools."
3.3.1-6:
Revert "Revert "Don't include repack tools.""
Add haptics firmware.
* This obviously on it's own isn't enough to get haptics working for the 3A in TWRP, but its a start.
Don't include a precompiled update_engine_sideload
* This should fix the issue of flashing officials for StatiXOS
[STABLE]
3.3.1-0: Initial official release!
Download:
https://twrp.me/google/googlepixel3a.html
XDA:DevDB Information
TWRP, Tool/Utility for the Google Pixel 3a
Contributors
ZVNexus, janjan
Source Code: https://github.com/TeamWin/android_device_google_bonito
Version Information
Status: Beta
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-07-17
Current Beta Version: 3.3.1-6
Beta Release Date: 2019-06-27
Created 2019-06-27
Last Updated 2019-11-15
Reserved
Incredible job thank you!
Thank you for all your guys hard work. I can't imagine the work involved
Congratulations and thank you for your time and effort.
This is awesome brother,,,if it werent for you we would not have a custom recovery! Thank you!
Thanks mate
Thank you!!!!!!!!
Shoud we allow Modifications or Keep Read Only when we boot for the first time?
WOOHOO!!! Thank you for this, it's so exciting!!!
Quick question: the instructions say there is also a zip to download but I didn't see it in anywhere. Do we really need it? TWRP did boot up temporarily just fine!
zombioptic said:
WOOHOO!!! Thank you for this, it's so exciting!!!
Quick question: the instructions say there is also a zip to download but I didn't see it in anywhere. Do we really need it? TWRP did boot up temporarily just fine!
Click to expand...
Click to collapse
Read the note
Fentadroid said:
Read the note
Click to expand...
Click to collapse
Ah yes... My bad!
Thank you for TWRP mate
Sent from my Pixel 3a using Tapatalk
Great job, now all we need is some proper rooting/with magisk, and everything will be golden!
jayyskittles said:
Great job, now all we need is some proper rooting/with magisk, and everything will be golden!
Click to expand...
Click to collapse
Magisk pushed a cannery build that roots for the Pixel 3s on Q4 last night.
Also, the Magisk dev has a Pixel 3 on Q4 (not 3a) that is his daily driver. So because of the similar file systems, it's good news for us on P3a.
Edit:
https://twitter.com/topjohnwu/status/1144159892430659584?s=09
12paq said:
Magisk pushed a cannery build that roots for the Pixel 3s on Q4 last night.
Also, the Magisk dev has a Pixel 3 on Q4 (not 3a) that is his daily driver. So because of the similar file systems, it's good news for us on P3a.
Edit:
https://twitter.com/topjohnwu/status/1144159892430659584?s=09
Click to expand...
Click to collapse
Does that canary build work for us?
jayyskittles said:
Does that canary build work for us?
Click to expand...
Click to collapse
Only if we get a Q compatible twrp. Or if someone can provide the Q beta 4 boot.img
jayyskittles said:
Does that canary build work for us?
Click to expand...
Click to collapse
For root It should even without TWRP. Pull the boot.img from the beta, modify it with Magisk Manager then Fastboot flash the modified boot image.
I have not tried it yet. I am still trying to spell canary correctly. :laugh:
Not sure how many of you have tested this thing out, but I can confirm it works on the stock rom. I had to root for a Titanium Backup, so I flashed Magisk through TWRP and rebooted just fine.
Finnaly!! Good work to OP who worked hard to get us this TWRP!
12paq said:
For root It should even without TWRP. Pull the boot.img from the beta, modify it with Magisk Manager then Fastboot flash the modified boot image.
I have not tried it yet. I am still trying to spell canary correctly. :laugh:
Click to expand...
Click to collapse
I wanted to try it tomorrow, but it seems ill better wait for a new update on the canary build:
https://github.com/topjohnwu/magisk_files/blob/master/canary_builds/notes.md
-> see the notes for the latest build. Afaik we need logical partition support or root will not work (correctly)
I'm also thinking if i can just pull boot.img via twrp backup (then extract if needed) or should i pull it via fastboot.
Really the userdata wipe holds me back (when OEM unlocking the device.)
Guess i will wait when root is successfully reported on P3 by topjohnwu, just to be sure.
Deleted
Does this need a12 firmware? If so you should post dtbo and vendor_boot images.
gillim74 said:
Does this need a12 firmware? If so you should post dtbo and vendor_boot images.
Click to expand...
Click to collapse
wait for official Update
The boot image isnt working at all, after restarting into recovery mode i end up in bootloader. im on the latest oos 11 (11.2.10.10 BA)
edit:
sadly there are no install instructions on how to flash, found out that oos 12 is needed and the flash files are in the download repo (Image files folder)
A - Reboot to bootloader
fastboot flash dtbo "dtbo.img"
fastboot flash vendor_boot "vendor_boot.img"
fastboot flash boot "boot_img"
B - Fastboot reboot recovery
Perform factory data reset
Apply update from sideload
adb sideload "file name.zip"
C -Reboot system
OnePlus 9 Pro (lemonadep) of Project Elixir has been dropped due to bad behavior of the maintainer.
So no more official support and we recommend not to flash builds which isn't available in OFFICIAL website.
Flashed yesterday without any issues. To get the boot, vendor_boot, and dtbo i used payload extraction. Changelog states CTS to pass by default, however it fails until Zygisk is enabled. Custom FOD icons are not working. Audio & mic (oos12) bug is present. Flashed BluSpark kernel about an 1hr. ago. Without issue.
Overall seems to be very stable with many options! Great Job! LE2125.
Flashed this but was having issues with haptic/vibrate feedback, they're not working.
Fyi BluSpark kernel fixes this
Advali said:
Flashed this but was having issues with haptic/vibrate feedback, they're not working.
Click to expand...
Click to collapse
cave.man1908 said:
Fyi BluSpark kernel fixes this
Click to expand...
Click to collapse
Bluspark doesn't work on LE2120. Already tried this 3x and it f'd up my phone and had to reinstall again.
Absolutely gorgeous ROM! Do I understand that I can flash this coming from OOS12 without the need to downgrade to android 11?
If so, can somebody please explain what changed since the first A12 ROMs were released as they warned against flashing from OOS12 directly.
Reremoll said:
Absolutely gorgeous ROM! Do I understand that I can flash this coming from OOS12 without the need to downgrade to android 11?
If so, can somebody please explain what changed since the first A12 ROMs were released as they warned against flashing from OOS12 directly.
Click to expand...
Click to collapse
Yes you flash this over OS12. make sure u have OS12 on both slots(if ur on c48 just download and local update once again to have on both sides). Then u have to download this rom, extract it on ur pc, so u can flash(in fastboot) dtbo, vendor_boot and boot. Then boot to recovery, wipe and adb sideload rom.
blu-spark kernel doesn't work on this rom, tried it. But it seem unfortunately it doesn't work on this rom.
break.cold said:
blu-spark kernel doesn't work on this rom, tried it. But it seem unfortunately it doesn't work on this rom.
Click to expand...
Click to collapse
I flashed BluSpark to elixir yesterday without issue. Weird. Im le2125
I've tried 4 roms yday and blu spark sometimes make you bootloop or doesn't want to flash which is weird.
After a few rom re-installs it worked on every rom I tried.
cave.man1908 said:
I flashed BluSpark to elixir yesterday without issue. Weird. Im le2125
Click to expand...
Click to collapse
I tried blu-spark of StagOS, Pixel Extended, Project ELixir, it keep sending me back to fastboot menu, however, its works on riceDroid without issue.
OnePlus 9 Pro (lemonadep) of Project Elixir has been dropped due to bad behavior of the maintainer.
So no more official support and we recommend not to flash builds which isn't available in OFFICIAL website.
sourav24071999 said:
OnePlus 9 Pro (lemonadep) of Project Elixir has been dropped due to bad behavior of the maintainer.
So no more official support and we recommend not to flash builds which isn't available in OFFICIAL website.
Click to expand...
Click to collapse
Well, I wouldn't have had "bad behavior" if you weren't trying to control what I did with my own Telegram group.
MOD ACTION:
Thread closed since OP has been edited removing content.