Database Info

[Q] OTA Update

So Cyanogen sent out the 44R ota today and I am rooted with a custom recovery. My current software version is 38R android 4.4.4. So in order to do the ota:
1. I need to go into SuperSU and do the permanant unroot.
2. Reboot
3. Flash stock recovery.
So for step 3 I downloaded the 38R stock firmware from cygen's site. Can I extract it and flash just the recovery? Will this work?

skyguy126 said:
So Cyanogen sent out the 44R ota today and I am rooted with a custom recovery. My current software version is 38R android 4.4.4. So in order to do the ota:
1. I need to go into SuperSU and do the permanant unroot.
2. Reboot
3. Flash stock recovery.
So for step 3 I downloaded the 38R stock firmware from cygen's site. Can I extract it and flash just the recovery? Will this work?
Click to expand...
Click to collapse
You don't need to do any of that. No unrooting is required. You can flash the OTA with a custom recovery. All you need to do is initiate the update process through your Settings menu.
Transmitted via Bacon

I'll try that next time but I used my method and it worked fine

skyguy126 said:
I'll try that next time but I used my method and it worked fine
Click to expand...
Click to collapse
Of course it did, but what I'm saying is it's completely unnecessary to do all that.
Transmitted via Bacon

timmaaa, what do you mean with
All you need to do is initiate the update process through your Settings menu.
Click to expand...
Click to collapse
with rooted OPO, custom recovery and xposed i don't can flash the regular OTA right? i need to take the modified OTA and uninstall xposed? is this the correct way?

RotesMeerJogger said:
timmaaa, what do you mean with
with rooted OPO, custom recovery and xposed i don't can flash the regular OTA right? i need to take the modified OTA and uninstall xposed? is this the correct way?
Click to expand...
Click to collapse
If you uninstall Xposed you can use the normal OTA. If you don't want to uninstall Xposed you can use the modified OTA. The custom recovery and root make no difference either way.
Transmitted via Bacon

hey thank you very much timmaaa! works perfect after update i only need root again

Thanks for the help everyone!

How to flash another kernel over franco

I have a nexus 5 running marshmallow Stock ROM rooted with Franco kernel and xposed framework installed. When I was on lollipop ,if I had to change kernels ,I would just flash the stock kernel using flashify and then flash custom kernel.
But now,i have Franco kernel running and I plan to flash code blue kernel. If I try to flash the stock kernel using flashify ,the phone won't boot,the Marshmallow boot Animation occurs infinitely. So what should I do? The superSU version is 2.52.
Please explain me the steps to flash code blue kernel.One the members suggested flashing superSU 2.61 but for that I need to flash the stock partition.I don't want to do that.Is there any workaround?
Thanks in advance

Flash stock System and Boot images, then flash code blue kernel. This is probably the safest solution, I don't know if there are many other options available.

Try flashing stock system.img and boot.img then blu_spark + SuperSU 2.61
EDIT: too late

ReAvenger said:
Flash stock System and Boot images, then flash code blue kernel. This is probably the safest solution, I don't know if there are many other options available.
Click to expand...
Click to collapse
Primokorn said:
Try flashing stock system.img and boot.img then blu_spark + SuperSU 2.61
EDIT: too late
Click to expand...
Click to collapse
Will i lose root if I do that? As I said I also have xposed installed.Will i also lose the xposed modules ? also,can you provide me with the links or else zip files would be more helpful so that i can flash them right away .
Sorry if I'm asking silly questions,please bare with me .

goutham kumar muvva said:
Will i lose root if I do that? As I said I also have xposed installed.Will i also lose the xposed modules ? also,can you provide me with the links or else zip files would be more helpful so that i can flash them right away .
Sorry if I'm asking silly questions,please bare with me .
Click to expand...
Click to collapse
Yes you will have to root again and install Xposed framework. You won't lose your modules though.
Use this to download the nexus 5 factory images: https://is.gd/84Nk59
Tutorials are availabe to know how to flash them with fastboot.

Apply monthly update, with Magisk and Xposed, without booting...

I want to update my Pixel phone with the latest monthly update, but also install Magisk and Xposed. But I want to do this without rebooting so that Xposed is always working.
How do I do this?
Is Flashfire the best way to do this, or can I do this manually.
I used to update my Nexus5 by downloading the full monthly update, opening the zip on my PC and then flashing the system update before booting into TWRP to apply Xposed.
But how do I do this on a pixel with the A/B partitions and the like.
Any help would be appreciated.
Ta.

scutworker said:
I want to update my Pixel phone with the latest monthly update, but also install Magisk and Xposed. But I want to do this without rebooting so that Xposed is always working.
How do I do this?
Is Flashfire the best way to do this, or can I do this manually.
I used to update my Nexus5 by downloading the full monthly update, opening the zip on my PC and then flashing the system update before booting into TWRP to apply Xposed.
But how do I do this on a pixel with the A/B partitions and the like.
Any help would be appreciated.
Ta.
Click to expand...
Click to collapse
I could be wrong but I don't think flashfire works with magisk but essentially no there is no way to do what it is you want. You could manually flash the factory images and re-mod or wait for a custom kernel you like to integrate latest security patches and flash that.

