Database Users

Question about systemless root and TWRP

So I'm following the guide on rooting, unlocking, etc and confused about systemless root and traditional. I was going to do systemless to keep android pay alive and it seems that is the future. However, I'm at the point of installing TWRP. But the guide mentioned "TWRP isn't able t persist without modifying system, so you'll lose it after booting into Android, you'll need to flash/boot it to access it again". What does this exactly mean? I read it as that after I reboot my phone after doing something in TWRP, than TWRP becomes non existent. And I'd have to flash it every time I wanted to get into TWRP. Is this correct? Seems not very smart because if something happens on my phone, I'd like to be able to boot right into my TWRP recovery to restore a stable version.

I don't know why it says that but I allow TWRP to make system modifications and I have systemless root with AP working.
You definitely don't want to let TWRP install it's version of SuperSU though. When it gives you the option select "Do not install".

I would like to share my experience on flashing systemless root with TWRP on my Nexus 9:
1. Reboot to bootloader and perform fastboot boot TWRP.img (TWRP.img is the filename of TWRP IMG file). Yes, TWRP is temporary and won't keep after reboot)
2. If TWRP prompts you to decrypt /data partition, simply skip that
3. Don't allow /system modifications
4. Use adb sideload to install systemless SuperSU
5. Directly reboot to system after installation. The device may reboot multiple times, just let it finish.
SuperSU should now appear in the app tray. This method works well for me.

Much info on systemless root here
http://forum.xda-developers.com/nexus-6p/themes-apps/systemless-root-themed-apps-t3292105

ADB Sideload SuperSU on encrpyted phone

