Develop Bugs

RN8Pro EEA TWRP & Root

So,
I have a RN8PRO running MIUI 11.0.3, on Android 9 (PGGEUXM)
From my understanding, it says global on about phone, but this is really EEA.
My question is, do all Global TWRP and Magisk support EEA?
How do I know this is a chinese device running PGGEUXM?
Has anyone put TWRP and rooted there phone running this software?
What is the best TWRP for this device? Should I go for the Official one or are there better ones that perhaps support OTA updates?
Why do some guides tell you to disable AVB where as others don't?
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
And why do some guides tell you to delete "recovery_fromboot.p"
My ultimate goal would be to have a custom recovery and root on stock MIUI.
I'm hoping someone could clear this up and perhaps reduce the rate of bricking phones! I will be using AgentFabulous preloader & lk.img as well in a preventive measure!
Tia!

I have the global model as well, LR-TWRP is what you want as most others will give you a black screen. If/when you upgrade to Q, there's an LR-TWRP that supports that too. Nice thing is, it comes with AVB and dm-verity feature built in. The regular Magisk will work fine too.
I removed the recovery_boot file as it would flash stock recovery on reboot if I didn't. Try it without and see.

wang1chung said:
I have the global model as well, LR-TWRP is what you want as most others will give you a black screen. If/when you upgrade to Q, there's an LR-TWRP that supports that too. Nice thing is, it comes with AVB and dm-verity feature built in. The regular Magisk will work fine too.
I removed the recovery_boot file as it would flash stock recovery on reboot if I didn't. Try it without and see.
Click to expand...
Click to collapse
Okay thanks, that clears quite a few things up, I believe in that case I'm going to follow pritish1998 guide on this, as he is uing LR-TWRP. I'm so out of touch it's been years since I've done any of this previously owning an s7 edge for 4 years.

Question Unable to update after rooting phone

Hello,
I received my oneplus 9 pro (global) the other day, and it's been working great. I rooted it no problem with a boot image I found on xda, and patched it using magisk manager. However, whenever I try to download the newest update, it fails every time. The first time it says that it's paused, and that it will continue whenever you press resume. I press resume, and then it says a problem occurred.
I tried to delete the .OTA folder, but it's no where to be found. I also tried to factory reset, as well as flashing the unpatched boot image, but it did not work.
Here's the link as to where I found the global boot image
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
if it is not the right version, or if there's a way to restore the original boot image, please let me know!

Andrew8578 said:
Hello,
I received my oneplus 9 pro (global) the other day, and it's been working great. I rooted it no problem with a boot image I found on xda, and patched it using magisk manager. However, whenever I try to download the newest update, it fails every time. The first time it says that it's paused, and that it will continue whenever you press resume. I press resume, and then it says a problem occurred.
I tried to delete the .OTA folder, but it's no where to be found. I also tried to factory reset, as well as flashing the unpatched boot image, but it did not work.
Here's the link as to where I found the global boot image
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
if it is not the right version, or if there's a way to restore the original boot image, please let me know!
Click to expand...
Click to collapse
Same here, was literally just googling for help.

vibrantliker said:
Same here, was literally just googling for help.
Click to expand...
Click to collapse
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).

zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.

Andrew8578 said:
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Click to expand...
Click to collapse
I'm in the USA and the bands (TMobile) work fine. No difference that I can see on this device or previous using the BA builds until the AA builds get going. Every OnePlus device has been this way for me.

Andrew8578 said:
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Click to expand...
Click to collapse
You may not want to hold your breath on that one. For whatever reason, oneplus does not release full OTA zips for AA half the time. (WTF ONEPLUS). Because of this, I long since started flashing BA over my global phone. As the gentleman said up above, it works absolutely perfectly.

zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
can I just flash the BA version on top of my current rom (AA) and not lose anything? I just got done reinstalling everything, and it was a pain. I don't want to do this a 3rd time, if I can avoid it.

I never had any issues with rooting/being unlocked and updating on my previous OnePlus phones... this is a new one for me.

On 8t I had to use EU..google is who releases OTAs for all variants except EU, which is still directly from oneplus. Rooting broke OTAs for me as well on any other rom besides EU...also I have 9pro, which I local updated to EU zip b4 flashing magisk_boot.img and I already received new update since rooting and all is good.