KittyRgnarok said:
I could be wrong but I don't think flashfire works with magisk but essentially no there is no way to do what it is you want. You could manually flash the factory images and re-mod or wait for a custom kernel you like to integrate latest security patches and flash that.
Click to expand...
Click to collapse
Thanks.
So is it just a case of boot to bootloader, manually flashing the factory image, then boot TWRP and flash Magisk and Xposed?
Ta.

scutworker said:
Thanks.
So is it just a case of boot to bootloader, manually flashing the factory image, then boot TWRP and flash Magisk and Xposed?
Ta.
Click to expand...
Click to collapse
Yep. You can also remove the -w in the flash-all.sh file so you can keep your data. (Or flash-all.bat if on windows)

Is there a latest stock ROM I can flash instead of the custom ROM I'm using now?

I'm TWRP'd and Magisk'd running a custom ROM (Havoc}, but it's a little buggy. I'm looking to flash a stock ROM with the latest OxygenOS, and then maybe use a Magisk module over that.
Can I? And if so, can you point me to the correct custom ROM thread? I see a couple, but not sure which one is flashable, and which one is for restoring the phone to completely stock (removing TWRP, etc.).

I suggest using this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
-BoneZ- said:
I see a couple, but not sure which one is flashable, and which one is for restoring the phone to completely stock (removing TWRP, etc.).
Click to expand...
Click to collapse
I don't think you can flash a stock ROM, and keep TWRP without flashing TWRP again. TWRP will always be removed when flashing a stock ROM, since recovery doesn't reside on it's own partition for this device, but rather is on boot.img, which by definition needs to be flashed with the ROM (contains the kernel).
AFAIK, you will need to flash the stock ROM then flash TWRP and Magisk again. To do that, fastboot flash the above linked stock ROM, then fastboot boot TWRP.img, then in TWRP flash TWRP installer zip and flash Magisk. Wouldn't take long to do, just have the TWRP zip and Magisk zip on the phone ready to go, before you flash the stock ROM.

redpoint73 said:
I suggest using this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
I don't think you can flash a stock ROM, and keep TWRP without flashing TWRP again. TWRP will always be removed when flashing a stock ROM, since recovery doesn't reside on it's own partition for this device, but rather is on boot.img, which by definition needs to be flashed with the ROM (contains the kernel).
AFAIK, you will need to flash the stock ROM then flash TWRP and Magisk again. To do that, fastboot flash the above linked stock ROM, then fastboot boot TWRP.img, then in TWRP flash TWRP installer zip and flash Magisk. Wouldn't take long to do, just have the TWRP zip and Magisk zip on the phone ready to go, before you flash the stock ROM.
Click to expand...
Click to collapse
I want to flash havoc OS and want to know if I can go back to OOS if I download the full OTA zip and flash it like you normally would (twrp and magisk)

D.Va said:
I want to flash havoc OS and want to know if I can go back to OOS if I download the full OTA zip and flash it like you normally would (twrp and magisk)
Click to expand...
Click to collapse
I have the same question. I'm on Havoc now and unencrypted and would like to back up Havoc and go back to OOS for now due to WiFi calling not working. With out having to reflash Twrp etc

The_Keeper86 said:
I have the same question. I'm on Havoc now and unencrypted and would like to back up Havoc and go back to OOS for now due to WiFi calling not working. With out having to reflash Twrp etc
Click to expand...
Click to collapse
Anyone?

General Global 11.2.6.6 rooted!!!

First off I'm not responsible for anything that happens to your device
Attached below is the patched image for OnePlus 9 global 11.2.6.6
Flash via fastboot
For support and faster answer look here

Thank you for this! Since Magisk removed the option for OTA install, I was forced to do it the harder way... But you my friend made it much easier on me ! Thank you!!

Sorry for newbie's question, what's the difference between the two files? one is stock and one is patched?

Yes. Stock has to be flashed to take next ota. And patched is for root on current rom. Since op9 now uses google ota if any partitions are modified including the boot image ,it will fail.

Jg1234 said:
Thank you for this! Since Magisk removed the option for OTA install, I was forced to do it the harder way... But you my friend made it much easier on me ! Thank you!!
Click to expand...
Click to collapse
When did they remove OTA install? Mine still has it....

illusiveairforce said:
When did they remove OTA install? Mine still has it....
Click to expand...
Click to collapse
Mine still there as well. But I like to flash stock boot image back. Take ota. Then fastboot boot patched.img. Dump current boot image to sd through shell. Then direct install in magisk. I've seen many users have issues taking ota's using the other method. As in not even being able to boot or booting back into old build . So I prefer this way. Wanna avoid the msm tool and not loose data on device/have to factory reset.

mattie_49 said:
Mine still there as well. But I like to flash stock boot image back. Take ota. Then fastboot boot patched.img. Dump current boot image to sd through shell. Then direct install in magisk. I've seen many users have issues taking ota's using the other method. As in not even being able to boot or booting back into old build . So I prefer this way. Wanna avoid the msm tool and not loose data on device/have to factory reset.
Click to expand...
Click to collapse
What are the shell commands to extract the stock boot?

