Database Info

[RECOVERY][TWRP 3.3.1][For all Quark][Moto Maxx/Turbo and Droid Turbo]

Team Win Recovery Project, or TWRP 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.
How it looks :
{
"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 must work on all devices model quark (XT1250 and XT1254) or quark_umts (XT1225) * custom ROM may display only quark
To know you device model just open the app Terminal Emulator for Android and see the quark after the @ like below.
Main download folder
Mirror download folder
The folder contains the Mod TWRP version base on the latest official with proper support to all android versions (The one from TWRP site doesn't have the proper support For Nougat, Oreo or newer OS's, I tryed to push the changes so the one from they site can be updated they did not answer me so I give it up), the mod other than having the proper support for all OS that prevent bug as the "Bootloop to TWRP after a Factory Reset" it has extra backup option (Radio/Modem, boot logo etc), NTFS support for USB-OTG devices, all possible TWRP languages, full encryption support (For Nougat and earlier, Oreo and up encryption is not suported) and etc improves...
All the extras featuring can be seen in the Changelog click here
Big thanks:
A big thank for those that donating to thanks for my work on TWRP.
@ChazzMatt for his donation, and his help on many other threads of Moto Maxx on XDA.
Renan R. R. for his donation
And all the other users that I contribute.
On the developer side, thanks to:
@Dees_Troy for his work on TWRP, for the tutorial and help to bring the official support...
@Skrilax_CZ for his hard work on building the first stable CM to this device
@Aadi for a tutorial.
@respider for his original work on TWRP for quark.
Developer donation link:
To donate via paypal click here
No other donation option is available.
XDA:DevDB Information
TWRP For all Quark(Moto Maxx/Turbo and Droid Turbo)
Contributors
fgl27
Source :
Android :
omnirom M source
LineageOS source
Device :
Device tree for omnirom source
Device tree for LineageOS base source
Kernel tree for LineageOS source
TWRP Version: 3.3.1
Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2015-08-16
Last Updated Check changelog (click here)
I use many tutorial to make this TWRP, here some to help those who want to do the same.
tags: how to port TWRP recovery, how to compile TWRP recovery, how to make TWRP recovery.
http://forum.xda-developers.com/showthread.php?t=1943625
http://forum.xda-developers.com/showthread.php?t=2294800
http://wiki.cyanogenmod.org/w/Build_for_quark#Build_CyanogenMod_and_ClockworkMod_Recovery
http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
https://source.android.com/source/building.html
https://source.android.com/source/building-running.html
https://source.android.com/source/initializing.html
http://review.cyanogenmod.org/#/c/89474/1/recovery.te

Check Changelog click here
How to install it.
Using Fastboot:
Download mfastboot
The fastboot I share is need replace fastboot with mfastboot in the commands below...
Copy the file you download form OP to the folder of fastboot and use the command in the bootloader screen
Code:
fastboot flash recovery recovery_name.img
! replace recovery_name with the name of the file, example:
Code:
fastboot flash recovery twrp-3.0.2-0-quark.img
Via app Flashify (for root users)
If you have root, try Flashify is really simple.
Install the app, download the recovery to the phone internal memory, open the app, chose recovery image, chose from file, confirm and flash, after you will go straight to the new recovery.
Via TWRP:
Yes TWRP can flash images recovery and boot image.
- install
- images... (is in the bottom right of the screen)
- select the image and image type (boot or recovery)
- swipe
- reboot to test, to recovery if flash a recovery or to system if is a boot...
...............................................................................
keep system read only?
This will be asked in the first time you boot to recovery after flash the recovery, if you not accepts it TWRP may be replace by the previously recovery of your device, but read way...
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.
..............................................................................
Note about restore from Stock 5.x.x to 4.4.4 and vice versa:
The format of data partition is different, in 4.4.4 is ext4 and 5.x.x is f2fs.
I have restore more then 100 times in my test, in some i end-up in a "bad/bug ROM" and it happens when flash 4.4.4 over 5.0.2 or vice versa, in the most bad one the device lost response of the touch screen even in the recovery, the bug was simply resolved by restoring to stock via fastboot using files from a stock XML rom. In others bug's android boot after boot i try to unlock to use and it reset, and stay in that loop, boot try to unlock reset, i try to wipe everything but system and did not work, in all those case partition format of data was wrong.
TWRP will backup the partition exactly how it is, If the backup is EXT4 and the Data partition of the device is f2fs TWRP will restore the data and will not change the format.
That may cause a problem, so when restoring to a different OS version advanced wipe the partition and change the format.
To do that click Wipe>advanced Wipe> select Data> click on Repair or change File System>change File System>
For Kitkat android 4.4.4 choose EXT4
For lollipop android 5.x.x choose F2FS
Swipe to change
Now restore.
But be aware that the data partition is were internal memory is, so if you change the file system you will loose all the files in internal memory
The wipe of internal memory doesn't happening if you only wipe data partition without change file system.
This will not affect custom ROM, but i recommend to use f2fs.
.....................................................................................
Note about encrypt
Test done in Nougat in the link below
Last Nougat test
Test done in Lollipop below
TWRP supports backup a encrypted system, but i only test this on lollipop stock ROM.
This is a simple description how to encrypt backup and restore the encrypted system.
Stock ROM
You can only encrypt if you have stock recovery and no modification to yours ROM, that means no root or rooted app like xposed modules etc, so if you have uninstall everything and do a full un-root.
To encrypt go to setting>secure>encryption the process take a while...
If you already have stock encrypted ROM you can flash TWRP and make a backup of it.
To remove the encryption you need to flash back the stock recovery and do a factory reset in Settings>Backup & Reset>Factory Reset
Factory Reset will deleted all the files of the device! so make a copy of important data...
Wiping all the partition in TWRP will not remove the encryption.
After the device finish the factory reset all the data of you phone will be deleted and the encryption will be gone.
Now you can flash back TWRP again and have fun...
If you need to restore that encrypted backup you can but after it finish restoring you will see that it is un-encrypted.
Custom ROM
I tested encrypt on custom Marshmallow AOSP base ROM (all the CM's), it is not need any recovery the only thing that is need to encrypt is that the encryption block of data be clean before encrypt.
Cleaning the encryption block of data
TWRP can't clean that so if the user encrypt the device the only way of clean that is by erasing the data via fastboot:
Code:
mfastboot erase userdata
The down side of it is that the partition will be erased lost every file of data and internal memory + when the system boot the data partition will be formatted as EXT4 that have a small performance lost over F2FS, to have it back to F2FS is need to give the command then start the OS, after the device finish boot and optimized it will format the partition and is need to go back to recovery and format the data as F2FS, going on wipe > advanced > select data > "repair change..." >change file sys> F2FS... then boot to the device and use it...
Note about official TWRP, USB driver via USB-OTG work, but your driver need to be formatted as FAT32(small drivers) or exFAT (big drivers), on the Mod version I have update the NTFS support and it now works
...........................................................
Collection of "Special_flash_zip" to go with the Mod TWRP
As some things are not directly attainable through TWRP menus, but they can be achieved via extra zips...
Clean_modem_status.zip
Logo_Flasher.zip
Modem_Flasher.zip
Clean_modem_status.zip
as the name implies this will erase the modem status partition, and erase any bad modem status, this can help in situations were the users is with some radio problem, one most famous on Quark is when user can get a GPS lock...
I test the GPS after flashing this and it works... (I did not had a GPS problem, but will test after I get one...)
Logo_Flasher.zip
This is a zip that can flash logo.bin via TWRP, is need of the user to have the logo.bin then place it inside of the root of the zip, then flash it over TWR.
Modem_Flasher.zip,
This is a zip made to flash the Radio.img + Clean modem status, thus achieving the update of Radio and clean any bad old radio status.
This zip is empty need the user to add the files on the future I will make a zip with the radio image inside... the below explain how to put the files inside.
As on Quark the radio.img is complex image that can't be flash via TWRP it is need to have a special zip, this zip contains the content of radio image after the user have flash it via fastboot, then for that I made this tutorial in how to use the zip, see the below hide...
Tutorial how to make this zip to work...
This zip must be used with a full backup of stock Modem image that can be achieve via app using apk called partition backup or via ADB
1# APP process... config the app Click on the tool, then in backup formats section, mark only Raw partition image
The partitions name to backup are
modem
mdm1m9kefs3
the file must be in sd/Partitionsbackups, the file names need to be just like describe below
before you put they on the zip so rename the files according the below...
modem.img
mdm1m9kefs3.img
make no modifications to the files, and place it on the root of this zip
The just flash the zip via TWRP
#############
2# ADB process, you must have SuperSu from Chainfire installed before making this, CM root will not work.
use the commands "adb devices" to check if the device is connected it will show the device serial number if it is...
then do the next two lines
Code:
adb shell
su
* after command "su" press enter 3 or more times... until the cmd displays
[email protected]:/ #
then... do the next 4 lines
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/modem.img
dd if=/dev/block/mmcblk0p32 of=/sdcard/mdm1m9kefs3.img
the files will be on the internal memory, the file names need to be just like describe below before you put they on the zip
modem.img
mdm1m9kefs3.img
make no modifications to the files or to the file name, and place it on the root of this zip
The just flash the zip via TWRP
The recommendation is to make a modem backup of yours device after you get a GPS lock, and store it to use whenever you need because you have a radio related problem, or make one to share on XDA with other users, be aware to share Radio zip and describe from with device model and ROM you pull it from, because flashing other device Radio may cause problem...
............................................................
This TWRP is theme-able, go to the tread to change the looks:
[THEME][TWRP] TWRP Materialised - Dark / Light / Play

Support, any bugs and errors just post in here, I will answer as soon as possible.

Can I flash it over using flashify?
Thx
Enviado desde mi Moto MAXX mediante Tapatalk

icondeg said:
Can I flash it over using flashify?
Thx
Enviado desde mi Moto MAXX mediante Tapatalk
Click to expand...
Click to collapse
i didn't try that only via fast-boot, but i will.
should not give any error, if you try let me know....
yes it work i just did over TWRP 2.8.1 :good:

baybutcher27 said:
i didn't try that only via fast-boot, but i will.
should not give any error, if you try let me know....
yes it work i just did over TWRP 2.8.1 :good:
Click to expand...
Click to collapse
It works fine!!!
Thanks for all
Enviado desde mi Moto MAXX mediante Tapatalk

omg great work! congrats
muito obrigado!

Awesome work! Thanks man! Can't thank you enough!!

Thank you!
Paypal donation sent.
Confirmation number: 08S12817NX2219226.

Thank you guys i really appreciate the supporter. Of every one.

Small, but big improvement change.
Change log in the 2° post. The TWRP now is much faster to wipe, restore or install a ROM, no more lag to format...

Ok
I believe in you men
If you say that this no affect anything, that's fine by me
Regards
Enviado desde mi Moto MAXX mediante Tapatalk

Update my source.
I can now compile TWRP from CM, Mokee and Omni source's.
Omni source is the best one because is the TWRP source, but it doesn't have quark device tree, so i need to create/port everything and that take time, i'm finishing the testing of the new TWRP no new feature just a more slim image but more complete.
My CM tree is incompatible with TWRP source, Dees_Troy was not able to use my previously tree to build the Official one he tried.
Now after the test i will send the new source and he will be able to produce a new TWRP from TWRP server and if that work make this Official.
+ Now that exist a quark device tree working on omnirom may some one make a AOSP ROM using it (i don't have time right now but i will try in the future after the Official TWRP).
Omni is the most close AOSP source to google AOSP so a rom from they is really clean and very update. I believe that CM kernel tree should work, if any one try let me know...

baybutcher27 said:
Update my source.
I can now compile TWRP from CM, Mokee and Omni source's.
Omni source is the best one because is the TWRP source, but it doesn't have quark device tree, so i need to create/port everything and that take time, i'm finishing the testing of the new TWRP no new feature just a more slim image but more complete.
My CM tree is incompatible with TWRP source, Dees_Troy was not able to use my previously tree to build the Official one he tried.
Now after the test i will send the new source and he will be able to produce a new TWRP from TWRP server and if that work make this Official.
+ Now that exist a quark device tree working on omnirom may some one make a AOSP ROM using it (i don't have time right now but i will try in the future after the Official TWRP).
Omni is the most close AOSP source to google AOSP so a rom from they is really clean and very update. I believe that CM kernel tree should work, if any one try let me know...
Click to expand...
Click to collapse
What about a kernel??
@w4tchout is trying to make a kernel but it seems so hard to do it
A kernel that we can use is the second dream of this forum
Jejejeje
Regards
Enviado desde mi Moto MAXX mediante Tapatalk

icondeg said:
What about a kernel??
@w4tchout is trying to make a kernel but it seems so hard to do it
A kernel that we can use is the second dream of this forum
Click to expand...
Click to collapse
@w4tchout
 @Skrilax_CZ
Has Motorola ever released the mandatory kernel source code for 5.1 for the XT1254? Been two months since 5.1 was released for the Droid Turbo. It's a Quark, just like the XT1225...
I know @Skrilax_CZj is using the kernel sources from stock 5.0.2 for CM12.1 (Lollipop 5.1). But would be nice to be able to use something from Motorola updated 5.1, if possible.

ChazzMatt said:
@w4tchout
@Skrilax_CZ
Has Motorola ever released the mandatory kernel source code for 5.1 for the XT1254? Been two months since 5.1 was released for the Droid Turbo. It's a Quark, just like the XT1225...
I know @Skrilax_CZj is using the kernel sources from stock 5.0.2 for CM12.1 (Lollipop 5.1). But would be nice to be able to use something from Motorola updated 5.1, if possible.
Click to expand...
Click to collapse
I don't know the actual problem as to why my kernel doesn't boot, it could be the dt img or the kernel itself. I'll try to figure it out though.

##W4TCH0UT## said:
I don't know the actual problem as to why my kernel doesn't boot, it could be the dt img or the kernel itself. I'll try to figure it out though.
Click to expand...
Click to collapse
I don't know much about Kernel yet so i cant see what is going wrong in yours...
But i find a workaround, to compile the recovery.img without compile the boot.img i generated a boot.img but use pre build dt + kernel.
That way i can compile recovery in under 13 min and without a kernel folder in the source, before it take over 30, and when i'm resolving bug and error, how much fast i can produce a image better.
The workaround i copy from victara and put in the omni folder of my device source, is need the mkbootimg.mk + dtb (dt image renamed) + kernel.
Then check BoardConfig.mk kernel lines, the dt and kernel i use from a previously build of my on, after you have one no need to compile the kernel every time...
Don't know if this will help but this way you may grub a previously working dt + new kernel or vice versa, and combine to see what works.
My CM source folder is working but not update do to that yet but i believe will work in others source other then omni.
if something work or not let me know.

I finished all the tested with TWRP compile in omni source, i update the download link.
No need to change TWRP unless you use a encrypted device, or you wanna to test it.
Put a note about encryption on 2# post.
If any bug found let me know.

glad to see someone resumed/restarted TWRP work for Maxx. Nice job buddy!
Unfortunately my Maxx was stolen back in Brazil so I wont use this as much as you guys.

respider said:
glad to see someone resumed/restarted TWRP work for Maxx. Nice job buddy!
Unfortunately my Maxx was stolen back in Brazil so I wont use this as much as you guys.
Click to expand...
Click to collapse
too bad bro
i hope you're ok
regards!

[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.

[TWRPv3.x.x]Tank Xtreme Pro Recovery

{
"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"
}
.
Screenshots attached below.
TeamWin Touch Recovery for BLU Tank Extreme Pro
Code:
* [U][B]Disclaimer[/B][/U]
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Older Version
CHANGELOG for 3.1.1-0:
TWRP 3.1.1 is Out, Brings Minor Fixes
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)
FEATURES
Backup & Restore fully functional
Micro SDcard and USB OTG storage support
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
Full SELinux support
Built with android-7.0 TWRP tree
CHANGELOG for 3.2.0-0:
TWRP 3.2.0 is now out
Allow restoring adb backups in the TWRP GUI (bigbiff)
Fix gzip backup error in adb backups (bigbiff)
Fix a bug in TWRP’s backup routines that occasionally corrupted backup files (nkk71)
Better support for installing Android 8.0 based zips due to legacy props (nkk71)
Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
v2 fstab support (Dees_Troy)
Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
Various other minor bugfixes and tweaks
CHANGELOG for 3.2.2-0:
TWRP 3.2.2-0 brings ADB fixes and improvements to OTA updates
adb backup fixes
OTA style update zips will now install automatically without prompting for decrypt
minor tweaks to handling date/time on Qualcomm devices
updates to some language translations
CHANGELOG for 3.2.3-0:
TWRP 3.2.3-0 is out now for most currently supported devices.
Fix automatic installing of OTA zips on encrypted devices
Remove SuperSU from TWRP
Support both md5 and md5sum file extensions when doing MD5 checking for zip files
BUGS:
MTP NOT Recognize Driver--So No mtp connection-- work-around for this now, is to use "mount as USB drive", this will allow similar function as MTP, but only for your micro-SDcard
SUPPORT: Post your questions below. I'll answer whenever I get time.
INSTALLATION
Most devices can be updated quickly and easily within TWRP if you already have version 3.x.y-z or higher installed
1) Download the latest version from DOWNLOAD TAB
2) Copy that file to your sdcard
3) Reboot to TWRP
4) Hit INSTALL and tap the "Images..." button in the lower right
5) Browse to the location of the TWRP image (recovery.img) on your device and select it
6) Select RECOVERY from the PARTITION list and swipe to flash
7) Go to Menu: Reboot recovery
If First time install
You can install with spft as described in following link BUT FIRST NEED unlock bootloader.
Instructions for Flash stock recovery or Custom recovery MEDIATEK devices only
You can also install with fastboot commands after unlocking bootloader.
****UNLOCKING BOOTLOADER WILL CAUSE WARNING ON SCREEN WHEN POWERING ON****
****WARNING WILL PAUSE THE BOOT PROCESS FOR % SECOND DELAY , Not big problem****
BOOTLOADER UNLOCK
How to Unlock Bootloader via Fastboot
1. Setup ADB and Fastboot on your PC.
2. Enable USB debugging and OEM Unlock on your Android device.
1). open settings
2). scroll to about phone
3). tap "Build number" 7 -8 times
4). go back, now you have new menu option"Developer options
5). open and make sure "off" switch at top is slid to right to turn on
5). slide switches for OEM unlocking and ADB debugging
6). Now connect usb cable from PC to Phone
7). phone should have popup window asking for authorization to connect with ADB
3. Connect your device to the PC with a USB cable.
4. Open a command window on your PC.
5. Boot your device into bootloader mode using the following command:
Code:
adb reboot bootloader
└ You may get a request to authorize USB debugging on the device, accept it.
6. Once your device is in bootloader mode, issue the following command to unlock bootloader:
Code:
fastboot oem unlock
You get a confirmation screen on your device. Press Volume Up button to highlight Yes and press Power button to select it.
This will begin bootloader unlocking process, which shouldn’t last more than couple of minutes.
7. Once bootloader is unlocked, your device will reboot into bootloader mode. You need to boot it into system now using the command below:
Code:
fastboot reboot
During reboot, your device will go through a factory reset and then finally boot into system.
RECOVERY INSTALL
1. make sure developer options is enabled
1). open settings
2). scroll to about phone
3). tap "Build number" 7 -8 times
4). go back, now you have new menu option"Developer options
5). open and make sure "off" switch at top is slid to right to turn on
5). slide switches for OEM unlocking and ADB debugging
6). Now connect usb cable from PC to Phone
7). phone should have popup window asking for authorization to connect with ADB
2. Reboot to bootloader
Code:
adb reboot bootloader
3. Test recovery works for your device
(example commands assume you have the 3.2.0 version of recovery downloaded to the desktop)
Code:
Fastboot boot Desktop/twrp-3.2.0-recovery.img
4. If recovery boots good, then return to bootloader and flash (commands work from in booted twrp)
These steps are what I find to be best order to prevent the stock rom from replacing the stock recovery on boot.
Code:
adb reboot bootloader
fastboot flash recovery Desktop/twrp-3.2.0-recovery.img
fastboot boot Desktop/twrp-3.2.0-recovery.img
adb wait-for-device
adb reboot recovery
ROOT
If your device haven't ROOT:
Thanks to @Chainfire for the file!
Rooting instructions: put the SuperSu...zip on sdcard. Go to TWRP and tap INSTALL. Search the zip file and select. Swipe to install. Reboot system.
Dowload: SuperSU V2.82
DOWNLOADS In Download Tab
SCATTER File
Stock boot ----- Stock recovery
TWRP 3.1.1 ------ TWRP 3.2.0 ------ TWPR 3.2.1 ------ TWPR 3.2.2-0 (based in stock V7.0.04.04_GENERIC 24-05-2018)
-----Added--TWRP 3.2.2-0(repacked)Has ro.secure=0; ro.adb.secure=0; to allow adb while data is wiped.
TWRP 3.2.3-0 [Has ro.secure=0; ro.adb.secure=0; to allow adb while data is wiped.] (based in stock V7.0.04.05_GENERIC 06-08-2018) download in post#2
Note:
After TWRP3.2.2 the partitions for the backup save have been modified to: /dev/block/platform/mtk-msdc.0/by-name/
So if you have a version older than TWRP3.2.2 you should copy the
Root [Internal Storage or MicroSD] / TWRP/ BACKUPS / VCIBIZMR7HT8GES8 / year-month-date-hour-minute-second_BLU_T0010UU_V70040x_GENERIC_dd-mm-yyyy
folder to the new one folder
Root [Internal Storage or MicroSD] / TWRP / year-month-date-hour-minute-second_BLU_T0010UU_V70040x_GENERIC_dd-mm-yyyy
of the version TWRP3.2.2 or last.
We've added the partition for internal storage if you want to create a backup of it. But keep in mind that the more files there are in the internal storage, the larger the size of the backup made and this will depend on your choice and how you can save it to other larger storage capacity.
So be more careful!
Contributors
@lopestom
@Dees_Troy
@teamwin
@vampirefo
Version Information
Status: Beta
Current Beta Version: 3.2.3-0-20181013
Beta Release Date: 2017-12-24
XDA:DevDB Information
Tank Xtreme Pro Recovery, Tool/Utility for all devices (see above for details)
Contributors
mrmazak, lopestom, vampirefo
Version Information
Status: Beta
Created 2017-12-08
Last Updated 2018-10-13