I just flashed BA on top on my current rom via system update (you have to click the cog wheel top right and put the OTA zip on your root directory)
Nothing changed and the navigation bar in split screen is indeed fixed, meaning this is the latest version.
Thanks again for letting me know about this!

zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
zoman7663 said:
I'm in the USA and the bands (TMobile) work fine. No difference that I can see on this device or previous using the BA builds until the AA builds get going. Every OnePlus device has been this way for me.
Click to expand...
Click to collapse
I'd be careful about flashing an international build for a global variant as EU regulations could be stricter, and most times are, with respect to signal strength, emissions, and other factors. Might work fine now, but there are different variants for a reason and one specific to the EU for a reason (laws are vastly different).

bulletbling said:
I'd be careful about flashing an international build for a global variant as EU regulations could be stricter, and most times are, with respect to signal strength, emissions, and other factors. Might work fine now, but there are different variants for a reason and one specific to the EU for a reason (laws are vastly different).
Click to expand...
Click to collapse
Noted, thanks for the info.

So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)

drmorrowa2 said:
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
Click to expand...
Click to collapse
What I want to know too!

drmorrowa2 said:
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
Click to expand...
Click to collapse
To unroot, go into magisk and click uninstall. Do know that I have tried this already and system update still won't go through. It appears it's being picky about the bootloader being unlocked I think. This is weird because on my OnePlus 7 pro, I did not have this issue and all I had to do was go to Magisk, uninstall ---> restore images, then do the OTA, and then have Magisk install to second slot, and then I would go back to system update, allow it to reboot, and I would still be rooted.

bulletbling said:
To unroot, go into magisk and click uninstall. Do know that I have tried this already and system update still won't go through. It appears it's being picky about the bootloader being unlocked I think. This is weird because on my OnePlus 7 pro, I did not have this issue and all I had to do was go to Magisk, uninstall ---> restore images, then do the OTA, and then have Magisk install to second slot, and then I would go back to system update, allow it to reboot, and I would still be rooted.
Click to expand...
Click to collapse
geez, I hope we don't have to relock and unlock for every update. I guess for the time being, there's no reason to be unlocked, but when custom ROM's start rolling out, that's going to be a major headache. I wonder if/when the updates are posted on One Plus website, will the updates work, or will root/unlock still prevent it?

I really want that update as I'm reading it made the battery much better. What to do!

I'm curious. so for a brand new phone why are you guys rooting it? It is not loaded with bloat ware (at least as much as samsung fpr example.) there are no custom roms yet, and oneplus is pushing updates to fix bugs. I think I'll wait till custom roms show up and then consider rooting.

TPXX said:
I'm curious. so for a brand new phone why are you guys rooting it? It is not loaded with bloat ware (at least as much as samsung fpr example.) there are no custom roms yet, and oneplus is pushing updates to fix bugs. I think I'll wait till custom roms show up and then consider rooting.
Click to expand...
Click to collapse
I root only for Viper4android but I'd like to unroot and relock bootloader again if it means I can get the updates.
I never reverse this process though. What are the best steps?

vibrantliker said:
I root only for Viper4android but I'd like to unroot and relock bootloader again if it means I can get the updates.
I never reverse this process though. What are the best steps?
Click to expand...
Click to collapse
My last rooting experience was on an S7. Afraid I can't help you with this one.

Question A bunch more questions from a noob

As title really, never flashed a custom ROM (at least not since my Galaxy S2) and while wait the 7 days to unlock the bootloader i'm trying to gather as much info as possible. So here goes;
1) Whilst I wait for the bootloader to unlock can I still turn off my phone and swap sim cards or will it reset the timer?
2) My Poco F3 is on MIUI Global 13.0.7.0 (SKHEUXM) - do I need to downgrade to 13.0.3.0 as per the instructions here?
3) The instructions for installing Crdroid lists an optional step for installing "DFE" but I cant seem to find out what DFE actually is.
4) Is it important to know if my phone has an A/B partition system and if it is how do I check for it?
5) After installing Magisk what other modules/tools/apps do I need to ensure Google Pay/Wallet will work as it seems a recent update has made it harder to fix.
6) Are there any bits of advice you can give for a avoiding a bootloop and/or bricked phone situation? Are there any common mistakes people make leading to a bootloop or bricked phone?
I think that's everything for now
Thanks

