Im running stock ROM 7.1.1 with Latest ElementalX Kernel and latest Magisk + MagiskSU. Also Running latest TWRP 3.1
I haven't updated yet. so I have the march patch, and this recent patch im behind on my 5x. I thought maybe i could just accept the OTA and just reflash magisk and the elementalX kernel afterwards. Oh, and likely would have to do TWRP as well. But accepting the update clicking to restart and install just rebooted me into TWRP. Flashfire doesn't work yet either been waiting a month on that. I get that failure during "uncrypting" error.
I'm slightly new back on the modding scene, until recently have been out of it for years. I did recently make a mistake with an audio mode and had to download the full image and use fastboot to throw that back on my device. Anyway with 7.1.2 out i really do want to update so i need to do it manually, and hopefully without losing my data. (or having to restore it from a backup if possible anyway)
I'd read somewhere that you can download the full images and extract the updated images you need and flash them to your device then your respective addons root kernel ect.. There seems to be lots of way to go about it, but little clear on how to do this so that's what brings me here to this post. What's the best way to manually update (add security patches) if im running Magisk and magiskSU.
Thanks in Advance.
https://elementalx.org/how-to-install-android-monthly-security-updates/
After you flash the /system /boot /vendor (I would also do bootloader and radio), reboot into TWRP and install kernel & Magisk.
Related
Hey guys, so I was running 3.2.8 firmware and modem (marshmallow) with latest AOKP stable (not nightly) nougat rom and things were working as they should...
Now the official 4.0 nougat oneplus oxygen rom comes out and I'd figure it's time for an update... So I do a clean install of oxygen 4.0, boot into system, and then flash twrp-3.0.2-1.28 recovery to flash aokp nougat rom.
After that I flash latest stable SuperSU 2.79, reboot and then boot back again to install Adaway systemless v2 zip
Problem is, my phone randomly un roots itself, busybox app would freeze (had to flash it through TWRP later) and Adaway won't merge hosts file.
I know it probably has to do with either latest root, the recovery, encryption/decryption, or firmware (or combination of some of these) from what I've read on the forums...
Can anybody tell me what is causing these problems and help me fix this?
I've tried installing twrp-3.0.2-0_blu_spark_v11 recovery, version 19 of bluspark's modified TWRP, and SuperSU 2.79 sr2 but I still can't get Adaway to work and system keeps unrooting...
Is it bc I have to keep the system read only in recovery? Update my partitions to f2fs? Do I need to encrypt/decrypt my device?
tl;dr: Updated to 7.1.1 OTA then installed twrp 3.1.1-0 had it apply what I assume is the F2FS kernel fix, now phone won't boot into system
Yesterday I was trying to update my rooted phone from MM to the latest software. I did this by reverting everything back to stock using this guide and that worked without a problem. Once it was back to stock I upgraded all the way up to the most recent OTA from Motorola (7.0.1 I believe), and then I upgraded up to the most recent 7.1.1 OTA manually using this guide. After all the updating I then flashed twrp 3.1.1-0 and booted into it. This is where things went wrong, after booting into twrp for the first time I asked me if I'd like to like to apply what I'm assuming is a kernel with the F2FS fix, I didn't think much about it and accepted it. In retrospect this was a very bad idea seeing as the F2FS fix for 7.1.1 hasn't been released yet. Now whenever I try to boot into the system the bootloader warning screen shows "ID: bad key" and won't boot. I can still get into the bootloader for fastboot and the twrp recovery but I don't know what to do from here in order to fix it. If anyone could help me fix this I'd really appreciate it!
f2fs fix is Kernel. You need an original boot.img of your currently installed firmware version and flash that to uninstall f2fs. Then it should work.
My advice in general:
Before doing any updates: do a full Nandroid backup.
Before modifying boot partition (f2fs fix, install Magisk or SuperSU or phh superuser) do a backup of at least boot.img. it may be a good idea to do a system backup (system boot recovery logo oem). Will help for OTA updates.
Before modifying recovery, back it up.
Before doing any modifications, save your data (data partition, but careful: /data/media is excluded here! You need that additional).
I hope I'll learn to keep all this in mind too without getting out of patience
I just spent the last day going through your exact issues. Pm me if you need instructions and files. I can look up exactly what firmwares and fastboot commands I used to get back to normal.
So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!
If you don't want to wipe just update through factory image, just open the factory zip, open flash-all file and remove "-w" from last line, then execute it (update without wipe)
But I suggest to flash the stock factory image with the "-w" to make a clean install, flashing major release like 7.x -> 8.x is always better wipe to avoid potential issues.
But yes, you can first give a try without wipe and only if you find bugs try wiping. Your choice.
simply flash the OTA, then re-root
xraystyle said:
So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!
Click to expand...
Click to collapse
Use full unroot in supersu. Then take ota. Then root again after upgrading to O
Thanks for the help everyone, you pointed be in the right direction.
In the event that it might help someone else, here's what I ended up doing:
1. I downloaded the OTA, booted into the TWRP I had currently installed, and then sideloaded the OTA.
2. I used ADB to push the newest TWRP flashable zip, the latest SuperSU, and the latest SU-Hide to /sdcard on the device.
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
4. Finally, I rebooted to recovery on the phone (latest TWRP now instead of stock), and flashed SuperSU and SU-Hide.
I'm now stock, rooted, on O. No wipe necessary, kept all my apps and data. So far the OS itself has been entirely stable. I had an issue or two with a few apps after the upgrade, but those were fixed with a quick re-install. Except for Better Terminal Emulator Pro, seems it doesn't want to work on Oreo and it's no longer under active development. It's fine though, there's other terminal emulators out there.
Thanks again for the help!
xraystyle said:
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
Click to expand...
Click to collapse
Which version of TWRP do you have TWRP working with Oreo 8.0?
I can boot into the modded TWRP 3.1 (fastboot boot twrp-3-1-pixel-bootable-mod.img) but AFAIK there is no working flashable recovery for 8.0 yet.
quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.
gordonlw said:
quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.
Click to expand...
Click to collapse
That's how I did it. I don't use suhide.
Does the -w in the .bat file format or wipe the data? I want a clean clean , o-fresh in the morning feeling kind of wipe
toknitup420 said:
That's how I did it. I don't use suhide.
Click to expand...
Click to collapse
Thanks! What I ended up doing:
Decided to try and unroot and take the ota. super-su full unroot would not work. so I fastbooted to the mod twrp and flashed UPDATE-unSU. I then took the ota. then fastbooted to mod twrp and flashed super-su. worked perfect!
As the title says I am unable to boot after flashing Magisk (tried v16 and v15.3). It boots fine without magisk but of course no root and no custom recovery. Any help would be appreciated. Didn't have any problems on the previous stable build.
You need to first flash OOS 5.1 let it boot, then go to fastboot and flash twrp then go to twrp and flash magisk, only way to get root
hello, that's what I did and it worked well
this has happened here since 5.0.4
Try to use lastest blu-spark's TWRP, then flash 5.1 & Magisk without extra boot in the middle.
Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan
ToucanSam said:
Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan
Click to expand...
Click to collapse
It's not broken. The vendor error message is because it was recently updated to work better with Project treble, which uses a hidden partition for the vendor. You can simply ignore the error and it will work fine. Or if you flash a treble ROM, the error will then go away.
I just got the phone. Format it in recovery.
Flash latest blu spark twrp (v.8.73).
Flash the Oos ob06.
Reboot to system. Set the phone, instal apps from Play.
Reboot to Fastboot.
Reflash recovery.
Reboot to recovery.
Flash Magisk 15.3. Reboot to system. OK.
Updated Magisk with Magisk.
Hi, Can anyone help me. in my oneplus 5T after installing new rom it is working smooth but i can't upgrade to new updates. in recovery mode the files seems to be decrypted and cant find any folders where i copied the updation . instead new files are found and can't access and find any of the folders of my own. this happened after i input the security lock. i wiped the entire data and installed new roms still it seems so. somebody please help me to find a solution for this
I did some searching, but could not see a guide for moving from Magisk rooted 8.1.0 to Magisk rooted 9.0. I believe I need to uninstall Magisk, then install the update, but not sure of the exact process. Also, is it better to wipe the data when going from 8.1.0 to 9.0 or doesn't matter?
Thanks in advance!
There's two ways you can do this.
One, you can sideload the OTA using ADB (if on stock recovery), or you can flash the OTA through TWRP.
Two, you can download the factory image, and manually flash the bootloader and radio, then update /system WITHOUT the -w flag, if you don't want to wipe data.
Any time you flash a software update, whether it's the OTA or the factory image, it WILL overwrite /boot, so you will lose Magisk and any custom kernel and recovery. Simply boot TWRP using fastboot, flash Magisk (and TWRP and kernel if desired), and you'll be good to go.
No need to wipe data. My process for installing OTAs and re-rooting has always been the same and it's no different with the 9.0 update other than one exception I encountered (patching the boot image AFTER updating).
I prefer the boot image patching method:
Download the latest platform-tools from Google
Download both the OTA and full factory images
Extract boot.img from the factory image
If already rooted prior to updating, re-flash current stock boot image
Sideload OTA
Patch the extracted boot image with Magisk (make sure you're on the latest version; 16.7 beta channel)
Flash patched boot image
Normally I patch the boot image prior to sideloading the OTA but it resulted in an endless boot after the 9.0 update.
Thanks guys. I actually found a thread I bookmarked previously on this topic. Do you think this would work well still? :
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
Also I saw some people mentioning trouble with Magisk after 9.0 update. Did you encounter that or anything special to consider there?
machx1111 said:
Thanks guys. I actually found a thread I bookmarked previously on this topic. Do you think this would work well still? :
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
Also I saw some people mentioning trouble with Magisk after 9.0 update. Did you encounter that or anything special to consider there?
Click to expand...
Click to collapse
Here's a bit more specific guide for updating to 9.0
https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77269862