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

Help withAndroid N Preview 5

Hi Guys, i have 1 little problem.
im on the last Android N Preview 5 and i wannt to root it.
i have downloaded SuperSU 2.76 and TWRP 3.0.2.0
I rebooted to bootloader flashed thw twrp via Terminal, now i wanna boot into recovery because of the SuperSU zip, but i am stucking on TWRP Logo.
Phone is working normal, but i cant enter into recovery, anyone else has the same problem?
Thanks and best Regards,
Taker

You have to flash another version of TWRP... But, dude, i'm on the exact same case, same preview, and i can't get it to work. TWRP doesn't seem to work :/ I always got the god damn "no command" even if i follow some of the tutorials here...
EDIT : Try flashing the 3.0.0 or 3.0.1, and when all will be working (if you achieve, tell me how xD) update it.
EDIT 2 : I may find something, i'll let you know !

TWRP doesnt work with the developer previews without modifying the boot image.
If you want to root, you can use CF-Auto root.
You will still have the stock recovery.

Taker18 said:
Hi Guys, i have 1 little problem.
im on the last Android N Preview 5 and i wannt to root it.
i have downloaded SuperSU 2.76 and TWRP 3.0.2.0
I rebooted to bootloader flashed thw twrp via Terminal, now i wanna boot into recovery because of the SuperSU zip, but i am stucking on TWRP Logo.
Phone is working normal, but i cant enter into recovery, anyone else has the same problem?
Thanks and best Regards,
Taker
Click to expand...
Click to collapse
This is a known issue, Search the forum for the resolution. Basically TWRP won't work on the Android N on Encrypted device.

The solution is pretty simple. You need to decrypt your device's storage. TWRP currently doesn't work with encrypted N preview.
This could be easily done by flashing the modified boot image, that will disable forced-encryption. After that, you will need to format the current userdata partition to decrypt the storage.
Code:
fastboot format userdata
fastboot format cache
Once that is done, you can flash TWRP and then use SuperSU to root.
Another way to direct root is by using Cf-Auto-Root. But I am not sure about that specifically. While some users have succeeded, there are a few who have failed to root using Cf-Auto-Root.

