Develop Bugs

Nexus 5X bricked trying to root via TWRP (SuperSu)

Hi,
Googled a while and looked around in the forum but did not find anyone with the exact same issue as me so here goes.
Maybe someone could tell me where exactly I am doing wrong.
I have a LG Nexus 5X, latest Oreo 8.1 official update.
I want to install a custom kernel to improve performance and/or battery life.
Never rooted or anything like that so I googled around to know what to do.
So I unlocked the bootloader and flashed the latest TWRP custom recovery (v3.2.1-0).
The first strange thing unlike what I kept reading in tutorials and forums is that, although I did reboot directly into recovery after flashing TWRP, and completed flashing TWRP using its interface, I was never able to reboot into TWRP unless I flashed it again. As if TWRP could not avoid being overridden by the stock recovery. So to get back to TWRP I always have to:
reboot into the bootloader: adb reboot bootloader
flash TWRP: flash recovery twrp-3.2.1-0-bullhead.img
reboot bootloader: fastboot reboot
immediately start into to bootloader (power + vol down)
choose 'Recovery Mode' from there
Which seemed odd, that TWRP wouldn't 'stick', although I was not root yet.
Which gets me to the second part. All I wanted was to root my phone.
So after not finding a consistent way to do it - it seemed every website I visited gave me slightly different instructions to do so, I took the chance and did the following:
download latest SuperSU flashable zip file (v2.82) and copy it to internal storage
go through the process I describe in the list above to get into TWRP
install SuperSU zip file (via Install TWRP option, logs seemed ok, warned me it would take a while to boot again)
reboot, wait until it boots
But the phone got stuck in the boot screen - OS does not start to load - for at least half an hour.
Luckily, probably because the OS did not load, TWRP was not overridden and so I have access to it.
My main problem at this point is that, as a newbie on this, I am not sure what can I do in TWRP to try to restore the OS.
I have tried to restore a Nandroid backup I performed before all this, and also tried to Wipe Data / Cache and Dalvik.
Both did not work - OS still won't load.
What can I do at this point? Wipe System partition? Wouldn't that delete my Nandroid backup?
Maybe 'sideload' (not sure if the right term) an official google image for my Nexus?
Sorry again if questions like this can be easily found around the forum, but from the threads I checked I did not bump into the exact same scenario...
Thank you in advance

So in the meantime I have wiped system partition, no success either.
Ended up restoring my Nandroid backup and sideloading the latest OTA from Google, which successfully restored my phone.
Of course TWRP was overridden once again.
So back to the start: can anybody help me out on the best way to permanently flash TWRP and root the phone?
Thanks!

Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)

jbaumert said:
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
Click to expand...
Click to collapse
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?

disacrol said:
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
Click to expand...
Click to collapse
Here's the guide stickied that should walk you through the TWRP install. https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
As for Magisk. There is a whole forum dedicated to it - https://forum.xda-developers.com/apps/magisk - Short story install the latest stable version (16.0) and call it good. I haven't had any issues with recent kernel builds including Franco, EX, etc.... One thing to keep in mind is that Magisk always gets flashed after the kernel install as it does some patching of the boot.img as part of its process.

jbaumert said:
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
Click to expand...
Click to collapse
Yes, flash, not boot.
Thanks a bunch for all your help. I didn't meant to be lazy to start by reading sticked topics, but it's so much new information for a newbie that I didn't exactly know where to start. Thanks again for sharing the links.

I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Click to expand...
Click to collapse
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..

disacrol said:
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
Click to expand...
Click to collapse
What version of super su are you using? Use 2.82 SR 3 or 5
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
What version of super su are you using? Use 2.82 SR 3 or 5
Click to expand...
Click to collapse
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.

disacrol said:
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
Click to expand...
Click to collapse
3 or 5 work on Oreo. I'm not sure about stable. I don't use it.
Sent from my [device_name] using XDA-Developers Legacy app

SR5 worked like a charm. I just wish there was a compatibility matrix somewhere in their website to avoid so many forum threads and misinformation on the subject and avoid all the hustle. The whole process is dead simple but it took me days and tailored help from you guys to figure this one out.
Thanks again to all of you for your assistance.

