Database Users

CM11S official & untouched image collection

2014.10.16.: Update!
MICa.fighter said:
Hy guys! As you might noticed, the links in the OP which are pointing to the official files on the CM server don't work any more thanks to CM. I was sure this will come, but i still wanted to use the official links as long as they are working. I would change the links to my mirrors in the OP, but @Spannaa already made mirrors in his thread: Mirrors for official CM11S roms & OTA updates. I don't see any reason to have 2 threads with mirrors of the same files, so i taught I would keep this thread as a discussion on how to use those official files. I will modify the OP in the coming days accordingly.
Click to expand...
Click to collapse
I will keep the OP as it is for now, and I will modify it a little in the coming days!
Hy guys, i have seen posts about different versions of CM11S, but I haven't seen a collection of them. I collect all the stock images i can, so i taught i would share it with you guys. As the thread title says, these are official and untouched images of the stock CM11S. I share the official links where it is available. I will share four kind of files:
1. Recovery flashable zips of the complete ROMz: these are the oldschool .zip images that you can flash through recovery.
2. Fastboot images of the complete ROMz: these are fastboot.zip files, that should be used through fastboot. You need to set up Android SDK for fastboot on your computer and you also need to unlock your phone's bootloader in order to use them. For setting up the Android SDK and unlocking your bootloader, please follow this guide: [GUIDE] OnePlus One - How to Unlock Bootloader, Install Custom Recovery and Root, until you complete the first step: 1. Unlocking Bootloader. After that you have to put the fastboot.zip file into your platform-tools folder (its explained in the previous link), and extract it there, but also keep the zip there because you need that too. After that, you may follow the instructions of the Open Post of this thread: CyanogenMod 11S.
Note: The conventional fastboot oem unlock which unlocks the bootloader will wipe your phone. You can make backup before that with Helium app or through adb. Neither of them requires root.
Note: The last command in the CyanogenMod 11S thread's open post is:
Code:
fastboot update -w cm-11.0-XNPH25R-bacon-signed-fastboot.zip
The command will wipe your phone because of the "-w" option.
Note: if you get the error message during flashing in fastboot:
Code:
FAILED (remote: data too large)
Then you are probably not on the latest Android SDK with the latest required tools: Android SDK Tools, Android SDK Platform-tools, Android Support Library, Google USB Driver.
Click to expand...
Click to collapse
3. Stock kernel images: these are .img files of the stock kernel images. You can flash these in fastboot like this:
Code:
fastboot flash boot boot.img
If the filename is for example g7389215.img then it looks like this:
Code:
fastboot flash boot g7389215.img
4. Latest OTA incremental update zip: I will also share the latest OTA zip file. The CM11S OTAs are incremental updates, that means you need to be on the latest version before applying an update. Incremental means it only updates the changed files since the last update.
So for example the latest OTA ATM is XNPH33R. Before that was the XNPH30O. If you want to use the XNPH33R OTA zip you need to be on XNPH30O, because that is the latest version before the XNPH33R OTA (check reference table below). If you apply the OTA on an earlier version (for example, XNHP25R), the installation will be aborted most probably. Or if you succeed with the installation, it will break stuff most probably.
You can also grab the latest OTA update zip after you recieved the OTA file and downloaded it. You can find it in the cache of your phone and you will need root access. If you want to make a copy you should do so before you install the OTA.
Wipe the cache then you can flash the OTA update zip through recovery.
Reference table
ROM version / release date / kernel version
XNPH22R / 2014.06.06. / dunno
XNPH25R / 2014.07.03. / geb9c0a5
XNPH30O / 2014.08.11. / g7389215
XNPH33R / 2014.08.21. / g0ad30e5
XNPH38R / 2014.10.07. / g33fa374
Links
1. Recovery flashable zips of the complete ROMz:
XNPH22R
XNPH25R
XNPH33R
2. Fastboot images of the complete ROMz:
XNPH22R
XNPH25R
XNPH30O
XNPH33R
XNPH38R
3. Stock kernel images:
XNPH22R
XNPH25R
XNPH30O
XNPH33R
XNPH38R / torrent magnet mirror
4. Latest OTA incremental update zip:
XNPH38R
Also here are the previous OTA incremental update zips:
same rule, check reference table, only use it if you are on the latest previous version! Its incremental.
XNPH33R
XNPH30O
Njoy!
You might also be interested in zephiK's modem collection of recovery flashable zips for the One: http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734

