Database Users

Downgrading from Pie(pixel exp) to Stock.

Hello Everyone!
I am a total noob. I have rooted many phone but never once reversed the process. Plus with stock moto being 32bit and customs being 64 it is even more complicated for me. And plus all this post about lost IMIE numbers and lost GPT makes me scared.
If i may, can I get step by step guide to relock my bootloader and get OTAs.
I have read most of the tutorials here but couldnt get the confidence to move forward(they all sound a little different)
I have moto G5 plus XT1686 indian version 4Gb/32GB currently running PE 9.0 (GTRCraft). I dont remember which version I had when I unlocked the bootloader. I do have a backup of my persist/efs.
I did see one tutorial but it is for 8.1.0 to stock and IDK if that works for me.
Thanks in advance.

reganEZ said:
Hello Everyone!
I am a total noob. I have rooted many phone but never once reversed the process. Plus with stock moto being 32bit and customs being 64 it is even more complicated for me. And plus all this post about lost IMIE numbers and lost GPT makes me scared.
If i may, can I get step by step guide to relock my bootloader and get OTAs.
I have read most of the tutorials here but couldnt get the confidence to move forward(they all sound a little different)
I have moto G5 plus XT1686 indian version 4Gb/32GB currently running PE 9.0 (GTRCraft). I dont remember which version I had when I unlocked the bootloader. I do have a backup of my persist/efs.
I did see one tutorial but it is for 8.1.0 to stock and IDK if that works for me.
Thanks in advance.
Click to expand...
Click to collapse
Just wipe everything from twrp and then use LMSA OR manually flash the stock ROM and then go for bootloader lock procedure. Then you are done. And you won't lose any IMEI or Persist, so you will be safe.

riyan65 said:
Just wipe everything from twrp and then use LMSA OR manually flash the stock ROM and then go for bootloader lock procedure. Then you are done. And you won't lose any IMEI or Persist, so you will be safe.
Click to expand...
Click to collapse
So just download a TWRP flashable 8.1.0 rom and i m good?

reganEZ said:
So just download a TWRP flashable 8.1.0 rom and i m good?
Click to expand...
Click to collapse
No, download a fastboot flashable ROM, with a TWRP flashable you won't be able to apply OTAs:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Use OPSS28.85-17-4 if you're in the US or OPSS28.85-13-3 for the rest of the world.
Follow the available tutorials for flashing that firmware and after that for relocking the BL (almost the same commands). Make sure you have Minimal ADB & Fastboot
https://androidfilehost.com/?fid=746010030569952951
and Motorola drivers
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view
installed on your PC.
For the fastboot commands you can use this flashall.bat:
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0

Wolfcity said:
No, download a fastboot flashable ROM, with a TWRP flashable you won't be able to apply OTAs:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Use OPSS28.85-17-4 if you're in the US or OPSS28.85-13-3 for the rest of the world.
Follow the available tutorials for flashing that firmware and after that for relocking the BL (almost the same commands). Make sure you have Minimal ADB & Fastboot
https://androidfilehost.com/?fid=746010030569952951
and Motorola drivers
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view
installed on your PC.
For the fastboot commands you can use this flashall.bat:
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
Click to expand...
Click to collapse
ATTENTION:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Example: If when you unlock your bl you was on NPNS25.137-33-11 you need the same (or later) complete firmware because you can't downgrade.
This is a part of the bootloader locking tutorial here on XDA. Does this make a difference?

reganEZ said:
ATTENTION:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Example: If when you unlock your bl you was on NPNS25.137-33-11 you need the same (or later) complete firmware because you can't downgrade.
This is a part of the bootloader locking tutorial here on XDA. Does this make a difference?
Click to expand...
Click to collapse
+ i tried the method and it says "slot not found" error