Goooober said:
As title really, never flashed a custom ROM (at least not since my Galaxy S2) and while wait the 7 days to unlock the bootloader i'm trying to gather as much info as possible. So here goes;
1) Whilst I wait for the bootloader to unlock can I still turn off my phone and swap sim cards or will it reset the timer?
2) My Poco F3 is on MIUI Global 13.0.7.0 (SKHEUXM) - do I need to downgrade to 13.0.3.0 as per the instructions here?
3) The instructions for installing Crdroid lists an optional step for installing "DFE" but I cant seem to find out what DFE actually is.
4) Is it important to know if my phone has an A/B partition system and if it is how do I check for it?
5) After installing Magisk what other modules/tools/apps do I need to ensure Google Pay/Wallet will work as it seems a recent update has made it harder to fix.
6) Are there any bits of advice you can give for a avoiding a bootloop and/or bricked phone situation? Are there any common mistakes people make leading to a bootloop or bricked phone?
I think that's everything for now
Thanks
Click to expand...
Click to collapse
1) Yes.
2) No, 13.0.3.0 is the required minimum, you can always use higher.
3) It disables forced encryption.
4) Poco F3 is A/B.
5) If any issues arise, you can always hide magisk and use safetynet fix.
6) When people don't follow installation instructions properly.

Dfe is disable force encryption but i dont think it works for android 12 so no need to flash it

ApexPrime said:
Dfe is disable force encryption but i dont think it works for android 12 so no need to flash it
Click to expand...
Click to collapse
It works, with DFE you can flash files from internal storage in twrp. But it also compromises phone security, so it's recommended not to use it.

If my phone is A/B do i have to do anything different when i flash Crdroid in TWRP?

Goooober said:
If my phone is A/B do i have to do anything different when i flash Crdroid in TWRP?
Click to expand...
Click to collapse
Almost all modern phones now ship with A/B partitions. So no, just follow the instructions given by the rom developer.

1. I unfortunately can't answer.
2. I wouldn't, 13.0.3 to 13.0.7 is very minor
3. DFE = Disable-Force-Encrypt = Android by default is encrypted.
DFE.zip removes the Boot-argument responsible for encrypting the Userdata-partition on the first boot, located in /vendor/etc/fstab
4. Poco F3 has an A/B-Partitionlayout. Most phones released with ~Android 10+ have A/B.
5. Personally, with the recent change, I tried many things to get GPay to work, got fed up with the Cat & Mouse Game with Google, and locked my BL.
6. If you flash using Fastboot Mode and the Flash aborts during a Partition-flash, don't reboot your phone, because otherwise your phone may never reboot back into Fastboot etc, and only show a Black screen.
ApexPrime said:
Dfe is disable force encryption but i dont think it works for android 12 so no need to flash it
Click to expand...
Click to collapse
It works on Android 12.
Goooober said:
If my phone is A/B do i have to do anything different when i flash Crdroid in TWRP?
Click to expand...
Click to collapse
No difference.
Further Notes about DFE:
If you don't use DFE before First Boot, userdata-partition gets encrypted, which means, beyond that, only TWRP SKKK will be able to access the userdata-partition.
If you decide to flash DFE once, you must flash it directly after every Update in TWRP, otherwise your phone may bootloop. At least that was the case for me! Before an update I decided I want my storage encrypted, but I got a bootloop. ^^
I wouldn't use DFE. Just leave it encrypted.

cyanGalaxy said:
5. Personally, with the recent change, I tried many things to get GPay to work, got fed up with the Cat & Mouse Game with Google, and locked my BL.
Click to expand...
Click to collapse
If you lock your bootloader after flashing a custom ROM does the custom ROM still work as intended or do you have to go back to stock?

Goooober said:
If you lock your bootloader after flashing a custom ROM does the custom ROM still work as intended or do you have to go back to stock?
Click to expand...
Click to collapse
Your phone will bootloop if you do that, because locked bootloader prevents custom roms from starting, thus it can only be used on stock roms.