Thanks was waiting for something like this.

While I appreciate this, the 33R Kernel isn't working... I tried flashing with fastboot and no go.... I'm on 33R from OTA. I'm rooted and I currently have Franco Kernel installed... (And TWRP recovery)
To reiterate, it flashes fine but when I go to boot up it stays at the One+ logo screen

How did you try it exactly?

MICa.fighter said:
How did you try it exactly?
Click to expand...
Click to collapse
flashing with adb through fastboot

You can use rashr app https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools works like a charm

Nomelas said:
While I appreciate this, the 33R Kernel isn't working... I tried flashing with fastboot and no go.... I'm on 33R from OTA. I'm rooted and I currently have Franco Kernel installed... (And TWRP recovery)
To reiterate, it flashes fine but when I go to boot up it stays at the One+ logo screen
Click to expand...
Click to collapse
You are right, the file is broken, I'm sorry. I'm going to update the OP soon with working kernel image. I'm also going to share the latest OTA grabbed from cache.
Edit: updated OP with the new 33R links, and fixed the broken kernel image. I also explained how to use the kernel images.

Thank you so much

Great post op :good:
Waiting the recovery flashable zip of XNPH33R to download. ( I am currently on XNPH22R, unlocked bootloader, with TWRP)
I am going to flash the zip through recovery ( and then flash modem from zephiK's post).
I don't need to do anything with the kernel images ( I am guessing they are there for another reason), right?

mhxmhx said:
I don't need to do anything with the kernel images ( I am guessing they are there for another reason), right?
Click to expand...
Click to collapse
You don't need the kernel images.
All the rom zip files has a kernel (boot.img). The reason i posted the kernel images separately too because custom kernel users sometimes need them. If they want to go back to stock kernel or just want to keep a backup, they don't need to download ~460MB for just the kernel image, they can download only the kernel image which is 5-10 MB.

Thank you for your work!

Thanks a lot, after flashing few mods and custom kernel my phone feels laggy, I must go back to stock

After @zephiK modem list, this is one more most usefull thread Thanks !!

So could I just flash the 33r update from stock recovery if I'm on 25r? Or do I need to update to 30O then 33r

Added to OnePlus One Resources Compilation Roll-Up Thread
[INDEX]OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon

jherring002 said:
So could I just flash the 33r update from stock recovery if I'm on 25r? Or do I need to update to 30O then 33r
Click to expand...
Click to collapse
The OTA Update is incremental, which means it only updates the files that changed from the last update, in this case XNPH30O. So you sould NOT try to flash the OTA Update of 33R if you are not on 30O.
If you want to update to 33R from 25R, there are a couple of options, for example:
A) update to 30O through OTA, then you can just flash the 33R OTA update, OR
B) download the 33R full rom zip, reboot to recovery, wipe cache and flash away OR
C) make a backup of your apps and settings, through adb, or Titanium Backup, or with Helium (TB requires root), then download the 33R fastboot.zip and flash through fastboot as described in the first post. If you already have the bootloader unlocked you can skip that step. After you are done, boot up the phone, then restore your backup. The flashing method described in the open post of CyanogenMod 11S thread will wipe your phone.
The "safest" method is A, the "cleanest" method is C.
timmaaa said:
Added to OnePlus One Resources Compilation Roll-Up Thread
[INDEX]OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
Click to expand...
Click to collapse
I'm out of thanks so i thank you here timmaaa :good:

Is there a flashable 30O file via recovery?

jherring002 said:
Is there a flashable 30O file via recovery?
Click to expand...
Click to collapse
Unfortunately no, but I can upload the 30O original OTA zip for you i grabbed that from cache too. You can flash it on 25R after a cache wipe. Or use it with the 25R recovery flashable zip: flash 25R zip then 30O OTA zip.

MICa.fighter said:
Unfortunately no, but I can upload the 30O original OTA zip for you i grabbed that from cache too. You can flash it on 25R after a cache wipe.
Click to expand...
Click to collapse
That would be nice. I went from 33r to 25r to see the difference in battery.
It's not that different so I wanted to go back, but when I check for ota there is not one. Says in up to date.

