Develop Bugs

OTA updates for TWRP

Would it be possible to list all OTA updates which are installable through TWRP? I am trying to find a way to update my P2 with TWRP to S244, and I find tutorials and ZIPs scattered around on the forum (except the one for S244), but it makes it a bit of a hassle when one buys this phone on MM, installs TWRP and finds out the OTA updates are not working (which makes sense).
I am on S233 now, but I can imagine I am not the only one using TWRP and looking for info whilst being even on an older firmware. I know it would be possible to reflash the stock recovery, but even these files are hard to find non-deodexed, non-TWRP.

same here
JayVerhofstadt said:
Would it be possible to list all OTA updates which are installable through TWRP? I am trying to find a way to update my P2 with TWRP to S244, and I find tutorials and ZIPs scattered around on the forum (except the one for S244), but it makes it a bit of a hassle when one buys this phone on MM, installs TWRP and finds out the OTA updates are not working (which makes sense).
I am on S233 now, but I can imagine I am not the only one using TWRP and looking for info whilst being even on an older firmware. I know it would be possible to reflash the stock recovery, but even these files are hard to find non-deodexed, non-TWRP.
Click to expand...
Click to collapse
same here bro. my phone is showing 125 mb update available which S244. i tired many times but it failed. im looking for this OTA update file which can be flash via TWRP.
please bro help me i dont want to flash whole stock rom. full updated ROM is available here.
https://forum.xda-developers.com/lenovo-p2/development/lenovo-p2-lenovo-p2a42-stock-nougat-t3661024.
please help me to find out only 125 mb TWRP update

Has anyone with systemless root, preferably Magisk, dared to try Flashfire? I looked in the official xda thread and there seem to be mixed experiences. Some get a black screen from which the phone doesn't wake up unless you use a hard reset. Others solved the black screen by booting into TWRP and flashing the Magisk uninstaller. Then doing a clean install before using Flashfire.
I guess the queue would look something like this:
1. Wipe cache
2. Flash OTA
3. EverRoot disabled
4 Flash Magisk
5. Normal reboot and preserve TWRP.
If unsuccessful
1. Flash stock boot.img
2. Flash OTA
3. EverRoot disabled
4 Flash Magisk
5. Normal reboot and preserve TWRP.

Magisk v14 and OTA updates

Hey, guys, I wanted to ask if someone tried OTA updates working with the new method of rooting released with magisk 14- a rooting method in which we do not need root or custom recovery beforehand, we just need to provide stock boot image dump to the magisk manager. This method will do us good because if OTA's still work after root we can be rooted on the stock roms without having to download full OTA's when a new update arrives. If someone can confirm working OTA's on the OOS open beta with this root method, it would be really helpful. Thank you!

As long as you take a backup of system and keep TWRP installed so you have a backup to revert to it should be fine. The risk of issues is just too high unless you don't give a **** about your personal data.

Puddi_Puddin said:
As long as you take a backup of system and keep TWRP installed so you have a backup to revert to it should be fine. The risk of issues is just too high unless you don't give a **** about your personal data.
Click to expand...
Click to collapse
Bro, I know how to work with TWRP. Your comment does not answer the question.

blaze95rs said:
Bro, I know how to work with TWRP. Your comment does not answer the question.
Click to expand...
Click to collapse
Well think of it about this. Magisk is just one big hack on the system partition. An OTA changes files on the system partition aswell. What if the OTA changes files that Magisk needs?
1. Your phone will go into a bootloop.
2. You might end up bricking it.
3. You just have to reflash Magisk.
4. Your phone becomes buggy as hell.
Thats why we also recommend to install the full zips when flashing roms and kernels that modify system because of possible conflicts.

Puddi_Puddin said:
Well think of it about this. Magisk is just one big hack on the system partition. An OTA changes files on the system partition aswell. What if the OTA changes files that Magisk needs?
1. Your phone will go into a bootloop.
2. You might end up bricking it.
3. You just have to reflash Magisk.
4. Your phone becomes buggy as hell.
Thats why we also recommend to install the full zips when flashing roms and kernels that modify system because of possible conflicts.
Click to expand...
Click to collapse
Obviously I would uninstall magisk and then install ota and reinstall magisk. Magisk is systemless so I think there shouldn't be any problem.