Instructions to unlock and relock bootloader
Instructions to unlock and relock bootloader soo... :silly:
https://youtu.be/5ZVW-XzPCXE
https://youtu.be/Zf6hMqGbC_4

With older version TWRP, does MTP work? I see you list it not working on 3.2.
MTP to me is more important than version of TWRP used.
Sent from my Tank Xtreme Pro using Tapatalk

vampirefo said:
With older version TWRP, does MTP work? I see you list it not working on 3.2.
MTP to me is more important than version of TWRP used.
Sent from my Tank Xtreme Pro using Tapatalk
Click to expand...
Click to collapse
No, mtp not working at all on this device. The recovery that I used to port older version is yours from life Max. Boh of these on this thread came from lopestom.
Suspect something in kernel, like touch on life Max was problem in kernel. As of last time I checked, sources we're not published from blue yet.

mrmazak said:
No, mtp not working at all on this device. The recovery that I used to port older version is yours from life Max. Boh of these on this thread came from lopestom.
Suspect something in kernel, like touch on life Max was problem in kernel. As of last time I checked, sources we're not published from blue yet.
Click to expand...
Click to collapse
Ok, thanks I will compile a recovery for Tank, see if I have any better luck with it.
I suspect it's the recovery looking for MTP in the wrong place, Android 6 and 7 access to MTP would be different.
Blu Life Max is Android 6, so MTP would be in platform, while tank is Android 7 so would be in virtual.
Sent from my Tank Xtreme Pro using Tapatalk

