Hi, I just received the the Android 11 (2nd) upgrade, 11.1.1.1, and flashed the boot.img specified at the link below (since it seemed to be the same version AC01BA) to regain Magisk capabilities.
Now it is stuck in a bootloop and I have tried to reflash boot with the "stock" boot.img with no luck.
My last hope is that the boot-image in this latest release from OP have changed and that is what made my boot-image the wrong one.
So PLEASE, can anyone please lend me a hand and give me the boot.img for the latest OxygenOS EU release?
For anyone stuck in the same ditch as I was here is the short story:
The boot-image seemed to have changed between the original OxygenOS (Android 11) release and the latest named 11.1.1.1.
I downloaded the stock OS using the first link below, extracted the boot-image using the instructions on the second link below and got the boot-image uploaded to my Google Drive on the third link below, at your pleasure.
Magisk and SafetyNet verified.
(I used this stock OS NordOxygen_14.E.18_OTA_0180_all_2103112026_22699e750a6)
[Update: Rollout Resumed] OnePlus Nord stable Android 11 update pulled due to performance and stability issues
Just over a week after releasing the first stable Android 11 update for the OnePlus Nord, OnePlus has paused the rollout due to performance and stability issues.
www.xda-developers.com
How to Extract payload.bin and get stock boot image file
To extract the payload.bin file from Android stock firmware and get stock boot image file, you should refer to the instructions given in here.
www.droidwin.com
boot_11.1.1.1.img
drive.google.com
Related
i have just got op7 and i am in china ... it has hydrogen os ... where can i download oxygen os for re-branding?
PSfficial websites don't show any for op7
Hopefully it'll appear in the official website within a week or maximum by a month.
I flashed GM57BA ROM from here: https://forum.xda-developers.com/oneplus-7/how-to/oneplus-7-repo-oxygen-os-builds-t3937152
It is the EU OTA as the name suggests. It works fine for me - so far.
You can copy it to your SD and run a manual update from settings. It should update your system.
DO NOT flash the stock boot image. I lost my Wifi after I did so.
If anything goes wrong, get the Chinese stock from here as backup: https://www.h2os.com/download
Hey,
Yesterday i received the official global version of Ogygen OS 11 (OnePlus7Oxygen_14.E.35_OTA_0350_all_2103221233) for my Oneplus 7 which made me happy and i installed it on my current TWRP and root Ogygen OS 10. Afterwards my root and TWRP was gone. I read many threads now about that TWRP is not available currently for Android 11. So i was stuck with extracting the boot.img from the stock zip file and patching it with the latest canary Magisk (66e30a77 (22006)). The patch is successful.
After i flashed the boot.img to boot_a and boot_b via fastboot the phone restarted but there was still no root. (Magisk still showed that its not installed and superuser rights for Magisk also weren't granted->notification during start).
After trying and validating that i used the latest version of everything and also did a factory reset and tried the same handling again, i tried to use the latest beta Oxygen OS11 stock image for flashing the boot.img (same handling as before). After flashing i gained superuser rights and magisk was installed but no bluetooth and WIFI was working so there was an issue (is clear because it was not the same stock zip).
So does anyone of you might have already an solution for this?
Rgds,
Matthias
matthi383 said:
Hey,
Yesterday i received the official global version of Ogygen OS 11 (OnePlus7Oxygen_14.E.35_OTA_0350_all_2103221233) for my Oneplus 7 which made me happy and i installed it on my current TWRP and root Ogygen OS 10. Afterwards my root and TWRP was gone. I read many threads now about that TWRP is not available currently for Android 11. So i was stuck with extracting the boot.img from the stock zip file and patching it with the latest canary Magisk (66e30a77 (22006)). The patch is successful.
After i flashed the boot.img to boot_a and boot_b via fastboot the phone restarted but there was still no root. (Magisk still showed that its not installed and superuser rights for Magisk also weren't granted->notification during start).
After trying and validating that i used the latest version of everything and also did a factory reset and tried the same handling again, i tried to use the latest beta Oxygen OS11 stock image for flashing the boot.img (same handling as before). After flashing i gained superuser rights and magisk was installed but no bluetooth and WIFI was working so there was an issue (is clear because it was not the same stock zip).
So does anyone of you might have already an solution for this?
Rgds,
Matthias
Click to expand...
Click to collapse
Hello,
Did you see this thread right below yours?
Android 11 OB4
Just installed OB4, anybody got a boot.img file or magisk patched boot image file? Also any news on TWRP for Android 11? Thanks in anticipation OK I was just lazy hoping somebody Elese did the work. Ended up using my OB2 patched boot image file...
forum.xda-developers.com
Magisk canary can also cause a lot of issues. I'm using 22.0.
Hey thank you! I already saw this and tried it out before to get TWRP working as in the Oxygen OS 11 Beta but this TWRP version does not work with the official OOS11 for the Oneplus 7. It's strange that on Open Beta it works and now its not working.
Watching this thread because I'm stuck too. I either need locked bootloader or unlocked with Magisk
Does anyone already has a solution to this one?
I got the OTA today for 11.0.0.2, rooted fine with Magisk 22.1. Check out my guide:
https://forum.xda-developers.com/t/...m1900-android-11-oos-stable-11-0-0-2.4253743/
WareDat said:
I got the OTA today for 11.0.0.2, rooted fine with Magisk 22.1. Check out my guide:
https://forum.xda-developers.com/t/...m1900-android-11-oos-stable-11-0-0-2.4253743/
Click to expand...
Click to collapse
I wish someone would upload the fastboot ROM
Thank you man it worked ! i hope others are seeing also your intructions and files so they can use them and have root back again
Hi everyone,
I wanted to know how can i go back to OxigenOS from LineageOS 18.1. I have tried fastbooting an older version of the Lneage recovery, but in their wiki Is no longer available. Also, i have tried fastbooting the OxigenOS 11 OTA but i am receiving an error that saya "The installed kernel version Is higher than this one"(OxigenOS 11).
Any idea of what can i do?
Thanks!
This is not the thread to post your queries.
Ans to your question is there is a Fastboot flashable rom(flash.all bat file in it) flash that. Flashing it will give oos10 and update to oos11 from there.
[ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via stock recovery (with twrp is possible but not recommended). The updates will be done on the slot not used for example...
forum.xda-developers.com
Thank you, and sorry, this Is my 1st post here. About the flashable ROM, where can i find it?
Link already shared now delete this thread
So as OnePlus said we released stable OOS12 for OnePlus 7, I got a notification on Oxygen OS Updater app about the update. I was on stable channel with 11.0.3.1 and after the download was available in the app I downloaded the full build (as I was rooted and unlocked) and updated it with local upgrade from system settings. After reboot I was getting option to wipe data saying data error and rebooting to recovery everytime.
After some research it turns out that the update is for Open Beta users. I flashed this boot.img and somehow managed to switch to slot A and it booted back to OOS11. Now my slot B is not bootable with OOS12.
Is there any way I can rollback to OOS11 on slot B without any data loss?
Or is there a way I can boot into OOS12 on slot B without any data loss?
Sturdy_99 said:
So as OnePlus said we released stable OOS12 for OnePlus 7, I got a notification on Oxygen OS Updater app about the update. I was on stable channel with 11.0.3.1 and after the download was available in the app I downloaded the full build (as I was rooted and unlocked) and updated it with local upgrade from system settings. After reboot I was getting option to wipe data saying data error and rebooting to recovery everytime.
After some research it turns out that the update is for Open Beta users. I flashed this boot.img and somehow managed to switch to slot A and it booted back to OOS11. Now my slot B is not bootable with OOS12.
Is there any way I can rollback to OOS11 on slot B without any data loss?
Or is there a way I can boot into OOS12 on slot B without any data loss?
Click to expand...
Click to collapse
Hi. I am in the same position. Can I get a link to the boot.img file that you used?
The link is dead
Sturdy_99 said:
So as OnePlus said we released stable OOS12 for OnePlus 7, I got a notification on Oxygen OS Updater app about the update. I was on stable channel with 11.0.3.1 and after the download was available in the app I downloaded the full build (as I was rooted and unlocked) and updated it with local upgrade from system settings. After reboot I was getting option to wipe data saying data error and rebooting to recovery everytime.
After some research it turns out that the update is for Open Beta users. I flashed this boot.img and somehow managed to switch to slot A and it booted back to OOS11. Now my slot B is not bootable with OOS12.
Is there any way I can rollback to OOS11 on slot B without any data loss?
Or is there a way I can boot into OOS12 on slot B without any data loss?
Click to expand...
Click to collapse
Hi. So I downloaded the OS12 OTA and used a payload dumper (instructions and download here, https://www.getdroidtips.com/extract-payload-bin/) to extract the boot image and then I used fastboot to flash the boot image. It booted me into OS12 and there are no issues so far.
I've attached the boot image file that I extracted. Hope this helps
Side note, it seems like I got the issue because while on OSS11, I updated to OS12 but before I rebooted, I used Magisk to patch the boot image and then rebooted.
Heelixx said:
Hi. So I downloaded the OS12 OTA and used a payload dumper (instructions and download here, https://www.getdroidtips.com/extract-payload-bin/) to extract the boot image and then I used fastboot to flash the boot image. It booted me into OS12 and there are no issues so far.
I've attached the boot image file that I extracted. Hope this helps
Side note, it seems like I got the issue because while on OSS11, I updated to OS12 but before I rebooted, I used Magisk to patch the boot image and then rebooted.
Click to expand...
Click to collapse
Did u extract the boot.img from stable Open Beta release? Can you provide the links to oos12 ota and boot.img?
Sturdy_99 said:
Did u extract the boot.img from stable Open Beta release? Can you provide the links to oos12 ota and boot.img?
Click to expand...
Click to collapse
This is where you can find the links to the OOS12 OTA, https://www.xda-developers.com/oneplus-7-7t-pro-android-12-oxygenos-12-stable/
For some reason, I thought I uploaded the boot.img file in my previous reply but it seems not. Here's the link to download the one I extracted, https://gofile.io/d/BoqcM0
Heelixx said:
This is where you can find the links to the OOS12 OTA, https://www.xda-developers.com/oneplus-7-7t-pro-android-12-oxygenos-12-stable/
For some reason, I thought I uploaded the boot.img file in my previous reply but it seems not. Here's the link to download the one I extracted, https://gofile.io/d/BoqcM0
Click to expand...
Click to collapse
Great thats open beta, looks like many have been impacted with this. Thanks for the boot .img
Where you on stable release or open beta before upgrading?
Sturdy_99 said:
Great thats open beta, looks like many have been impacted with this. Thanks for the boot .img
Where you on stable release or open beta before upgrading?
Click to expand...
Click to collapse
I was on stable release before upgrading.
Strange that it's open beta when the headline says Stable OxygenOS 12. Oneplus is confusing people
Heelixx said:
I was on stable release before upgrading.
Strange that it's open beta when the headline says Stable OxygenOS 12. Oneplus is confusing people
Click to expand...
Click to collapse
Great, Thanks, ill give it a try.
Heelixx said:
Hi. So I downloaded the OS12 OTA and used a payload dumper (instructions and download here, https://www.getdroidtips.com/extract-payload-bin/) to extract the boot image and then I used fastboot to flash the boot image. It booted me into OS12 and there are no issues so far.
I've attached the boot image file that I extracted. Hope this helps
Side note, it seems like I got the issue because while on OSS11, I updated to OS12 but before I rebooted, I used Magisk to patch the boot image and then rebooted.
Click to expand...
Click to collapse
Does that mean, it would boot fine, if you do not install magisk before rebooting? In that case, you reinstall majgisk?
mzahs said:
Does that mean, it would boot fine, if you do not install magisk before rebooting? In that case, you reinstall majgisk?
Click to expand...
Click to collapse
So it would boot fine if I don't install magisk before rebooting.
However, I did flash the update again recently and then flashed the magisk patched boot image but I got stuck in a bootloop again. I don't know if I'm doing something wrong. So I'm without root on my phone at the moment
Hey everyone, I messed up today trying to root with Magisk using a firmware zip with a different incremental version (but same OOS version) as my device. After flashing the patched boot.img my device is stuck in a bootloop. Unable to boot into system (the text "turn off" with a progress/loading bar shown on my wallpaper), fastboot is still available.
Firmware version before flashing: IN2013_11.C.36_1360_202210310935
Firmware version that the wrong boot.img was extracted from: IN2013_11.C.36_1360_202210171428 (from this thread, under "signed flashable zips>Europe")
Magisk version: 25.2
Recovery: stock
TWRP?: no
I would rather not have to go through the MSM route/fully restore to stock firmware as I am under the impression that these will wipe my data.
I'm now looking for anyone who has the full firmware zip for OOS 12 incremental version (IN2013_11.C.36_1360_202210310935) so that I can extract the stock boot.img file myself. I'm hoping that this manages to fix my mistake.
If anyone is currently running this version and also has TWRP it would also be great if you can follow this guide to extract your boot.img directly from your device.
Another option I am looking into is to flash a stock ROM (with a different build number but the same OOS version: IN2013_11.C.36_1360_202210171428) into my inactive slot without wiping data, I'm not sure if that's wise. Does anyone know if that will work?
update:
- tried booting into older versions of IN2013 firmware using fastboot boot boot.img to no avail.
- Based on the fact that I definitely did an OTA incremental update after upgrading to OOS 12 before, maybe the boot.img was tied to the incremental update zips instead. So, I tried extracting boot.img from incremental update zips (from here, importantly did not have C.36 incremental zips yet) using the FastbootEnhance payload dumping tool, but got the error "multiple dst in one operation" and was unable to continue with this idea.
possible solutions:
1. Flash a full stock firmware to partition A and boot to that. Will this wipe my data?
2. Wait for a full stock firmware zip of IN2013_11.C.36_1360_202210310935 and extract the boot.img myself to flash.
3. Wait for an incremental update zip for C.36 to be uploaded.
4. Somehow find and transfer the stock boot.img that Magisk supposedly makes a backup of when you patch boot.img with the app.
update 2: FIXED
Tried IN2015_11.C.36_1360_202210310935 from this thread for fun. Extracted the boot.img from this one and flashed it. It somehow worked even though it's for a different version????
Doubled checked Oxygen Updater and I am indeed running OTA version IN2013_11.C.36_1360_202210310935.