reganEZ said:
ATTENTION:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Example: If when you unlock your bl you was on NPNS25.137-33-11 you need the same (or later) complete firmware because you can't downgrade.
This is a part of the bootloader locking tutorial here on XDA. Does this make a difference?
Click to expand...
Click to collapse
You have to use the firmware you were on before you changed to a custom ROM or a newer one.
Never use an older one, downgrading can brick your device.
reganEZ said:
+ i tried the method and it says "slot not found" error
Click to expand...
Click to collapse
The "slot not found" error is normal, it's related to A/B devices with more than one recovery slot like Pixel phones. The commands should work nevertheless. Ignore the message.

I reloaded my G5 Plus with POTTER_RETAIL_7.0_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip sucessfuly. However, I was not able to relock the bootloader :
C:\Moto potter>fastboot oem lock
...
(bootloader) Still require signed boot.img
It got OTA'ed to Oreo 8.1 latter on, but still bootloader unlocked.
I just went through the flashing process to POTTER_RETAIL_8.1.0_OPSS28.85-17-4, same damned thing.
Everything works fine, excpet for Netflix that can't be installed no more and my bank software who keeps complaining.
I just dunno what to do to relock, any advice ?

Wolfcity said:
You have to use the firmware you were on before you changed to a custom ROM or a newer one.
Never use an older one, downgrading can brick your device.
The "slot not found" error is normal, it's related to A/B devices with more than one recovery slot like Pixel phones. The commands should work nevertheless. Ignore the message.
Click to expand...
Click to collapse
Hello, Thank you for your reply.
I understand I cannot use an older firmware. I remember I unlocked my BL when I was in 7.0 itself, but when I installed the Arrow 9.0, I flashed the 8.1 firmware zip to get the NFC and Fingerprint working. So now my ro.build fingerprint doesnt tell me which firmware build i am on it just says "8.1"
I am confused what to do. Should I download the latest 8.1 moto rom and flash it? I tried the TWRP flashable rom but the phone just goes upto Hello Moto bootscreen and then bootloops.
I erased everything and flashed PE 9.0 again.

reganEZ said:
Hello, Thank you for your reply.
.....Should I download the latest 8.1 moto rom and flash it?.......
Click to expand...
Click to collapse
That's what I would do. If you flash the latest firmware it can't be older as the one you're originally coming from.
Follow my previous post:
Wolfcity said:
No, download a fastboot flashable ROM, with a TWRP flashable you won't be able to apply OTAs:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Use OPSS28.85-17-4 if you're in the US or OPSS28.85-13-3 for the rest of the world.
Follow the available tutorials for flashing that firmware and after that for relocking the BL (almost the same commands). Make sure you have Minimal ADB & Fastboot
https://androidfilehost.com/?fid=746010030569952951
and Motorola drivers
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view
installed on your PC.
For the fastboot commands you can use this flashall.bat:
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.batflashallO.bat?dl=0
Click to expand...
Click to collapse

Wolfcity said:
That's what I would do. If you flash the latest firmware it can't be older as the one you're originally coming from.
Follow my previous post:
Click to expand...
Click to collapse
Hello Sir, i was on OPSS28.85-13-5 when i flashed custom rom. The link you provided lists OPSS28.85-13-3 as the latest firmware. Should i install that? I am from India if that helps. Help please.

MrAshuBrar said:
Hello Sir, i was on OPSS28.85-13-5 when i flashed custom rom. The link you provided lists OPSS28.85-13-3 as the latest firmware. Should i install that? I am from India if that helps. Help please.
Click to expand...
Click to collapse
Take this one:
85-13-5
https://forum.xda-developers.com/g5-plus/how-to/official-oreo-coming-soon-t3779098/post78844908

