So im rooted on my G5Plus US can i just updated it or do i have to install in some other way?
Yes, you can!
However, it's not trivial. I'm writing a guide.
In any case, you need to use SYSTEMLESS root (for example, with Magisk), and a backup of your SYSTEM, OEM, RECOVERY & BOOT partitions.
And to complete the OEM backup with TWRP we need that some developer will update it.
Regards.
Related
I installed twrp and SU. Really the only reason I did it is because I use titanium backup to back up and restore apps and such. Otherwise I really don't need root.
I have two questions.
First Question: Can I re-lock the boot loader if I have TWRP and SuperSU installed? If not how can I use Android pay? Is there a work around? It's not allowing me to because it can't verify
Second Question: The OTA 6.0.1 won't stick. I'm pretty sure I've done one other over the air update (at least I thought I did, I may be remembering incorrectly) and it worked just fine. But for some reason 6.0.1 isn't taking. Any ideas?
If you don't need root what you can do is download the 6.0.1 imag direclty from google, put it in your adb/fastboo folder and use the flash-all command and it will erase root, twrp and it will be like you just got it from the factory. The only thing that would be still there is the unlocked bootloader. Once you've performed the flash-all command, you can simple lock the bootloader again. That's if you want to get rid of Root and Twrp.. If not, you can try a Rom like Chroma that has android pay working on it.. Here's the instructions. Hope this helps: http://forum.xda-developers.com/showpost.php?p=64269166&postcount=2338
Edit: Make sure you follow the systemless root instructions from that link to get android pay to work...
So I cannot lock the boot loader if I have root and twrp installed?
I really don't want to use a Rom. I'm happy with stock, just want to be able to use titanium backup.
And are ota updates not working if you have twrp installed?
OTA updates won't flash properly if you have TWRP installed, though I heard there is a way to extract the components of the update you want to apply so you can preserve root and custom recoveries while still updating. Sorry I don't know where the instructions are though.
No you can't lock the bootloader with TWRP installed, it can result in a brick.
I would not lock the bootloader unless you are 100% stock. You open yourself up to unrecoverable bricks. As for the update if you download the image from google you can just flash the individual partitions in fastboot. This way you can preserve your data. Heisenburg has a great guide here: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 You will loose root but getting it back just involves reflashing the SuperSU-v2.62-3-20151211162651.zip from this thread http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344/post64161125#post64161125
I am a little unclear about how to flash new images such as the recent 3.2. I want to update my shield TV Pro and not lose root.
I currently have the bootloader unlocked, which is necessary in order to apply SU for rooting. I installed SU via TWRP which has been flashed to the recovery partition. Should I ONLY install the system.img. (I'm uncertain what the vendor.img contains although but I'm pretty certain it can be flashed and not loose root.) Of course I would prefer to keep the custom recovery (TWRP) so why flash over that?
I suspect that if I flash the boot.img (isn't that what is "unlocked" with the "oem unlock" command?) I will have to do it again before I can flash SU using TWRP. This takes HOURS and I would like to avoid it if the 3.2 boot.img is unnecessary. Am I right that the boot.img contains the bootloader?
tman777 said:
I am a little unclear about how to flash new images such as the recent 3.2. I want to update my shield TV Pro and not lose root.
I currently have the bootloader unlocked, which is necessary in order to apply SU for rooting. I installed SU via TWRP which has been flashed to the recovery partition. Should I ONLY install the system.img. (I'm uncertain what the vendor.img contains although but I'm pretty certain it can be flashed and not loose root.) Of course I would prefer to keep the custom recovery (TWRP) so why flash over that?
I suspect that if I flash the boot.img (isn't that what is "unlocked" with the "oem unlock" command?) I will have to do it again before I can flash SU using TWRP. This takes HOURS and I would like to avoid it if the 3.2 boot.img is unnecessary. Am I right that the boot.img contains the bootloader?
Click to expand...
Click to collapse
try flashfire by chainfire search xda forums app is on playstore
I have chainfire. However my main question is whether I should flash the boot image? Does chainfire patch or unlock the bootloader?
if you are all ready rooted then your bootloader IS ALREADY unlocked i have used it default settings
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.
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"
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?