blaze95rs said:
Obviously I would uninstall magisk and then install ota and reinstall magisk. Magisk is systemless so I think there shouldn't be any problem.
Click to expand...
Click to collapse
See it for yourself! Its something most people do not recommend.

Puddi_Puddin said:
See it for yourself! Its something most people do not recommend.
Click to expand...
Click to collapse
You have missed the whole point of the post. This is a NEW method. Many people have not tried this method of root. So please, if you have any valuable information then only share. Do not litter. There should be logic to your answer and not general acceptance. Saying that many people do this or do that is not a very solid answer.

blaze95rs said:
You have missed the whole point of the post. This is a NEW method. Many people have not tried this method of root. So please, if you have any valuable information then only share. Do not litter. There should be logic to your answer and not general acceptance. Saying that many people do this or do that is not a very solid answer.
Click to expand...
Click to collapse
That doesn't matter. I get that it can be installed without a custom recovery. But that doesn't mean it won't conflict with possible ota's. Again, see it for yourself. Most people including me do rather play it the safe way.

I have recently updated to the lateset Oxygen OS Beta i had Magisk installed, i use Sparks Latest twrp version, with this you can install OTA updates. I dit not unlinstalled Magisk first, you do need the full rom file, but for me when i wanted to install the OTA, it found i had rooted and autmatacly downloaded the full rom. After you installed the update you can install the latest version of Magisk.

Is there an easy way to update an unlocked/rooted Pixel 3a XL?

I unlocked my bootloader and rooted my Pixel 3a XL as soon as I got it. But I've been unable to install the OTA and security updates since (September 2019). I've been digging around in the forum trying to figure out how to load the updates. I was really hoping Flashfire would work, but it gives me errors - something about the root not being available or right... but my root works for everything else I've tried (maybe its an issue with Magisk)...
Anyway, I was hoping to find a simple way to install the updates. Help!
Thanks in advance,
Tom

Tom2112 said:
I unlocked my bootloader and rooted my Pixel 3a XL as soon as I got it. But I've been unable to install the OTA and security updates since (September 2019). I've been digging around in the forum trying to figure out how to load the updates. I was really hoping Flashfire would work, but it gives me errors - something about the root not being available or right... but my root works for everything else I've tried (maybe its an issue with Magisk)...
Anyway, I was hoping to find a simple way to install the updates. Help!
Thanks in advance,
Tom
Click to expand...
Click to collapse
I have seen postings about people fastboot flashing back the original boot.img, then taking the ota then repatching the new boot image and flashing it via fastboot. Not as simple as you hoped i am sure but it works.
The other way is to download the full image, remove the -w option in the flashsall.bat and then run the modded flashall file. You then need to patch the new boot image as above and fastboot flash that to regain root. I have not found any other ways to get updates besides doing one of the 2 above every month

Thanks, adm1jtg! I appreciate the help.
Unfortunately, I tried the second method you mentioned on my own... but I missed the part about removing the -w from the flashall.bat. Faaaaaaaaaaaqqqqqqqq!!! And ended up wiping my phone.
But now I think I'll remember that -w trick! I love learning things the hard way. LOL
I'm still going to hold out hope that someone will come along and make an app like FlashFire to script the process for us.

Tom2112 said:
Thanks, adm1jtg! I appreciate the help.
Unfortunately, I tried the second method you mentioned on my own... but I missed the part about removing the -w from the flashall.bat. Faaaaaaaaaaaqqqqqqqq!!! And ended up wiping my phone.
But now I think I'll remember that -w trick! I love learning things the hard way. LOL
I'm still going to hold out hope that someone will come along and make an app like FlashFire to script the process for us.
Click to expand...
Click to collapse
Why wouldn't you just side load the OTA and be done with it?? Easy instructions where you'll download the OTA image. Easier than what your currently doing

thatsupnow said:
Why wouldn't you just side load the OTA and be done with it?? Easy instructions where you'll download the OTA image. Easier than what your currently doing
Click to expand...
Click to collapse
Sideloading the ota would be a great option EXCEPT he said he was on a much older version... Like sept.
My understanding is that the ota for dec would only contain changes implemented for the month of December, this in this scenerio he would not get the patches for October and November with your method and i am not even sure if it would boot after that mismatch
It's really not saving much work if any over flashing the full version, and with the full version they're is no potential for bootloop due to missing some patches or updates. It's just much safer.