CanadianGixxerman said:
I reloaded my G5 Plus with POTTER_RETAIL_7.0_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip sucessfuly. However, I was not able to relock the bootloader :
C:\Moto potter>fastboot oem lock
...
(bootloader) Still require signed boot.img
It got OTA'ed to Oreo 8.1 latter on, but still bootloader unlocked.
I just went through the flashing process to POTTER_RETAIL_8.1.0_OPSS28.85-17-4, same damned thing.
Everything works fine, excpet for Netflix that can't be installed no more and my bank software who keeps complaining.
I just dunno what to do to relock, any advice ?
Click to expand...
Click to collapse
Flash all the system files while locking. (0-8). Older locking guides have only 0-4. Newer firmware has 9 system files.

Wolfcity said:
Take this one:
85-13-5
https://forum.xda-developers.com/g5-plus/how-to/official-oreo-coming-soon-t3779098/post78844908
Click to expand...
Click to collapse
Thank you so much ?

[CLOSED][Guide] How to ROOT the OnePlus8T KB2003 & current OTA

Hi,
quick files that many of us waiting for
OnePlus 8T, 11.0.1.2 KB05BA KB2003
Newest (20.10.2020) OTA:
https://drive.google.com/file/d/1uKV_j8yIQLPeIRJkf1KIUlJcIaH8BppR/view?usp=sharing
boot.img (stock)
https://drive.google.com/file/d/12VopoB984YmJHUJuqMBA4jyID1Sp_sPQ/view?usp=sharing
boot.img (patched, checked, working)
https://drive.google.com/file/d/1V4esvmJCBkwskq2shfWcylPL53h4dd_2/view?usp=sharing
=======================================
You like it?
paypal.me/widmak
=======================================
Thanks!

Thanks. But where's the guide or howto, that the title says ?

I flashed your patched boot image, but no Magisk is detected in either stable or canary Magisk Manager. There might be an issue.
EDIT: Confirmed that the issue is on your end. Patched the image myself and flashed it, with Magisk being detected by Magisk Manager.
https://drive.google.com/file/d/1yw5Fwgy0_ArPD_itnZ66nmdWA2NapFPg/view
This boot image works.

Any idea to flash the EU rom from India?

felata said:
Any idea to flash the EU rom from India?
Click to expand...
Click to collapse
Download the full OTA zip, keep it in internal storage outside any folders.
Go to System -> System Updates
Click the gear icon, select local upgrade
Then, select the downloaded Full OTA zip.
Install and reboot.
Done.

theincognito said:
Download the full OTA zip, keep it in internal storage outside any folders.
Go to System -> System Updates
Click the gear icon, select local upgrade
Then, select the downloaded Full OTA zip.
Install and reboot.
Done.
Click to expand...
Click to collapse
The system says that it won't allow downgrade

Which magisk did you use please?

Alvincyq said:
The system says that it won't allow downgrade
Click to expand...
Click to collapse
If you updated to the Indian/Global 11.0.1.2 before doing this, you only have 2 options:
1. Wait for the next OOS update, but when the Indian/Global update comes, don't update.
Instead, wait for the full update zip of the EU to be available, and then follow the steps in the previous comment.
2. Unlock bootloader, flash the full OTA zip of any variant via fastboot, and relock the bootloader.

elliottweaver said:
I flashed your patched boot image, but no Magisk is detected in either stable or canary Magisk Manager. There might be an issue.
EDIT: Confirmed that the issue is on your end. Patched the image myself and flashed it, with Magisk being detected by Magisk Manager.
https://drive.google.com/file/d/1yw5Fwgy0_ArPD_itnZ66nmdWA2NapFPg/view
This boot image works.
Click to expand...
Click to collapse
Your file did not work for me but i modified the stock file from the first post myself and that worked. i guess there is something coded into the file by magisk that is depended on the phone.

theincognito said:
Download the full OTA zip, keep it in internal storage outside any folders.
Go to System -> System Updates
Click the gear icon, select local upgrade
Then, select the downloaded Full OTA zip.
Install and reboot.
Done.
Click to expand...
Click to collapse
I'm on Kb2005 and I'm only able to get an incremental update. Can I pull the bin file from that update