vampirefo said:
Ok, thanks I will compile a recovery for Tank, see if I have any better luck with it.
I suspect it's the recovery looking for MTP in the wrong place, Android 6 and 7 access to MTP would be different.
Blu Life Max is Android 6, so MTP would be in platform, while tank is Android 7 so would be in virtual.
Click to expand...
Click to collapse
@mrmazak tested some TWRP and we have same issue with driver mtp in PC/laptop like Indisponible driver so the device is recognized but cannot open mtp. If we boot ROM so that's recognizing and open.
I tried with libtwrpmtp.so from sbin folder: replacing from other, open to know if need more informations and compared with same lib name of Android 6 as I have mtp working..... So no luck!
Remember: TWRP3.1.1 and 3.2.0 from me is based in Android 7 Nougat TWRP base x32.
As I'm no good with programming to open libtwrpmtp.so to see if have or need specific info so... I hope that you can help better on it...
Congrats and enjoy...
Sent from my BLUBOO Xtouch using XDA Labs

lopestom said:
@mrmazak tested some TWRP and we have same issue with driver mtp in PC/laptop like Indisponible driver so the device is recognized but cannot open mtp. If we boot ROM so that's recognizing and open.
I tried with libtwrpmtp.so from sbin folder: replacing from other, open to know if need more informations and compared with same lib name of Android 6 as I have mtp working..... So no luck!
Remember: TWRP3.1.1 and 3.2.0 from me is based in Android 7 Nougat TWRP base x32.
As I'm no good with programming to open libtwrpmtp.so to see if have or need specific info so... I hope that you can help better on it...
Congrats and enjoy...
Sent from my BLUBOO Xtouch using XDA Labs
Click to expand...
Click to collapse
I don't know about your 3.2 recovery, mrmazak used my Blu Life Max recovery, I told that recovery to look in platform for MTP, that's why I suspect my Blu Life Max recovery is the problem.
If I am correct, just rebuilding a new recovery telling it to look in virtual for MTP should work, if I am wrong it won't, doesn't hurt to try.
Sent from my Tank Xtreme Pro using Tapatalk