i had that issue with a nex 6 and flashing supersu fixed it. when i got a 6p i tried the same and get stuck on the boot logo and had to sideload factory firmware to get back to go. i have a 5x on the way maybe i will try magisk.

so after i flash twrp reboot the bootloader, i open twrp and flash supersu sr5 and all is well, no more disappearing act for twrp and no more stuck on the "google"?

Rooting with Android 10

My RN8P Currently has:
MIUI global 11.0.4 Stable QGGMIXM
Android 10 QP1A.190711.020
I only want to root so i can install 2-3 apps the need rooting.
I don't want to flash Roms or even have use for twrp.
Which root guide should i follow?
Do in need to Downgrade to Android pie?
will i be able to get OTA updates when rooted?

buddy the best bet for not hard/soft bricking is to downgrade to android 9 and install preloader and then root/install recovery.
if you want you can search "konah begonia guardian" on YouTube. he has quite nice guides.
regards

david_z said:
My RN8P Currently has:
MIUI global 11.0.4 Stable QGGMIXM
Android 10 QP1A.190711.020
I only want to root so i can install 2-3 apps the need rooting.
I don't want to flash Roms or even have use for twrp.
Which root guide should i follow?
Do in need to Downgrade to Android pie?
will i be able to get OTA updates when rooted?
Click to expand...
Click to collapse
FYI this device is really easy to brick that one single misstep can brick your phone and mostly the only way to restore it is via service center. So you must really pay attention to each instruction on the guides. Most root guide need to flash custom recovery first so I guess its inevitable. In order to flash custom recovery, you need to downgrade to Android 9 or Pie, more higher version than that will brick your phone.
In order to root this phone, you first need to unlock the bootloader, refer to here for the guide. (Warning, just follow the unlock bootloader guide since the flashing twrp and rooting guide from there are kinda outdated and not recommended to follow)
Then you need to flash factory firmware (preloader and lk) so you can unbrick your phone in case you brick it, refer to Megathread for guide how to do it. After that you can flash custom recovery, then you can flash magisk via custom recovery to root your phone.

This guy does a ice job explaining a simple root method for Android 10 on youtube

thanks :good:
one more thing , in all methods , after flashing twrp recovery and booting into it the guides say to delere a file called "recovery-from-boot.p".
i saw on telegram channel describing the same mathod but it also said that if i skip the deletion of that file the original recovery will remain , the phone will be rooted
and be able to OTA update.
does anyone know if its ok to do that?

I rooted from Android 10, and same with you, I only need to root to remove ads and install a few apps only.
I used this guide
https://forum.xda-developers.com/re...de-unlock-bootloader-flash-twrp-root-t3995919
Make sure that the twrp is the one that compatible with android 10, otherwise it won't boot to recovery.
Have mi flash app and android stock rom ready on your PC so that if you find problem you can always flash the stock ROM.
david_z said:
My RN8P Currently has:
MIUI global 11.0.4 Stable QGGMIXM
Android 10 QP1A.190711.020
I only want to root so i can install 2-3 apps the need rooting.
I don't want to flash Roms or even have use for twrp.
Which root guide should i follow?
Do in need to Downgrade to Android pie?
will i be able to get OTA updates when rooted?
Click to expand...
Click to collapse

