Database Users

Couldn't update Installation problem with august update

So this week i hadn't time enough to install the august update since my phone is rooted so i decided to do it now. What i did before trying to download the update :
1.Deleted all magisk modules that i had then rebooted
2.Unistalled magisk using restore image then rebooted
3.Went to sys update downloaded and it says installation failed
What do to? I'm not rooted now and i don't have twrp installed.
PS. don't want to install it via fastboot/miflash

Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.

emiljano539 said:
PS. don't want to install it via fastboot/miflash
Click to expand...
Click to collapse
If you don't want to use Miflash (Why ?) you can boot temporary TWRP and flash .zip here:
https://forum.xda-developers.com/showpost.php?p=77353883&postcount=542

sipollo said:
If you don't want to use Miflash (Why ?) you can boot temporary TWRP and flash .zip here:
https://forum.xda-developers.com/showpost.php?p=77353883&postcount=542
Click to expand...
Click to collapse
Do i lose my data if i flash this via twrp?
Idk i don't really trust miflash

emiljano539 said:
Do i lose my data if i flash this via twrp?
Idk i don't really trust miflash
Click to expand...
Click to collapse
You won't lose your data.

ludditefornow said:
Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.
Click to expand...
Click to collapse
flashed the stock boot image tried to install it but again it shows that error , i guess the only thing i can do is to flash it manually via fastboot/miflash

sipollo said:
You won't lose your data.
Click to expand...
Click to collapse
Okay thanks, do i have to remove the magisk and flash the stock boot.img or it doesn't matter?

emiljano539 said:
Okay thanks, do i have to remove the magisk and flash the stock boot.img or it doesn't matter?
Click to expand...
Click to collapse
It doesn't matter. You'll have to reinstall Magisk (if you want to).

sipollo said:
It doesn't matter. You'll have to reinstall Magisk (if you want to).
Click to expand...
Click to collapse
which one should i install from them because there are 2 tissot-T files ( for twrp)
"tissot-T-OPM1.171019.026.8.8.23.zip" or "tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip" ?

emiljano539 said:
which one should i install from them because there are 2 tissot-T files ( for twrp)
"tissot-T-OPM1.171019.026.8.8.23.zip" or "tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip" ?
Click to expand...
Click to collapse
tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip
The other file is the latest beta.

sipollo said:
tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip
The other file is the latest beta.
Click to expand...
Click to collapse
I installed the zip from twrp and now after reboot i am stucked in bootloop now i can't even boot into twrp. What to do?
After i flashed it in the end says:
Failed to mount /system Invalid argument

Which TWRP did you use?

sipollo said:
Which TWRP did you use?
Click to expand...
Click to collapse
the official one. what version should i use?
its funny now that i flashed the stock rom via mi flash tool and now again the installation shows error..

ludditefornow said:
Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.
Click to expand...
Click to collapse
I'm facing same issue and I was following the guide.

Same here, can't install set Ota, even after remove magisk.
Other thing, cell won't show screen to put pin to boot, previous pin of sim so I think encryption is disable!? Any idea?

Problem flashing stock image

I have UB and rooted with magisk 20.1. I rooted the October build by patching the boot image using magisk. I try to flash the new November stock image and it fails. It says
Writing boot
Failed (failed to write to partition Not found)
I think it may be connected to booting into slot a or b. Maybe?
Can anybody help?

You already took the November OTA or are you still on October?

ctfrommn said:
You already took the November OTA or are you still on October?
Click to expand...
Click to collapse
I'm on October trying to flash November

Pretty sure you cant flash the boot image alone. I always flash the stock boot for the build Im currently on then take the OTA. I think there is a new bootloader for November. Not 100% on that though.

I'm just trying to flash the full factory November stock image. I downloaded it, unzip it, plug in the phone in fastboot and double click the run me bat file.
This has always been fine before but I am new to pixel 3a and have only done this once before, on October build. But I came from an original pixel so I've spent 2 years updating that in this way.
I can't work out why the flash is failing.

Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.

ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
I've tried flashing October factory image and get the exact same result. Not sure what else to try.

ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
Sorry just reread your post. Will try and reflash boot IMG. I do that with fastboot flash boot.img?
Thanks

Yes.... fastboot flash boot boot.img

