F-18 stock Global Na op9, untouched boot. I messed up cleaning phone with Sd maid and accidentally deleted magisk backup of stock F18 img couldn't take F20 system update that came tonight. Downloaded F18 stock boot img flashed through Franco kernel manager with no reboot. Direct installed in magisk rebooted into F18 rooted and stock backup image now in place. !!! Restored stock and finally took F20 off oxygen updater. Hope this helps someone.
F-18 stock boot.img
drive.google.com
What you posted is not really a question but in the future, you can post this in this thread:
[DISCONTINUED][OOS & PA] OnePlus 9 stock/patched boot images
Now as we have TWRP for any A11-13 ROMs, there's no need for boot image patching, just flash magisk in TWRP. Hi! There's a great root guide here on xda by @zymphad and i thought i'd share the boot images for different OOS and Paranoid Android...
forum.xda-developers.com
Saying that, a copy of the NA F.18 stock boot.img is already there.
Z-Blade said:
What you posted is not really a question but in the future, you can post this in this thread:
[DISCONTINUED][OOS & PA] OnePlus 9 stock/patched boot images
Now as we have TWRP for any A11-13 ROMs, there's no need for boot image patching, just flash magisk in TWRP. Hi! There's a great root guide here on xda by @zymphad and i thought i'd share the boot images for different OOS and Paranoid Android...
forum.xda-developers.com
Saying that, a copy of the NA F.18 stock boot.img is already there.
Click to expand...
Click to collapse
This is where I obtained the compressed image. Very grateful I found. Just wanted to mainly share that I flashed stock boot through fkm and did direct install. Rebooted with backup in place and root. Took ota to f20! Thank you for original file my friend.
Related
All of the similar threads just end after a few replies (I think because people didn't have unlocked bootloaders) so I thought I'd try to ask again. I have a T-Mo OP8 (IN2017) on 10.5.22IN55CB. I already have the bootloader unlocked. But all of the root methods I can find need a payload.bin from the stock firmware, and I can't seem to find that. Is there another method or a source for branded firmware? I wasn't sure if I could do it by just booting the TWRP found on this board without flashing the recovery.
TIA.
SilverZero said:
All of the similar threads just end after a few replies (I think because people didn't have unlocked bootloaders) so I thought I'd try to ask again. I have a T-Mo OP8 (IN2017) on 10.5.22IN55CB. I already have the bootloader unlocked. But all of the root methods I can find need a payload.bin from the stock firmware, and I can't seem to find that. Is there another method or a source for branded firmware? I wasn't sure if I could do it by just booting the TWRP found on this board without flashing the recovery.
TIA.
Click to expand...
Click to collapse
I booted into TWRP and took a backup of the device. I then transferred the backup to my local PC and took the boot file from the backup, renaming the extension to .img. I then put this boot image on my device and downloaded magisk manager and set magisk manager to install magisk by patching a file. Once completed, I downloaded the patched file to my PC and booted to fastboot. While in fastboot, I flashed the magisk_patched boot image to both boot slots (boot_a, and boot_b). Upon rebooting, I had root. One thing, as soon as you have root, I recommend taking an image of your persist file (for fingerprint) to prevent any issues if the persist partition gets corrupted on your device. Search the forum for instructions on how to do this.
Cheers,
B.D.
You literally don't have to do anything special. Boot TWRP, flash Magisk zip in TWRP, reboot. Done.
stompysan said:
You literally don't have to do anything special. Boot TWRP, flash Magisk zip in TWRP, reboot. Done.
Click to expand...
Click to collapse
Works great. Thanks!
BostonDan said:
I booted into TWRP and took a backup of the device. I then transferred the backup to my local PC and took the boot file from the backup, renaming the extension to .img. I then put this boot image on my device and downloaded magisk manager and set magisk manager to install magisk by patching a file. Once completed, I downloaded the patched file to my PC and booted to fastboot. While in fastboot, I flashed the magisk_patched boot image to both boot slots (boot_a, and boot_b). Upon rebooting, I had root. One thing, as soon as you have root, I recommend taking an image of your persist file (for fingerprint) to prevent any issues if the persist partition gets corrupted on your device. Search the forum for instructions on how to do this.
Cheers,
B.D.
Click to expand...
Click to collapse
Post below yours worked for me but I appreciate the advice on backups and what to watch for. I haven't installed TWRP yet, just booted it and installed.
SilverZero said:
Works great. Thanks!
Click to expand...
Click to collapse
I should state one thing that I didn't in my original post. Booting TWRP and flashing that way ONLY works if you are still running Android 10. Since you have a T-Mobile variant, I knew this was a non-issue (we STILL don't have official A11). For those running Android 11, you do have to patch the boot image and flash it like stated above. Also note that this will likely change if we get TWRP on A11. Once we have that working, flashing Magisk from it should work fine.
stompysan said:
I should state one thing that I didn't in my original post. Booting TWRP and flashing that way ONLY works if you are still running Android 10. Since you have a T-Mobile variant, I knew this was a non-issue (we STILL don't have official A11). For those running Android 11, you do have to patch the boot image and flash it like stated above. Also note that this will likely change if we get TWRP on A11. Once we have that working, flashing Magisk from it should work fine.
Click to expand...
Click to collapse
Following up on this just in case you know anything new. My IN2017 just updated to A11 without any action on my part, and I lost root. Is there a TWRP or patched boot img that you know of for us on TMo now?
There is no working twrp for us on Android 11. I also haven't seen a patched boot image of 11.0.1.3.IN55CB around yet. I have that firmware extracted on my laptop so I could grab the boot image and patch it for you, but I won't be able to do that until later tomorrow. If no one else has it out or if you don't find it before I can get to it, I'll post it up.
Edit: Here's the patched boot image: Magisk Patched Boot IMG TMO 11.0.1.3
Hi there,
I updated to ColorOS12 and accidentely rebooted, before flashing Magisk and TWRP.
My question is now: Can flash TWRP the ususal way WITHOUT losing my data?
Bootloader is unlocked of course.
TWRP doesn't work on Android 12 and flashing Magisk with recovery isn't supported anymore anyway.
Are you actually on ColorOS or are you calling OxygenOS ColorOS? If you're on OOS, you can get patched images here (there is a guide linked in the post too).
[DISCONTINUED][OOS & PA] OnePlus 9 stock/patched boot images
Now as we have TWRP for any A11-13 ROMs, there's no need for boot image patching, just flash magisk in TWRP. Hi! There's a great root guide here on xda by @zymphad and i thought i'd share the boot images for different OOS and Paranoid Android...
forum.xda-developers.com
If you're on ColorOS, you won't be able to use these images and will have to do the patching yourself.
Root OnePlus ColorOS 12 OxygenOS Android 12 via Magisk
In this tutorial, we will show you detailed steps to root your OnePlus device running ColorOS 12 Android 12 via Magisk Patched Boot.img file.
www.droidwin.com
I thought it's ColorOS, but now as you're asking.....
LE2113_11.C.48 is Oxygen OS, right?
nonleft said:
I thought it's ColorOS, but now as you're asking.....
LE2113_11.C.48 is Oxygen OS, right?
Click to expand...
Click to collapse
Yes it is.
Ok, but flashing the boot.img only doesn't erase my data, right?
And after there is no c.48 available in the linked thread, I have to patch it on my own I guess?!
nonleft said:
Ok, but flashing the boot.img only doesn't erase my data, right?
And after there is no c.48 available in the linked thread, I have to patch it on my own I guess?!
Click to expand...
Click to collapse
Just boot the C.47 image and direct install once it's up. As long as you don't flash it, it should work to get the device up and running with root to install.
And no, flashing the boot image doesn't wipe data.
So I see a lot of people using magisk patched boot images that are really old. It'd be better to patch the image yourself from magisk and use that. The problem might be that it's not that easy to extract it.
You can find most of the stuff from stock rom extracted by me here. The files were extracted from the Indian varient. Make sure to use the appropriate files for your stock rom. The index site does have other files like some old and unstable kernels so don't go flashing everything you see from the root directory. This just started as a personal archive. The domain is free, so idk how long it'll stay active either.
As always, use everything at your own risk.
Do Magisk versions newer than v24.3 work this way?
newt23 said:
Do Magisk versions newer than v24.3 work this way?
Click to expand...
Click to collapse
Yes, patching the boot image is the recommended way to install Magisk.
The official guide does ask to patch AP wholly for samsung devices, but patching the boot image itself is faster.
Official Guide
I don't understand why I get bootloops if I update to v25.x from v24.3 from the Magisk app (using direct method). As I understand it, it also (re-)patches the boot image.
newt23 said:
I don't understand why I get bootloops if I update to v25.x from v24.3 from the Magisk app (using direct method). As I understand it, it also (re-)patches the boot image.
Click to expand...
Click to collapse
That's how I updated too. Try flashing the magisk zip directly.
Or, only update the magisk app, patch the boot image, rename it as boot.img, put it in a tar file, and then flash it to "AP" using Odin.
Hmm... this is funny. I patched the stock boot image and flashed it using Odin and still got bootloops. I took a full nandroid backup beforehand so I was able to get everything working by flashing TWRP again and restoring the previous boot image.
I get bootloops if I install v25.x from TWRP after installing a rom or update to v25.x from v24.3 directly or by patching the stock boot image. The only one that's left now is flashing v25.x zip from TWRP (while having a functioning system with v24.3) but something tells me it's going to end in bootloops too.
Hey I am on KB2003.F13 and wanted to upgrade to F15.
When I start the process by uninstalling Magisk before I download the update and then would re-install Magisk to the inactive slot to retain root I get the errror message "Stock image does not exist".
I'm imagining this is because I did not patch the stock image myself. After MSM-ing back to OOS11 and updating to OOS13 I rooted by flashing a F13 image that I found on these forums that was already patched.
What can I do? Thanks in advance
kevinco1 said:
Hey I am on KB2003.F13 and wanted to upgrade to F15.
When I start the process by uninstalling Magisk before I download the update and then would re-install Magisk to the inactive slot to retain root I get the errror message "Stock image does not exist".
I'm imagining this is because I did not patch the stock image myself. After MSM-ing back to OOS11 and updating to OOS13 I rooted by flashing a F13 image that I found on these forums that was already patched.
What can I do? Thanks in advance
Click to expand...
Click to collapse
I never add problems updating my 8T while it was rooted. I never restored the stock image before installing the update, I would just install to inactive slot before rebooting when the update finished.
Anyway, if you want to be super safe you could extract the stock boot.img from the full update package of your current version and flash it (it would be the same as restoring the stock image with Magisk). Btw I suggest you never flash images patched by others to avoid this exact problem. You can still use images from others if you want, just boot them (fastboot boot boot.img) instead of flashing them and then do a direct install with Magisk.
TheNewHEROBRINE said:
I never add problems updating my 8T while it was rooted. I never restored the stock image before installing the update, I would just install to inactive slot before rebooting when the update finished.
Anyway, if you want to be super safe you could extract the stock boot.img from the full update package of your current version and flash it (it would be the same as restoring the stock image with Magisk). Btw I suggest you never flash images patched by others to avoid this exact problem. You can still use images from others if you want, just boot them (fastboot boot boot.img) instead of flashing them and then do a direct install with Magisk.
Click to expand...
Click to collapse
So if I booted the F13 image I previously used and then did a direct install, Magisk would then make that backup IMG file and then I can proceed with the update to F15?
Or can I not boot the F13 image and do a direct install if I've already flashed it?
kevinco1 said:
So if I booted the F13 image I previously used and then did a direct install, Magisk would then make that backup IMG file and then I can proceed with the update to F15?
Or can I not boot the F13 image and do a direct install if I've already flashed it?
Click to expand...
Click to collapse
I think that Magisk backups the currently flashed boot image, so if you just boot the stock image it would backup the patched image.
kevinco1 said:
Hey I am on KB2003.F13 and wanted to upgrade to F15.
Click to expand...
Click to collapse
Update straightforward to F.62
Does anyone have stock 13.1 boot.img for OnePlus 9 na global. I carried some modules over and had to hard reset and lost backup stock img in magisk. Please and ty beforehand
This has been sorted in:
[DISCONTINUED][OOS & PA] OnePlus 9 stock/patched boot images
Now as we have TWRP for any A11-13 ROMs, there's no need for boot image patching, just flash magisk in TWRP. Hi! There's a great root guide here on xda by @zymphad and i thought i'd share the boot images for different OOS and Paranoid Android...
forum.xda-developers.com