Was there an OTA specific to models outside of the U.S.? I see at least two variations are already getting an update but nothing is available yet for my US (KB2005) variant I got today.

MNoisy said:
Was there an OTA specific to models outside of the U.S.? I see at least two variations are already getting an update but nothing is available yet for my US (KB2005) variant I got today.
Click to expand...
Click to collapse
I have KB2005 as well. No updates for me. I tried to just boot the images posted in the other thread with no luck.

northmendo said:
I have KB2005 as well. No updates for me. I tried to just boot the images posted in the other thread with no luck.
Click to expand...
Click to collapse
Unless OnePlus is very different from the other major manufactures, you definitely do not want to use a patched boot image from a different model variation of software/firmware. At best it will cause major issues.. At worst, it will brick it.
If Oneplus is different, I would love some feedback on why and what they do from other users.

MNoisy said:
Unless OnePlus is very different from the other major manufactures, you definitely do not want to use a patched boot image from a different model variation of software/firmware. At best it will cause major issues.. At worst, it will brick it.
If Oneplus is different, I would love some feedback on why and what they do from other users.
Click to expand...
Click to collapse
Correctish, you don't want to flash it. You can just boot the image. If successful it'll just boot the phone. If unsuccessful it will hang and you can just force reboot. No damage can because because it's not writing the boot image to the phones storage. Kinda like booting from a flash drive. The code is
Code:
fastboot boot /path/boot.img
If you boot a patched boot image you will have access to a rooted phone until you reboot. I.E. just enough time to flash magisk on the installed boot image.
Hope that makes sense.

northmendo said:
Correctish, you don't want to flash it. You can just boot the image. If successful it'll just boot the phone. If unsuccessful it will hang and you can just force reboot. No damage can because because it's not writing the boot image to the phones storage. Kinda like booting from a flash drive. The code is
Code:
fastboot boot /path/boot.img
If you boot a patched boot image you will have access to a rooted phone until you reboot. I.E. just enough time to flash magisk on the installed boot image.
Hope that makes sense.
Click to expand...
Click to collapse
I am familiar with how it works but with brands like HTC and Samsung, if we use a boot.img from a different variation, it will not work or even brick it. Thanks for the heads up! It sounds like there is more room for error for testing with OnePlus and modifying the system.

Can someone please provide a link to the Magisk Manager that 's working with this bootimage?
Edit: Found it, got root but it doesn't pass SafetyNet...

epr said:
Can someone please provide a link to the Magisk Manager that 's working with this bootimage?
Edit: Found it, got root but it doesn't pass SafetyNet...
Click to expand...
Click to collapse
Which one was it? My Magisk is not working either. I assumed it was because the kb2005 was only an incremental update. I have the canary version from github. Is there another for oneplus?

MNoisy said:
Which one was it? My Magisk is not working either. I assumed it was because the kb2005 was only an incremental update. I have the canary version from github. Is there another for oneplus?
Click to expand...
Click to collapse
Downloaded it from github: https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk

epr said:
Downloaded it from github: https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
Click to expand...
Click to collapse
Yeah, same one. And it worked on the incremental Ota for kb2005?
Do you mind posting the patched boot.img?
Thank you!

MNoisy said:
Yeah, same one. And it worked on the incremental Ota for kb2005?
Do you mind posting the patched boot.img?
Thank you!
Click to expand...
Click to collapse
Don't know for KB2005, mine is KB2003.
I used stock boot.img from OP and patched it myself, all already patched files didn't work.

11.0.8.8 Rooting Issue

I am on the latest 11.0.8.8 EU version. I had patched the boot.img using magisk 23 app, but when i try to flash the patched boot.img using adb fastboot, keep getting "com.android.phone" crashes. Need to flash stock boot.img to get the sim cards working. Any suggestion to get root ?

Remove oos native call recorder module if you have it, if not just remove all modules.

