Question Rooting T-Mobile A12 DE2118_11_C.16 (July 2022 patch) - OnePlus Nord N200 5G

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 !

Related

[Alpha][Systemless Root][bacon] Rooted Boot Images

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.

Possibly dense question about OEM unlock and magisk flash

EDIT: On a V30 H930 if that matters.
Coming from an S7 Edge and a Jelly Pro (which was fairly open) so my understanding of how LG does things may be off.
If I just want Magisk - not interested in TWRP/custom roms etc.
Can I:
- enable OEM unlock in developer settings (device is encrypted etc)
- use magisk manager to generate a new boot.img
- use fastboot to flash this e.g. fastboot flash boot patched_boot.img
Or am I missing something? (Probably!)
molotov_sh said:
EDIT: On a V30 H930 if that matters.
Coming from an S7 Edge and a Jelly Pro (which was fairly open) so my understanding of how LG does things may be off.
If I just want Magisk - not interested in TWRP/custom roms etc.
Can I:
- enable OEM unlock in developer settings (device is encrypted etc)
- use magisk manager to generate a new boot.img
- use fastboot to flash this e.g. fastboot flash boot patched_boot.img
Or am I missing something? (Probably!)
Click to expand...
Click to collapse
EDIT:
See post #7 below for root on this phone without TWRP.
For root for this phone WITH TWRP, see this post.
ChazzMatt said:
No, what you said won't work. See this thread below.
You need TWRP to root, by the way.
https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500
Click to expand...
Click to collapse
You don't need TWRP to root (some) other phones with Magisk, hence my original probing question. Originally when I did some poking around this forum I couldn't tell if some of the hackery being used was specifically for network locked phones or for some custom rom needs.
It looks like the subtlety here is that LG doesn't really unlock when you choose OEM unlock, it just lets you then request unlocking from them (or the trick you've linked). What a right pain in the behind.
Thanks for the pointer.
molotov_sh said:
You don't need TWRP to root (some) other phones with Magisk, hence my original probing question. Originally when I did some poking around this forum I couldn't tell if some of the hackery being used was specifically for network locked phones or for some custom rom needs.
It looks like the subtlety here is that LG doesn't really unlock when you choose OEM unlock, it just lets you then request unlocking from them (or the trick you've linked). What a right pain in the behind.
Thanks for the pointer.
Click to expand...
Click to collapse
In my experience, very few phones actually unlock bootloader with simple "OEM unlock". That setting only works if the OEM or carrier wants it to work.
XIAOMI makes you wait TWO months for bootloader unlock:
https://www.xda-developers.com/xiaomi-2-month-wait-unlock-bootloader/
Note I didn't say no phones, I said very few -- compared to the plethora of brands available.
For instance, Motorola makes you request a bootloader unlock code, but Verizon Motorola phones are not eligible.
Sent via open market LG US998 V30/V30+
I'm confused... 10c didn't need TWRP
So I last rooted when I was running 10c on my open market bootloader unlocked US998 V30 (through the official LG method with an LG-generated unlock.bin) and all I had to do was get a boot.img and let Magisk patch it then flash it using adb/fastboot flash.
I have updated to 20d (many thanks ChazzMatt for the KDZ and instructions) and was going to use westwood24's 20d boot.img with Magisk to systemless-ly root again. Since it seems to be asked a lot, I prefer to leave my /data encrypted and never noticed a slowdown without disabling rctd and prefer to have dm-verity on. If there's a way to do that with TWRP and leave stuff encrypted I'm all for it.
Is it no longer possible to flash back a patched boot.img to have just Magisk root and an otherwise completely stock device?
Kakari said:
So I last rooted when I was running 10c on my open market bootloader unlocked US998 V30 (through the official LG method with an LG-generated unlock.bin) and all I had to do was get a boot.img and let Magisk patch it then flash it using adb/fastboot flash.
I have updated to 20d (many thanks ChazzMatt for the KDZ and instructions) and was going to use westwood24's 20d boot.img with Magisk to systemless-ly root again. Since it seems to be asked a lot, I prefer to leave my /data encrypted and never noticed a slowdown without disabling rctd and prefer to have dm-verity on. If there's a way to do that with TWRP and leave stuff encrypted I'm all for it.
Is it no longer possible to flash back a patched boot.img to have just Magisk root and an otherwise completely stock device?
Click to expand...
Click to collapse
You're doing very advanced stuff, and I don't know the answer to that. A developer could give you answers...
I do know I prefer TWRP custom recovery for purposes of having backups. Like having a nifty time machine where you can erase mistakes you make.
TWRP can also let you flash zipped files to install other elements to your phone.
"Stock" recovery is fairly useless in my opinion.
Magisk systemless root without TWRP
ChazzMatt said:
You're doing very advanced stuff, and I don't know the answer to that. A developer could give you answers...
I do know I prefer TWRP custom recovery for purposes of having backups. Like having a nifty time machine where you can erase mistakes you make.
TWRP can also let you flash zipped files to install other elements to your phone.
"Stock" recovery is fairly useless in my opinion.
Click to expand...
Click to collapse
I decided to just 'go for it' again and it still works with Magisk 16 and 17.1 (I didn't dare try 17 with the possible bootloop problems). In the interest of not making something 'advanced' & possibly dangerous too accessible I'll share what I did in broad strokes so molotov_sh and future me can have a rough guide.
The process was:
0. Have an unlocked bootloader (either you have an open market US998 and used the official method or the WTF method)
1. Download the 20d update (what I'm using a newer one will hopefully also work) and the LGUP dev version.
2. Plug in your V30 using a USB2 cable and switch it to File Transfer mode.
3. Open LGUP
4. 'Upgrade' the phone using the KDZ from (1), let it reboot, finish and check that the phone boots, I like throwing in an extra reboot with the phone unplugged from the computer just to be sure. Do any backups of app data, make sure you have 2FA backup codes etc.
5. Reconnect the phone and open LGUP again and choose 'Dump'
5a. It's probably a good idea to dump the whole of your phone excluding 'userdata' just in case. I had a timeout error after about 30-35 minutes but it seemed to get all portions.
6. Choose the 'boot' checkbox for what you want to dump and choose a folder to save it in. The file it dumps is in .img format but does not have a file extension.
7. When its done, unplug the phone, close LGUP, reboot the phone to the regular OS, and plug it back in in file transfer mode.
8. Copy the boot image you dumped in (6) onto the phone, perhaps under Internal SD/Download (I'd add the .img and possibly a version like boot20d.img)
9. Install MagiskManager.
10. Open it, choose Install, Patch Boot Image file, choose the .img file you copied in (8). When its done (without any errors!) you'll have a patched_boot.img file
11. Copy patched_boot.img onto your computer (I like placing it right next to my fastboot executable); you might have to wait a few minutes or restart since the phone can be slow to show newly created files.
12. Unplug your phone & turn it off. Then hold volume down while your plug in the USB cable.
13. Open a terminal/command prompt and navigate to the patched_boot.img file and then run
Code:
fastboot flash boot patched_boot.img
14. It'll take a few tenths of a second and said 'OK'/'Done'. Then enter
Code:
fastboot reboot
and unplug the phone after it starts rebooting. I had mine go through 2 reboot cycles and then it was fine, Magisk works and SafetyNet checks pass.
Recovery is stock and I can have a working hosts file and TitaniumBackup. I use LGBridge for more significant backups.
molotov_sh said:
EDIT: On a V30 H930 if that matters.
Coming from an S7 Edge and a Jelly Pro (which was fairly open) so my understanding of how LG does things may be off.
If I just want Magisk - not interested in TWRP/custom roms etc.
Can I:
- enable OEM unlock in developer settings (device is encrypted etc)
- use magisk manager to generate a new boot.img
- use fastboot to flash this e.g. fastboot flash boot patched_boot.img
Or am I missing something? (Probably!)
Click to expand...
Click to collapse
See @Kakari's post just above this one for root without TWRP, using a patched boot.img.
@Kakari I actually posted a PM to @ChazzMatt about a day after I originally posted here with roughly your procedure (I think he may have seen this thread before that PM). I debated posting it here as I didn't have a clean experience with FOTA 20r to 20y (potential for others to suffer data wipes) - in the end I had to LGUP to go to 20y, see below.
For anyone interested in following my method it will wipe your data.
Let me quote my PM to him here:
Thanks for the pointer the other day
I've used your detailed guides, roms and the rather impressive group discovery thread to come up with a simpler method if you're just after root only and you want the official ROM - "light" root users.
As an aside, I should note that after downgrading to 20r (H930 European here), unlocking the bootloader and hard resetting the FOTA wouldn't bump me to 20y, it'd go through the motions and just wipe the phone each time it rebooted to apply it. So I used LGUP to flash 20y (what I was on before rooting with no updates available) and it's all good for now.
My steps:
- Downgrade to unlockable ROM version using LGUP. EU H930 20r here.
- Flash new_unlock.bin to unlock bootloader in fastboot.
- Hard reset as suggested.
- Flash "latest" official ROM using LGUP. EU H930 20y for me as I wanted what I had originally.
- Get the matching boot image (I pulled boot_6.bin from the 20y kdz)
- Feed to to Magisk Manager's install.
- Flash it in fastboot (fastboot flash boot <patched_boot_6.bin>)
Now I have an entirely stock ROM except for boot, so in theory FOTA capable. Rare use case possibly, but saves TWRP and the funky recovery flashing - which looked like it might also trip safetynet with the LG anti-root stuff (I guessed that might hit system?).
Not sure how FOTA will work going forwards for me, but my hope is that all I'll have to do is reflash a Magisk'ed boot. That'd (hopefully) be the only downside - needing to wait for a boot image to regain root, or (somehow) extract it from the phone.
In reality given my FOTA wipe experience I imagine full backups in advance (titanium in my case, as no twrp) will probably be necessary, just like one should do before flashing any custom ROM or update I suppose. Also as it's a modified boot, if the FOTA does a delta update/verify on it that could get awkward, and would necessitate another trip to LGUP.
Your work on the LG V30 has been invaluable, I hope the above is useful.
Click to expand...
Click to collapse
So yes, I have root with Magisk but no need for TWRP! Thanks for your input anyway, it may help others especially as it has LGUP backup bits.

How To Guide [CLOSED] Firmware is out! Get your root on!

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.

How To Guide N20 5G [CPH2459] - Unlock/Root/Safetynet (Step-by-Step)

These instructions are for the CPH2459 – Unlocked Nord N20 50
I wanted to give back and distribute an easy to follow step-by-step guide as many were asking for a complete guide and I had a little time to create it today. Hopefully this will help kick off some good dev for the device as we are light currently.
I take no responsibility for any issues with your device and do not have backups in the steps, so use at your own risk as always...
COMPLETE STEPS......
Update your phone to the latest OS/patch level over Internet OTA from 1+ and reboot
Verify you are running OS/patch à CPH2459_11_C_10 (latest at time of this)
Enable developer options by clicking on the build number until activation appears (Under Setting-->About-->Version)
Enable Unlock bootloader in the new Developers Options section now in the Phone menu
Enable USB debugging under the new Developers Options
Plug in your phone with usb connected to pc and select transfer files if prompted
Download and extract install latest ptools-n20.zip (with included patched boot files)
Open a windows command prompt in the folder that you extracted the platform tools into
Run adb devices and be sure the phone shows up as a device that is attached
Accept device fingerprint if asked
Run command to boot to bootloader: adb reboot bootloader
Run command to ensure connection in bootloader to your phone: fastboot devices
Run Command to unlock bootloader: fastboot flashing unlock
Lave command prompt open
Use volume keys to select “unlock bootloader” then press “power” to unlock
The device will reset and will now be unlocked
After phone boots, complete the quick setup
Repeat step #3, #5-6, #9-12
In Command prompt where platform tools are installed run command: fastboot flash boot a.img
Reboot phone and you will be patched
Install Magisk 25.2 App from official repo & Enable Zygisk in settings
Enable Magisk hide and reopen the app
Add your google account if not already added and use Play Store or use Aurora store to install Safetynet Checker by flink apps
Run Safetynet checker and notice the device fails 2 checks
Transfer 2 zip files included to your phone: Shamiko & Safetynet fix. These will help hiding root and will allow your phone to pass Safetynet fixes
Install both zips under module section in Magisk. (you can do 1…don’t reboot when asked, then do other and reboot to activate both)
Run Safetynet Checker again and you should pass all checks.
Viola…you are unlocked/rooted/patched and pass safetynect checks.....ENJOY!
I will update here on how to take future OTAs as more come out and if time allows.
NOTES: Files in platform tools
a.img = boot_a.img magisk patched
b.img = boot_b.img magisk patched (just in case)
boot_a.img = Unpatched a (just in case)
boot_b.img = Unpatched b (just in case)
==============================================
2/3/23 UPDATE: How to take an OTA and preserve root
==============================================
1. First, Under developer options, make sure the option to apply automatic updates on reboot is ENABLED. (If you do not do this, you will loose root)
2. Unroot the device. We wont completely remove Magisk, just restore images. To do this Open Magisk, click uninstall magisk, and only click "restore images". DO NOT REBOOT!
3. Check for software updates. Install OTA update after downloaded. DO NOT REBOOT!
4. Open Magisk again and now reinstall it but select "inactive slot" for the option.
5. REBOOT. Boot will take about 30 seconds to apply.
You are now updated
ScarletWizard said:
Thank you for this I will post this on the telegram channel
Click to expand...
Click to collapse
What is the link to the telegram chan?
mvincent2k said:
What is the link to the telegram chan?
Click to expand...
Click to collapse
My CPH2459 crappped out on me, and I have had little luck since moving from GN2200 to this model and could use a backup if you could lend a hand
mvincent2k said:
What is the link to the telegram chan?
Click to expand...
Click to collapse
OnePlus Nord N20 | Official
You can view and join @oneplusnordn20 right away.
t.me
ScarletWizard said:
Incorrect link
Click to expand...
Click to collapse
Can you share the right channel.
mvincent2k said:
These instructions are for the CPH2459 – Unlocked Nord N20 50
I wanted to give back and distribute an easy to follow step-by-step guide as many were asking for a complete guide and I had a little time to create it today. Hopefully this will help kick off some good dev for the device as we are light currently.
Click to expand...
Click to collapse
Damn son, your attention to detail is admirable! Very thorough and well-documented. Thanks.
Can I use this on the new ota update
mvincent2k said:
a.img = boot_a.img magisk patched
Click to expand...
Click to collapse
killerex said:
Can I use this on the new ota update
Click to expand...
Click to collapse
No you would need an updated img if you are on the latest upgrade. I no longer have an N20 to test with otherwise would create one for the group. Someone else may possibly.
How? I'm not updated yet can guide me how to do it.thank
killerex said:
How
Click to expand...
Click to collapse
Search the other XDA threads here for this device. A few explain how to extract payload and patch.
If you are on the previous update, see the update to my instructions just posted on how to take the OTA and stay rooted with Magisk
I'm getting installation error.. I'm in previous update
mvincent2k said:
These instructions are for the CPH2459 – Unlocked Nord N20 50
I wanted to give back and distribute an easy to follow step-by-step guide as many were asking for a complete guide and I had a little time to create it today. Hopefully this will help kick off some good dev for the device as we are light currently.
I take no responsibility for any issues with your device and do not have backups in the steps, so use at your own risk as always...
COMPLETE STEPS......
Update your phone to the latest OS/patch level over Internet OTA from 1+ and reboot
Verify you are running OS/patch à CPH2459_11_C_10 (latest at time of this)
Enable developer options by clicking on the build number until activation appears (Under Setting-->About-->Version)
Enable Unlock bootloader in the new Developers Options section now in the Phone menu
Enable USB debugging under the new Developers Options
Plug in your phone with usb connected to pc and select transfer files if prompted
Download and extract install latest ptools-n20.zip (with included patched boot files)
Open a windows command prompt in the folder that you extracted the platform tools into
Run adb devices and be sure the phone shows up as a device that is attached
Accept device fingerprint if asked
Run command to boot to bootloader: adb reboot bootloader
Run command to ensure connection in bootloader to your phone: fastboot devices
Run Command to unlock bootloader: fastboot flashing unlock
Lave command prompt open
Use volume keys to select “unlock bootloader” then press “power” to unlock
The device will reset and will now be unlocked
After phone boots, complete the quick setup
Repeat step #3, #5-6, #9-12
In Command prompt where platform tools are installed run command: fastboot flash boot a.img
Reboot phone and you will be patched
Install Magisk 25.2 App from official repo & Enable Zygisk in settings
Enable Magisk hide and reopen the app
Add your google account if not already added and use Play Store or use Aurora store to install Safetynet Checker by flink apps
Run Safetynet checker and notice the device fails 2 checks
Transfer 2 zip files included to your phone: Shamiko & Safetynet fix. These will help hiding root and will allow your phone to pass Safetynet fixes
Install both zips under module section in Magisk. (you can do 1…don’t reboot when asked, then do other and reboot to activate both)
Run Safetynet Checker again and you should pass all checks.
Viola…you are unlocked/rooted/patched and pass safetynect checks.....ENJOY!
I will update here on how to take future OTAs as more come out and if time allows.
NOTES: Files in platform tools
a.img = boot_a.img magisk patched
b.img = boot_b.img magisk patched (just in case)
boot_a.img = Unpatched a (just in case)
boot_b.img = Unpatched b (just in case)
==============================================
2/3/23 UPDATE: How to take an OTA and preserve root
==============================================
1. First, Under developer options, make sure the option to apply automatic updates on reboot is ENABLED. (If you do not do this, you will loose root)
2. Unroot the device. We wont completely remove Magisk, just restore images. To do this Open Magisk, click uninstall magisk, and only click "restore images". DO NOT REBOOT!
3. Check for software updates. Install OTA update after downloaded. DO NOT REBOOT!
4. Open Magisk again and now reinstall it but select "inactive slot" for the option.
5. REBOOT. Boot will take about 30 seconds to apply.
You are now updated
Click to expand...
Click to collapse
Thank you for this! Glad to see people are picking up the slack. I havent updated yet because im worried about having to battle tighter restrictions that newer versions of android inevitably bring. I wont be able to use the images as i have the gn2200 but grateful for the how to guide on updating. Didnt realize it was quite that easy. Im still on May on one device and July on the other tho recently had to downgrade it to restore it in an emergency situation and was thankfully able to do all the flashing from the may device otg
PsYk0n4uT said:
Thank you for this! Glad to see people are picking up the slack. I havent updated yet because im worried about having to battle tighter restrictions that newer versions of android inevitably bring. I wont be able to use the images as i have the gn2200 but grateful for the how to guide on updating. Didnt realize it was quite that easy. Im still on May on one device and July on the other tho recently had to downgrade it to restore it in an emergency situation and was thankfully able to do all the flashing from the may device otg
Click to expand...
Click to collapse
Not a problem. Always glad to help the community out!
Very nice. I'm expecting delivery of one of these phones tomorrow. It already has Android 12 installed on it. So, I'm wondering if it's safe to use the attached image files to root it or should I go through the process of having Magisk patch the phone's existing a and b images?
Raybo58 said:
Very nice. I'm expecting delivery of one of these phones tomorrow. It already has Android 12 installed on it. So, I'm wondering if it's safe to use the attached image files to root it or should I go through the process of having Magisk patch the phone's existing a and b images?
Click to expand...
Click to collapse
Just make sure your using a12 boot image if your trying to use a posted one.balso be sure to use the same security patch boot image as the system you already have installed.
Safest bet is to use the DSU sideloader method to pull your own boot image and then patch it if your unsure of which patched boot image to use. It's a little more complicated but pulling your own boot image will ensure that you have an exact match for your device.
If you have or can locate and obtain an unpatched boot image that matches your system. You should have one on hand just in case the patched boot image doesn't work so that you can simply reflash your stock image in that case.
A mismatching boot image can lead to an unbootable state so you need to be prepared.
You shouldn't have to worry much about anything crazy or unrepairable so long as your flashing boot images made for the device your flashing them to. Just don't flash boot images from a completely different device as that can cause you to end up with any sort 9f crazy weird issues that may not even be fixable.
Raybo58 said:
Very nice. I'm expecting delivery of one of these phones tomorrow. It already has Android 12 installed on it. So, I'm wondering if it's safe to use the attached image files to root it or should I go through the process of having Magisk patch the phone's existing a and b images?
Click to expand...
Click to collapse
By any chance you got the latest boot.img
Will this work on a GN2200?
NO
Followed instructions and it worked. BUT, can't update the firmware. When I try to restore images in Magisk it says they don't exist. So I can't update to the latest firmware. Suggestions?
alipps1 said:
Followed instructions and it worked. BUT, can't update the firmware. When I try to restore images in Magisk it says they don't exist. So I can't update to the latest firmware. Suggestions?
Click to expand...
Click to collapse
I recently ran into this on another device and had to fix so you are in luck. I believe something broke with magisk running on 13 during the last OTA with security, so here are the steps...
1) Unhide and Uninstall magisk app completely and Update to the latest canary version of magisk apk here and restart: https://github.com/topjohnwu/Magisk
2) Verify it sees magisk installed and has latest build.
3) Try restoring images again and it may work.
If that does not work...
1) You will need to do a full unroot...which technically should not work if the images were not present, but it does, so images are present (proving it is a bug)
2) You will need to complete the full procedure of patching the boot image again yourself.
3) Extract payload and patch the boot.img per instructions in this forum, then flash per my instructions above.
FYI. I did this on the current version of the OS and then did the restore images and upgrade to take the OTA and prove the bug and that OTA updates will work as in the instructions above in the future again, which it did.
Alternatively, you could also update the to the latest OTA after unrooting and just do it once, but I wanted to play it safe just in case Google updated something in the latest 13 builds blocking magisk... So your choice, but please post back here how you make out.
Good luck