Amd4life said:
What are the shell commands to extract the stock boot?
Click to expand...
Click to collapse
we are making a group for global only and help can be found there

Amd4life said:
What are the shell commands to extract the stock boot?
Click to expand...
Click to collapse
'dd' command in Linux - GeeksforGeeks

Edit- I got it, I had to flash original images and then updates showed up. Thanks for posting these images.
Hi, thanks for posting the images. I assume global as in the US AA model since that is the only model with OTA from googles server right? The reason I was asking is I am on 11.0.4.4 and never received the notification for the update yet, but using oxygen updater, when I go in settings and check advanced mode, it shows a incremental update. My system under local file of course can't see it or will not show the update. I figured I could fastboot boot the stock image and then maybe it system could see the update, but when I try, the device just hangs on the fastboot screen(right before normally booting). I tried with my image and it booted. Do you have any suggestions? Thanks

Steps as follows if on rooted 11.2.5.5
1. flash stock 11.2.6.6.img
2. install OTA
3. flash patched 11.2.6.6.img
4. profit

TheBurgh said:
Steps as follows if on rooted 11.2.5.5
1. flash stock 11.2.6.6.img
2. install OTA
3. flash patched 11.2.6.6.img
4. profit
Click to expand...
Click to collapse
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?

netgar said:
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?
Click to expand...
Click to collapse
netgar said:
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?
Click to expand...
Click to collapse
You are correct my friend. One needs stock untouched boot image to be able to take next update. If your on 11.2.5.5 you need that boot image to get ota to install correctly. This 11.2.6.6 img if for next round of updates. Here is 11.2.5.5 for anyone that might still be on older build.
Stock 11.2.5.5.img
drive.google.com

netgar said:
Aren't you supposed to flash 11.2.5.5 if you are on 11.2.5.5?
After that uninstall magisk, update ota and 3. and 4. ?
Click to expand...
Click to collapse
mattie_49 said:
You are correct my friend. One needs stock untouched boot image to be able to take next update. If your on 11.2.5.5 you need that boot image to get ota to install correctly. This 11.2.6.6 img if for next round of updates. Here is 11.2.5.5 for anyone that might still be on older build.
Stock 11.2.5.5.img
drive.google.com
Click to expand...
Click to collapse
Appreciate the input. I have been out of the game since the 6t so I am still trying to catch up

UPDATED POST
Alternatively, you could:
1. Go to Magisk manager, and tap Uninstall to unroot. And then regular reboot.*
2. Download and install partial OTA, reboot and confirm update. Reboot to bootloader.
3. Fastboot boot patched boot img**
4. Go to Magisk Manager and direct install for permanent root.
5. Reboot and profit.
*this step presupposes that Magisk has a STOCK boot.img to restore for the unroot procedure. If it does not have that, you're obligated to use the process described in post #11.
**you could actually use a recent previous version of patched boot img (like patched 11244) if the update's patched boot img is still unavailable, and then use Magisk manager to patch the update with a direct install

reaper000 said:
Alternatively, you could:
1. Go to Magisk manager, and tap Uninstall to unroot. And then regular reboot.
2. Download and install partial OTA, reboot and confirm update. Reboot to bootloader.
3. Fastboot boot patched boot img*
4. Go to Magisk Manager and direct install for permanent root.
5. Reboot and profit.
*you could actually use a recent previous version of patched boot img (like patched 11244) if the update's patched boot img is still unavailable, and then use Magisk manager to patch the update with a direct install
Click to expand...
Click to collapse
So doing it this method backs up stock untouched current boot image and reflashes during uninstall of magisk to allow ota to go through.? Since the op9 uses google ota all partitions have to be stock including boot image. Or it fails

reaper000 said:
Alternatively, you could:
1. Go to Magisk manager, and tap Uninstall to unroot. And then regular reboot.
2. Download and install partial OTA, reboot and confirm update. Reboot to bootloader.
3. Fastboot boot patched boot img*
4. Go to Magisk Manager and direct install for permanent root.
5. Reboot and profit.
*you could actually use a recent previous version of patched boot img (like patched 11244) if the update's patched boot img is still unavailable, and then use Magisk manager to patch the update with a direct install
Click to expand...
Click to collapse
this will fail

FizzyAps said:
this will fail
Click to expand...
Click to collapse
What's the command to flash the stock 11.2.5.5 boot.img? I tried renaming the boot_a.img the mattie_49 posted to boot.img but it would not flash.

TheBurgh said:
What's the command to flash the stock 11.2.5.5 boot.img? I tried renaming the boot_a.img the mattie_49 posted to boot.img but it would not flash.
Click to expand...
Click to collapse
Fastboot flash boot boot.img

mattie_49 said:
Fastboot flash boot boot.img
Click to expand...
Click to collapse
Thanks. Got the command to work this time. Tried a few times yesterday but had no luck