MrEvilPanda said:
I am on the latest 11.0.8.8 EU version. I had patched the boot.img using magisk 23 app, but when i try to flash the patched boot.img using adb fastboot, keep getting "com.android.phone" crashes. Need to flash stock boot.img to get the sim cards working. Any suggestion to get root ?
Click to expand...
Click to collapse
Have you been on my guide mate?? It's all laid out for you..
Don't flash anything, you want to boot first as this is not permanent.
Stable 23 is the correct version..

dladz said:
Have you been on my guide mate?? It's all laid out for you..
Don't flash anything, you want to boot first as this is not permanent.
Stable 23 is the correct version..
Click to expand...
Click to collapse
I am on the stable 23 version. Disabling the native OOS call recording module solved the issue. @gsser Thanks mate.

MrEvilPanda said:
I am on the stable 23 version. Disabling the native OOS call recording module solved the issue. @gsser Thanks mate.
Click to expand...
Click to collapse
Ah yes, always disable Magisk modules prior to upgrading firmware.
As they may not be compatible, this is also in the guide.
Glad you're up and running mate
Nice one

So idk if this is the correct place to post questions but i have a OnePlus 8 pro 11.0.8.8IN11BA, i want to root it, but i can't find the stock rom for this version. Can anyone help me??

Arksuga said:
So idk if this is the correct place to post questions but i have a OnePlus 8 pro 11.0.8.8IN11BA, i want to root it, but i can't find the stock rom for this version. Can anyone help me??
Click to expand...
Click to collapse
Hi, see this thread:
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com

galaxys said:
Hi, see this thread:
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you so much!!!! So now in order to root it i should unlock the bootloader, and then patch the IMG i downloaded with the magisk manager app, connect the phone to the PC with USB debugging on, reboot in fastboot mode, and type on the windows command thing this ( the commands in the image attached ):

Arksuga said:
Thank you so much!!!! So now in order to root it i should unlock the bootloader, and then patch the IMG i downloaded with the magisk manager app, connect the phone to the PC with USB debugging on, reboot in fastboot mode, and type on the windows command thing this ( the commands in the image attached ):
Click to expand...
Click to collapse
Yep I've got guides for unlocking the bootloader and rooting in the guides sections.
Both called as such accordingly.
Tbh there are a few guides all should be fine.
Just read through the root guide.
Unlocking the bootloader it's easy.
Code: fastboot OEM unlock
Agree on phone.
Rooting:
Obtain patched image
Fastboot boot Magisk patched
Don't flash it, just wait for boot then open Magisk and click install / direct install.
Again this is all in the guides.

Magisk 23 to 24 ruined

Hi!
I had Magisk v23 working fine with Magisk hide but then I upgraded to v24. Magisk app successfully installed and shows Magisk not present. And when I try to DirectInstall Magisk, I get verification failed error. Attached both screenshots.
Now, I have installed and confirm TWRP is working but do not know how to make Magisk working again and it seems it gonna be a wipe. Any help appreciated.

