Database Develop

Relock bootloader (with magisk) on the Oneplus 5?

Hello everyone, I've tried to search on the web about this issue since the OTA for Android O is finally out for the Oneplus 5 and couldn't get a satisfying solution. I rooted my OP5 a while ago with Magisk and now that this update is out and tried to install it, It just wouldn´t let me, searching I found that my locked swich to relock the bootloader was because I had to enable it on Magisk, so I opened magisk and couldn´t find that option, and now that I searched on how to enable the "Lock bootloader option" in the Magisk app and found nothing, I'm just out of ideas, so guys, could you help a (noob) brother out with this?
Ps.: If you could attach some screenshots about where to click or what to do, I'll apreciate it a lot (yeah, I'm that stupid when I freak out and don't find how to undo mi mess)

No... Do not lock your bootloader! Since you've been modifying your device that would potentially brick it.
What you're probably looking for is to restore your boot image. That's what Magisk modifies and is the reason why a normal OTA doesn't work. If you have TWRP installed, that would also be an issue.
The easiest way for you to update would be to download the full OTA zip, flash that in TWRP directly followed by the Magisk zip. That way you'll be nice and updated and still rooted.

Didgeridoohan said:
No... Do not lock your bootloader! Since you've been modifying your device that would potentially brick it.
What you're probably looking for is to restore your boot image. That's what Magisk modifies and is the reason why a normal OTA doesn't work. If you have TWRP installed, that would also be an issue.
The easiest way for you to update would be to download the update, flash that in TWRP directly followed by the Magisk zip. That way you'll be nice and updated and still rooted.
Click to expand...
Click to collapse
Allright! I've downloaded the zip with the update, now: do I have to get the latest magisk zip, flash the update and then immediately flash the newest magisk zip?

Fosko Stock said:
Allright! I've downloaded the zip with the update, now: do I have to get the latest magisk zip, flash the update and then immediately flash the newest magisk zip?
Click to expand...
Click to collapse
Yes.

Startup Hang after Installing Magisk v18.0

Hey, all!
Had a notification this morning for the new Magisk Manager (6.1) and Magisk (18.0) release. I downloaded both and rebooted the phone (OnePlus 2), updating from 17.3 to 18.0 directly, which had no errors during the install. Now upon startup it hangs on the splash screen. I can get into recovery (TWRP) and I have tried to flash the latest Magisk Uninstaller but I'm greeted with an ERROR 1: Error Installing zip file '/sdcard/...' - Unable to unpack boot.img
Any help here? Thanks in advance!

SpikyAndroid3 said:
Hey, all!
Had a notification this morning for the new Magisk Manager (6.1) and Magisk (18.0) release. I downloaded both and rebooted the phone (OnePlus 2), updating from 17.3 to 18.0 directly, which had no errors during the install. Now upon startup it hangs on the splash screen. I can get into recovery (TWRP) and I have tried to flash the latest Magisk Uninstaller but I'm greeted with an ERROR 1: Error Installing zip file '/sdcard/...' - Unable to unpack boot.img
Any help here? Thanks in advance!
Click to expand...
Click to collapse
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk

DarkSJ1998 said:
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
Thanks for the response, just about to do a dirty flash of the stock ROM. My memory doesn't serve me well, is it best to wipe Cache as well as Dalvik Cache, or just Dalvik Cache?
The recovery also stays as is, right?

Hello,
The same for me from 17.3 to 18.
I'm on Nexus 6 with stock ROM.

SpikyAndroid3 said:
Thanks for the response, just about to do a dirty flash of the stock ROM. My memory doesn't serve me well, is it best to wipe Cache as well as Dalvik Cache, or just Dalvik Cache?
The recovery also stays as is, right?
Click to expand...
Click to collapse
Yep the recovery should stay as it is. I would recommend wiping both Dalvik Cache & Cache. Also, do keep fastboot handy. TWRP survival really depends on the device. For my device (OnePlus 3T), the OOS overrides TWRP if no root solution is used or patched boot.img isn't used.
Sent from my #FlagshipKiller3T using Tapatalk
---------- Post added at 01:08 AM ---------- Previous post was at 12:55 AM ----------
StreamingMT said:
Hello,
The same for me from 17.3 to 18.
I'm on Nexus 6 with stock ROM.
Click to expand...
Click to collapse
Weird :/
Did you check the Magisk release thread for people facing similar issues? I'm still on v17.3.
I'm really reluctant to move to v18.0 after reading such things... Moreover, I always wait for feedbacks before trying out things that play with the boot.img's & stuff, because I already got /data partition of my last device corrupted [emoji52]
Sent from my #FlagshipKiller3T using Tapatalk