vampirefo said:
I don't know about your 3.2 recovery, mrmazak used my Blu Life Max recovery, I told that recovery to look in platform for MTP, that's why I suspect my Blu Life Max recovery is the problem.
If I am correct, just rebuilding a new recovery telling it to look in virtual for MTP should work, if I am wrong it won't, doesn't hurt to try.
Sent from my Tank Xtreme Pro using Tapatalk
Click to expand...
Click to collapse
I assume you already looked, but, the recovery log shows mtp error , over and over again.
Code:
E:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] response write returned -1, errno: 5, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 22
pretty sure it happens with all versions

The stock boot img has "init.usb.configs.rc"
in this file it sets usb_gadget # for mtp.
there is nothing that I find similar in the twrp.
I am thinking to add this rc file to twrp and import it with the init.rc to see if it changes anything.
***UPDATE*** No change with adding this configfs file
Attached is a listing of all mentins of "mtp" in the stock boot.img ramdisk
this link is in Russian , but google translate helps.
posts #1354 and 1355 reference the same error I see in the recovery log. Also mention addressing the usb_gadget #
.

mrmazak said:
The stock boot img has "init.usb.configs.rc"
in this file it sets usb_gadget # for mtp.
there is nothing that I find similar in the twrp.
I am thinking to add this rc file to twrp and import it with the init.rc to see if it changes anything.
***UPDATE*** No change with adding this configfs file
Attached is a listing of all mentins of "mtp" in the stock boot.img ramdisk
this link is in Russian , but google translate helps.
posts #1354 and 1355 reference the same error I see in the recovery log. Also mention addressing the usb_gadget #
.
Click to expand...
Click to collapse
Oh, well if MTP doesn't work it doesn't work, I compiled my own today, removed MTP tab and just use Mount USB Storage instead, works fine for micro sdcard. I compiled mine using TWRP 8.1 source, and uploaded it to needrom.

