Related
Hi there,
Yesterday I have downloaded the full OTA package with Oxygen Updater, then I have dumped the payload and grabbed the stock 10.0.11 boot.img from there, patched with Magisk (after the update install) and then flashed the patched image. I have got root access and Magisk is working fine, but after I flash the patched image, the phone can't see the SIM slots. If I re-flash the stock boot.img, it just works fine - but I loose root of course.
I have tried multiple times to patch the stock boot image, but all my attempts was failed, if I've got root access, the phone can't see the SIM card.
I used this method since 10.0.7 to upgrade and until now it just worked fine, without any problem and I don't have any idea what could go wrong.
Any idea, link, etc are welcome.
Had same problem with 10.0.9 EU, have you disabled all magisk modules? For me that was the cause
Hitman478™ said:
Had same problem with 10.0.9 EU, have you disabled all magisk modules? For me that was the cause
Click to expand...
Click to collapse
No, I didn't disable any module before the update. How should I now proceed?
I have tried this:
- flashed patched boot image
- disabled all the modules
- flashed stock boot image
- flashed patched boot image, now this time the modules were disabled
and other one, because this wasn't worked:
- flashed patched boot image
- uninstalled (with restore images) Magisk
- flashed stock boot image
- flashed patched boot image
but my issue still occurs in both cases. If I disable all the modules the SIM is working with the patched boot image, if I enable any of them, the SIM stops working.
So the problem is that I haven't disabled the modules, but now what should I do?
Also same here
I just bought my 7T and i flashed 10.0.9 EU Magisk working fine but i lost sim card and no WIFI
Please any help
Thanks.
Sir Mohd said:
Also same here
I just bought my 7T and i flashed 10.0.9 EU Magisk working fine but i lost sim card and no WIFI
Please any help
Thanks.
Click to expand...
Click to collapse
Well, I did the hard way → flashed a fastboot ROM with full wipe and started clean. Now it's fully working again - but I had to configure everything...
Unfortunately I couldn't find any better solution to make this work.
Th3Scr34m said:
Well, I did the hard way → flashed a fastboot ROM with full wipe and started clean. Now it's fully working again - but I had to configure everything...
Unfortunately I couldn't find any better solution to make this work.
Click to expand...
Click to collapse
Mine as well working now,
I flashed OB1 EU and i reinstall Magisk again and patch it
So SIM, WIFI, Magisk working fine now,
I think there is a problem with latest update with magisk IDK if some1 can confirm by any chance
Thanks.
Th3Scr34m said:
Hi there,
Yesterday I have downloaded the full OTA package with Oxygen Updater, then I have dumped the payload and grabbed the stock 10.0.11 boot.img from there, patched with Magisk (after the update install) and then flashed the patched image. I have got root access and Magisk is working fine, but after I flash the patched image, the phone can't see the SIM slots. If I re-flash the stock boot.img, it just works fine - but I loose root of course.
I have tried multiple times to patch the stock boot image, but all my attempts was failed, if I've got root access, the phone can't see the SIM card.
I used this method since 10.0.7 to upgrade and until now it just worked fine, without any problem and I don't have any idea what could go wrong.
Any idea, link, etc are welcome.
Click to expand...
Click to collapse
Do you have the OOS native recorder ? Uninstall it and you are good to go. Don't recall if disabling it and rebooting will do the trick
Felheipe said:
Do you have the OOS native recorder ? Uninstall it and you are good to go. Don't recall if disabling it and rebooting will do the trick
Click to expand...
Click to collapse
Yes I had (and have now with the new setup) but I had it before 10.0.9 and didn't cause this kind of issues - actually I did this process 3 times without any problem.
You have to remove call recording module and.than reinstall
Made the OTA update yesterday, stupid as I am, I rebooted after updating causing me to lose root.
When downloading stock image, patching boot.img and transferring the patched boot.img back using fastboot, will that make me lose my apps and data? Can't find a clear answer unfortunatly...
karazz said:
Made the OTA update yesterday, stupid as I am, I rebooted after updating causing me to lose root.
When downloading stock image, patching boot.img and transferring the patched boot.img back using fastboot, will that make me lose my apps and data? Can't find a clear answer unfortunatly...
Click to expand...
Click to collapse
Magisk OTA Upgrade Guides:
https://topjohnwu.github.io/Magisk/ota.html
Sir Mohd said:
Magisk OTA Upgrade Guides:
https://topjohnwu.github.io/Magisk/ota.html
Click to expand...
Click to collapse
Thanks for the link, but I already found that information (and realized my mistake).
But on that page there is no clear answer on my original question. Does the flashing of patched_boot.img make me lose my apps and data?
I tried and found out, the apps and data are still there.
And, more important, magisk is working again!
Copied my oxygenOS-update.zip to my pc and patched my boot.img using these steps starting from step 2.
GoodSoul said:
You can also patch the boot.img yourself.
Here is how:
.) Download latest Stock OOS
.) Extract boot.img using payload.bin dumper (needs python)
.) Install Magisk Manager on your device
.) Copy boot.img to your device
.) Patch boot.img using Magisk Manager
.) Copy patched boot.img to your pc, reboot your phone to fastmode and use 'fastboot boot patched_boot.img' to boot from patches bootimage.
.) Run Magisk Manager, choose direct install
-> Voila, you have a rooted OP7pro.
Click to expand...
Click to collapse
karazz said:
Made the OTA update yesterday, stupid as I am, I rebooted after updating causing me to lose root.
When downloading stock image, patching boot.img and transferring the patched boot.img back using fastboot, will that make me lose my apps and data? Can't find a clear answer unfortunatly...
Click to expand...
Click to collapse
Simply flashing stock or patched boot img would not impact your apps and data, evenprevious magisk modules.
Th3Scr34m said:
Hi there,
Yesterday I have downloaded the full OTA package with Oxygen Updater,
whats the link u downloaded 10.0.11 HD65BA (EU) ota package from?
Click to expand...
Click to collapse
Hi,
OnePlus7T HD1903
I had working root, survived many OTA's, after each OTA I launched Magisk, flash inactive boot bank, it works perfect.
Last time i did the same, but have bootloop.
I downloaded ZIP with OTA, extracted payload, extracted stock boot.img, flash into phone so it boot
Tha same image I'm trying to patch with Magisk Manager 7.5.1 - but everytme i have bootloop.
Force encryption / dm-verify enabled.
Can I have working, patched IMG for my phone?
Or how to resolve my issue?
I tried it many times. After flashing Magisk from orange fox I tap on reboot and it always shows me this boot/recovery corrupt message and didn't start. Can anyone help me?
Sumit Sikder said:
I tried it many times. After flashing Magisk from orange fox I tap on reboot and it always shows me this boot/recovery corrupt message and didn't start. Can anyone help me?
Click to expand...
Click to collapse
My boot partition was corrupted when I installed Magisk also. I installed from ADB after extracting stock boot.img and patching it with Magisk, then flashed patched.img with ADB,. There were no warnings and flashing had no errors.
I had to flash stock ROM to boot again.
My only guess would be to try flashing newer versions of Magisk. Hope we can get help
I tried the latest v22.1. It worked in Android 11 evolution X ROM but not in realme UI 1! The only reason I installed my Android 10 was because Magisk modules weren't working in Android 11!
oxbowlarry said:
My boot partition was corrupted when I installed Magisk also. I installed from ADB after extracting stock boot.img and patching it with Magisk, then flashed patched.img with ADB,. There were no warnings and flashing had no errors.
I had to flash stock ROM to boot again.
My only guess would be to try flashing newer versions of Magisk. Hope we can get help
Click to expand...
Click to collapse
I have seen another rooting method with ADB and the patched boot image BUT that method first flashes vbmeta.img before flashing the patched boot.img.
Perhaps that is why my boot partition was corrupted because I just flashed the patched boot.img.
Has anyone had success with this rooting method on a Realme 6 pro ?
Hello, this morning I found my poco f3 updated to Miui 12.5.3.0 (I was on 12.5.0.0) even though I had automatic updates disabled. After the automatic update I lost my root via magisk and twrp in recovery. No problem, I got twrp installed again, then I proceeded to install magisk v23.0 from TWRP, as I had done after 12.5.0.0. update.
Afterwars phone is stuck in a bootloop. I reflashed stock boot image, recovering the phone, but I ave been unable to install magisk in 12.5.3.0, I tried copying boot.img to the phone, then using magisk manager to patch the boot image, then flash the patched image trough fastboot, with the same result.
Anyone knows how to make magisk work in this new update?
Thank you
suloku said:
Hello, this morning I found my poco f3 updated to Miui 12.5.3.0 (I was on 12.5.0.0) even though I had automatic updates disabled. After the automatic update I lost my root via magisk and twrp in recovery. No problem, I got twrp installed again, then I proceeded to install magisk v23.0 from TWRP, as I had done after 12.5.0.0. update.
Afterwars phone is stuck in a bootloop. I reflashed stock boot image, recovering the phone, but I ave been unable to install magisk in 12.5.3.0, I tried copying boot.img to the phone, then using magisk manager to patch the boot image, then flash the patched image trough fastboot, with the same result.
Anyone knows how to make magisk work in this new update?
Thank you
Click to expand...
Click to collapse
Try flashing the older patched boot.img on the new stock firmware.
On the 12.5.3.0 ill patched boot.img from 12.5.1.0 and all right.
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
i have the same issue of auto updated and lost my root access.
Which boot.img I should Magish'd to get the root access again?
Currently installing my twrp
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
if Flash Current TWRP fails, go to Backup > Refresh Sizes and try Flash Current TWRP again
Click to expand...
Click to collapse
Currently at the Resizing stage
Edit 1: failed, I have the error bootctrl error that prevent me from installing after resizing.
I have flashed the twrp3.5.2 directly to boot resulting in bootloop and needed to install the Boot.img from the 12.5.1 from the previous bulit
Edit: actually I can ignore that error.
Magisk installed but safety checked failed even I have the "universal safety check module installed "
Also the app thoax isn't working
I'd try removing all magisk modules, installing stock 12.5.3, then using magisk apk to create patched boot.img and flash it with fastboot (fastboot flash boot magisk_boot_patched.img)
Also, maybe try flashing bot boot_a and boot_b? I had a problem were my active boot partition changed and phone became even more broken.
suloku said:
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
Might wanna also uncheck Automatic system updates in the Developer settings to be safe.
suloku said:
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
There is a setting in the Xiaomi system updater that had by default checked auto-update. That setting need to be disabled/unchecked as well.
Since you have root with Magisk, can also Force stop or debloat the updater app, so the system will not update itself.
suloku said:
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
I had the same issue on Redmi Note 9 Pro (joyuse). Based on your tip I've removed some modules from `data/adb/modules` and my device is finally booting normally. Thanks!
HI there, so after patching the Boot.img with Magiskv23, it seems as if flashing it with ABD/Fastboot causes the bootloop. I had to flash to flash the stock boot.img back. Any advices? As I research this seems to be an issue with the fix being "I made some investigation and checked that replacing the file in the Magisk-v21.4.zip/arm/magiskboot with the magiskboot from v21.0 and flashing that one fixes the problem." But I have no idea how it'd work.
My device used to work with Magiskv21 until I updated my device and it has to be rooted again. So I got the stock boot.img file, patched it adb/fastboot flash it into the device (same method as before) and it causes bootloop.
If you experience a bootloop, attach a dmesg (kernel logs) when the device refuse to boot. This may very likely require a custom kernel on some devices as last_kmsg or pstore ramoops are usually not enabled by default.
HOW do I do this?
In addition, please also upload the result of cat /proc/mounts when your device is working correctly WITHOUT ROOT.
I can't go back to unrooting it, as I still want to keep my data on the device. Is there any way I could attach this without unrooting it?
If you experience issues during installation,
boot.zip
in recovery, upload the recovery logs, or in Magisk, upload the install logs. Please also upload the boot.img or recovery.img that you are using for patching.
Will include both stock boot.img, and stable and v23001 patched files.
I'll upload the boot.img file I use and the patched_boot.img file.
I can't upload with github so here https://drive.google.com/drive/folders/1YkekFaXmtOg6d5sMiecf3OnT7oqCEf4S?usp=sharing
Uploading boot.zip…
Device: Xiaomi 10T Pro (apollo) with MIUI Global Stable 12.5.1.0 (RJDMIXM)
Android version: 11 RKQ1.200826.002
Magisk version name: 23001
Magisk v23001 (I chose canary because that's what's needed to submit this report but I tried stable and the issue is the same as well)
Magisk version code: f822ca5(23001)
chinjangs said:
HI there, so after patching the Boot.img with Magiskv23, it seems as if flashing it with ABD/Fastboot causes the bootloop. I had to flash to flash the stock boot.img back. Any advices? As I research this seems to be an issue with the fix being "I made some investigation and checked that replacing the file in the Magisk-v21.4.zip/arm/magiskboot with the magiskboot from v21.0 and flashing that one fixes the problem." But I have no idea how it'd work.
My device used to work with Magiskv21 until I updated my device and it has to be rooted again. So I got the stock boot.img file, patched it adb/fastboot flash it into the device (same method as before) and it causes bootloop.
If you experience a bootloop, attach a dmesg (kernel logs) when the device refuse to boot. This may very likely require a custom kernel on some devices as last_kmsg or pstore ramoops are usually not enabled by default.
HOW do I do this?
In addition, please also upload the result of cat /proc/mounts when your device is working correctly WITHOUT ROOT.
I can't go back to unrooting it, as I still want to keep my data on the device. Is there any way I could attach this without unrooting it?
If you experience issues during installation,
boot.zip
in recovery, upload the recovery logs, or in Magisk, upload the install logs. Please also upload the boot.img or recovery.img that you are using for patching.
Will include both stock boot.img, and stable and v23001 patched files.
I'll upload the boot.img file I use and the patched_boot.img file.
I can't upload with github so here https://drive.google.com/drive/folders/1YkekFaXmtOg6d5sMiecf3OnT7oqCEf4S?usp=sharing
Uploading boot.zip…
Device: Xiaomi 10T Pro (apollo) with MIUI Global Stable 12.5.1.0 (RJDMIXM)
Android version: 11 RKQ1.200826.002
Magisk version name: 23001
Magisk v23001 (I chose canary because that's what's needed to submit this report but I tried stable and the issue is the same as well)
Magisk version code: f822ca5(23001)
Click to expand...
Click to collapse
when you were setting up the patched file you made sure you didnt choose rrecovery method in the magisk app
also rather flash it through twrp there are probably scripts that twrp has to run during the installation
if you dont have twrp you can flash it to recovery if you can access your fastboot/bootloader
reboot to recovery after then flash the patched boot.img to boot in twrp
(i dont know if you should clear cache or data or not just look for the guide )
reboot
flairepathos.info said:
when you were setting up the patched file you made sure you didnt choose rrecovery method in the magisk app
also rather flash it through twrp there are probably scripts that twrp has to run during the installation
if you dont have twrp you can flash it to recovery if you can access your fastboot/bootloader
reboot to recovery after then flash the patched boot.img to boot in twrp
(i dont know if you should clear cache or data or not just look for the guide )
reboot
Click to expand...
Click to collapse
I'm not sure how to use twrp, but I've rooted this device already just have issues with installing magisk patching boot.img after updating from magisk v20=>v23.
After that using boot.img that has been patched by magisk just causes bootloops.
Thanks for you comment though <3
chinjangs said:
I'm not sure how to use twrp, but I've rooted this device already just have issues with installing magisk patching boot.img after updating from magisk v20=>v23.
After that using boot.img that has been patched by magisk just causes bootloops.
Thanks for you comment though <3
Click to expand...
Click to collapse
Yes the stock boot image is locked bootloader so you will boot loop, flash magiskpatched boot image again to stop bootloop , even if its the old patched one
flairepathos.info said:
Yes the stock boot image is locked bootloader so you will boot loop, flash magiskpatched boot image again to stop bootloop , even if its the old patched one
Click to expand...
Click to collapse
Are you suggesting I use the old stock image where it works before I updated the magisk to version 23?
(I did that and it still bootloops)
Thank you for everyone's help. I've solved this by Uninstalling magisk v23001 and reinstalling magisk v23 thru TWRP in this method https://forum.xda-developers.com/t/...tom-rom-working-on-xiaomi-mi-10t-pro.4246339/
I have OnePlus7T Indian version. I was on 11.0.9.1 and rooted with Magisk Canary version. There was an Update to Magisk which I accidentally installed with OTA option instead of full. Now my phone is not booting. It goes into original recovery mode or fastboot only. How can I recover from this? I tried to flash the magisk patched image file and it shows as flashed but when I reboot I again reach original recovery / fastboot menu only. Please help!!
Problem solved but don't know how. I was trying many things and when I used Tool All in One to flash TWRP the phone rebooted into the system. Not even sure if TWRP is installed or not but everything is working now and phone is rooted. Not sure how it got resolved. Magisk is updated to latest version.
jesrani said:
Problem solved but don't know how. I was trying many things and when I used Tool All in One to flash TWRP the phone rebooted into the system. Not even sure if TWRP is installed or not but everything is working now and phone is rooted. Not sure how it got resolved. Magisk is updated to latest version.
Click to expand...
Click to collapse
Most likely changed slot accidentally when it crashed and then corrected on multiple interventions
HueyT said:
Most likely changed slot accidentally when it crashed and then corrected on multiple interventions
Click to expand...
Click to collapse
Hi. I am again having same problem. I updated Magisk Manager and Magisk and some other apps and phone was not booting. After many tries it again booted but all the modules in Magisk were off. So I switched them on and rebooted the phone and now it is just not booting. I tried to use Tool All In One to flash a TWRP but now there is no recovery. The phone is either not booting (stuck on Circle dot rotating) or just going into fastboot, does not go into recovery. I was on OOS11. I tried flashing original recovery through the tool but it fails. Any way out of this mess??
jesrani said:
Hi. I am again having same problem. I updated Magisk Manager and Magisk and some other apps and phone was not booting. After many tries it again booted but all the modules in Magisk were off. So I switched them on and rebooted the phone and now it is just not booting. I tried to use Tool All In One to flash a TWRP but now there is no recovery. The phone is either not booting (stuck on Circle dot rotating) or just going into fastboot, does not go into recovery. I was on OOS11. I tried flashing original recovery through the tool but it fails. Any way out of this mess??
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
This will wipe your data. Otherwise, you can try manually fastboot flash each individual files of oos11 rom:
⭐[ROM][STOCK] 11.0.9.1-GLOBAL-OnePlus7TOxygen_14.O.35_GLO_0350_2206171459-FASTBOOT
Created my own FASTBOOT Rom can anybody test this out, to see if it works please? Used to "Restore the Firmware" on your phone or when bricked you cannot downgrade or upgrade with FASTBOOT Roms, you must be on the same (Firmware Update Global...
forum.xda-developers.com
HueyT said:
This will wipe your data. Otherwise, you can try manually fastboot flash each individual files of oos11 rom:
Click to expand...
Click to collapse
Thanks. I managed to boot the phone but having root problems. After spending a number of hours doing various trials and checking Xda threads I managed to get it to boot again but root was lost.
I again read more articles and learnt that I have to flash recovery to both partitions so I used Tool All in one, changed active slots and flashed the magisk patched image from this thread i think on both slots. But i am not sure. I managed to get root but the Magisk manager was not getting installed.
I tried few other things and finally i am now not able to root again. Phone is booting after I flash a recovery but I am not sure if it will boot if restarted or go into loop.
Can anyone explain the proper procedure and sequence to follow for rooting and which files to use.
I am on OOS11.09.1
jesrani said:
Thanks. I managed to boot the phone but having root problems. After spending a number of hours doing various trials and checking Xda threads I managed to get it to boot again but root was lost.
I again read more articles and learnt that I have to flash recovery to both partitions so I used Tool All in one, changed active slots and flashed the magisk patched image from this thread i think on both slots. But i am not sure. I managed to get root but the Magisk manager was not getting installed.
I tried few other things and finally i am now not able to root again. Phone is booting after I flash a recovery but I am not sure if it will boot if restarted or go into loop.
Can anyone explain the proper procedure and sequence to follow for rooting and which files to use.
I am on OOS11.09.1
Click to expand...
Click to collapse
[OP7T][Stock/Magisk v23.0] OxygenOS 11.0.9.1.HD65AA boot.img
OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img Stock: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g Magisk v23.0 Patched: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc Note: DISABLE...
forum.xda-developers.com
HueyT said:
[OP7T][Stock/Magisk v23.0] OxygenOS 11.0.9.1.HD65AA boot.img
OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img Stock: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g Magisk v23.0 Patched: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc Note: DISABLE...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi. I already used these boot images but I was still having a problem. I had flashed the stock image to both partitions and then the Magisk patched image also but either I was not rooted or Magisk App not working. Finally got things to work by installing TWRP to partition a I believe. I changed active partition to a and then flashed the twrp recovery. Again changed active to b and booted and had root. I had to install Magisk Canary 25210 version only as other versions did not install. After checking on net it seems this version is faulty. So I installed Magisk Delta, then installed Magisk using Direct Install option, rebooted, checked regular Magisk Manager and showed the same Magisk version. Removed all modules from old Magisk Manager and unstalled the app. Setup Magisk Delta modules, hide, SuList as well as apps like LSPosed, HMA etc and now everything is working again.
I still am not very sure where the recovery is installed, on partition a or b? And if a difference recovery is installed on each partition what happens? I am pretty sure I had not installed TWRP on partition b. I am also assuming that once I set a partition as active and flash a recovery in fastboot that recovery is flashed to that partition, is this correct? Things are working but I don't know if the phone will go to recovery mode from system, I have not tried that. So I am not very clear yet but still got things to work.
jesrani said:
Hi. I already used these boot images but I was still having a problem. I had flashed the stock image to both partitions and then the Magisk patched image also but either I was not rooted or Magisk App not working. Finally got things to work by installing TWRP to partition a I believe. I changed active partition to a and then flashed the twrp recovery. Again changed active to b and booted and had root. I had to install Magisk Canary 25210 version only as other versions did not install. After checking on net it seems this version is faulty. So I installed Magisk Delta, then installed Magisk using Direct Install option, rebooted, checked regular Magisk Manager and showed the same Magisk version. Removed all modules from old Magisk Manager and unstalled the app. Setup Magisk Delta modules, hide, SuList as well as apps like LSPosed, HMA etc and now everything is working again.
I still am not very sure where the recovery is installed, on partition a or b? And if a difference recovery is installed on each partition what happens? I am pretty sure I had not installed TWRP on partition b. I am also assuming that once I set a partition as active and flash a recovery in fastboot that recovery is flashed to that partition, is this correct? Things are working but I don't know if the phone will go to recovery mode from system, I have not tried that. So I am not very clear yet but still got things to work
Click to expand...
Click to collapse
Only data partition is shared. All else have both A and B parts