DarkSJ1998 said:
Yep the recovery should stay as it is. I would recommend wiping both Dalvik Cache & Cache. Also, do keep fastboot handy. TWRP survival really depends on the device. For my device (OnePlus 3T), the OOS overrides TWRP if no root solution is used or patched boot.img isn't used.
Click to expand...
Click to collapse
Alrighty! Just went ahead and did the flash and it successfully reboots! Tried to reboot into recovery to flash Magisk 17.3 and lo and behold TWRP is still there
Guess I'll wait until there has been an update or patch of some sorts if @StreamingMT is also getting this issue, maybe there are others too. Thanks for the help @DarkSJ1998

I will try to remember that @DarkSJ1998.
I was excited to have a new update, just got reckless...
Anyways, I replied to the official thread about the details, just search through it. I just restored my phone to the way it used to...
All my saves... Gone to trash.

SpikyAndroid3 said:
Hey, all!
Had a notification this morning for the new Magisk Manager (6.1) and Magisk (18.0) release. I downloaded both and rebooted the phone (OnePlus 2), updating from 17.3 to 18.0 directly, which had no errors during the install. Now upon startup it hangs on the splash screen. I can get into recovery (TWRP) and I have tried to flash the latest Magisk Uninstaller but I'm greeted with an ERROR 1: Error Installing zip file '/sdcard/...' - Unable to unpack boot.img
Any help here? Thanks in advance!
Click to expand...
Click to collapse
I had the same bootloop issue when I was reinstalling H2OS beta 21 in my OnePlus 5 today. I got it to boot again with Magisk 18.0 after:
1. Dirty flashing ROM. Now this is important Did not flash Magisk (yet).
2. Rebooting to Bootloader (fastboot) in TWRP (since no root, now stock recovery will reinstall).
3. Fastboot flashed TWRP. Booted to Recovery mode from Fastboot menu.
4. Flashed Magisk 18.0 in TWRP. Now this is important Only flashed Magisk, nothing else.
5. Rebooted to Recovery again instead of System to flash other stuff.
6. Rebooted system.
If course YMMV. The important thing was to not try to flash Magisk while flashing ROM.

Same here on a mi max 2, updated manager and magisk directly from app, now stuck in bootloop. im downloading my rom as im typing to restore stock boot image. will flash v17.1 instead.

I have 1 plus 5 with official H2OS and Magisk 17.1.
Today when after installed Magick 18 and reboot, it stuck at startup.
I try to flash TWRP using adb, but it give me error:
E:\Program Files\Android\platform-tools>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
E:\Program Files\Android\platform-tools>adb kill-server
E:\Program Files\Android\platform-tools>
Click to expand...
Click to collapse

I too am having with latest magisk 18.0 my device is redimi 4x, on trying to update via magisk manager crashes with an error report, installed update using twrp now i get a error popup at start and magisk manger still shows am on 17.1 and tells to update, which crashes the app on trying

tmicrd68 said:
I had the same bootloop issue when I was reinstalling H2OS beta 21 in my OnePlus 5 today. I got it to boot again with Magisk 18.0 after:
1. Dirty flashing ROM. Now this is important Did not flash Magisk (yet).
2. Rebooting to Bootloader (fastboot) in TWRP (since no root, now stock recovery will reinstall).
3. Fastboot flashed TWRP. Booted to Recovery mode from Fastboot menu.
4. Flashed Magisk 18.0 in TWRP. Now this is important Only flashed Magisk, nothing else.
5. Rebooted to Recovery again instead of System to flash other stuff.
6. Rebooted system.
If course YMMV. The important thing was to not try to flash Magisk while flashing ROM.
Click to expand...
Click to collapse
Using Xiaomi Mi Max
Using your method and it work just took afew for it to boot back up :good:

netsonic said:
I have 1 plus 5 with official H2OS and Magisk 17.1.
Today when after installed Magick 18 and reboot, it stuck at startup.
I try to flash TWRP using adb, but it give me error:
Code:
E:\Program Files\Android\platform-tools>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
E:\Program Files\Android\platform-tools>adb kill-server
Click to expand...
Click to collapse
Try 'Revoking USB Debugging' and restart the adb server. Then reinstate its authorization by plugging it back in with USB Debugging enabled. And just to check, make sure you run cmd as administrator, and ensure MTP is on.
huzeifa88 said:
I too am having with latest magisk 18.0 my device is redimi 4x, on trying to update via magisk manager crashes with an error report, installed update using twrp now i get a error popup at start and magisk manger still shows am on 17.1 and tells to update, which crashes the app on trying
Click to expand...
Click to collapse
Try flashing the uninstaller which you can get here. Then reinstall/reflash Magisk with a previous version that worked for you.

DarkSJ1998 said:
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?

otraver said:
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?
Click to expand...
Click to collapse
I guess it's possible, but I'm not sure about that.... You can backup/restore boot.img from TWRP but I don't know if you can do this also... Do check it on the Internet.
Sent from my #FlagshipKiller3T using Tapatalk

DarkSJ1998 said:
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
DarkSJ1998 said:
I guess it's possible, but I'm not sure about that.... You can backup/restore boot.img from TWRP but I don't know if you can do this also... Do check it on the Internet.
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
Don't work.
The cellular boot but stops in the Miui Screen with the unlocked symbol
I tried a dirty install of the rom but don't work
I need to install a clean global stock rom to boot correctly.

otraver said:
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?
Click to expand...
Click to collapse
Actually, Magisk does a backup of stock boot.img before patching it, which lies stored in /data as ".img.gz.zip". Haven't looked for how to restore it yet; however, assuming it's a flashable zip, it can be restored via TWRP. Should check Magisk release OP to be sure...
Sent from my Moto Z2 Play using XDA Labs

The Analog Kid said:
Actually, Magisk does a backup of stock boot.img before patching it, which lies stored in /data as ".img.gz.zip". Haven't looked for how to restore it yet; however, assuming it's a flashable zip, it can be restored via TWRP. Should check Magisk release OP to be sure...
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
Doesn't look like a flashable zip too me. It stores a *.img file in it, which I think is flashable as an image from TWRP. But, I'm not 100% sure about it.
Great discovery though dude there
Sent from my #FlagshipKiller3T using Tapatalk

otraver said:
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?
Click to expand...
Click to collapse
Hello, I do this with my Nexus 6, it's OK. Flash again Magisk (v17 not 18 for me) and all is OK for me.

Boot loop for me too after upgrading from v17 to v18 . I'm on Nexus 6. Any official information about this bug?
Fixed by installing TWRP then restored backup through TWRP and selected only boot image. I guess TWRP or me saved backup at some point, don't remember exactly. Will have to use v17 for now.

TWRP install and magisk root xz3

So over the last day or 2 I've tried flashing the twrp recovery image. It flashes fine and reboots and loads the twrp recovery. However nothing works after that like it hangs and the touch screen is inop. How do I get past this? I have flashed the latest twrp for 52.0.A. 8.131 and phone is on the stock firmware also.
Just trying to get to the stage of installing the magisk root software. I've heard also people having issues with certain versions of magisk on Sony phones to? Is this fixed in the latest version?
Is there anything else I should be doing? Is the xz3 able to be rooted on the latest software released by Sony as of August update

Jharrisonkerr said:
So over the last day or 2 I've tried flashing the twrp recovery image. It flashes fine and reboots and loads the twrp recovery. However nothing works after that like it hangs and the touch screen is inop. How do I get past this? I have flashed the latest twrp for 52.0.A. 8.131 and phone is on the stock firmware also.
Just trying to get to the stage of installing the magisk root software. I've heard also people having issues with certain versions of magisk on Sony phones to? Is this fixed in the latest version?
Is there anything else I should be doing? Is the xz3 able to be rooted on the latest software released by Sony as of August update
Click to expand...
Click to collapse
I didn't got bug reports to fix something in this direction.
Touch doesn't work in the android system?
And it hangs?
Or what hangs where?
Yes, you either need to use magisk 18.1 or the newest canary should work too.