gaban05 said:
I rooted from Android 10, and same with you, I only need to root to remove ads and install a few apps only.
I used this guide
https://forum.xda-developers.com/re...de-unlock-bootloader-flash-twrp-root-t3995919
Make sure that the twrp is the one that compatible with android 10, otherwise it won't boot to recovery.
Have mi flash app and android stock rom ready on your PC so that if you find problem you can always flash the stock ROM.
Click to expand...
Click to collapse
after reading a bit i think the right recovery version to root with android 10 is in the following thread:
https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695
and this is the procedure:
1. Download recovery file from this message
2. Open CMD from the dir where you store twrp.img (it's important because you don't need to type whole path of the twrp.img
3. Turn off the device, hold Power button & Vol- to enter fast boot and connect device to USB
4. In CMD type first fastboot devices to ensure that device is in fastboot, this is not important but recommended. Output should be something like this 4l6lsctgskpj4swc fastboot
5. Then it's time to flash recovery file. Type fastboot flash recovery twrp.img
6. This is the most important step now, on the device screen it should write USB Transmission ok if that is there you are ready to go. Remove device from the USB and hold Power button & Vol+, When the device turn off the screen keep holding Vol+ it'll keep screen off for about 5-10 seconds, then it'll show a recovery, still holding vol+ because it will get restarted again, and again still holding vol+ and recovery will show up. Simple words (Keep holding vol+ till recovery not appear for second time)
7. If it asks for a password, it's a password you use on the device it self(one for unlocking the screen or unlock the device after reboot), enter password and wait for Data decrypt.
At the moment there is no root and recovery will be replaced after you try to boot next time. To prevent it from replacing recovery do next (my opinion is skipping step 8. and 9. and having stock recovery because of MIUI updates):
8. Go to mount and tick the /system
9. Go back, tap on advanced, then to File Manager search for system_root dir open it, then find system and on the bottom is file called recovery-from-boot.p Remove that file and recovery wont be replaced
Now how we root it:
10. Go to advanced and tap on Close AVB2.0 and swipe to confirm
11. Go back and tap to Install ROOT, swipe to install and Reboot system
This will install Magisk v19.4, after boot you can update it from the Magisk Manager, my suggestion is to first update the manager then Magisk binary.
can anyone confirm that?

Thisnameisepic said:
This guy does a ice job explaining a simple root method for Android 10 on youtube
Click to expand...
Click to collapse
Yes it was his video I used to flash twrp to my phone,his explanation is amazing

david_z said:
after reading a bit i think the right recovery version to root with android 10 is in the following thread:
https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695
and this is the procedure:...
can anyone confirm that?
Click to expand...
Click to collapse
Yup, that worked for me on Android 10, global 11.0.5.0 QGGMIXM. The LR Team TWRP is the only one that worked for me, and I tried several.
Do make sure you download the v1210 for Android 10...
- in step 5, the 'twrp.img' you write in the command must match the actual filename you downloaded. Either change the name of the file, or enter the full filename in the command line.
- step 6 is kinda tricky. you might not get it right the first time. before installing twrp, i actually made sure i got the key combination right by going into stock recovery a few times.
When you do get TWRP up and running, the very first step is to set the language to English (unless you want Chinese). It will be the lower right buttton on the very first screen you are presented with (where you are asked for your password, if there is one).
I did not do steps 8 or 9, and TWRP has held. I did, however, reboot right back to recovery immediately after my first successful TWRP load-up. That may have stuck it.
The LR Team TWRP installed Magisk 20.3 for me. 20.4 is the latest, but I'm a little timid about letting it update. I had softbrick issues with trying to install Magisk manually thru this TWRP (instead of using the 'Install Root' button). Let me know if you update yours.
HTH

david_z said:
My RN8P Currently has:
MIUI global 11.0.4 Stable QGGMIXM
Android 10 QP1A.190711.020
I only want to root so i can install 2-3 apps the need rooting.
I don't want to flash Roms or even have use for twrp.
Which root guide should i follow?
Do in need to Downgrade to Android pie?
will i be able to get OTA updates when rooted?
Click to expand...
Click to collapse
You can go follow guide from telegram group

i tried twrp avb2.0 but it gave me bootloop after power off and on again , it's better to get the avbmeta image file from fastboot rom(same miui rom you use) and disable it from fastboot mode.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

[OP7T][Stock/Magisk] OxygenOS 11.0.2.1.HD65AA boot.img

OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://file5.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img

Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?

My computer is down so:
THANKS A MILLION!!!!!!!!!!!!!
YOU'RE SO AWESOME!!!!!!!!!!!!

Orion9k0 said:
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
Click to expand...
Click to collapse
If you are not using TWRP, follow this guide: https://forum.xda-developers.com/t/guide-how-to-root-oneplus-7t-without-twrp.3979307/

didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on

posiblyLopsided said:
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
Click to expand...
Click to collapse
Did you switch back the default OTA active slot after flashing both?

nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
i did not flash i only booted. i have tried flashing in the past with android 11 and had the same result of eternal loading. but that was a while ago and it is possible i did smth wrong.

nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
Did you remove or at the very least disable all Magisk modules before OTA updating?

i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.

posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"

kurskoo40 said:
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
Click to expand...
Click to collapse
the issue is that when i do fastboot boot magisk.img it gets stuck on the boot animation. i have to hold the power button and volume up to force it to power off then i can boot it back to the normal version

posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.

thexile said:
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
Click to expand...
Click to collapse
how would i do that? can i use my phone file manager or do i need to use adb?

posiblyLopsided said:
how would i do that? can i use my phone file manager or do i need to use adb?
Click to expand...
Click to collapse
Since you have no root access currently, you have to do so via adb in recovery mode with adb enabled.

thexile said:
Since you no root access currently, you have to do so via adb in recovery mode with adb enabled.
Click to expand...
Click to collapse
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.

posiblyLopsided said:
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
Click to expand...
Click to collapse
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.

thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
yeah looks like i learned the hard way too. also i didnt realise they released twrp for oneplus 7t. id heard that it just didnt work with android 11 but maybe im wrong. ill try it out anyways. if the twrp works that would be amazing. also thanks for all the help.

thexile said:
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://srv-store6.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Click to expand...
Click to collapse
Thanks. This worked fine. I just used local install from update, backed out without rebooting, installed magisk app and did the first reboot into bootloader, then wrote magisk modded boot image to boot a/b. It was a dirty update over the prior version.

thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
i have successfully rooted after useing twrp to remove those magisk modules.

Hi, I really need EU version of boot.img, could you please help me?
I've even looked for the full 11.0.2.1.HD65BA but with no luck.
So basically can't find anywhere both the boot.img and the full stock rom, any advice?
Thank you

Question [Latest OOS C.44 EU] Rooting via Magisk/fastboot not working

Hello all,
yesterday I've updated to latest OOS LE2123_11.C.44_1440_202201182111 (Android 12). I was previously on root, so I've updated the phone via full 4GB OTA through the system updater.
Everything was fine until I've tried to root by following these steps:
ATTENTION: if you're a Googler and willing to root the OPO 9 Pro, don't use the steps below, because they lead to a soft-bricked phone! (at least, for me)
Download the full OTA via Oxygen Updater
Extract the boot.img (192MB) via Payload Dumper (and I was confused, because the previous Android 11 boot.img was exactly the half in size)
Let the phone update itself
Throw the boot.img inside Magisk and create a patched boot.img
Flash the pathed boot image via fastboot with "fastboot flash boot Magisk_patched_blabla.img"
The phone was refusing to boot, as it was automatically booting in Fastboot mode.
So I've reflashed the patched IMG file, and the phone switched to Qualcomm Crashdump mode
Then, don't ask me how, I've managed to get it back to fastboot mode. Searched XDA for a clean and tested boot.img, understood that the boot contains 2 slots A/B, set the active boot slot to A, flashed the boot.img downloaded before, and the phone turned back to life.
So...what am I doing wrong? Maybe everything?
What are the correct steps to root the phone?
Thank you in advance

you don't have to flash the magisk_patched.img but instead boot it with : "fastboot boot magisk_patched.img"
Then you can install magisk by it's manager and reboot the phone.
Here is everything explained: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-0-0-0.4252373/

OS Update with install to inactive slot in magisk works too.

nicoilboss said:
you don't have to flash the magisk_patched.img but instead boot it with : "fastboot boot magisk_patched.img"
Then you can install magisk by it's manager and reboot the phone.
Here is everything explained: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-0-0-0.4252373/
Click to expand...
Click to collapse
I follow those steps I can get the boot and install alpha apk after it's install completed to reboot, phone gets bricked and stuck in fastboot.

Wait for the new Magisk, it's going to support Android 12.
https://twitter.com/topjohnwu/with_replies

djsubterrain said:
Wait for the new Magisk, it's going to support Android 12.
https://twitter.com/topjohnwu/with_replies
Click to expand...
Click to collapse
Missed this one...
How come some people is actually running on the rooted OOS C.44 EU? Are they using a particular version of a patched boot.img that's floating underground?

l_mike said:
OS Update with install to inactive slot in magisk works too.
Click to expand...
Click to collapse
I've clickbaited like a moron on the UPDATE/REBOOT button after OTA, and I've missed the opportunity to do it *before* rebooting the phone... then followed the steps I've posted and knocked out of the door...

xmff00 said:
Missed this one...
How come some people is actually running on the rooted OOS C.44 EU? Are they using a particular version of a patched boot.img that's floating underground?
Click to expand...
Click to collapse
Your post doesn't specify which version of magisk you're using, unless I overlooked it. If you're not using alpha already, use alpha. And make sure you also patch the boot.img with alpha and not a different version than you're trying to install. A couple of people have said canary works now (at least for C40), but I can't confirm whether it still works on C44. Stable doesn't work (yet).

terlynn4 said:
Your post doesn't specify which version of magisk you're using, unless I overlooked it. If you're not using alpha already, use alpha. And make sure you also patch the boot.img with alpha and not a different version than you're trying to install. A couple of people have said canary works now (at least for C40), but I can't confirm whether it still works on C44. Stable doesn't work (yet).
Click to expand...
Click to collapse
New stable V24 is released. Works great

nicoilboss said:
you don't have to flash the magisk_patched.img but instead boot it with : "fastboot boot magisk_patched.img"
Then you can install magisk by it's manager and reboot the phone.
Here is everything explained: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-0-0-0.4252373/
Click to expand...
Click to collapse

I've tried to use this method but when I try to flash using the 'fastboot boot magisk_boot.img' I get the error "failed - command boot not recognized"
ADB shows the 'sending' command but then nothing happens other than error mentioned above. I've tried to use both the patched and unpatched images but same error. No idea how to proceed from here

Question Rooting a T-Mobile 9 Pro on A12?

I recently got my hands on a T-Mobile 9 Pro. Fresh out of the box a couple weeks ago.
It updated to A12 a few days ago (Software Version says LE2127_11_C.16).
What are my options to root this thing? I'm relatively aware of the steps, but I don't see any temp boot images for the T-Mobile variant.
As I've seen other people mention, OEM unlocking is no longer grayed out, so that appears to be one hurdle out of the way. Right now, after reading about users having data connection issues, I'm not interested in flashing the global/EU images and I'm more than happy sticking with the T-Mobile image.

i have been trying this all day so far and all i get is either bootloop to fastboot or black screen of nothing...
i have also been trying to find the tmo a12 update on my phone where they place it before it installs. but can seem to find it even with a rooted 11.2.9.9. does ne1 know where this file is located. i want to pull it and try and get the boot.img out and try it that way..
ok we are making progress on this, i was apparently doing it the wrong way.

galaxyuser88 said:
i have been trying this all day so far and all i get is either bootloop to fastboot or black screen of nothing...
i have also been trying to find the tmo a12 update on my phone where they place it before it installs. but can seem to find it even with a rooted 11.2.9.9. does ne1 know where this file is located. i want to pull it and try and get the boot.img out and try it that way..
ok we are making progress on this, i was apparently doing it the wrong way.
Click to expand...
Click to collapse
How did you manage to get the root? I have been looking into it for a long time now and haven't been able to obtain it or should I say I'm more afraid to obtain the wrong method and ruin the phone.

NotSoSweet6626 said:
How did you manage to get the root? I have been looking into it for a long time now and haven't been able to obtain it or should I say I'm more afraid to obtain the wrong method and ruin the phone.
Click to expand...
Click to collapse
Well when I fastbooted I would flash boot instead of just boot boot.img.
Also make sure you use the correct boot.img with the same security patch version other wise you might or will have issues..
I am hoping that you have all the adb, fastboot, device drivers all set on your computer. If you do not you can search the internet to see how to setup your computer for this. You will need this to properly root your phone.
Make sure you download and have msm just in case you need it..
1. Download magisk and the magisk app to your phone and install it.
2. You have two choices here you can either pull your own stock boot.img and use magisk app on your phone to patch the img or download the correct version magisk patched boot.img from these forums.
3. Put your phone into fastboot mode
4. Open cmd prompt and Use fastboot " fastboot boot (magisk_patched_boot.img) < this is your patched boot.img".
5. Hit enter. Your computer should send the patched boot img to your phone and then your phone should reboot.
6. Once your phone boots ups, open the magisk app and then click on install. On this part you have to click direct install and then click let's go. Magisk will then root your stock boot img and will reboot.
7. After your phone reboots and you have done everything correctly you should have a rooted phone.
8. Enjoy root.
Sorry I do not have the n10 so I can not help you there.

galaxyuser88 said:
Well when I fastbooted I would flash boot instead of just boot boot.img.
Also make sure you use the correct boot.img with the same security patch version other wise you might or will have issues..
I am hoping that you have all the adb, fastboot, device drivers all set on your computer. If you do not you can search the internet to see how to setup your computer for this. You will need this to properly root your phone.
Make sure you download and have msm just in case you need it..
1. Download magisk and the magisk app to your phone and install it.
2. You have two choices here you can either pull your own stock boot.img and use magisk app on your phone to patch the img or download the correct version magisk patched boot.img from these forums.
3. Put your phone into fastboot mode
4. Open cmd prompt and Use fastboot " fastboot boot (magisk_patched_boot.img) < this is your patched boot.img".
5. Hit enter. Your computer should send the patched boot img to your phone and then your phone should reboot.
6. Once your phone boots ups, open the magisk app and then click on install. On this part you have to click direct install and then click let's go. Magisk will then root your stock boot img and will reboot.
7. After your phone reboots and you have done everything correctly you should have a rooted phone.
8. Enjoy roo
Click to expand...
Click to collapse

NishiMoon said:
Would you happen to have a copy of the Oneplus 9 (not pro) TMobile LE2117_11_C.18 Stock Boot.img?? It would be greatly and I mean greatly appreciated
Click to expand...
Click to collapse

galaxyuser88 said:
Well when I fastbooted I would flash boot instead of just boot boot.img.
Also make sure you use the correct boot.img with the same security patch version other wise you might or will have issues..
I am hoping that you have all the adb, fastboot, device drivers all set on your computer. If you do not you can search the internet to see how to setup your computer for this. You will need this to properly root your phone.
Make sure you download and have msm just in case you need it..
1. Download magisk and the magisk app to your phone and install it.
2. You have two choices here you can either pull your own stock boot.img and use magisk app on your phone to patch the img or download the correct version magisk patched boot.img from these forums.
3. Put your phone into fastboot mode
4. Open cmd prompt and Use fastboot " fastboot boot (magisk_patched_boot.img) < this is your patched boot.img".
5. Hit enter. Your computer should send the patched boot img to your phone and then your phone should reboot.
6. Once your phone boots ups, open the magisk app and then click on install. On this part you have to click direct install and then click let's go. Magisk will then root your stock boot img and will reboot.
7. After your phone reboots and you have done everything correctly you should have a rooted phone.
8. Enjoy root.
Sorry I do not have the n10 so I can not help you there.
Click to expand...
Click to collapse
Would you happen to have a copy of the Oneplus 9 (not pro) TMobile LE2117_11_C.18 Stock Boot.img?? It would be greatly and I mean greatly appreciated

NishiMoon said:
Would you happen to have a copy of the Oneplus 9 (not pro) TMobile LE2117_11_C.18 Stock Boot.img?? It would be greatly and I mean greatly appreciated
Click to expand...
Click to collapse
I will check when I get home. If I do it will prolly be the 9pro 5g one I have..

I would imagine the boot.img would be the same if not very close. I can't seem to get oppo_decrypt to extract the firmware ops file for the boot.img. I just wanna root my phone already

Rooted Stock TMO LE2127_11_C.18
After the last update that screwed up my oneplus 9 pro, I decided it was time to look at unlocking the bootloader and rooting my phone so that I could get control over these damn updates. I just want to be able to root my stock OOS so that I can...
forum.xda-developers.com
Take a look here for the c18 boot img for tmo..

galaxyuser88 said:
Rooted Stock TMO LE2127_11_C.18
After the last update that screwed up my oneplus 9 pro, I decided it was time to look at unlocking the bootloader and rooting my phone so that I could get control over these damn updates. I just want to be able to root my stock OOS so that I can...
forum.xda-developers.com
Take a look here for the c18 boot img for tmo..
Click to expand...
Click to collapse
Thank you but I ended up pulling my own boot.img for the OnePlus 9 instead of trying the OP9 Pro. I was able to pull my own boot.img then patch it, boot it, flash it. Now I'm happily rooted

LE2117.11.c18