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.
Related
Pixel 2 (XL) is now officially added on the Magisk support list, please install Magisk v14.5+. These builds here are deprecated
Check out the latest beta from the official beta thread
---------------------------------------------------------------------------------------------------
Root for Pixel 2 XL has been achieved!
There are still some things I'd like to add before I push out an official release, but since people can't wait to ROOT their shiny new Pixel 2s, I figured I'd build one for you!
I do not own either Pixel 2 or Pixel 2 XL, so testing is limited. This build is ONLY tested on Pixel 2 XL Android 8.0 OPD1.170816.010.
For Android 8.1 beta, Pixel 2 etc, it should work IN THEORY.
Magisk Version: v14.4 (code: 1444)
Magisk Manager Version: 5.4.1 (code: 58)
Instructions
Since TWRP cannot decrypt /data yet, the proper way to install Magisk is via Magisk Manager. You will need a stock boot image from official factory images.
Download MagiskManager-v5.4.1.apk from attachments and install it to your device.
This Magisk Manager is specifically built for this release ONLY, both stable and beta channels points to the same custom URL.
Once you've got Magisk Manager installed, I'll just copy and paste the instructions from the Magisk OP here:
This method does not need root, and also does not require a custom recovery.
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img
Flash the patched boot image to your device and reboot. Voilà!
Click to expand...
Click to collapse
Please don't share a patched boot image in the forums since it will help no one. Flashing a patched boot image alone is not sufficient to run Magisk properly. The "patch through Magisk Manager" step is actually mandatory if you wonder why.
Special Thanks
@nathanchance for his Pixel 2 XL and speedy tests
@Dees_Troy for TWRP on Pixel 2 XL - thanks to TWRP's root shell, the debugging process is 1000 times faster
Donations
I spent endless hours on Magisk. If you like my work, feel free to donate.
https://www.paypal.me/topjohnwu
P.S. Magisk-v14.4(1444).zip is also hosted here because I do not have my own server
Reserved
Donating later
Glad to help be a part of testing and here's to the future of root
Thank you @topjohnwu!!!
Thanks again! Also for people using BusyBox it goes in /system/bin
topjohnwu said:
Root for Pixel 2 XL has been achieved!
There are still some things I'd like to add before I push out an official release, but since people can't wait to ROOT their shiny new Pixel 2s, I figured I'd build one for you!
I do not own either Pixel 2 or Pixel 2 XL, so testing is limited. This build is ONLY tested on Pixel 2 XL Android 8.0 OPD1.170816.010.
For Android 8.1 beta, Pixel 2 etc, it should work IN THEORY.
Magisk Version: v14.4 (code: 1444)
Magisk Manager Version: 5.4.1 (code: 58)
Instructions
Since TWRP cannot decrypt /data yet, the proper way to install Magisk is via Magisk Manager. You will need a stock boot image from official factory images.
Download MagiskManager-v5.4.1.apk from attachments and install it to your device.
This Magisk Manager is specifically built for this release ONLY, both stable and beta channels points to the same custom URL.
Once you've got Magisk Manager installed, I'll just copy and paste the instructions from the Magisk OP here:
Please don't share a patched boot image in the forums since it will help no one. Flashing a patched boot image alone is not sufficient to run Magisk properly. The "patch through Magisk Manager" step is actually mandatory if you wonder why.
Special Thanks
@nathanchance for his Pixel 2 XL and speedy tests
@Dees_Troy for TWRP on Pixel 2 XL - thanks to TWRP's root shell, the debugging process is 1000 times faster
Donations
I spent endless hours on Magisk. If you like my work, feel free to donate.
https://www.paypal.me/topjohnwu
P.S. Magisk-v14.4(1444).zip is also hosted here because I do not have my own server
Click to expand...
Click to collapse
Can we use a custom kernel like the Snoke kernel from Despair after we root or will it break root?
Also I've seen a few posts about needing to do this before any Google accounts are on the phone, etc. Any truth to any of those; or just flash original boot back on and follow your instructions?
Thanks for all your work!
Install snokes kernel first then root with magisk
Hopefully will have a 2 XL coming and will be happy to test this on 8.1.
I would flash snokes first, then root with magisk , also I have Google account in my device and am not encrypted in twrp
Sweetness! Thanks all for getting this going.
Sent from my Pixel 2 XL using Tapatalk
Megaflop666 said:
Can we use a custom kernel like the Snoke kernel from Despair after we root or will it break root?
Also I've seen a few posts about needing to do this before any Google accounts are on the phone, etc. Any truth to any of those; or just flash original boot back on and follow your instructions?
Thanks for all your work!
Click to expand...
Click to collapse
I tested it with Google accounts already on my phone.
I don't know if Snoke uses AnyKernel2 or a boot image. If it uses a boot image, just patch that with Magisk Manager and flash it (that's what I did with my kernel). If it uses AnyKernel, flash the Magisk patched boot image then Snoke.
Also, to be clear to everyone, this works with encrypted data and SELinux enforcing.
nathanchance said:
I tested it with Google accounts already on my phone.
I don't know if Snoke uses AnyKernel2 or a boot image. If it uses a boot image, just patch that with Magisk Manager and flash it (that's what I did with my kernel). If it uses AnyKernel, flash the Magisk patched boot image then Snoke.
Also, to be clear to everyone, this works with encrypted data and SELinux enforcing.
Click to expand...
Click to collapse
The newer ones are anykernel2
ne0ns4l4m4nder said:
I would flash snokes first, then root with magisk , also I have Google account in my device and am not encrypted in twrp
Click to expand...
Click to collapse
I already have Snoke kernel on the device. I was going to wipe userdata to unencrypt my phone as well. I'm just going to be happy to get root so I can tibu over my apps and data easily and quit using my opt for my dd.
Thanks
bryantjopplin said:
The newer ones are anykernel2
Click to expand...
Click to collapse
Don't necessarily think it's the wisest to rely on TWRP right now but not my call in which case, Magisk can be flashed whenever since Snoke isn't going to mess with any internal patching that Magisk does (or shouldn't...)
nathanchance said:
Don't necessarily think it's the wisest to rely on TWRP right now but not my call [emoji14] in which case, Magisk can be flashed whenever since Snoke isn't going to mess with any internal patching that Magisk does (or shouldn't...)
Click to expand...
Click to collapse
So this magisk also patches the util_functions.sh ?
bryantjopplin said:
So this magisk also patches the util_functions.sh ?
Click to expand...
Click to collapse
You mean this? https://github.com/topjohnwu/Magisk/blob/master/scripts/util_functions.sh
It's just a helper script while flashing, it isn't used once things are installed.
how do you do the final step: " Flash the patched boot image to your device and reboot. Voilà!"?
phyl0x said:
how do you do the final step: " Flash the patched boot image to your device and reboot. Voilà!"?
Click to expand...
Click to collapse
Fastboot
Sent from my Pixel 2 using Tapatalk
For Pixel Noobs out there including myself... Could someone post a step-by-step description of how to install Magisk, Smoke Kernel, and TWRP maybe on a separate thread?
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>
/*
* 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.
*
*/
Features:
All function in a normal TWRP
Multi-language support
Support USB OTG!
Support decrypt /data!
Tips:
For unknown reason, after formatting userdata in TWRP, you won't be able to boot stock MIUI as encryption will fail. The fix is flashing factory images via MiFlash or just flash factory userdata.img via fastboot.
Decrypt Oreo userdata is NOT supported, I'll release an Oreo compatible build after it's a thing.The latest version already supports decrypting Oreo data
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot flash recovery twrp.img" in command line
5. Reboot and enjoy it
Download:
https://twrp.me/xiaomi/xiaomiminote3.html
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/TeamWin/android_device_xiaomi_jason
Thank you for your work.Do you think you will continue this project?
We will be pleased if you continue...Best regards...
Great is this TWRP with OTG, thankyou very much!
Not working otg for me!!
Enviado desde mi Mi Note 3 mediante Tapatalk
Somebody has Test with xiaomi.eu rom 8.1.11? Touch in recovery works?
Does OTG still work with one of the newer dev ROMs installed?? After installing Xiaomi.eu ROM 8.1.11, OTG stopped working for me with a different TWRP version, TWRP_3.2.1-3_jason-v2, that I downloaded from another site.
@dianlujitao could you please update this recovery to the latest source? Thank you very much!
quyleanh said:
@dianlujitao could you please update this recovery to the latest source? Thank you very much!
Click to expand...
Click to collapse
yea would be very nice!
Vihru said:
yea would be very nice!
Click to expand...
Click to collapse
Here are links to newer builds I've come across.
http://www92.zippyshare.com/v/9LsITy1z/file.html
https://yadi.sk/d/Z9ollcvX3RbiZg
https://mega.nz/#F!CUhgUIia!_QSBBwWFvtgtP3DuIl4SmQ
Pumpino said:
Here are links to newer builds I've come across.
http://www92.zippyshare.com/v/9LsITy1z/file.html
https://yadi.sk/d/Z9ollcvX3RbiZg
https://mega.nz/#F!CUhgUIia!_QSBBwWFvtgtP3DuIl4SmQ
Click to expand...
Click to collapse
https://xiaomi.eu/community/index.php?threads/43306/
Here's another one, Im using this and it works so far I used it.
Skickat från min Mi Note 3 via Tapatalk
exionen said:
https://xiaomi.eu/community/index.php?threads/43306/
Here's another one, Im using this and it works so far I used it.
Click to expand...
Click to collapse
That's the second (direct) link I posted.
Its better you post the authors threads so users can read what to expect and the authors gets credited for their work
Skickat från min Mi Note 3 via Tapatalk
Wish someone could bring the Red Wolf Recovery Project to our Mi Note 3 devices...
Do the same thing as red wolf.
Twrp_3.2.1-0
yadi.sk/d/Z9ollcvX3RbiZg
hello,
I am not allowed to start a new topic (at least not yet) so I will ask here, maybe someone can help me.
I have unlocked my MiNote3 (official way). I have installed all needed drivers on the PC (win 7) and tried to install latest TWRP on the phone.
I managed to install it but is not booting in TWRP when I press power and Vol+ or any other buttons combination.
Any idea why is not working?
I also tried to install another ROM (global developer instead of stable) but the phone is not entering in EDL mode. It's just restarting.
Any idea why?
Thanks
I am using this TWRP and the unlock pattern always appears before starting the android. Do you know how to turn it off?
nicolae.fratila said:
hello,
I am not allowed to start a new topic (at least not yet) so I will ask here, maybe someone can help me.
I have unlocked my MiNote3 (official way). I have installed all needed drivers on the PC (win 7) and tried to install latest TWRP on the phone.
I managed to install it but is not booting in TWRP when I press power and Vol+ or any other buttons combination.
Any idea why is not working?
I also tried to install another ROM (global developer instead of stable) but the phone is not entering in EDL mode. It's just restarting.
Any idea why?
Thanks
Click to expand...
Click to collapse
When you flash TWRP using adb and if everything went well type after this command :
fastboot boot twrp.img
You need to immediately after flashing twrp ,boot into it and set it up so on the next restart it wont get overwritten by stock recovery.
So the full process should be like this :
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot boot twrp.img
Yep i use that one too. Works like a charm!
dimi89 said:
When you flash TWRP using adb and if everything went well type after this command :
fastboot boot twrp.img
You need to immediately after flashing twrp ,boot into it and set it up so on the next restart it wont get overwritten by stock recovery.
So the full process should be like this :
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot boot twrp.img
Click to expand...
Click to collapse
Thank you for advice. It's working now but the TWRP doesn't stay installed.
After first reboot in Miui Stable is deleting it.
I tried everything but is just removed.
Shall I install custom rom (from Xiaomi.eu) when I enter first time in TWRP?
Will there be any issue when booting after the new ROM will be installed?
I just want to avoid bricking the devices.
Has anyone had trouble with the screen not registering touches in TWRP? I tried two different versions of TWRP and when my phone boots into it, the screen won't respond to any presses. It only worked the first time when I flashed xiaomi.eu.
Edit: I've realised that TWRP is unresponsive only if my phone doesn't vibrate when it restarts prior to entering TWRP. When it's unresponsive, I force a restart into TWRP by pressing the power button and volume up button simultaneously. The phone is never unresponsive when booting normally, so it's not clearly a hardware issue. However, it occurs in two different builds of TWRP that I've tried. Any suggestions?
Edit 2: I see I'm not the only one. https://xiaomi.eu/community/threads/twrp-3-1-1-0-no-working-touch-with-new-roms.42800/
Samsung Galaxy S8+ (Snapdragon)
PLEASE READ READ READENTIRE OP
"ALL MAJOR WORK DONE BY HASHCODE SO GO GIVE HIM SOM THANKS.DO NOT POST ANY BUG OR ISSUE COUSED BY THIS RECOVERY IN ORIGINAL THREAD BY HASHCODE, POST HERE AND I WILL HELP YOU."
CURRENT PROJECT STATUS:
BETA v4.09-B01 [Nougat:7.0]
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 3.2.1 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
APK install:
Once installed, open up the Safestrap application, Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
APK:
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Open your old Safestrap app and use the "Uninstall Recovery" button
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK, Grant SU access, Use the "Install Recovery" button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
KNOWN ISSUES:
- Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again.
DOWNLOADS:
CONFIRM THAT YOU ARE USING A SAMSUNG GALAXY S8+ (Snapdragon) [Nougat:7.0]
LATEST ZIP: Safestrap-4.09-B01-DREAM2QLTE-SS-FF-flashable.zip
LATEST APK: Safestrap-4.09-B01-DREAM2QLTE.apk
androidfilehost
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Special Thanks To
@Hashcode, DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery.
@jrkruse for pointing me that S8 has permissive root. @partcyborg for getting root on S8.
CHANGELOG:
4.09-B01 [2019-04-19]
- TWRP updated to 3.3.0.
- Fix reboot function
- Add reboot to safestrap button in reboot menu
- Add Edl button in reboot menu
- Move Boot Options to advanced menu items.
- Safestrap app: Update topjohnwu's libsu to 2.4.0.
- Safestrap app: Update install recovery function.
4.08-B01 [2019-03-01]
- TWRP updated to 3.2.3.
- Fix datamedia mount.
- Add hijack-backup during image flashing.
- Major code clean up
4.07-B01 [2018-07-16]
- Fix CHARGER_BOOT detection.
- TWRP updated to 3.2.2.
- Update safestrap portrait theme.
- Update safestrap app to use topjohnwu's libsu & internal busybox (busybox app not needed anymore).
4.06-B02 [2018-04-10]
- Fix taskset cpus to 8 cores (thanks to Hashcode).
- Add exfat support for recovery (ext-sdcard fix).
- Fix MTP (thanks to me2151).
4.06-B01 [2018-04-03]
- Initial release.
BUGS:
- ROM-slots not working for now.
Mine
Yessssss finally a solution. But I can't do it lol I'm running Oreo
Sent from my SM-G955U using Tapatalk
Could you boot an AOSP rom off of it?
Slypnslyde said:
Yessssss finally a solution. But I can't do it lol I'm running Oreo
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
So downgrade - flash PartCyborg's rom, I think it's doable while on Oreo. Don't quote me on this though. I'll just be very sad if it's not possible.
psych0r3bel said:
So downgrade - flash PartCyborg's rom, I think it's doable while on Oreo. Don't quote me on this though. I'll just be very sad if it's not possible.
Click to expand...
Click to collapse
Totally possible
ParisInLove said:
Totally possible
Click to expand...
Click to collapse
Cool I hope it do it right
Sent from my SM-G955U using Tapatalk
ParisInLove said:
Totally possible
Click to expand...
Click to collapse
Just to clarify, when I downgrade from 8.0 to 7.0 to obtain root, boot the rooted ROM then
install busybox and safestrap.apk before reflashing Oreo and that will run alongside Rooted QL1 in a second ROM slot under safestrap?? I apologise if I misread instructions, it's been a while as I haven't used safestrap since my s3 years ago
Edit: just saw the ROM slots not working, and the new Oreo modified thread. Lol
gerryl432 said:
Just to clarify, when I downgrade from 8.0 to 7.0 to obtain root, boot the rooted ROM then
install busybox and safestrap.apk before reflashing Oreo and that will run alongside Rooted QL1 in a second ROM slot under safestrap?? I apologise if I misread instructions, it's been a while as I haven't used safestrap since my s3 years ago
Edit: just saw the ROM slots not working, and the new Oreo modified thread. Lol
Click to expand...
Click to collapse
Were is this oreo thread you mention? iv been searching for it, but i cant find it.
siulmagic said:
Were is this oreo thread you mention? iv been searching for it, but i cant find it.
Click to expand...
Click to collapse
https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206
gerryl432 said:
https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206
Click to expand...
Click to collapse
thank you.
@afaneh92 Do you have sources for this recovery? As in how did you get it to work with android 7 when safestrap support ended in KK. I'd like to boot it on LP+.
kirito9 said:
@afaneh92 Do you have sources for this recovery? As in how did you get it to work with android 7 when safestrap support ended in KK. I'd like to boot it on LP+.
Click to expand...
Click to collapse
Here its
https://github.com/mohammad92/android_bootable_recovery-safestrap
We have permissive root on S8, S8+ and Note 8 thats why its working on 7.0+
Would this allow us to flash magisk? Or a custom kernel?
afaneh92 said:
Here its
https://github.com/mohammad92/android_bootable_recovery-safestrap
We have permissive root on S8, S8+ and Note 8 thats why its working on 7.0+
Click to expand...
Click to collapse
Thank you. So as long as you can get root and make the selinux permissive it should work?
TacoTuco said:
Would this allow us to flash magisk? Or a custom kernel?
Click to expand...
Click to collapse
No.
kirito9 said:
Thank you. So as long as you can get root and make the selinux permissive it should work?
Click to expand...
Click to collapse
I think yes.
afaneh92 said:
No.
I think yes.
Click to expand...
Click to collapse
Could a Dev make a DT and possibly build a rom with this new freedom to flash things? Cause as far as I know all you need is a DT and a way to compile and you should be fine right? Or will the whole no custom kernel thing prevent that.
Would I be able to install this on Nougat, and then update to Oreo and keep it installed?
Then from there add a Nougat ROM with root so that I could update it and use my root stuff.
This is awesome! Recovery is working great so far! Pls let me know of any roms working with this method I can't wait to try it out!
Any mod please close this thread
XDA:DevDB Information
Orange Fox Recovery For Nitrogen, Tool/Utility for the Xiaomi Mi Max 3
Contributors
ROMFACTORY
Source Code: https://gitlab.com/OrangeFox
Version Information
Status: Stable
Stable Release Date: 2018-09-04
Created 2018-09-04
Last Updated 2019-01-17
reserved
Appreciate the new recoveries. Looking forward to your custom rom, bro! Thanks for your hard work :highfive:.
Edit:
Flashed OrangeFox-R8.0-nitrogen.zip and it just goes to fastboot. Booted phone as well and then reboot from there and power + volume up takes me to fastboot. I tested three new downloads of the orange recovery and all took me to fastboot instead of recovery. Flashed back to TWRP 3.2.3.0 using twrp app without a problem and booted into that recovery. Then, I flashed Pitch Black recovery without any problems. Let me know what you think. Thanks!
opasha said:
Appreciate the new recoveries. Looking forward to your custom rom, bro! Thanks for your hard work :highfive:.
Edit:
Flashed OrangeFox-R8.0-nitrogen.zip and it just goes to fastboot. Booted phone as well and then reboot from there and power + volume up takes me to fastboot. I tested three new downloads of the orange recovery and all took me to fastboot instead of recovery. Flashed back to TWRP 3.2.3.0 using twrp app without a problem and booted into that recovery. Then, I flashed Pitch Black recovery without any problems. Let me know what you think. Thanks!
Click to expand...
Click to collapse
will fix the issue
ROMFACTORY said:
will fix the issue
Click to expand...
Click to collapse
Thanks, brother :highfive:.
opasha said:
Thanks, brother :highfive:.
Click to expand...
Click to collapse
recovery is updated
link is updated
have a look now
ROMFACTORY said:
recovery is updated
link is updated
have a look now
Click to expand...
Click to collapse
Ok, downloading now. Will report back, thanks.
Edit: .img didn't flash - "flash failed." I used twrp app - same way I flashed pitch black recovery image when previous orange fox zip would remain stuck on fastboot screen.
opasha said:
Ok, downloading now. Will report back, thanks.
Edit: .img didn't flash - "flash failed." I used twrp app - same way I flashed pitch black recovery image when previous orange fox zip would remain stuck on fastboot screen.
Click to expand...
Click to collapse
have you downloaded the latest zip from the Android file host ?
ROMFACTORY said:
have you downloaded the latest zip from the Android file host ?
Click to expand...
Click to collapse
No, downloaded and used the latest .img above the zip in androidfilehost. I'll test the zip now.
Edit:
Just flashed the zip using pitch black recovery. Both the image and the zip file have the same problem. They both, like your first version, reboot to fastboot instead of recovery. I just flashed back to pitch black without issue using twrp app. Maybe check the script in case fastboot reboot line is in there by mistake?
opasha said:
No, downloaded and used the latest .img above the zip in androidfilehost. I'll test the zip now.
Edit:
Just flashed the zip using pitch black recovery. Both the image and the zip file have the same problem. They both, like your first version, reboot to fastboot instead of recovery. I just flashed back to pitch black without issue using twrp app. Maybe check the script in case fastboot reboot line is in there by mistake?
Click to expand...
Click to collapse
idk not a issue on my side using the same device tree on both the recoveries. i have contacted the dev team we are working on a fix
Check out OrangeFox R8.1A.
DarthJabba9 said:
Check out OrangeFox R8.1.
Click to expand...
Click to collapse
What are the improvements/changes? Last few didn't boot for mi max 3.
Edit: I flashed it, and it didn't work just like all the previous versions. Leads straight to fastboot screen.
Edit2: @DarthJabba9 fixed the build. Latest version, which he will post shortly works great. This is definitely a nicer/cleaner recovery. I highly recommend it! Thanks, buddy!
OrangeFox R8.1
* Updated support for new fstab encryption statements
* Updated support for disabling DM-Verity
* Added separate settings page for languages
* Added quick settings in operation pages (flashing zips, backing up, restoring)
* Added "notch mode" for supported devices.
* Use dark transparent background for quick settings
* Added "restore defaults" for OrangeFox settings
* Updated languages
* Added /cust in fstab
* Minor UI changes
* Minor bug fixes
* Fixed problems with random reboots
* Fixed problems with changing data FS to f2fs
* Led indicator now works on most devices
------------------:
Our group - https://t.me/joinchat/HNZTNky4zkpWc7na_-Beow
Our channel - https://t.me/OrangeFoxRecovery
Download - https://sourceforge.net/projects/orangefox/files/test_builds/OrangeFox-R8.1A-nitrogen.zip/download
------------------:
Installed Orange Fox recovery,
But backup is only 2GB, I now it has more data to backup. It is also asking for Encryption password on start. How could I find this Password?
Regards
Tunc
eresen said:
How could I find this Password?
Click to expand...
Click to collapse
Maybe you want to explain, step by step, from the beginning to the end, how you got to this point?
It's a hardware generated key(FDE), not a password per say so you can't get it. The recovery needs more work to be able to support it and decrypt device automatically at boot just like the rom does...
Something like this: https://github.com/TeamWin/android_...mmit/05137578dc6d382c159c3abc8c2f181f7490d6e5
nijel8 said:
It's a hardware generated key(FDE), not a password per say so you can't get it. The recovery needs more work to be able to support it and decrypt device automatically at boot just like the rom does...
Click to expand...
Click to collapse
It does it already. And I doubt that regressing to Marshmallow code will improve anything.
DarthJabba9 said:
OrangeFox R8.1
Click to expand...
Click to collapse
Having trouble with the official twrp, can I flash the recovery.img from the zip in fastboot?
Then I will try to use it to flash twrp... can I do adb sideload with this recovery?
totalz said:
Having trouble with the official twrp, can I flash the recovery.img from the zip in fastboot?
Then I will try to use it to flash twrp... can I do adb sideload with this recovery?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=76885728&postcount=3
DarthJabba9 said:
https://forum.xda-developers.com/showpost.php?p=76885728&postcount=3
Click to expand...
Click to collapse
Like the orange theme
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?