thatsupnow said:
Why wouldn't you just side load the OTA and be done with it?? Easy instructions where you'll download the OTA image. Easier than what your currently doing
Click to expand...
Click to collapse
Um... prolly because I'm dumb... and maybe a little because I couldn't find instructions on how to do it properly. I don't suppose you happen to have a link to how to do the OTA sideload thing properly?

Tom2112 said:
Um... prolly because I'm dumb... and maybe a little because I couldn't find instructions on how to do it properly. I don't suppose you happen to have a link to how to do the OTA sideload thing properly?
Click to expand...
Click to collapse
https://developers.google.com/android/ota

The most simple way to update while keeping root would be to follow the instructions for "Devices with A/B Partitions" at the following link in the Magisk documentation:
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Basically, Magisk allows you to restore the original boot image to the current partition so you can take the OTA when it arrives on your phone. Before rebooting you install Magisk to the inactive slot so that when the phone restarts you retain root without having to mess with Fastboot.

Delete Me!
Think all you have to do is click uninstall magisk, dont reboot... Take ota, but before reboot click install magisk/ install to empty slot...
Oops didnt see the reply above

OK, so when this month's security update came out, I tried to following the Magisk instructions (uninstall Magisk, restore stock boot, flash OTA, etc...) but when I went to uninstall Magisk and restore the stock boot, it tells me there is no stock boot image to restore! Dammit. Now what?

