At least, I think this is what happened and I'm not willing to try again to test it. It could have been the custom kernel I installed with MultiROM (it does say that having a custom kernel when flashing can cause it to fail). Like an idiot, I didn't make a backup before letting FlashFire do it's thing. I fixed it by dirty flashing OTA 4.0 from MidgetMob's Stock Recovery Image and OTA Library and letting TWRP inject MultiROM. I do not recommend dirty flashing to fix things, I'm just saying what I did.
What I should have done:
Made backups with TWRP and Titanium
Downloaded the ROM as a ZIP from MidgetMob's library
Flashed it with TWRP. Please correct me if I'm wrong but I believe dirty flashing would have been ok since it's flashing an Android update and not a seprate ROM
Flashed the latest SuperSU ZIP (again from MidgetMob's library)
Let TWRP inject MultiROM
Boot, do not let TWRP reroot your device, you already flashed SuperSU and SuperSU says specifically to not have TWRP root your device
It might boot loop once or twice, just let it do it's thing and it will boot
TWRP 3.0.2-0
SuperSu Pro 2.78
Android 6.0 Marshmallow build MPH24.49-18
I have systemless rooted my phone as per the instructions at http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380
although, it didn't work without some tweaking... Unfortunately I don't remember what steps I took to get it working.
I am not sure of the process form here. Now that I have root, am I supposed to flash boot_orig.img permanently or just when I want to update?
I have tried:
fastboot flash boot boot_orig.img
but I loose wifi and can't download.
I have tried letting the OTA fail with the boot.img flashed, then reflashed with boot_orig.img and tried to install the update zip file via TWRP, but that fails.
I made a TWRP backup before I started rooting and for every major step after that, so I can start fresh if need be.
[EDIT]
I noticed on this thread, http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 , the following comment:
You must absolutely re-flash your stock /system partition, or the separate root instances will interfere with each other. The installer for this experiment will not clean up old root files.
- Flash stock /system (and /vendor and /oem, if present)
- Flash the attached boot image
- Flash the attached SuperSU ZIP in TWRP
Click to expand...
Click to collapse
Could this be the problem? If so, How do I "flash stock /system (and /vendor and /oem, if present)"?
Any help appreciated...
I'm currently on November's NDE63V with root and twrp installed. I updated to SR5 root when it was released using TWRP and it boot looped. I assumed it was because I didn't flash the stock boot.img(both slots?), boot to TWRP, flash TWRP then install root. Is this correct? Does that method need to be followed every time there's an update?
I want to update to 7.1.1, December's OTA -> I want stock ROM on one slot and WETA on the other. Both with root. Of course either Franco or ElementalX. Can someone outline the steps, as I don't want to boot loop again, setting everything up is a PITA!
http://forum.xda-developers.com/showpost.php?p=69834495&postcount=2
This should help you with dual booting.
Haven't read through it all yet as I'd like to dual boot as well. But all I did to update is download all the files Weta has when you go to download the rom (boot, bootloader, radio and vendor.)
I Fastboot flashed bootloader, radio and vendor rebooted to bootloader and flashed weta, elementalx and SuperSU sr5.
I'm running stock ROM on unlocked bootloader with root through Magisk. I've been using TWRP, but changed over to Blu_spark TWRP recently.
Every time I update my OS Ota, I lose TWRP and Magisk. The Magisk app is installed, but the ROM is not rooted. If course, if I try to install patch the system so it's rooted through the Magisk app, it says that it can't unpack the file. If I reboot to recovery to install from there, I get the stock recovery, not TWRP.
I tried to re-install TWRP and Magisk once before, and borked my phone. I had to quote and start from scratch. I lost all data since I wasn't rooted and Titanium Backup would not run.
What is the proper way to get TWRP and Magisk back after an OTA update?
Flash them after you flash update zip. If you don't you will lose recovery and root every time. Gets overwritten by stock recovery. Normal behavior
Sent from my ONEPLUS A6003 using Tapatalk
So you're saying that instead of doing the OTA update, I should download the update from here, and manually update it ? Can I just install the update? I'm rooted, (well, I was) so the OTA will only download the full update. Is that required instead of the update?
I really have to do a full re-install for every update? That sucks. A lot.
Full reinstall? No. You just have to flash the full ROM. This doesn't mean, you'll loose all your data: Just TWRP, Magisk and (if you have it) your custom kernel. You only have to flash TWRP (or simply boot into it), Magisk and kernel (again: if you have it) after the update. Done.
MickyFoley said:
Full reinstall? No. You just have to flash the full ROM. This doesn't mean, you'll loose all your data: Just TWRP, Magisk and (if you have it) your custom kernel. You only have to flash TWRP (or simply boot into it), Magisk and kernel (again: if you have it) after the update. Done.
Click to expand...
Click to collapse
Ok. Cool. I tried that last time, but it failed. As a result, I'm a bit anxious about doing it again. Hopefully, I won't have any problems this time.
Thanks for the info.
I have had similar troubles as you, here's an overview of how to solve those problems.
OTA through OS:
Download and install OTA
Use Magisk Manager to download the TWRP A/B retention script and install it
Install Magisk to current and inactive slot
Reboot
Guys I am using latest blu_spark twrp. my bootloader is unlocked and I am running oxygenOS openbeta23. Following is my problem.
My flash order: (Note: already I have bue_spark twrp recovery running without issues)
1. Flash the full OTA(openbeta)
2. Flash the blu_spark twrp zip file on both active and non active slots.
3. Flash the latest magisk zip file. If step 3 is not successful means I will try to reboot in to recovery and again flash the magisk installer zip.
Until some time back all this worked fine. But for last 2-3 times although the flashing process of twrp zip on both slots ends with success message, when I reboot to recovery from twrp in order to flash magisk, the device boots in to stock recovery. I don't know how even after flashing twrp zip on both slots successfully why the devices bootbback to stock recovery. Then to have blu_spark twrp I have to connect my device to a computer in fastboot mode and then boot in to custom recovery using the blu_spark twrp image file and again flash the blu_spark twrp zip file which is inconvenient and also requires a computer.
Am I missing anything here?? If yes why this method was working perfectly before? Please somebody help.
Regards,
Sivabalan K
I flash in following order my stable updates
Flash full rom zip
Flash bluespark recovery
Restart into bluespark recovery
Flash magisk
Restart into Android
Everything works flawless. Magisk installed with all the modules running
Hi guys,
Don't you need to disable lock pattern/PIN or fingerprint/face ID? And don't need to uninstall magisk modules?
I never update my OP6 from my initial unlock/twrp/magisk and I'm a bit anxious to do it now...
Thanks
PS : I'm using original twrp (3.2.3-1), is this a problem?
Hello guys, i have a question. What is the proper way of flashing miui updates from twrp. Atm i am on 10.2.2.0 but a new pie udpate has been released and i want to update to it. Also, do i need a certain recovery? I am on pitchblack atm.
I just don't want to brick my phone. Thanks in advance.
You can flash with no problem.
But after flash you lose twrp (it will be stock recovery). Need it reflash.
I successfully updated to pie, but a problem emerged. I can no longer flash magisk. Flashing magisk results in a bootloop and when i uninstall it from the recovery, the phone boots normally.
Any suggestions?
Did you flash that zip "lazyflasher"? For the dm verification thing.