[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Step by step: Magisk 24.1 is new and as you have seen completely different.
Installation instructions: https://topjohnwu.github.io/Magisk/install.html

Issue is that on my other phone, Sony Xperia XZ Premium G8142, the same in-app upgrade weas successful with out any issues. I lost Magisk Hide but an extension recovered that function. But it all went haywire on this S8

xabu said:
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Step by step: Magisk 24.1 is new and as you have seen completely different.
Installation instructions: https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
This guide expects me to know what ROM I have. Thing is, I do not know what my device really is. It's running a ROM that I do not recognize (My post: https://forum.xda-developers.com/t/...l-and-odin-cannot-flash.4372669/post-86069051). I do not have the sources for it so I cannot acquire the required two files. Ramdisk is Yes as per my screenshot but I cannot follow the rest of the guide without the files.

try this
Check hardware and software info Galaxy:
*#12580*369#
Android 9 shows almost certainly a stockrom Pie .

xabu said:
try this
Check hardware and software info Galaxy:
*#12580*369#
Android 9 shows almost certainly a stockrom Pie .
Click to expand...
Click to collapse
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.

Your phone needs twrp and a new good custom ROM ...
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Here are certainly members of the forum with lots of expertise!

Doomer D. Great said:
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Click to expand...
Click to collapse
Maybe only European ?

xabu said:
Your phone needs twrp and a new good custom ROM ...
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Here are certainly members of the forum with lots of expertise!
Click to expand...
Click to collapse
I just TWRP it. It went smoothly. I love a new ROM but need to know what device is it.
Download mode say it is SM-G950N
Android say it is SM-950FD
Both SIM slots have the same IMEI number. This part is beyond my understanding.
I have Odin and know the basics. Just need to find a ROM I can go for: What official I should flash first and what custom. Any recommendation?

As soon as you make a TWRP total backup, you can see your boot.img and move a copy to your internal sd-card. There it can be picked up by Magisk and patched....Magisk will put it in your download folder on the internal sd-card ...
for the best Rom ask members with your S8 phone. I'am on the S7 Edge.

xabu said:
Maybe only European ?
Click to expand...
Click to collapse
Doomer D. Great said:
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Click to expand...
Click to collapse
Just found out:The "famous" secret codes only work on stock based ROMs ¯\_( ͡❛ ͜ʖ ͡❛)_/¯

xabu said:
As soon as you make a TWRP total backup, you can see your boot.img and move a copy to your internal sd-card. There it can be picked up by Magisk and patched....Magisk will put it in your download folder on the internal sd-card ...
for the best Rom ask members with your S8 phone. I'am on the S7 Edge.
Click to expand...
Click to collapse
I have been trying to make the total backup but I do not see any boot.img:
And I do not see the file in the Device/TWRP/Backups:
Again, I must be missing something obvious. And as per the Magisk guide, I need the boot.img

magisk 24 is ****, it's bricking MediaTek powered Samsung phones

Boot.img from TWRP backup
In clockworkmod kernel and recovery are backed up as IMGs. But in TWRP it is boot.emmc.win Anybody know how to convert jt to boot.img? Help will be really appereciated. Sent from my HTC One X using xda app-developers app
forum.xda-developers.com
I must tell you that my custom rom for the s7 gives me the boot.img as the first file as soon as i open the zip.
the boot.img can also be reached by downloading the right stock rom for your phone. In that case it is the best practice to patch the whole
AP file by using Magisk.

IN2023 (EU) OP 8 Pro. Anyone managed to root?

Hi, I have the above device
I tried to root today 13.1 .0.513(EX01) but going into bootloop with magisk 26.1 anyone managed to do ?
I was rooted before but as usual my update led to automatic reboot (for some reason it doesn't ask me). I used the extracted boot to patch but the patched boot leads to boot loop (Stays at oneplus red sign)

You could try the patched boot.img from one of the links in my signature. I patched it myself. Should work?

Kuronosu said:
You could try the patched boot.img from one of the links in my signature. I patched it myself. Should work.
Click to expand...
Click to collapse
Thanks. Unfortunately I managed to have my phone wiped for some reason yesterday (didn't ask me). So since I couldn't do anything I reverted to oxygen 11 via downgrade and the upgrtaded to f30 or so with android 13. Btw my boot imaged was patched correctly but loading it caused bootloop

Where can I download the rom 13.1 .0.513(EX01)? Searched everywhere but couldnt find the EU version

yoonohoo said:
Where can I download the rom 13.1 .0.513(EX01)? Searched everywhere but couldnt find the EU version
Click to expand...
Click to collapse
oxygen updater

jimger said:
oxygen updater
Click to expand...
Click to collapse
OTA or the app? Never use the app. And the OTA now's playing up with the auto reboot