vampirefo said:
Oh, well if MTP doesn't work it doesn't work, I compiled my own today, removed MTP tab and just use Mount USB Storage instead, works fine for micro sdcard. I compiled mine using TWRP 8.1 source, and uploaded it to needrom.
Click to expand...
Click to collapse
I just gave this a try, I have noticed something, could be intentional , not sure.
On your other recovery you could flash system as image, this one you cannot.

mrmazak said:
I just gave this a try, I have noticed something, could be intentional , not sure.
On your other recovery you could flash system as image, this one you cannot.
Click to expand...
Click to collapse
Correct something I don't use, that's controlled by recovery.fstab
just use this recovery.fstab if you want that option, unpack recovery and replace recovery.fstab

vampirefo said:
Correct something I don't use, that's controlled by recovery.fstab
just use this recovery.fstab if you want that option, unpack recovery and replace recovery.fstab
Click to expand...
Click to collapse
thanks, is it ok to add this version to the downloads of this thread?

mrmazak said:
thanks, is it ok to add this version to the downloads of this thread?
Click to expand...
Click to collapse
Thanks fine with me.
Sent from my Tank Xtreme Pro using Tapatalk

vampirefo said:
Thanks fine with me.
Sent from my Tank Xtreme Pro using Tapatalk
Click to expand...
Click to collapse
I've added you as contributor and added your version, with the fstab that has system_image and also cache enabled (because of an error message in recovery.log that stated could not mount cache)

sorry for asking,, can i use this recovery into blu tank xtreme 5.0??
im looking everywhere the method how to root blu tank xtreme 5.0 android 6

gabmika69 said:
sorry for asking,, can i use this recovery into blu tank xtreme 5.0??
im looking everywhere the method how to root blu tank xtreme 5.0 android 6
Click to expand...
Click to collapse
No!
Each device should have the own Custom Recovery.
Sent from my BLUBOO Xtouch using XDA Labs

Please HELP!
Was hung on boot with TWRP installed. Fixed the problem by installing SuperSU to unlock the bootloader. No help needed.

[TWRP 3.2.1-1] [ROOT] A8+ sm-a730f - 21/01/2018

