Root any BL UNLOCKED T-Mobile/Metro OnePlus Nord with Magisk and temp root

Search This thread

bouyakasha

Senior Member
Jan 23, 2008
107
17
I'm sorry to hear that.

I had the feeling it was inevitable but I was holding out hope that there was a way to stop the updates.

I'm thinking of flashing a third-party ROM and rooting that and never updating after that if it's possible. I have no need to chase updates.

If you're using a Metro phone please let me know what solution you come up with for your phone.


.

I actually have a bunch of N100s free from work that are TM and Metro. Gave up on them because of this blocker. Can you help me figure out how to do this third-party ROM idea? I'm happy to try it. I also have no need to chase updates.
 

onlycash

Senior Member
Nov 23, 2006
133
26
I actually have a bunch of N100s free from work that are TM and Metro. Gave up on them because of this blocker. Can you help me figure out how to do this third-party ROM idea? I'm happy to try it. I also have no need to chase updates.
HI

First, let me get this out of the way when I spoke of flashing a third-party ROM I was talking about my Metro N10, not my Metro N100.

As far as I know, no one has created a ROM other than the stock for any N100.

I will say that it's very easy to root the N100 with the fastbooted TWRP and a sideloaded Magisk.zip. Once that method had been probably explained to me I found it took not much more than two or three minutes to root the N100.

I have little fear of losing root anymore with the N100.

There are two threads that I was posting in about rooting my N100. This post below pretty much explains the easy way to root the N100. If you have any questions feel free to ask.

Rooting The N100


By the way, how many N100s do you have, and are you looking to sell them?


.
 
  • Like
Reactions: bouyakasha

bouyakasha

Senior Member
Jan 23, 2008
107
17
HI

First, let me get this out of the way when I spoke of flashing a third-party ROM I was talking about my Metro N10, not my Metro N100.

As far as I know, no one has created a ROM other than the stock for any N100.

I will say that it's very easy to root the N100 with the fastbooted TWRP and a sideloaded Magisk.zip. Once that method had been probably explained to me I found it took not much more than two or three minutes to root the N100.

I have little fear of losing root anymore with the N100.

There are two threads that I was posting in about rooting my N100. This post below pretty much explains the easy way to root the N100. If you have any questions feel free to ask.

Rooting The N100


By the way, how many N100s do you have, and are you looking to sell them?


.
Thank you very much for the clarification. I'll try this on the N100s I have now. I imagine it will work on any of them?

I don't think we're looking to sell them, but thank you.

One big question I have is: Though this sideload will work with the N100s + Android11, when N100s may force updates in the future, it'll lose root without sideloading again. Right?
 

onlycash

Senior Member
Nov 23, 2006
133
26
Thank you very much for the clarification. I'll try this on the N100s I have now. I imagine it will work on any of them?

I don't think we're looking to sell them, but thank you.

One big question I have is: Though this sideload will work with the N100s + Android11, when N100s may force updates in the future, it'll lose root without sideloading again. Right?


There is a way to retain root after an OTA update. It involves settings in the Magisk app. This webpage does a far better job explaining what's going on than I can do here, I would focus on "Step 5".

Preserve Magisk Root after OTA Installation


As far as I can tell we can always fastboot the TWRP and sideload Magisk.zip and easily restore root even if it's ever lost as long as your N100 is bootloader unlocked and this TWRP is "working".

I believe there is a better working but still not perfect TWRP out there for the N100 but I haven't tried it myself and I think it's still mostly broken. I heard touch doesn't work on that other version floating around.

But in either case, this TWRP which we're fastbooting lets us easily sideload Magisk.zip so I guess we should be grateful for that.


Good luck rooting my N100s.




.
 
  • Like
Reactions: bouyakasha

Qbalaq

New member
Dec 23, 2021
4
0
Disclaimer: NOT RESPONSIBLE FOR ANY BRICKED DEVICES

YOUR DEVICE MUST HAVE AN UNLOCKED BOOTLOADER FOR THIS TO WORK

My first tutorial, gonna keep this short and sweet

