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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 3.2.1-0:
- minui fixes (cryptomilk)
- Better android-8.0 compatibility in ROM trees (Dees_Troy)
- Fix missing library in android-8.0 (nkk71)
- Fix inconsistent SDCard naming (DevUt)
- Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD LINKS:
Current and past versions of TWRP can be found at one of the mirrors below:
- Primary (Recommended)
- Primary (Backup)
INSTALL INSTRUCTIONS:
TWRP install (requires TWRP 2.8.4 or higher already installed):
1) Download the latest version of TWRP appropriate for your device/firmware
2) Reboot to TWRP
3) Hit Install and tap the "Install Image" button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find other alternative installation methods on our website (direct link to your device)!
BUGS:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log to SD, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.
If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to 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][OFFICIAL] TWRP for Xiaomi Mi Note 2, Tool/Utility for the Xiaomi Mi Note 2
Contributors
joe2k01
Version Information
Status: Stable
Created 2018-04-06
Last Updated 2018-04-06
I really want twrp 3.2.1-1. Miui firmware not Packed in new.dat are not installed on Android 8.
Thank you very much! Very nice to see the official one!
Sorry about the noob question but I'm not sure. Is possible updating with this version without getting the official recovery? Any explanation helps, thank you!
Hi
I hope someone can help me. I unlocked my Note 2 running MIUIPro 9 (Android 7) and then installed TWRP 3.2.1.0 Scorpio and rebooted into TWRP via fastboot and now my Note 2 will not boit, it just sits on the MIUIPro unlocked screen.
I have tried to transfer the Global MIUI 9 Firmware file to the internal storage while connected via TWRP but the PC keeps telling me the phone is not connected although I can access the root of the phone on the PC and have the drivers installed.
TIA
Sent from my Nokia 7 plus using Tapatalk
Stransky said:
Hi
I hope someone can help me. I unlocked my Note 2 running MIUIPro 9 (Android 7) and then installed TWRP 3.2.1.0 Scorpio and rebooted into TWRP via fastboot and now my Note 2 will not boit, it just sits on the MIUIPro unlocked screen.
I have tried to transfer the Global MIUI 9 Firmware file to the internal storage while connected via TWRP but the PC keeps telling me the phone is not connected although I can access the root of the phone on the PC and have the drivers installed.
TIA
Click to expand...
Click to collapse
I had the same problem a few days ago trying to recover root after updating to MIUI 9.5.4 and sadly have no idea whats going on.
I fixed it downloading the MIUI firmware to my PC (fastboot option) and used Mi Flash Tool to flash it above the existing one (no wipe) and it booted again normally.
I recently updated to 9.5.5 but I haven't tested yet if now it works. So far I have no clue what I'm doing wrong.
Sorry if my english it's not perfect, hope it helps.
Good morning friends!
I installed Rom Beta MIUI 10 Global 8.7.5 in TWRP 3.2.2
However, the system does not boot even though I'm formatting with TWRP.
Would there be some other method for ROM to reboot?
Can anyone help me with this question?
I install MIUI 10, do the procedure by installing TWRP, restart Smatphone via TWRP, install SuperSU, format the System. But when I restart my Smartphone, it does not leave the startup screen
Thanks a lot man. I've got a minor issue. Mouse cursor in the center for all time.
hi is there any way install twrp in mi note 2 with support of ota update
kmanilpillai said:
hi is there any way install twrp in mi note 2 with support of ota update
Click to expand...
Click to collapse
Always need to flash the full rom instead of ota after installing twrp. Why?
kmanilpillai said:
Always need to flash the full rom instead of ota after installing twrp. Why?
Click to expand...
Click to collapse
If you are referring to MIUI OTAs, those are differently sorted inside(folder wise) the archive... So TWRP will not find the files he needs to read...
Full ROMs are normally arranged inside (folder wise) and that's why you can flash them...
New version available 3.3.0-0 as of 20190412.
No changelog for scorpio, but article on XDA here about changes.
https://www.xda-developers.com/twrp-3-3-0-release/
Maybe useful if you need encryption, or edl?
Been using previous version for Xiaomi.eu with no problems.
Scorpio is actually a really good phone, very dependable, as long as you don't overheat it.
latest version of miui (miui11)
did it the latest twrp 3.3.1.0 work/run/installed fine on latest miui (miui 11.0.2.0) please help me
thanks in advance
I can boot the latest version of TWRP (3.4.0) through fastboot, but everytime I tried to install it (whether via fastboot or booted TWRP), it reverts back to mi recovery. Any suggestions? Do I have to install 2.8.4 first? (Please note that the 2.8.4 version image file no longer exists in twrp's site)
My device is bootloader unlocked running on Global MIUI 11.0.2.0 (OADMIXM)
Shok II said:
I can boot the latest version of TWRP (3.4.0) through fastboot, but everytime I tried to install it (whether via fastboot or booted TWRP), it reverts back to mi recovery. Any suggestions? Do I have to install 2.8.4 first? (Please note that the 2.8.4 version image file no longer exists in twrp's site)
My device is bootloader unlocked running on Global MIUI 11.0.2.0 (OADMIXM)
Click to expand...
Click to collapse
Official MIUI will always revert back to Mi recovery.
You have to flash a custom rom if you want to keep TWRP, without rebooting to MIUI.
cobben said:
Official MIUI will always revert back to Mi recovery.
You have to flash a custom rom if you want to keep TWRP, without rebooting to MIUI.
Click to expand...
Click to collapse
Ah so that's why.
Flashed Lineage 17, and now TWRP is persistent, thank you!
Oh right, I noticed that the display brightness is not working (default is too bright btw), as I slide to the right or left, there is no brightness change, TWRP 3.4.0. Haven't tried the older versions tho. Display brightness settings in Lineage works fine.
Related
Team Win Recovery Project 3.0.2-1
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy S6 edge+ stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Flash a root such as SuperSU or phh-superuser. You can also flash .
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
[url]http://teamw.in/devices/samsunggalaxys6edgeplus.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
FULL STEPS FOR ROOTING YOUR DEVICE
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for your device variant.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot without touching any other options, then press [Start].
Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 12 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
Only if you want your internal storage or data partition to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you only want a bootable system partition or readable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
** If your internal storage is encrypted, you will need to use adb sideload instead.
Go to [Reboot] -> [System].
Wait up to 5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-1 - New device tree and kernel, support added for Marshmallow, f2fs, and MTP.
v3.0.2-0 - See here for the changes.
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/TeamWin/android_device_samsung_zenlte (android-6.0)
Kernel: https://github.com/jcadduono/nethunter_kernel_noblelte (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy S6 edge+, Tool/Utility for the Samsung Galaxy S6 Edge+
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/jcadduono/android_device_samsung_zenlte
Version Information
Status: Stable
Current Stable Version: 3.0.2-1
Stable Release Date: 2016-04-08
Created 2016-04-08
Last Updated 2016-12-18
Builds are coming soon guys, I just made the thread so that we have a reference when updating the site.
Bricked after flash, any suggestion? SM-G928F variant with audax plus 3.0 + audax kernel. Recovery not booting, tried reflash with odin old 3.0.0 recovery but the brick persist...
pmisun said:
Bricked after flash, any suggestion? SM-G928F variant with audax plus 3.0 + audax kernel. Recovery not booting, tried reflash with odin old 3.0.0 recovery but the brick persist...
Click to expand...
Click to collapse
Flash the twrp via Odin provided by the Audax rom, that note 5 recovery
Sent from my Darkside of Edge plus
Solved. Btw there is in repo of twrp dev which is linked by audax also 3.0.1 twrp working version. working as charm.
pmisun said:
Solved. Btw there is in repo of twrp dev which is linked by audax also 3.0.1 twrp working version. working as charm.
Click to expand...
Click to collapse
https://idlekernel.com/twrp/zenlte see 3.0.2-1, should be built soon on official, whenever someone confirms that everything is working ok
this includes:
adb shell
brightness slider
installing zips
formatting partitions (as ext4 and f2fs)
not crashing
backup & restore works for each partition
mtp
vibration
otg storage
whatever else you can think of checking
check on both L and M bootloaders, preferably quote my list with Y(working)/N(not working) in front of issues, and give recovery.log
jcadduono said:
https://idlekernel.com/twrp/zenlte see 3.0.2-1, should be built soon on official, whenever someone confirms that everything is working ok
this includes:
adb shell
brightness slider
installing zips
formatting partitions (as ext4 and f2fs)
not crashing
backup & restore works for each partition
mtp
vibration
otg storage
whatever else you can think of checking
check on both L and M bootloaders, preferably quote my list with Y(working)/N(not working) in front of issues, and give recovery.log
Click to expand...
Click to collapse
will try this evening.
pmisun said:
will try this evening.
Click to expand...
Click to collapse
welcome to xda, don't say you'll do things, just do things, it makes people think that they don't have to do it because someone else will do it eventually, slowing things down for everyone.
jcadduono said:
welcome to xda, don't say you'll do things, just do things, it makes people think that they don't have to do it because someone else will do it eventually, slowing things down for everyone.
Click to expand...
Click to collapse
will try and will do..make sense? ok i wont try this.
Why nothing for s6 edge + USC? Everything else except usc version :'(
Tokumei no said:
Why nothing for s6 edge + USC? Everything else except usc version :'(
Click to expand...
Click to collapse
read after first post, builds not up on the site yet, links available
jcadduono said:
read after first post, builds not up on the site yet, links available
Click to expand...
Click to collapse
But there has never been a custom recovery for the s6 edge + USC model. (SM-G928R4 US Cellular) Unless I have missed something then please point me in the right direction for a custom recovery for this specific model.
perfect update TWRP for G928F
https://idlekernel.com/twrp/zenlte/3.0.2-1/twrp-3.0.2-1-zenlte.zip
flash from CWM
It works perfectly fine! The only bug I've found is that vibration doesn't work but that's really not important
Sent from my SM-G928F using XDA-Developers mobile app
Can someone please work on a custom recovery for SM-G928R4? I mean come on now :'(
Works really great on my 928g only vibrations don't work but I don't care thanks a lot.
Guys help
I am using note 5 twrp-3.0.0-0-nobleltezt recovery for my G928C so how to flash this
I have the international SM-G9287 Duo variant on the latest firmware 6.0.1/MMB29K/G9287ZHU2BPC6 (marshmallow) and it's rooted. When I get to the step to press Home+Vol up towards the end of the flash it just reboots normal. Then when I turn of to boot into recovery Home+Vol up+Power I get "RECOVERY IS NOT SEANDROID ENFORCING" in red along the top with the Samsung GS6 logo. I have a tar file with the stock recovery and that boots fine. Any suggestions? Thanks in advance.
I can't find the download link to v.3.0.2-1 on the device page. Am I searching in the wrong place? (https://dl.twrp.me/zenlte)
fisk4rn said:
I can't find the download link to v.3.0.2-1 on the device page. Am I searching in the wrong place? (https://dl.twrp.me/zenlte)
Click to expand...
Click to collapse
Its link is in Post #6.
Powered by Elektrik
Unofficial release -TWRP recovery for the Galaxy J7 Max 2017 - SM-G615F MEDIATEK MT6757
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Update 25/11/2017
TWRP 3.1.1-1 NN build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
NOTE2: THIS DEVICE USES DM-VERITY, ANY CHANGES TO THE SYSTEM PARTITION COULD CAUSE THE DEVICE TO BOOTLOOP. IT MAY BE NECESSARY TO FLASH THE BOOT IMAGE PATCH BELOW.
NOTE: ON ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.1-1_sm-g615f_26817
To Root:
Flash the latest Magisk release with TWRP:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption, dm-verity and mount internal storage (/data) :
1. Boot to Twrp
2. Format the Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install Magisk
5. Reboot
TWRP DEVICE Tree: https://github.com/ashyx/TWRP_Samsung_j7maxlte
Kernel source: https://github.com/ashyx/KERNEL_j7maxlte
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
NOTE: I built this months ago, but forgot to post it up!
.
Great work @ashyx can you please share device tree
I Tested the recovery on my J7 Max and it's working perfectly after flashing the "Boot image patch : no-verity-no-encrypt_ashyx".
one thing i want to tell that the recovery bootlooped(Rebooting the system or Shutting down and again powering on boots into Twrp) the first time i booted it but after flashing Magisk 14.0 and the "no-verity-no-encrypt" patch it works fine.
I've attached the recovery and kernel logs.
Also add a Warning for users to backup their data as i lost all my data after flashing (
and
Thank you for building a TWRP for my device
If you have free time can you please try to build LineageOS for J7 Max
Can you please share the device tree ?
Rumorbox33 said:
Can you please share the device tree ?
Click to expand...
Click to collapse
Yes when I have the opportunity, but be aware twrp device trees are no good for building LineageOS or other custom OS systems.
Thank you for replying.
i just want to study it, upload whenever you have the time
Samsung j700h
[email protected] said:
Samsung j700h
Click to expand...
Click to collapse
No
ashyx said:
Unofficial release -TWRP recovery for the Galaxy J7 Max 2017 - SM-G615F MEDIATEK MT6757
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Update 25/11/2017
TWRP 3.1.1-1 NN build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
NOTE2: THIS DEVICE USES DM-VERITY, ANY CHANGES TO THE SYSTEM PARTITION COULD CAUSE THE DEVICE TO BOOTLOOP. IT MAY BE NECESSARY TO FLASH THE BOOT IMAGE PATCH BELOW.
NOTE: ON ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.1-1_sm-g615f_26817
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption, dm-verity and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Please post your source code This have been up for roughly a month And we need em....Thank you good sir for your hard work
Hi since j7 plus has same chipset.. Can we use this also? Thanks
ashyx said:
No
Click to expand...
Click to collapse
@ashyx Please read PMs.
TheMadScientist said:
@ashyx Please read PMs.
Click to expand...
Click to collapse
I'm guessing you're asking me to post the kernel source as I'm sure you're aware that TWRP device trees are not subject to any license as they are merely config files?
TWRP source code is freely available from their GITHUB.
However I shall endeavour to post the kernel source and device tree.
ashyx said:
I'm guessing you're asking me to post the kernel source as I'm sure you're aware that TWRP device trees are not subject to any license as they are merely config files?
TWRP source code is freely available from their GITHUB.
However I shall endeavour to post the kernel source and device tree.
Click to expand...
Click to collapse
Thank you and disregard any PMS and such all have been reversed
https://imgur.com/a/LHpfm
I did everything said amd everything worked fine and flawlessly. I wanted to spoof in pokemon go by changing an app to system app after rooting and installing magisk bt it gives the error as shown in pic. please help. i m a total noob. i think this was cause i formatted data partition bt i thought it was part of root process. was that necessasry for me do i.e format data partition? Can nybody tell me why i cant move app to system and what can be done? plsssss
Edit: is it beacause the system is not mounted? How to mount a system using twrp? And what does mounting a system actually mean ?
Yuaan rai said:
https://imgur.com/a/LHpfm
I did everything said amd everything worked fine and flawlessly. I wanted to spoof in pokemon go by changing an app to system app after rooting and installing magisk bt it gives the error as shown in pic. please help. i m a total noob. i think this was cause i formatted data partition bt i thought it was part of root process. was that necessasry for me do i.e format data partition? Can nybody tell me why i cant move app to system and what can be done? plsssss
Edit: is it beacause the system is not mounted? How to mount a system using twrp? And what does mounting a system actually mean ?
Click to expand...
Click to collapse
You can use any file manager with root support to move the apk to /system/app
Rumorbox33 said:
You can use any file manager with root support to move the apk to /system/app
Click to expand...
Click to collapse
Used every app and file manager but to no avail. Finally used twrp itself and boom the problem was solved. Thnks anyway.
Any custom roms for samsung j7 max sm-g615f ??
Plez help
Hey I am using samsumg galaxy j7 2015 model which rooted and have twrp recovery in it so I want to add kernel into it so can you give the file and the method to do so and also the best rom for my device
Hey, i built TWRP 3.2.1-1 for this device including some fixes such as pixel format and many more, will you update the thread if i give you the twrp and device trees or i have to make another thread ?
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
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!
Click to expand...
Click to collapse
Images
Prerequisites
Unlocked Bootloader
Click to expand...
Click to collapse
Installation instructions
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
Code:
fastboot reboot
Alternate Installation Method (requires prior TWRP installation):
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed. NOTE: This will only flash TWRP to the active slot!
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select recovery from the partition list and swipe to flash
Click to expand...
Click to collapse
Device Changelog
Current version: 3.6.0_11-0:
Initial version
Click to expand...
Click to collapse
Older Device-specific versions:
N/A
Click to expand...
Click to collapse
Click to expand...
Click to collapse
TWRP Official Change Log
Frequently Asked Questions (FAQ)
Downloads
Download
Latest Official versions
Sources
TWRP
Device tree
Common tree
Kernel source
Click to expand...
Click to collapse
Known Issues
Device-specific
N/A
TWRP Upstream
N/A
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website. 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!
Click to expand...
Click to collapse
Additional Help/Support
Live support is available on Zulip.
Click to expand...
Click to collapse
Frequently Asked Questions (FAQ):
How do I install an OTA while rooted and keep TWRP/root?
Full Firmware zip - in Android
Prerequisites:
Full Firmware zip for new software
TWRP installed to the current slot
Magisk Manager
Steps:
Put Full Firmware zip on root of internal storage
Reboot the device so that the update is detected
Install the update
After install completes BUT BEFORE REBOOTING, install "TWRP A/B Retention Script" module by @osm0sis in Magisk Manager
Install Magisk "to Inactive Slot (After OTA)" in Magisk Manager
Reboot and you're updated with TWRP and root retained
Full Firmware zip - Through TWRP
Prerequisites:
Full Firmware zip for new software
TWRP_Flash_tpposite_Slot-CPTBv2.zip
Magisk zip (optional)
Steps:
Reboot into TWRP
Navigate to Full Firmware zip and install, or sideload zip over adb
Flash TWRP_Flash_tpposite_Slot-CPTBv2.zip to retain TWRP.
(Optional) Reboot into TWRP and flash Magisk for root.
Incremental OTA package - Through TWRP ONLY
Prerequisites:
Current software stock boot.img
Current software stock recovery.img
Current software stock dtbo.img (only if modified by Magisk or custom ROM)
Incremental OTA zip for current software to new software
TWRP_Flash_tpposite_Slot-CPTBv2.zip
Magisk zip (optional)
Steps:
Ensure you have the latest version of TWRP installed. If you don't, follow the instructions in the OP to flash it.
Boot into TWRP.
Use the "Install Image" feature to flash the stock boot and recovery (and dtbo) images.
Flash the incremental OTA zip.
Flash TWRP_Flash_tpposite_Slot-CPTBv2.zip to retain TWRP.
(Optional) Reboot into TWRP and flash Magisk for root.
The key here is making sure the current slot is fully stock (including boot and recovery images) in order for the incremental OTA zip to install successfully.
What's the deal with these dynamic partitions?
Here's Google's explanation.
Why can't I write to system?
Dynamic partitions (see link above). See @topjohnwu's detailed explanation here.
How do I make modifications to system?
On the stock ROM, you don't. However, you can modify system "systemlessly" with Magisk.
Can I boot the recovery image without flashing it?
No. Fastboot boot isn't possible on this device, but since there's a separate recovery partition (two in fact), and ASUS provides full stock firmware, this isn't a big concern.
What is fastbootd?
Here's Google's explanation.
Can I back up the system/vendor partition separately?
No. Because dynamic partitions. The Super partition is backed up and restored in its entirety. If you need to flash the individual images, use fastbootd.
Why can't I restore X partition (read-only error)?
Some of the partitions that can be backed up in TWRP include sensitive device data which, if corrupted, backed up, and then restored, can irreparably damage the device. Therefore, while these partitions can be backed up in TWRP, only experienced users should restore them, which can be done manually via the dd command.
(I will not provide any additional details on this procedure)
Click to expand...
Click to collapse
Reserved
Big thanks to @Buffydamion for all his tireless testing and log-providing to get this TWRP in fully working order!!
Hopefully there aren't any bugs besides the upstream ones listed in the OP, but if there are, I'll do my best to figure them out.
Since I don't have the device, I'll have to rely on all of you for logs and feedback.
Enjoy!!
--Cap
How did you make it boot on this android 10 device? Official TWRP doesn't support android 10. Dees_Troy is still working on the solution.
Volski_ said:
How did you make it boot on this android 10 device? Official TWRP doesn't support android 10. Dees_Troy is still working on the solution.
Click to expand...
Click to collapse
@Dees_Troy isn't the only person on the TWRP team.
@bigbiff has been working tirelessly to add Android 10 support to TWRP, with help from @mauronofrio, @androiabledroid, myself and others. TWRP is open-source and a team effort. As you'll notice, there are still some upstream bugs that need to be fixed, which is why the official TWRP hasn't been updated yet. But it's working well enough to release it for devices that need it, and when the official TWRP is ready, these devices will have official support.
Works fine for me. Thanks!
The data partition was already partitioned to f2fs.
Flashed magisk and have a rooted phone now. Perfect!
Update - new 20200920 build with stock kernel with f2fs support thanks to a proper fix from @aleasto.
I've also unified the dtb & dtbo with the ROG3 build, so this one needs testing to confirm it's booting for everyone. Please report back here once you have a chance to update.
--Cap
Captain_Throwback said:
Update - new 20200920 build with stock kernel with f2fs support thanks to a proper fix from @aleasto.
I've also unified the dtb & dtbo with the ROG3 build, so this one needs testing to confirm it's booting for everyone. Please report back here once you have a chance to update.
--Cap
Click to expand...
Click to collapse
So I had to remove the above build as it didn't boot. Building a new one now and hopefully it'll work. I'll keep everyone posted.
New release 20200922-14
There's a new release available today, which I recommend everyone switch to at their earliest convenience. I've also added a zip attachment to the first post that will allow you to flash a TWRP installed to your current slot to the opposite/inactive slot after an OTA is installed, so that you keep TWRP (otherwise it gets replaced by the OTA/firmware zip). The zip can be flashed either in Magisk Manager after the OTA completes installing (but BEFORE rebooting) or in TWRP after manually flashing a full firmware update zip (but PRIOR to rebooting). The zip simply duplicates the recovery from the existing recovery partition to the opposite slot, so it will only work if TWRP is currently installed to the active slot.
Change Log:
Update prebuilt kernel to source built with @aleasto's patch for f2fs
Set data filesystem to f2fs in recovery fstab
Add TWRP flags to disable screen blank to ensure touchscreen gets initialized on boot and screen wake works
Hi guys, i tried on mine and worked smoothly...the only thing I still cant do is writing in system folder...I tried multiple app as Root explorer but still can't manage to write anything even with root permission...
Any thoughts?
luiscaproducer said:
Hi guys, i tried on mine and worked smoothly...the only thing I still cant do is writing in system folder...I tried multiple app as Root explorer but still can't manage to write anything even with root permission...
Any thoughts?
Click to expand...
Click to collapse
That is normal for dynamic partitions. The full super partition can be written but not the individual block devices.
Thanks Captain! So basically I will have to wait for the official release of the TWRP? Or it will just never happen to have a super partition...Excuse the ignorance
luiscaproducer said:
Thanks Captain! So basically I will have to wait for the official release of the TWRP? Or it will just never happen to have a super partition...Excuse the ignorance
Click to expand...
Click to collapse
That is unrelated to TWRP being official or not, lol.
TWRP upstream will soon be updated to allow read/write of the system partition, but keep in mind that verity will need to be disabled for you to change any of the content, unless you don't want your device to boot .
--Cap
P.S. If you need to make modifications to system, you should use Magisk - it's made for this exact situation.
Captain_Throwback said:
There's a new release available today, which I recommend everyone switch to at their earliest convenience. I've also added a zip attachment to the first post that will allow you to flash a TWRP installed to your current slot to the opposite/inactive slot after an OTA is installed, so that you keep TWRP (otherwise it gets replaced by the OTA/firmware zip). The zip can be flashed either in Magisk Manager after the OTA completes installing (but BEFORE rebooting) or in TWRP after manually flashing a full firmware update zip (but PRIOR to rebooting). The zip simply duplicates the recovery from the existing recovery partition to the opposite slot, so it will only work if TWRP is currently installed to the active slot.
Change Log:
Set data filesystem to f2fs in recovery fstab
Add TWRP flags to disable screen blank to ensure touchscreen gets initialized on boot and screen wake works
Click to expand...
Click to collapse
Works perfect for me. Thank you
Update 20201001-02
Changelog:
- Add support for installing incremental OTAs (requires flashing/restoring stock boot and recovery images while in TWRP)
- Add all relevant partitions to dynamic partition list and improve display of Super partition in Backup screen
- Add asusfw, EFS, Modem, & Persist partitions as backup options (USE WITH CAUTION!!)
Captain_Throwback said:
Changelog:
- Add support for installing incremental OTAs (requires flashing/restoring stock boot and recovery images while in TWRP)
- Add all relevant partitions to dynamic partition list and improve display of Super partition in Backup screen
- Add asusfw, EFS, Modem, & Persist partitions as backup options (USE WITH CAUTION!!)
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------
Hi,
I would like to install TWRP. if I understood correctly you have to do this:
1. Unlock Bootloader
2. Install TWRP on both partitions.
3. Install TWRP_Flash_tpposite_Slot-CPTB.zip
4. Install Magisk.
Is it right?
And the correct procedure to update OTA? can you remove magisk and module before?
Thank you for your answers.
[email protected] said:
------------------------------------------------------------------------------------------------------------------------
Hi,
I would like to install TWRP. if I understood correctly you have to do this:
1. Unlock Bootloader
2. Install TWRP on both partitions.
3. Install TWRP_Flash_tpposite_Slot-CPTB.zip
4. Install Magisk.
Is it right?
And the correct procedure to update OTA? can you remove magisk and module before?
Thank you for your answers.
Click to expand...
Click to collapse
You don't need #3, as you're flashing TWRP to both slots in #2. That zip is for keeping TWRP after flashing a full firmware zip.
To update with an incremental OTA, you have to have the stock boot and recovery images from the current firmware available to be flashed in TWRP. You have to boot to TWRP and flash both stock boot and recovery, and then you can flash the incremental OTA. Then reboot to bootloader and flash TWRP, then reboot to recovery and flash Magisk for root.
Great and thanks Captain T.
Just a clarification, if i flash a full OTA (not incremental OTA) i don't need flash the stock boot, right?
[email protected] said:
Great and thanks Captain T.
Just a clarification, if i flash a full OTA (not incremental OTA) i don't need flash the stock boot, right?
Click to expand...
Click to collapse
Correct.
And then you need to flash the zip that flashes TWRP to the opposite slot so you keep TWRP once you reboot. You'll have to reboot back into TWRP and flash Magisk if you want to keep root.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
FEATURES AND FIXES:
No need to reboot TWRP after flashing ROM, to flash gapps or any other zips. All zips you flash after a ROM will automatically go to the new slot.
No need to flash TWRP everytime after flashing a ROM. TWRP automatically flashes itself after a zip (Controllable via a toggle)
Supports Hentai OS encrypted devices
Supports flashing MIUI zips
Supports Vibration
Supports wiping data without wrecking encryption.
BUGS:
On encrypted devices, if u unmount and remount /data, it will show garbage files in storage. This is because of metadata encryption and to fix it, reboot recovery.
SUPPORTS AND TESTED ON:
Mi11x (aliothin)
UNSUPPORTED (BUT MAY WORK):
Poco F3, Redmi K40 (alioth)
FLASHING INSTRUCTIONS:
Boot into attached boot.img using the following command:
Code:
fastboot boot twrp-aliothin.img
Once booted, go to Advanced -> Press "Flash current booted TWRP"
KNOWN LIMITATIONS:
The following are some known limitations due to either the design nature of Virtual A/B or a problem with ROM themselves. Please read carefully :-
You cannot format data after flashing a ROM zip (Limitation of Virtual A/B). If you want to format, then reboot recovery after flashing ROM. Additionally, if you are encrypted, the newly flashed ROM must be able to decrypt your device. If not, then you have to format data before flashing the ROM It appears, you can actually format data after reboot even if the new ROM cannot decrypt.
You can flash only one ROM in one boot. If you wanna flash another ROM, you must boot to system once. This is again a limitation of Virtual A/B.
Once you have rebooted after flashing a ROM, you cannot write to the data partition until you boot successfully to the new ROM. Android seals the data partition after a ROM flash to prevent any accidental brick since the newly flashed ROM is actually stored in /data. Only data format is allowed in this case. Once you successfully boot to the new ROM, your storage becomes ready for writing again.
Ideally, after flashing a new ROM, you should only need to wipe your data rather than format. But, due to a problem in the device trees current ROMs are using, you will have to format data if you are currently on miui and want to switch to a custom ROM. Specifically, the roms need this commit and to set vendor security patch level to fix this issue. Switching between custom ROMs should not need format, except for hentai OS.
If you are currently on hentai OS, then before using TWRP, you must flash vendor_boot from the link provided in every hentai OS release. Otherwise, you will get black screen. This is only needed when you boot to TWRP for the first time. Do not repeat this step again. Also, do not try this with beta version of the ROM. Use it only with stable.
If you reboot to older slot after flashing new ROM, the new ROM will be cancelled and you will have to reflash again. This is because of how Virtual A/B works.
If you must flash magisk via recovery (it's not recommended now), please uncheck "Inject TWRP after install" else TWRP will remove magisk.
Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.
Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.
CREDITS:
@Nebrassy for original TWRP and device tree. I also repurposed some of his commits from gerrit.
SOURCE CODE:
Kernel (Prebuilt): https://github.com/ArrowOS-Devices/android_kernel_xiaomi_alioth
DOWNLOADS:
https://drive.google.com/file/d/1oY5WxfXYPRLumCcaPPFGuq9OhtB3CM_X/view?usp=sharing
MD5:- 0909f61c83ce9876843dabba5bf1247e
TELEGRAM GROUP LINKS:
https://t.me/PocoF3GlobalOfficial
https://t.me/pocoF3GlobalUpdates
Reserved
Reserved
ayy pro <3
Yay Yahoo
Thx for your work, dev.
Quick question. Why is it not recommended to install magisk via TWRP now?
UPD: Flashed Magisk successfully with unchecked "inject twrp..."
I have the same question, how should we flash magisk now? I'm old school so for me it was allways the best and fastest way...
vasishath said:
Great work.
Click to expand...
Click to collapse
blinoff82 said:
Thx for your work, dev.
Quick question. Why is it not recommended to install magisk via TWRP now?
UPD: Flashed Magisk successfully with unchecked "inject twrp..."
Click to expand...
Click to collapse
Twrp reflashes itself after every zip flash, hence it removes magisk, you can uncheck inject twrp option to flash tho.
@vasishath
Hello,
First of all thank you for developing a version of TWRP.
I have a little problem with this one: failed to mount: system_root, vendor, odm
Unable to find partition for path storage
I can't install TWRP ...
I'm on the weekly xiaomi.eu
Here are the issues I'm currently having with your version of TWRP.
Shadowk1ller said:
I have the same question, how should we flash magisk now? I'm old school so for me it was allways the best and fastest way...
Click to expand...
Click to collapse
Patch the boot.img using the Magisk App and then flash the patched boot.img via fastboot
Shadowk1ller said:
I have the same question, how should we flash magisk now? I'm old school so for me it was allways the best and fastest way...
Click to expand...
Click to collapse
John Wu recommands direct install from magisk app
vasishath said:
John Wu recommands direct install from magisk app
Click to expand...
Click to collapse
TWRP not installed after installing custom ROM. Please check.
deif102 said:
Patch the boot.img using the Magisk App and then flash the patched boot.img via fastboot
Click to expand...
Click to collapse
To much work, when i can simply flash it in twrp after i flash the rom, it was that easy in past times...
But can i uncheck inject before flashing and then check it again and flash current booted TWRP as in the beggining?
Which rom did u flash ?
blinoff82 said:
TWRP not installed after installing custom ROM. Please check
Click to expand...
Click to collapse
vasishath said:
Which rom did u flash ?
Click to expand...
Click to collapse
My own ROM - Syberia OS (AOSP).
(Maybe after flashing ROM I can install twrp.img in recovery ramdisk?)
blinoff82 said:
My own ROM - Syberia OS (AOSP).
(Maybe after flashing ROM I can install twrp.img in recovery ramdisk?)
Click to expand...
Click to collapse
He is referring to use controllable toggle so I assume you should have enabled it before flashing rom. I still didn't tried this twrp so dunno where actually this toggle is..
NE0HP said:
He is referring to use controllable toggle so I assume you should have enabled it before flashing rom. I still didn't tried this twrp so dunno where actually this toggle is..
Click to expand...
Click to collapse
Of course this toggle was turned on before flashing (by default).
blinoff82 said:
My own ROM - Syberia OS (AOSP).
(Maybe after flashing ROM I can install twrp.img in recovery ramdisk?)
Click to expand...
Click to collapse
It appears to me that the ramdisk-files.sha256sum file was removed after u flashed the ROM. That caused the TWRP flashing to fail. Does your ROM's zip modify the current running ramdisk in anyway ?
Will future Miui builds now be using this version of twrp? if this is the case i wont need to flash it right now.
Hey folks OrangeFox Recovery is finally here for OnePlus Nord (avicii)...
THIS RECOVERY WILL SUPPORT STOCK ROMS, FBEv1 CUSTOM ROMS, FBEv2 CUSTOM ROMS.
DISCLAMER
Your warranty is now void.
I am not responsible for any damage that is made due to this action.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"If the device is encrypted, then you must format the data partition (NOTE: format - not just wipe). If the device is not encrypted, then you can just wipe the data partition (ie, no need to format)"
-source wiki.orangefox.tech
KNOWN ISSUE FOR FBEv1 Recovey : DATA BACKUP AND RESTORE NOT WORKING
DATA DECRYPTION NOT WORKING FOR SOME ROMS
KNOWN BUG FOR 00S12 Recovery (0.1%) : DATA BACKUP AND RESTORE WORKS, BUT HAVEN'T FOUND A PERFECT WAY TO RESTORE AND MAKE THE PHONE FULLY WORKING. IF YOU ARE FREE PLEASE CONSIDER TO FIND A WAY TO PERFECTLY BACKUP AND RESTORE OOS12 ROM DATA PARTITION
Note: Only boot and work with OOS12, never try to flash with FBEv1 or FBEv2 roms, if you do so, your device will face a softbrick. Similarly donot try FBEv1 or FBEv2 recoveries with OOS12. This is due to the mismatch in firmwares of OOS12 and other roms
If flashing rom from OOS12 variant, after installing custom rom, flash FBEv1, FBEv2 recovery accordingly. And vice versa
To flash OOS12 OTA (Only available from R11.1_3 onwards)
I added 2 scripts inside the recovery.
Before flashing OOS12 OTA
Go to terminal
Type and press enter
sh /system/bin/pre_oos_flash.sh
You will see an error "kPostinstallError" : just ignore it.
After flashing OOS12 OTA
Go to terminal
Type and press enter
sh /system/bin/post_oos_flash.sh
Then switch slot to updated slot
Downloads :
For FBEv1 Custom Roms :
OrangeFox Recovery R11.1_2 (Image File)
OrangeFox Recovery R11.1_2 (Flashable Zip Installer)
For OOS12 Rom:
OrangeFox Recovery R11.1_3 (Image File)
OrangeFox Recovery R11.1_3 (Flashable Zip Installer)
For FBEv2 Custom Roms :
OrangeFox Recovery R11.1_2 (Image File)
OrangeFox Recovery R11.1_2 (Flashable Zip Installer)
Guide to flash recovery :
• Reboot to FASTBOOT
• Connect your phone via USB to PC
• Open Command Prompt (You must install ADB and fastboot platform files) and type
• Only to boot the recovery
fastboot devices
fastboot boot <path to recovery image file>
• To flash recovery
fastboot devices
fastboot flash recovery <path to recovery image file>
Special Thanks to
OrangeFox Recovery Project
@DarthJabba9
@Wishmasterflo
@lordfinix
For People residing inside India
UPI :- [email protected]
For People residing outside India
Paypal
CHANGELOG (16/11/2022) - R11.1_3_OOS12
1) Initial Build
2) Support OOS12
3) 99.9% Features work
CHANGELOG (16/11/2022) - R11.1_2_FBEv1
1) Initial Build
2) Toggle Flashlight FIxed
3) Screen Ratio Fixed
4) Notch Positioning Fixed
5) Added CPU Temperature Monitor
6) Slot Switching Fixed
CHANGELOG (16/11/2022) - R11.1_2_FBEv2
1) Fixed Data Partition Backup & Restore
2) Fixed Data Partition Wipe
CHANGELOG (13/11/2022) - R11.1_1_FBEv2
1) Initial Build
2) Data Decryption Fixed
3) Toggle Flashlight FIxed
4) Screen Ratio Fixed
5) Notch Positioning Fixed
6) Added CPU Temperature Monitor
7) Slot Switching Fixed
Can you do one for a12 coloros?
skia16 said:
Can you do one for a12 coloros?
Click to expand...
Click to collapse
Ys. But require few edits. I need to build another separate version for Oxygen OS, Color OS and some other custom roms since they use FBEv1 file encryption.
Works super good! one of GOAT recoveries
@Sreeshankar K
Thanks for this great recovery! It´s working like a charm on my device.
One question: is it able to decrypt data/internal storage? I have a pattern, but there is no option in decryption to use this or am I wrong? I´m on Lineage OS 19.1.
gllark said:
@Sreeshankar K
Thanks for this great recovery! It´s working like a charm on my device.
One question: is it able to decrypt data/internal storage? I have a pattern, but there is no option in decryption to use this or am I wrong? I´m on Lineage OS 19.1.
Click to expand...
Click to collapse
Probably Lineage OS 19.1 is FBEv1 ROM. This recovery only support FBEv2 ROMs. I had mentioned it in the post. Currently no support for FBEv1 ROMs. If u want fully functioning recovery please go to the telegram group mentioned in the XDA post.
And also thanks for ur positive comment
Wasn't able to decrypt the data partition with LOS 18.1 and the FBEv1 version.
And now after booting, Bluetooth is no more starting/working.
It's doesn't turn on, it goes back to off every time.
Had this problem also in the past with the OFRP from the other thread.
Edit: was able to fix the Bluetooth problem with: restorecon -R /data
Doc Sniper said:
Wasn't able to decrypt the data partition with LOS 18.1 and the FBEv1 version.
And now after booting, Bluetooth is no more starting/working.
It's doesn't turn on, it goes back to off every time.
Had this problem also in the past with the OFRP from the other thread.
Edit: was able to fix the Bluetooth problem with: restorecon -R /data
Click to expand...
Click to collapse
Lemme check with lineage os 19.1. both 18.1 and 19.1 are FBEv1
Doc Sniper said:
Wasn't able to decrypt the data partition with LOS 18.1 and the FBEv1 version.
And now after booting, Bluetooth is no more starting/working.
It's doesn't turn on, it goes back to off every time.
Had this problem also in the past with the OFRP from the other thread.
Edit: was able to fix the Bluetooth problem with: restorecon -R /data
Click to expand...
Click to collapse
I checked it on superior os which is FBEv1. And data partition was successfully decrypted
Sreeshankar K said:
I checked it on superior os which is FBEv1. And data partition was successfully decrypted
Click to expand...
Click to collapse
Strange, because here the decryption doesn't work.
The partition was once encrypted by LOS 18.1, hence probably FBEv1.
Also tried the FBEv2 recovery, but as expected no decryption dialog appears.
Thanks for testing and also creating the recovery.
Do we have any other options to test or fix this?
Doc Sniper said:
Strange, because here the decryption doesn't work.
The partition was once encrypted by LOS 18.1, hence probably FBEv1.
Also tried the FBEv2 recovery, but as expected no decryption dialog appears.
Thanks for testing and also creating the recovery.
Do we have any other options to test or fix this?
Click to expand...
Click to collapse
Ys not working. It was the first build of FBEv1 recovery released yesterday. I will check it.. Thanks for testing it. I go through the logs found that FBE decrypt setup is working fine but it cannot decrypt metadata partition.
Sreeshankar K said:
Ys not working. It was the first build of FBEv1 recovery released yesterday. I will check it.. Thanks for testing it. I go through the logs found that FBE decrypt setup is working fine but it cannot decrypt metadata partition.
Click to expand...
Click to collapse
This could possibly cause the Bluetooth problem, because the SELinux permissions don't seem to match after trying to decrypt data.
In any case, it's great that you're taking the time to look for the problem and fix it. Thanks.
Doc Sniper said:
This could possibly cause the Bluetooth problem, because the SELinux permissions don't seem to match after trying to decrypt data.
In any case, it's great that you're taking the time to look for the problem and fix it. Thanks.
Click to expand...
Click to collapse
Recovery settings and rom settings have no connections. Recovery only look for the fstab of rom to do the operations like wipe, install, backup and restore etc. Idk why that prob is appeared
Sreeshankar K said:
Ys not working. It was the first build of FBEv1 recovery released yesterday. I will check it.. Thanks for testing it. I go through the logs found that FBE decrypt setup is working fine but it cannot decrypt metadata partition.
Click to expand...
Click to collapse
Any news ?
Tried booting then flashing the R11.1_2_FBEv1 build using the fastboot manual flash, with OOS F17 EU (the latest for my device at the time of writing), it doesn't boot and just show the "boot/recovery destroyed" screen, any idea why?
Phone was also not booting after the flash, stuck on the "destroyed" screen, and I had to reflash the boot.img (no, I did not flash over boot, I double checked that I did specify recovery_a/_b when flashing)
WORMSTweaker said:
Tried booting then flashing the R11.1_2_FBEv1 build using the fastboot manual flash, with OOS F17 EU (the latest for my device at the time of writing), it doesn't boot and just show the "boot/recovery destroyed" screen, any idea why?
Phone was also not booting after the flash, stuck on the "destroyed" screen, and I had to reflash the boot.img (no, I did not flash over boot, I double checked that I did specify recovery_a/_b when flashing)
Click to expand...
Click to collapse
It is bcoz, OOS12 firmware doesn't support other custom kernels, firmwares etc
Sreeshankar K said:
It is bcoz, OOS12 firmware doesn't support other custom kernels, firmwares etc
Click to expand...
Click to collapse
Isn't "For Stock Roms (Oxygen OS and Color OS) & FBEv1 Custom Roms" a bit misleading then? Since it mention OOS and it being "For Stock Roms"
Tried out the new OOS12 option, works like a charm! Both the img and the zip!
I haven't tested everything but decryption, usb mounting, usb_otg, backups, sideloading and a lot more works perfectly!
I did encounter a bug tho, after trying out a few features, my filesystem appeared encrypted, with gibberish names for the folders and files
Fortunately it didn't affect anything and a reboot fixed everything
Finally a proper working recovery for the Nord!
WORMSTweaker said:
Tried out the new OOS12 option, works like a charm! Both the img and the zip!
I haven't tested everything but decryption, usb mounting, usb_otg, backups, sideloading and a lot more works perfectly!
I did encounter a bug tho, after trying out a few features, my filesystem appeared encrypted, with gibberish names for the folders and files
Fortunately it didn't affect anything and a reboot fixed everything
Finally a proper working recovery for the Nord!
Click to expand...
Click to collapse
Data backup and restore is buggy, means not saying that it is not working, haven't found a correct way to restore the backup of data partition, so if you have time please found a correct way to restore data partition, and post it here. Data decryption and all other features work.
[RECOVERY] [13] [UNOFFICIAL] TeamWin Recovery Project (8T / 9R) (2022-07-27)
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Like this we also need correct way to backup and restore data partition, so, if your are free do it.
WORMSTweaker said:
Tried out the new OOS12 option, works like a charm! Both the img and the zip!
I haven't tested everything but decryption, usb mounting, usb_otg, backups, sideloading and a lot more works perfectly!
I did encounter a bug tho, after trying out a few features, my filesystem appeared encrypted, with gibberish names for the folders and files
Fortunately it didn't affect anything and a reboot fixed everything
Finally a proper working recovery for the Nord!
Click to expand...
Click to collapse
"I did encounter a bug tho, after trying out a few features, my filesystem appeared encrypted, with gibberish names for the folders and files
Fortunately it didn't affect anything and a reboot fixed everything "
This is bcoz your data partition is not decrypted. Decrypt it using your rom password then everything will be normal. That's not a bug... Bug is in the restoration of backuped data. Actually not a bug. Didn't found a fully working way.
Need to find a perfect way to restore. OOS12 data restore is bit painful.
Take a look on data backup and restore
if you are free
Thank you