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.
Related
I put LRX21O on my N5 by sideloading the factory image (incl the fresh cache and userdata images). Worked fine!
I used ChainFire's first(?) Lollipop Autoroot package. I don't see a version in there, but all its files are dated 11/14. As I understand it, that method needed to patch the kernel to keep root.
His new package (as of 11/25) uses another method, allowing the kernel to remain stock. I did not run the new CFAR, but I let SuperSU update from the market and update the SU binary ("normal" method, not booting into recovery).
My questions:
Did that also undo the kernel patching from the earlier root retention method?
If not, how do I go back to the stock kernel without losing any data?
Thanks! Hope these aren't dumb-ass questions.
Well as far as I know Cf auto root just booted into another customised kernel by chainfire and then rooted the system. It didn't flash a new kernel. Maybe he changed the ramdisk. Not sure about that. But since nothing got flashed I doubt he changed even that.
On how to flash stock kernel just use flashify to flash the img or do it using fastboot.
Code:
fastboot flash boot boot.img
My understanding is that the ramdisk was changed, so that means the boot partition has been edited.
I just did a fastboot flash of the image:
Code:
fastboot flash boot boot.img
If you're really concerned, you can also flash system and re-root using the newer SuperSU ZIP. Flashing boot or system doesn't wipe data. I didn't bother with re-flashing system. No ill effects as far as I can tell.
Code:
fastboot flash system system.img
I've just flashed boot and system.
Then I had to reflash twrp.
Finally SuperSU. All working fine
Hello.
I have a Pixel with stock Android that was rooted with Chainfire SuperSU 2.78SR3
Last night I've noticed that the phone isn't rooted anymore and has installed the Feb security update OTA. (I only had the Nov update installed).
I've tried rerooting using the same method (Fastboot boot) and got stuck in a bootloop.
I had to flash a clean stock rom to get it out of the bootloop.
Next I installed TWRP. That worked.
Next I tried installing a ZIP version of SuperSU 2.78SR4. The Zip installs but when I boot into Android SuperSU says that the phone isn't rooted.
Anyone had anything similar happen to them?
Borrisl said:
Hello.
I have a Pixel with stock Android that was rooted with Chainfire SuperSU 2.78SR3
Last night I've noticed that the phone isn't rooted anymore and has installed the Feb security update OTA. (I only had the Nov update installed).
I've tried rerooting using the same method (Fastboot boot) and got stuck in a bootloop.
I had to flash a clean stock rom to get it out of the bootloop.
Next I installed TWRP. That worked.
Next I tried installing a ZIP version of SuperSU 2.78SR4. The Zip installs but when I boot into Android SuperSU says that the phone isn't rooted.
Anyone had anything similar happen to them?
Click to expand...
Click to collapse
You might need to flash back to stock to fix this. If you do let us know so we can help you save your data and apps.
You used the wrong SU. You need 2.79 SR3. Note the 9 on there, you used 2.78.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Copy it to your phone and boot to TWRP. Then INSTALL it from TWRP.
Full steps on how to take OTA updates when rooted with Magisk, TWRP & Custom Kernel?
I tried to take the 5.1.6 OTA by using these steps: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md but it didn't work properly.
Could someone give me a list of the full steps that will keep Magisk, TWRP and Blu Spark Kernel installed? When I did the steps above it kept Magisk after rebooting, but didn't keep the custom kernel, so I rebooted to recovery to reinstall the kernel. However it was replaced with OxygenOS Recovery and it automatically wiped my device.
There is no way for you to take OTA with twrp and kernel persisted.
You need to understand how update works. Apparently, the update replaces your boot partition and your kernel is exactly implemented in the boot partition.
The changes will get overwritten. Thus, you will need to reinstall the kernel by yourself.
And as what I just mentioned, there is no specific recovery partition on A/B partitioning method. When boot partition get overwritten, the twrp will also be replaced by the stock recovery.
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.