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
Related
My IN2015 is on Oxygen OS 11.0.2.2.IN21AA and am having issues successfully rooting. I have tried multiple different tutorials, but thus far no go. Here are some notes on what I have done/tried so far.
USA
The IN2015 is carrier unlocked - I am using it on T-Mobile
My PC is on Windows 10
No problems installing adb/fastboot on the PC
Android 11
Unlocking the bootloader was not a problem and it remains unlocked. - Ok
I downloaded and unpacked the same firmware from OP and put the payload.bin file in the payload dumper and extracted the .img file.
I copied that .img file to the phone and patched it with Magisk (says All Done) w/o error.
I copied the patched .img file back to the PC.
I flashed the patched image to both a and b slots. No errors and says ok, but the time is much shorter than the video tutorials I've followed. e.g. 0.25s total vs 1.25s total. I know it's only a second, but that's an eternity in computing time. It makes me think this is where it fails.
After flashing the boot images, rebooting is successful.
But when rebooted and I go back into Magisk it says: N/A under installed.
It's interesting that Magisk says Latest: 20.4 (20400) when on the most recent tutorial it changes to 21.1 thereafter.
Manager version is 8.0.3 (314) and is installed.
Root Checker says Root access is not properly installed.
I have tried this more than a few times already with the same result. My next idea is to try and take a different image, but the You Tube tutorial is from India, so I am uncertain if using an Indian .img or even a global .img is a problem here in the US.
Any suggestions would be appreciated. Many tutorials are out of date now.
Thank you,
Falcon_73 said:
My IN2015 is on Oxygen OS 11.0.2.2.IN21AA and am having issues successfully rooting. I have tried multiple different tutorials, but thus far no go. Here are some notes on what I have done/tried so far.
USA
The IN2015 is carrier unlocked - I am using it on T-Mobile
My PC is on Windows 10
No problems installing adb/fastboot on the PC
Android 11
Unlocking the bootloader was not a problem and it remains unlocked. - Ok
I downloaded and unpacked the same firmware from OP and put the payload.bin file in the payload dumper and extracted the .img file.
I copied that .img file to the phone and patched it with Magisk (says All Done) w/o error.
I copied the patched .img file back to the PC.
I flashed the patched image to both a and b slots. No errors and says ok, but the time is much shorter than the video tutorials I've followed. e.g. 0.25s total vs 1.25s total. I know it's only a second, but that's an eternity in computing time. It makes me think this is where it fails.
After flashing the boot images, rebooting is successful.
But when rebooted and I go back into Magisk it says: N/A under installed.
It's interesting that Magisk says Latest: 20.4 (20400) when on the most recent tutorial it changes to 21.1 thereafter.
Manager version is 8.0.3 (314) and is installed.
Root Checker says Root access is not properly installed.
I have tried this more than a few times already with the same result. My next idea is to try and take a different image, but the You Tube tutorial is from India, so I am uncertain if using an Indian .img or even a global .img is a problem here in the US.
Any suggestions would be appreciated. Many tutorials are out of date now.
Thank you,
Click to expand...
Click to collapse
Try creating an apex folder in the root of your sd. It should be empty.Then do the root steps again. Happy modding!
Nathan.7118391 said:
Try creating an apex folder in the root of your sd. It should be empty.Then do the root steps again. Happy modding!
Click to expand...
Click to collapse
Thank you.
SD card? But the OP8 doesn't have a slot for one, no? I put an apex folder in the root of the internal storage but it's the same result.
Rooting was much easier on the OP6T with TWRP, but I guess that's still not supported on 11 yet.
Maybe I should try a global image.
Let me see if I can attach a few screencaps.
You are right, the internal memory. The commands are correct and it looks like no problems. I'm not sure what you mean when you say try a global image? I did the same thing you did but I'm rooted in 11.0.2.2.21AA from TMO. I pulled the OTA then placed on computer, extracted the boot image. Then I patched with magisk and ran it through fastboot. Wait, the only thing I did was got into bootloader mode. After getting into fastboot then I booted into bootloader and ran the commands.
Well, it turns out that I needed to switch to the Beta channel in Magisk (21.1) as it was still trying to patch it with an old version of Magisk (20.4), which clearly didn't work on Android 11.
It's rooted now. Thanks for your help!
Falcon_73 said:
Well, it turns out that I needed to switch to the Beta channel in Magisk (21.1) as it was still trying to patch it with an old version of Magisk (20.4), which clearly didn't work on Android 11.
It's rooted now. Thanks for your help!
Click to expand...
Click to collapse
Awesome bro. Happy modding!
Hey guys
I need your help to be happy having my phone rooted....
After update to android 11 I try to install TWRP 3.5.2 but the phone stuck on fastboot screen and TWRP not opens. So, I found an another way to root the device patching boot.img trough magisk, even it not pass on SafetyNet validation.
The root works but after reboot the phone lose it.
Some one have a solution for root on android 11?
Thanks for your help.
At the moment the TWRP in android 11 is giving problems when the mobile is encrypted does not work, you would have to make a backup and decrypt the phone to be able to use it. Any questions let me know
You need to decrypt your data and stay decrypted to get twrp working in A11.
And for the magisk part (assuming you don't wanna use twrp and stay encrypted), after booting using the patched boot image, open Magisk app, then select the Install option, then Direct Install. And that's it. You won't lose root access after reboot.
dewri21 said:
You need to decrypt your data and stay decrypted to get twrp working in A11.
And for the magisk part (assuming you don't wanna use twrp and stay encrypted), after booting using the patched boot image, open Magisk app, then select the Install option, then Direct Install. And that's it. You won't lose root access after reboot.
Click to expand...
Click to collapse
Are you referring to the patched boot.img you make yourself using Magisk? I've tried that myself, but the phone keeps being stuck at the boot logo (not a boot loop). I'm always forced to flash the original boot.img file to make the phone operational again.
Skyrider said:
Are you referring to the patched boot.img you make yourself using Magisk? I've tried that myself, but the phone keeps being stuck at the boot logo (not a boot loop). I'm always forced to flash the original boot.img file to make the phone operational again.
Click to expand...
Click to collapse
You patched the boot.img yourself? I mean did you get the proper image using payload dumper? It should have booted. Check it again and try. If that doesn't help you still, decryption is the way to go. I have been decrypted since a long time, with a working twrp.
dewri21 said:
You patched the boot.img yourself? I mean did you get the proper image using payload dumper? It should have booted. Check it again and try. If that doesn't help you still, decryption is the way to go. I have been decrypted since a long time, with a working twrp.
Click to expand...
Click to collapse
I thought TWRP wasn't/isn't fully supported on Android 11?
And yes, I used the proper proper image as I grabbed the entire package using Oxygen Updater, while using the patched version to update the OS. And if I didn't get the proper image, I would assume reverting back to the original boot.img (from the full package) wouldn't have worked.
Skyrider said:
I thought TWRP wasn't/isn't fully supported on Android 11?
And yes, I used the proper proper image as I grabbed the entire package using Oxygen Updater, while using the patched version to update the OS. And if I didn't get the proper image, I would assume reverting back to the original boot.img (from the full package) wouldn't have worked.
Click to expand...
Click to collapse
I found working patched boot at OnePlus forum, I guess it was patched with canary version of magisk. Maybe you can try.
Skyrider said:
I thought TWRP wasn't/isn't fully supported on Android 11?
Click to expand...
Click to collapse
It is, if and only if you're decrypted. TWRP doesn't support encryption on A11.
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Than
Click to expand...
Click to collapse
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
Click to expand...
Click to collapse
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
hammered58 said:
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
Click to expand...
Click to collapse
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
¿GotJazz? said:
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
Click to expand...
Click to collapse
1. Yes that is the app Iam talking about.
2. Will you lose data? I always do a format (after the down grade) so I lost data but I never tried it with out formating, it might work, you could try it and see what happens .If it acts strange then it will need a format.
3. Yes you install 11.04 via twrp
4. Yes you will get root but if you want twrp you will have to reinstall
Once you down grade install the oxygen updater, let it download the update , don't let it install it, you can then grab the update from your root directory as it doesn't hide it, then your good to go, you can extract the boot.img by using payload dumper, then take the boot.img and patch that with the magisk app . ( Just install the magisk app on your downgraded 11.04 you don't need root to run the app ) ,,Then after your thru upgrading to 11.05 and after setup just reboot to bootloader and run the magisk patched boot.img, ( fastboot flash boot boot.img) reboot and wait a minute for the magisk app to appear ,it will want to install and do a reboot . Then you can install twrp if you want.
This is how I did it and it worked, you may find a simpler way once you start doing it ,, hth
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
¿GotJazz? said:
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
Click to expand...
Click to collapse
Right now I have 11.05 installed and Iam rooted, tomorrow I will unroot and downgrade to 11.04 without wiping and let you know what happens iam curious myself
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
¿GotJazz? said:
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
Click to expand...
Click to collapse
I guess that's possible , I never thought of that, the only way to know is to do a fresh install only this time setup encryption then try to install magisk . But for now your rooted,, until the bug hits you or me to try another rom then we can start the whole thing over again,,
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