Goooober said:
If you lock your bootloader after flashing a custom ROM does the custom ROM still work as intended or do you have to go back to stock?
Click to expand...
Click to collapse
No, I don't use a Custom ROM anymore. I'm back to Stock ROM, MIUI 13.0.7 for Europe.
Don't lock the BL with a Custom ROM. Only the Official ROM. Otherwise you risk hardbricking your phone.

Question Cannot update to C.47

Hello everyone,
I have a problem. I tried installing Nameless ROM on my OnePlus 9 Pro with no success. After that I reflashed my phone using MsmTool. Than I've updated it do 11.2.10.10 and later to C.47. But when I installed C.47 phone rebooted to recovery and when I selected reboot It wouldn't boot. Don't know what I'm doing wrong. My bootloader is locked.

Which phone version do you have?

luckylui said:
Which phone version do you have?
Click to expand...
Click to collapse
You mean software version or phone model?
Right now I'm on 11.2.10.10
My phone model is LE2120

skrubxgt said:
You mean software version or phone model?
Right now I'm on 11.2.10.10
My phone model is LE2120
Click to expand...
Click to collapse
Phone model.
So, I'd try it this way..
Since you are already on 11.2.10.10, I'd unlock the bootloader. (It'll wipe the device)
Download Oxygen Updater and download the stock versions through their.
Local update through your phone settings.
Once you are on A12 I'd follow the steps to installing Nameless.
My phone model is 2127 and I'm running Pixel Experience with no issues.

luckylui said:
Phone model.
So, I'd try it this way..
Since you are already on 11.2.10.10, I'd unlock the bootloader. (It'll wipe the device)
Download Oxygen Updater and download the stock versions through their.
Local update through your phone settings.
Once you are on A12 I'd follow the steps to installing Nameless.
My phone model is 2127 and I'm running Pixel Experience with no issues.
Click to expand...
Click to collapse
Oxygen Updater shows C.47 is available, should I install it?

Yes, download it and local update through the phone settings.
Keep in mind you will need to unlock your bootloader in order to flash a custom Rom.

luckylui said:
Yes, download it and local update through the phone settings.
Keep in mind you will need to unlock your bootloader in order to flash a custom Rom.
Click to expand...
Click to collapse
Well it didn't work, local update wouldn't allow me to install it.

skrubxgt said:
Well it didn't work, local update wouldn't allow me to install it.
Click to expand...
Click to collapse
I wonder if you need to unlock the bootloader and root? I can't test it out unfortunately since I'm on the Pixel Rom :/

luckylui said:
I wonder if you need to unlock the bootloader and root? I can't test it out unfortunately since I'm on the Pixel Rom :/
Click to expand...
Click to collapse
I wonder why I can't install official update, when I installed C.47 it just bootloops. Tried installing Global, India and EU builds but after all it is the same situation.

skrubxgt said:
I wonder why I can't install official update, when I installed C.47 it just bootloops. Tried installing Global, India and EU builds but after all it is the same situation.
Click to expand...
Click to collapse
Yeah, that is very weird.
I wonder if something with your phones partitions got messed up, but I would figure doing an MSM restoration would bring everything back.

luckylui said:
Yeah, that is very weird.
I wonder if something with your phones partitions got messed up, but I would figure doing an MSM restoration would bring everything back.
Click to expand...
Click to collapse
Tried restoring it using MsmTool, still nothing

I have exactly the same problem, except my device is a LE2123. Running the stock version that came out of the box. 11.2.10.10.LE15BA. down load and install seem to be ok, but at the point to reboot the device loop several times and then recovers to 11.2.10.10....

If you guys are going custom Rom, I would just go ahead and install the custom Rom. Looks like the firmware will carry over once you transition. Maybe that'll work out better than updating to the next available stock firmware.

luckylui said:
If you guys are going custom Rom, I would just go ahead and install the custom Rom. Looks like the firmware will carry over once you transition. Maybe that'll work out better than updating to the next available stock firmware.
Click to expand...
Click to collapse
Yea, if you want a custom ROM, just do it and follow the instructions to the letter....

TheGhost1951 said:
Yea, if you want a custom ROM, just do it and follow the instructions to the letter....
Click to expand...
Click to collapse
I have the 2127 Tmo model and was on C.19 version. Downloaded and installed Pixel Experience Rom which is C.62 and it works fine. But, I have heard C.19 is pretty much C.62 and Pixel Rom you can install it on any version.. not sure about Nameless though. Worst case scenario is you would have to MSM back (which I know is a pain) but, I guess gotta try whatever works.