According to the following post, I should be able to gain root on my encrypted phone.
wgspoelstra said:
Yes, decryption is broken right now. On all versions of TWRP available, that support Oxygen OS 3.x.x, decryption is non-functional.
I have a workaround for flashing zips with an encrypted phone:
Boot into recovery, flash SuperSU over ADB Sideload, reboot phone.
You now have working root. Any zips you want to flash, place them in /system/media folder.
I use Root Explorer for this. When you boot back into recovery, mount /system and navigate to /system/media folder.
This way you can still flash all zips you want without decryption.
Click to expand...
Click to collapse
But I am having issues. Most notably, ADB does not recognize my phone unless I connect while in the OS or in stock recovery. If I connect while using any custom recovery (I've tried Hybrid and a few versions of TWRP), ADB does not list my phone when I run ADB devices. It's also very wonky trying to get stock recovery back on my phone afterwards, but that's a different issue.
While attempting to flash SuperSU when using stock recovery, the command sends the file and the phone begins the "update". It runs for about a second and then I get a "Installation Failed" message on my phone's screen. I've tried many different versions of SuperSU.
My current setup is the latest OOS (3.0.2) and stock recovery. The device is encrypted. My bootloader is unlocked, but I do not have root.
Could someone please help me out here? I have to have encryption on the phone for my work, but I really want to have root as well. Being able to customize my phone is why I went with OnePlus, but it's not proving to be any better than my Samsung Galaxy S4!!! Please help!

OP2 cannot upgrade from Oxygen OS 2.2.1/Cannot flash TWRP versions newer than 3.0.2-0

So.... Pokemon Go has a lot to answer for......
I have run into a really strange problem when trying to install an OTA on my *unrooted* Oneplus 2. I have been trying to fix this for days but I have completely run out of ideas.
I originally had a working stock Oxygen 3 (Marshmallow) rom with TWRP recovery on my device (not sure of the version). The device was rooted and apart from not being able to install OTAs, I was fairly happy with the setup. Then along came the Pokemon GO update that banned rooted devices. Ok, "big deal" I thought. I was quite content playing Ingress instead (a far better game by the way that doesn't rely on a "pay to win" structure). I really wasn't too worried but then I found out about "systemless root" and "Magisk". I thought that if I installed this correctly I could still play a bit of Pokemon GO when I wanted to and could toggle a root button in Magisk Manager to install OTAs when they became available.
This is where the problems started.
I followed a guide on how to unroot and install Magisk and "Phh's Superuser". The problem was that the Phh Superuser was being denied permissions for Magisk Manager, there were no pop up notifications prompting me to give it access, just toast notifications. I couldn't for the life of me figure out how to give it permission so the "enable root" slider button kept sliding back, not allowing root. This is when I used SuperSU ver 2.76 (Magisk version) and it seemed to work fine. I now had a stock Marshmallow rom with TWRP and Magisk Manager all working exactly how they should be. I could toggle root and play Pokemon GO, then return to a rooted state when I needed to.
"Awesome, mission accomplished." I thought. Now I just need to toggle root off, download the latest OTA and install it through Flashfire.
First I made a complete nandroid backup (as I've done with other devices many times before) through TWRP. I even copied the backup folder to my PC in case something went wrong.
Well, this is when the nightmare started.
The first mistake I made was to use Flashfire when it clearly stated that Oneplus devices were currently untested. Not sure if it was a big issue or not, but it was a mistake none the less. The second mistake I made was to not stop the stock recovery being replaced when prompted before the reboot. I assumed (and it even states in the app) that the custom recovery should be reverted back to the stock recovery when attempting to apply OTA updates.
So I went ahead and rebooted, waiting for the OTA to install. I'm fairly sure from memory that it went into the stock recovery, flashed the OTA and restarted.
This is when the phone soft bricked.
"Oh well, that is why I made the backup." I thought.
I reflashed TWRP in fastboot mode and attempted to restore my backup. No dice, the phone was still soft bricked.
(And by "soft bricked" and "boot looping" I mean the Oneplus logo was in the middle of the screen, "Powered by Android" was at the bottom and the two blue LEDs for the buttons either side of the fingerprint scanner/home button remained on. This for me was the tell tale sign of the soft brick because these two light go off after a few seconds after rebooting usually.
So from here I have tried EVERYTHING. All I really want now is a working stock (rooted) Marshmallow rom with TWRP. I have downloaded many different full rom zips and attempted to flash them through TWRP with no success, I have returned to stock recovery and tried flashing signed roms with no success, I've even tried flashing the official CM13 rom for Oneplus 2 (with the correct GAPPs and kernel) through TWRP with no luck.
But here is where it gets interesting......
There are a few things that are really weird...
1. I have always been able to get into Fastboot mode and ADB and Fastboot commands "work".
* Operations succeed but don't stick (for example trying to flash TWRP versions 3.0.2-1 and 3.0.2-2 through Fastboot mode result in no recovery being there at all.
2. I can flash TWRP recovery though Fastboot mode but ONLY VERSIONS 3.0.2-0 and lower. I can also successfully flash the stock recovery.
3. I can flash OxygenOS 2.2.1 but NOT ANY VERSION RELEASED AFTER THAT. Doing so results in the soft brick "bootloop" I mentioned earlier.
4. Attempting to flash the official CM13 rom for Oneplus 2 doesn't work either. Originally I got the error 7 message, but after editing "Updater-script" in the rom and re-zipping, the process seemed to work fine in TWRP but the reboot gave me... you guessed it... a softbrick.
I have flashed custom roms on a few different devices before so I'm not a COMPLETE newbie when it comes to this stuff, but I am by no means a developer or even anything close to one. I have bricked this phone in the past (long story, involved getting it without an invite and it being shipped to me with spyware on it) but I used a guide very similar to this and it worked a treat.
www(dot)androidbrick(dot)com/unbrick-oneplus-one-two-3-qualcomm-hs-usb-qdloader-9008
So, thinking that this process would format all partitions and start me from scatch I tried it. It worked fine but I was still unable to upgrade from Oxygen OS 2.2.1 or install TWRP versions 3.0.2-1 or 3.0.2-2.
I have tried all sorts of things. I have wiped, flashed and wiped again. Factory resets, dirty flashes, clean flashes.... everything. All sorts of different sources for the TWRP images and Oxygen roms... nothing seems to work.
It's just so weird considering it's not a hard brick... just a soft brick.
So I really need my phone so I am sitting on this current build because it is the only one that works.
Here are some details of the current build I am using. (using CPU-Z app)
Model: Oneplus 2 (ONE A2001)
Android version: 5.1.1
Oxygen OS version: 2.2.1
Bootloader: Unknown
Build ID: ONE A2001_14_160226
Java VM: ART 2.1.0
OpenGL ES: 3.1
Kernel Architecture: aarch64
Kernel version: 3.10.49-perf+ (56)
Root access: Yes
Super user app: SuperSU Free v2.46 (Chainfire)
OEM unlocking: Enabled
USB debugging: Enabled
And these are some of the ZIPs and IMGs that refuse to be flashed to my device.
TWRP-3.0.2-1-oneplus2
TWRP-3.0.2-2-oneplus2
Grarak's TWRP recovery IMG for Oneplus2 (modified to install CM13) according to this guide:
missingtricks(dot)net/oneplus-2-official-cyanogenmod-13
cm-13.0-20160924-NIGHTLY-oneplus2
OnePlus2Oxygen_14_OTA_019_all_1606041303_bd42fc5cc5cc4ab2
And also my TWRP backup named 2016-09-16--09-44-09
I am really at a loss as to what to do next. ANY help ANYONE could give me would be greatly appreciated. I have been all over the net looking for ways around this bt have had no luck.
As I've said, I'm not a huge tech head, but I'm not a newbie either. The only thing I can think of is that somehow one of the partitions (maybe boot? ) may have been corrupted somehow when messing around with systemless root. But I don't know how considering it's "systemless". If anyone knows how to check for corrupted partitions on the Oneplus 2 please let me know and I'll try it. Maybe formatting these partitions might help (????), but I don't want to permanently brick my phone.
But I don't know how I've got this particular build working if one of the partitions has been corrupted. And the corrupted partition thing is just a guess.....
Please, anyone, someone point me in the right direction. Again, any and all feddback is welcomed and would be very much appreciated.
This is all Pikachu's fault.

Kamakiriash said:
A very long post...
Click to expand...
Click to collapse
The normal way too update from OOS 2 to OOS 3 is:
Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
Reboot recovery via TWRP so that you now have a recovery that's compatible with the new bootloader
Wipe data, cache & dalvik-cache (but not internal storage)
Flash the OOS 3 signed flashable zip again to update the system
Flash one of the modified SuperSU zips if you want root
Reboot system
All the files you need are in post #1 of this thread.

Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:

Kamakiriash said:
Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:
Click to expand...
Click to collapse
Glad you're sorted.
Not sure about Magisk as I've never used it.
CM13 is OK but whether it's worth you moving to it is your choice. Personally, I prefer TipsyOS!

Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Click to expand...
Click to collapse
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
Click to expand...
Click to collapse
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?

Aood said:
Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?
Click to expand...
Click to collapse
I don't have a OP2 anymore but that post was seven months ago and the instructions worked for numerous users.
Don't enable zip signature verification in TWRP - it's unnecessary.
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.

thanx for replay Spannaa,
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.
Click to expand...
Click to collapse
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.

Aood said:
thanx for replay Spannaa,
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.
Click to expand...
Click to collapse
Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?

Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?
Click to expand...
Click to collapse
Yes, rebooting recovery "directly from TWRP"
and bootloader loader is unlocked,..
anyway it's not important to fix the phone, it's almost one year since last time I use it, yesterday I saw it in the drawer and try to figure out the issue..,

"System" deleted, mild softbrick. Best way to fix?

I am no noobie when it comes to android rooting since I root and flash all of my android devices. But the axon 7 is a really tough son of a b*tch.
I got it brand new. Unlocked the bootloader then proceeded to update to marshmallow just so I can get nougat on my device. Then I installed TWRP so I can flash supersu, xposed and an audio mod zip. I believe this audio mod is what killed my devices since it was not booting into the os. Just stuck at the flashy axon booting screen. I booted into TWRP, deleted data, system and system storage and installed the nougat 2,6gb "update.zip" file. Since then the os is not booting at all, its just stuck at the booting screen, the warning because of the unlocked bootloader. And also, now, stock recovery is installed.
I have an idea how to fix this I am rather cautious so thats why Im asking the experts here first
EDIT: I have the 2017G Version

I have an A2017U, but if you can get your hands on an official Marshmallow zip, then that should hopefully let you boot. From there you can OTA update back to Nougat, then you just need to figure out how to install TWRP again.
Another recovery method is to flash EDL files with MiFlash while your phone is booted into EDL mode.
As for audio mods, I just use Arise, it's very comprehensive and has never bricked my phone.
I have an idea why you can't boot after flashing the Nougat zip: you triggered dm-verity. You must also flash a root zip that patches out the dm-verity. Or you can use @jcadduono's "no verity opt encrypt" zip as an alternative if you don't want to root. Your system and cache partitions should be formatted as ext4, and data should be F2FS. I recommend a full wipe of all partitions except the MicroSD.

GriechischerYoghurt said:
I am no noobie when it comes to android rooting since I root and flash all of my android devices. But the axon 7 is a really tough son of a b*tch.
I got it brand new. Unlocked the bootloader then proceeded to update to marshmallow just so I can get nougat on my device. Then I installed TWRP so I can flash supersu, xposed and an audio mod zip. I believe this audio mod is what killed my devices since it was not booting into the os. Just stuck at the flashy axon booting screen. I booted into TWRP, deleted data, system and system storage and installed the nougat 2,6gb "update.zip" file. Since then the os is not booting at all, its just stuck at the booting screen, the warning because of the unlocked bootloader. And also, now, stock recovery is installed.
I have an idea how to fix this I am rather cautious so thats why Im asking the experts here first
EDIT: I have the 2017G Version
Click to expand...
Click to collapse
If you still have TWRP, download Raystef66's B09 TWRP flashable Stocksystem and Bootstack, plus Magisk 15.2. Flash everything then wipe data.
What broke your device was probably Xposed.
Also, which audio mod are you talking about? Ainur, V4Android, V4ARISE, AK4490 patch, maybe some other?

Thanks for the help! i Managed to flash TWRP in EDL mode (black screen). Then I proceeded to flash nougat B9. I was up all night reading about it and searching tutorials how to flash stock from TWRP. I installed Bootstack and System, supersu 2.79 and xposed. First boot did not work but that was actually in the guide so I had to flash system and root again. My data partition is ext4 and everything works good now. I hope it wont make any problems.
The audio mod was "divine 10" or something. I will try the ones you have mentioned.
Thanks for all the help

GriechischerYoghurt said:
Thanks for the help! i Managed to flash TWRP in EDL mode (black screen). Then I proceeded to flash nougat B9. I was up all night reading about it and searching tutorials how to flash stock from TWRP. I installed Bootstack and System, supersu 2.79 and xposed. First boot did not work but that was actually in the guide so I had to flash system and root again. My data partition is ext4 and everything works good now. I hope it wont make any problems.
The audio mod was "divine 10" or something. I will try the ones you have mentioned.
Thanks for all the help
Click to expand...
Click to collapse
Xposed usually needs a 2 or 3 minute first boot for some reason, just sayin

Need instructions to install Magisk systemless root in S7 Edge running 8.0

Hi guys,
I have gone thru the forum to install Magisk systemless root in S7 Edge running 8.0 but have few questions.
1. Is TWRP mandatory to install Magisk for systemless root?
2. If above point is yes, then will the device be eligible for OTA even with TWRP recovery?
3. Please provide steps to install Magisk systemless root in S7 Edge running 8.0 latest October patch
Thanks in advance.

mpadhu said:
Hi guys,
I have gone thru the forum to install Magisk systemless root in S7 Edge running 8.0 but have few questions.
1. Is TWRP mandatory to install Magisk for systemless root?
2. If above point is yes, then will the device be eligible for OTA even with TWRP recovery?
3. Please provide steps to install Magisk systemless root in S7 Edge running 8.0 latest October patch
Thanks in advance.
Click to expand...
Click to collapse
Go Here https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-root-android-8-0-oreo-t3840271
1. U need TWRP for flashing Magisk.
2. When ur intentions are gaining root access, u should forgo OTA.
3. The above link has everything u need.

joeljose1001 said:
Go Here https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-root-android-8-0-oreo-t3840271
1. U need TWRP for flashing Magisk.
2. When ur intentions are gaining root access, u should forgo OTA.
3. The above link has everything u need.
Click to expand...
Click to collapse
Thank you for your time and response. There is something called systemless root which will hide the root from the system and also allows official OTA updates.

mpadhu said:
Thank you for your time and response. There is something called systemless root which will hide the root from the system and also allows official OTA updates.
Click to expand...
Click to collapse
From what I know, when you download an OTA and prompt your device to install it, your Android system performs a series of checksums to ensure that your /system, /boot, /recovery, and /vendor (or /OEM) partitions are unmodified from their original stock configuration.
The benefit of Magisk is that it does not modify the system partition, but while installing Magisk, the first thing it does is patch boot image. So you might have to restore the original boot image for the OTA to work.
Also, the OTA is designed to be installed via the stock recovery which has been overwritten with TWRP. So, I think u will face a problem there too.
I'm not saying that it's impossible to get an OTA update. It just might not be as easy as u r used to.

joeljose1001 said:
From what I know, when you download an OTA and prompt your device to install it, your Android system performs a series of checksums to ensure that your /system, /boot, /recovery, and /vendor (or /OEM) partitions are unmodified from their original stock configuration.
The benefit of Magisk is that it does not modify the system partition, but while installing Magisk, the first thing it does is patch boot image. So you might have to restore the original boot image for the OTA to work.
Also, the OTA is designed to be installed via the stock recovery which has been overwritten with TWRP. So, I think u will face a problem there too.
I'm not saying that it's impossible to get an OTA update. It just might not be as easy as u r used to.
Click to expand...
Click to collapse
Got your point. Thank you. I read that Magisk can be installed without root or even custom recovery.
The below is taken from the official Magisk thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
How to download or extract the stock boot image file from my official ROM?
"Via Magisk Manager:
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/Download/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img"