Tom2112 said:
OK, so when this month's security update came out, I tried to following the Magisk instructions (uninstall Magisk, restore stock boot, flash OTA, etc...) but when I went to uninstall Magisk and restore the stock boot, it tells me there is no stock boot image to restore! Dammit. Now what?
Click to expand...
Click to collapse
This should be a one time issue. One of the latest versions of Magisk changed the default location of the boot.img backup. They released it in December after most of us had already upgraded to the December Pixel update. This means we used the older version of Magisk when we installed the Dec update and it saved the backup to the old/original location. We then updated Magisk sometime later in December, but the Magisk update doesn't move the backup file to the new location (a poor execution from the Magisk team IMHO). Because we are now on the updated version, it expects the boot.img backup to be in the new location, but it is still in the old location and Magisk doesn't check that old location (again, a poor execution from the Magisk team IMHO).
To fix this you have several options.....
Option one is to find the original backup location that Magisk used for the boot.img and move it to the new backup location that Magisk uses. Unfortunately, I don't know where those backup locations are and didn't feel like researching it, so I used one of the other methods.
Option two is to "reinstall" Magisk (choose the patch file option and select the stock boot.img that may still on the phone from whatever the last update was (if you sideloaded the update and then had to rerooted the phone)- or download it from the applicable factory image and move it to the phone) to force Magisk to backup the current boot.img file to the new location. Stop after this initial step (ie you don't actually need to flash the patched file because it has already been done). Then you should be able to follow the normal Magisk update process to move to the January update.
That being said, I have horrible success being able to take the updates OTA (they usually fail) and usually end up sideloading the update. That is the final option - sideload the Jan update and then reroot the phone using the normal root method (ie getting Magisk to patch the stock boot.img file and then flashing the patched file).

Upgrade rooted 2015 16gb Shield TV (non Pro)

Hi
I have a 2015 Shield (non pro) currently running rooted 5.2.0. I am looking to update it with the latest 8.0.1 dev image to keep root. Is there any precautions or extra steps I need to take over what is in the instructions in the download centre. From what I have read I will need to ADB sideload Magisk to get full root access after installing the dev image.

you'll need to patch the boot.img in magisk canary and then flash it
https://forum.xda-developers.com/shield-tv/general/guide-root-nvidia-shield-experience-t3882254

Do I need to unroot or factory reset the rooted 5.2.0 before flashing 8.0.1. Is there any benefit in flashing the dev image rather than the factory image before flashing the patched boot.img.

You should update the firmware OTA. Because you'll flash the OTA you'll need to patch then flash the dev image or this root boot image: https://forum.xda-developers.com/shield-tv/development/kernel-overclock-kernel-2-22-ghz-t3943079

But do I need to unroot etc to do an OTA.

g1dtf said:
But do I need to unroot etc to do an OTA.
Click to expand...
Click to collapse
yes unroot will happen automatically when you install the OTA. if you know how to use adb and follow my steps it's not a big deal though you can get it back quickly

I have just unfroze system upgrade (com.nvidia.ota) and it offers experience 6.3. I guess I have to incrementally install subsequent OTA's until I get to 8.0.1 then follow your guide to re-root using your guide, I am familiar with using ADB although its been quite a while since I last used it.

g1dtf said:
I have just unfroze system upgrade (com.nvidia.ota) and it offers experience 6.3. I guess I have to incrementally install subsequent OTA's until I get to 8.0.1 then follow your guide to re-root using your guide, I am familiar with using ADB although its been quite a while since I last used it.
Click to expand...
Click to collapse
yes correct you need to do it incrementally--it's totally worth it Nvidia has done some great upgrades!

Got it up to 8.0.0 installing the OTA's. However the next OTA offered is 8.0.2 rather than 8.0.1 which as far as I know has no root options yet as the 8.0.2 images have not been released by NV.

yes but you don't need dev images to root, you can just patch this boot.img and it should give you root (as long as you install the latest Magisk canary and then upgrade through that)
https://forum.xda-developers.com/sh...l-2-22-ghz-t3943079/post81708169#post81708169

False double post please ignore.

Just a little confused as to which boot.img I need to patch. Looked at the XDA link you posted but there are quite a few different ones mentioned in that thread. I am currently running stock 8.0.2 OTA on my 2015 16gb.

g1dtf said:
Just a little confused as to which boot.img I need to patch. Looked at the XDA link you posted but there are quite a few different ones mentioned in that thread. I am currently running stock 8.0.2 OTA on my 2015 16gb.
Click to expand...
Click to collapse
Just boot into twrp using this https://drive.google.com/file/d/1934405D1S0lv52jZMqS-Zny62RIzGWSi/view
Then flash magisk canary in there, and you are done

Thanks! Flashed the latest canary and now rooted on 8.0.2.

How to update the Firmware, Magisk, TWRP on a rooted FireTV Stick 4k (mantis)?

Hello,
I rooted my FireTV Stick 4k (mantis) some time ago with fireISO 1.0, kamakiri-mantis 1.2 (I believe) and it worked just fine until recently. Now it often crashes, is slow or I have to reboot several times before I can use it.
The firmware version is 6.2.6.8, Magisk 20.1, Magisk Manager 7.4.0, TWRP 3.3.1-0. So everything seems a bit outdated and I hope that an update will solve the problems mentioned.
I found several threads on different websites but they are either referring to other devices, software versions or starting situations.
Can someone please show me where I can find a comprehensive guide or tell me how to do the updates, where to find the latest firmware and software versions and what to consider in general (e.g. I never had to use TWRP after the rooting and now, when I cancel the rebooting on the stick and start TWRP it asks me if I want to leave the system partition read only or allow changes. No idea.)?
Thanks for your help!

There are some threads, guides and youtube videos on how to install roms and how to interact with twrp...
but if you want to keep your device 'kamakiri vulnerable via shorting' then you want only install this prerooted rom to your stick:
Fire TV Stick 4K (mantis) Prerooted Stock Images [6.2.8.1_r3]
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might. First, you must be unlocked. You can follow the instructions...
forum.xda-developers.com
Make sure that you flash July 17, 2021 - 6.2.8.1.r2 first, then 6.2.8.1 r3 if you like. Don't forget to disable the OTA updates.

Sus_i said:
There are some threads, guides and youtube videos on how to install roms and how to interact with twrp...
but if you want to keep your device 'kamakiri vulnerable via shorting' then you want only install this prerooted rom to your stick:
Fire TV Stick 4K (mantis) Prerooted Stock Images [6.2.8.1_r3]
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might. First, you must be unlocked. You can follow the instructions...
forum.xda-developers.com
Make sure that you flash July 17, 2021 - 6.2.8.1.r2 first, then 6.2.8.1 r3 if you like. Don't forget to disable the OTA updates.
Click to expand...
Click to collapse
Thanks for the link. I've already found this thread but since I don't know what "NEVER FLASH A STOCK ROM >= 6.2.8.0 AFTER FLASHING 6.2.8.1_r2 OR LATER! THIS WILL BLOW AN EFUSE." means I was hoping that I can flash a stock rom instead of a pre-rooted so that I don't have to be careful about that blow efuse thingy.
Btw, what means keep your device "kamakiri vulnerable via shorting"?

Droidknot said:
Thanks for the link. I've already found this thread but since I don't know what "NEVER FLASH A STOCK ROM >= 6.2.8.0 AFTER FLASHING 6.2.8.1_r2 OR LATER! THIS WILL BLOW AN EFUSE." means I was hoping that I can flash a stock rom instead of a pre-rooted so that I don't have to be careful about that blow efuse thingy.
Click to expand...
Click to collapse
You can flash stock roms, easiest is to enable updates and the OTA app will install the latest...
But netflix and prime video etc won't play stuff, until you flash an updated trustzone (TZ image) to your stick (which the 6281r2 prerooted does for you).
Together with this updated TZ image, every stock rom above 6.2.8.0 burns an efuse in the SOC, which will prevent/patch the kamakiri shorting method, i.e. unbricking via short is gone forever.
Droidknot said:
Btw, what means keep your device "kamakiri vulnerable via shorting"?
Click to expand...
Click to collapse
You may know how you did the unlock in the first place, open and short a special point...!?
PS: The prerooted was put together because the blow efuse thingy, i.e. efuse burning is disabled in the prerooted...

Sus_i said:
You can flash stock roms, easiest is to enable updates and the OTA app will install the latest...
But netflix and prime video etc won't play stuff, until you flash an updated trustzone (TZ image) to your stick (which the 6281r2 prerooted does for you).
Together with this updated TZ image, every stock rom above 6.2.8.0 burns an efuse in the SOC, which will prevent/patch the kamakiri shorting method, i.e. unbricking via short is gone forever.
Click to expand...
Click to collapse
Thanks for the explainations, that makes it clearer. Isn't it possible to manually flash a specific firmware version (which doesn't patch the kamakiri shorting method) with TWRP? E.g. to download a stock rom zip file and then flash it with TWRP?
Sus_i said:
You may know how you did the unlock in the first place, open and short a special point...!?
PS: The prerooted was put together because the blow efuse thingy, i.e. efuse burning is disabled in the prerooted...
Click to expand...
Click to collapse
Yes, I know the shorting method but I didn't know that later firmware versions make this method impossible. The warning "NEVER FLASH A STOCK ROM >= 6.2.8.0 AFTER FLASHING 6.2.8.1_r2 OR LATER! THIS WILL BLOW AN EFUSE." made me believe that it is basically possible to (manually) flash a specific stock rom, e.g. 6.2.7.1.
After flashing the pre-rooted rom will it still be possible to OTA update to the latest version and bring the device back to stock mode?
If not, I would prefer to update Magisk, Magisk Manager and TWRP (if this can be updated separately) first and to check if this already solves the issues. If it's always possible to go back to stock mode, flashing the pre-rooted rom would maybe be the easier way.
Do I have to set up TWRP as read only or read write on system partition? I ask because some sources say this, other say that.

Droidknot said:
Thanks for the explainations, that makes it clearer. Isn't it possible to manually flash a specific firmware version (which doesn't patch the kamakiri shorting method) with TWRP? E.g. to download a stock rom zip file and then flash it with TWRP?
Click to expand...
Click to collapse
Ofc thats possible, but as I said DRM is broken because the new OS needs a new TZ
Droidknot said:
After flashing the pre-rooted rom will it still be possible to OTA update to the latest version and bring the device back to stock mode?
Click to expand...
Click to collapse
It's possible, but all new Stock will burn the efuse by default, if the new TZ is also there.
Easiest is if you just flash the prerooted 6281r2 (which updates the TZ so no DRM issues for you), then the 6281r3, done. Make sure that updates are disabled and thats it. Watch out if your issues are gone.
If you somehow/sometimes want the stick at a higher stock OS than 6281, @SweenWolf released a patch, which deletes the efuse burner for you... needs to be flashed just after the stock rom.