jherring002 said:
That would be nice. I went from 33r to 25r to see the difference in battery.
It's not that different so I wanted to go back, but when I check for ota there is not one. Says in up to date.
Click to expand...
Click to collapse
Okay I'm gonna upload the 30O OTA zip too, it will be available in the first post in a few minitues. If you want to go back to 33R you could also use the 33R full rom zip, just wipe cache and you can flash it on 25R. Make a backup before it, but i don't think there would be any problem.
Edit: Done!

[Guide][Zenfone 2]Flash Custom ROM in Unlocked Android 6.0

**All credit to @shakalaca for his dedication. Also thanks to Enjie in Taiwan Asus Zentalk forum.
**Do it at your risk
This guide is to help you flash custom rom, like CM 13, in unlocked Android 6.0.
The point of this thread is to pack signature files into TWRP and boot.img so that we can boot from custom roms.
This thread won't be needed if TWRP/Custom Rom patch into MM the signature file in the future. For now, sorry for the mess.
1.Add signature to TWRP
a. Download your favorite twrp. The latest official twrp is doable.
b.Download and unzip the attached file: recovery_z00a.sig
c.Copy the above 2 files in the same directory.
d.Activate cmd window in your pc (window button + R, type cmd, Enter)
e.Add signature to TWRP in cmd window: (Suppose you put all files in c:\) , replace <twrp.img> with your TWRP file name.
Code:
cd c:\
copy /b <twrp.img> + recovery_z00a.sig recovery_mod.img
Now you will see a new file, recovery_mod.img created.
2.Add signature to boot.img
a. Unzip and extract boot.img from custom rom.
b. Download and unzip the attached file: boot_z00a.sig
c.Copy the above 2 files in the same directory.
d.Activate cmd window in your pc (window button + R, type cmd, Enter)
e.Add signature to boot.img in cmd window: (Suppose you put all files in c:\)
Code:
cd c:\
copy /b boot.img + boot_z00a.sig boot_mod.img
Now you will see a new file, boot_mod.img created.
3.Unlock MM6.0.
Refer to this thread. This is a 2 click unlock procedure. The device should be unlocked before we can flash twrp and custom rom.
4. After the device is unlocked, in bootloader, flash TWRP recovery now:
Code:
fastboot flash recovery recovery_mod.img
5. Boot from TWRP
6. Flash custom rom from TWRP
7. After done flashing custom rom in TWRP, flash boot_mod.img from TWRP.
Or, from bootloader:
Code:
fastboot flash boot boot_mod.img
8.Reboot system.
*My suggestion is to put the revised kernel in SD card. Later on If you upgrade custom rom, it is easier to flash the repacked boot_mod.img again in TWRP.

god bless you

Thanks But is there any way I can add the signature in kernel and recovery in android without pc. Can I use those commands in android terminal?

Thanks,man

pless support Z008

MrPhamHpGYC said:
pless support Z008
Click to expand...
Click to collapse
Z008 files

Any other easy method for noob like me please..
Sent from my ASUS_Z008 using XDA-Developers mobile app

kjinx01 said:
Any other easy method for noob like me please..
Sent from my ASUS_Z008 using XDA-Developers mobile app
Click to expand...
Click to collapse
It won't be easy unless TWRP and Custorm Roms patch the signature files with them. Maybe we should wait after ASUS roll out its official release.

i try step by step and its work , i flash blurOS on my marshmallow based zenfone . thanks for your hardwork mate

Thanks a lot!!! I already wanted to throw this damn Z00A against the next wall, since neither 5.0 nor 6.0 were working flawlessly. But CM13 is fantastic! Best rom so far. Will never go back to stock.

delete

which rom do i use? can i use cm13 to get the boot.img file

Guys, I want to root my Z00A (MM beta -- .111 build). Is there a way without unlocking the bootloader?
Also I want to know whether the Asus official bootunlocker tool can be used in this MM .111 build so that I can flash CM13 instead.
Thanks in advance.

rohithramesh96 said:
Guys, I want to root my Z00A (MM beta -- .111 build). Is there a way without unlocking the bootloader?
Also I want to know whether the Asus official bootunlocker tool can be used in this MM .111 build so that I can flash CM13 instead.
Thanks in advance.
Click to expand...
Click to collapse
Try this.
http://forum.xda-developers.com/zenfone2/general/android-6-0-beta-root-xposed-downgrade-t3404321

Hi. where I can find more modern sig keys? I make custom kernel for marshmallow and use old ramdisk from 4.21.40.61 firmware. If I take ramdisk from boot.img from newer firmware and tnen pack back into boot.img, then to sign boot.img, device can't start. I suppose the reason of this- incompatible key?

