Hi,
I have a somewhat general question about different OTA update application methods for OOS when Magisk and potentially TWRP is involved.
I'm still running 3T on 4.0.3 (as rooting with SuperSU broke OTA updates) and will be clean flashing Android P release once OP releases one.
Going forward, I'd like to be in a state where I have a Magisk-rooted phone, able to use TWRP, and receive OTA updates. Generally I've seen these two methods being recommended:
1) With TWRP:
a) download full image from OP site;
b) boot to TWRP, flash said image, followed by re-flashing TWRP as flashing full image restores stock recovery;
c) wipe dalvik & cache
d) reboot to TWRP & flash Magisk
2) Without TWRP:
a) restore stock recovery if using custom one;
b.1) restore stock boot image of currently installed android version by flashing it via fastboot; OR
b.2) restore stock boot image using Magisk's 'RESTORE IMAGES' option;
c) reboot and follow through with the OTA update from your phone menu (as you'd do normally with completely stock setup);
d) download stock boot image for the version you updated to, and patch it with Magisk Manager;
e) flash this boot image again using fastboot;
Now, my questions:
1. Which of the two methods above should be preferred?
2. Could either of the two methods used for OTA updates without losing data nor apps/settings?
3. Is there anything inherently different between flashing full image as in method 1) vs. going for the regular incremental OTA update as in method 2)?
4. for option 2), should b.1 OR b.2 be used? Magisk tutorials page seems to be recommending the latter.
I like to keep things simple, so if I'm going to install TWRP, then that's what I use for updates.
There's no benefit in swapping recoveries, especially since you end up with the same result.
By the way, it's been a long time since TWRP stopped patching kernels to prevent it being replace by the stock recovery. So, your step 1 is simpler:
a) download full image
b) flash it in TWRP
c) flash Magisk
And that's it. There's no need to wipe Dalvik or cache. I've not wiped either of these for years (and I've updated countless ROMs) and I've never had an issue requiring me to wipe them.
Sent from my OnePlus 3T using XDA Labs
Thanks for the reply.
Any idea if there's anything specific that needs to be taken care of depending on whether phone is encrypted or not?
Any specifics re. Android P releases, or old flashing methods should work the same?
laur89 said:
Hi,
I'm still running 3T on 4.0.3 (as rooting with SuperSU broke OTA updates) and will be clean flashing Android P release once OP releases one.
Click to expand...
Click to collapse
There is nothing stopping you from installing an Oreo version OOS (such as the latest stable 5.0.8). Who knows when stable P is coming. Maybe soon, maybe not that soon?
Just download the full zip, flash in TWRP, and flash Magisk right away (do not reboot before flashing Magisk). Same process BillGoss suggested in a previous reply.
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
laur89 said:
Hi,
2) Without TWRP:
a) restore stock recovery if using custom one;
b.1) restore stock boot image of currently installed android version by flashing it via fastboot; OR
b.2) restore stock boot image using Magisk's 'RESTORE IMAGES' option;
c) reboot and follow through with the OTA update from your phone menu (as you'd do normally with completely stock setup);
d) download stock boot image for the version you updated to, and patch it with Magisk Manager;
e) flash this boot image again using fastboot;
Click to expand...
Click to collapse
I wouldn't mess with any of this. The phone is modded, and it seems that the above process is just trying to "trick" the system into thinking it has never been modded, so you can do an incremental update. For no actually benefit, and just making a much more complicated process.
Full zip makes for a cleaner install than incremental, anyway. You can keep your user data in either case, so again, you aren't gaining anything with incremental (versus full zip) OTA.
---------- Post added at 01:03 PM ---------- Previous post was at 12:55 PM ----------
laur89 said:
Any idea if there's anything specific that needs to be taken care of depending on whether phone is encrypted or not?
Click to expand...
Click to collapse
Well, are you encrypted, or not?
I've always had the phone encrypted, so can only say for certain about that condition. If it is encrypted, it will stay that way. There are a few TWRP builds that don't play well with encryption. But for the most part, just flash the update as stated previously, and you don't need to worry about encryption.
If decrypted, I believe flashing by TWRP will keep it that way. If you flash an update by stock recovery, I think it will force back to being encrypted. But again, I can't say for certain, as I've always been encrypted.
laur89 said:
Any specifics re. Android P releases, or old flashing methods should work the same?
Click to expand...
Click to collapse
The community beta P release is having issue with devices which are bootloader unlocked and encrypted. If the device is just one of those (or neither) and not both, then it seems to work fine in most cases.
For the stable P release, I'm guessing it will work the same as the "old flashing methods" which has been described above. But we won't know for certain, until a stable P build is released.
Related
hi! my OP3T is rooted and have a custom recovery (TWRP). now i get an ota update. i have read somewhere in this case its necessary to flash the ota manually in TWRP because i will lost root after this and if i flash it in TWRP i can after ota update flash superSU and will have no problems after reboot the phone.
i have tried this but get "Error 7" in TWRP while flashing ota update. isn't it possible at this way? what is my mistake?
thanks a lot for help and pardon for my bad english!
RotesMeerJogger said:
hi! my OP3T is rooted and have a custom recovery (TWRP). now i get an ota update. i have read somewhere in this case its necessary to flash the ota manually in TWRP because i will lost root after this and if i flash it in TWRP i can after ota update flash superSU and will have no problems after reboot the phone.
i have tried this but get "Error 7" in TWRP while flashing ota update. isn't it possible at this way? what is my mistake?
thanks a lot for help and pardon for my bad english!
Click to expand...
Click to collapse
I have a detailed thread already running on how to update here
http://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
I shall keep it up to date with further releases
Sent from Funk Tuned 3T
okay, i have searched in the wrong category thanks a lot for the link!
this thread can be closed.
how can i receive the updates when i root my phone?
and is there anyway to change the emoji without root?
a7mad-911 said:
how can i receive the updates when i root my phone?
Click to expand...
Click to collapse
You should still receive OTA notifications with root. And it should detect you have root, and will download the full update zip, and it will install with TWRP.
Otherwise, you can manually download the full zip update from Funk WIzard's thread which he linked in Post #2 above (which also has detailed instructions on how to update when rooted and TWRP installed).
Works like a charm with magisk 13.6
I just did it with my OP3t and was super easy.
1) download update.
2) go to hidden folder .Ota
3) move zip file to another folder
4) put Magisk in the folder, too
5) reboot to recovery, flash ROM, then Magisk
6) wipe dalvik/cache and reboot
Edit: updated following testing of redpoint73's correct advice
LeighR said:
4) put twrp and Magisk in the folder, too
5) reboot to recovery, flash ROM, then twrp, then Magisk
Click to expand...
Click to collapse
As long as you already have TWRP installed (which is the situation we are talking about) you just need to flash the OTA update zip, then flash Magisk.
Magisk prevents TWRP from being over-written (replaced) with stock recovery. In other words, you don't need to flash TWRP, since TWRP is already there.
redpoint73 said:
As long as you already have TWRP installed (which is the situation we are talking about) you just need to flash the OTA update zip, then flash Magisk.
Magisk prevents TWRP from being over-written (replaced) with stock recovery. In other words, you don't need to flash TWRP, since TWRP is already there.
Click to expand...
Click to collapse
This means I will keep all apps/settings/files?
Thank you.
JayDz said:
This means I will keep all apps/settings/files?
Click to expand...
Click to collapse
Yes.
Although I will caveat that with my rule of thumb: "hope for the best, prepare for the worst". In that a "dirty" flash of an update is often possible (saving your a lot of work setting up the device again). But you should still be prepared to wipe and do a "clean" install if you run into any problems. So back up your data, by your method of choice, before you try to update.
In particular, for a major update (such as OOS 4.x to 5.x) a clean install (default wipe in TWRP - data, cache and Dalvik) is typically advised.
Shall?? You used the word 'shall' properly in context? Kudos to the school system (I here assume India's) you attended, and to you for paying attention, using the 'King's English' in it's most proper form.
Hello Community,
I am using a custom recovery (TWRP) and my phone is rooted. Can I update this build update in an official way (like in the picture) or do I need to flash a complete ROM? And if I need to flash a complete ROM, has someone the ROM from the new build update? Wasn't able to find it until now.
Sincerely PIPT
You need to do some reading before trying anything more, because you're likely to brick your phone and then you'll really be in trouble.
Yes, you can download and apply updates without having your data wiped and starting from scratch, but there's a very specific process to do this. Failing to follow the proper steps will result in a bricked device. Save yourself some trouble, and learn more about what you're doing before you make a mistake that you can't fix.
I had the same situation as you. I first tried update with OTA, it downloaded and rebooted and failed.
When it booted again, and ran the OTA updater it downloaded the full ROM package, rebooted and installed fine in twrp.
You should flash full rom over your system like dirty flash, just wipe dalvik and cache after flashing completed, then reboot.
This is safe way if you have root and twrp
Keep in your mind you will lose root and twrp after upgraded, flash them again ?
chazarss said:
You should flash full rom over your system like dirty flash, just wipe dalvik and cache after flashing completed, then reboot.
This is safe way if you have root and twrp
Keep in your mind you will lose root and twrp after upgraded, flash them again
Click to expand...
Click to collapse
You also have to flash supersu after dirty flashing the rom. Also I personally wipe Dalvik and cache before flashing the rom. I've never had any issues with the procedure I follow.
---------- Post added at 17:19 ---------- Previous post was at 17:17 ----------
olskar said:
I had the same situation as you. I first tried update with OTA, it downloaded and rebooted and failed.
When it booted again, and ran the OTA updater it downloaded the full ROM package, rebooted and installed fine in twrp.
Click to expand...
Click to collapse
If you have a custom recovery or you're rooted never install an OTA. you need to have official recovery to install an OTA. Dirty flashing the full rom is the best way to update.
PIPT said:
I am using a custom recovery (TWRP) and my phone is rooted. Can I update this build update in an official way (like in the picture) or do I need to flash a complete ROM? And if I need to flash a complete ROM, has someone the ROM from the new build update?
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
In addition to the needed files, the thread has detailed instructions on how to update (stock phone vs. rooted with TWRP) in Post #3 of the thread.
Based on this, you must flash the full ROM zip (as opposed to the partial OTA "patch"), if you are rooted. But you should still be able keep your data. But I would still back up what is important to you, before updating. Just common sense to have your important data backed up, especially before large OS updates.
I'm actually about to do this myself today (rooted OOS 4.0.3 to 4.1.1), so I'll let you know how that goes.
bonham1988 said:
If you have a custom recovery or you're rooted never install an OTA. you need to have official recovery to install an OTA. Dirty flashing the full rom is the best way to update.
Click to expand...
Click to collapse
You can flash full OTA packages through TWRP. You can't flash the smaller patches, but if it's the full firmware, then TWRP 3.0.4.1 will work just fine. Just be sure to flash SuperSU or Magisk before booting to retain root.
redpoint73 said:
See here: https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
In addition to the needed files, the thread has detailed instructions on how to update (stock phone vs. rooted with TWRP) in Post #3 of the thread.
Based on this, you must flash the full ROM zip (as opposed to the partial OTA "patch"), if you are rooted. But you should still be able keep your data. But I would still back up what is important to you, before updating. Just common sense to have your important data backed up, especially before large OS updates.
I'm actually about to do this myself today (rooted OOS 4.0.3 to 4.1.1), so I'll let you know how that goes.
Click to expand...
Click to collapse
Can I install stock recovery too to make OTA updates and then after the update install TWRP and flash root again? I only ask because I want to do the smaller updates (bug fixes and improvements) too and won't wait for OS and Firmware updates to update my build, because not every little update is listed to get installed manually.
But all in all thx for so many answers
I updated officially with stock recovery and full it's zip, DM Verity has been triggered. It's annoying, anyone else?
edit: fixed it, still annoying that a stock rom tripped it tho.
Update: A working solution is listed below for reference.
A detailed tutorial for encrypted and rooted Nougat OOS users on how to flash Oreo OxygenOS without running into the infamous boot loop issue.
Step 1: Remove all fingerprint & pin from the device
Step 2: Backup everything on your PC/Laptop
Step 3: Reboot the device to TWRP bootloader
Step 4: Using a PC/Laptop, flash Blu_Spark TWRP via ADB command
Step 5: Reboot device to TWRP
Step 6: Wipe dalvik, cache, system & internal partition
Step 7: Format device
Step 8: Copy Oreo Rom & no_verity_mod file onto your device
Step 9: Flash Oreo under TWRP
Step 10: Flash TWRP again
Step 11: Reboot to recovery again
Step 12: Flash Magisk Beta for root (I used Magisk beta 14.5)
Step 13: Flash no_verity_mod file
Step 14: Reboot into Oreo Oxygen OS
Your device is now decrypted, rooted and running the latest stable Oreo OxygenOS build.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Seeing as a couple of forum members have messaged me regarding the official update of Android Oreo, I would like to make a proper discussion thread for it.
I just want to make it clear that HatRiGt has made an outstanding effort by making a tutorial thread. -> ([OFFICIAL] [Stable Oreo 8 ] Oxygen OS 5.0 Update [Tutorial-Root] [Mirror] by HatRiGt)
With that said, I believe the title is somewhat misleading. Since a lot of members are under the impression that this Oreo update will be a simple and straightforward process like all previous Nougat updates, except for it's not.
Stock OxygenOS
Rooted with Magisk v14
TWRP Recovery
Device already encrypted
Almost everyone with the device configuration listed above has run into some sort of serious issues, such as boot loop, file system decrypted/corrupted, or a complete data loss.
So far, it seems like the few groups of members that have managed to update their device without any data loss are either users that have flashed the Oreo Beta rom, or users with a non-rooted & stock recovery device. Almost everyone else is facing some form of issues.
I understand that some people have suggested that rooted users should first format the internal storage, before proceeding with the Oreo update. I personally feel that it is an inconvenient method of OS update, since many of us have a huge collection of photos, media files and app settings etc... to worry about.
The purpose of this thread is to address the aforementioned problem for rooted OOS users and to come up with a solution, so that everyone can enjoy this latest stable release of Android Oreo.
Any comments or thoughts are welcomed.
Maybe a stupid idea, but I am a bit noobish in this. Running stock 4.5.15, rooted, K2 TWRP and Magisk.
Is it not an option to just flash stock recovery (via ADB or Root Toolcase), then remove/deinstall Magisk and use the OTA update? After that flash Blue Spark via ADB, reflash Magisk and be good to go?
Unfortunately this is my daily driver company phone so I haven't the time to experiment with it at the moment.
I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.
Malcol13 said:
I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.
Click to expand...
Click to collapse
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?
DionysosD said:
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?
Click to expand...
Click to collapse
I saw the same thing. Unable to copy the zip file until I did the full wipe, which means no chance of recovering what was on it, but I'm cutting my losses.
I'm now stuck on the configuration stage, it's just sitting on "Just a sec..." for forever it would seem. Trying to update on Christmas day was a bad decision.
Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
fards said:
Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I had the same idea, encrypted, rooted (no system modifications) and running twrp, I flashed stock OP5 recovery, and updated through the ota and ended up in a bootloop.
I did a nandroid to a usb before updating, but I still lost all internal storage files
so...the no verity is only for decrypted users right?
fards said:
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.
The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.
igoorsoouza said:
The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.
Click to expand...
Click to collapse
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?
Are you sure flashing Open beta2 won't compromise the internal storage? I bet no one affords to loose previous photos, apps, settings, etc without full backup.
I've triyed this. All good till i flash 5.0 & Magisk & no verity....
Hello there and Merry Christmas.
I faced to this issue too, fortunately before to update to Oreo. I made a full backup of my data.
My OP5 was running under Oxygen OS 4.5.15 Nougat 7.1.1
Rooted with Magisk V14.5
TWRP Blue_Spark 3.1.1
First I have updated my TWRP to Blue_Spark 3.2
And then I've installed Oreo Oxygen OS 5.0 from TWRP with the full zip.
After the update, my op5 has been bricked and locked on blank black screen with a blue led.
To unbrick my phone I used a tiers softwate to install Hydrogen OS first.
After that I could installed TWRP Blue_Spark 3.2 and then flash to the full zip Oreo Oxygen OS 5.0
My OP5 works as well but...
Right now I'm blocked, Google who usually sends an SMS, does not offer me. Only the authentificatorator or the security code. : /
Be careful, print a Google code to access your account when you go to install Oreo.
I'm waiting for Google to do the right thing.
Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,
1) What is that "no-verity" file?
2) Isn't the regular TWRP 3.2.0 good with Oreo?
MadCow809 said:
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?
Click to expand...
Click to collapse
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.
BenSow said:
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.
Click to expand...
Click to collapse
I think it's possible to flash the Oreo Beta without a full wipe. And yeah, I've got way too much stuff on my device, so I can't afford to wipe my storage.
MadCow809 said:
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.
Click to expand...
Click to collapse
I never suggested either.
Oneplus don't test using twrp or using root.
Their prescribed ota route, as pretty much every other OEM, is unmodified system partition using stock bootloader.
Twrp or root will affect those and can cause bootloops.
Obviously there's a chance with so much diversity in installs that there can be an issue arises.
raboliot said:
Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-5/how-to/guide-restore-data-stuck-bootloop-n-o-t3724515
Read it all.
I have a Encrypted phone and I was able to recover all.
Actually I was able to restore my Nandroid backup.
I was running LineageOS 14.1 up until 15.1 came out. I re-flashed my Nexus 6 with the first build of 15.1 along with OpenGApps. About a week later I decided to flash AddonSU. Here's where it gets goofy. For some unknown reason my brain decided to download and flash SuperSU. Once flashing completed, I went into developer options to enable Root, and to my surprise, root options weren't available. I flashed SuperSU again and still no root options. I then realized that I flashed the wrong SU zip. So, I downloaded and flashed AddonSU. Back into developer options and Root options were available. A few days later, the Nightly 4/30 OTA update became available. The update failed during install. I then flashed the nightly build along with the MindTheGapps zip this time. A week or so later, the Nightly 5/8 OTA update was available. That update also failed during install. I read in multiple forums here that the OTA updates fail due to a conflicting SuperSU binary, and that the only way to remove SuperSU was to reflash stock factory Android, in this case 7.1.1. So, I downloaded and flashed stock Android rom for Build N6F27M. Relocked the bootloader. Unlocked the bootloader. Re-flashed TWRP 3.2.1-0. I booted into recovery and went to File Manager and noticed that the SuperSU folder is still there. I deleted the folder and went through the entire flashing of Stock Android again, one .img file at a time. Locked and unlocked the bootloader again. Flashed TWRP again. Go to File Manager and guess what was there... The SuperSU folder was back!
Before I flash anything else, how can I totally remove SuperSU from my device once and for all?
Current setup:
- Using ADB and Fastboot on Lenovo X230 running Fedora 27 Linux
- Nexus 6 (Build N6F27M), Stock Android 7.1.1
- TWRP 3.2.1-0 Stock recovery just replaced TWRP!
MadFoss1 said:
I was running LineageOS 14.1 up until 15.1 came out. I re-flashed my Nexus 6 with the first build of 15.1 along with OpenGApps. About a week later I decided to flash AddonSU. Here's where it gets goofy. For some unknown reason my brain decided to download and flash SuperSU. Once flashing completed, I went into developer options to enable Root, and to my surprise, root options weren't available. I flashed SuperSU again and still no root options. I then realized that I flashed the wrong SU zip. So, I downloaded and flashed AddonSU. Back into developer options and Root options were available. A few days later, the Nightly 4/30 OTA update became available. The update failed during install. I then flashed the nightly build along with the MindTheGapps zip this time. A week or so later, the Nightly 5/8 OTA update was available. That update also failed during install. I read in multiple forums here that the OTA updates fail due to a conflicting SuperSU binary, and that the only way to remove SuperSU was to reflash stock factory Android, in this case 7.1.1. So, I downloaded and flashed stock Android rom for Build N6F27M. Relocked the bootloader. Unlocked the bootloader. Re-flashed TWRP 3.2.1-0. I booted into recovery and went to File Manager and noticed that the SuperSU folder is still there. I deleted the folder and went through the entire flashing of Stock Android again, one .img file at a time. Locked and unlocked the bootloader again. Flashed TWRP again. Go to File Manager and guess what was there... The SuperSU folder was back!
Before I flash anything else, how can I totally remove SuperSU from my device once and for all?
Current setup:
- Using ADB and Fastboot on Lenovo X230 running Fedora 27 Linux
- Nexus 6 (Build N6F27M), Stock Android 7.1.1
- TWRP 3.2.1-0 Stock recovery just replaced TWRP!
Click to expand...
Click to collapse
This seems like overkill but if you go to Advanced Wipe in TWRP and wipe everything, then flash each .img file again from Fastboot there should be no way SuperSU could survive that.
The answer is to dirty flash the ROM in recovery. You need to overwrite the system and boot partitions with the lineage release. This does not mean using a lineage OTA.
But I'm at a loss why why you indicated indicated the N6 is;
Nexus 6 (Build N6F27M), Stock Android 7.1.1
- TWRP 3.2.1-0 Stock recovery just replaced TWRP!
Click to expand...
Click to collapse
Did you revert to stock?
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Yes, I reverted to stock Android. I read somewhere here that it was the only way to remove SuperSU. And, yes, I did dirty flash. I wiped each partition one by one before flashing. After each wipe, I rebooted to recovery until all were wiped. I also deleted the SuperSU folder. And every time I rebooted into recovery, I'd go to File Manager and the SuperSu folder would re-write itself.
You're mixing and matching things here.
The supersu folder will show up in TWRP even if you've never rooted the device.
A modern, systemlessly rooted device modifies the boot image, not the system partition. By dirty flashing the ROM, you replace the modified boot.img with the "stock" ROM version. Stock is in quotes because it's stock to the custom ROM, not meaning a stock ROM.
Wiping each partition is not a dirty flash. If you were going to dirty flash to remove root, all you needed to do is remove the relevant supersu script in system/addon.d, reboot to recovery, flash the ROM normally, wipe data and cache then reboot.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
I forgot you were originally taking about lineage. Using lineage's su.zip, you will (I think) be rooted in system mode, so dirty flashing will result the original system.img reverting the changes.
As stated above, in systemless it's the boot.img that needs to be reverted.
As an additional caveat, if a third party kernel has been flashed, AND you have systemless root; first you dirty flash the original ROM, then re-flash the kernel to unroot.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
The last "good" flash I completed was with Lineage nightly 4/30. Once I realized that there were still issues, I completely wiped all 5 partitions one at a time (Dalvik/Art, System, Data, Internal Storage, Cache) from TWRP. After rebooting to bootloader, I then fastboot flashed factory 7.1.1 images one at a time (bootloader, radio, boot, cache, recovery, system, and userdata). I then rebooted to stock recovery and selected Factory reset, then rebooted system. 7.1.1 loaded without a hitch.
I just finished flashing TWRP recovery back, wiping all 5 partitions again, and adb pushed only Lineage Nightly 5/15, and MindTheGapps zip's to sdcard and flashed them.
Besides the problematic SuperSU zip (previously installed), those were the only zips and images that were flashed to the device.
I would think after all that, SuperSU would be gone! Your saying I might also have to re-flash the kernel? Wouldn't the latest Lineage zip resolve that?
Please quote the part where you think I told you to do anything more than dirty flash the ROM. I'm trying to figure out why you think I said flashing the lineage ROM is insufficient.
What you have done is serious overkill, but does get the job done (removing root).
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
First, let me preface that I am new to flashing ROM's. Second, I was unclear of the differences between dirty and clean flashing.
Third, I didn't realize that the "supersu" folder at the root of the device, is persistent. Had I known this in the first place, none of this conversation would really be necessary as I believed that SuperSU wasn't going away.
Fourth, nowhere do I even remotely insinuate that flashing a Lineage ROM is insufficient.
Fifth, here is your quote from post #6 where you mention the possibility of flashing more than the ROM, "...first you dirty flash the original ROM, then re-flash the kernel to unroot."
Finally, any forum I've been a part of, details have always been a prerequisite to receiving feedback. All I've done here is provide those details so that anyone, (not just you) could be best informed of my situation.
I do agree now that what I've done with my device is serious overkill. Everything I've done thus far has been done from the advice of other Devs or experts here on XDA, Reddit, or other forum posts somewhere on the internet. However, I, in no way, intentionally or unintentionally tried to undermine your expertise (as I sensed you have in your last post). I am merely a noob in the world of custom ROMS, and all I seek is advice. And for the advice that you provided I am grateful, and I sincerely thank you. If I offended you or made you feel your advice and expertise was inadequate, I do apologise!
Again, I thank you, as well as all of the Developers and experts here on XDA for your knowledge and advice. I look forward to possibly talking to you again in the future.
As, in the future, you read solutions to problems you post, please keep in mind that it's not uncommon for people to post complete explanations that may not totally apply to the situation at hand. There are a couple of reasons for that.
One is that it can help develop understanding of the larger picture the specific problem fits into.
Another, and often why I almost always expand answers, it so future readers of a thread get a more complete view of the process under discussion.
In the case where I expanded on the idea that if an additional custom kernel is used on top of a custom ROM, then that has to be taken into account when removing root. I did make an assumption that if you didn't use a 3rd party kernel, then you would understand that didn't apply to you.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
alryder said:
This seems like overkill but if you go to Advanced Wipe in TWRP and wipe everything, then flash each .img file again from Fastboot there should be no way SuperSU could survive that.
Click to expand...
Click to collapse
BTW, thanks for your input. This Definitely should take care of it. This would have been much easier had I known that a supersu folder existed at the root of the device. For all the times I've flashed my phone, I've never noticed it. Lesson learned. Thanks again.
Hello XDA fam, I just picked up a 3T and unlocked the bootloader.
I was just wondering what the general flashing process was for this
device (A3000). Also a tad confused about this dm-verity ...
disabler zip, is this and format data required every time you flash a
new ROM?
MoistPicklez said:
Hello XDA fam, I just picked up a 3T and unlocked the bootloader.
I was just wondering what the general flashing process was for this
device (A3000). Also a tad confused about this dm-verity ...
disabler zip, is this and format data required every time you flash a
new ROM?
Click to expand...
Click to collapse
Dm-verity warnings are similar to the unlocked bootloader screen you get, but are red. You get them if you are running stock OOS and modify the system partition.
You don't need the dm-verity disabler unless you've got a dm-verity warnings screen.
Note that you cannot disable the unlocked bootloader warning you get every time the phone boots except by re-locking the phone.
Another thing to note: if you are running stock OOS and flash TWRP, then TWRP will be replaced by the stock recovery when your reboot the phone unless you:
- use a patched boot image like the one from @Xennet's thread https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324/post79357241
- use a custom kernel, or
- use Magisk.
Flashing using TWRP is just like any other phone. If you're changing ROMs then you need to do a clean install (wipe /data and/system).
Some ROMs don't handle an encrypted phone (most Android 10 ones except for Los and PE), so you you have to remove the encryption before using those ROMs (TWRP>wipe>format data).
Finally if your phone is unlocked and running OOS 5.x or lower, and you want to upgrade to OOS 9.x then you'll either have to:
- remove the encryption (but can re-encrypt after installing 9.x) or
- use the modded firmware (that keeps the 5.x bootloader and keys) so that you don't have to remove the encryption. See https://forum.xda-developers.com/on...-5-0-8-firmware-barrier-t3941164/post79758055
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Dm-verity warnings are similar to the unlocked bootloader screen you get, but are red. You get them if you are running stock OOS and modify the system partition.
You don't need the dm-verity disabler unless you've got a dm-verity warnings screen.
Note that you cannot disable the unlocked bootloader warning you get every time the phone boots except by re-locking the phone.
Another thing to note: if you are running stock OOS and flash TWRP, then TWRP will be replaced by the stock recovery when your reboot the phone unless you:
- use a patched boot image like the one from @Xennet's thread https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324/post79357241
- use a custom kernel, or
- use Magisk.
Flashing using TWRP is just like any other phone. If you're changing ROMs then you need to do a clean install (wipe /data and/system).
Some ROMs don't handle an encrypted phone (most Android 10 ones except for Los and PE), so you you have to remove the encryption before using those ROMs (TWRP>wipe>format data).
Finally if your phone is unlocked and running OOS 5.x or lower, and you want to upgrade to OOS 9.x then you'll either have to:
- remove the encryption (but can re-encrypt after installing 9.x) or
- use the modded firmware (that keeps the 5.x bootloader and keys) so that you don't have to remove the encryption. See https://forum.xda-developers.com/on...-5-0-8-firmware-barrier-t3941164/post79758055
Click to expand...
Click to collapse
Wow thank you for the detailed info, I really appreciate the insight.
I am currently running the latest OOS update 9.0.6 I believe.
Once I have TWRP installed do I swipe and enable modifications?
Flashing Magisk afterwards avoids the bootloop and allows me to
keep TWRP in place of the stock recovery as you said, correct?
So installing most ROMs seems fairly straightforward, following
the flashing instructions. However if I were to install an Android
10 ROM wouldn't formatting data remove all zips and everything
from the internal storage? So at that point I'd have to copy back
all my ROMs and zips back to the phone in TWRP and flash from
this point correct?
Sorry for the loads of questions, my most recent device was a
Note 9, which has a locked bootloader, so it has been a while since
I have flashed anything or used TWRP.
MoistPicklez said:
Wow thank you for the detailed info, I really appreciate the insight.
I am currently running the latest OOS update 9.0.6 I believe.
Once I have TWRP installed do I swipe and enable modifications?
Flashing Magisk afterwards avoids the bootloop and allows me to
keep TWRP in place of the stock recovery as you said, correct?
Click to expand...
Click to collapse
You don't need you enable modifications of the system partition. Any zip you flash will make the system writable if required.
So, just flash Magisk.
MoistPicklez said:
So installing most ROMs seems fairly straightforward, following the flashing instructions. However if I were to install an Android
10 ROM wouldn't formatting data remove all zips and everything from the internal storage? So at that point I'd have to copy back all my ROMs and zips back to the phone in TWRP and flash from this point correct?
Click to expand...
Click to collapse
Correct. So it's best to take a backup of your current system and backing up everything on internal storage (/sdcard) to an external drive or PC.
The fastest way to take the backup is to use ADB.
Code:
adb pull /sdcard
MoistPicklez said:
Sorry for the loads of questions, my most recent device was a
Note 9, which has a locked bootloader, so it has been a while since
I have flashed anything or used TWRP.
Click to expand...
Click to collapse
You'll find that nearly all the rom, kernel, and recovery development threads are under the OnePlus 3 forum in https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development as they are unified: good to flash on both the 3 and 3T.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
You don't need you enable modifications of the system partition. Any zip you flash will make the system writable if required.
So, just flash Magisk.
Correct. So it's best to take a backup of your current system and backing up everything on internal storage (/sdcard) to an external drive or PC.
The fastest way to take the backup is to use ADB.
You'll find that nearly all the rom, kernel, and recovery development threads are under the OnePlus 3 forum in https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development as they are unified: good to flash on both the 3 and 3T.
Click to expand...
Click to collapse
Awesome info, big thanks to you my good sir. Finally
on Havoc 2.9 and decrypted. Now just gotta get a feel
for this phone and keep on reading. Cheers!