Related
WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are risking voiding your warranty! I am NOT responsible for what you do to your device either, so follow these instructions at your own risk. Make sure you know what you're doing, it's best to understand the process rather than just copy and paste commands and such.
Useful and important general information can be found in the second post here.
NOTES
1. If you flash the TWRP Installer when you've already got Magisk installed, your device will keep booting to the recovery. You should be able to fix this by just simply reflashing Magisk.
2. If you have TWRP installed via the TWRP Installer, you will not be able to install stock OTA updates. You will have to reflash the stock boot image for whatever build you're running beforehand.
3. The prebuilt TWRP image may not have touch functionality if you're using the September 2018 Update or newer. Patching the boot image, however, for these builds with the TWRP Installer will allow touch to work flawlessly. Here is a pre-patched September 2018 Boot Image with TWRP. It should also work with builds newer than September. Since it's based off the September 2018 update, I suggest not using this as your main boot image but rather just as a replacement for the pre-built TWRP image from the official TWRP thread.
4. Simple "flash and forget" boot images pre-patched with Magisk and TWRP are provided by @aer0zer0 and are available here. They are based on ianmacd's variant of Magisk. If you are running stock, you can flash these boot images to get root and TWRP instead of following the guide to patch it yourself. Here is January's.
If you don't care about TWRP and simply want to just root your device, you can just simply patch the boot image for your ROM with the Magisk Manager and flash it in fastboot with
Code:
fastboot flash boot patched_boot.img
The link to the boot images for most stock builds can be grabbed from my Google Drive link in the second post or from the back-to-stock zips.
REQUIREMENTS
An unlocked bootloader
Working adb and fastboot environment, along with knowledge on how they work.
The latest build of TWRP along with the TWRP Installer. Read Note 3 above beforehand.
1. Download the latest build of TWRP and the TWRP Installer. Transfer the TWRP Installer zip to your device.
2. Reboot your phone into fastboot. Once in fastboot, change your device's current slot using the command
Code:
fastboot set_active other
If the command above doesn't work for you, use fastboot getvar current-slot followed by fastboot -aX, replacing "X" with the slot opposite (a or b) from your current slot.
3. Once your device's current slot has been switched, flash the TWRP image you downloaded earlier using the command
Code:
fastboot flash boot twrp.img
Depending on your version of fastboot, the above command might not work either. In that case, you can enter the following command, replacing "X" with your current slot (a or b).
Code:
fastboot flash boot_X twrp.img
4. Once TWRP has been flashed, boot into the recovery.
5. Once you have booted into TWRP, simply flash the TWRP Installer zip.
6. Once you have finished flashing the TWRP Installer zip, boot to recovery on the OPPOSITE slot. You can do this from TWRP by going to "Reboot", then selecting the opposite of the current slot (if on A, select Slot B. If on B, select Slot A), then select "Recovery." You can also do this through fastboot by running the same command from step 2.
7. Once you have booted back into TWRP, simply flash the Magisk zip and you are now good to go! Feel free to flash anything else like kernels while you're at it.
8. Reboot. :good:
NOTE: TWRP WILL remain installed on your device so long as you reflash the installer zip after every update.
Important Information for the Essential PH-1 can be found here. Keep it bookmarked.
Tips on updating via OTA after rooting can be found here.
In the case that you mess something up on your device, you may find it helpful to revert back to stock with the unofficial factory images graciously provided by @invisiblek and @aer0zer0 over here.
Official TWRP XDA Thread for the Essential PH-1
Join the Essential PH-1 Discord Server! -- Lots of cool people here!
Join the Essential PH-1 Development Telegram Channel!
Stock Boot Images for most builds can be found at my Google Drive link here.
Have a Red Verity Warning when booting your device? Click here.
If the link to the boot.fix.red image isn't working, you can also find it here or in my Google Drive link in the first post.
Essential Phone (PH-1) Partition Layout
Dumping Boot Images
1. Find the current slot with
Code:
fastboot getvar current-slot
or
Code:
adb shell getprop ro.boot.slot_suffix
2. Switch to the opposite slot in Fastboot using the command
Code:
fastboot set_active other
3. Flash TWRP using the command
Code:
fastboot flash boot twrp.img
4. Now, boot into TWRP and use the following command from your PC, replacing X in "boot_X" with the original slot from step 1 (a or b). TRIPLE CHECK:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot_X of=/sdcard/boot.img
5. Profit! Don't forget to switch back to the original partition with the same command from step 2!
extractTarFork() error when restoring data from a TWRP backup
1. Reinstall the ROM from which the backup is based on.
2. Wipe your data. You can do this from the recovery or from fastboot using the command
Code:
fastboot -w
3. Boot into the ROM. When going through the initial setup, use the EXACT same security setup as the one from your backup. For example, if you used a Fingerprint + Password in the backed up ROM, use the exact same combo along with the exact same password as well. There is no need to set up anything else, like accounts.
4. Flash, install, and reboot into TWRP. You should now be able to restore the data backup without any issues.
AFH mirrors for images:
Build NMJ32F
NMJ32F patched boot image
NMJ32F factory image
Build NMJ20D
NMJ20D patched boot image
NMJ20D factory image
TWRP (alpha v4)
Thanks for getting the latest boot image up so quickly.
Thanks for the detailed guide, it worked great!
Any idea how to install xposed sdk 25? I tried the adb sideload function and the Magsik Module but both failed. Any ideas?
how to install the NMJ32F ota update when you are already rooted on NMJ20D?
Tried adb sideload but cannot install obviously because boot-loader is unlocked and is rooted.
prgopala said:
how to install the NMJ32F ota update when you are already rooted on NMJ20D?
Tried adb sideload but cannot install obviously because boot-loader is unlocked and is rooted.
Click to expand...
Click to collapse
You need to flash the system and boot images from Invisiblek's stock ROM dump. You'll then be unrooted and will be able to accept the update.
Factory reset no longer required if your bootloader is already unlocked? Does TWRP read encypted storage now? Or is that still a problem?
@bmg1001 , good looks, here are more free XDA points to trade in for that pool table, lol.
gk1984 said:
Factory reset no longer required if your bootloader is already unlocked? Does TWRP read encypted storage now? Or is that still a problem?
Click to expand...
Click to collapse
As far as I know, TWRP still doesn't have decryption fully working just yet, but installing Magisk works fine without any factory resets.
prozo said:
Thanks for the detailed guide, it worked great!
Any idea how to install xposed sdk 25? I tried the adb sideload function and the Magsik Module but both failed. Any ideas?
Click to expand...
Click to collapse
Xposed works fine for me. Make sure you installed the correct Xposed Installer/Manager apk linked in the thread for the Xposed Module. Also, it may take a reboot or two for Xposed to fully activate.
Did anyone manage to disable encryption? I tried everything and failed
bmg1001 said:
Xposed works fine for me. Make sure you installed the correct Xposed Installer/Manager apk linked in the thread for the Xposed Module. Also, it may take a reboot or two for Xposed to fully activate.
Click to expand...
Click to collapse
Maybe I'm not gathering the information correctly, using the Magisk Module itself doesn't work, sideloading the zip file via the adb fastboot TWRP.img doesn't work either, using the actual Xposed APK installer doesn't work either. I rebooted the phone about 4 times before removing it entirely.
Any chance you can walk me through how you got it installed without the TWRP recovery fully installed?
prozo said:
Maybe I'm not gathering the information correctly, using the Magisk Module itself doesn't work, sideloading the zip file via the adb fastboot TWRP.img doesn't work either, using the actual Xposed APK installer doesn't work either. I rebooted the phone about 4 times before removing it entirely.
Any chance you can walk me through how you got it installed without the TWRP recovery fully installed?
Click to expand...
Click to collapse
All I did was install the Xposed APK and then the Xposed Magisk Module. After two reboots, the apk said everything was working. This is the apk I used: https://drive.google.com/file/d/16-OHpswcngp1KLtkWCBDwwl8AvFafR5H/view?usp=drivesdk
bmg1001 said:
All I did was install the Xposed APK and then the Xposed Magisk Module. After two reboots, everything was working. This is the apk I used: https://drive.google.com/file/d/16-OHpswcngp1KLtkWCBDwwl8AvFafR5H/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks for replying so quickly I appreciate it, the file you linked keeps opening on my end and fails to install saying it's corrupt
prozo said:
Thanks for replying so quickly I appreciate it, the file you linked keeps opening on my end and fails to install saying it's corrupt
Click to expand...
Click to collapse
The apk should be the same one found here: https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
bmg1001 said:
All I did was install the Xposed APK and then the Xposed Magisk Module. After two reboots, the apk said everything was working. This is the apk I used: https://drive.google.com/file/d/16-OHpswcngp1KLtkWCBDwwl8AvFafR5H/view?usp=drivesdk
Click to expand...
Click to collapse
Alright I got it to work
So I didn't use the APK instead I downloaded the zip from the XDA thread that is specifically for Magisk Module and then added via the modules tab on the left side of the Magisk Module APK.
After I restarted I had the newly installed APK to download and install the proper version of Xposed 88.2 sdk25
Another restart and boom I got the active module notification in green.
Thanks man!
Thread for downloads can be found here:
https://www.google.com/amp/s/forum....ed/unofficial-systemless-xposed-t3388268/amp/
Thank you for this!
My PH-1 is arriving today. SooOoo excited!
spotmark said:
You need to flash the system and boot images from Invisiblek's stock ROM dump. You'll then be unrooted and will be able to accept the update.
Click to expand...
Click to collapse
Would using flashfire work to install the ota?
drocny87 said:
Would using flashfire work to install the ota?
Click to expand...
Click to collapse
Couldn't tell you. I just used TWRP to flash the system and boot, and then took the update, and then rerooted.
Hello everyone,
I've been tinkering around with Generic System Images since the Oreo Developer Preview 1 came out for the Razer Phone. I'm glad to say I got it to work, with lots of help from @MishaalRahman, @P4Block and indirect help of @phhusson and @TheCrazyLex.
What's working as of right now:
- GPS
- Rear Camera (only one of the lenses, needs further testing/pulling the Razer camera app apk)
- Front camera
- Microphones
- Sensors, each and every of them
- Speakers, sound playback, videoplayback (needs further testing)
- Fingerprint scanner
- WiFi, Bluetooth, NFC
- 120Hz screen features
- Color adjustments from the Oreo DP1 by Razer
- 4G LTE
- In-Call audio
What needs further testing:
- 4G/LTE FIXED check out post #77!
- Once the above is confirmed to work => VoLTE on any carrier, and also testing on certain carriers like 3 UK (since they sold a version with different software).
What's broken:
- Audio in phone calls (works properly in VoIP/3rd party apps) FIXED check out post #48!
What ROMs can be booted with this (as of 30-03-2018):
AOSP 8.1
Lineage OS 15.1
Resurrection Remix
More to come...
Setting up your device:
You'll need:
Code:
To [URL="https://forum.xda-developers.com/razer-phone/how-to/guide-to-unlocking-bootloader-t3706462"]fully unlock your bootloader[/URL] and [URL="https://forum.xda-developers.com/showpost.php?p=74607352&postcount=8"]unlock flashing capabilities[/URL] on your device.
[URL="https://eu.dl.twrp.me/cheryl/twrp-3.2.1-0-cheryl.img.html"]TWRP image[/URL] + [URL="https://eu.dl.twrp.me/cheryl/twrp-installer-3.2.1-0-cheryl.zip.html"]TWRP injector[/URL]
[URL="http://tiny.cc/latestmagisk"]Magisk flashable zip[/URL]
A GSI of your preference from the ones listed [URL="https://forum.xda-developers.com/project-treble/trebleenabled-device-development"]here[/URL]. PS: Use the Gapps+SU one if you choose AOSP ;)
0. Make sure you're running the Android O DP1 from Razer, or any future update to it.
THIS WON'T WORK ON NOUGAT
1. Properly install TWRP on your device: (I'll be using @Dees_Troy's guide with a few modifications to make very sure everything will work as intended)
- fastboot flash the twrp image as explained by him, in your currently active boot partition. PS: After flashing the Android O DP1, it will always be A.
Dees_Troy said:
Once you have adb working, run this command: adb shell getprop ro.boot.slot_suffix
It should say: [ro.boot.slot_suffix]: [_a] Or: [ro.boot.slot_suffix]: [_b]
Make note of whether you are currently using slot A or B. Next power off the device and boot to the bootloader using your USB cable and volume down. You want to switch to the other boot slot. If you are currently on slot A, type this: fastboot --set-active=_b Or on slot B type this: fastboot --set-active=_a
You should see something like this: Setting current slot to 'a'... OKAY [ 0.042s] finished. total time: 0.042s
I found the bootloader on the Razer Phone to be extremely finicky and I had to run the command multiple times until I got it to run successfully. You may have to hold the power button for 15 seconds to force power off the device and then re-enter fastboot mode. Keep trying until it works. Once it's on the right boot slot, type this: fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot
Click to expand...
Click to collapse
2. Once you're in TWRP, DO NOT SLIDE to allow modifications, but tap on Mount as Read Only. Plug in your USB cable, and adb push the boot image from the Android O DP1 factory image to your sdcard, as well as the TWRP injector and the Magisk zip. That can be done with the following commands:
Code:
adb push twrp-installer-3.2.1-0-cheryl.zip /sdcard
Code:
adb push path/to/the/factoryimage/boot.img /sdcard
Code:
adb push Magisk-16.0.zip /sdcard
3. Go into Reboot, then make sure you're on partition A. Else, tap on the button to set A as the active partition.
Now go back, tap Install, then tap on 'Install Image' then choose the boot.img you just pushed, and flash it as boot image.
Now go back, into Reboot, and move to partition B and repeat the step above.
Once you're sure both partitions only contain the unmodified boot images, set the partition A as active, go into Install, choose the twrp-installer-3.2.1-0-cheryl.zip and flash it.
Once it finishes, do the same with the Magisk zip file.
4. Go into Reboot, press on Bootloader.
5. Connect the usb cable, and flash the GSI system image onto your system_a partition through fastboot from your pc. This can be done with the command:
Code:
fastboot flash system_a system-arm64-ab.img
5.b If you wish, you can install a different GSI onto your system_b partition, and that can be done with the following commands:
Code:
fastboot set_active b
Code:
fastboot flash system_b system-arm64-ab-gapps-su.img
5.c If you wish to go back to the system_a partition, you can execute:
Code:
fastboot set_active a
6. Reboot and enjoy.Prebuilt boot image:
If doing the steps from 1-4 seems messy or you don't get it to work properly, I've published the image I made following them with the latest Magisk and TWRP versions available as of April 20th 2018.
You can download it from here. You can then flash it from fastboot by using the commands:
Code:
fastboot flash boot_a boot_linuxct_20180420_cheryl_omr0.img
Code:
fastboot flash boot_b boot_linuxct_20180420_cheryl_omr0.img
SHA-2: 2f0c7348ac906f2f81fa39df7b24b69392783bd2379d5da357777be444c67d97
Old version (from ODP1 - may experience the bootloader issues):
You can download it from here. You can then flash it from fastboot by using the commands:
Code:
fastboot flash boot_a boot_linuxct_20180330_cheryl_odp1.img
Code:
fastboot flash boot_b boot_linuxct_20180330_cheryl_odp1.img
SHA-2: 8f763162415167b2e919a450654f9a46f69b81f6853013bcabf362dfeb2a115e
Many thanks to everyone that helped me today to get this to work properly!
Want some screenshots?
Thanks for all the hard work!
I've followed the guide but after flashing the GSI I get stuck at the Android logo and the system never boots?
Any help would be appreciated
PupPupG said:
Thanks for all the hard work!
I've followed the guide but after flashing the GSI I get stuck at the Android logo and the system never boots?
Any help would be appreciated
Click to expand...
Click to collapse
Did you follow all the steps carefully? Did you make sure you flashed Magisk?
Magisk is needed since it disables DM-Verity, which is what IMO gets the device stuck at first boot.
Oh, and also, sometimes during first boot your device gets encrypted. Mine took a bit extra that time (specifically booting the LineageOS image).
If you can't still get it to work, try with the prebuilt boot image.
This is awesome!!!
I'd love to have a fully working resurrection remix build working on my cheryl!!!!! =D <3
KEEP UP THIS AWESOME WORK!!!!!!!!!
linuxct said:
Did you follow all the steps carefully? Did you make sure you flashed Magisk?
Magisk is needed since it disables DM-Verity, which is what IMO gets the device stuck at first boot.
Oh, and also, sometimes during first boot your device gets encrypted. Mine took a bit extra that time (specifically booting the LineageOS image).
If you can't still get it to work, try with the prebuilt boot image.
Click to expand...
Click to collapse
I tried again using all of the info but they closest I've gotten to a boot is the Android logo and then a prompt to decrypt but no matter what I enter I get "Decryption Unsuccessful" and it just brings me back to TWRP
PupPupG said:
I tried again using all of the info but they closest I've gotten to a boot is the Android logo and then a prompt to decrypt but no matter what I enter I get "Decryption Unsuccessful" and it just brings me back to TWRP
Click to expand...
Click to collapse
Flash the Oreo DP1 image and start over.
linuxct said:
Flash the Oreo DP1 image and start over.
Click to expand...
Click to collapse
From what I can tell, TWRP cannot format the data partition properly which is what causes LOS to appear as encrypted and won't finish booting. I was able to successfully able to get it to boot by flashing the stock boot.img and booting to stock recovery and factory reset that way. After doing that, flash your ROM of choice and Magisk and it should be usable.
ThatGuy94 said:
From what I can tell, TWRP cannot format the data partition properly which is what causes LOS to appear as encrypted and won't finish booting. I was able to successfully able to get it to boot by flashing the stock boot.img and booting to stock recovery and factory reset that way. After doing that, flash your ROM of choice and Magisk and it should be usable.
Click to expand...
Click to collapse
Flashing the Oreo DP1 image actually flashes an empty, non-encrypted userdata image. That's why I requested to start over.
That can also be another solution, bit messier than starting over but it's good.
Does anyone have Magisk fully working with this? I still get ctsprofile:false
Aside from this, excellent work!
M1cky said:
Does anyone have Magisk fully working with this? I still get ctsprofile:false
Aside from this, excellent work!
Click to expand...
Click to collapse
I do. Try installing the latest beta of Magisk and then, if that didn't solve it, try setting a new Build fingerprint with a tool like MagiskHide Props Config (PS. Just to be sure, set the Google Pixel 2 XL one since that's the only 8.1.0 build fingerprint provided by that tool).
ThatGuy94 said:
From what I can tell, TWRP cannot format the data partition properly which is what causes LOS to appear as encrypted and won't finish booting. I was able to successfully able to get it to boot by flashing the stock boot.img and booting to stock recovery and factory reset that way. After doing that, flash your ROM of choice and Magisk and it should be usable.
Click to expand...
Click to collapse
Could you please tell me how you flash Magisk? After I flash a ROM I'm not able to boot into TWRP to flash Magisk
Happy to see people making use of Treble on Razer Phone this quickly.
Good job! @linuxct
Have no idea where I went wrong but after I had RR up and running I rebooted and It went into download mode.
RUNNERX said:
Have no idea where I went wrong but after I had RR up and running I rebooted and It went into download mode.
Click to expand...
Click to collapse
Yes, it happens sometimes. Let me explain this briefly:
1. This bootloader seems to forget what the active partition was when it was told to reboot the device instead of turning itself off, and I don't know why yet. It happens 1/5 times I press on "Reboot", more or less.
2. You need to re-set the active partition to the one you were using, in my case A, so with a cable and my pc I run
Code:
fastboot set_active a && fastboot reboot
Tired of typing, I made myself a script named razer in my /usr/bin
Code:
#!/bin/zsh
fastboot set_active a && fastboot reboot
So, be careful when rebooting the device if you don't have a close-by PC with fastboot to make it work again, instead, fully turn it off and turn it back on.
el4nimal said:
Could you please tell me how you flash Magisk? After I flash a ROM I'm not able to boot into TWRP to flash Magisk
Click to expand...
Click to collapse
Just fire up a terminal with ADB and type in
Code:
adb reboot recovery
It should be more than enough, no need for root privileges or anything.
linuxct said:
Just fire up a terminal with ADB and type in
Code:
adb reboot recovery
It should be more than enough, no need for root privileges or anything.
Click to expand...
Click to collapse
I'm trying to boot into LineageOS 15.1 but it keeps saying "Decryption Unsuccessful". I followed your guide step by step, and I also tried the pre-built image you provided.
I started over from Oreo DP1 image many times and I've been getting the same error over and over again.
Then, I noticed that @ThatGuy94 mentioned he was able to get it to boot, by flashing stock boot.img and factory reset it that way, and then install the ROM and Magisk.
But I can't figure out how to install Magisk without installing TWRP, is there any fastboot command to install Magisk from the command line?
Resurrection Remix Intensifies
el4nimal said:
I'm trying to boot into LineageOS 15.1 but it keeps saying "Decryption Unsuccessful". I followed your guide step by step, and I also tried the pre-built image you provided.
I started over from Oreo DP1 image many times and I've been getting the same error over and over again.
Then, I noticed that @ThatGuy94 mentioned he was able to get it to boot, by flashing stock boot.img and factory reset it that way, and then install the ROM and Magisk.
But I can't figure out how to install Magisk without installing TWRP, is there any fastboot command to install Magisk from the command line?
Click to expand...
Click to collapse
Unless you have overwritten it, boot to download mode and use fastboot to switch to the other slot which will allow you to boot into TWRP and install Magisk. If you have overwritten TWRP, flash it on the other slot (for example if you have LOS installed in A, flash TWRP into B).
linuxct said:
So, be careful when rebooting the device if you don't have a close-by PC with fastboot to make it work again, instead, fully turn it off and turn it back on.
Click to expand...
Click to collapse
It has happened after a power off also, would putting the same rom in a&b slot stop it? system_other is not bootable so the phone enters download mode? I don't understand the working of the a/b system.
And THANK YOU so much for working on this, so nice to be back on custom roms!
How to Install TWRP Recovery & Root Essential PH-1 (Windows/Mac/Linux)
This is an alternate method on how install TWRP. This one might give you a better understanding of slots.
Another method can be found at below link. Use whatever is easier for you.
https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
Warning 1: If you can't do fastboot commands, do a flash all, root your device or flash TWRP/ROM, please do not ask for help here. If you cannot flash all back to stock, please stay stock for everyone's sake.
Warning 2: You might loose all your data. Make sure to backup your data.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Pre-Requisites
Make sure you have unlocked the bootloader.
Download and Install drivers (Windows) :- https://storage.googleapis.com/essential-static/Essential-PH1-WindowsDrivers.exe
Make sure to remove pin/password/pattern etc. Even though TWRP support decryption I personally suggest you remove it and can add it back later.
Make sure you are stock. If you are rooted, please install stock boot.img.
How to Boot into fastboot/bootloader mode
1. Reboot phone, and keep volume down pressed while device is rebooting until you see bootloader mode screen.
2. While phone is off, press volume down and then press power button. Keep holding both until you see bootloader mode screen.
How to Install
Steps
1. Download all the files listed in downloads section and place them inside one folder say ph-1.
2. Unzip fastboot and adb zip file (platform-tools). Rename twrp image file to twrp-mata.img. move twrp img file to platform-tools folder.
3. Connect phone to computer and copy below files to internal memory.
* TWRP Installer Zip
* Magisk Zip
Reboot device into bootloader mode.
4. Using command prompt/terminal navigate to folder where fastboot is.
Command Prompt
Code:
fastboot devices
Mac/Linux/Powershell
Code:
./fastboot devices
Make sure device is detected in fastboot mode.
5. Find current slot. Note this down some where.
Command Prompt
Code:
fastboot getvar current-slot
Mac/Linux/Powershell
Code:
./fastboot getvar current-slot
6. If you get current slot as
* A - we will flash twrp to slot B
* B - we will flash twrp to slot A
7. Flash TWRP to slot opposite of what we found out in Step 5.
Command Prompt
Code:
fastboot flash boot_slot twrp-mata.img
Mac/Linux/Powershell
Code:
./fastboot flash boot_slot twrp-mata.img
So, if your current slot was a, you will use boot_b above. If current slot was b, you will use boot_a above.
8. Set slot where we flashed TWRP as active.
Command Prompt
Code:
fastboot --set-active=slot
Mac/Linux/Powershell
Code:
./fastboot --set-active=slot
So, if your current slot was a, you will use --set-active=b above. If current slot was b, you will use --set-active=a above.
9. Use volume rockers till you see recovery option. Then press power button to select. You should now boot into TWRP.
If the touchscreen doesn't function, skip to instructions in post 2 below.
Now, flash TWRP installer zip file.
Once zip is flashed and has patched both slots. Go back to home screen.
Reboot.
On this screen select the slot which we had noted down in step 5.
Then reboot into system. You should now boot into Android.
10. To root. Boot back into bootloader mode. Go into TWRP recovery. Flash magisk zip. reboot.
Support :
1) Search. Search, search, search. If you make the effort of reading atleast 5 pages back, most if not all your questions will be answered. I personally, will ignore any questions, if I know they have been answered in the last 5 pages. Not being rude, but please read.
2) If you can't find answers in last 5 pages, ask here, be respectful and have a good time.
Video Guide
Downloads :
Latest ADB & Fastboot Zip File :- https://developer.android.com/studio/releases/platform-tools
TWRP for Essential Phone (need both .img and zip file) :- https://forum.xda-developers.com/es...official-twrp-3-2-3-0-essential-ph-1-t3840931
Magisk :- https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Going Back to Stock :- https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
If you flashed September Android 9.0 Pie Back to Stock (BTS) it flashes to both slots. In that case, if touch is not working please refer post 2.
Credits
@Dees_Troy for TWRP
@aer0zer0 for back to stock (BTS)
@topjohnwu for Magisk
@munchy_cool for this guide
reserved
Common Issues
Thanks to @starcms for helping with the instructions.
No touch in TWRP in Step 9.
Keep your phone connected to computer. Open command prompt/terminal/powershell.
Now we are going to install TWRP installer zip.
Command Pormpt
Code:
adb shell twrp install path/to/zip
So, let's say you have twrp installer zip (named
twrp-installer-mata-3.2.3-0.zip) in root of internal memory.
Code:
adb shell twrp install /sdcard/
twrp-installer-mata-3.2.3-0.zip
This should flash TWRP to both slots. Now, you can reboot using
Code:
adb reboot bootloader
and go back into TWRP. Check if touch is working and then set your slot to one noted in step 5.
If touch is not working use fastboot (step 8) to change the slot to that noted in Step 5..
Now boot back into TWRP using volume rockers and proceed to Step 10 (flashing Magisk zip)
Terminal/Powershell users please add ./ before the adb.
reserved 002
reserved 002
Nice write-up. I would also maybe add (to your discretion ofc) that if you flash the latest P BTS, it flashes to both slots, making touch unusable in twrp and will need to follow your addendum.
aer0zer0 said:
Nice write-up. I would also maybe add (to your discretion ofc) that if you flash the latest P BTS, it flashes to both slots, making touch unusable in twrp and will need to follow your addendum.
Click to expand...
Click to collapse
Done. Thanks for the advice :highfive:
Uh I...have a new problem. I use "adb shell twrp install" to install twrp-installer-mata-3.2.3-0.zip and it seem to work...but later I flash the stockboot and flash magisk. Than I cant boot into the system. It reboot itself to the stock recovery when it finished booted. And told me cant start up the system and two options down below "try again" "factory reset"
Is my stockboot file is incorrect?
YunolexDDP said:
Uh I...have a new problem. I use "adb shell twrp install" to install twrp-installer-mata-3.2.3-0.zip and it seem to work...but later I flash the stockboot and flash magisk. Than I cant boot into the system. It reboot itself to the stock recovery when it finished booted. And told me cant start up the system and two options down below "try again" "factory reset"
Is my stockboot file is incorrect?
Click to expand...
Click to collapse
recovery is part of boot image. if you flash stock boot, twrp is removed.
munchy_cool said:
recovery is part of boot image. if you flash stock boot, twrp is removed.
Click to expand...
Click to collapse
Yeah i know but now i wonder where goes wrong with my phone
Seem my English is not very good so....I dont know how to search the key word
So..I wonder if you have seem this situation before.
YunolexDDP said:
Yeah i know but now i wonder where goes wrong with my phone
Seem my English is not very good so....I dont know how to search the key word
So..I wonder if you have seem this situation before.
Click to expand...
Click to collapse
after installing twrp zip, if you instal stock boot or new kernel it will remove twrp.
you have to flash twrp zip after installing new kernel.
to root, boot into android once after instalinh twrp zip.
then boot back into twrp, and flash magisk zip.
munchy_cool said:
after installing twrp zip, if you instal stock boot or new kernel it will remove twrp.
you have to flash twrp zip after installing new kernel.
to root, boot into android once after instalinh twrp zip.
then boot back into twrp, and flash magisk zip.
Click to expand...
Click to collapse
I am pretty close it. Now i have my twrp install in one slot and the system can boot from another slot but uh..
do I need to flash stock boot before I flash magisk?
cus now I still cant boot the system from twrp..
the official website said "use the devices as normal" hmm..
I need to change the slot if i want to boot the system. Is that normal?
YunolexDDP said:
I am pretty close it. Now i have my twrp install in one slot and the system can boot from another slot but uh..
do I need to flash stock boot before I flash magisk?
cus now I still cant boot the system from twrp..
the official website said "use the devices as normal" hmm..
I need to change the slot if i want to boot the system. Is that normal?
Click to expand...
Click to collapse
NO you don't need to flash stock boot to instal Magisk.
yes, you need to change slot to boot system.
all of this is mentioned in first post.
i have a question, is there a way to just boot into TWRP to just flash magisk? without flashing TWRP itself? i want to recive OTAs still and all i want is just magisk installed, i tried the ,ethod of patching the boot.img but that was a huge fail please help!!!
DeimosPhobos said:
i have a question, is there a way to just boot into TWRP to just flash magisk? without flashing TWRP itself? i want to recive OTAs still and all i want is just magisk installed, i tried the ,ethod of patching the boot.img but that was a huge fail please help!!!
Click to expand...
Click to collapse
No.
We don't have fastboot boot
aer0zer0 said:
No.
We don't have fastboot boot
Click to expand...
Click to collapse
Ahhhh ok,
I figured out the patched boot image method, although when I tried to make my own patched boot IMG, it didn't work, I found a Reddit thread where someone had done it, I used theirs and it worked....although the command was supposed to be fastboot flash boot patched_boot.img and Everytime I did that it sent it to B, but failed on the write, they yelled at me saying that's the command and it should work lol, but I had to actually put fastboot flash boot_b patched_boot.img....the damn A/B partition stuff confuses me Alot lol
DeimosPhobos said:
Ahhhh ok,
I figured out the patched boot image method, although when I tried to make my own patched boot IMG, it didn't work, I found a Reddit thread where someone had done it, I used theirs and it worked....although the command was supposed to be fastboot flash boot patched_boot.img and Everytime I did that it sent it to B, but failed on the write, they yelled at me saying that's the command and it should work lol, but I had to actually put fastboot flash boot_b patched_boot.img....the damn A/B partition stuff confuses me Alot lol
Click to expand...
Click to collapse
sometimes older fastboot versions dont work well with Essential.
for ab slots, if you are want to flash magisk pre-rooted boot.img
just do
fastboot gervar current-slot (say you get a)
and then flash boot.img to current slot.
fastboot flash boot_a nameofboot.img
munchy_cool said:
sometimes older fastboot versions dont work well with Essential.
for ab slots, if you are want to flash magisk pre-rooted boot.img
just do
fastboot gervar current-slot (say you get a)
and then flash boot.img to current slot.
fastboot flash boot_a nameofboot.img
Click to expand...
Click to collapse
essential's driver package for windows doesnt require _a,_b unless you are being specific
fastboot flash boot whatever will work and flash to the current slot if your using essentials (which is an older version) if your using a newer version from google or minimal, it gives the __a or b error trying to append an extra underscore
aer0zer0 said:
essential's driver package for windows doesnt require _a,_b unless you are being specific
fastboot flash boot whatever will work and flash to the current slot if your using essentials (which is an older version) if your using a newer version from google or minimal, it gives the __a or b error trying to append an extra underscore
Click to expand...
Click to collapse
true, but not everyone is on Windows :highfive:
munchy_cool said:
true, but not everyone is on Windows :highfive:
Click to expand...
Click to collapse
Poor Linux folks ?
aer0zer0 said:
Poor Linux folks
Click to expand...
Click to collapse
lol.
Essential is the only phone to give me issues with fastboot though.
munchy_cool said:
lol.
Essential is the only phone to give me issues with fastboot though.
Click to expand...
Click to collapse
Tell me about it, lol.
---------- Post added at 12:00 PM ---------- Previous post was at 11:46 AM ----------
aer0zer0 said:
Tell me about it, lol.
Click to expand...
Click to collapse
Never seen a phone so finicky. I've also got the holy Grail cable that I don't let out of my sight. I've often wondered what makes it so finicky, and I come from a long line of HTC and motos
So if anyone is interested in booting a GSI Image Here is the guide: also thanks to @Dollscythe I just updated it as he forget to write me a step for flashing the vbmeta.img..
1. you need to download the firmware file for your model
2. you need to open it with your zipping software of choice (i use 7zip) And after it unzips you need to unzip AP file to get to the recovery.img.lz4
3. you extract the recovery.img and you patch it to enable fastbootd https://github.com/Johx22/Patch-Recovery you will also find the info how to patch it on the link, it is easy if you know how to follow it) - Currently is NOT working, the dev said to me that he will fix this once his exams are over. (If you know how to Decompress the Iz4.img to get just the .img it will probably work - didn't try tho.
4. this step will wipe your device so make sure to back up (unlocking the bootloader) And it will also trigger your Knox!
To unlock the bootloader you need to go to settings, about phone - software info and press on the build number like 7times to enable developer options. After that go to developer options and enable OEM unlock.
Turn off the phone, put the USB C cable into the phone (but not into the computer yet!) Then hold the volume + and volume - button at the same time and put the cable into the phone.
When you are in the download mod you will see the instructions on how to unlock the bootloader.
5. Boot into the system and do the first time setup (make sure to connect to wifi, but skip any prompts to register or login to accounts)
6. double check if the oem unlock toggle is still on, then reboot to download mode
7. you need to flash the patched bootloader using odin - you flash your patched recovery in AP window in Odin. Then you immediately boot into the recovery (you gotta boot to your new recovery immediately after the flash is complete, make sure to hold the key combination for recovery immediately after pressing start in odin to get it right. otherwise, the system will wipe your newly flashed recovery and you'll have to do step 7 again)
8. You will now notice that your recovery has a new option: fastbootd mode (yes there's a d in there, it's not a typo, it stands for fastbootdynamic mode) 9. once you're in, your device now officially supports fastboot. you just do "fastboot flash system *the_name_of_the_system_image_you_downloaded.img", RIGHT AWAY AFTER THAT flash vbmeta.img (it can be found in the telegram group) and once that is done flashing just exit fastbootd mode back to the recovery, then format data and then then reboot for system images, i recommend pixel experience https://github.com/ponces/treble_bu...4-ab-vndklite-12.1-20220518-UNOFFICIAL.img.xz 10. you'll be greeted by a google bootlogo and thats a success.
Good luck!
Bucika said:
RIGHT AWAY AFTER THAT flash vbmeta.img (it can be found in the telegram group)
Click to expand...
Click to collapse
I'd just add that the proper command to flash vbmeta.img is ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (I don't use "./" though, as I've included platform-tools in my path env variable).
Not disabling verity/verification sent me to a bootloop from hell after rebooting... I began reading more carefully the Telegram chat, found the proper command and I'm now setting my PixExp as I write.
One thing I wish people on here would give more instructions than they do it's not easy on button the recovery image I don't know why you say it's easy cause it's not that makes no sense you don't put no links into the description of where to ago why don't somebody do like they used to do and actually give a s*** about what they put on this website
jdg007 said:
One thing I wish people on here would give more instructions than they do it's not easy on button the recovery image I don't know why you say it's easy cause it's not that makes no sense you don't put no links into the description of where to ago why don't somebody do like they used to do and actually give a s*** about what they put on this website
Click to expand...
Click to collapse
The purpose of XDA "Developers" was actually to share knowledge between developers, you know, people who actually know how the most basic stuff works. It's open up for the public, sure, but most of the stuff you can find here are not meant for the average noob that doesn't know how to unlock a bootloader.
The instructions are pretty clear for people who can use a google search. Don't expect everything to be spoon fed, put in a little effort.
There's a difference between saying "OMG this is too complicated why don't you explain it with a video or why don't you tell me step by step on how to flash custom firmware on my phone" and saying "Hey I'm stuck in step 3, I don't understand the part here. This is what I've tried so far..."
I bet for the most part, the first person would be ignored while the second person would more likely get a response.
That means to offend you in any way or whatever I just wished people would give more explanations on what they post because you know I don't make no sense on how you patch the recovery I'm new at this it's my it's my fault I do know how to unlock bootloaders not bootleggers and I do know how to install TWRP and Flash zip balls but as when it comes to patching something the only thing I know how to pack is using magisk That's the boot image I'm sorry hope Hope you can help me out
If you don't mind email me a copy of that recovery image that you got Text I sure would appreciate it Just looking forward For your reply
Thanks @Bucika, here's a guide that might be a bit more noob friendly. Also a big thanks to @Dollscythe for their help.
Files can be found here.
These are the latest GSIs.
1. Unlock bootloader by opening developer options and flipping the "unlock bootloader" switch.
2. Boot into download mode (press and hold vol + and - while plugging into computer).
Press and hold vol + to enter unlock mode. Accept and click enter. Your phone will reset.
3. Using Odin, flash fastbootd through AP. (recovery.img).
4. Press and hold volume + key as the phone reboots, as when you restart again it will reverse this step. You should be in recovery now.
Click on fastboot.
5. Get fastboot working on your computer. Test connection by using the command "fastboot devices" to see if your device is there.
6. Run the command fastboot flash system [name of gsi file]. (without square brackets)
7. When you're done, run ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
8. Go back to recovery and wipe your phone.
9. Go back into fastboot, flash magisk file if you would like root: fastboot flash boot magisk
10. Wipe again, reboot.
11. Once you are fully booted in, open settings > phh settings (first entry) > misc settings > then scroll down until you find "force fps"
Change that to the @120fps option.
Hope this helps! Note that this is unofficial and WiFi hotspot doesn't work, Samsung Health has issues too. I couldn't get my watch 4 working with GSI.
This will blow your Knox bit fuse!
Ivan Fuentes Hagar said:
I'd just add that the proper command to flash vbmeta.img is ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (I don't use "./" though, as I've included platform-tools in my path env variable).
Not disabling verity/verification sent me to a bootloop from hell after rebooting... I began reading more carefully the Telegram chat, found the proper command and I'm now setting my PixExp as I write.
Click to expand...
Click to collapse
I find myself in a bootloop too after this step, how did you get out of the bootloop?
edit, answer to my own question in case it helps someone in the future: plug phone into a pc and then hold `volume up + volume down` buttons to enter download mode.
edit 2 if after flashing a GSI rom your device wont boot, plug it into power and wait a few minutes.
I know I am kind of late but after flashing the pixel experience GSI, it is stuck in the google logo. What do I do?
ActuallyJammy said:
I know I am kind of late but after flashing the pixel experience GSI, it is stuck in the google logo. What do I do?
Click to expand...
Click to collapse
flash another gsi this gsi doesn't work on a53 unless you use pixel experience 12
TringQuack said:
flash another gsi this gsi doesn't work on a53 unless you use pixel experience 12
Click to expand...
Click to collapse
Alright, so I got an old build of PE 13 to work, but somewhy the newer security patches don't work. Is there any reason, or is it just not compatible at all? Also, there's a problem with the fingerprint; it detects it as if the fingerprint scanner is in the back when it is on the screen. Is there any fix? Mainly because it's my primary phone.
ActuallyJammy said:
Alright, so I got an old build of PE 13 to work, but somewhy the newer security patches don't work. Is there any reason, or is it just not compatible at all? Also, there's a problem with the fingerprint; it detects it as if the fingerprint scanner is in the back when it is on the screen. Is there any fix? Mainly because it's my primary phone.
Click to expand...
Click to collapse
new patch was introduced in trebledroid that fixes this fingerprint issue, you can either use another gsi built on trebledroid on the date of jan 31 or later, or wait for Ponces to make a new PE build for A13
TringQuack said:
new patch was introduced in trebledroid that fixes this fingerprint issue, you can either use another gsi built on trebledroid on the date of jan 31 or later, or wait for Ponces to make a new PE build for A13
Click to expand...
Click to collapse
Could you give me a GSI rom with a patch and similar to PE?
@TringQuack What's your current state with A53?
Running GSI? Stock?
ThugMaster said:
@TringQuack What's your current state with A53?
Running GSI? Stock?
Click to expand...
Click to collapse
Stock
@TringQuack How do I know if the build is compatible with A13?
Hello everyone hope you are all keeping well.
Here is a little guide on how to Unlock/Lock the Bootloader and Root/Unroot our Nord2T.
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
Unlock The Bootloader;
If you haven't done it already...beware that this will erase all of your user data. To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
Code:
adb devices
(just to make sure that your phone is, in fact, recognized by your PC and that you're able to run adb commands)
Code:
adb reboot bootloader
(so your phone will reboot into fastboot mode)
Code:
fastboot flashing unlock
(device should now unlock)
Code:
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
Rooting Guide;
Unlocking the Bootloader is necessary before continuing
1 - Download Nord2T stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your devices internal memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...you never know if you will need to use it again in the future...to restore the stock boot.img, aka revert to stock...)
Spoiler: Global Build boot.img's
Stock boot CPH2399_11_A.07 (did not extract it and can't find the firmware file to be able to download and extract, if someone could please upload a link to it on this thread I would sincerely appreciate it)
Stock Boot CPH2399_11_A.09
Stock Boot CPH2399_11_A.11
Stock Boot CPH2399_11_A.14
Stock Boot CPH2399_11_A.15
Stock Boot CPH2399_11_A.16
Stock Boot CPH2399_11_A.17
Stock Boot CPH2399_11_A.19
Stock Boot CPH2399_11_C.24
Stock Boot CPH2399_11_C.26
Stock Boot CPH2399_11_C.27
Spoiler: IND Build boot.img's
Stock Boot CPH2401_11_A.11
Stock Boot CPH2401_11_A.13
Stock Boot CPH2401_11_A.14
Stock Boot CPH2401_11_A.15
Stock Boot CPH2401_11_A.16
Stock Boot CPH2401_11_A.17
Stock Boot CPH2401_11_A.18
Stock Boot CPH2401_11_A.19 (I didn't capture the download for this, if anyone has it please send me a link to the official OTA)
Stock Boot CPH2401_11_C.23
Stock Boot CPH2401_11_C.24
Stock Boot CPH2401_11_C.26
Stock Boot CPH2401_11_C.27
2 - Download latest Magisk Manager from HERE and install it on your phone
3 - Open Magisk Manager App and press:
Install
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
4 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
5 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot reboot
6 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
7 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
System Updates;
For system updates. Just apply the OTA update as normal.
Once updated you will have no root and you must follow steps above again with the new boot.img that corresponds to the firmware version you are on.
Unroot;
To unroot simply flash the stock boot.img.
Relock Bootloader;
If you have TWRP installed flash the stock boot.img (same as your firmware version from earlier in this post)
This is so as you can access fastboot properly.
1 - To relock Bootloader first download Oxygen Updater app from the Playstore.
2 - Download the firmware which corresponds to the firmware which you have currently installed.
3 - Move/copy this firmware.zip to your PC and extract it. (inside you will see a folder and a couple files. The only file we need is payload.bin)
4 - Download/install Fastboot Enhance on your PC
5 - Reboot phone to bootloader mode so it gets detected by Fastboot Enhance, from there boot to fatsbootd.
6 - Flash payload.bin in Fastboot Enhance
7 - Wipe data in fastbootd from your Nord 2T, reboot and finish phone setup.
8 - Enable developer options, enable USB debugging from developer options.
9 - Reboot to bootloader and run the command;
Code:
fastboot flashing lock
The device will be now successfully locked.
Hope this helps out
Thank you so much
Thanks so much. Going to try this weekend with my daughter phone.
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
jolaviska said:
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
Click to expand...
Click to collapse
No I still haven't received the ota. Did you get updated to this version already?
I received the update but refusing to apply it
jolaviska said:
I received the update but refusing to apply it
Click to expand...
Click to collapse
It will show up again.
Don't worry.
Rooted my Nord 2T successfully. Thanks once again
Download Nord2T stock boot.img
Click to expand...
Click to collapse
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
luke! said:
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
Click to expand...
Click to collapse
By using THIS software. I will always update this thread with the latest boot.img files in the future but this is the software I used
Thank you.
And what is the procedure to OTA update, once we have magisk_patched_boot.img installed.
OTA won't install, so need to revert somehow install new update and root again?
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Stock Global boot CPH2399_11_A.11 added to OP. Sorry for the delay, only received the update today
nielsync said:
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Click to expand...
Click to collapse
Ya I didnt do it this way at all because my device updated while i was asleep and i was unrooted, so I had to patch the new boot using the method in the OP.
I would definitely advise restoring the stock boot.img before proceeding with an update, then install the update normally and just patch the new image with magisk and then flash.
For a while the 'install to inactive slot' option only works on certain devices, the Nord 2T obviously is'nt one of those devices.
I'm sure the magisk documentation recommends restoring stock images before an update.
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
cioce said:
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
Click to expand...
Click to collapse
I didn't want to share any of the magisk images because there is a new version of magisk every other week and people may like to be on the beta branch or canary branch of magisk or whatever.
It's very easy to patch the image though. Just download magisk.apk and use it to patch the boot.img's I've provided above. Then move the patched.img to your pc and flash.
But anyways here is the magisk patched.img for CPH2399_11_A.11 using magisk 25.2 stable
Stock Boot for Indian variant CPH2401_11_A.13 added to OP
can u post the latest update boot.img for indian unit CPH2401_11_A.14
Stock boot for Indian CPH2401_11_A.14 added to OP
Stock boot for Global CPH2399_11_A.14 added to OP