There is a new OTA so please check that your still on may or july patch before using these:
***First and foremost I am NOT responsible for anything you do with the information posted, nor do I know how to help you unbrick your device, this is for testing purposes ONLY. If you cannot source the stock boot image for your current build/security patch wait for someone to post it and patch it yourself.****
It's always best to pull your own stock image and patch it with magisk YOURSELF. This is just to save some time for people who know exactly what their doing. If you have any doubt whatsoever DO NOT FLASH.
***Warning this MAY BRICK YOUR DEVICE IF YOUR NOT ON THE RIGHT SECURITY PATCH ***""
You will lose radios if you flash this to the wrong device, I have successfully recovered by flashing the correct boot image and have helped someone else recover with mismatching images by flashing the correct modems. I do not have the time to find the modems and troubleshoot your device so be careful please.
Flashing boot images from mismatching security patches on this device leads to no-boot and/or loss of radio functionality(cellular,wifi,Bluetooth).
The May patched boot image does NOT work for devices with the the latest security patch. Confirm that you are on the May 05, 2022 security patch BEFORE flashing MAY image. ( NOT JUNE OR JULY)
Works on build number GN2200_11_A.05
Only tested on TMOBILE variant and probably won't work for anything else(Metro apps are installed but disabled on the TMobile variant so it's possible that it MIGHT work for those devices but don't take that as any kind of reassurance that it would work***
The same boot image should work for both A and B slot but dont do anything unless you have a backup to recover from.
If you have read all the above and are 100% sure of what your doing, Flash the boot image, reboot and install magisk app as usual.
Magisk patched May boot image(should work for A/B):
magisk_boot_b.img
drive.google.com
[/URL]
here are the July (GN2200_11_A.06)Images:
Stock:
https://drive.google.com/file/d/1eALH0BxkhGPEBVSMLXfSOwp0xtySXLe4/view?usp=sharing
Magisk Patched July Image:
n20julybootmagisk.img
drive.google.com
**Edit**: According to JWhitley the images DO work for Metro by T-Mobile devices"
updated with july boot images
Darn, probably should've rooted first before updating to August patch.
PsYk0n4uT said:
updated with july boot images
Click to expand...
Click to collapse
You, kind stranger, are amazing! Thanks!
Rogo00 said:
You, kind stranger, are amazing! Thanks!
Click to expand...
Click to collapse
Flash vbmeta with
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you have issues and that should at least get you going if security checks prevent booting.
PsYk0n4uT said:
Flash vbmeta with
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you have issues and that should at least get you going if security checks prevent booting.
Click to expand...
Click to collapse
Where is the vbmeta image?
PsYk0n4uT said:
There is a new OTA so please check that your still on may or july patch before using these:
***First and foremost I am NOT responsible for anything you do with the information posted, nor do I know how to help you unbrick your device, this is for testing purposes ONLY. If you cannot source the stock boot image for your current build/security patch wait for someone to post it and patch it yourself.****
It's always best to pull your own stock image and patch it with magisk YOURSELF. This is just to save some time for people who know exactly what their doing. If you have any doubt whatsoever DO NOT FLASH.
***Warning this MAY BRICK YOUR DEVICE IF YOUR NOT ON THE RIGHT SECURITY PATCH ***""
You will lose radios if you flash this to the wrong device, I have successfully recovered by flashing the correct boot image and have helped someone else recover with mismatching images by flashing the correct modems. I do not have the time to find the modems and troubleshoot your device so be careful please.
Flashing boot images from mismatching security patches on this device leads to no-boot and/or loss of radio functionality(cellular,wifi,Bluetooth).
The May patched boot image does NOT work for devices with the the latest security patch. Confirm that you are on the May 05, 2022 security patch BEFORE flashing MAY image. ( NOT JUNE OR JULY)
Works on build number GN2200_11_A.05
Only tested on TMOBILE variant and probably won't work for anything else(Metro apps are installed but disabled on the TMobile variant so it's possible that it MIGHT work for those devices but don't take that as any kind of reassurance that it would work***
The same boot image should work for both A and B slot but dont do anything unless you have a backup to recover from.
If you have read all the above and are 100% sure of what your doing, Flash the boot image, reboot and install magisk app as usual.
Magisk patched May boot image(should work for A/B):
magisk_boot_b.img
drive.google.com
[/URL]
here are the July (GN2200_11_A.06)Images:
Stock:
https://drive.google.com/file/d/1eALH0BxkhGPEBVSMLXfSOwp0xtySXLe4/view?usp=sharing
Magisk Patched July Image:
n20julybootmagisk.img
drive.google.com
Click to expand...
Click to collapse
posting as a confirmation that the . img files provided here do play nice on the Metro by T-Mobile phone versions with currently
JWhitley said:
posting as a confirmation that the . img files provided here do play nice on the Metro by T-Mobile phone versions with currently
Click to expand...
Click to collapse
Thanks I was thinking they might since it's basically the same carrier but I didn't want to encourage anything untested
iKlover said:
Where is the vbmeta image?
Click to expand...
Click to collapse
Please see the response in the other thread
hawk1500 said:
Darn, probably should've rooted first before updating to August patch.
Click to expand...
Click to collapse
You can use DSU sideloader and boot a prerooted GSI, pull your stock images from whatever patch your on, easy way is to just use Partitions Backup and Restore app from playstore if you don't wanna use command line tools much. Install magisk and patch the extracted boot.img. save all your backups to your PC and flash the patched image in fastboot
PsYk0n4uT said:
You can use DSU sideloader and boot a prerooted GSI, pull your stock images from whatever patch your on, easy way is to just use Partitions Backup and Restore app from playstore if you don't wanna use command line tools much. Install magisk and patch the extracted boot.img. save all your backups to your PC and flash the patched image in fastboot
Click to expand...
Click to collapse
What "Partitions Backup and Restore app" are you talking about? This one? https://play.google.com/store/search?q=partitions+backup+and+restore&c=apps
famewolf said:
What "Partitions Backup and Restore app" are you talking about? This one? https://play.google.com/store/search?q=partitions+backup+and+restore&c=apps
Click to expand...
Click to collapse
yep
Related
Read before continue:
http://forums.yuplaygod.com/threads/15124/
http://forum.xda-developers.com/showpost.php?p=63197935
http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Requirements:
Completely stock, untouched device (OnePlus One).
Unlocked bootloader.
Rooted boot images:
cm-12.1-YOG7DAS2K1-bacon-boot-debuggable-rooted.img
Usage:
Download the rooted boot image that matches with your installed build.
Flash using fastboot:
Code:
fastboot flash boot XXX.img
Install the SuperUser manager app: https://play.google.com/store/apps/details?id=me.phh.superuser
Profit!
To take incremental OTA:
Download the stock boot image that matches with your installed build. Either extract from signed fastboot flashable zips or get from this thread.
Flash using fastboot:
Code:
fastboot flash boot XXX.img
You should be able to take & install the OTA, if /system isn't tampered previously.
Note:
The rooted boot images are based on official boot-debuggable images & super-bootimg by @phhusson.
The whole thing is in alpha stage & still WIP, so expect bugs.
Not all apps are compatible with systemless root approach, so root access mayn't be visible to them.
Please provide detailed feedback to me, @phhusson & the concerned app developer.
Reserved for future v1.
Reserved for future v2.
I read the second and third links, but had to sign up to get the first (not with it at this time) and I'm kinda confused. What exactly is wrong with the "old way" of rooting? Is it just for things like Android pay to work or is there other benefits?
Sent from my LG-D800 using Tapatalk
@FlashHappy78
In a nutshell, traditional rooting method modifies the /system partition. As a consequence, subsequent OTAs will fail. In case of Cyanogen OS devices, it may be easier to grab the full signed zip later & update manually, but for others they need to re-flash the stock system.img to take the OTA.
In this new approach, only the boot image is modified but /system is untouched. Thus any event/application that verifies the integrity of /system partition (like OTA, Android Pay etc.) is ready to be executed on top of the rooted device without any hitch.
If OTA contains an updated boot image, then user need to re-flash the stock boot image first which is considerably easy to re-flash than the whole system.img.
I've always been under the assumption that oem OTA updates usually break root anyways, plus patch whatever exploits were used to gain root (especially from OEM's like Samsung and LG), so because of that, I never take OTA updates unless they come from custom ROM devs.
Anyways, thanks for the clarification. I don't use android pay and I use only custom ROMs, so this probably isn't for me then. Thanks again mate.
Sent from my LG-D800 using Tapatalk
Do you have any systemless image for CM13? I tried to find a way to change the : cm-13.0-ZNH0EAS2JK-bacon-boot-debuggable.img for myself but no luck, I will have to come back to it next week.
Do you have any links to suggest?
poulopoulosa said:
Do you have any systemless image for CM13? I tried to find a way to change the : cm-13.0-ZNH0EAS2JK-bacon-boot-debuggable.img for myself but no luck, I will have to come back to it next week.
Do you have any links to suggest?
Click to expand...
Click to collapse
Flash supersu at least the stable 2.64
poulopoulosa said:
Do you have any systemless image for CM13? I tried to find a way to change the : cm-13.0-ZNH0EAS2JK-bacon-boot-debuggable.img for myself but no luck, I will have to come back to it next week.
Do you have any links to suggest?
Click to expand...
Click to collapse
As suggested by @hellcat50, I'll not provide any more update on this as newer SuperSU can patch the boot image on the fly.
Hey,
Has someone figured out how to root the phone after bootloader unlock? I saw some attempts in the GSI thread but it wolud be nice if somebody who done it publish a guide. [here or in the new thread]
This way it will be easier to find for future people to follow.
hi, i couldn't find a stock boot.img so far. seems we will have to wait some more time to be able to download latest firmware as full rom to get the boot.img, which we can then patch with magisk.
eagerly waiting for it, as i cannot hide my unlocked bootloader so far and some apps refuse to work now (also safetynet check fails)
juergenh99 said:
hi, i couldn't find a stock boot.img so far. seems we will have to wait some more time to be able to download latest firmware as full rom to get the boot.img, which we can then patch with magisk.
eagerly waiting for it, as i cannot hide my unlocked bootloader so far and some apps refuse to work now (also safetynet check fails)
Click to expand...
Click to collapse
You can use the Oxygen Updater app on google play to download the latest full rom. then use https://github.com/vm03/payload_dumper
to get the boot.img.
Manugamé said:
You can use the Oxygen Updater app on google play to download the latest full rom. then use https://github.com/vm03/payload_dumper
to get the boot.img.
Click to expand...
Click to collapse
Oxygen Updater says the Oneplus Nord 2 is not supported, and i couldn't find a Download of latest FullRom.
If you are already unlocked, download the boot image, patch with magisk etc Do you have to factory reset again?
moisthat said:
If you are already unlocked, download the boot image, patch with magisk etc Do you have to factory reset again?
Click to expand...
Click to collapse
That's the point....where and how to download the latest boot.img??
Bootloader is unlocked already.
That's why I want the latest full rom to extract it from that.
juergenh99 said:
That's the point....where and how to download the latest boot.img??
Bootloader is unlocked already.
That's why I want the latest full rom to extract it from that.
Click to expand...
Click to collapse
My reply was confusing, and I wasn't actually replying to you. Sorry about that. I don't know how or where to download the boot.img.
I am trying to ask the community if we need to factory reset again when we flash the patched boot.img. Or if the reset we did during unlock is the only reset needed.
moisthat said:
My reply was confusing, and I wasn't actually replying to you. Sorry about that. I don't know how or where to download the boot.img.
I am trying to ask the community if we need to factory reset again when we flash the patched boot.img. Or if the reset we did during unlock is the only reset needed.
Click to expand...
Click to collapse
unlocking the bootloader means to do a reset. flashing the boot.img does not cause a reset.
you just have root and working magisk after flashing and reboot
juergenh99 said:
unlocking the bootloader means to do a reset. flashing the boot.img does not cause a reset.
you just have root and working magisk after flashing and reboot
Click to expand...
Click to collapse
Well then, now I have joined you in the hunt for this bloody boot.img
HofaTheRipper said:
I am not respondible if you brick your device as there is no full rom download to revert all this.
i have done this:
- installed magisk on the phone and transfered the attached boot.img to the phone.
- patched it with magisk and transfered it to pc
Flashing:
- Unlock bootloader
- Reboot into bootloader
- Download https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
- `fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img`
- `fastboot flash boot magisk_patched_boot.img`
rebootet and root worked but wifi/bt was broken due some version conflict
Fix for wifi/bt for me was:
- unpack vendor.xz
- reboot to bootloader
- `fastboot reboot fastboot`
- `fastboot flash vendor vendor`
- reboot
My Build Version is DN2103_11_A.08.
Thanks to @phhusson for his help and for his files!
Click to expand...
Click to collapse
Found in this thread. Hope it will work for further updates.
Update 12/15/21: Magisk 23016 incorporates fixes for vbmeta header patching; disabling verity/verification is no longer necessary. Update and root should work as it always has - simply patch and flash the boot image.
Any update method can be used. If you've already disabled verity/verification, simply don't worry about it at next update; no need to re-enable.
I am closing this thread.
Spoiler: Deprecated
On Android 12, boot verification must be disabled in order to run a patched boot image. Unfortunately, if you have never disabled it before, it will require you to wipe data. To be clear:
***************************************************
PERMANENT ROOT CURRENTLY REQUIRES A DATA WIPE.
***************************************************
However, if you don't want to lose your data, you can "live boot" the patched image as long as /vbmeta and /boot are stock. This will allow you to use temporary root. DO NOT attempt to Direct Install Magisk to the boot image.
For subsequent updates, it is imperative that you do not allow the device to boot into system before you have disabled Verified Boot.
What this means: If you sideload the OTA, IMMEDIATELY reboot to bootloader and reflash /vbmeta with --disable-verity and --disable-verification. If you dirty flash the factory image, make sure you add these two switches to the command.
If you fail to do this, and allow the device to boot into system, you WILL have to wipe data to disable it again.
IF YOU ARE ROOTED, DO NOT USE AUTOMATIC UPDATES AS THIS WILL REFLASH /VBMETA WITHOUT DISABLING BOOT VERIFICATION!
Factory Images
OTA Images
Latest Magisk Canary
Spoiler: To root:
On your device, enable Developer Options (tap build number 8 times), and enable the OEM Unlocking toggle. Reboot to bootloader:
Code:
adb reboot bootloader
Unlock bootloader:
Code:
fastboot flashing unlock
Download the latest factory image and extract it. Inside, you will find the bootloader image, the radio image, and the image-device-buildnumber.zip. Extract boot.img and vbmeta.img from this zip.
Flash vbmeta:
Code:
fastboot flash vbmeta --disable-verity --disable-verification <drag and drop vbmeta.img>
Allow the device to boot into Android. Once you have Magisk installed, copy the boot.img and patch it in Magisk, then copy it back to your PC.
Reboot to bootloader.
Flash patched boot image:
Code:
fastboot flash boot <drag and drop magisk_patched-23xxx_xxxxx.img>
Reboot into system.
Spoiler: For subsequent updates:
Download the latest factory image and extract it. Inside, you will find the bootloader image, the radio image, and the image-device-buildnumber.zip. Extract boot.img from this zip.
Reboot to bootloader.
Update bootloader and radio if they are out of date. BE CAREFUL, A MISTAKE CAN BRICK YOUR DEVICE! If you update the bootloader, remember to reboot back to bootloader so that the update reads the correct bootloader version.
Update system:
Code:
fastboot update --disable-verity --disable-verification <drag and drop image-device-buildnumber.zip here>
Note: If you get an error for bootloader/radio version, this means you need to update bootloader and/or radio; go back to step 3.
Allow the device to boot into Android. Copy the boot.img and patch it in Magisk, then copy it back to your PC.
Reboot to bootloader.
Flash patched boot image:
Code:
fastboot flash boot <drag and drop magisk_patched-23xxx_xxxxx.img>
Reboot into system.
I personally do not recommend updating via OTA Sideload, as you would have to download and extract the factory zip anyway. AUTOMATIC OTA WILL LOSE ROOT AND REQUIRE A WIPE TO ROOT AGAIN.
Spoiler: If you choose to update via OTA Sideload:
Sideload the OTA. When complete, IMMEDIATELY reboot to bootloader.
Reflash vbmeta:
Code:
fastboot flash vbmeta --disable-verity --disable-verification <vbmeta.img>
Boot to system and allow the update to complete.
Patch and flash the boot image.
Note: If you run into a bootloader message
failed to load/verify boot images
this means you forgot to disable verity and verification. Reflash vbmeta with the --disable options.
If you run into this recovery message
View attachment 5455805
This means that verity and verification were not disabled before, and a wipe is required to proceed.
Let the fun begin!
Awesome news! Now that the devices are in peoples hands and this is released, development can begin!
So it looks like if you grabbed the Pixel 6 OTA yesterday, you are on 036, and that binary is not yet posted. Please correct if I am wrong. Cant wait to root this thing, non V4A audio is horrible
Just literally got my pixel 6 20 mins ago, I’m at work but when I get home the first thing I’m doing is rooting it!
For some reason I can not unlock the bootloader on the P6.
I unlocked the bootloader in the developer options.
Tried "fastboot flashing unlock" and the CMD says waiting for device.
I can transfer files from the pc to the P6 with no problems.
Maybe I need to check on an ADB driver!
EDIT: Google ADB driver was needed.
Until a Magisk hide alternative is available, what's the point in rooting for those who don't develop? Most banking apps (among others) won't work.
Not to downplay the significance of the importance of this, just asking.
XNine said:
Until a Magisk hide alternative is available, what's the point in rooting for those who don't develop? Most banking apps (among others) won't work.
Not to downplay the significance of the importance of this, just asking.
Click to expand...
Click to collapse
Geez, the firmware was just released today. Give the devs some time, there are other devices they need to update their mods on as well.
vandyman said:
Geez, the firmware was just released today. Give the devs some time, there are other devices they need to update their mods on as well.
Click to expand...
Click to collapse
Again, I was just asking what would be the benefit of rooting for a daily driver for most people (not devs), not trying to be impatient or rude. From my fairly limited understanding, Hide is pretty essential for a plethora of apps to work while rooted.
XNine said:
Again, I was just asking what would be the benefit of rooting for a daily driver for most people (not devs), not trying to be impatient or rude. From my fairly limited understanding, Hide is pretty essential for a plethora of apps to work while rooted.
Click to expand...
Click to collapse
Gotha!
When I had my Pixel 5 rooted I did not need to use hide. I use PNC Bank with no issues. I do not us Gpay, to me it is a waste of time.
I use root for AdAway, Appdash, EX Kernel, and SD Maid.
XNine said:
Until a Magisk hide alternative is available, what's the point in rooting for those who don't develop? Most banking apps (among others) won't work.
Not to downplay the significance of the importance of this, just asking.
Click to expand...
Click to collapse
Use Magisk 23001. You don't have to use 23011. I believe 23000 stable will also work as it still has MagiskHide if I'm not mistaken and works with Riru.
V0latyle said:
Use Magisk 23001. You don't have to use 23011. I believe 23000 stable will also work as it still has MagiskHide if I'm not mistaken and works with Riru.
Click to expand...
Click to collapse
You're a beautiful human being. Thank you!
XNine said:
You're a beautiful human being. Thank you!
Click to expand...
Click to collapse
My wife thinks so too, although "beautiful" isn't the word she uses
Been waiting for kernel source. Skimming through it, there's a ton of exynos named files.
XNine said:
Until a Magisk hide alternative is available, what's the point in rooting for those who don't develop? Most banking apps (among others) won't work.
Not to downplay the significance of the importance of this, just asking.
Click to expand...
Click to collapse
I’ve got an old apk of magisk so I’d assume this would work fine, no?
Also, I’ve got build number showing SD1A.210817.019.C2. Just got my 6 today and didn’t do the OTA security update as batteries to low. Will this work or nope?
DefeatedSouls said:
Also, I’ve got build number showing SD1A.210817.019.C2. Just got my 6 today and didn’t do the OTA security update as batteries to low. Will this work or nope?
Click to expand...
Click to collapse
Patch the image from the factory zip, and boot it instead of flashing it. Then, once booted, use Direct Install in Magisk to patch the boot image already on your phone.
V0latyle said:
Patch the image from the factory zip, and boot it instead of flashing it. Then, once booted, use Direct Install in Magisk to patch the boot image already on your phone.
Click to expand...
Click to collapse
Uh.. normally I’m good at this but okay, I’ll try!
XNine said:
Until a Magisk hide alternative is available, what's the point in rooting for those who don't develop? Most banking apps (among others) won't work.
Not to downplay the significance of the importance of this, just asking.
Click to expand...
Click to collapse
For instance, I need root to use Adguard in local Proxy mode and third-party VPN service. Also, I use CapitalOne, Amex, Discover, Tdbank and Chase with NO MagiskHide. There were problems with Chase, but later they probably realized it's a crap - to block rooted phones to access the app to pay your card. Some of these apps don't let you to login by a fingerprint, but it's not a big deal to enter the password (you won't forget one at least, haha)
Getting Installation failed when trying to patch the boot.img from the factory zip with Magisk.
Hello, what should I do to revert from this faulty December update? Even if I flash patched Magisk boot.img it says "device corrupted" and I can't do. I was trying to do anything with that vbmeta thing but no success maybe I'm doing something wrong.. What should I do?
You can just extract the November factory image and flash the radio.img to both slots
reas0n said:
Hello, what should I do to revert from this faulty December update? Even if I flash patched Magisk boot.img it says "device corrupted" and I can't do. I was trying to do anything with that vbmeta thing but no success maybe I'm doing something wrong.. What should I do?
Click to expand...
Click to collapse
You will have to do a full wipe to go back to an earlier firmware. Flash the full November firmware via fastboot.
Tulsadiver said:
You will have to do a full wipe to go back to an earlier firmware. Flash the full November firmware via fastboot.
Click to expand...
Click to collapse
Yes I had some issues still though, but sideloading full OTA fixed it somehow. Now I'm on Nov firmware and GSM signal is great
Thread closed at request of OP @reas0n
Long story short, I rooted my N200 T-Mobile variant to A12 DE2118_11_C.15 (Full OTA) not a long time ago with no issues. However to be able to update to DE2118_11_C.16 (Incremental update, w/July 2022 Patch) I had to uninstall Magisk first, then update it to c.16. Now my phone is updated to c.16 but I am very unsure how to root it again to avoid bootloop;
1. Can I use c.15 stock boot image since c.16 was an incremental update? or I need c.16 version?
2. If c.16 boot image is already extracted please share.
3. If none above, how and where I can find the OTA file to extract payload.bin and then boot.img?
I would really appreciate if somebody help me with this, thank you.
HTCore said:
Long story short, I rooted my N200 T-Mobile variant to A12 DE2118_11_C.15 (Full OTA) not a long time ago with no issues. However to be able to update to DE2118_11_C.16 (Incremental update, w/July 2022 Patch) I had to uninstall Magisk first, then update it to c.16. Now my phone is updated to c.16 but I am very unsure how to root it again to avoid bootloop;
1. Can I use c.15 stock boot image since c.16 was an incremental update? or I need c.16 version?
2. If c.16 boot image is already extracted please share.
3. If none above, how and where I can find the OTA file to extract payload.bin and then boot.img?
I would really appreciate if somebody help me with this, thank you.
Click to expand...
Click to collapse
The steps below is what I do since Android 12 update:
**Automatic system updates should be unchecked on Developer options.**
Prerequisites: Rooted with Magisk (v25.2 recommended) / Have stock boot image available.
Preparation:
A. Restore active slot boot img with stock boot on adb shell with root
ex) dd if=/sdcard/boot_a.img of=/dev/block/bootdevice/by-name/boot_a
OR
B. Uninstall Magisk with Restore Image option if available
--------------------------------------------------------------------------------------------------------------
**If you do A first and Direct Install with Magisk, then B option will be available.
1. Update OTA and DO NOT PRESS Restart Button.
2. Backup the new stock boot image. If your current boot is b, then new stock boot is a
ex) dd if=/dev/block/bootdevice/by-name/boot_a of=/sdcard/boot_a.img
3. Patch the newly extracted stock boot with Magisk -> Reboot -> Reboot to fastboot
4. Flash the newly magisk patched image
ex) fastboot flash boot_a new_magisk_boot.img
5. Reboot
OR you can try to install Magisk with in-active slot option at Step #3, then restart with OTA, not with Magisk; however, I've been told that it sometimes makes an issue such as bootloop. Up to you.
follow A1.1 to get your boot.img.
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
After your phone is rooted again, go in developer options and disable automatic system updates so it won't restart without your consent in future OTAs. when it asks for you to restart, go into the magisk app and press install and then "install to inactive slot". Then go back to the system update screen and press restart.
That's it. If you followed the steps correctly, your device should be updated and you should still have root!
Thank you both of you for your help and thorough explanation.
I suppose since I already restarted my device after update I have no chance with @lentm's method.
Now I'm going to follow what @justauserthatusesaphone posted and see what happens.
I will post the result here if somebody else is interested too.
HTCore said:
Thank you both of you for your help and thorough explanation.
I suppose since I already restarted my device after update I have no chance with @lentm's method.
Now I'm going to follow what @justauserthatusesaphone posted and see what happens.
I will post the result here if somebody else is interested too.
Click to expand...
Click to collapse
All you need is the stock boot img file, and here's the latest one:
11_C.16_DE18CB_tmobile_stock.7z is available for download
Click to access the 11_C.16_DE18CB_tmobile_stock.7z (35.3 MB) download with TransferNow
www.transfernow.net
Thank you for posting boot.img @lentm!
I was middle of what @justauserthatusesaphone posted when you attached the boot.img! So thank you very much being mindful of others!
However, just to learn more and be prepared for future updates I tried the other method and it worked perfectly! My device is now rooted with latest update thanks both of you guys!
Next I'm gonna use your method for another N200 which hasn't been updated yet and experience that one as well.
HTCore said:
Thank you for posting boot.img @lentm!
I was middle of what @justauserthatusesaphone posted when you attached the boot.img! So thank you very much being mindful of others!
However, just to learn more and be prepared for future updates I tried the other method and it worked perfectly! My device is now rooted with latest update thanks both of you guys!
Next I'm gonna use your method for another N200 which hasn't been updated yet and experience that one as well.
Click to expand...
Click to collapse
glad to hear you got it!
lentm's link didn't work for me so for anyone else who needs the stock image here is a non-expiring link for stock boot image for Tmobile DE2118 11_C.16:
boot_11_C.16_DE2118_tmobile_stock.img | by towardsdawn for Nord N200 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Could someone please tell me if it's possible to root this device running the latest July 5th update mentioned above without a pc ?
And if so where to find or how to do it ?!
I've been searching everywhere and have only come across a bunch of "one clock root options" that haven't worked .
Brisingrmischief said:
Could someone please tell me if it's possible to root this device running the latest July 5th update mentioned above without a pc ?
And if so where to find or how to do it ?!
I've been searching everywhere and have only come across a bunch of "one clock root options" that haven't worked .
Click to expand...
Click to collapse
One click root APKs don't have access to fastboot to flash a rooted boot.img, which is what you need to do for permanent root for newer Android devices. Also I wouldn't trust those anyway, most are not open source and might contain malware/ads/etc.
You can have a temporary root if your bootloader is unlocked by using a DSU, however if your bootloader has not been unlocked (which you need a PC to do) do NOT attempt to do this. Multiple people have reported bricking their devices attempting to do this so you have been warned.
All files on the DSU will be deleted when you discard the DSU since it is a different system image from the original. If you really know what you're doing you might be able to flash a Magisk rooted boot.img to the original system image from the DSU, I don't know how to do this. You can play around with making the DSU persist through reboots using this guide, I don't know if that works with updates or if all files will have to be discarded if you want to update. I recommend using DSU sideloader with a GSI from phhusson, when it says to run the shell script over ADB you can use a terminal app like Termux instead.
towardsdawn said:
One click root APKs don't have access to fastboot to flash a rooted boot.img, which is what you need to do for permanent root for newer Android devices. Also I wouldn't trust those anyway, most are not open source and might contain malware/ads/etc.
You can have a temporary root if your bootloader is unlocked by using a DSU, however if your bootloader has not been unlocked (which you need a PC to do) do NOT attempt to do this. Multiple people have reported bricking their devices attempting to do this so you have been warned.
All files on the DSU will be deleted when you discard the DSU since it is a different system image from the original. If you really know what you're doing you might be able to flash a Magisk rooted boot.img to the original system image from the DSU, I don't know how to do this. You can play around with making the DSU persist through reboots using this guide, I don't know if that works with updates or if all files will have to be discarded if you want to update. I recommend using DSU sideloader with a GSI from phhusson, when it says to run the shell script over ADB you can use a terminal app like Termux instead.
Click to expand...
Click to collapse
Thank you for your help !
I assume that since my bootloader is not unlocked and I don't have access to a pc I'm pretty much out of luck on rooting this device until I can get access to one .
Guess I'll have find a way to access one .
Much appreciated though !