Unofficial release -TWRP recovery for the Galaxy A8+ - SM-A730F, EXYNOS 7885
{
"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.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 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
Update 21/1/2017
TWRP 3.2.1-1 NN build released.
Current status: beta
Features:
MTP >> to be confirmed
ADB working >> to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Raw SYSTEM image backup
NTFS support
F2FS support >> To be added
Twrp app support
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SamMobile or updato.com in case of problems. This will trip the knox counter.
Instructions:
Flash with odin in the AP slot.
Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
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 + VOL DOWN
As soon as the screen goes blank change to POWER + VOL UP
You should now see TWRP recovery.
FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY
NOTE: ON SOME 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.2.1-1_sm-a730f_210117
To Root:
Flash the latest SuperSU or Magisk release with TWRP:
SUPERSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
MAGISK - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
(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
DONATE ME HERE IF YOU WANT TO BUY ME A BEER/COFFEE OR HIT THE THANKS BUTTON IF I HELPED YOU

NOTE:
This may be a dead duck in the water before it even installs due to the fact Samsung currently seem to be locking bootloaders on all recent devices even devices with previously unlocked bootloaders.
BEFORE attempting to install this software please ensure you have the stock firmware available (this can be found on updato.com) and that you are able to flash it with Odin.
.

1.1k views, 120 downloads and not one report or tap of a thanks.
XDA truly is about community spirit.
Cheers guys.

If you do one for the the a530f i would be glad to test it ! (if there's no risk of complete brick of course)

tibey said:
If you do one for the the a530f i would be glad to test it ! (if there's no risk of complete brick of course)
Click to expand...
Click to collapse
No risk as long as you've got the firmware handy.

ashyx said:
1.1k views, 120 downloads and not one report or tap of a thanks.
XDA truly is about community spirit.
Cheers guys.
Click to expand...
Click to collapse
It's amazing.
I would very much like to know if this is locked from factory, but no one reports if it can be flashed or not :/

Guide on TWRP recovery for A8
ashyx said:
Unofficial release -TWRP recovery for the Galaxy A8+ - SM-A730F, EXYNOS 7885
TWRP 3.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 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
Update 21/1/2017
TWRP 3.2.1-1 NN build released.
Current status: Testing stage
NOTE: THIS IS AS YET UNTESTED. IF YOU DECIDE TO TRY THIS OUT PLEASE REPORT ANY ISSUES WITH DETAILS. POSTS LIKE 'NOT WORKING' WILL BE IGNORED
Features:
MTP >> to be confirmed
ADB working >> to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Raw SYSTEM image backup
NTFS support
F2FS support >> To be added
Twrp app support
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 in the AP slot.
Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
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 + VOL DOWN
As soon as the screen goes blank change to POWER + VOL UP
You should now see TWRP recovery.
FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY
NOTE: ON SOME 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.2.1-1_sm-a730f_210117
To Root:
Flash the latest SuperSU or Magisk release with TWRP:
SUPERSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
MAGISK - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
(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
DONATE ME HERE IF YOU WANT TO BUY ME A BEER/COFFEE OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Hello @ashyx, I have made a guide based on your thread: http://techbeasts.com/install-twrp-recovery-root-galaxy-a8-plus-2018/
Just wanted to notify.

Sucks that no one is reporting anything, but tbh in europe it seems that only the A8 (A530f) has been released so far.
Do you think it would be easy to port for that model ? I think there's a couple of us waiting for this port, would be much appreciated and would test it asap.

tibey said:
Sucks that no one is reporting anything, but tbh in europe it seems that only the A8 (A530f) has been released so far.
Do you think it would be easy to port for that model ? I think there's a couple of us waiting for this port, would be much appreciated and would test it asap.
Click to expand...
Click to collapse
It will be ready at some point today.

@tibey
Here you go, good luck: https://androidfilehost.com/?fid=746010030569951180
.

ashyx said:
@tibey
Here you go, good luck: https://androidfilehost.com/?fid=746010030569951180
.
Click to expand...
Click to collapse
Seems to work great on a530f ! Just followed the instructions (had just a minor issur with MTP not working in TWRP)
Thanks a lot :good:
Edit : Guess you should post it there : https://forum.xda-developers.com/ga...18-roms-kernels-recoveries--other-development (damn that forum is invisible in search)

tibey said:
Seems to work great on a530f ! Just followed the instructions (had just a minor issur with MTP not working in TWRP)
Thanks a lot :good:
Edit : Guess you should post it there : https://forum.xda-developers.com/ga...18-roms-kernels-recoveries--other-development (damn that forum is invisible in search)
Click to expand...
Click to collapse
Yep it seems Samsung are forcing the use of their own MTP driver in the kernel as I couldn't disable it.

And it continues, now 2.2k views and 199 downloads and still not one downloader could be bothered to post.

ashyx said:
And it continues, now 2.2k views and 199 downloads and still not one downloader could be bothered to post.
Click to expand...
Click to collapse
Well samsung mtp isn't in a8+ defconfig i just looked. So post your device tree and the partition layout and fstab from stock kernel and I will see if I can help.

travis82 said:
Well samsung mtp isn't in a8+ defconfig i just looked. So post your device tree and the partition layout and fstab from stock kernel and I will see if I can help.
Click to expand...
Click to collapse
I know it isn't which is why it isn't included.
Seems like they are forcing their own driver.
There is probably a way to fix it by modifying the make files, but I won't spend any more time on it until people can be bothered to take the time to respond.

Not working
ashyx said:
Unofficial release -TWRP recovery for the Galaxy A8+ - SM-A730F, EXYNOS 7885
TWRP 3.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 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
Update 21/1/2017
TWRP 3.2.1-1 NN build released.
Current status: Testing stage
NOTE: THIS IS AS YET UNTESTED. IF YOU DECIDE TO TRY THIS OUT PLEASE REPORT ANY ISSUES WITH DETAILS. POSTS LIKE 'NOT WORKING' WILL BE IGNORED
Features:
MTP >> to be confirmed
ADB working >> to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Raw SYSTEM image backup
NTFS support
F2FS support >> To be added
Twrp app support
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SamMobile or updato.com in case of problems. This will trip the knox counter.
Instructions:
Flash with odin in the AP slot.
Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
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 + VOL DOWN
As soon as the screen goes blank change to POWER + VOL UP
You should now see TWRP recovery.
FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY
NOTE: ON SOME 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.2.1-1_sm-a730f_210117
To Root:
Flash the latest SuperSU or Magisk release with TWRP:
SUPERSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
MAGISK - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
(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
DONATE ME HERE IF YOU WANT TO BUY ME A BEER/COFFEE OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Not Working Properly its give bootloop
i try according to this method but not working it restart after the first logo of the phone.
odin show passed message but phone get bootloops

akshaygpt2 said:
Not Working Properly its give bootloop
i try according to this method but not working it restart after the first logo of the phone.
odin show passed message but phone get bootloops
Click to expand...
Click to collapse
.
What are your phone specs and build number?

ashyx said:
.
What are your phone specs and build number?
Click to expand...
Click to collapse
Android 7.1.1
Galaxy A8 plus
Sent from my SM-A730F using Tapatalk

akshaygpt2 said:
Android 7.1.1
Galaxy A8 plus
Click to expand...
Click to collapse
I need your firmware build.

ashyx said:
I need your firmware build.
Click to expand...
Click to collapse
Build Firmware -
NMF26X.A730FXXU1ARAC
Sent from my SM-A730F using Tapatalk

TWRP 3.4.0 for the Samsung Galaxy Fold

TWRP 3.4.0 for the Samsung Galaxy Fold
{
"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
It gives me great pleasure to present to you TWRP on the Samsung Galaxy Fold. Your foldable phone just became even more flexible.
This project picks up TWRP where Chris Williamson left off. Chris produced the initial release of TWRP for the Fold, which combined a custom kernel sporting some extra features with a pre-rooted TWRP image.
Chris asked me to take over the development of TWRP for the Fold to allow him to concentrate on kernel development for the device, and I was happy to oblige. My goal is to offer you the most functional build of TWRP that I possibly can, whilst making no assumptions about your desire to root the device or run a custom kernel. For that reason, the kernel I am supplying as part of this project is as close to stock as possible, with only the minimum number of changes required to allow TWRP to function, and with no added features. For the same reason, the images I provide have not been pre-rooted with Magisk.
Rooting Samsung system-as-root devices
How you root your Fold depends on whether you are running Android 9 (Pie) or Android 10. If, however, you have already upgraded your device to Android 10, you can root your device only in the boot partition. For reasons that are not yet clear, the Fold will not boot Android froma custom kernel that is rooted in recovery.
Rooting in the recovery partition
When the device is rooted in recovery, the TWRP image must be patched with Magisk (using the Magisk Manager app) to allow the same kernel to be shared between TWRP and Android. After patching, the user always boots the device from the recovery partition, and uses the device's hardware keys at boot time to select between Magisk-rooted Android and TWRP. A normal system boot from the boot partition brings the system up without root.
Rooting in the boot partition
When the device is rooted in the boot partition, the TWRP image is left untouched. Instead, the boot partition must be rooted with Magisk by flashing the Magisk zip file in TWRP. Rooted Android is booted via a normal system boot and the hardware keys play no special role. There is no option to boot Android unrooted.
Device preparation
Before doing anything else, back up your data now if you have any.
If you are installing TWRP on a brand new device, you must first unlock its bootloader. Select OEM Unlocking from Settings → Developer Options, then reboot to Device Unlock mode to actually unlock the bootloader. This will have the side-effect of resetting the device.
If you are installing TWRP on an unrooted device, it is crucial that you also flash the attached vbmeta.img file at the same time. Simply include this in a tar file with the TWRP image for your device (renamed recovery.img) and flash them together. You must reformat /data after doing this.
If you fail to neutralise the device's vbmeta protection before rebooting, the device's anti-tampering protection will be triggered and you will be unable to boot either Android or TWRP. A full reinstallation of stock firmware will be required and your device may be left in KG State Prenormal, requiring time-consuming extra steps to restore its ability to accept unofficial images again. Do not fail to neutralise vbmeta.
If you have already rooted your device with Magisk, vbmeta has already been disarmed and you may proceed with installing TWRP.
Image preparation
Rooting in the recovery partition
As noted above, the TWRP images supplied here are not pre-patched with Magisk. If you wish to dual-boot TWRP and Android Pie, you must patch the recovery image with Magisk before flashing it. Version 20.2 of Magisk is recommended for this. Versions 20 and 20.1 contain a serious bug that will render the recovery partition unbootable after patching. Please see John Wu's excellent step-by-step instructions for rooting the 2019 generation of Samsung Pie devices with Magisk.
An altogether simpler way of working is to flash the TWRP image on demand, only when required. After finishing your work in TWRP, simply replace TWRP with a Magisk-rooted stock recovery image and reboot to Android. I personally recommend this swapping approach, as it frees both the TWRP maintainer and the user from constantly updating the TWRP image to ensure it contains a kernel that is compatible with the version of the firmware on the device.
Here is a basic sample script that will check whether the current environment is Android or TWRP, flash the appropriate recovery image for the other environment, then reboot to it. You can easily adapt it to fit your needs.
Code:
twrp_img=/sdcard/twrp/twrp-3.3.1.img
stock_img=/sdcard/twrp/recovery-ask2-magisk.img
if [ -f /sbin/magisk ]; then
# We're in Android: Switch to TWRP.
#
infile=$twrp_img
else
# We're in TWRP: Switch to Android.
#
infile=$stock_img
fi
dd if=$infile of=/dev/block/by-name/recovery bs=$(stat -c%s $infile) && reboot recovery
Rooting in the boot partition
No special image preparation is required for installation on Android 10 devices.
TWRP images
TWRP is offered here as an assortment of recovery image files. To use with Odin, first rename the appropriate file recovery.img and then tar it. Ready-made tar files are not supplied here, because it would double the number of files to be maintained, and because it's trivial to generate a tar archive on any modern computing platform, including on the Fold itself.
Post-installation
The Fold, like all 2019 Samsung devices, utilises file-based encryption (FBE) by default. The use of encryption in TWRP on Samsung devices is invariably problematic, however, and encryption is therefore routinely disabled by users wishing to use TWRP. If this is not done, your files will remain unreadable to TWRP.
To remove encryption from your device, please flash the Samsung multi-disabler after installing TWRP, and then reformat /data again. Do not skip this step, even if you have already formatted /data one or more times thus far. If installing TWRP on Android 10, you need at least v2.3 of the multi-disabler.
Compatibility
The images below are known to be compatible with the firmware revisions stated. Results on other revisions will vary.
The F907B images have been personally tested and verified by me on my own Fold 5G prior to release. The F900F images should be of comparable quality.
Download
Android 10
Latest release for F907B (BTH2 firmware)
twrp-winnerx-3.5.0_9-1_ianmacd.img
twrp-winnerx-3.5.0_9-1L_ianmacd.img (landscape)
Latest release for F900F (BTH2 firmware)
twrp-winner-3.5.0_9-1_ianmacd.img
twrp-winner-3.5.0_9-1L_ianmacd.img (landscape)
Android 9
Latest release for F907B (ATA1 firmware)
twrp-winnerx-3.3.1-23_ianmacd.img
twrp-winnerx-3.3.1-23L_ianmacd.img (landscape)
Latest release for F900F (ATA3 firmware)
twrp-winner-3.3.1-23_ianmacd.img
twrp-winner-3.3.1-23L_ianmacd.img (landscape)
Known problems
TWRP is currently displayed only on the device's main (inner) screen.
Haptic feedback is currently unavailable in TWRP.
Frequently Asked Questions
Q. Why do you offer a separate build for each device with landscape orientation?
A. The aspect ratio of the main (inner) screen 4.2:3 is such that TWRP on this device looks good in both portrait and landscape orientation. In portrait mode, the clock and battery meter are shifted to the left to avoid the camera notch. In portrait mode, the entire image is shifted to the right to avoid the notch.
See the gallery of images below, or simply try each version of TWRP on your device, to discover which orientation you prefer.​
TWRP source code
TWRP bootable recovery
TWRP device trees
Galaxy Fold a.ka. winner (F900F)
Galaxy Fold 5G a.ka. winnerx (F907B)
Kernel source code
Galaxy Fold a.ka. winner (F900F)
Galaxy Fold 5G a.k.a. winnerx (F907B)
Real-time chat
For support or just to talk about the device amongst friends, please join our small Telegram group dedicated to the Galaxy Fold.
Credits
I am indebted to Chris Williamson (@chrisaw) for laying the foundations for TWRP on the Fold. And thanks in no small part to him and his contagious enthusiasm for the device, I'm now also indebted to Samsung for the purchase price of a Fold 5G.
Thanks to @osm0sis for AIK, a tool without which working with boot images would be far more tedious than it already is.
Thanks to Samsung for engineering this amazing device in the first place.
And last but not least, thanks to my wife, Sarah, for her tolerance of my expenditure on gadgetry.
XDA:DevDB Information
TWRP for the Samsung Galaxy Fold, Tool/Utility for the Samsung Galaxy Fold
Contributors
ianmacd, chrisw
Version Information
Status: Stable
Current Stable Version: 3.4.0-4_ianmacd
Stable Release Date: 2020-10-05
Created 2019-11-20
Last Updated 2021-01-19

Gallery
Unlocked bootloader stage 1
Unlocked ootloader stage 2
Main menu
Making a back-up (in Dutch)
Main menu (landscape)
Instaling an image (landscape)

Changelog
3.5.0_9-1_ianmacd
Update to TWRP 3.5.0.
3.4.0-4_ianmacd
Use latest F907BXXS4BTH2 and F900FXXS4BTH2 kernel source code.
3.4.0-1_ianmacd
TWRP updated to version 3.4.0.
3.3.1-101_ianmacd
Use latest F900FXXU3BTDD and F907BXXU3BTDD kernel source code.
Kernel now built using clang 8.0.11.
3.3.1-100_ianmacd
First release supporting Android 10.
Use latest F900FXXU3BTCD and F907BXXU3BTC9 kernel source code.
3.3.1-23_ianmacd
Use latest F900FXXS3ATA3 and F907BXXS3ATA1 kernel source code.
3.3.1-22_ianmacd (F907B only)
Build kernel from latest F907BXXS2ASL3 source code.
3.3.1-21_ianmacd (F907B only)
Build kernel from latest F907BXXU2ASK9 source code.
3.3.1-20_ianmacd
Use latest F900FXXS2ASKC and F907BXXS2ASK2 kernel source code.
Build without crypto code, as crypto is unsupported.
MInor fstab fix for /data.
Disable sundry irrelevant kernel features for a slightly leaner kernel.
3.3.1-17_ianmacd
First ianmacd release, using F900FXXU1ASJ4 and F907BXXS2ASK2 kernel source code.

That was fast!
Sadly most of us can't afford this 2000$ phone lol

Selling my US version, time to get F900F

Version 3.3.1-20_ianmacd released.
This release upgrades the kernel from the latest Samsung source code. In the case of the F900F, there are significant changes, whereas the F907B's kernel is hardly differs from the previous version.
The builds have also been stripped of superfluous crypto code, and a harmless bug in the fstab has been fixed.
3.3.1-20_ianmacd
Use latest F900FXXS2ASKC and F907BXXS2ASK2 kernel source code.
Build without crypto code, as crypto is unsupported.
MInor fstab fix for /data.
Disable sundry irrelevant kernel features for a slightly leaner kernel.

ianmacd said:
This release upgrades the kernel from the latest Samsung source code. In the case of the F900F, there are significant changes, whereas the F907B's kernel is hardly differs from the previous version.
The builds have also been stripped of superfluous crypto code, and a harmless bug in the fstab has been fixed.
3.3.1-20_ianmacd
Use latest F900FXXS2ASKC and F907BXXS2ASK2 kernel source code.
Build without crypto code, as crypto is unsupported.
MInor fstab fix for /data.
Disable sundry irrelevant kernel features for a slightly leaner kernel.
Click to expand...
Click to collapse
Thank you for all your work !!!

help me plz
hello, I can't flash with Odin because it gives me an error message: blocked from the OEM.

Version 3.3.1-21_ianmacd released for the F907B.
Changelog
3.3.1-21_ianmacd (F907B only)
Kernel built from latest F907BXXS2ASK9 source code.

Hi ianmacd
I know this is off top, but couldn't private message you
On libsecure_storage companion for rooted Samsung devices ver. 2.0 I experienced strong connectivity issues with airpods 2 (on note 9), rolling back to 1.8 got working it ok. Just for your information

DTman22 said:
hello, I can't flash with Odin because it gives me an error message: blocked from the OEM.
Click to expand...
Click to collapse
Same here.. anyone can help ...?

Version 3.3.1-22_ianmacd for the F907B released.
Changelog
3.3.1-22_ianmacd (F907B only)
Build kernel from latest F907BXXS2ASL3 source code.

hi I tried to use the method but something wrong happened, now my f900f stuck on starting android and it won't start up .
how can I go to download mode .?
Note: the VOL_UP + Power bottom it's not doing anything, even if putting the cable into the phone while starting up ..
any solutions .. ?

I'M getting "custom binary blocked by OEM lock "
the OEM unlock in developer option is ON
model F900F
Any solution ?

thmthoom said:
I'M getting "custom binary blocked by OEM lock "
the OEM unlock in developer option is ON
model F900F
Any solution ?
Click to expand...
Click to collapse
All you have done by toggling that option under Developer Options is enable OEM-unlocking of the device. You haven't actually opened the lock yet.
Boot to Download Mode to actually open the lock.
See the OP for more details.
Sent from my SM-N975F using XDA Labs

ianmacd said:
All you have done by toggling that option under Developer Options is enable OEM-unlocking of the device. You haven't actually opened the lock yet.
Boot to Download Mode to actually open the lock.
See the OP for more details.
Sent from my SM-N975F using XDA Labs
Click to expand...
Click to collapse
Thanks for your response brother..
Actually I’m booting to download mode using K 300 tool .. because I cannot boot using VOLUP + POWER bottom .. so my question is :
1- how to open the lock through the download mode , coz I’m not getting any options there.
2- what do u mean by “ see the op for more details “

ianmacd said:
All you have done by toggling that option under Developer Options is enable OEM-unlocking of the device. You haven't actually opened the lock yet.
Boot to Download Mode to actually open the lock.
See the OP for more details.
Sent from my SM-N975F using XDA Labs
Click to expand...
Click to collapse
Brother , for Unlocking Bootloader these are the steps :
Allow bootloader unlocking in Developer options → OEM unlocking ( DONE )
Reboot your device to download mode. Either use adb reboot download, or use the key combo for your device. ( DONE )
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot. ( the volume up won't work in this step, only I can use Volume down+power to restart the phone )
So what to do in this case if you have any ideas ...

I Followed " John Wu's excellent step-by-step instructions for rooting the 2019 generation of Samsung Pie devices with Magisk. " STEP-BY-STEP these was the resutls :
1- I won't able to use VOL_UP bottom , I skip this step " I think this step caused me a lot of problems "
2- all other steps I'm getting ( boot ) locked OEM or ( vbmeta ) locked OEM
3- I tried to flash recovery alone
4- I tried to flash vbmeta alone
5- I tried to flash both recovery + vbmeta together
The result : FAIL
I think my main problem is unlocking the bootloader using VOL_UP key ..... How to do this while I don't have an option to use VOL_UP key.
even if i'm pressing the VOL_UP key for 1 Minute nothing happens .
you kindness solution will be appreciated

Any chance to have TWRP for F907N?

@ianmacd
First I'd like to say thank you for the work that you've done, and your intro was very well put and super kind to Chris. I know you likely have your hands very full, however I was wondering if you knew of any plans for the F900U or F900U1. I would like to reformat my AT&T phone so that I can get access to unlocking bootloader and hopefully use your TWRP, but I'm not sure if it would work.