MartinX3 said:
I didn't got bug reports to fix something in this direction.
Touch doesn't work in the android system?
And it hangs?
Or what hangs where?
Yes, you either need to use magisk 18.1 or the newest canary should work too.
Click to expand...
Click to collapse
Hi Martin, touch doesn't work when in the main twrp screen after using fastboot to move the twrp. img file over to the device so I can install the magisk program to allow root access.

Jharrisonkerr said:
Hi Martin, touch doesn't work when in the main twrp screen after using fastboot to move the twrp. img file over to the device so I can install the magisk program to allow root access.
Click to expand...
Click to collapse
Hi Jharrison,
You did say it hangs
At twrp boot logo?

MartinX3 said:
Hi Jharrison,
You did say it hangs
At twrp boot logo?
Click to expand...
Click to collapse
Well it's like it hangs as it loads the Sony logo and then boots into twrp but nothing happens when touching the touch screen or using the side volume buttons apart from showing the twrp boot logo.
What's the full process of flashing twrp to the device? Maybe I'm doing something wrong? I did see some people have had to connect a mouse to there phone to operate twrp?
Sorry for the confusion. I'm not sure if it's the way I'm doing it or if there is a issue with twrp on the xz3 on the latest Sony firmware. I've done a few roots before as I have a tablet install in my car as well as rooting a previous xperia phone but the latest android 9 seems harder to crack.

Jharrisonkerr said:
Well it's like it hangs as it loads the Sony logo and then boots into twrp but nothing happens when touching the touch screen or using the side volume buttons apart from showing the twrp boot logo.
What's the full process of flashing twrp to the device? Maybe I'm doing something wrong? I did see some people have had to connect a mouse to there phone to operate twrp?
Sorry for the confusion. I'm not sure if it's the way I'm doing it or if there is a issue with twrp on the xz3 on the latest Sony firmware. I've done a few roots before as I have a tablet install in my car as well as rooting a previous xperia phone but the latest android 9 seems harder to crack.
Click to expand...
Click to collapse
So you see just the twrp logo, no buttons?
That indicates a failing decryption
Did you downloaded the reuploaded twrp?
And twrp and firmware having the same version?

MartinX3 said:
So you see just the twrp logo, no buttons?
That indicates a failing decryption
Did you downloaded the reuploaded twrp?
And twrp and firmware having the same version?
Click to expand...
Click to collapse
Yeah that's it, just the main twrp boot screen/logo no buttons to install the magisk.
I haven't as of yet. When was this uploaded? Recent? Yeah the version for twrp was for the same firmware version not custom rom just stock version
Is there any specific way to flash it in fastboot?

Jharrisonkerr said:
Yeah that's it, just the main twrp boot screen/logo no buttons to install the magisk.
I haven't as of yet. When was this uploaded? Recent? Yeah the version for twrp was for the same firmware version not custom rom just stock version
Is there any specific way to flash it in fastboot?
Click to expand...
Click to collapse
I did reupload the twrp with new omnirom code changes to fix this problem in the past
Please redownload the twrp
I hope it is fixed now
If not, I would like to see a dmesg and a /tmp/recovery.log

MartinX3 said:
I did reupload the twrp with new omnirom code changes to fix this problem in the past
Please redownload the twrp
I hope it is fixed now
If not, I would like to see a dmesg and a /tmp/recovery.log
Click to expand...
Click to collapse
OK, I will try this later.
Just to confirm what is the correct way to flash the twrp. Img file using fastboot? Fastboot flash recovery twrp.img?

Jharrisonkerr said:
OK, I will try this later.
Just to confirm what is the correct way to flash the twrp. Img file using fastboot? Fastboot flash recovery twrp.img?
Click to expand...
Click to collapse
The correct way is in the first post of the first page in the main twrp thread.