Hi,
How could I manually sign these files on Ubuntu-based OS? I'm no longer use Windows as my daily OS. Thanks.
Also: Could anyone provide MM final signature keys?
Sent from my ASUS_Z00A using XDA Labs

krasCGQ said:
Also: Could anyone provide MM final signature keys?
Click to expand...
Click to collapse
yes, I get it and use it for sign my lastest kernels. for recovery sign you may use old keys, it compatible

Hi guys , my zf2 is unlocked and rooted ( MM stock .134 )
Is possible sign stock boot.img and stock recovery.img for pass the verification on boot ??

siteswap said:
Hi guys , my zf2 is unlocked and rooted ( MM stock .134 )
Is possible sign stock boot.img and stock recovery.img for pass the verification on boot ??
Click to expand...
Click to collapse
That's what I want to know. And, I want to know too if there is any ota for the marshmallow, and want to flash it, the bootloader needs to be relocked or not? And, dont need to un- systemless root+xposed, right?
Someone who uses MM beta before and succesfully flash ota with unlocked bootloader + systemless root and xposed can you confirm me please?
Sent from my ASUS_Z00A using Tapatalk

I used MM beta, and after that i update to MM ( .134 ) official Fw , and my bootloader was locked.
For unlock+root i used shakalaka metod in xda index.
At moment the last ota that you can find is .134 in Asus site , but i dont know if in future the new ota will relock bootloader

Install Magisk without permanent TWRP - is it possible?

I just finished reading a thread on another Redmi forum, here on XDA, about rooting a Redmi S2 without permanent TWRP flash.
Do you think it's possible to successfully apply the same steps on MIUI 11 Global Stable Redmi 7A (using the proper boot.img)?
Things needed :
- Unlocked Bootloader
- PC with ADB and Fastboot installed
- boot.img of your miui rom. You can grab it (open with winRar) from fastboot firmware (.tgz) xiaomi redmi S2. Download the firmware file in xiaomi site or in this section thread. The version are reccomended to be the same as your current miui version.
- Magisk Manager.apk
1. Open Magisk Manager
2. Press Install > Install > Patch Boot Image File, and select your boot.img file
3. Magisk Manager will now patch your boot image, and store it in Internal Storage/Download/patched_boot.img
4. Copy the patched boot image to your PC. Place it in Minimal ADB & Fastboot directory.
5. Flash the patched boot image to your device. Here is the command :
fastboot flash boot boot.img
6. If adb say "Okay" twice, mean it succesfully.
Type : fastboot reboot
7. Wait your phone to reboot.
From here:
https://forum.xda-developers.com/redmi-s2/how-to/magisk-root-custom-recovery-t3863402

cris2d2 said:
I just finished reading a thread on another Redmi forum, here on XDA, about rooting a Redmi S2 without permanent TWRP flash.
Do you think it's possible to successfully apply the same steps on MIUI 11 Global Stable Redmi 7A (using the proper boot.img)?
Things needed :
- Unlocked Bootloader
- PC with ADB and Fastboot installed
- boot.img of your miui rom. You can grab it (open with winRar) from fastboot firmware (.tgz) xiaomi redmi S2. Download the firmware file in xiaomi site or in this section thread. The version are reccomended to be the same as your current miui version.
- Magisk Manager.apk
1. Open Magisk Manager
2. Press Install > Install > Patch Boot Image File, and select your boot.img file
3. Magisk Manager will now patch your boot image, and store it in Internal Storage/Download/patched_boot.img
4. Copy the patched boot image to your PC. Place it in Minimal ADB & Fastboot directory.
5. Flash the patched boot image to your device. Here is the command :
fastboot flash boot boot.img
6. If adb say "Okay" twice, mean it succesfully.
Type : fastboot reboot
7. Wait your phone to reboot.
From here:
https://forum.xda-developers.com/redmi-s2/how-to/magisk-root-custom-recovery-t3863402
Click to expand...
Click to collapse
but what would that help you with? having the normal recovery?

mike500005 said:
but what would that help you with? having the normal recovery?
Click to expand...
Click to collapse
I just want Root capabilities, I don't want to replace stock Global Stable MIUI.