1. Go to settings > About Phone > check your version number (eg 10.5.9 for mine)
2. Go to this thread and download the global zip with the corresponding number https://forum.xda-developers.com/t/...ota-oxygenos-repo-of-oxygenos-builds.4253501/
3. Use payload dumper to extract the payload.bin file in the zip (you don't have to extract the whole thing, I killed mine when I got my boot.img file)
4. Install Magisk on your device and patch the just extracted boot.img
5. Copy patched boot.img to your computer
6. Reboot into bootloader, run this command and NOTHING ELSE
fastboot boot <location of patched boot.img>
7. Now your device should be booted into a rooted state and if your wifi or cellular doesn't work, have no fear. This is only temporary and we need root for the next few steps
8. Install Partitions Backup https://www.apkmirror.com/apk/wanam/partitions-backup/partitions-backup-2-3-0-release/
9. Use that to dump boot.img from both slots to your device
10. Use Magisk to patch both boot.img files just dumped from Partitions Backup
11. Copy all dumped and patched boot.img files to your computer
12. Reboot into bootloader and fastboot boot into your newly patched boot.img files
13. If everything works, reboot back into the bootloader and flash the working patched boot.img files to both slots
14. Profit and enjoy! Tested and working on 10.5.9 for my N100, not yet tested on Android 11, do so at your own risk!

Leave a thanks if this helped you, this is for folks like me who couldn't find a backup of their OS build on the internet and needed a temp way to root their carrier devices
im lost on these steps... am i flashing these just like i did the boot.img
or am i missing something because i dont understand what you mean by boot into your newly patched files if it works flash them...

11. Copy all dumped and patched boot.img files to your computer
12. Reboot into bootloader and fastboot boot into your newly patched boot.img files
13. If everything works, reboot back into the bootloader and flash the working patched boot.img files to both slots
14. Profit and enjoy! Tested and working on 10.5.9 for my N100, not yet tested on Android 11, do so at your own risk!
 

thomaskmaagaard

Senior Member
May 15, 2014
112
19
OnePlus Nord
OnePlus Nord N100
im lost on these steps... am i flashing these just like i did the boot.img
or am i missing something because i dont understand what you mean by boot into your newly patched files if it works flash them...

11. Copy all dumped and patched boot.img files to your computer
12. Reboot into bootloader and fastboot boot into your newly patched boot.img files
13. If everything works, reboot back into the bootloader and flash the working patched boot.img files to both slots
14. Profit and enjoy! Tested and working on 10.5.9 for my N100, not yet tested on Android 11, do so at your own risk!
What exactly do you not understand?

Did you successfully patch the downloaded rom?
Did you successfully boot the rooted rom?
Did you successfully dump the boot images from your phone?
Did you successfully patch these?
 
  • Like
Reactions: luridphantom

Qbalaq

New member
Dec 23, 2021
4
0
What exactly do you not understand?

Did you successfully patch the downloaded rom?
Did you successfully boot the rooted rom?
Did you successfully dump the boot images from your phone?
Did you successfully patch these?

i did everything, im just trying to fix the wifi/network
i dont understand what im doing with the extracted boot A & B images
 

thomaskmaagaard

Senior Member
May 15, 2014
112
19
OnePlus Nord
OnePlus Nord N100
i did everything, im just trying to fix the wifi/network
i dont understand what im doing with the extracted boot A & B images
Those are the ones you need to get flashed. The point of it all was to get those so THEY can the be patched in Magisk. Then flash them with "fastboot flash boot_a PatchedBootA.img" and "fastboot flash boot_b PatchedBootB.img".
 

Qbalaq

New member
Dec 23, 2021
4
0
Those are the ones you need to get flashed. The point of it all was to get those so THEY can the be patched in Magisk. Then flash them with "fastboot flash boot_a PatchedBootA.img" and "fastboot flash boot_b PatchedBootB.img".
yeah im still lost, so i patch with magisk... and then what exactly?
how am i flashing them?
 

thomaskmaagaard

Senior Member
May 15, 2014
112
19
OnePlus Nord
OnePlus Nord N100
yeah im still lost, so i patch with magisk... and then what exactly?
how am i flashing them?
Move them to the PC and call them "boot_a.img" and "boot_b.img"

FIRST, as the steps say, IT IS RECOMMENDED that you test it first to see if it works.

This is why there's a step that says to BOOT one of them first.

To do a TEST BOOT put phone in fastboot and use:

fastboot boot boot_a.img

If your phone boots correctly and WiFi + cellular works when using this command, then you can do the flash.

Put phone in fastboot and flash them with:

fastboot flash boot_a boot_a.img

Then

fastboot flash boot_b boot_b.img

Reboot phone.
 
Last edited:
  • Like
Reactions: luridphantom

Qbalaq

New member
Dec 23, 2021
4
0
Move them to the PC and call them "boot_a.img" and "boot_b.img"

FIRST, as the steps say, IT IS RECOMMENDED that you test it first to see if it works.

This is why there's a step that says to BOOT one of them first.

To do a TEST BOOT put phone in fastboot and use:

fastboot boot boot_a.img

Now reboot.

If your phone boots correctly and WiFi + cellular works when using this command, then you can do the flash.

Put phone in fastboot and flash them with:

fastboot flash boot_a boot_a.img

Then

fastboot flash boot_b boot_b.img

Reboot phone.
got ya, i had to reroot it i got a crashdump, the first patched booted up but it didnt fix my network... im guessing it had to do with the command(s)
 

keystar23

Member
Mar 22, 2022
6
0
Disclaimer: NOT RESPONSIBLE FOR ANY BRICKED DEVICES

YOUR DEVICE MUST HAVE AN UNLOCKED BOOTLOADER FOR THIS TO WORK

My first tutorial, gonna keep this short and sweet

1. Go to settings > About Phone > check your version number (eg 10.5.9 for mine)
2. Go to this thread and download the global zip with the corresponding number https://forum.xda-developers.com/t/...ota-oxygenos-repo-of-oxygenos-builds.4253501/
3. Use payload dumper to extract the payload.bin file in the zip (you don't have to extract the whole thing, I killed mine when I got my boot.img file)
4. Install Magisk on your device and patch the just extracted boot.img
5. Copy patched boot.img to your computer
6. Reboot into bootloader, run this command and NOTHING ELSE
fastboot boot <location of patched boot.img>
7. Now your device should be booted into a rooted state and if your wifi or cellular doesn't work, have no fear. This is only temporary and we need root for the next few steps
8. Install Partitions Backup https://www.apkmirror.com/apk/wanam/partitions-backup/partitions-backup-2-3-0-release/
9. Use that to dump boot.img from both slots to your device
10. Use Magisk to patch both boot.img files just dumped from Partitions Backup
11. Copy all dumped and patched boot.img files to your computer
12. Reboot into bootloader and fastboot boot into your newly patched boot.img files
13. If everything works, reboot back into the bootloader and flash the working patched boot.img files to both slots
14. Profit and enjoy! Tested and working on 10.5.9 for my N100, not yet tested on Android 11, do so at your own risk!

Leave a thanks if this helped you, this is for folks like me who couldn't find a backup of their OS build on the internet and needed a temp way to root their carrier devices
Can you explain to me the step 9. I dont understand the 2 slots concept.....

And also once rooted , is there a way to get lineage OS or other custom ROM for this model (BE2015) , or it is not a model enough popular ?
 

onlycash

Senior Member
Nov 23, 2006
133
26
Can you explain to me the step 9. I dont understand the 2 slots concept.....

And also once rooted , is there a way to get lineage OS or other custom ROM for this model (BE2015) , or it is not a model enough popular ?

HI

I believe you're trying to Root a MetroPCS N100 (BE2015). This isn't as difficult as it seems. Keep in mind your MetroPCS N100 needs to be both SIM unlocked and bootloader unlocked before you can obtain root.


I've made a fairly easy-to-follow post that you may find helpful.





I was able to Root my Metro N100 fairly easily by just fastbooting TWRP, don't flash TWRP just fastboot boot the TWRP img.


On your PC run ADB once your phone is in the bootloader and run "fastboot boot TWRP.img"


Once you're in TWRP go to Mount and Disable MTP

Next, go to Advanced, ADB sideload

At this point, you slide the slider in TWRP to start the sideload

Go back to the PC and run this command in ADB: "adb sideload pathToMagisk.zip"

This should patch your boot.img and give you a rooted phone.

If you don't have a magisk.zip, rename magisk.apk to magisk.zip, it's best if you put the Magisk.zip in the same folder as ADB so the command is simply "adb sideload Magisk.zip


The only thing that gave me an issue was trying to do this with an old ADB, I would suggest downloading this one if you don't already have it: ADB


Good luck!
 

thomaskmaagaard

Senior Member
May 15, 2014
112
19
OnePlus Nord
OnePlus Nord N100
So I have question if anyone here can help me out...
and sorry if everyone has already moved on...

The question, I have pulled both boot.img a+b, patched and tried em out. Only Boot_a works... Do I flash that image to both a+b??? Or just a?
Well, you only need to patch the one you're currently using. I'm guessing that's A, since that's the one that works. Only this one will work since the other boot image is for the previous update. If you used a fastboot command to change current slot then you would need boot_b. Then you would boot to previous OTA update.

So just patch and flash boot_A. When you get an OTA update you have to be careful when you install it. After it has installed you should NOT reboot. Instead go to magisk manager and select "Install to inactive slot" and then reboot. Then it will patch boot_b where the new OTA is installed and boot from boot_b.

This is only necessary after installing OTA updates and if you forget to do it then you have to extract the boot image again from the new OTA and patch it.
 
  • Like
Reactions: Sayitainttone88

thomaskmaagaard

Senior Member
May 15, 2014
112
19
OnePlus Nord
OnePlus Nord N100
Any one have a boot.img for metro BE82CF 11.0?? i had finally fixed my bricked device, downgraded to 10.5... had root for maybe a week or two, and the auto update just took it away. this method of patching and temp root doesnt work for 11 i guess.
You could have just updated yourself to keep root. When you've run the update you have to remember not to reboot. First patch to inactive slot in magisk manager, then reboot.

Once you're rooted on 11 you can pull the patched boot image that's on the phone, if you want to keep it around to re-root. Although this image will only work on the same update version number.

If I were you at this point, I would just sideload through TWRP.
 
You could have just updated yourself to keep root. When you've run the update you have to remember not to reboot. First patch to inactive slot in magisk manager, then reboot.

Once you're rooted on 11 you can pull the patched boot image that's on the phone, if you want to keep it around to re-root. Although this image will only work on the same update version number.

If I were you at this point, I would just sideload through TWRP.
I was planning to but been hella busy lately...then last night when I was working my phone turned off and rebooted on its own twice. Afterwards it told me my **** was updated. Sideload what, the patched ota?
 

thomaskmaagaard

Senior Member
May 15, 2014
112
19
OnePlus Nord
OnePlus Nord N100
Sideload what, the patched ota?
Magisk zip. This method is technically depricated and I've seen some say they had problems with the latest versions. So maybe use 24.1 or 24.2. You can update it once installed.

Get it from GitHub and rename from .apk to .zip.

We've discussed this method and have steps on the TWRP thread:
HI

I was able to Root my Metro N100 fairly easily by just fastbooting TWRP, don't flash TWRP just fastboot boot the TWRP img.


On your PC run ADB once your phone is in the bootloader and run "fastboot boot TWRP.img"


Once you're in TWRP go to Mount and Disable MTP

Next, go to Advanced, ADB sideload

At this point, you slide the slider in TWRP to start the sideload

Go back to the PC and run this command in ADB: "adb sideload pathToMagisk.zip"

This should patch your boot.img and give you a rooted phone.

If you don't have a magisk.zip, rename magisk.apk to magisk.zip, it's best if you put the Magisk.zip in the same folder as ADB so the command is simply "adb sideload Magisk.zip


The only thing that gave me an issue was trying to do this with an old ADB, I would suggest downloading this one if you don't already have it: ADB


Good luck!


.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I just tried this method with N200. 11.0.2.0 is the latest good rooted boot.img I have, but 11.0.3.0 is latest update and there's no MSM.

    Anyway booting to 11.0.3.0 using the 11.0.2.0 rooted boot.img works great! Still, I tried this method and when I extract the BootA and BootB partitions and try to flash them with Magisk, Magisk tells me it's an unsupported file. This is true when I try it as tar.gz (that's how it comes from Partitions Backup) and if I rename it to *.img - either way I can't get Magisk to want to flash it. Any ideas?

    In the meantime, using the 11.0.2.0 rooted boot image seems to work fine with 11.0.3.0. So, maybe I can just go with it?

    Anyway this is an awesome guide and I learned a lot from it. HUGE THANK YOU.
    1
    I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.

    I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.
    youre not supposed to flash the global rom boot.img but boot from it, thats why it relies on a temp root. and the versions have to be exactly the same or you'll brick the device

    what version was your old device on? good luck unbricking it though, hope you get another shot at it
    1
    You're right about the flash, my mistake. Sigh.
    Versions need to be exactly the same anytime you're rooting with a boot image.
    This is version I was attempting to root: 11.0.1.BE82CB
    yea if you had booted from a magisk rooted 11.0.1 global boot.img and followed the rest of the steps you wouldve been ok because as soon as you reboot you lose root and boot from your original boot partition again

    the number 1 rule of rooting with fastboot is always boot from it and test it before flashing it. other users were warning about wifi/cell failures so i played it safe and am still fine
    1
    I just tried this method with N200. 11.0.2.0 is the latest good rooted boot.img I have, but 11.0.3.0 is latest update and there's no MSM.

    Anyway booting to 11.0.3.0 using the 11.0.2.0 rooted boot.img works great! Still, I tried this method and when I extract the BootA and BootB partitions and try to flash them with Magisk, Magisk tells me it's an unsupported file. This is true when I try it as tar.gz (that's how it comes from Partitions Backup) and if I rename it to *.img - either way I can't get Magisk to want to flash it. Any ideas?

    In the meantime, using the 11.0.2.0 rooted boot image seems to work fine with 11.0.3.0. So, maybe I can just go with it?

    Anyway this is an awesome guide and I learned a lot from it. HUGE THANK YOU.
    partitions backup compresses the dump so you cant just simply rename it. think theres an option to dump it uncompressed so you can pass it on to magisk. the other way is to untar it then pass it to magisk

    i'd just experiment a bit more as long as you remember to use fastboot boot until you get the config you want then you can flash it
    1
    partitions backup compresses the dump so you cant just simply rename it. think theres an option to dump it uncompressed so you can pass it on to magisk. the other way is to untar it then pass it to magisk

    i'd just experiment a bit more as long as you remember to use fastboot boot until you get the config you want then you can flash it
    Oh, thank you! That makes sense. I will try to UN-Tar it :)