Managed to get it working, however once all installed it asks to update the magisk app to 19.3 which I have done however it is now stuck in a bootloop where it loads Sony and powered by android and then reboots every time.
What's the fix for this?

So far I've fixed it by reinstalling the previous version through twrp. Is there issues with magisk 19.3?
Alos now in the magisk manager I have the manager showing up to date(7.3.2) but magisk is showing not installed only able to install magisk 19.3?

Please either use magisk 18.1 or the newest canary
Or switch to a custom ROM. [emoji14]

MartinX3 said:
Please either use magisk 18.1 or the newest canary
Or switch to a custom ROM. [emoji14]
Click to expand...
Click to collapse
For some reason I can't seem to get magisk 18.1 back on now after the update. I'm guessing I'll have to do a clean install again. The magisk manager is fine but magisk doesn't shown as installed. Is there a fix for this or will a clean stock flash work? Or is there a way to flash a new boot.img?
Is this also a known issue when updating magisk?

Jharrisonkerr said:
For some reason I can't seem to get magisk 18.1 back on now after the update. I'm guessing I'll have to do a clean install again. The magisk manager is fine but magisk doesn't shown as installed. Is there a fix for this or will a clean stock flash work? Or is there a way to flash a new boot.img?
Is this also a known issue when updating magisk?
Click to expand...
Click to collapse
You can flash the magisk uninstaller first
Or the firmware
Or the boot.sin from the firmware folder
It's a known issue for the xperias from sony
The developer said that a working magisk before was an accident and since he used an official way it wasn't working anymore correctly
And then it seems in 19.4/canary fixed er the xperia specific issue.

MartinX3 said:
You can flash the magisk uninstaller first
Or the firmware
Or the boot.sin from the firmware folder
It's a known issue for the xperias from sony
The developer said that a working magisk before was an accident and since he used an official way it wasn't working anymore correctly
And then it seems in 19.4/canary fixed er the xperia specific issue.
Click to expand...
Click to collapse
Tried the magisk uninstaller but every time I do it comes up with error 1 and then never installs.
The flash boot.sin sounds a easy fix, I will try that and see. If not looks like a full firmware reinstall is on the cards. I'll stick with 18.1 when I do as that seemed to work until I updated. I'll wait till a stable release of 19.4 is released.
Many thanks for your help so far Martin.

MartinX3 said:
You can flash the magisk uninstaller first
Or the firmware
Or the boot.sin from the firmware folder
It's a known issue for the xperias from sony
The developer said that a working magisk before was an accident and since he used an official way it wasn't working anymore correctly
And then it seems in 19.4/canary fixed er the xperia specific issue.
Click to expand...
Click to collapse
Managed to reflash the beta 19.3 zip for magisk then restart, flashed the uninstaller which worked and then reinstalled magisk which is now working again.
Is it safe to update the manager app from 7.0.0 to 7.3. 2 and leave the magisk version at 18.1?

Jharrisonkerr said:
Managed to reflash the beta 19.3 zip for magisk then restart, flashed the uninstaller which worked and then reinstalled magisk which is now working again.
Is it safe to update the manager app from 7.0.0 to 7.3. 2 and leave the magisk version at 18.1?
Click to expand...
Click to collapse
The app is fine

MartinX3 said:
The app is fine
Click to expand...
Click to collapse
Awesome I'll update the app to latest then and leave magisk at 18.1 as root is working fine so far.
Many thanks for your help with all this Martin. :good:

MartinX3 said:
The correct way is in the first post of the first page in the main twrp thread.
Click to expand...
Click to collapse
Can you share the link please? I visited your profile but did not found the that thread how to flash my sony xz3 using TWRP.

[ROM] [10.0] OnePlus 6/6T Open Beta 2 for Android 10 OxygenOS Links

6- https://otafsg1.h2os.com/patch/amaz...22_OTA_061_all_1911200429_a3efe64891d2c42.zip
6T- https://otafsg1.h2os.com/patch/amaz..._41_OTA_061_all_1911200419_f2e12518eef8ae.zip
Found this today. File has a date of 11/20/19. I put in root and do manual update thru settings/update.
Magisk patched boot.img for the above 6T ROM.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF

I had a boatload of bugs with the OB1. I have a 6T converted. Couldnt answer or make calls, reboots, freezes, crashes, WIFI didnt work, no pic messages, etc. I just tested for a second and I could make calls and wifi works. Do not try to install the Magisk patched boot.img. It will give the problems I had with OB1. I tried.

Def works a lot better. No freezes or reboots. My phone was useless on OB1 and I didn't want to flash back to 9 and lose my data. I had to forward my calls to another phone and wait for an updated ROM. But this def fixed a lot of the problems I encountered.
Edit: Still cant flashboot boot twrp.img.(3.3.1-1) Same error as before (failed remote unknown command)

Here's a bonus: Magisk patched boot.img for this OB2. Tested and verified root and no problems. Patched myself. For 6T. Extracted the boot.img from the payload.bin and patched.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF

shatty said:
Here's a bonus: Magisk patched boot.img for this OB2. Tested and verified root and no problems. Patched myself. For 6T. Extracted the boot.img from the payload.bin and patched.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
Click to expand...
Click to collapse
@shatty, thanks.
What did you do to upgrade ? Actually i'm in OB1 Android 10 and Root with patched boot. So you upgrade with OTA or local upgrade ? You loose Root, and you put the new patched in adb? IS it ok?
Thanks

g4seb said:
@shatty, thanks.
What did you do to upgrade ? Actually i'm in OB1 Android 10 and Root with patched boot. So you upgrade with OTA or local upgrade ? You loose Root, and you put the new patched in adb? IS it ok?
Thanks
Click to expand...
Click to collapse
If you're rooted use the same method as always, use local update ( you don't have access to incremental update anyway as you are rooted) and BEFORE rebooting go in Magisk manager and install Magisk again but on other slot. You don't need to play with adb or fastboot.

@Striatum_bdr :
Thanks, so download the update, do local update and after juste install magisk on the other slot.

shatty said:
Here's a bonus: Magisk patched boot.img for this OB2. Tested and verified root and no problems. Patched myself. For 6T. Extracted the boot.img from the payload.bin and patched.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
Click to expand...
Click to collapse
wiped my device and flashed A10 beta 2, but every time flash this patched img file from fastboot my not booting. is there any other way to flash this patched img ?

ariyan rana said:
wiped my device and flashed A10 beta 2, but every time flash this patched img file from fastboot my not booting. is there any other way to flash this patched img ?
Click to expand...
Click to collapse
It worked on my 6t converted from tmo. Anyone else try this patched boot.img? Why wipe? Upgrade works fine.

So after hours of using the ob2 I didn't have any freezes or reboots. 1000000x better than my experience on ob1

shatty said:
So after hours of using the ob2 I didn't have any freezes or reboots. 1000000x better than my experience on ob1
Click to expand...
Click to collapse
Same here bud. Thanks.

shatty said:
Def works a lot better. No freezes or reboots. My phone was useless on OB1 and I didn't want to flash back to 9 and lose my data. I had to forward my calls to another phone and wait for an updated ROM. But this def fixed a lot of the problems I encountered.
Edit: Still cant flashboot boot twrp.img.(3.3.1-1) Same error as before (failed remote unknown command)
Click to expand...
Click to collapse
For now the right command is fastboot flash boot twrp mauronofrio.img version and then flash the installer zip through recovery.
It's a Oneplus's problem.
[EDIT 1]
After a few tries it worked! Now I try to install twrp (mauronofio version) and root the phone.
P.s. I'm trying to update (come form OB-1) I removed all magisk's modules, flashed magiks unistaller but the update with update manager keep failing...any idea?
[EDIT2]
ok, now I'm rooted and I've twrp but wifi doesn't work it's turn off automatically!
[EDIT3]
I've fix it! I've talked with mauronofrio and he said that it's due to flashing the twrp in the boot partition, so he suggested me two ways:
1. Root your device and flash the twrp installer using magisk manager
2. After the command fastboot flash boot twrp.img reboot in recovery, flash the stock boot.img flash twrp installer.zip and finally flash magisk.
I choosen the second way and it worked! Now I've OB_2, twrp, magisk and wifi connection.