cris2d2 said:
I just want Root capabilities, I don't want to replace stock Global Stable MIUI.
Click to expand...
Click to collapse
yes i understand but what would be the goal? what you dont like or are afraid that you dont want the recovery is it because OTA updates? or??? you can try to root it and then reflash the stock recovery.img and apply a patched boot image could work idnk cause i have already done a lot to get mine working with latest update and i don't really want to go threw all the backups again

cris2d2 said:
I just want Root capabilities, I don't want to replace stock Global Stable MIUI.
Click to expand...
Click to collapse
custom recovey doesn't replace rom

indeed what you descripe is the official and recommended root method. TWRP is just for nandroid backup (not really needed since Migrate Backup and Magisk Modules can flash straight from android without TWRP at all), therefore the Magisk.zip is just for traditional reasons. Many devices don't even have TWRP (or with no working encryption support)
Installation
The Magic Mask for Android
topjohnwu.github.io
We no longer recommend installing Magisk through custom recoveries on modern devices. The custom recovery installation method exists mostly for legacy support
Click to expand...
Click to collapse

[Guide] Root US OnePlus 8T KB2005 Unlocked

We have root!
All you have to do is follow these few steps and have a working adb / fastboot installation
1 Download this patched boot image -
https://www.androidfilehost.com/?fid=10763459528675569219
2. Reboot your phone to the bootloader
Code:
adb reboot bootloader
3. Boot from the patched image
Code:
fastboot boot magisk_patched.img
4. Make sure you have the latest Magisk Manager Canary and do a direct install to patch your internal boot image on both slots.
Latest Magisk Manager -> https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
Done!
It seems like a lot of people are still having issues. If this doesn't work for you, then my boot image is slightly different than yours. You can follow the steps from this post to pull your stock boot image. After you do that you can just patch your stock image with Magisk Canary. Pull the patched image from your phone and use it in step 3 above.
Special thanks to SAKO4444GODZ for pulling the stock boot img first

Reserved

Reserved 2

northmendo said:
I started this to share information and files in order to get root on the KB2005 US Unlocked 8T. I have tried the boot images from the other variations with no luck. So, lets discuss and get this thing rooted.
Click to expand...
Click to collapse
Maybe we can flash an older firmware? I currently can't because the system update app doesn't have the local update option.

Over here just patiently waiting for an ota. dont even want to put my sim in it from my oneplus 6t until I get root

dreisus said:
Over here just patiently waiting for an ota. dont even want to put my sim in it from my oneplus 6t until I get root
Click to expand...
Click to collapse
I got a download from OnePlus Updater. They just updated to support the 8T. I haven't got my payload dumper working yet. Heres the download if anyone wants to try it.
https://www.androidfilehost.com/?fid=10763459528675568207

Possible Extraction method from phone
When I boot from the 2001 boot.img, it doesn't get to the system ui, but I do have ADB access and su is available. Normally it would say that su could not be found, but now it waits for authorization (which I can't give because system UI won't display and the screen is blank). If we can make magisk auto accept su from shell we can get the 2005 boot.img. Difficult but worth a shot.

northmendo said:
I got a download from OnePlus Updater. They just updated to support the 8T. I haven't got my payload dumper working yet. Heres the download if anyone wants to try it.
https://www.androidfilehost.com/?fid=10763459528675568207
Click to expand...
Click to collapse
Downloaded it and got the boot.img but it says Unsupported/Unkown img format when I try to patch the boot.img
This is my first time using the unloader but it extracted everything fine from what I can tell. It's just the boot img that fails in Magisk when trying to patch.
Anyone else seeing this?

MNoisy said:
Downloaded it and got the boot.img but it says Unsupported/Unkown img format when I try to patch the boot.img
This is my first time using the unloader but it extracted everything fine from what I can tell. It's just the boot img that fails in Magisk when trying to patch.
Anyone else seeing this?
Click to expand...
Click to collapse
That zip is only 350MB so it won't contain a proper boot.img. You need to extract it from a full sized OTA zip which is around 3GB. So far there's no link to KB2005 full OTA zip yet.

zellleonhart said:
That zip is only 350MB so it won't contain a proper boot.img. You need to extract it from a full sized OTA zip which is around 3GB. So far there's no link to KB2005 full OTA zip yet.
Click to expand...
Click to collapse
Thanks for confirming!

I have done a full msm tool readback of the device, patched boot img, flashed and there is am encryption issue. Booted or flashed after a long boot up, it starts up plays the boot animation, then as it completes, the screen goes black. Only way out of it if it was flashed and not booted is flash unpatched boot, format and then reboot. It cannot be rooted at this time. I am compiling a kernel with kernel assisted root built in to see if that will circumvent the issue for root at least while on stock.
My device is kebab 2005 model too