TWRP for Cubot P50?

Hi, I've just bought a Cubot P50, it's a Chinese brand and seems more than decent for the price, I've rooted it with Magisk and I want to install TWRP on it but can't find anything for that brand. Has anyone came across a TWRP that might work on it?
Marko Lyno said:
Hi, I've just bought a Cubot P50, it's a Chinese brand and seems more than decent for the price, I've rooted it with Magisk and I want to install TWRP on it but can't find anything for that brand. Has anyone came across a TWRP that might work on it?
Click to expand...
Click to collapse
I have the same phone how did you root it ? If there a guide that is safe to use ? Thank you
Unlock the bootloader first, this step will factory reset your phone https://romprovider.com/unlock-bootloader-android/
On your PC:
1. Install Fastboot driver
2. Install MediaTek_Preloader_USB_VCOM_Drivers_Setup_Signed
3. Extract platform-tools
4. On your phone, Enable Developer Options, USB debugging and OEM Unlocking
5. Unlock bootloader (this step will factory reset your phone): Phone in fastboot mode, open command prompt on PC > fastboot devices > fastboot flashing unlock. Note this will cause the phone to show the "Orange State" warning on boot up. You can ignore this or remove it later.
(If device is unauthorised in ADB or Fastboot, go to Developer Options on phone, revoke USB debugging authorisation, disable then enable USB debugging. You should now get an authorisation confirmation dialogue when you try to connect with ADB/Fastboot. If not, type "adb kill-server", then "adb devices" or "adb start-server" in the command prompt).
6. Place boot.img on phone with USB file transfer (either from stock ROM, or read from phone using SP_Flash_Tool_v5.1924_Win) and patch it with Magisk v5.2. NO need to patch vbmeta.img
7. Transfer patched boot.img back to PC
8. Flash the patched boot.img to phone either with SP Flash Tool or Fastboot command in ADB (fastboot flash boot boot.img). Take care here, make sure it's the right image going to the right location and that ALL other files are de-selected, especially the preloader file, always de-select this when flashing any firmware unless you know what you're doing!
Phone is now rooted.
How to remove orange state warning on this device:
How to remove Orange, Yellow & Red state warnings on MTK
This guide will explain how to hide or remove Yellow, Red and Orange state warnings on a Mediatek Android device. Its ideal for those who feel irritated by constantly seeing these warnings on reboot.
www.hovatek.com
Edit: If you need a stock ROM for the phone it's here https://www.cubot.net/Support/id/78/cid/19.html#hh
Good evening, I would like to know if in the future it is possible to install a twrp with a custom rom?
Thank you have a nice day.
Good evening, I would like to know if in the future it is possible to install a twrp with a custom rom on the Cubot p50?
Thank you have a nice day.
Mark8:9 said:
Good evening, I would like to know if in the future it is possible to install a twrp with a custom rom on the Cubot p50?
Thank you have a nice day.
Click to expand...
Click to collapse
It is possible that in the future, developers may create custom ROMs and TWRP recoveries for the device, especially if it becomes popular among the Android community.
If a custom ROM and TWRP recovery becomes available for your device in the future, you will be able to flash it by following the instructions provided by the developer. Keep in mind that installing custom ROMs and recoveries comes with some risks, and it is important to backup your data and follow the instructions carefully to avoid damaging your device.
Good evening, can you tell me the correct procedure for how to Root the Cubot p50 smartphone? Thank you.
Mark8:9 said:
Good evening, can you tell me the correct procedure for how to Root the Cubot p50 smartphone? Thank you.
Click to expand...
Click to collapse
Well if you really want to know that, surely you would have read the entire thread? It's not that long. I gave complete instructions 5 posts up
Marko Lyno said:
Well if you really want to know that, surely you would have read the entire thread? It's not that long. I gave complete instructions 5 posts up
Click to expand...
Click to collapse
Good evening, be patient ... but where do I find Magisk 5.2 to download and how do I install it? Thanks good evening.
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com
Just get the latest version and follow the instructions I posted.
Thanks for your work on the Cubot phone .Im a fan of them also. I found that twrp recovery 3.40 works on the Note 20/20Pro you just have to flash vbmeta BEFORE and AFTER you flash twrp to the device. Im also seeing separate websites claiming twrp 3.40 is also used with the Cubot P40 model. I dont see why it wouldnt work with the P50. Its worth a shot. Also theres alot more "familiars" with Mediatek phones like these in Hovatek forum. Since you already have information on how to root maybe consider starting your own P50 thread over there.
My references: https://www.hovatek.com/forum/thread-44810-post-233457.html#pid233457
elimoviebuff said:
Thanks for your work on the Cubot phone .Im a fan of them also. I found that twrp recovery 3.40 works on the Note 20/20Pro you just have to flash vbmeta BEFORE and AFTER you flash twrp to the device. Im also seeing separate websites claiming twrp 3.40 is also used with the Cubot P40 model. I dont see why it wouldnt work with the P50. Its worth a shot. Also theres alot more "familiars" with Mediatek phones like these in Hovatek forum. Since you already have information on how to root maybe consider starting your own P50 thread over there.
My references: https://www.hovatek.com/forum/thread-44810-post-233457.html#pid233457
Click to expand...
Click to collapse
Thanks for that. Is there a specific vbmeta to patch it with?
Good evening, can you give me the link to download a compatible cust recovery for the cubot p50? Thank you
The link is on the page just posted above. Here's the direct link to the file:
Hovatek
Download files
www.hovatek.com
Let us know if it works please, and what steps you took.
Good evening, how will I flash the lk file? Thanks.
Hi, you will have, or should have, downloaded a zip file containing a recovery.img. The recovery.img is the file you need to flash. Then follow the instructions here:
How to Install TWRP Recovery on Any Android 2022 [100% Working]
In this article, I will be showing you how you can install TWRP recovery on any Android smartphone. By following this guide you will be able to install
magiskapp.com
The TWRP Recovery file it refers to is the one you (hopefully) downloaded from this link:
Hovatek
Download files
www.hovatek.com
BUT, you also need to flash a vbmeta file BEFORE and AFTER the recovery.img, and I'm still unsure which vbmeta file it is, as elimoviebuff hasn't replied to my question regarding that.
Marko Lyno said:
Hi, you will have, or should have, downloaded a zip file containing a recovery.img. The recovery.img is the file you need to flash. Then follow the instructions here:
How to Install TWRP Recovery on Any Android 2022 [100% Working]
In this article, I will be showing you how you can install TWRP recovery on any Android smartphone. By following this guide you will be able to install
magiskapp.com
The TWRP Recovery file it refers to is the one you (hopefully) downloaded from this link:
Hovatek
Download files
www.hovatek.com
BUT, you also need to flash a vbmeta file BEFORE and AFTER the recovery.img, and I'm still unsure which vbmeta file it is, as elimoviebuff hasn't replied to my question regarding that.
Click to expand...
Click to collapse
I get it, but I have to flash the .bin to remove the yellow/red state on boot. I don't know how to install the lk.bin file. If you can help me. Thank you.
Ah I see, you're rooting the phone first. Ok I've just checked my own notes on this, so, if you have edited the lk.img file as described in that Hovatek thread, then do as follows:
When flashing with SP Flash Tool, make sure the correct lk.img file is chosen as SP Flash Tool chooses lk-verified.img by default (click along to the right of the file list under "Location" and choose your edited lk.img file here).
OR, flash with ADB (fastboot flash lk lk.img).
Then install Magisk on your phone if you haven't already.
boot.img is for rooting the phone, lk.img is only to remove the orange state message and the 5 second delay when the phone boots, it does not actually remove it's orange state and is not needed for the phone to be rooted.
To un-root, you should just flash the original boot.img and lk-verified.img from the stock firmware ROM file.
Marko Lyno said:
Ah I see, you're rooting the phone first. Ok I've just checked my own notes on this, so, if you have edited the lk.img file as described in that Hovatek thread, then do as follows:
When flashing with SP Flash Tool, make sure the correct lk.img file is chosen as SP Flash Tool chooses lk-verified.img by default (click along to the right of the file list under "Location" and choose your edited lk.img file here).
OR, flash with ADB (fastboot flash lk lk.img).
Then install Magisk on your phone if you haven't already.
boot.img is for rooting the phone, lk.img is only to remove the orange state message and the 5 second delay when the phone boots, it does not actually remove it's orange state and is not needed for the phone to be rooted.
To un-root, you should just flash the original boot.img and lk-verified.img from the stock firmware ROM file.
Click to expand...
Click to collapse
Good morning. Thank you for the information given.
I wanted to ask: is it necessary or useful to install an antivirus on your smartphone now that it's been rooted? Thank you.
I haven't but that's just down to personal choice really. It's certainly useful if you like to try stuff from unknown sources, although personally I've rarely encountered viruses on Android. I'm not saying they don't exist though.
Have you successfully rooted your phone then? What about TWRP, have you tried that yet?

Categories

Resources