Database Info

[Recovery] TWRP Recovery 2.7.0.x (recommended for 4.2.2)

Hi there, i'm starting here a discussion thread about Team Win Recovery Project 2.x for our HTC One SV.
Team Win Recovery Project 2.x, or twrp2 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.
Click to expand...
Click to collapse
{
"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"
}
Pictures by TWRP
As long as i know it will work for k2_u and k2_ul (LTE), cause both have the same partition layout.
This recovery don't work for boost mobile users!
Notice:
This is not my work, i'm not the developer of it!!! I only start the thread here about it because the dev is a russian guy (and i don't know, if he is here at xda and if he speaks english language).
Please be sure what you are doing, when you flash it, bricks can happen and i am not responsible for damaged devices. Do at your own risk!
Credits:
- xpirt for building it
- Modding.MyMind for his open mind
- MikG for earlier versions
- Team Win Recovery Project
- rollon76 for posting this here on xda
- jmztaylor (for being a great guy and help if needed)
- bkcokota (for his cwm recovery, a start for development)
Important: Recommended for hboot 2.21!
Download:
--------------------------------------------------------------------------------
This is not for boost mobile users!
You can find TWRP Recovery 2.7.0.1 (made by xpirt, credits and thanks to him) here.
Only for k2u & k2ul!
--------------------------------------------------------------------------------
The recovery for boost mobile (K2_CL) users is in the second post!!!
--------------------------------------------------------------------------------
How to install:
Download the img file and rename it to recovery.img
Put it into your fastboot folder and start a command window there.
Boot your phone into fastboot USB mode (bootloader + device plugged to pc)
Enter the following command:
Code:
fastboot flash recovery recovery.img
That's it.

