Related
~*~ Disclaimer: I'm not responsible if you destroy your device or break your warranty. Use at your own risk! ~*~
Easy way to update your Realme X2 Pro Global or India Variant from C.38 to F.14 (Android 10 to Android 11) [with Magisk root]
Update your Realme X2 Pro with C.38 download the file specific for your device IN/Global
Make sure the bootloader is unlocked. click here for Unlock Procedure
Boot to recovery (power off device and then hold vol- and power together)
Must check if this version is installed OrangeFox-R11.0_2-Beta-RMX1931
Download: OrangeFox @4j17h
Install RUI 2.0 (F.11) with OrangeFox - Dont format anything
Download: RUI 2.0 (F.11) India
Download: RUI 2.0 (F.11) Global/EU
------------------------------------------
Download: RUI 2.0 (F.14) Zip (Region -Unknown)
Download: RUI 2.0 (F.14) Global/EU
Do not restart to System now if you need custom recovery.
Install OrangeFox Beta img (RUI2.0) for Android 11 & select recovery partition.
Download: OrangeFox Beta RUI 2.0 for Android 11 Thanks @Jerry08, @4j17h
Install Patched vbmeta img & select vbmeta partition.
[This step is essential to have recovery persistent by not getting replaced with stock recovery and also to avoid bootloop]
Code:
fastboot --disable-verity --disable-verification flash vbmeta patched_vbmeta.img
Download: Patched vbmeta
If needed Stock Recovery -
Rich (BB code):
fastboot flash recovery stock_recovery_RUI2_A11.img
MUST Wipe DATA after 4 digit code in stock recovery
[Skip this step, Only Experimental for testing]
Install Magisk Canary - Rename apk to zip and flash with USB OTG (Optional only if root is required)
Reboot to System (May take 5-7 minutes to complete booting)
Enjoy RUI 2.0 updated with all your apps and data intact.
Realme has restricted access of Data in Beta phase which means we cant access Data partition and most of files with OrangeFox.
Your "usrdata" partition or the standard sdcard folder having your Contents, photos, videos, files, songs etc will be accessible as you will use normally after restarting in RUI2.0.
Dont ask steps for Roll back to old version. Will lose all data and will be formatted when roll back.
Any issues, feel free to discuss and help out each other politely.
After read all bugs i am happy with android 10
anang1979 said:
After read all bugs i am happy with android 10
Click to expand...
Click to collapse
Hell yeah, I'll happily stay on RUI 1 with that issues list lol
I am using RUI 2.0 F.10 as my daily driver for normal use. I find it to be good and only not having root is my current issue.
Games and other performance is fine, issues happen with extreme settings or over long time usage on battery.
No one actually needs to lock bootloader or need DRM L1 unless have to watch OTP (Netflix, prime,etc) in high resolution or HDR.
Sir Thanks Soo Much But For ur Keen And Kind Information Bootloader Is Currently Not Unlocking Due To Some Network Error If U Really A Developer Fix That ...... Everyone Will Appreciate U For That Believe Me..
hack-os said:
I am using RUI 2.0 F.10 as my daily driver for normal use. I find it to be good and only not having root is my current issue.
Games and other performance is fine, issues happen with extreme settings or over long time usage on battery.
No one actually needs to lock bootloader or need DRM L1 unless have to watch OTP (Netflix, prime,etc) in high resolution or HDR.
Click to expand...
Click to collapse
Same here, the only thing stopping me from updating now is that there is no root. Don't care about DRM.
Root I use for adaway and AccA. I have found temporary alternatives for them. Instead of adaway now I use adguard and enabled optimised night charging feature of Android 11 instead of AccA.
This open beta F.10 could be the preview of final stable release as informed by Realme
"The latest Open Beta version will be chosen as the stable version and rolled out to all users,there is no difference if you have already joined the Open Beta program." Source: Realme Support Forums.
hack-os said:
~*~ Disclaimer: I'm not responsible if you destroy your device or break your warranty. Use at your own risk! ~*~
Easy way to update your Realme X2 Pro Global or India Variant from C.37 to F.10 (Android 10 to Android 11) [will lose Magisk root]
Update your Realme X2 Pro with C.37 download the file specific for your device IN/Global
Make sure the bootloader is unlocked. click here for Unlock Procedure
Boot to recovery (power off device and then hold vol- and power together)
Must check if latest OrangeFox is installed [email protected]_1.zip
Download: OrangeFox Thanks @Jerry08, @4j17h
Install RUI 2.0 Beta (F.10) with OrangeFox - Dont format anything
Download: RUI 2.0 Beta (F.10)
Do not restart to System now if you need custom recovery.
Skip this step if you dont want custom recovery
Install OrangeFox Beta img (RUI2.0) for Android 11 & select recovery partition.
Download: OrangeFox Beta RUI 2.0 for Android 11 Thanks @Jerry08, @4j17h
Install Patched vbmeta img & select vbmeta partition.
[This step is essential to have recovery persistent by not getting replaced with stock recovery and also to avoid bootloop]
Download: Patched vbmeta
[Skip this step, Only Experimental for testing]
Install Magisk Canary - Rename apk to zip and flash with USB OTG (Optional only if root is required)
Reboot to System (May take 5-7 minutes to complete booting)
Enjoy RUI 2.0 updated with all your apps and data intact.
Realme has restricted access of Data in Beta phase which means we cant access Data partition and most of files with OrangeFox.
Your standard sdcard folder having your Contents, photos, videos, files, songs etc will be accessible as you will use normally after restarting in RUI2.0.
There are couple of issues with the current RUI 2.0 Beta.
No ROOT - installing Magisk is difficult and root doesn't work
Cant safely lock bootloader
Widewine DRM L3 due to bootloader unlock
Battery,Camera, Audio performance poor
General usage and Games performance will be average.
Need to report any bugs identified in open beta phase.
Dont ask steps for Roll back to old version. Will lose all data and will be formatted when roll back.
Any issues, feel free to discuss and help out each other politely.
Click to expand...
Click to collapse
I've followed exact same instructions and I'm now stuck in boot splash. not even boot animation.
First I updated from C32 to C37 and then I updated to RUI 2.0 accordingly. But now I'm stuck in Boot splash. BL is unlocked. Followed exact same instructions. Please help me out I have some very important personal data in storage
ImperoDroider said:
I've followed exact same instructions and I'm now stuck in boot splash. not even boot animation.
First I updated from C32 to C37 and then I updated to RUI 2.0 accordingly. But now I'm stuck in Boot splash. BL is unlocked. Followed exact same instructions. Please help me out I have some very important personal data in storage
Click to expand...
Click to collapse
Fixed it!!!
Okay I think I've found the solution.
I never wanted custom recovery so I skipped flashing OFOX for RUI2 version.
But as I've mentioned above I was stuck in Realme, powered by android Spash screen and nothing more.
I have tried several things but nothing worked and then I did following steps and Voila! it worked.
1. Flashed ofox recovery for RUI 2.0 with fastboot.
2. flashed patched_vbmeta with following commad (use without quotes) "fastboot --disable-verity --disable-verification flash vbmeta patched_vbmeta.img"
3. executed "fastboot reboot" command in CMD fastboot.
Now I have a fully functional system and it took only 2 minutes for my first boot (data not wiped)
Thank you @hack-os for his amazing guide and anyone who stuck in splash like me, follow above steps and you'll be out
Hello, I am not a beta tester or part of open beta. Yesterday I just checked software update and there is no update. I just opened Realme Trail and I can see there is an optional update to RUI 2 and I said yes.
Today I got the update for RUI2 and I am from India.
ImperoDroider said:
Fixed it!!!
Okay I think I've found the solution.
I never wanted custom recovery so I skipped flashing OFOX for RUI2 version.
But as I've mentioned above I was stuck in Realme, powered by android Spash screen and nothing more.
I have tried several things but nothing worked and then I did following steps and Voila! it worked.
1. Flashed ofox recovery for RUI 2.0 with fastboot.
2. flashed patched_vbmeta with following commad (use without quotes) "fastboot --disable-verity --disable-verification flash vbmeta patched_vbmeta.img"
3. executed "fastboot reboot" command in CMD fastboot.
Now I have a fully functional system and it took only 2 minutes for my first boot (data not wiped)
Thank you @hack-os for his amazing guide and anyone who stuck in splash like me, follow above steps and you'll be out
Click to expand...
Click to collapse
Skipping custom recovery to have stock needs unpatched vbmeta. That why your boot got corrupted. Glad you fixed the issue with fastboot. The guide is mainly made to upgrade only with custom recovery and not using PC for fastboot.
You could still replace your recovery to stock recovery img in fastboot and flash RUI 2.0 A11 stock vbmeta
fastboot flash recovery stock_recovery_RUI2_A11.img
Could give it a try. Even i haven't tried this but that should work.
But I could not unlock the phone after the update. the phone became useless. all I can see on the phone screen is network icons and a strange lock symbol at the centre of the status bar on top of the screen. nothing worked, like hard reboot, wipe data in recovery but wipe data with format worked but I lost all data for which I am not ready.
finally, format the device from Recovery and could boot properly and experiencing RUI 2.0 with Android 11. there are no issues when compared to C37, it is working like a charm.
Does this work on locked bootloader and stock recovery?
Rahulfere1 said:
Does this work on locked bootloader and stock recovery?
Click to expand...
Click to collapse
you can update directly by flashing the zip given with your custom recovery.
This guide is only for unlocked bootloader and phones with orange fox as custom recovery with zip file.
satish.yarramsetti said:
But I could not unlock the phone after the update. the phone became useless. all I can see on the phone screen is network icons and a strange lock symbol at the centre of the status bar on top of the screen. nothing worked, like hard reboot, wipe data in recovery but wipe data with format worked but I lost all data for which I am not ready.
finally, format the device from Recovery and could boot properly and experiencing RUI 2.0 with Android 11. there are no issues when compared to C37, it is working like a charm.
Click to expand...
Click to collapse
Updating from c.37 to F.10 Rui 2.0 does not have any issues when the instructions are followed right. It's weired to get issues to unlock the screen after updating to Rui 2.0. Share any screenshots of the strange lock symbol if it was taken. Glad, you found a way fix your problem.
hack-os said:
Updating from c.37 to F.10 Rui 2.0 does not have any issues when the instructions are followed right. It's weired to get issues to unlock the screen after updating to Rui 2.0. Share any screenshots of the strange lock symbol if it was taken. Glad, you found a way fix your problem.
Click to expand...
Click to collapse
Yes, it is strange. I did not do it manually from xda to follow instructions. I have received the update from Realme itself and the phone became unusable after the update until I format the device.
Rahulfere1 said:
Does this work on locked bootloader and stock recovery?
Click to expand...
Click to collapse
Yes, not related to this thread. we are getting officially from realme . go to settings, software update, trail, and register. you will get it in 24 hours. not sure if slots are full. somewhere I have seen there are 50,000 slots.
satish.yarramsetti said:
Yes, not related to this thread. we are getting officially from realme . go to settings, software update, trail, and register. you will get it in 24 hours. not sure if slots are full. somewhere I have seen there are 50,000 slots.
Click to expand...
Click to collapse
You may be getting it officially in India, but European and UK users have never had the option to take part in any of the beta programs.
My big worry is that when Realme eventually decide to include Europe in the rollout of the update then there is massive potential for all of the various online banking apps etc that are specific to each European country might not work, meaning that we'll have to stay on Android 10.
satish.yarramsetti said:
Yes, not related to this thread. we are getting officially from realme . go to settings, software update, trail, and register. you will get it in 24 hours. not sure if slots are full. somewhere I have seen there are 50,000 slots.
Click to expand...
Click to collapse
Same update is done here without wait or approval
Mod machine translation:
good evening anyone please try to install the rui 2.0 firmware on the European version with locked bootloader and stock recovery? Thanks for your answers
*****************************
bonsoir quelqu'un s'il vous plaît essayez d'installer le firmware rui 2.0 sur la version européenne avec bootloader verrouillé et récupération de stock? Merci pour vos réponses
Hello there! I've loved using twrp on several of my devices over the years and tried today on my OP 8P and each version that I have tried lands me with the Qualcomm CrashDummp Mode.
I'm guessing I haven't found the right version. I have been on the latest update from OnePlus. An update today made everything weird, so I decided to go with a custom ROM thru twrp. Now I'm here!
So far I've unlocked my bootloader and tried flashing to both of my partitions.
I've tried:
twrp-3.4.0-2-instantnoodle-unified-mauronofrio
twrp-3.3.1-0-instantnoodle-unified-mauronofrio
340 Oneplus 8 pro mauronofrio
Anything else I can try flashing?
spydieee said:
Hello there! I've loved using twrp on several of my devices over the years and tried today on my OP 8P and each version that I have tried lands me with the Qualcomm CrashDummp Mode.
I'm guessing I haven't found the right version. I have been on the latest update from OnePlus. An update today made everything weird, so I decided to go with a custom ROM thru twrp. Now I'm here!
So far I've unlocked my bootloader and tried flashing to both of my partitions.
I've tried:
twrp-3.4.0-2-instantnoodle-unified-mauronofrio
twrp-3.3.1-0-instantnoodle-unified-mauronofrio
340 Oneplus 8 pro mauronofrio
Anything else I can try flashing?
Click to expand...
Click to collapse
You obviously don't read. It says next to the twrp download that its NOT compatible with Android 11
You gotta read for every ROM installations and every mods
Hi if u want to flash a custom ROM first check what type of ROM u are flashing, whether its Android 11 or 10. If u are flashing Android 10 custom ROM, when ur Oneplus 8 Pro is running Android 10, u can do it by unlocking bootloader and flashing TWRP recovery.
If u have updated ur OnePlus 8 Pro to Android 11, then u cannot flash TWRP as its incompatible. U have to unlock bootloader, install recovery image given in the ROM download page and flash the ROM via abd sideload in the recovery menu.
If ur OnePlus 8 Pro is bricked here is the unbrick tool. Download the ROM and flash it via MSM download tool by going to EDL mode.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Make sure u have the right drivers installed in ur PC.
For going to EDL mode refer this video
Then next thing: Post ur doubts or questions next time in Q&A section. Research well before u start flashing my friend. It ll be easier and smooth.
Take care.
Yep @paarry I was mislead by an article I read that has instructions for twrp be installed on a OP 8P a few months ago. I later realized that I never found anywhere else that said it was possible no matter where I searched, certainly not their official site.
Well, I fixed my problem by ceasing to try any more twrp versions and pivoting to @CarbonROM and so far it's been good.
Hello,
I tried to root my 9T(model M2010JI9SG) following this guide:
I used twrp from this link:
Xiaomi Mi 9T / Redmi K20
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
version 3.5.2_9-0
after I flashed twrp, I got into fastboot mode, which I can't leave.
I tried doing volume up +power, volume down+ power, and all the buttons as well, nothing worked, every time it goes back to fastboot,
I tried to redo everything, still didn't fix, and tried to flash stock via mi tool, didn't work too.
Please help me fix that,
Thanks!!!
Shahaf said:
Hello,
I tried to root my 9T(model M2010JI9SG) following this guide:
I used twrp from this link:
Xiaomi Mi 9T / Redmi K20
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
version 3.5.2_9-0
after I flashed twrp, I got into fastboot mode, which I can't leave.
I tried doing volume up +power, volume down+ power, and all the buttons as well, nothing worked, every time it goes back to fastboot,
I tried to redo everything, still didn't fix, and tried to flash stock via mi tool, didn't work too.
Please help me fix that,
Thanks!!!
Click to expand...
Click to collapse
OMG
You should first of all know your phone model
"Redmi 9T" reads as different name than "Mi 9T", isn't it?
Hence you MUST NEVER flash TWRP for Redmi K20/Mi 9T (guide clearly says it is for that phone, check the big picture in your post) to your Redmi 9T
oh damn, I can fix that somehow?
Shahaf said:
oh damn, I can fix that somehow?
Click to expand...
Click to collapse
Check on twrp.me is there TWRP for your Redmi 9T
Or download the so called Fastboot/TGZ ROM for your M2010JI9SG, extract recovery.img (stock Recovery) and flash it back over the wrong TWRP
For more details search on XDA for Redmi 9T subforum (this one is for Mi 9T), there should be users and freaks who can better help you for the same phone
zgfg said:
Check on twrp.me is there TWRP for your Redmi 9T
Or download the so called Fastboot/TGZ ROM for your M2010JI9SG, extract recovery.img (stock Recovery) and flash it back over the wrong TWRP
For more details search on XDA for Redmi 9T subforum (this one is for Mi 9T), there should be users and freaks who can better help you for the same phone
Click to expand...
Click to collapse
Thank you, I will check with them!
Shahaf said:
Thank you, I will check with them!
Click to expand...
Click to collapse
Here you can find firmwares for lime:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
You should (?) know what was your installed firmware, download the same Fastboot/tgz and extract (TGZ=Tar+GZIP) your original stock recovery.img, and flash it from Fastboot (just like you flashed the wrong TWRP)
You could also use MiFlash tool to flash the whole firmware, but it must be not needed
zgfg said:
Here you can find firmwares for lime:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
You should (?) know what was your installed firmware, download the same Fastboot/tgz and extract (TGZ=Tar+GZIP) your original stock recovery.img, and flash it from Fastboot (just like you flashed the wrong TWRP)
You could also use MiFlash tool to flash the whole firmware, but it must be not needed
Click to expand...
Click to collapse
It worked!!! now my device is working, now in order to root, which twrp should I use?
Shahaf said:
It worked!!! now my device is working, now in order to root, which twrp should I use?
Click to expand...
Click to collapse
You don't need TWRP. Extract boot.img (like you extracted recovery.img). Install Magisk apk and use the method Install (Magisk), then Select and patch your boot.img (do not tick Recovery option)
Find the patched img in Download folder, transfer to PC and flash from Fastboot - this time to boot partition, not to recovery partition
If anything goes wrong, flash back the stock boot img
Btw, on that Redmi 9T, do you have A12 (or A11 or what) and is it MTK chipset?
Generally, use Magisk Stable v23 from TJW:
Magisk/README.MD at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
But if A12 or MTK and if it ain't work, you can try Magisk Alpha ('pilot' builds for the new Magisk to be soon? released)
zgfg said:
You don't need TWRP. Extract boot.img (like you extracted recovery.img). Install Magisk apk and use the method Install (Magisk), then Select and patch your boot.img (do not tick Recovery option)
Find the patched img in Download folder, transfer to PC and flash from Fastboot - this time to boot partition, not to recovery partition
If anything goes wrong, flash back the stock boot img
Btw, on that Redmi 9T, do you have A12 (or A11 or what) and is it MTK chipset?
Generally, use Magisk Stable v23 from TJW:
Magisk/README.MD at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
But if A12 or MTK and if it ain't work, you can try Magisk Alpha ('pilot' builds for the new Magisk to be soon? released)
Click to expand...
Click to collapse
I tried to do it, after I patched boot.img I transfered it to my PC and did fastboot boot boot_patched.img
it did ok on sending, but then failed on booting(unknown command), any fix for that?
Flash (not boot) a healthy un-patched stock "boot.img" that is signed with your ROM version to the device and see if that works.
Shahaf said:
I tried to do it, after I patched boot.img I transfered it to my PC and did fastboot boot boot_patched.img
it did ok on sending, but then failed on booting(unknown command), any fix for that?
Click to expand...
Click to collapse
fastboot boot xxx.img boots one time to the xxx.img
For flashing (permanently) to boot you need to use:
fastboot flash boot xxx.img
Before flashing the 'stock' or patched boot img, pls double check: compare your firmware name in Settings / My device against the fastbboot/tgz package you downloaded and extracted the boot.img from
Recovery images might be the same for several firmwares, but boot.img is more critical. If extracted from the wrong firmware, it will not be your real stock boot.img and will not boot
You can use this app (now when your phone boots) to download and look for the proper firmware:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
Shahaf said:
It worked!!! now my device is working, now in order to root, which twrp should I use?
Click to expand...
Click to collapse
I would trust to the following thread on Xiaomi.eu forum, to find the suitable TWRP for your device.
Post #1, link to AFH, then scroll to lime (if that's the code name for your Redmi 9T):
[TWRP][RECOVERY] List of relevant recovery in one place
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/ I have compiled a list of relevant recovery in one place, i think it will be useful. Updates are monitored each day. Welcome, friends! How to install TWRP https://xiaomi.eu/community/threads/installing-a-custom-recovery.67841/
xiaomi.eu
Based on experience with my 9T I would pick
twrp-3.5.2_10-3-lime-brigudav.img
I.e., Xoaomi.eu provides weekly and stable firmwares that are usually well ahead of the official firmwares (on my Mi 9T, daily driver and businesses phone I was 9 months on their weeklies until I switched to their Stable two months ago)
The point is that Xiaomi.eu firmwares for most phones (I just checked, Redmi 9T is on the list) require TWRP to flash
That means if people recommend the TWRP as there, it nust be the right one
Once you have TWRP you can back up your boot partition. You will get boot.emmc.win and that will be your exact stock boot.img
You can still use the Patch and Flash method to install Magisk (as described you earlier), by patching that boot.emmc.win
zgfg said:
I would trust to the following thread on Xiaomi.eu forum, to find the suitable TWRP for your device.
Post #1, link to AFH, then scroll to lime (if that's the code name for your Redmi 9T):
[TWRP][RECOVERY] List of relevant recovery in one place
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/ I have compiled a list of relevant recovery in one place, i think it will be useful. Updates are monitored each day. Welcome, friends! How to install TWRP https://xiaomi.eu/community/threads/installing-a-custom-recovery.67841/
xiaomi.eu
Based on experience with my 9T I would pick
twrp-3.5.2_10-3-lime-brigudav.img
I.e., Xoaomi.eu provides weekly and stable firmwares that are usually well ahead of the official firmwares (on my Mi 9T, daily driver and businesses phone I was 9 months on their weeklies until I switched to their Stable two months ago)
The point is that Xiaomi.eu firmwares for most phones (I just checked, Redmi 9T is on the list) require TWRP to flash
That means if people recommend the TWRP as there, it nust be the right one
Once you have TWRP you can back up your boot partition. You will get boot.emmc.win and that will be your exact stock boot.img
You can still use the Patch and Flash method to install Magisk (as described you earlier), by patching that boot.emmc.win
Click to expand...
Click to collapse
it worked! thank you
Thank you for reading me, I am desperate, I cannot flash the oxygen os official rom by anyway.
First of all, the situation:
I have the bootloader unlocked, fastboot installed and the drivers running fine (at least that's what I think, when I type "fastboot devices" I get mine back) and I also have TWRP installed and working.
Attempts with fastbootI have tried with the fastboot image provided by mauronofrio, executing the flash-all script, it said that it was successful but it boots again in the Fastboot Mode.
I have tried flashing it manually but there are some problems while flashing some of the files
Attempt with ADBADB Sideload does not work neither
Attempt with twrpI am not able to send the rom file from my pc by any means...
I have a clue but I don't find the solution...Something similar has happened to me before, and If I am not wrong I solved it by writing the side a and b, like when installing TWRP (I am not sure 100% by if it rings a bell to someone...)
Thank you for your help
Does anybody have an idea??
Use this to get back to OOS 11.0.4.4.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Please note: Using the MSM Tool will erase all data and relock your bootloader.
Update via ota afterwards or do a local upgrade with this.
[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
If you like to make sure to have the newest OOS on both slots go here:
Install LineageOS on instantnoodlep | LineageOS Wiki
wiki.lineageos.org
xtcislove said:
Use this to get back to OOS 11.0.4.4.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Please note: Using the MSM Tool will erase all data and relock your bootloader.
Update via ota afterwards or do a local upgrade with this.
[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
If you like to make sure to have the newest OOS on both slots go here:
Install LineageOS on instantnoodlep | LineageOS Wiki
wiki.lineageos.org
Click to expand...
Click to collapse
Thank you for your reply, finally I got msmTools to recognize my phone, now is working fine.
TLDR: I need boot.img (stock or patched) for C.21
I made a huge mistake. I thought the _11 in the new version was OOS11. The upgrade window didn't indicate it was a significant upgrade.
Anyway, I was also on an old version of Magisk because I need Magisk Hide to hide root from applications required for work.
I did the usual OTA by restoring binaries in Magisk, then installing to inactive slot before reboot, but I guess due to the old MAgisk and New OOS12, it failed.
I'm now on the terrible IN2025_11_C.21 and I lost root.
I need a copy of the boot.img from C.21
I cant seem to boot into the latest TWRP (fastboot boot twrp.img) to access adb shell and extract this myself. (Should I be able to? Does TWRP still work?)
I tried downloading the OTA from here: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87101587 so I can extract boot.bin myself but payload dumper just throws an error.
I tried downloading the images from here: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87129235 but it seems I have to pay for them. Doesnt seem legit.
I was able to extract the c.21 image from the IN2021 (India) model, but I'm not sure if that's safe for my IN2025 model.
Advice? Help?
x51 said:
TLDR: I need boot.img (stock or patched) for C.21
I made a huge mistake. I thought the _11 in the new version was OOS11. The upgrade window didn't indicate it was a significant upgrade.
Anyway, I was also on an old version of Magisk because I need Magisk Hide to hide root from applications required for work.
I did the usual OTA by restoring binaries in Magisk, then installing to inactive slot before reboot, but I guess due to the old MAgisk and New OOS12, it failed.
I'm now on the terrible IN2025_11_C.21 and I lost root.
I need a copy of the boot.img from C.21
I cant seem to boot into the latest TWRP (fastboot boot twrp.img) to access adb shell and extract this myself. (Should I be able to? Does TWRP still work?)
I tried downloading the OTA from here: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87101587 so I can extract boot.bin myself but payload dumper just throws an error.
I tried downloading the images from here: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87129235 but it seems I have to pay for them. Doesnt seem legit.
I was able to extract the c.21 image from the IN2021 (India) model, but I'm not sure if that's safe for my IN2025 model.
Advice? Help?
Click to expand...
Click to collapse
There are boot images.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
AFAIK, there isn't twrp for Android 12 yet
bacon612 said:
There are boot images.
https://forum.xda-developers.com/t/guide-how-to-avoid-killing-your-oneplus-8-pr
Click to expand...
Click to collapse
http://
bacon612 said:
There are boot images.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
AFAIK, there isn't twrp for Android 12 yet
Click to expand...
Click to collapse
Thanks.
I ended up using the Indian boot.img. it worked.
x51 said:
http://
Thanks.
I ended up using the Indian boot.img. it worked.
Click to expand...
Click to collapse
I have the same problem with IN2025_ 11_C.35 no version of twrp worked for me either. Wondering if c.21 boot.ing will work
Downloaded IN2025_11_C.21 last stable in full zip from oxygen update. Payload dumpered it and fastboot booted the stock boot.img and screwed it up good, restarted thinking it'd go back to original image but no, takes a while to fire up lock screen image comes up, home screen is black. Strangely google assistant works to voice open file manager and oxygen update, downloaded IN2025_11_c.35 incremental zip but "op12 local update" doesn't see it. Twrp doesn't work so can't side load the c.35 zip to restore the boot.img. if anyone's got a IN2025_11_C.35 boot.img or any advice I'd appreciate
Orig-pinetree said:
Downloaded IN2025_11_C.21 last stable in full zip from oxygen update. Payload dumpered it and fastboot booted the stock boot.img and screwed it up good, restarted thinking it'd go back to original image but no, takes a while to fire up lock screen image comes up, home screen is black. Strangely google assistant works to voice open file manager and oxygen update, downloaded IN2025_11_c.35 incremental zip but "op12 local update" doesn't see it. Twrp doesn't work so can't side load the c.35 zip to restore the boot.img. if anyone's got a IN2025_11_C.35 boot.img or any advice I'd appreciate
Click to expand...
Click to collapse
I think boot.img corrupted the system launcher, making the settings, home screen and app drawer black or blank. Had Google assistant open a file manager and uninstalled the launcher and it came back