luckylui said:
I have the 2127 Tmo model and was on C.19 version. Downloaded and installed Pixel Experience Rom which is C.62 and it works fine. But, I have heard C.19 is pretty much C.62 and Pixel Rom you can install it on any version.. not sure about Nameless though. Worst case scenario is you would have to MSM back (which I know is a pain) but, I guess gotta try whatever works.
Click to expand...
Click to collapse
Hi my friend, I am on TMO with Model LE2127 running stock 11.2.9.9 and happy as a Lark. I got rid of bloatware, full root with partitions mounted as R/W, custom bootanimation and custom systemwide font. With just Magisk Root, you are not fully rooted. And stock OOS 12 is squirrelly anyway. The latest is not always the greatest.....hope you are having a great day! TheGhost!

To me, the main reason for root on any smartphone is to be able to customize it anyway you like without having to go and find this module or that module for Magisk. I tried the custom font module for Magisk and it was not systemwide. The way I am rooted, even the keys on the keyboard are changed to the custom font I have installed....if you don't have complete control of your phone, you are not truly rooted!

TheGhost1951 said:
Hi my friend, I am on TMO with Model LE2127 running stock 11.2.9.9 and happy as a Lark. I got rid of bloatware, full root with partitions mounted as R/W, custom bootanimation and custom systemwide font. With just Magisk Root, you are not fully rooted. And stock OOS 12 is squirrelly anyway. The latest is not always the greatest.....hope you are having a great day! TheGhost!
Click to expand...
Click to collapse
Hello, TheGhost! Glad to see an old timer on the forums from many moons ago! We've seen it all and still learning till this day as technology develops. Totally agree with ya and it sure does make a difference once you take full control of your phone. That's why Android will always be my go to! Cheers to ya!!

luckylui said:
Hello, TheGhost! Glad to see an old timer on the forums from many moons ago! We've seen it all and still learning till this day as technology develops. Totally agree with ya and it sure does make a difference once you take full control of your phone. That's why Android will always be my go to! Cheers to ya!!
Click to expand...
Click to collapse
You bet my friend,

I had a similar problem on my 9 with the C.48 ROM. I ended up MSM back to stock, unlocked the bootloader, then took the OTAs and it downloaded the full ones. All those flashed fine, then it got stuck at C.60 and said I was up to date so I had to grab the C.62 full India OTA and flashed that and now I'm back up to date.
I'm assuming based on the version and model that you're running the EU ROM? If so, grab Oxygen Updater and download the full OTA of C.62 from it (turn on advanced setting so you can select incompatible images, select EU full). Take that and copy to PC. Download Fastboot Enhance, reboot to fastbootd (adb reboot fastboot). Double click when it shows your device, go to partitions page. Search cow and select and delete each one you find there individually (you just keep searching cow after you delete each one, no idea why the program wasn't designed to just let you select all of them at once and delete them, maybe it's a safety design for dumb people). Then click flash payload.bin and choose the C.62 zip file you downloaded and it will flash to your phone. Reboot to system and you should be good to go.
Fastboot Enhance doesn't have all the checks that the regular updater does so as long as it's a full OTA and it's not corrupted, it should flash fine.
If you screw anything up, it's time to MSM again. Annoying but that's how it goes with these frustrating OnePlus devices.

OOS 12.1 Stable arrives for India & EU, no date for global

"What's disappointing is that these devices are the last to receive stable OOS12, despite their beta programs starting earlier than a lot of other devices... Hopefully this means there won't be too many bugs, but honestly we doubt it. This is OnePlus after all. "
https://oxygenupdater.com/article/352/

I got oneplus 7t HD1903 its global or EU?

Global 12.1 already up.

I received the updated on 10/31/2022 - my device model is HD1905_11.F.17 and located in USA. Not sure if I like OS12 - the Oxygen Launcher shelf is now replaced by Google Discussion unless I swipe-down from the top-right. WTH! Google Discussion is a waste and garbage chewing, with it disabled is a nasty looking screen that tells me to enable discussion... Not sure why OPPO pushed this particular change.