K2_CL ONLY!!!!!
Kernel Source: Click Here!
Changelog Version 2:
Code:
* From commit [URL="https://github.com/ModdingMyMind/android_kernel_htc_k2_cl_twrp/commit/86a317157a741ef12042426696e3c84eeed3e263"]86a317157a[/URL] on my github.
* Kernel built in version 2.7.1.0
* Disabled Module support
Changelog Version 1:
Code:
* From commit [URL="https://github.com/ModdingMyMind/android_kernel_htc_k2_cl_twrp/commit/c34ea02e20b758e78cae9f8b8bc975d268accd84"]c34ea02[/URL] on my github.
* Kernel built in version 2.7.0.2[B]d[/B]
* Added full SELinux support.
* Removed HTC write protection.
---------------------------
---------------------------
TWRP 2.7.1.0 - for 4.2.2
TWRP 2.7.0.2d - for 4.2.2
TWRP 2.7.0.2c - for 4.2.2
TWRP 2.7.0.2b - for 4.2.2 (deprecated)
TWRP 2.7.0.2a - for 4.2.2 (deprecated)
---------------------------
---------------------------
TWRP source was patched from https://gerrit.omnirom.org/#/c/6283/
This patch allows the ability to take screenshots while in the recovery. It has not been merged over to the TWRP source yet so only unofficial builds at this moment will be seen with this feature.
To take screenshots while in recovery just press both the power key and volume down key. The screen will flash. It will naturally store the screenshot in your pictures folder of your sdcard if mounted in either your internal or external.
TWRP Changelogs:
Code:
[U]2.7.1.0
[/U]Built with custom kernel.
- [B]Removed custom theme and reverted back to stock theme.[/B]
- Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button.
- Various bugfixes to backup and restore
- Improvements to USB storage handling
- Added a class to search for files to make finding the correct brightness file automatic in most cases
- Various other bugfixes and tweaks
[U]2.7.0.2d[/U]
Built with custom kernel.
- Added full SELinux support
- Completely removed HTC write protection.
[U]2.7.0.2c[/U]
Fixed init.rc to allow communication with binaries in /sbin.
TWRP 2.7.0.2c is built ready for SELinux, but the kernel is stock. Until they release the source I can't modify the kernel to support SELinux. This is really only needed for having 4.3+ roms but I want to include it in case the day comes and we see CM, AOSP, or possibly other sources.
[U]2.7.0.2b[/U]
Minor theme adjustment
Upgraded screenshot functionality throughout entire recovery
Note - version 2.7.0.2a screenshots are limited to only the main page
TWRP 2.7.0.2b is built ready for SELinux, but the kernel is stock. Until they release the source I can't modify the kernel to support SELinux. This is really only needed for having 4.3+ roms but I want to include it in case the day comes and we see CM, AOSP, or possibly other sources.
[U]2.7.0.2a[/U]
Built from CM11 and Omni 4.4 sources.
Extended backup options.
1. System
2. Boot
3. Cache
4. Data
5. Recovery
6. Misc
7. Firmware_radio
8. Firmware_q6
9. android secure
*** I think I listed them all ;)
Built in AromaFM.
Implemented screenshot functionality.
Added offmode charging.
Completely updated to fit with 4.2.2.
Includes Holofied Black Theme.
TWRP 2.7.0.2a is built ready for SELinux, but the kernel is stock. Until they release the source I can't modify the kernel to support SELinux. This is really only needed for having 4.3+ roms but I want to include it in case the day comes and we see CM, AOSP, or possibly other sources.
HTC Dumlock Instructions:
HTC Dumlock Instructions specifically for S-On users but S-Off users can use it as well if they choose to:
1. Install the build of TWRP using your method of choice, but you must actually flash TWRP to recovery.* No fastboot booting it.* We need it in recovery so that this build of TWRP will be flashed to your boot.* This new build of TWRP has features in it to easily restore your original boot.
2. Reboot into recovery.
3. Make a backup of your phone.
4. Tap Advanced.
5. Tap HTC Dumlock. (If you don't see HTC Dumlock then you need to remove any custom TWRP theme that you might be using.)
6. Tap Install HTC Dumlock.* This will install the app and binaries needed to make everything work nicely.
7. Reboot your device.
8. Find and open the HTC Dumlock app.
9. If/when prompted, give the app root (SuperUser) permissions.
10. Tap the Execute HTC Dumlock button.
11. Wait patiently for a couple of minutes.* It takes a little while.
If your device doesn't reboot automatically, reboot it manually.* Reboot it normally.* DO NOT reboot it to recovery.
You should now be in your recovery, but your recovery is flashed into boot.
12. Tap Advanced.
13. Tap HTC Dumlock.
14. Tap Restore Original Boot.
Use your recovery like normal.* Flash a new kernel.* Restore a backup with a different kernel.* Do whatever you please!
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Addition
This recovery also works in the ADB mode with root rigths.
In this mode, you can add (delete) files in the SYSTEM
on OS Jelly Beam
And sets the superuser, if superuser is not in the system.:good:

Are you the developer of it?
I hope it is ok for you that i have started a thread for it here?
Anyway, it works great and you have done it very well ! :good::good::good:
Thanks a lot!!

Thank you. Use it. Version 2.5.0.1 is made on the kernel 3.14.10-gf43d146.

Bootloader and boot restored only if you have S-OFF.

where can i download version 2.5.0.1?? i have 2.5.0 and it works great.
---------- Post added at 06:13 PM ---------- Previous post was at 06:06 PM ----------
MikG said:
This recovery also works in the ADB mode with root rigths.
In this mode, you can add (delete) files in the SYSTEM
on OS Jelly Beam
And sets the superuser, if superuser is not in the system.:good:
Click to expand...
Click to collapse
Is compulsory be S-OFF to delete files in system??could you explain how to do it??
thanks

titin83 said:
Is compulsory be S-OFF to delete files in system?
Click to expand...
Click to collapse
A custom kernel can do this also.

old.splatterhand said:
A custom kernel can do this also.
Click to expand...
Click to collapse
And is there alredy a kernel that let us do this?? By the way , what recovery are you using?? if is 2.5.0.1 , could yo tell me where download it?? in the russian page i got an error when i try to sign in there , and the translation with google is rather bad...
thanks

titin83 said:
And there is alredy a kernel that let us do this?? By the way , what recovery are you using?? if is 2.5.0.1 , could yo tell me where download it?? in the russian page i got an error when i try to sign in there , and the translation with google is rather bad...
thanks
Click to expand...
Click to collapse
To sign in there is really painful if you don't speak the language, but as far as i know it does not work as long you are on google translation. The captcha i could only pass with a guy from another board who speaks russian.
The recovery shows 2.5.0.0 but the filename from download page was Recovery_TWRP_2.5.0.1_HTC_ONE_SV.img so i think it is the same.
Kernel can be found here.

old.splatterhand said:
To sign in there is really painful if you don't speak the language, but as far as i know it does not work as long you are on google translation. The captcha i could only pass with a guy from another board who speaks russian.
The recovery shows 2.5.0.0 but the filename from download page was Recovery_TWRP_2.5.0.1_HTC_ONE_SV.img so i think it is the same.
Kernel can be found here.
Click to expand...
Click to collapse
And the last question , can i flash the kernel without installing the whole rom?? i mean , flash it in the rom that i update some weeks ago via OTA or have i to flash the ro that you have in your signature? My SV is K2_U , can i flash this despite be for K2_UL devices??
thanks

You can flash the kernel only and also for k2u (i have too).
If you are not S-off, you need to flash the zip in recovery and the boot.img inside with fastboot.

once i have flashed the kernel , what i have to do to delete some system app??
thanks again

Use a root explorer and go to system/apps/ and delete the one you don't need anymore (or rename it first to see if it causes problems).
But be carefull with what you delete and make a nand backup before!!!!!

titin83 said:
where can i download version 2.5.0.1?? i have 2.5.0 and it works great.
Is compulsory be S-OFF to delete files in system??could you explain how to do it??
thanks
Click to expand...
Click to collapse
Link in the header right.
S-OFF not need.
In the recovery mount SYSTEM. And the button ADVANCED-> File manager can work fine.
old.splatterhand said:
Use a root explorer and go to system/apps/ and delete the one you don't need anymore (or rename it first to see if it causes problems).
But be carefull with what you delete and make a nand backup before!!!!!
Click to expand...
Click to collapse
No, in JB OS files not be deleted.
Instead, use the file manager in the TWRP recovery.

edit: i was too fast... twrp doesnt work for me. it install perfectly but i cannot boot android anymore? does this work for someone else?

sakax said:
edit: i was too fast... twrp doesnt work for me. it install perfectly but i cannot boot android anymore? does this work for someone else?
Click to expand...
Click to collapse
Everything works fine in my device. Flash it again , perhaps something was wrong.

sakax said:
edit: i was too fast... twrp doesnt work for me. it install perfectly but i cannot boot android anymore? does this work for someone else?
Click to expand...
Click to collapse
This twrp recovery work on many device k2_u and k2_ul fine.

MikG said:
This twrp recovery work on many device k2_u and k2_ul fine.
Click to expand...
Click to collapse
my phone doesnt boot anymore after installing twrp recovery? do i have to reinstall kernel and system backup after flashing recovery? the problem is that i only have cwm backup available?

As long as i know, you can't restore cwm backup with TWRP. So you need to flash cwm and restore your backup with that.

[TOOL]GalaxyTab3_Toolkit v1.1 - All-in-One Tool - SM-T310 (UPDATED 02/02/2014)

GalaxyTab3_Toolkit v1.1
For use with the Samsung Galaxy Tab 3 8" WiFi - SM-T310 Model
{
"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"
}
This is an all-in-one tool, used to assist with rooting/custom recovery/stock rom/custom rom/bricks
I've made this because, there isn't a tool specifically for the 8" sm-t310 available, and I figured everybody could benefit from it somehow.
- Instantly and directly download the following:
--- GalaTab3 Kernel v14.1.6 (thanks to @arshull )
--- CWM Recovery v6.x r#4 (thanks to @emwno )
--- TWRP Recovery v2.5.0.0 r#3 (thanks to @emwno )
--- TWRP Recovery 2.6.3.0 (thanks to @gr8nole )
--- Philz Advanced CWM v6.12.8 (thanks to @Phil3759 )
--- Odin v.3.09
- Flash recovery, stock firmware image
- Read system information
- Run Odin within this app to flash recovery/firmware
- View live logcat
- Supports JDQ39 firmware 4.2.2 (does not currently work with 4.3/4.4!!)
- Perfect for noobs and advanced users
Download
http://www.f0il.com/android/GalaxyTab3_Toolkit_v1.1.zip - v1.1
Special thanks to:
@arshull - for his GalaTab3 Kernel work
@emwno - for his CWM & TWRP Recovery work
@regaw_leinad - for his AndroidLib project
@autoprime - for being a cool ass dude
@gr8nole - for his work on CWM recovery and Cyanogenmod port
@Phil3759 - for his awesome advanced CWM port
Changelog -
02/02/2014 - v1.1
(*) Fixed Reboot Download issue requiring root, will now reboot regardless
(*) Reworked GUI to be quite a bit more friendly
(*) Fixed a few connection related bugs
(+) Added option to make program always on top of other forms on/off
(+) Added options to download more recoveries
01/22/2014 - v1.0
(*) Fixed bug in GalaTab3 Kernel Download
(*) Changed GUI slightly, added section for "links" instead of including them under "tools"
(+) Added link to this support thread
01/20/2014 - v0.1a
First initial release

@emwno I tried to contact you in your twrp thread, but never got a response. If you want me to remove cwm & twrp from this program, or my server, please let me know and I will do so!
Sent from my iPhone using Tapatalk

Fantastic! Downloading..

Ok DEV i may need a spoon-full. Fired up the tool and scanned, it worked perfect, tab information showed-up and all buttons lit-up. Didn't try any recovery options cause i'm already rooted but i had been meaning to install galatab3. Clicking on "Get GT3 Kernel" didn't do anything and neither did clicking on "Gala Tab 3" (tools section) took me to the discussion thread but nothing else. Neither option downloaded the file, so is it something I'm doing wrong?
Downloading odin worked like a charm, i didn't try TWRP or CWM since I'm already rooted.
Reboot recovery and reboot system work. i haven't had a need to try any other functions (yet). Oh, one thing i found inconvenient is the tool is always-on-top.
I do believe if you intend for it to a tool for noobs, you do a separate tool for rooting and recovery only, sort of like a one or two click rooting with only one or buttons to click. As it is right now, there are too many options. And also you can really get in that noob mode and it would dawn on you to put in the instruction how to make the developer options show up in the first place LOL Just IMO DEV.

Thank you for all of your feedback @treetop777
When you click "Get GT3 Kernel," it should download the GalaTab3 Kernel right into the same directory as the program itself.
Once it downloads, if you then click the "Copy GT3," it will then copy the Kernel over to /sdcard/ path of the device. From there, you can reboot into recovery and install the zip file of GalaTab3 from the sdcard.
Please try that and let me know how it works for you. I will try to categorize everything better and lay it out easier with your feedback. Thank you
Sent from my iPhone using Tapatalk

foil said:
Thank you for all of your feedback @treetop777
When you click "Get GT3 Kernel," it should download the GalaTab3 Kernel right into the same directory as the program itself.
Once it downloads, if you then click the "Copy GT3," it will then copy the Kernel over to /sdcard/ path of the device. From there, you can reboot into recovery and install the zip file of GalaTab3 from the sdcard.
Please try that and let me know how it works for you. I will try to categorize everything better and lay it out easier with your feedback. Thank you
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
NP DEV. Will you put out an update? Cause for sure the version i have DO NOT download the Kernel and also, i don't see the "Copy GT3" you mentioned.
You know, now that i think of it, when i hover over the "Get GT3 Kernel" i get a message about the SD card. Maybe you meant that button to read "COPY GT3 Kernel" ?? If that's the case, then it would have to be moved to the tools section.
But first DEV, it has to download the Kernel which it's not doing right now. Unless I'm doing something wrong.

I'm sorry about the issue that you're having.. I am going to look into it in just a few minutes. I will release an update tonight for you.
Sent from my iPhone using Tapatalk

treetop777 said:
NP DEV. Will you put out an update? Cause for sure the version i have DO NOT download the Kernel and also, i don't see the "Copy GT3" you mentioned.
You know, now that i think of it, when i hover over the "Get GT3 Kernel" i get a message about the SD card. Maybe you meant that button to read "COPY GT3 Kernel" ?? If that's the case, then it would have to be moved to the tools section.
But first DEV, it has to download the Kernel which it's not doing right now. Unless I'm doing something wrong.
Click to expand...
Click to collapse
I have uploaded version 1.0 now, and have fixed the bug in the Kernel download method that I was using.
Please try the new version, and let me know if that fixes your problem(s)!
Once you click "Get GT3 Kernel," it will download the kernel zip, and place it into the current directory of the GalaxyTab3_Toolkit, then the button will rename itself to "Copy Kernel." Click that, and it will ask you if you'd like to transfer the kernel zip over to /sdcard/ on the tablet. Click yes, then once it finishes, click Reboot Recovery, and you will be able to install the kernel zip file from there.

Worked EXACTLY as expected! Downloaded GT3 then pushed it to the internal storage then rebooted into TWRP. After flashing GT3, rebooted into system and the tab is running smooth. No glitches, no problems. What more can i say - flawless!
It's nice to have all these procedures all in one place.
Thanks!

treetop777 said:
Worked EXACTLY as expected! Downloaded GT3 then pushed it to the internal storage then rebooted into TWRP. After flashing GT3, rebooted into system and the tab is running smooth. No glitches, no problems. What more can i say - flawless!
It's nice to have all these procedures all in one place.
Thanks!
Click to expand...
Click to collapse
Great! I am going to work on making everything a bit easier for everyone to understand, thanks to your input!
I'm glad everything worked for you
Sent from my SM-T310 using Tapatalk

Looks awesome going to give it a shot, lets see if this meets my needs.

Using it now but why no philz recovery?
Update....
Worked great thanks.
One small issue was having to put the device into download mode manually. I was getting an exception error about no root when I chose the reboot download button.
Once philz was installed, I used his root option and then installed supersu and Staricson busybox using smart install. Device is now rooted and I can start modding.
Thanks !
Small recomendation.. allow for the app to use or not use system proxy. Also, app should have an option to not always be on top.

CodeJACK said:
Using it now but why no philz recovery?
Update....
Worked great thanks.
One small issue was having to put the device into download mode manually. I was getting an exception error about no root when I chose the reboot download button.
Once philz was installed, I used his root option and then installed supersu and Staricson busybox using smart install. Device is now rooted and I can start modding.
Thanks !
Small recomendation.. allow for the app to use or not use system proxy. Also, app should have an option to not always be on top.
Click to expand...
Click to collapse
Well, I haven't had the chance to test Philz recovery out just yet, I only included the tools that I have personally tested.
I am going to add an option for all of the updated recoveries that support CM10-CM11! Also, I will add an option to allow it to not always be on-top, too!
I will look into the root-required Download Mode reboot, but it would always fail to reboot into Download Mode for me if I didn't run it as SU.. I'll see what I can do to fix it, because I know that it doesn't require root through a regular shell.
Thank you for your feedback!!
Sent from my SM-T310 using Tapatalk

duh... i was working on a toolkit :cyclops::cyclops: but anyways this looks awesome :fingers-crossed:

Nice all in one root package. Thanks a lot...
Sent from my SM-T310 using XDA Premium 4 mobile app

Does this toolkit also works with T311 (Tab3 8.0 3G)?
Gesendet von meinem SM-T311 mit Tapatalk 2

OllerLoewe said:
Does this toolkit also works with T311 (Tab3 8.0 3G)?
Gesendet von meinem SM-T311 mit Tapatalk 2
Click to expand...
Click to collapse
I don't have a T311 to test with, but once I get everything implemented that I want for the T310, I will try to add functions for the T311 for you!

Any love for the t315 4g version?

I've updated to version 1.1 guys, please check the changelog in the original post for more information!
@gx3k - no, I'm sorry, no support for T311 or T315 yet! I think everything is now good with the T310, so I will start working on the other two now!
@Phil3759 & @gr8nole - I added your recoveries to my project, and have hosted them on my server as well for a direct-download method. If this is a problem at all, please let me know and I will remove them asap! Thank you guys for all of your work

Superb!
Echoing what others have said, nice to see everything in one place, had my Tab rooted within ten minutes, thanks for the tool!

[Recovery][Unofficial] TWRP 3.0.2-C [r7plusf]

This recovery will work ONLY for the Snapdragon 615 version of Oppo R7 Plus!
Here is an update to my UNOFFICIAL TWRP 3.0.2
Everything works well, with one caveat: It will reboot as soon as the display times out. The workaround is simple: Go to settings and disable Screen Timeout.
The -C revision is just to remind me that the recovery it is build on CyanogenMod.
If you don't need encryption and don't care about wrong date/time in your backups, then the official twrp will be all you need.
{
"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"
}
Full Source: Github.​Old stuff:
My goal with this UNOFFICIAL twrp recovery is to enable encryption on Oppo R7Plus-f(Snapdragon) version.
Tested with AICP on MarshMallow. Full encryption support.
All hard work was done by the TWRP Team and the R7 kernel gurus at CyanogenMod.
I just made a few additions and changed the official TWRP kernel to the CM kernel using the AICP build system.
To get your Oppo R7Plusf encrypted, there are a few points you must follow.
Note1: This wil not work with ColorOS. The ROM must support encryption. ColorOS does not!
Note2: You will LOOSE ALL DATA if you choose to encrypt your R7Plusf.
Here is a small howto:
1. Boot to bootloader and flash TWRP-3.0.2.u
2. Boot to recovery
3. Choose A or B to backup your data
....A: Backup Data and copy it to PC (Internal Storage - TWRP/BACKUPS/xxxxxxxx/BackupName)
....B: Backup Data to the Micro SDcard (Now, be careful not to format the Micro SD)
4. Wipe -> Format Data (type YES and tap the OK/Enter button)
....This command is slow, have patience!
5. Reboot to android. The install wizard should show - be sure to create a PIN or Pattern kode during the setup.
6. Charge the phone to 90-100%
7. Open Settings/Security and -> Encrypt phone
8. Follow instructions
Click to expand...
Click to collapse
Now the device will reboot a few times and finally it will boot to the login screen and ask for your pin code.
All this will take time, have patience.
On my AICP ROM it sometimes "hang" when Finishing boot and make some tick sounds. Turning the screen off and on a few times will make it boot to the login and you can enter the PIN or Pattern. It will boot again and quickly get into your Android system.
Once booted to Android, everything is smooth and there are no more issues (at least not encryption related )
This is an issue with my AICP ROM only, CM13 start without issues.

...reserved...
Please share your experience here, if you choose to check out encryption on the R7+. Thanks.

Major Props ! Great job and you actually fulfilled a request of mine ! Thanks

I have followed the steps and @ step 5 I wasnt asked to enter any PIN , Im on CM13 latest nighly on october 31 and twrp 3.0.2 , any advise Please ?
is the backup step A or B optional or a must ?

midterm_2003 said:
I have followed the steps and @ step 5 I wasnt asked to enter any PIN , Im on CM13 latest nighly on october 31 and twrp 3.0.2 , any advise Please ?
is the backup step A or B optional or a must ?
Click to expand...
Click to collapse
It is 6 months since I tried. At that time I was asked for the pin. Don't know if that is different for the latest cm.
Note that this recovery is not perfect. It handles encryption well, but has a few issues. To avoid these, you can flash the official twrp from http://twrp.me, but don't format data - it will break encryption.
Maybe CyanogenMod recovery is fully functional now, then it might be a better choice. @maniac103 ?
Yes backup is optional. It is always your choice.

It was my mistake I selected wipe instead of format , it works now ! :good: do you know what other issues this recovery have as I want to keep
Thanks

Small update - read OP.

teemo said:
Small update - read OP.
Click to expand...
Click to collapse
I have recently done a complete new TWRP from scratch including:
- LineageOS kernel 3.10.104
- decryption using 7.1.1 LineageOS blobs
- included misc for 7.1.1
- overlay graphics support
- modem binary flashing support (no zip file required) just select non-hlos.bin from Oppo's stock ROM
- proper IMEI Partition Backup
- flashimage support in TWRP (just like fastboot)
- latest TWRP 3.0.3-0
If you would like to build one or want me to provide you a build let me know.
I pushed the repo here: https://github.com/Celoxocis/android_device_oppo_r7plusf
Of course I made it for the R7S but our two devices are almost identical so I made the necessary changes to create a R7Plus repo.
Let me know what you think.

celoxocis said:
I have recently done a complete new TWRP from scratch including:
- LineageOS kernel 3.10.104
- decryption using 7.1.1 LineageOS blobs
- included misc for 7.1.1
- overlay graphics support
- modem binary flashing support (no zip file required) just select non-hlos.bin from Oppo's stock ROM
- proper IMEI Partition Backup
- flashimage support in TWRP (just like fastboot)
- latest TWRP 3.0.3-0
If you would like to build one or want me to provide you a build let me know.
I pushed the repo here: https://github.com/Celoxocis/android_device_oppo_r7plusf
Of course I made it for the R7S but our two devices are almost identical so I made the necessary changes to create a R7Plus repo.
Let me know what you think.
Click to expand...
Click to collapse
That is simply brilliant
I just started syncing down LineageOS from scratch again. You say decryption is from LOS 14.1, but I assume you build twrp on cm-13.0.
Overlay: I have always been puzzled over the slow graphics on twrp. My old 2012 HTC is super smooth in the same recovery. I saw you discuss it somewhere, maybe on IRC you mentioned one drawback by running on overlay, but don't remember what it was ?
Modem flashing: That will be handy for testing stuff.
Proper IMEI, wasn't aware it was broken?
Flash image, another great feature, although easily done from Android as well. I have been a few times in recovery, wanting to just flash an image.
Big thanks for taking time to update plusf. I will check it out and return
EDIT: Built with following changes:
- All CyanogenMod repos changed to LineageOS in localmanifest
- kernel and dt replaced with my latest, as the supplied boots into fastboot
Will test the next few days.
Huge thanks @celoxocis

teemo said:
That is simply brilliant
I just started syncing down LineageOS from scratch again. You say decryption is from LOS 14.1, but I assume you build twrp on cm-13.0.
Overlay: I have always been puzzled over the slow graphics on twrp. My old 2012 HTC is super smooth in the same recovery. I saw you discuss it somewhere, maybe on IRC you mentioned one drawback by running on overlay, but don't remember what it was ?
Modem flashing: That will be handy for testing stuff.
Proper IMEI, wasn't aware it was broken?
Flash image, another great feature, although easily done from Android as well. I have been a few times in recovery, wanting to just flash an image.
Big thanks for taking time to update plusf. I will check it out and return
EDIT: Built with following changes:
- All CyanogenMod repos changed to LineageOS in localmanifest
- kernel and dt replaced with my latest, as the supplied boots into fastboot
Will test the next few days.
Huge thanks @celoxocis
Click to expand...
Click to collapse
Just the build tree is cm-13.0 but as you can see from the manifest everything that is required is from TWRP's Android 7.1. I.
I didn't want to test the build on an bleeding edge LineageOS 14.1 tree. As I wasn't sure about if it works and repo syncing the sources takes time.
Funny they boot into fastboot?
Kernel + DT.IMG were LineageOS 14.1 (7.1.1).
To my knowledge the kernel + DT.img are identical for the R7Plus,/R7S. The DT.img contains 15022 + 15018 as far as I know.
The only downside when using graphics overlay was that some users reported screenshot In recovery would not work. While I had one user report it works.

celoxocis said:
Just the build tree is cm-13.0 but as you can see from the manifest everything that is required is from TWRP's Android 7.1. I.
I didn't want to test the build on an bleeding edge LineageOS 14.1 tree. As I wasn't sure about if it works and repo syncing the sources takes time.
Funny they boot into fastboot?
Kernel + DT.IMG were LineageOS 14.1 (7.1.1).
To my knowledge the kernel + DT.img are identical for the R7Plus,/R7S. The DT.img contains 15022 + 15018 as far as I know.
The only downside when using graphics overlay was that some users reported screenshot In recovery would not work. While I had one user report it works.
Click to expand...
Click to collapse
Actually it didn't boot into the bootloader (fastboot screen), it was stuck on the Oppo screen. Did not respond to adb, but gave correct answer from 'fastboot devices'. Didn't check other fastboot commands though.
Screenshots works well

teemo said:
Actually it didn't boot into the bootloader (fastboot screen), it was stuck on the Oppo screen. Did not respond to adb, but gave correct answer from 'fastboot devices'. Didn't check other fastboot commands though.
Screenshots works well
Click to expand...
Click to collapse
I feel video overlay graphics in twrp recovery feels smoother than adf graphics.
Unfortunately I can't compare them side by side.
What do you think which feels smoother?

celoxocis said:
I feel video overlay graphics in twrp recovery feels smoother than adf graphics.
Unfortunately I can't compare them side by side.
What do you think which feels smoother?
Click to expand...
Click to collapse
For the filemanager, I feel it is a little smoother than before. Might be my imagination though.
It is very picky about how you scroll with your finger, sometimes mistaking it for a "tap". But old adf did the same.
I can say definitely, that the slider is much much better now. Not supersmooth as my HTC, but good enough for a recovery tool. Don't see any downsides yet.
EDIT: Funny, the slider animation is the same as on my 3.0.2-C. I made a video and compared. It's the same. I may have seen the slower animations on an older recovery, I am sure it was much more choppy before.

Is there any chance that this would be updated.?

kishd said:
Is there any chance that this would be updated.?
Click to expand...
Click to collapse
Yes I will update it. Just don't know when yet.
It's a long weekend here. So I might do it tomorrow.
I will post once updated.

x
Help please...I'm stucked at the unlock bootloader...
First to say I have root but I got root only with kingroot app...is this a problem?
I have installed the color os r7plusfEX_11_151225 (didn't do full wype data, installed over the latest color os version), but with the oppo tools it didn't do nothing so I got root with kingroot.
I can go into fastboot but when I type "fastboot oem unlock" it always say this:
"C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.053s"
where I was wrong or where I miss something?
thanks for replies I really will to intall a custom rom on this phone........

celoxocis said:
Yes I will update it. Just don't know when yet.
It's a long weekend here. So I might do it tomorrow.
I will post once updated.
Click to expand...
Click to collapse
I hate to be a nuisance, but have you had a chance to look at this?

kishd said:
I hate to be a nuisance, but have you had a chance to look at this?
Click to expand...
Click to collapse
Yes i decided not to bring another unofficial release.
There will be an update for TWRP for the entire R7 series.
It will be made official soon.

[ROM][UNOFFICIAL][6.0.1] CyanogenMod 13.0 for Elephone Trunk

This ROM is a genuine CM13 build from source for the Elephone Trunk. It's based on mdeejay's Ark Benefit code with modifications by @BlueFlame4 and @hisname. The source code is available on GitHub.
Working:
Phone
Mobile data in dual-sim configuration
Wifi
GPS
Bluetooth
Audio
Known Bugs:
Torch tile in the status bar is not available
Haptic feedback on soft buttons
XDA:DevDB Information
CM13 for Elephone Trunk, ROM for all devices (see above for details)
Contributors
ottmi, siljaer
Source Code: https://github.com/ottmi/android_device_elephone_trunk
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 20160902
Beta Release Date: 2016-09-02
Created 2016-06-07
Last Updated 2016-09-02

Changelog
20160902
First try to fix sdcard issues, will need more testing
Fix thermal-engine to actually start
Fix audio_effects.conf
Tweak auto-brightness
Enable OTA updates
Use Wileyfox Swift blobs for everything but camera
Update to latest CM13 source
20160816
Enable thermal-engine to fix overheating emergency shutdowns
Update kernel to latest MSM8916 to fix Quadrooter vulnerabilities
Re-enable AEC audio effects
Update to latest CM13 source
20160811
Revert changes to mixer_paths.xml and audio_effects.conf to fix echo problems
Update to latest CM13 source
20160803
Update to latest CM13 source to fix surfaceflinger crashes
20160803
Tweak GPS settings to obtain faster locks
Enable input event for headphone jack
Use ACDB libraries from Wileyfox swift, fix some ACDB-related settings
Update to latest CM13 source
20160722
Incorporate @siljaer's modifications to mixer_paths.xml to fix echoes and low volume audio recordings
Pull in additional permissions to reflect actual hardware of the phone (light & proximity sensor)
Change screen density to 300dpi
Backport LZ4 compression from Linux 3.12 for use in ZRAM
Try to fix Torch problems by restarting media service after full boot
Update to latest CM13 source
20160708
Fix wpa_supplicant crashes
Update to latest CM13 source
20160706
Switch to generic CyanogenMod MSM8916 kernel
Use Wileyfox Swift kernel configuration as template
Increase partition sizes of system and data to 1.8GB and 12GB
Update to latest CM13 source
20160630
Fix bug in libstagefright properly
Fix sensor glue code to only show actually existing sensors
Fix device permissions
Use own key to sign code instead of testkeys
Set selinux to enforce
Update to latest CM13 source
20160616
Fix mediaserver crashes to a bug in libstagefright (roll back to commit 8f270dc)
Use Adreno binary blobs from Wileyfox Swift (which are more complete)
Update to latest CM13 source
20160614
Enabling of Qualcomm Fluence as suggested by @Bingo Bronson
Backport of the F2FS driver from Linux 3.12
Enabling of LTE as preferred network on 2nd SIM card as well
Some changes to the auto brightness thresholds
Update to latest CM13 source
20160611
Enable haptic feedback on soft keys
Change default device name for wifi direct and hotspot to "Trunk" (not Benefit!)
Update to latest CM13 source
20160606
Use mixer_paths.xml file by Wenderer7755 to fix low volume on mic recordings
Update to latest CM13 source

Flashing Instructions
You will have to disable the bootloader lock first:
Enable developer options in Android by tapping the Build version in Settings > About 7 times
Check "Enable OEM unlock"
Next you will have to boot into TWRP, use @hisname's TWRP:
http://forum.xda-developers.com/gen...410-5-inch-t3177753/post66208281#post66208281
You can boot TWRP either by flashing it to the recovery partition or by booting it directly via fastboot if you don't want to overwrite the stock recovery, i.e.:
Code:
fastboot flash recovery twrp-05042016.img
or
Code:
fastboot boot twrp-05042016.img
Make a backup of the stock ROM and then do a factory reset. You can then flash the CM13 image from sdcard or via adb sideload.

Installation Xposed Rom Ottmi
Installation Xposed Rom Ottmi
 @ottmi
Which version of Xposed install since I can not use: - cm-13.0-20160515-UNOFFICIAL-trunk - trunk1-TWRP-3.0.2.x- Xposed-v85-sdk23-arm64 can give me advice and thank you for your work

josoft86 said:
Installation Xposed Rom Ottmi
@ottmi
Which version of Xposed install since I can not use: - cm-13.0-20160515-UNOFFICIAL-trunk - trunk1-TWRP-3.0.2.x- Xposed-v85-sdk23-arm64 can give me advice and thank you for your work
Click to expand...
Click to collapse
Sorry, I don't use Xposed, so I don't have any idea. arm64 and sdk23 sounds about right, though. What's the problem?

josoft86 said:
I can not use: - cm-13.0-20160515-UNOFFICIAL-trunk - trunk1-TWRP-3.0.2.x- Xposed-v85-sdk23-arm64
ottmi said:
Sorry, I don't use Xposed, so I don't have any idea. arm64 and sdk23 sounds about right, though. What's the problem?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
v84 works (used it for at least 3 weeks), updated to v85 yesterday: also working.
edit: Updated to 20160606 build, framework still active, all good.
Since no further details were provided, it would be nice if josoft86 could describe what happens during the "attempted" installation.

ottmi said:
20160606
Use mixer_paths.xml file by Wenderer7755 to fix low volume on mic recordings
Update to latest CM13 source
Click to expand...
Click to collapse
Great, so many thanks, but, the link?

marcachas said:
Great, so many thanks, but, the link?
Click to expand...
Click to collapse
You have to use the download tab on the top of the thread since this is a DevDB supported thread...
http://forum.xda-developers.com/devdb/project/?id=15607#downloads
Example:
{
"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"
}
Visit xda with your browser if you are currently on xda labs or some kind of forum app.

Bingo Bronson said:
You have to use the download tab on the top of the thread since this is a DevDB supported thread...
http://forum.xda-developers.com/devdb/project/?id=15607#downloads
Example:
Visit xda with your browser if you are currently on xda labs or some kind of forum app.
Click to expand...
Click to collapse
Oh, thanks, you are the best, this rom is so table and smooth, your job is awesome, a hug.

Thank you. I decided to buy the Elephone Trunk because I was interested in a economic phone that could 'easily' be upgraded with non stock ROM (preferably CM 13).
I have gone through the previous conversation and I must admit I'm impressed with your progress so far. Congratulations and a big thank you!
I will definitely flash your build as soon as I receive the phone.
Enviado desde mi Nexus 5 mediante Tapatalk

Great job!
Great job and super useful guide @ottmi.
Thank you!
I am currently running your previous release (cm-13.0-20160515-UNOFFICIAL-trunk) and have no issues to report at all!
In order to upgrade to the latest one, do I need to delete everything and start from scratch or is there an upgrade process?
Thank you for the excellent work.
Kind regards.
P.S. I have downloaded and installed GAPPS (Google Apps) from CM portal and found that the "nano" package has everything I need, while anything larger (e.g. full package) can't find enough space on system partition - no big deal though.

kbezerianos said:
In order to upgrade to the latest one, do I need to delete everything and start from scratch or is there an upgrade process?
[...] and found that the "nano" package has everything I need, while anything larger (e.g. full package) can't find enough space on system partition - no big deal though.
Click to expand...
Click to collapse
Dirty flash is enough, no need to clean everything. Just install the new build, wipe the caches afterwards like it is suggested by TWRP recovery.
Some of your apps may have a survival script, others need to be reflashed (this is just the case for special tools, like Xposed, etc.)
Nano Gapps is a smart choice either way, because all the pre-installed Gapps will be outdated soon enough, so why bother to install a "huge" Gapps pack...
I use microG and have roughly 260 MB left on the system partition.

Bingo Bronson said:
v84 works (used it for at least 3 weeks), updated to v85 yesterday: also working.
edit: Updated to 20160606 build, framework still active, all good.
Since no further details were provided, it would be nice if josoft86 could describe what happens during the "attempted" installation.
Click to expand...
Click to collapse
Evidently use TWRP 3.0.2.0 not compatible but I works fine with other rom CM13 who have tried. I will try to install TWRP-05042016 to check. Thank you

josoft86 said:
Evidently use TWRP 3.0.2.0 not compatible but I works fine with other rom CM13 who have tried. I will try to install TWRP-05042016 to check. Thank you
Click to expand...
Click to collapse
But, but... I'm also on 3.0.2-0 and the Xposed zips & ROMs, for example, are processed without error, Aroma installer is also supported...
Who compiled / ported your TWRP version? I used only @hisname releases and they never let me down. ?
ottmi said:
If you're using a TWRP image that has been built for the Ark Benefit, it won't work with my ROM as TWRP will report the device as Ark Benefit and not as Elephone Trunk.
Click to expand...
Click to collapse
I didn't even consider that possibility, since it has been mentioned numerous times in the old thread, ignorance is bliss (on my side), ahem...
I'm out of "thanks" to give, so I'll "upvote for awareness" later...

josoft86 said:
Evidently use TWRP 3.0.2.0 not compatible but I works fine with other rom CM13 who have tried. I will try to install TWRP-05042016 to check. Thank you
Click to expand...
Click to collapse
If you're using a TWRP image that has been built for the Ark Benefit, it won't work with my ROM as TWRP will report the device as Ark Benefit and not as Elephone Trunk.

ottmi said:
You can boot TWRP either by flashing it to the recovery partition or by booting it directly via fastboot if you don't want to overwrite the stock recovery, i.e.:
Code:
fastboot flash boot twrp-05042016.img
or
Code:
fastboot boot twrp-05042016.img
Make a backup of the stock ROM and then do a factory reset. You can then flash the CM13 image from sdcard or via adb sideload.
Click to expand...
Click to collapse
Sorry, but I think there is an error. If you want to flash a recovery the code would be "flash recovery" instead of "flash boot".
Code:
fastboot flash recovery twrp-05042016.img
Appart from that (and the silly minute I've suffered because I did not understand at first what had gone wrong) everything is perfect :good:
Thank you, great job!

One question, have any of you got to use a SD memory card as internal memory?
I have tried to do so but it gives me an error message when moving apps and pictures, as if there was not enough space (when the fact is that there is more than enough by far - 32 Gb).
Thanks in advance
Enviado desde mi Nexus 5 mediante Tapatalk

21prods said:
Sorry, but I think there is an error. If you want to flash a recovery the code would be "flash recovery" instead of "flash boot".
Code:
fastboot flash recovery twrp-05042016.img
Appart from that (and the silly minute I've suffered because I did not understand at first what had gone wrong) everything is perfect :good:
Thank you, great job!
Click to expand...
Click to collapse
Bummer. You're right, I've fixed the instructions accordingly. Sorry for that!

21prods said:
One question, have any of you got to use a SD memory card as internal memory?
I have tried to do so but it gives me an error message when moving apps and pictures, as if there was not enough space (when the fact is that there is more than enough by far - 32 Gb).
Thanks in advance
Click to expand...
Click to collapse
I'm using a 32GB microsdhc to store music and pictures, no issues at all. I've also used 64GB mirosdxc without problems. I've never tried moving apps though.. How does it show in Settings->Storage & USB?

Yes, that's it. There you have the possibility of formatting the SD card to use it as (more) internal memory.
Enviado desde mi Nexus 5 mediante Tapatalk

[Recovery] Official TWRP for the OnePlus 3 & 3T

Team Win Recovery Project 3.0.4-1 (unreleased)
Notice #1: Please don't wipe your data partition if TWRP cannot decrypt it. Instead, make an effort to gather logs to help solve the issue!
Notice #2: Themes from 3.0.0 to 3.0.3 are incompatible with 3.0.4. Sorry! (small theme engine changes regarding backlight control)
This is a unified build for both the OnePlus 3 and the OnePlus 3T!
WARNING: The OnePlus 3 & 3T stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!
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.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/oneplusthree.html
Use 3.0.4-1 for now, rather than the builds on twrp.me until an official release happens. You will have problems with 3.0.3 on Nougat!
For now, please download the build from:
https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-1-oneplus3.img
Officially 3.0.4 has not been released yet, but it has critical fixes for this device on Nougat, so please be patient.
There is a download link there, as well as instructions on how to flash it.
You can find up to date fastboot & adb binaries here!
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
Extract/install adb & fastboot to your computer.
{
"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"
}
Download TWRP for OnePlus 3 & 3T (oneplus3).
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
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.
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Up] + [Power] buttons while your device reboots or boots from power off.
Once you're in fastboot mode, you need to unlock your bootloader. To do this, run the command:
fastboot oem unlock
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Once your bootloader is unlocked, you're ready to flash TWRP. To do this, run the command (replacing twrp.img with the actual image name):
fastboot flash recovery twrp.img
Once the image is flashed, you should use your volume keys to navigate to RECOVERY and the press the power key to select it.
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 the next step 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.
If your device asks for a password to mount internal storage, and your password doesn't work or you haven't set one, see below under known issues for a fix!
If you want to be rooted with SuperSU:
Download the latest SuperSU Stable by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
---or (not both) ---
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up. (SuperSU will reboot you a few times)
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TWRP
To update TWRP, simply download the new twrp.img on your phone, then boot into your current TWRP and flash it.
To flash a twrp.img, navigate to [Install] -> [Flash Image] -> select your twrp.img -> [x] Recovery -> Flash!
After that, just use [Reboot] -> [Recovery] to reboot into the updated TWRP.
CHANGES
v3.0.4-1 (build.nethunter.com) - Fix crash when trying to reboot that resulted in TWRP restarting, CAF kernel updates
v3.0.4-0 (build.nethunter.com) - Capability restoration for Nougat, F2FS backport support, EXT4 decryption support
v3.0.3-0 (twrp.me) - Same as 3.0.3-1-rc2. In sync with the OnePlus 3T device tree (3.0.3-1).
v3.0.3-1-rc2 (build.nethunter.com) - Redo the device tree for OOS 4.0, including dynamic encryption support (pull libs from ROM)
FEATURES
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
Allows OnePlus full OTA flashing
KNOWN ISSUES
F2FS takes a long time to boot, see below.
If your device is taking more than 10 minutes to boot, you probably have a misc flag enabled that disables passing cmdline, see below.
Reboot buttons don't work in TWRP (restarts TWRP) - disable Ask to install TWRP App on settings page, fix on the way. - fixed in 3.0.4-1
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Personally, I'd have tried this after 15 minutes.
WHY DOES F2FS MAKE TWRP SO SLOW?
When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!
I suggest switching your data partition to ext4 - all the f2fs hype is merely from benchmarks that don't actually represent real world use (ie. you're not writing thousands of files per second)
For someone who doesn't do lots of write access to their data partition, ext4 can actually be advantageous (it has faster access times and reads!)
WHY WON'T MY DATA DECRYPT / WHY IS MY PASSWORD INVALID IN TWRP?
In order for encryption to work in TWRP, it must pull the encryption libraries from your current ROM. It does this during TWRP boot logo. If you have no ROM installed, then it will fall back to the default OxygenOS 4.0.2 encryption libraries included in the TWRP image.
The crypto daemon in recovery will not be able to decrypt unless the version of the encryption key matches the version of the libraries. This is an unusual restriction that was added by OnePlus.
You can usually fix this by simply booting into your ROM and changing your boot up password. You can change it back or remove it if you want immediately after. This will generate a new crypto key which should be compatible when you next enter TWRP.
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
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-7.1)
Device tree: https://github.com/TeamWin/android_device_oneplus_oneplus3 (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_oneplus_msm8996 (twrp-7.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 for the OnePlus 3 & 3T, Tool/Utility for the OnePlus 3
Contributors
jcadduono, Team Win
Source Code: https://github.com/jcadduono/android_device_oneplus_oneplus3
Version Information
Status: Stable
Current Stable Version: 3.0.4-1
Stable Release Date: 2017-01-21
Created 2017-01-23
Last Updated 2017-02-07

Reserved
ONEPLUS FULL OTA ZIPS
You can flash these zips in TWRP to update your device or save yourself from a broken or soft-bricked state.
They are official zips distributed by OnePlus.
For the OnePlus 3 only:
OxygenOS 3.2.8: http://s3.amazonaws.com/oxygenos.on...6_OTA_017_all_1611182000_fbe1471194d64b3e.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...en_16_OTA_035_all_1612310359_e10cadfb2af7.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...16_OTA_039_all_1701140133_89fcc9baba94e4c.zip
OxygenOS 4.0.3: http://otafsc.h2os.com/patch/amazon...ygen_16_OTA_041_all_1702081756_0f1e56a75f.zip
For the OnePlus 3T only:
OxygenOS 3.5.3: https://s3.amazonaws.com/oxygenos.o...8_OTA_027_all_1611222319_884473ff95304c30.zip
OxygenOS 3.5.4: http://oxygenos.oneplus.net.s3.amaz...8_OTA_029_all_1612131737_17e7161d2b234949.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...ygen_28_OTA_037_all_1701041831_a2ba632ce9.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_039_all_1701140132_400a7.zip
OxygenOS 4.0.3: http://otafsc.h2os.com/patch/amazon...3TOxygen_28_OTA_041_all_1702081824_e3a712.zip
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.

jcadduono said:
Team Win Recovery Project 3.0.4-0 (unreleased)
Click to expand...
Click to collapse
Nice mate as always.
Pm: you might need yo check the format of the first post, everything is written 3 times. :laugh:

peshellas said:
Nice mate as always.
Pm: you might need yo check the format of the first post, everything is written 3 times. :laugh:
Click to expand...
Click to collapse
Never quote full op, this is spamming.
For 3 times same content, open xda in browser, it's xda app bug.

RohanAJoshi said:
Never quote full op, this is spamming.
For 3 times same content, open xda in browser, it's xda app bug.
Click to expand...
Click to collapse
You re Right mate, i know, i have been here since the very old days, I thought i had deleted ot, and continued, apparently not. Thanks for the tip, didn't know about the bug.

ext4 decrypted fine on OnePlus 3 OOS 4.0.2.

Is flashing twrp-data-fstype-swap-x.x.zip still necessary when switching between f2fs and ext4?
The instructions and the link are not stated in OP anymore.

fbf2201 said:
Is flashing twrp-data-fstype-swap-x.x.zip still necessary when switching between f2fs and ext4?
The instructions and the link are not stated in OP anymore.
Click to expand...
Click to collapse
Both EXT4 and F2FS should work out of the box now.
No flashing needed.

Hello and thanx for the hard job.
I wanted to try a clean install starting from stock, hoping to correct my issue with twrp black screen.
I need your help. Here is what I've done :
- Restore stock with the unbrick tool
- Update to Nougat 7.0 and OOS4.0.2 via oneplus update
- Unlock bootloader
- Flash twrp 3.0.4-0 via fastboot
- Flash no-verity-opt-encrypt-5.0
- Flash RR rom
- Wipe data and Dalvik
- Reboot.
This is the first time it made it to me. It ask me a password when it boot. I saw a lot of post about that, but I can't understand how to solve it.
Can someone help me please ? My phone is OP3T

Hello, thanks for the super-useful tool. TWRP has been my goto recovery for as long as I have been rooting (days of htc-hd2). I am experiencing the following issues with v3.0.2-1 (all my checkpoint backups are in that version).
* Device = op3
* If it helps, this was a OOS 4.0.1 backup. I was trying to restore it because of a 4.0.2 upgrade failure attempt
* restore hangs at 100% after the backup is complete.
* After waiting for nearly 15 mins, I used the power down to restart the phone - i had lost recovery
* tried to re-install recovery. but when twrp boots - it doesn't get to main menu
* Oddly enough op recovery installs and boots into fine. Which is what I am on.
I am currently on stock recovery without root unable to restore backup ups in twrp and in titanium backup
any thoughts?

Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?

ScratMan38 said:
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
Click to expand...
Click to collapse
Its a unified version

ScratMan38 said:
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
Click to expand...
Click to collapse
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.

cultofluna said:
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
Click to expand...
Click to collapse
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything

cultofluna said:
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
Click to expand...
Click to collapse
it's unified. even if it says op3 it will work for the 3t. read the op. a lot of 3t stuff baked in. works fine. only issue now is the black screen with LED light when booting into recovery. at least for me

Renosh said:
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
Click to expand...
Click to collapse
Thanks your reply was really helpful:laugh:

the 3.0.4.0 is recommend version or have some problem must need? for now i'm use 3.0.3.1 is good with f2fs data partition, OS version is RR-N-v5.8.0-20170117-oneplus3t-Official, i want to dirty flash update to RR-N-v5.8.0-20170122-oneplus3t-Official, i need update TWRP to 3.0.4.0 first? or i can keep use 3.0.3.1?

Renosh said:
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
Click to expand...
Click to collapse
Abaddon said:
it's unified. even if it says op3 it will work for the 3t. read the op. a lot of 3t stuff baked in. works fine. only issue now is the black screen with LED light when booting into recovery. at least for me
Click to expand...
Click to collapse
There was two links in the OP, one for 3.0.3-1 mentioning "unified", and one for 3.0.4 with only "oneplus3".
As I knew the dev was working on both version and still supplies 3.0.3-1 test releases in Op3T thread that were newer than the 3.0.4 he built ; and as the changelog did not mention the unification for 3.0.4, for sure, OP was not clear at all.

Is this 3.0.3.x or 3.0.4.0 backward compatible with Marshmallow ROMs?

chancex said:
the 3.0.4.0 is recommend version or have some problem must need? for now i'm use 3.0.3.1 is good with f2fs data partition, OS version is RR-N-v5.8.0-20170117-oneplus3t-Official, i want to dirty flash update to RR-N-v5.8.0-20170122-oneplus3t-Official, i need update TWRP to 3.0.4.0 first? or i can keep use 3.0.3.1?
Click to expand...
Click to collapse
You want to update a custom rom which by definition has no issue with dm-integrity (only present in stock boot image), so if you don't have any issue keep your recovery.
It seems though that latest version has a minimized risk of issues with f2fs so why not updating it?
cultofluna said:
Thanks your reply was really helpful[emoji23]
Click to expand...
Click to collapse
He was right, the thread's title says clearly 3 and 3T.