Coming from a Nexus 5.
Happy with the 4g after a week.
Much better battery life.
I unlocked the Moto yesterday.
I have a few questions.
Want to have more control over the phone.
1. If i root the phone and install twrp i won't be able to get 7.0 when they release it for this phone?
Unless i flash a factory image? If thats the case does my phone have to be unlocked and unrooted again?
You'll need an unmodified system partition, i.e. the root method should be systemless and don't let TWRP modify it, and you'll also need the stock recovery.
This is what I do:
I install twrp + magisk + systemless root + systemless xposed
When a new OTA arrives I flash stock boot + stock recovery. Then I take the OTA
Then I reflash twrp , backup boot and reflash magisk + systemless root + systemless xposed
The only 2 partitions modified are recovery and boot all the rest is stock.
Subsequent OTAS -> resotore boot, flash stock recovery, take OTA + reflash twrp, backup boot, reflash magisk + systemless root + systemless xposed
one more question
So if i'm not worried about ota's
Can i just flash twrp and supersu
Then flash whatever rom's the dev's come up with using twrp as i did with my nexus 5?
Thanks again
Yes
Related
Hi,
I lost root after updating to JWR66Y, and when I open up SuperSU, it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
So I turned off my phone, pressed volume down+power button to go into TWRP and re-flash SuperSU.zip, but the screen only shows broken android with exclamation mark on it.
So, my question is, what do I do? I want to flash TWRP via adb and then flash SuperSU.zip via TWRP. Is that the correct procedure? I'm afraid if something goes wrong I won't have a way to restore my nandroid backup or something.
Thanks.
you always lose root if you take an ota update or flash the factory img. when you flash stock, its just that, stock. its been that way since the beginings of android.
you want to fastboot(not adb) a custom recovery, then flash the latest su binaries via your custom recovery.
simms22 said:
you always lose root if you take an ota update or flash the factory img. when you flash stock, its just that, stock. its been that way since the beginings of android.
you want to fastboot(not adb) a custom recovery, then flash the latest su binaries via your custom recovery.
Click to expand...
Click to collapse
To add on what simms22 said,
SuperSU 1.60 flashable zip: http://download.chainfire.eu/350/SuperSU/UPDATE-SuperSU-v1.60.zip
I am at a loss.
I am crazy and like to restore to stock whenever there is a security update or anything like that just so I can remember how to flash recovery, boot images, etc.
So I had the **18-3 with the Feb update and was rooted with SuperSU ( don't recall which ) and TWRP 3.0.0-1 I believe.
When I got the notification for the new security update I promptly unrooted, and flashed the stock 24.49-18-4 / 24.221.4 firmware and am able to boot.
I have installed the latest TWRP and can boot to it, and reboot to system all I want.
I have done this process twice now because the first time I tried to install SuperSU (2.76??) after all this I got stuck on the moto logo and could not boot.
Other threads have mentioned you cannot root with SuperSu on 6.0, or something to that effect.
So I am not unrooted (I believe) on 24.49-18-4 and want to root to be able to get SuperSU and the rest of my root apps up and running.
What do I do from here?
Fixed: http://forum.xda-developers.com/moto-x-style/help/rooting-stock-xt1575-marshmallow-6-0-t3353812
Su 2.62-3 for root & boot up normal then flash over Su 2.76
Done.
I'm about to provision my One Plus 5 for use I will be running it with TWRP a unencrypted data partition (makes restores easier) and root via Magisk day one.
I'm curious if I'm running it in this configuration when an OTA comes down the pipe will it do any of the following?
re apply fastboot oem lock?
flash the recovery to stock recovery?
remove magisk?
re-enable dm-verity?
Curious if the process after an OTA apply is to re-flash TWRP potentially re-apply magisk? Does applying ota mess with your data partition if you already decrypted it?
Also was thinking about leaving the data partition decrypted so I can push things to it via ADB or manipulate it when it's in a non-functional state can anyone here comment on if that's still possible while encrypted? And if so what dis-advantages of leaving it encrypted I hear one is you have to remove the lock screen password before you create a backup since the keys are not backed up and you might be locked out after a restore.
With some more research I've answered my own question I'll put them here in case anyone wants to refer to them in the future.
TWRP users will lose TWRP after a flash of the OTA.
Root will be lost regardless if you flash using TWRP or stock.
Data is not touched during flash so it should stay as is.
DM-verity requirement is unknown.
For rooted users it's better to do a full flash with TWRP OTA through TWRP will cause a problem.
Actually, you won't get the small incremental OTA, you will download the complete 1.5 - 2gb rom... This happens when you have root whether you have got TWRP or stock recovery.
Root will always be lost, yes but if you flash with TWRP you can flash magisk oe SuperSU immediately afterwards to gain root again. Not having TWRP you will need to either boot TWRP or install it to install root again.
DM-Verity, I have never had any problems with this after flashing and then rooting...
I dirty flash the 4.5.10 and i had to reflash the ROM + no_verity_op5.zip. My first and only issue was a sort of bootlop to the recovery.
So wait. If I flash the OTA, then flash Magisk, I will have root and lose TWRP, right?
Then could I use some app like Flashify or the TWRP app to install the recovery?
I don't own a PC right now and want to know if it's possible.
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?
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"