Just use CF-Auto Root, it will do all the things.
Make sure you have unlocked your Bootloader and downloaded the good version of CF for your device.
Reboot your phone in bootloader mode, plug it to a computer, and just open the .bat (if you're on windows, or the equivalent for Mac / Linux). It will install SuperSU. When it's done, don't forget to download the TWRP Manager on the Playstore, and you'll have a working Recovery ! I did that, i know have a rooted nexus 6P on Android N preview 5
Also, lot's of Root's only apps will not work properly, because lots of changes took place on Android N. So make sure you follow some guide out there (exemple : Ex Kernel don't work if you don't tweak some things, same with Ad Away, so make sure you're googling)

I followed the premise of this thread here so all credits go to the OP http://forum.xda-developers.com/showthread.php?t=3410906 I flashed the latest Marshmallow vendor.img via fastboot, then flashed TWRP via fastboot. Booted into recovery from the bootloader then side loaded supersu using adb side load in TWRP. After that I rebooted to bootloader from TWRP and fastboot flashed the DP5 vendor.img and recovery.img. All is working well.

Galaxy j3 sm-j320zn trying to twrp???

Can anyone give me instructons on how to twrp n rot sm-j320zn ? I cant find the corrcy twrp for this model not having much luck thanks guys

koniva85 said:
Can anyone give me instructons on how to twrp n rot sm-j320zn ? I cant find the corrcy twrp for this model not having much luck thanks guys
Click to expand...
Click to collapse
Don't know if you still need the info, but I've just worked out TWRP. I've been rooted for ages but never saw your post; it's only because I decided to try TWRP again that I found you in a Google search.
TWRP that works on the J320ZN is for j3lte. To download: https://dl.twrp.me/j3lte/
Others have had issues installing SuperSU.zip in TWRP.... as did I. The only way to get root that would work is CF-Auto-Root..... because usually SuperSU.zip would then cause a bootloop. BUT of course, what I didn't realize at the time, was CF-Auto-Root once installed reflashed stock recovery! But what it DID enable me to work out (once it clicked in my head that this was going to be the issue and after I'd nearly set up my phone again) was that I was getting a dm-verity error.... something I know nothing about other than it's a new thing I have to do on my Samsung Galaxy Tab A. So MAYBE SuperSU wasn't installing because of that? Who knows.
Anyway, now I'm fully working with TWRP and root and it's sticking with no problems.
So install TWRP the usual way....(I used twrp-3.2.1-0-j3lte.img from the link above). If you need help with this quote me and ask, or look for a TWRP tutorial on j3lte (I know the J320YZ uses this TWRP and has a tutorial on how to install TWRP with Odin).
Then install the latest SuperSU.zip:
https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip through TWRP "Install" method.... it must be on your external SD card. Go to the "Install" button on TWRP menu, select storage to extSD and then find SuperSU.zip.
THEN I had to install the Dm-verity and Forced Encryption Disabler through TWRP "Install" method (so this file also needs to be on your external SD card):
https://androidfilebox.com/miscellaneous/dm-verity-and-forced-encryption-disabler/
I used no-verity-opt-encrypt-6.0.zip
Then reboot, and reset up your phone.
FINALLY!
Whether you need to do the dm-verity thing I don't know... I'm FAR from an expert. This was all through trial and error but it is the only way to keep root through TWRP without CF-Auto-Root.....FOR ME PERSONALLY.
You could try just TWRP and the latest version of of SuperSU.zip through TWRP....see if that works. If you get stuck in a bootloop, then I just flashed CF-Auto-Root with Odin and it fixed that.... then start the install process again, this time adding dm-verity patch AFTER SuperSU.zip.
If you want to skip TWRP and just root your phone, then the easiest way is to flash CF-Auto-Root with Odin. File at https://download.chainfire.eu/986/CF...etrieve_file=1.

How can I remove Magisk?

I've flashed Magisk, but because I can't get Xposed to work, I'd like to remove Magisk and install SuperSU, but I don't know how. I tried to flash the uninstaller via TWRP and it says everything is fine, but after rebooting it just stays installed. If I try to flash SuperSU anyway I get stuck on boot. I have to flash stock boot.img via TWRP and then Magisk magically reappears. I tried using MiFlash but it refuses to do anything. It says no permission.
One possible solution, I guess, would be to flash stock ROM via TWRP. Can this be done? Any other ideas? Or am I just stuck with Magisk until a new version is available?

Filip013 said:
I've flashed Magisk, but because I can't get Xposed to work, I'd like to remove Magisk and install SuperSU, but I don't know how. I tried to flash the uninstaller via TWRP and it says everything is fine, but after rebooting it just stays installed. If I try to flash SuperSU anyway I get stuck on boot. I have to flash stock boot.img via TWRP and then Magisk magically reappears. I tried using MiFlash but it refuses to do anything. It says no permission.
One possible solution, I guess, would be to flash stock ROM via TWRP. Can this be done? Any other ideas? Or am I just stuck with Magisk until a new version is available?
Click to expand...
Click to collapse
Magisk is pretty much "useless" for now. Because it is based on system-less root, and cannot be updated (because still in testing phase! Newer Xposed module from Magisk requires latest Magisk root binary, which is pretty out of option atm as we can't update to the latest binary). The only solution if you want to have proper root access is:
1. Head over to Xiaomi MIUI website and download the full stock ROM again, and then flash it via fastboot (choose flash_all_except_storage.bat if you want to preserve your data).
2. Once flashed, reboot back to bootloader and unlock it.
3. While still in bootloader flash the correct CF-Auto root boot image for your ROM (contains SuperSU 2.82 binary, https://desktop.firmware.mobi/device:1748)
4. Wait patiently and it will automatically reboot. Install SuperSU from Play Store if you want root management app.
5. If you need Xposed, download the Xposed apk from XDA and then install it normally (not via recovery).
6. ??? Profit
*DO NOT INSTALL permanent TWRP as it will cause your phone stuck in boot loop.

@soralz
Thanks for your help, but no luck. I understand what I'm supposed to do, but I can't get MiFlash to work. When I try to flash stock image I get a "Permission Denied" error. (I have unlocked my bootloader successfully). I tried flashing modified stock image from here But then I couldn't boot. My only solution is to flash stock boot.img via TWRP and I can boot, but I stay stuck with Magisk.
So far, the only options I can think of is to wait for a recovery-flashable ROM, a new software update or a new version of Magisk.

Filip013 said:
@soralz
Thanks for your help, but no luck. I understand what I'm supposed to do, but I can't get MiFlash to work. When I try to flash stock image I get a "Permission Denied" error. (I have unlocked my bootloader successfully). I tried flashing modified stock image from here But then I couldn't boot. My only solution is to flash stock boot.img via TWRP and I can boot, but I stay stuck with Magisk.
So far, the only options I can think of is to wait for a recovery-flashable ROM, a new software update or a new version of Magisk.
Click to expand...
Click to collapse
You couldn't boot, are you using permanent TWRP?
Have you tried download the Full ROM from here and run this (as attachment)?
http://en.miui.com/download-333.html
Btw, place the folder under 1 directory only eg: as attachment. (I tried in multiple directory eg: "D:\Phones\ROM\Stock ROM", it just wouldn't flash)

@soralz
OMG!!! I can't believe it. MiFlash refused to let me flash because I tried to do that from the wrong location. Weird??!!
Good. I’ve managed to follow your instructions and success!! Just a minor note, I couldn't flash the modified boot.img directly via fastboot, it still won't let me. But I just booted TWRP (without flashing) and then flashed it from there. Again, THANK YOU!
BTW, yes, I had flashed permanent TWRP and then unsuccessfully tried to remove it.

Filip013 said:
@soralz
OMG!!! I can't believe it. MiFlash refused to let me flash because I tried to do that from the wrong location. Weird??!!
Good. I’ve managed to follow your instructions and success!! Just a minor note, I couldn't flash the modified boot.img directly via fastboot, it still won't let me. But I just booted TWRP (without flashing) and then flashed it from there. Again, THANK YOU!
BTW, yes, I had flashed permanent TWRP and then unsuccessfully tried to remove it.
Click to expand...
Click to collapse
Oh you manage to fix that? Good for you then. And yes you cannot have permanent TWRP and SuperSU at the same time. The CF-auto root for me I just click root.bat and done. btw side note, you will lose root after each update, besure to check out the new patched boot image. I m sure in the future we will have automated process, don't need to re-root manually after each update

How do I get a stock backup after flashing magisk? (for ota)

So I've read a bunch of stuff and everything I've read tells me to do the same thing that I've already done. Also those thread seemed pretty old so....
Anyway I need a stock backup so I can perform OTA update but I don't have one. this is what I did
I used msmtool to start over
pushed through setup
unlocked bootloader switch in developer settings
unlocked bootloader in fastboot
updated android
fastboot boot twrp.img
wiped everything
flashed magisk.zip
(I didn't install TWRP because I am under the impression I can't pass safteynet with a custom recovery am I wrong about this?)
installed magisk.apk
So what step am I missing to save the stock backup so I can uninstall magisk for OTAs?
I had a Pixel for 3 years that had a broken fastboot and so I couldn't unlock the bootloader and never got to learn about the new AB partitioning until now. so I'm a little behind
Thanks

GbizzleMcGrizzle said:
(I didn't install TWRP because I am under the impression I can't pass safteynet with a custom recovery am I wrong about this?)
Click to expand...
Click to collapse
Unlocking the bootloader can make you fail safety net, much less Magisk if its not set up right. The recovery wont matter.
My guide here is for installing Lineage, however Step 5 will work for OOS too and make you pass safety net. So feel free to install TWRP.
I recommend Funk Wizards Guide on installing TWRP. Also note the section on EFS backups.
Look into TWRP backups, I dont use them, but I know its not straight forward unfortunately.

So when I'm flashing the magisk file in TWRP, does it save a copy of the image it's modifying? And where does it save that image? Also where should i put that image so I can uninstall-> Restore Images?