Thx a lot for the links and Infos.
I have flashed it and it feels definitely smoother and I hope the random reboots are fixed.
From the changelog they should be.
Here is a small how to, how the upgrade from 10 to 10 ob2 went smooth. Also using this on every update.
1. Just use normal systen ota & let it install or Flash full OOS 10 zip via local update . (DO NOT REBOOT)
2a. Flash newest TWRP: fajita twrp 3.3.1-28.zip (or newer) by @mauronofrio via Magisk Manager (DO NOT REBOOT)
or 2b. go into magisk manager, search for a module called "twrp a/b retention script" Install it (DO NOT REBOOT)
3. Flash magisk to 2nd slot via MAgisk Manager (Magisk Manager → Tap on Install → Then select Install to Inactive Slot)
4. Reboot, wait and enjoy
pOpY
Gesendet von meinem ONEPLUS A6013 mit Tapatalk

Be very careful with the patched boot image. It hard-bricked my OP6T! Full details here:
https://forum.xda-developers.com/oneplus-6t/help/spent-6-hours-trying-to-rooted-android-t4012909

It looks like they took FactoryMode away using *#808# when using the dialer... anyone noticed?

Did they fix the extra blank space under navigation keyboard when type? Thanks

nicche said:
For now the right command is fastboot flash boot twrp mauronofrio.img version and then flash the installer zip through recovery.
It's a Oneplus's problem.
[EDIT 1]
After a few tries it worked! Now I try to install twrp (mauronofio version) and root the phone.
P.s. I'm trying to update (come form OB-1) I removed all magisk's modules, flashed magiks unistaller but the update with update manager keep failing...any idea?
[EDIT2]
ok, now I'm rooted and I've twrp but wifi doesn't work it's turn off automatically!
Click to expand...
Click to collapse
same thing happened to me. Have you found the fix sir?
OK just reflash the rom and dont forget to flash twrp and magisk again
anddd boom i got wifi working again

Anyone else having issues like the systems is getting slower animation is choppy and it just lag. I noticed it as well when playing games when that happens and it feels like i dont get as much framerates but a reboot of system fixed it for me. I thought by updating to ob2 it would fix this choppy feeling but its still there

I upgraded from OOS 10 Stable to OOS Beta 2 and all went on okay. No data lost.

Rickydwi said:
Anyone else having issues like the systems is getting slower animation is choppy and it just lag. I noticed it as well when playing games when that happens and it feels like i dont get as much framerates but a reboot of system fixed it for me. I thought by updating to ob2 it would fix this choppy feeling but its still there
Click to expand...
Click to collapse
I don't have this issue, but I do have the Bluetooth not working bug

Question Bootloop with patched boot.img