Anyone knows how can i install OOS12 both slots? I've tried to local upgrade, but it doesn't work.

Ronam said:
Anyone knows how can i install OOS12 both slots? I've tried to local upgrade, but it doesn't work.
Click to expand...
Click to collapse
If you're rooted Should just be
download full oos, disable or uninstall magisk modules, do local upgrade from system /system updates/gear.
Install magisk to inactive slot, reboot
Repeat process if you want 12 on both slots
If you're not rooted i don't believe you can force the update to both slots without flashing with ADB

wfred said:
If you're rooted Should just be
download full oos, disable or uninstall magisk modules, do local upgrade from system /system updates/gear.
Install magisk to inactive slot, reboot
Repeat process if you want 12 on both slots
If you're not rooted i don't believe you can force the update to both slots without flashing with ADB
Click to expand...
Click to collapse
I did this (to inactive slot) but now my phone wont boot. I can get in fastboot. Anyone have stock boot for OS12 lying around?

wfred said:
If you're rooted Should just be
download full oos, disable or uninstall magisk modules, do local upgrade from system /system updates/gear.
Install magisk to inactive slot, reboot
Repeat process if you want 12 on both slots
If you're not rooted i don't believe you can force the update to both slots without flashing with ADB
Click to expand...
Click to collapse
Thanks, i've found an update method without root in telegram. OPlocalupdate app, update works with that application.

ViNOK16Bit said:
I did this (to inactive slot) but now my phone wont boot. I can get in fastboot. Anyone have stock boot for OS12 lying around?
Click to expand...
Click to collapse
You can use ADB to find out which slot is booting then force boot into the other (not updated) slot and try the update again
Here are the rollback files and instructions if you want to go back to 11
https://community.oneplus.com/thread?id=1181216999612088323 [OxygenOS 12 MP2 for OnePlus 7T/7T Pro]
BTW you should scroll through the comments there. You might have 2nd thoughts about going to 12

Anyone succeeded with upgrade to Android 12.1 with OP7T T-Mobile converted to Global ROM?
Mine crashes to Black Screen after update.

hasanin.xaidi said:
Anyone succeeded with upgrade to Android 12.1 with OP7T T-Mobile converted to Global ROM?
Mine crashes to Black Screen after update.
Click to expand...
Click to collapse
Sure, no prob here. Try to go into fastboot (bootloader mode) and switch slot by typing "fastboot set_active other" and reboot

I have Oneplus 7t HD1907 T-Mobile version converted to Global but I still don't have an update for OxygenOS 12

dokuzovski said:
I have Oneplus 7t HD1907 T-Mobile version converted to Global but I still don't have an update for OxygenOS 12
Click to expand...
Click to collapse
Use oxygen updater apk from Play store and ota manually (local install) from oos11

It only gives me HD1901 version Indian version. I already messed up my phone once using that version via local update.

These are the only 7T OOS 12 OTA files that I've seen so far, from Oxygen Updater:
India HD1901_11_F.17 Android 12 https://mega.nz/file/s09VyDAb#qhoLjfqUPQzoJdJ-eJ5K37GabcoVYsnzE4HE87zNvlI
EU HD1903_11_F.17 Android 12 (fails to upgrade?)
3.7 GB file on MEGA
mega.nz

GLOBAL uses INDIAN rom though EU works on GLOBAL also

HueyT said:
Sure, no prob here. Try to go into fastboot (bootloader mode) and switch slot by typing "fastboot set_active other" and reboot
Click to expand...
Click to collapse
I tried, but it fails to a black screen everytime

HueyT said:
GLOBAL uses INDIAN rom though EU works on GLOBAL also
Click to expand...
Click to collapse
Is this correct? Users are reporting screen brightness problems and OTA upgrade failures.

andrelecomte said:
Is this correct? Users are reporting screen brightness problems and OTA upgrade failures.
Click to expand...
Click to collapse
Works for me, no problem, hd1907 converted to global with patched msmtool by Superboy58 on XDA

HueyT said:
Works for me, no problem, hd1907 converted to global with patched msmtool by Superboy58 on XDA
Click to expand...
Click to collapse
Did you use one of these OTA upgrades?:
India
HD1901_11_F.17
EU
HD1903_11_F.17