ctfrommn said:
Yes.... fastboot flash boot boot.img
Click to expand...
Click to collapse
Have tried reflashing boot.img and still won't update ota and same result trying to flash factory image. Any other ideas? And thanks very much for your help

ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
Do I need to flash boot.img to both slots a and b? If so how do I do that?

I only ever flash the one in use.
Just fastboot flash boot boot.img is all you need.
Your can also always just clean flash the OTA. Just download it, factory reset, adb sideload the OTA in recovery.
I've done that a few times now.

ctfrommn said:
I only ever flash the one in use.
Just fastboot flash boot boot.img is all you need.
Your can also always just clean flash the OTA. Just download it, factory reset, adb sideload the OTA in recovery.
I've done that a few times now.
Click to expand...
Click to collapse
Thanks. Will try things tomorrow. It's late here in London. But I can't get a twrp.img to work. It doesn't seem to mount the system and I can't flash anything. Have you got twrp to work? I'll come back to you in about 18hrs if that's ok?

TWRP doesn't work with Q. Just use stock recovery to sideload.

ctfrommn said:
TWRP doesn't work with Q. Just use stock recovery to sideload.
Click to expand...
Click to collapse
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much

Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
Yes, OTA and factory images are essentially the same thing just packaged differently.
And the easiest way to reroot is to just download and repatch the new stock image, or flash a custom pre patched kernel.

Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
The OTA zip is packaged differently and does not include a boot.img file that we can use. (I'm sure it must be in there somewhere, but not in a usable form). Therefore you must download the "Factory Image" from Google. Unzip it, open it where you will find another zip file inside. Open that second zip file and you will find the boot.img file there. Move that boot.img file to your phone so that Magisk can access it and to modify it.
https://developers.google.com/android/images

Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
FYI here are the steps I took to update my rooted 3a this morning:
1. in Magisk Manager select Uninstall and select restore images (I did this because I kept getting a 'installation error' on the OTA page)
2. Like an idiot I rebooted my phone, do not reboot! So I had to reinstall magisk
2a. copy the boot.img of Oct to my phone to have it patched by magisk
2b. fastboot flash boot boot_patched.img
3. the OTA downloaded while I was on the stock boot.img so I just followed the magisk instructions to install the OTA in the other partition
Next month I'll just jump from step 1 to 3 and carry on being rooted.

The simplest way to update when youre rooted is to......
Reflash the stock boot from the current build youre on
Take the OTA directly on the phone
Download stock image from new build and move it to phone
Patch with Magisk and move to your PC
Fastboot flash boot boot.img
Ive done this for the last 3 updates and it works perfectly every time......I obviously substitute my kernel for the patched boot but the process is the same. I find this far simpler than messing with Magisk

Thanks for all the suggestions but I still cannot update.
I have tried restoring boot.img
data reset from recovery
relocking bl - ota fails
Unlocking bl again - won't flash using ADB
There is no problem with the phone being recognised on ADB, the flash Just fails as the screen shot in my opening post. I'm thinking it may be connected to needing to flash to the inactive slot.
Anyone got any ideas?

Problem installing Magisk Android 11

Hello all,
When still on Android 10 I had Magisk stable installed and working.
Now, after upgrade to Android 11 I cannot get it to work.
Here's what I did:
- first off, I have factory reset the phone (without erasing external storage) because of WiFi not working anymore on Android 10 (Omega kernel problem maybe?).
- update the phone to Android 11 in Settings, System, System updates (now I'm on Android 11 build IN2023_15_200930)
- install Magisk Manager from here
- download the firmware from here
- extract boot.img from firmware zip file
- copy boot image from pc to mobile
- patch boot image with Magisk manager
- copy magisk_patched.img from mobile to pc
- flash magisk_patched.img
Code:
❯ fastboot flash boot magisk_patched.img
Sending 'boot_a' (43464 KB) OKAY [ 1.824s]
Writing 'boot_a' OKAY [ 0.131s]
Finished. Total time: 1.966s
- reboot the device
Now, when I open Magisk Manager, it says Magisk Installed ' N/A' and I expect to be able to install Magisk using 'direct install'.
However this option 'direct install' is not shown, only Download Zip Only & Select and Patch a File.
What is missing here?
Any help is appreciated!
Edit: I got it working using canary build of magisk manager in stead of the stable build.

Got the same issue plus the phone sometimes turn into a bootloop.

saphirrot said:
Got the same issue plus the phone sometimes turn into a bootloop.
Click to expand...
Click to collapse
I got it working using canary build of magisk manager in stead of the stable build.

lvbaal said:
I got it working using canary build of magisk manager in stead of the stable build.
Click to expand...
Click to collapse
I tried both, same result

saphirrot said:
I tried both, same result
Click to expand...
Click to collapse
Flash to both slots. Not just one.
Fastboot flash boot_a "name of boot IMG"
Fastboot flash boot_b "name of boot IMG"

saphirrot said:
I tried both, same result
Click to expand...
Click to collapse
Maybe Wipe Cache in recovery? I did that anyway

Tried wiping Cache and flashing to both Slots.. still bootloop..

saphirrot said:
Tried wiping Cache and flashing to both Slots.. still bootloop..
Click to expand...
Click to collapse
Sorry for you man! Maybe this than?

Uploaded some logs, maybe someone can helpView attachment 2020-10-11_16.00.zip

@saphirrot
Quite possible it's the magisk patched image you're using, obtain another, best to extract it yourself.

dladz said:
Quite possible it's the magisk patched image you're using, obtain another, best to extract it yourself.
Click to expand...
Click to collapse
Patched my own boot.img, still the same issue... thats so Strange, because I havent modified anything after the o11 Update..

saphirrot said:
Patched my own boot.img, still the same issue... thats so Strange, because I havent modified anything after the o11 Update..
Click to expand...
Click to collapse
Don't flash twrp whatever you do it'll end up in crash mode, not suggesting you will but a chap I was helping did it and that's what happened. Forced him to use MSM tool.
Try another patched image, if you're on EU/UK then I have one in my thread in the guides section. Just don't do anything else. If needs be I can upload a stock boot.img if your get stuck in a boot loop, least then your can boot.
What version of magisk did you use to patch?
Also what was the commands you used to flash it in fastboot?

Using the canary magisk Version, latest ofc. Also tried all patched boot.img posted around here. Also extracted my own working boot.img and Patched it with magisk. Then flashed IT via Fastboot and bootloop again. The logs should help to find my problem

saphirrot said:
Using the canary magisk Version, latest ofc. Also tried all patched boot.img posted around here. Also extracted my own working boot.img and Patched it with magisk. Then flashed IT via Fastboot and bootloop again. The logs should help to find my problem
Click to expand...
Click to collapse
Dont flash your image just boot it first. And if it boots and you have root you can install magisk from manager permanently

Had to factory Reset the Phone, now root works fine

Same Problem
yeah same problem here... you can exit the bootloop by flashing the stock boot.img on it.
But still, neither canary or the standard does work for rooting.

saphirrot said:
Using the canary magisk Version, latest ofc. Also tried all patched boot.img posted around here. Also extracted my own working boot.img and Patched it with magisk. Then flashed IT via Fastboot and bootloop again. The logs should help to find my problem
Click to expand...
Click to collapse
Were you using lucky patcher?? Sounds a lot like you are.

dladz said:
We're you using lucky patcher?? Sounds a lot like you are.
Click to expand...
Click to collapse
So you're saying that lucky patcher is the problem?

MrZaga said:
So you're saying that lucky patcher is the problem?
Click to expand...
Click to collapse
Lol well that depends mate, are/ were you using it.
Lucky patcher breaks so much when it's used, bootlooping is one of those symptoms.
I intend to make a thread saying do not use it as you're the fifth person I've seen now with issues I've troubleshooted and the culprit was that stupid app.

dladz said:
Lol well that depends mate, are/ were you using it.
Lucky patcher breaks so much when it's used, bootlooping is one of those symptoms.
I intend to make a thread saying do not use it as you're the fifth person I've seen now with issues I've troubleshooted and the culprit was that stupid app.
Click to expand...
Click to collapse
As it sounds, uninstalling doesn't help then. But do you know why it bootloops only when using the patched img, and not when using the stock img?

Device boots only into fastboot after Magisk 22.0 update

I had Magisk 21.4 and tried to update to Magisk 22.0, but after a restart the phone rebooted to fastboot and does not boot to system
I downloaded the firmware from oneplus's website (11.0.4.4.IN11BA) and extracted the boot.img with the payload dumper, and flashed it through fastboot (fastboot flash boot boot.img)
But it still will not boot to system, it bootlops
Any ideas?

Nikos2k said:
I had Magisk 21.4 and tried to update to Magisk 22.0, but after a restart the phone rebooted to fastboot and does not boot to system
I downloaded the firmware from oneplus's website (11.0.4.4.IN11BA) and extracted the boot.img with the payload dumper, and flashed it through fastboot (fastboot flash boot boot.img)
But it still will not boot to system, it bootlops
Any ideas?
Click to expand...
Click to collapse
Try to re flash 21.4

Nameless Foe said:
Try to re flash 21.4
Click to expand...
Click to collapse
yes, but how?

Nikos2k said:
yes, but how?
Click to expand...
Click to collapse
Are you able to boot into fastboot mode?

Nameless Foe said:
Are you able to boot into fastboot mode?
Click to expand...
Click to collapse
Yes

Nikos2k said:
Yes
Click to expand...
Click to collapse
Are you able to flash the older version magisk through fast boot?

Nameless Foe said:
Are you able to flash the older version magisk through fast boot?
Click to expand...
Click to collapse
Don't know how
Magisk 21.4 is a .zip file: Magisk 21.4
Is it possible to flash it through fastboot ?

Nameless Foe said:
Are you able to flash the older version magisk through fast boot?
Click to expand...
Click to collapse
You might have to reset your phone via fastboot then flash the stock firmware

Nameless Foe said:
You might have to reset your phone via fastboot then flash the stock firmware
Click to expand...
Click to collapse
How can i reset it from fastboot?
And will I lose all my data?

Did you have any luck restoring your OP8 pro? The same thing (updating from Magisk 21.4 to 22.0) soft-bricked my 8pro. I believe soft-brick is the correct term since it's in a bootloop at loading O.S.--I guess I'll try to figure out how to flash Magisk 21.4, but I've reset it through fastboot, and when I try to flash boot.img garnered through payload dumper, I keep getting messages that says I cannot flash to critical partitions. I've tried Mauronofio's all-in-one tool but keep getting flash-bat-all missing. Man I sure would appreciate any earnest suggestions. Thank you.

Just boot the image you originally patched it with, that'll get it to boot
Then remove 22 and install 21.4
If that doesn't work then boot the stock boot image.
Magisk 22 beta causes a bootloop.

Nikos2k said:
How can i reset it from fastboot?
And will I lose all my data?
Click to expand...
Click to collapse
Just use the MSM tool,, easier and risk free

wgs1028 said:
Did you have any luck restoring your OP8 pro? The same thing (updating from Magisk 21.4 to 22.0) soft-bricked my 8pro. I believe soft-brick is the correct term since it's in a bootloop at loading O.S.--I guess I'll try to figure out how to flash Magisk 21.4, but I've reset it through fastboot, and when I try to flash boot.img garnered through payload dumper, I keep getting messages that says I cannot flash to critical partitions. I've tried Mauronofio's all-in-one tool but keep getting flash-bat-all missing. Man I sure would appreciate any earnest suggestions. Thank you.
Click to expand...
Click to collapse
I didn't manage to restore it by just flashing boot.img
I then flashed all the image files from the output of payload dumper, but it didn't work either
Then wiped userdata (by using -w switch of fastboot), still no luck
Then changed active slot and flashed all the image files to that slot, and it booted successfully

dladz said:
Just boot the image you originally patched it with, that'll get it to boot
Then remove 22 and install 21.4
If that doesn't work then boot the stock boot image.
Magisk 22 beta causes a bootloop.
Click to expand...
Click to collapse
i didn't manage to successfully boot it with the stock boot.img ...

Nikos2k said:
i didn't manage to successfully boot it with the stock boot.img ...
Click to expand...
Click to collapse
What did you end up doing? Strictly speaking the only thing that changes should be the app and the boot image.
So fixing them should be all that's required

dladz said:
What did you end up doing? Strictly speaking the only thing that changes should be the app and the boot image.
So fixing them should be all that's required
Click to expand...
Click to collapse
flashed all the images extracted from the payload dumper, to both slots, including wiping the userdata

Nikos2k said:
flashed all the images extracted from the payload dumper, to both slots, including wiping the userdata
Click to expand...
Click to collapse
Then did you try safe mode

Add bookmark
#45
For the Oneplus 8 pro with 11.0.4.4.IN11AA I had to get a boot.img (for 11.0.4.4IN11AA) and flashed it with adb via fastboot (from PC), then my phone started up without root but still unlocked (and none of my data was lost). I reinstalled Magisk 22.0 (apk) and then put the boot.img on my sdcard and used Magisk to patch my boot.img and then i booted into fastboot and and flashed the patched boot.img via adb fastboot(from my PC). I never orginally had Magisk hidden so not sure why my phone lost root after the Magisk 22.0 update. Hopefully this helps someone onto the right path.

Nikos2k said:
flashed all the images extracted from the payload dumper, to both slots, including wiping the userdata
Click to expand...
Click to collapse
Oh you installed all those images to the boot slots? Why? They need to be flashed to particular partitions AFAIK

dladz said:
Oh you installed all those images to the boot slots? Why? They need to be flashed to particular partitions AFAIK
Click to expand...
Click to collapse
No no, i installed them to their respective partitions
Like a total firmware reset

How to update to 11.0.8.8IN11AA on pre rooted device

Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.

paq1170 said:
Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.
Click to expand...
Click to collapse
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.

MrEvilPanda said:
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.
Click to expand...
Click to collapse
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?

Sneakdovi said:
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?
Click to expand...
Click to collapse
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot commands.

MrEvilPanda said:
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot comma
Click to expand...
Click to collapse
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.

paq1170 said:
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.
Click to expand...
Click to collapse
We only need the boot.img(correct one) to proceed with root no need to download the entire stock rom.

Where are you guys getting 11.0.8.8IN11AA? Full zip?
Nothing on Oxygen updater for me yet.

Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...

datnewnew said:
Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...
Click to expand...
Click to collapse
Things like this makes me so cautious and ask so many questions. Hope you didnt soft brick your device?

Okay it worked out somehow, i was looking for a stock boot.img, and was gonna flash that to try and save it, but had trouble with my pc recognizing my oneplus in fastboot mode, so i pressed both vol up/down and power at the same time to while being connected with usb cable, to try and get into fastboot, then screen went black but my PC got some pop ups for recognizing a device with unavailable drivers, then i just press vol up and power after a minute of it being black, phone rebooted and it loaded past the booting animation into android... weird stuff worked out, even after a dozen reboots with hardware keys, even letting it spin the animation for an hour...
I'm never updating again ahahhah
edit: if you do update, make sure you disable all your magisk/xposed addons and some native os call recording module... thats what i learned while googling yesterday, and its something i did not do, that could of have possibly contributed to my headaches

What i ended up doing that worked was;
. Flash stock 11.0.7.7 boot.img to slot A & B to unroot the phone.
. Reboot and install the ota update. I had no magisk modules to uninstall.
. After updating i downloaded the stock boot.img for 11.0.8.8 then patched and flashed to get rooted again.
Its a longer process but quite safer for me.

It's the same on each firmware, providing you have the full update available to you.
Use oxygen updater and grab the full update, download and install but don't Reboot.
Open Magisk send install after OTA.
Then reboot.
If you're unable to grab the full update then probably best to update then boot lineage recovery and sideload Magisk.zip using lineage recovery, then flash and you're done.

Could someone post boot img I can't find this 11.8.8 to download.
Thanks.

Mchlbenner51 said:
Could someone post boot img I can't find this 11.8.8 to download.
Thanks.
Click to expand...
Click to collapse
Same here please, cant find the 11.0.8.8.IN11AA anywhere.

If 8.8AA is in oxygen updater (full update)
Then make your own, using someone else's comes with inherent issues and risks.
It's good practice to make your own.

h4x3r101 said:
Same here please, cant find the 11.0.8.8.IN11AA anywhere.
Click to expand...
Click to collapse
Go here: https://forum.xda-developers.com/t/...magisk_patched-boot-img.4255757/post-85522541