Installed the 2.7.0.0 version of TWRP using Autorec. Worked flawless on my D802.
Took me a little bit more time to figure out how to upgrade recovery to version 2.7.1.0.
So far I discovered 2 possible approaches and like to share it with you:
1. Following the instructions within the original TWRP thread (http://forum.xda-developers.com/showthread.php?t=2449679).
This requires the TWRP Manager app from the Play Store. Install TWRP Manager, open it and provide root permissions. Then hit Advanced->Install Recovery.
Downside of this approach is that the TWRP Manager app requires you to install Stericson BusyBox. Since I didn't want to mess with an other already installed Busybox version, I looked for another approach
2. Flash new version through TWRP recovery itself. This is probably the most simple/straight approach.
Download zip version of TWRP 2.7.1.0 (e.g. from http://techerrata.com/browse/twrp2/g2d802)
Save it in phone memory. Reboot in recovery and flash zip the usual way.
I did use the second approach, which worked flawless.
I downloaded de.robv.android.xposed.installer_v33_36570c.apk but it said there was a compatibilty issue with my version of sdk and arm64-v8a.
Any install instructions that cover marshmallow on the 1575?
You need to XposedInstaller_3.0_alpha4.apk and xposed-v80-sdk23-arm64.zip found in the official xposed forum. Install the apk file as usual then you need to flash the framework zip file in recovery. Wipe cache/dalvik before rebooting to system.
The files are listed at the bottom, here: http://forum.xda-developers.com/showpost.php?p=58828974&postcount=1
Can we use xposed with systemless root or should we wait ?
Xposed runs with systemless root. But to note, it is preferable to install to system partition, the traditional method.
Because several Users have problems with understanding what they actually should do i think the easiest way is writing some How-to.
Guide for Unlocking Bootloader Backup TA and so on
I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY CAUSE YOUR DEVICE
Your Bootloader must be unlocked and TWRP recovery installed.
1. Systemless Root/Xposed
Systemless Mode means that there is no File changed in your System Partition, this works because the main changes are made in the Kernel and not to the Android System itself. Because of this you have a special file on your Internal Memory in /data/ for Systemless Root you get a su.img file and for Systemless Xposed you get a xposed.img file. If you have both sure there are both files present. These files are loaded while your device is booting before the Android System is booting. This is good for us because we can easily Update our Systems (on same Rom).
1.1 Download latest beta-superSU/systemless xposed framework and place them on your sdcard.
1.2 Reboot into recovery and flash beta-superSU/systemless xposed framework (if both, in that order)
1.3 clear cache/dalvik
1.4 reboot
2. System Root/Xposed
With System Mode your changes are direct on the System Partition and mostly Updates dont work.
2.1 System Root is not available for our Device with MM. Download latest beta-superSU/xposed Framework and place them on your sdcard.
2.2 Reboot into recovery and flash beta-superSU/xposed framework (if both, in that order)
2.3 clear cache/dalvik
2.4 reboot
3. Change your Kernel while having a Systemless modified Android
Because the changes that were made while flashing Systemless Root/Xposed, your System wont work with just flashing the new Kernel.
3.1 Download the new Kernel to your Computer (make sure it is with TWRP or you flash it seperate after flashing the Kernel).
3.2 Download latest beta-superSU/systemless xposed framework and place them on your sdcard.
3.3 Reboot your device into fastboot mode and flash the new Kernel "fastboot flash boot xxxx.img"
3.4 Reboot your device into TWRP and flash beta-superSU/systemless xposed framework (if both, in that order)
3.5 clear cache/dalvik
3.6 reboot
4. Switch between System and Systemless Mode
For Switching from System Mode to Systemless with Xposed:
4.1 Update or install Material Design xposed installer App
4.2 Download the usual xposed uninstaller zip and the systemless xposed framework for your device
4.3 Open Material Xposed Installer and deactivate the framework
4.4 Reboot into recovery
4.5 Flash the uninstaller zip
4.6 clear cache/dalvik
4.7 Flash systemless xposed framework
4.8 reboot into System (take a few minutes)
4.9 Open Material Xposed Installer and activate Systemless Xposed framework
4.10 reboot
5. Delete / uninstall Systemless Root/Xposed
5.1 Open Material Xposed Installer and deactivate the framework
5.2 restart your System
5.3 Use an Explorer with root access and delete the files "/data/su.img" and "/data/xposed.img"
5.4 restart your System
If i forgot something please tell me i will add it.
Regards
make this for locked bootloaders :/
Can you please provide the link for systemless xposed file??
Oneplus 5, Official ROM, H2OS, Android 7.1
1. First time, I followed https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 and successfully install TWRP and root using Supersu. I can goes into TWRP recovery without any problem. I notice that the supersu I installed in a systemless one, some apps can't get root access, like AD Away, Titanium Backup. But most apps can work with it. I used the one of the two root method in that tutorial as follows:
For Users who want to remain Encrypted:
1. Boot into TWRP Recovery and allow system modifications.
2. Swipe right and enable modifications.
3. Select your preferred Language, Tap “Never show this screen on boot again,” and Swipe allow modification.
4. Navigate to Install and select Magisk Or SuperSU to root OnePlus 5.
5. Swipe to confirm the flash
6. Reboot System
Click to expand...
Click to collapse
2. After several months I want to upgrade the original H2OS to new version, so I unroot in Supersu first, when it ask me if I want to recover Boot Image, I say "Yes", and say "NO" when ask me if I want to recover Recovery Image. Then I upgrade to the new H2OS v13 (Android 7.1) using the Full package through TWRP, after that I reinstall TWRP 3.2.1, it was successful. But it doesn't ask me to allow it to make modification. I tried to install Supersu 2.82 and 2.82 SR5 using the same method as in tutorial, at the end of "Booting Image patcher" it shows
.........
-Calling user ramdisk patch script
---Failure, aborting
-Unmounting /system and /vender
-Done
Click to expand...
Click to collapse
Then I reboot to recovery, it return to official REC, not TWRP, and system says there is no root.
netsonic said:
Oneplus 5, Official ROM, H2OS, Android 7.1
1. First time, I followed https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 and successfully install TWRP and root using Supersu. I can goes into TWRP recovery without any problem. I notice that the supersu I installed in a systemless one, some apps can't get root access, like AD Away, Titanium Backup. But most apps can work with it. I used the one of the two root method in that tutorial as follows:
2. After several months I want to upgrade the original H2OS to new version, so I unroot in Supersu first, when it ask me if I want to recover Boot Image, I say "Yes", and say "NO" when ask me if I want to recover Recovery Image. Then I upgrade to the new H2OS v13 (Android 7.1) using the Full package through TWRP, after that I reinstall TWRP 3.2.1, it was successful. But it doesn't ask me to allow it to make modification. I tried to install Supersu 2.82 and 2.82 SR5 using the same method as in tutorial, at the end of "Booting Image patcher" it shows
Then I reboot to recovery, it return to official REC, not TWRP, and system says there is no root.
Click to expand...
Click to collapse
Just use the latest universal codeworks recovery and flash it via fastboot.
For root i suggest use of Magisk over Su, the latest 15.3 works fine for me.
What is the codeworks recovery? Is it "twrp-3.2.1-0-cheeseburger.img" on https://twrp.me/oneplus/oneplus5.html?
netsonic said:
What is the codeworks recovery? Is it "twrp-3.2.1-0-cheeseburger.img" on https://twrp.me/oneplus/oneplus5.html?
Click to expand...
Click to collapse
No, it's the -universal- one from here https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
I can flash universal TWRP and Magisk 15.3. But Magisk show "SafetyNet API Error"? How to fix it?
1. I have a G900T and am running Lineage_KLTE_userdebug 9 PPR1.180610.00970687de056 Test Keys.
2. I have developer options enabled and Root Access enabled for Apps and ADB.
3. I have downloaded open_gapps-arm-9.0-aroma-20190414.zip onto my phone.
4. I use TWRP 3.2.3-0 in recovery and attempt to install the .zip. I
5. I get the line 'Starting Aroma Installer version 2.80RC2 .... and then the phone reboots. No GAPPS text scrolling up, nothing like that. Just right back into TWRP.
Any help appreciated.
synpax said:
1. I have a G900T and am running Lineage_KLTE_userdebug 9 PPR1.180610.00970687de056 Test Keys.
2. I have developer options enabled and Root Access enabled for Apps and ADB.
3. I have downloaded open_gapps-arm-9.0-aroma-20190414.zip onto my phone.
4. I use TWRP 3.2.3-0 in recovery and attempt to install the .zip. I
5. I get the line 'Starting Aroma Installer version 2.80RC2 .... and then the phone reboots. No GAPPS text scrolling up, nothing like that. Just right back into TWRP.
Any help appreciated.
Click to expand...
Click to collapse
AFAIK aroma gapps do not play nicely with our klte version of TWRP.
Download one of the other arm-9.0 gapps packages and try again it should work fine.
I also have G900T and non aroma gapps work for me
Good luck :good:
BlueCyclone said:
AFAIK aroma gapps do not play nicely with our klte version of TWRP.
Download one of the other arm-9.0 gapps packages and try again it should work fine.
I also have G900T and non aroma gapps work for me
Good luck :good:
Click to expand...
Click to collapse
Confirmed i have also installed new rom today and gapps from aroma does not work but other ones work.