Just flashed patched recovery - success
I decided to take the risk and flashed the patched recovery from the EU 2003 version, it worked and I have root adb shell. I'm about to extract the 'boot.img'.
---------- Post added at 11:54 PM ---------- Previous post was at 11:32 PM ----------
SAKO4444GODZ said:
I decided to take the risk and flashed the patched recovery from the EU 2003 version, it worked and I have root adb shell. I'm about to extract the 'boot.img'.
Click to expand...
Click to collapse
Stock boot.img should be attached in a zip file
checksums for the .img (after extraction, not the zip)
MD5: d6615931724d901956c8d855af75c1c0
SHA1: 01e699edec71dea408420b1aaed6e5bbdf6a9eb3
SHA256: 2f58564817ff189177e135fcee92a5070100aaa26529bbfafbdcf34e149ee998
SHA512: 2a579411ca054488b6114d9efb5f36e2a52bc6114775f33913b33a8ff0a29af71dbf5e8bb8d632a359cb489ebb146764e515e73c8140007791f42bdfc4c3a07b

Uploaded the zip correctly, it didn't upload last time, sorry.
SAKO4444GODZ said:
I decided to take the risk and flashed the patched recovery from the EU 2003 version, it worked and I have root adb shell. I'm about to extract the 'boot.img'.
---------- Post added at 11:54 PM ---------- Previous post was at 11:32 PM ----------
Stock boot.img should be attached in a zip file
checksums for the .img (after extraction, not the zip)
MD5: d6615931724d901956c8d855af75c1c0
SHA1: 01e699edec71dea408420b1aaed6e5bbdf6a9eb3
SHA256: 2f58564817ff189177e135fcee92a5070100aaa26529bbfafbdcf34e149ee998
SHA512: 2a579411ca054488b6114d9efb5f36e2a52bc6114775f33913b33a8ff0a29af71dbf5e8bb8d632a359cb489ebb146764e515e73c8140007791f42bdfc4c3a07b
Click to expand...
Click to collapse
Uploaded the zip correctly, it didn't upload last time, sorry.

SAKO4444GODZ said:
Uploaded the zip correctly, it didn't upload last time, sorry.
Click to expand...
Click to collapse
Could you upload it somewhere else? I'm getting a 404 when attempting to download it.

TheUnkn0wn said:
Could you upload it somewhere else? I'm getting a 404 when attempting to download it.
Click to expand...
Click to collapse
I also get a 404, weird, I can't submit links yet, so any suggestions?

SAKO4444GODZ said:
I decided to take the risk and flashed the patched recovery from the EU 2003 version, it worked and I have root adb shell. I'm about to extract the 'boot.img'.
Click to expand...
Click to collapse
Funny I tried this too
Didn't work

Here's a semi-broken TWRP that allows su access through adb: https://drive.google.com/file/d/1dRXJj7HZcqlNsHlVcNH0qR3sNx_uBA__
DO NOT FLASH, ONLY USE WITH BOOT COMMAND!
Code:
fastboot boot recovery.img
adb shell
dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img
dd if=/dev/block/by-name/boot_b of=/sdcard/boot_b.img
exit
adb pull /sdcard/boot_a.img boot_a.img
adb pull /sdcard/boot_b.img boot_b.img
I borked my boot_a by flashing it with boot_b (boot_b was broken on my device), so I was unable to obtain a working boot_a.img. If someone could kindly share their KB2005 boot_a.img that would be nice.

Thanks to @ SAKO4444GODZ and his extracted boot.img!! I patched it and now have working root. I'll update the front page.

https://i.imgur.com/pynYfD4.jpg success
---------- Post added at 12:28 AM ---------- Previous post was at 12:25 AM ----------
Oh, I can post links now? Here is the patched boot.img for US_2005
https://drive.google.com/file/d/1V_wI8dl4SulMst4G-yMcPQsjFFs8j_Ns/view?usp=sharing
SHA 512: 1e54faef40c104a3e93545fef821e3c94abb90e8eea56f1ee402705e54607b3b038ef614d16c91865daee2df1ac02134202a7e4061f05af312ead39b7732c7e4

Awesome!

IN2025_11_C.21 Root / Boot.img Help

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