Hi, i have a 11T (not the Pro version) and i unlocked it yesterday.
I want root it (like i did with my previous 9T), but it goes into bootloop.
My stock miui version is: 12.5.8.0(RKWEUXM). This are the operation i did:
- installed magisk 23 APK from the git page
- copied the boot image from the image of the same version (i also tried to extract the image from the payload)
- patched with magisk
- flashed in fastboot using fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img
- reboot the phone.
If i flash again the original boot.img, of course bootloop disappear!
I also tried to boot in recovery mode for clean the magisk modules without success (but is a fresh install, i don't think that the restore from xiaomi cloud can copy also the magisk modules).
I don't understand why i'm the only one in the web that have this problem. Someone have idea of what i can try to do?
For now, i want try to keep the original recovery for install the OTA update, but if all doesn't work i'll try the twrp installation (i think with this recovery all problem will go away).
Thank you very much
Marco

Marcolo88 said:
Hi, i have a 11T (not the Pro version) and i unlocked it yesterday.
I want root it (like i did with my previous 9T), but it goes into bootloop.
My stock miui version is: 12.5.8.0(RKWEUXM). This are the operation i did:
- installed magisk 23 APK from the git page
- copied the boot image from the image of the same version (i also tried to extract the image from the payload)
- patched with magisk
- flashed in recovery (stock recovery) using fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img
- reboot the phone.
If i flash again the original boot.img, of course bootloop disappear!
I also tried to boot in recovery mode for clean the magisk modules without success (but is a fresh install, i don't think that the restore from xiaomi cloud can copy also the magisk modules).
I don't understand why i'm the only one in the web that have this problem. Someone have idea of what i can try to do?
For now, i want try to keep the original recovery for install the OTA update, but if all doesn't work i'll try the twrp installation (i think with this recovery all problem will go away).
Thank you very much
Marco
Click to expand...
Click to collapse
In My pro version. I renamed the patched boot.img to just boot.img before i flashed it.

Belpek said:
In My pro version. I renamed the patched boot.img to just boot.img before i flashed it.
Click to expand...
Click to collapse
And flash it in fastboot not recovery.

Belpek said:
And flash it in fastboot not recovery.
Click to expand...
Click to collapse
I flashed too in recovery, i wrote wrong (now i edit my message).
I'll try your suggestion to rename the img, but in the previous Xiaomi i never did it and it worked .
Thank you very much

Belpek said:
And flash it in fastboot not recovery.
Click to expand...
Click to collapse
I tried just now and it doesn't work also with the file renamed

Do you unlock bootloader?

zelenko said:
Do you unlock bootloader?
Click to expand...
Click to collapse
Yes i unlocked, and if I watch the status, it says unlocked!.
What I can also do?

Marcolo88 said:
Yes i unlocked, and if I watch the status, it says unlocked!.
What I can also do?
Click to expand...
Click to collapse
Flash in fastboot...

leobak said:
Flash in fastboot...
Click to expand...
Click to collapse
This i did but it goes into boot loop

you need to use the correct boot.img this issue occurs when the boot.img is not correct according to the version of the ROM.
from where are you downloading the patched image?

nousernamesorry said:
you need to use the correct boot.img this issue occurs when the boot.img is not correct according to the version of the ROM.
from where are you downloading the patched image?
Click to expand...
Click to collapse
With magisk canary it works!
I downloaded the image from here: https://xiaomifirmwareupdater.com/miui/agate/stable/V12.5.8.0.RKWEUXM/
is the correct image.
I don't like the new implementations in canary version, but for now it worked only with this version.

I know you got it working already but I flashed mine with XiaomiADBFastbootTools.jar and never done that whole "fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img" thingy in ADB. It works no problem every time I do it after an update. I know you can install directly from Magisk after applying an OTA but I prefer this metod. Zygisk will be needet to get root on A12 though and it doesn't have Magisk hide which means I'll never get those banking apps to work anymore thill someone figures out a better method I'll wait with the A12 update. Just my two cents.

MocnePifko said:
I know you got it working already but I flashed mine with XiaomiADBFastbootTools.jar and never done that whole "fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img" thingy in ADB. It works no problem every time I do it after an update. I know you can install directly from Magisk after applying an OTA but I prefer this metod. Zygisk will be needet to get root on A12 though and it doesn't have Magisk hide which means I'll never get those banking apps to work anymore thill someone figures out a better method I'll wait with the A12 update. Just my two cents.
Click to expand...
Click to collapse
For me, with zygisk, i can make work all application with root checker (like banking apps).

Marcolo88 said:
With magisk canary it works!
I downloaded the image from here: https://xiaomifirmwareupdater.com/miui/agate/stable/V12.5.8.0.RKWEUXM/
is the correct image.
I don't like the new implementations in canary version, but for now it worked only with this version.
Click to expand...
Click to collapse
Hi man, I am wondering can I have the download address about that magisk canary build? I've been bootlooping just like you before.

louiswong2099 said:
Hi man, I am wondering can I have the download address about that magisk canary build? I've been bootlooping just like you before.
Click to expand...
Click to collapse
Hi, the canary build is in the same place of the "normal" build in the official git page.
This is the direct link of the APK:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
The main page is this: https://github.com/topjohnwu/Magisk

Marcolo88 said:
Hi, the canary build is in the same place of the "normal" build in the official git page.
This is the direct link of the APK:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
The main page is this: https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
It worked on my Xiaomi 11T(not pro version) with a magisk-canary-patch, now the bootloop has been gone and really appreciated for your kindness help.